Thinkpad X61s is unable to boot 9.1-BETA1. A verbose boot, last line is acpi_acad: acline initialization done, tried 1 times Issuing a 'set debug.acpi.disabled="hostres"' does not help. Disabling ACPI altogether does not help either, boot stops at "No usable eventtimer found". How-To-Repeat: Try to install 9.1-BETA on a Thinkpad X61s
Can you capture more lines from a verbose dmesg? Also, how are you booting? Are you booting from a CD or netbooting via PXE? -- John Baldwin
Update: It appears it is only one of our X61s's (mine, of course) that does not boot 9.1-BETA1, we are currently looking into exactly what causes this. More on this as soon as we know.
More info: Thinkpad X61s 7669-29G, latest BIOS Disk: Kingston SSDNow SV200S37A/128G, firmware E111008a With this drive, it will not boot BETA1, 9.0-RELEASE is fine. Checked with a mechanical driva and then it boots fine. Will try to upgrade firmware on SSD drive to check if it remedies. Selected dmesg parts: ---- atapci0: <Intel ICH8M UDMA100 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x18e0-0x18ef at device 31.1 on pci0 ata0: <ATA channel> at channel 0 on atapci0 ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 59 ahci0: <Intel ICH8M AHCI SATA controller> port 0x1c30-0x1c37,0x1c24-0x1c27,0x1c28-0x1c2f,0x1c20-0x1c23,0x1c00-0x1c1f mem 0xfe226000-0xfe2267ff irq 16 at device 31.2 on pci0 ahci0: attempting to allocate 1 MSI vectors (4 supported) msi: routing MSI IRQ 258 to local APIC 0 vector 60 ahci0: using IRQ 258 for MSI ahci0: AHCI v1.10 with 3 3Gbps ports, Port Multiplier not supported ahci0: Caps: 64bit NCQ SNTF ALP AL CLO 3Gbps PMD SSC PSC 32cmd CCC 3ports ahci0: Caps2: ahcich0: <AHCI channel> at channel 0 on ahci0 ahcich0: Caps: ahcich1: not probed (disabled) ahcich2: <AHCI channel> at channel 2 on ahci0 ahcich2: Caps: ---- ata0: reset tp1 mask=03 ostat0=7f ostat1=7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat0=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: stat1=0x7f err=0x7f lsb=0x7f msb=0x7f ata0: reset tp2 stat0=ff stat1=ff devices=0x0 ahcich0: AHCI reset... ahcich0: SATA connect time=3200us status=00000123 ahcich0: AHCI reset: device found ahcich0: AHCI reset: device ready after 0ms ahcich2: AHCI reset... ahcich2: SATA offline status=00000004 ahcich2: AHCI reset: device not found battery0: battery initialization start acpi_acad0: acline initialization start battery0: battery initialization done, tried 1 times acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times ---- Hangs here ----
Updated disk firmware to latest, no change.
Could you try to enable CAM debugging by setting kern.cam.dflags=0xff loader tunable either from loader prompt or /boot/loader.conf? It should tell us on what stage of device detection hang happens. -- Alexander Motin
Setting kern.eventtimer.timer="i8254" makes boot possible as per the discussion on the list Links to dmesg and log below. Unfortunately enabling cam debugging seem to create more info than the buffer takes. ----- Attachments (Links will expire on 03/31/2013) http://webmail.bsdlabs.com/imp/attachment.php?f=dmesg-x61s-nocamdebug&t=1347662983&u=peo http://webmail.bsdlabs.com/imp/attachment.php?f=boot-messages-x61s-nocamdebug&t=1347662983&u=peo
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped
Unfortunately this PR was never addressed before these versions of FreeBSD went out of support. Sorry. If this is still a problem, please open a new PR. Thanks.