Lenovo A740 gave up waiting for root device with kernels >= 4.3
Hi,
I have a Lenovo A740 (running Xubuntu 16.04) which, with kernel versions >= 4.3.0, tested up until 4.7.0, gives this on trying to boot:
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done. […]
done.
Gave up waiting for root device.
and drops me into an (initramfs) shell, where my keyboard is unresponsive. The last kernel I tried which booted fine was 4.2.8.
I reported this at https://bugzilla.kernel.org/show_bug.cgi?id=118401
and, after some investigation, was asked to contact ahci.c - AHCI SATA support. The attachments in that report show some output from initramfs (using a script in /etc/initramfs-tools/scripts/init-premount due to the keyboard not working).
What should I do to keep debugging this issue?
best regards,
Kevin Brubeck Unhammer
Quoted 16 lines · Kevin Brubeck Unhammer
Hi,
I have a Lenovo A740 (running Xubuntu 16.04) which, with kernel versions >= 4.3.0, tested up until 4.7.0, gives this on trying to boot:
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done. […]
done.
Gave up waiting for root device.and drops me into an (initramfs) shell, where my keyboard is unresponsive. The last kernel I tried which booted fine was 4.2.8.
Quoted 8 lines
I reported this at https://bugzilla.kernel.org/show_bug.cgi?id=118401
and, after some investigation, was asked to contactahci.c- AHCI SATA support. The attachments in that report show some output from initramfs (using a script in/etc/initramfs-tools/scripts/init-premountdue to the keyboard not working).What should I do to keep debugging this issue?
I have been working with Kevin on the bug 118401 .
I'll post the summary.
The kernel 4.2 works and he is able to boot the system. Kernel 4.4 and 4.6, 4.7 drops into initramfs shell for the same uuid. Upon further investigation cat /proc/devices showed no block devices other than zram and loop.The command /sbin/blkid on 4.6 and later didn't give any output whereas on 4.2 it does.
Kernel 4.2 shows the ahci used count is 3
ahci 36864 3 - Live 0x0000000000000000
libahci 32768 1 ahci, Live 0x0000000000000000
Where kernel 4.7 doesn't load the ahci module upon boot and upon modprobe ahci from the initramfs shell it shows the ahci count as 0. So it is not detecting the drive. Not sure why ?
Some more things to note from 4.2 dmesg it prints not sure if it is relevant.
[ 0.716610] ahci 0000:00:1f.2: version 3.0 [ 0.716620] ahci 0000:00:1f.2: can't find IRQ for PCI INT B;
probably buggy MP table
[ 0.735267] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 4 ports 6
Gbps 0x1 impl SATA mode
[ 0.746033] ata1: SATA max UDMA/133 abar m2048@0xb5618000 port
0xb5618100 irq 44
[ 1.068001] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1.134029] ata1.00: ATA-8: ST1000LM014-1EJ164-SSHD-8GB, LIV6, max UDMA/133 [ 1.134030] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 1.178470] ata1.00: configured for UDMA/133 [ 1.178620] scsi 0:0:0:0: Direct-Access ATA ST1000LM014-1EJ1 LIV6 PQ: 0 ANSI: 5 [ 1.178853] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 1.178855] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 1.178879] sd 0:0:0:0: [sda] Write Protect is off [ 1.178881] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
where as 4.6 and later doesn't print these messages.dmesg | grep ata[0-4] gives no output.
lspci on 4.2 gives this
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04) (prog-if 01 [AHCI 1.0])
Subsystem: Lenovo 8 Series SATA Controller 1 [AHCI mode]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 44
Region 0: I/O ports at 6088 [size=8]
Region 1: I/O ports at 6094 [size=4]
Region 2: I/O ports at 6080 [size=8]
Region 3: I/O ports at 6090 [size=4]
Region 4: I/O ports at 6060 [size=32]
Region 5: Memory at b5618000 (32-bit, non-prefetchable) [size=2K]
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0400c Data: 4181
Capabilities: [70] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
Kernel driver in use: ahci
Kernel modules: ahci
Regards,
Navin
Hello,
Quoted 26 lines · Navin P.S
Some more things to note from 4.2 dmesg it prints not sure if it is relevant.
[ 0.716610] ahci 0000:00:1f.2: version 3.0 [ 0.716620] ahci 0000:00:1f.2: can't find IRQ for PCI INT B;probably buggy MP table
[ 0.735267] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 4 ports 6Gbps
0x1impl SATA mode[ 0.746033] ata1: SATA max UDMA/133 abar m2048@0xb5618000 port
0xb5618100irq 44[ 1.068001] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)[ 1.134029] ata1.00: ATA-8: ST1000LM014-1EJ164-SSHD-8GB, LIV6, max UDMA/133 [ 1.134030] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 1.178470] ata1.00: configured for UDMA/133 [ 1.178620] scsi 0:0:0:0: Direct-Access ATA ST1000LM014-1EJ1 LIV6 PQ: 0 ANSI: 5 [ 1.178853] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 1.178855] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 1.178879] sd 0:0:0:0: [sda] Write Protect is off [ 1.178881] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Quoted 2 lines
where as 4.6 and later doesn't print these messages.dmesg | grep ata[0-4] gives no output.
Can you please cc full dmesg after boot on both 4.2 and 4.6?
Thanks.
Signature · 1 line
tejun
Tejun Heo <[email protected]> čálii:
Quoted 3 lines
Can you please cc full dmesg after boot on both 4.2 and 4.6?
Thanks.
Hi,
dmesg from 4.2 is attached; from 4.6 I'm not sure how to get it …
perhaps I could mount a USB-stick through a /etc/initramfs-tools/scripts/init-premount/ script, I'll try this later (I'm travelling this week, so might be a bit delayed).
regards,
Kevin
Quoted 5 lines · Kevin Brubeck Unhammer
dmesg from 4.2 is attached; from 4.6 I'm not sure how to get it …
perhaps I could mount a USB-stick through a
/etc/initramfs-tools/scripts/init-premount/script, I'll try this later (I'm travelling this week, so might be a bit delayed).
You can also use serial or netconsole.
Thanks.
Signature · 1 line
tejun
Tejun Heo <[email protected]> čálii:
Quoted 10 lines · Kevin Brubeck Unhammer
Quoted 5 lines
dmesg from 4.2 is attached; from 4.6 I'm not sure how to get it …
perhaps I could mount a USB-stick through a
/etc/initramfs-tools/scripts/init-premount/script, I'll try this later (I'm travelling this week, so might be a bit delayed).You can also use serial or netconsole.
Thanks.
I'm still working on getting the full dmesg text :-/
There's no /dev/sd[abcd] when I have a USB-stick in there, so I don't know how I would mount that (and from 4.7 initramfs script a "dmesg|grep /dev/sd[abcd]" gives nothing).
I got netconsole working from the booted 4.2, but when I try from the 4.7 initramfs script it can't find eth0 even though I have r8169 in modules.
It seems r8169 is the right driver since 4.2 shows
$ grep DRIVER /sys/class/net/*/device/uevent /sys/class/net/eth0/device/uevent:DRIVER=r8169 /sys/class/net/wlan0/device/uevent:DRIVER=rtl8723au
I tried
/etc/initramfs-tools/modules:
r8169
ahci
libahciuhci_hcdehci_hcdusb_storage
configfs
netconsole
/etc/initramfs-tools/scripts/init-premount/kbu-blkid:
echo 'cat /proc/scsi/scsi # gives:'
cat /proc/scsi/scsi
echo 'dmesg | grep -i libata # gives:'
dmesg | grep -i libata
echo 'grep -i ahci /proc/modules # gives:'
grep -i ahci /proc/modules
echo 'modprobe ahci # gives:'
modprobe ahci
echo 'grep -i ahci /proc/modules # gives:'
grep -i ahci /proc/modules
dmesg |grep -i eth
mount none -t configfs /sys/kernel/config mkdir /sys/kernel/config/netconsole/target1 cd /sys/kernel/config/netconsole/target1
echo 0 >enabled
echo 192.168.1.117 > local_ip
echo 192.168.1.2 >remote_ip
echo eth0 >dev_name
echo 68:05:CA:29:E4:7F >remote_mac
echo 6666 > remote_port
echo 1 >enabled
echo kbu-testing >/dev/kmsg
echo 'dmesg | tail'
dmesg | tail
echo "/KBU"
and got
http://bildr.no/image/dXFjbkEw.jpeg
http://bildr.no/image/MUpqLzZx.jpeg
I guess I'll have to start shopping for (two) USB-to-serial cables.
Hi again,
Navin found a workaround: acpi=noirq (and pci=noacpi) lets me boot with the newer kernels.
Attached are dmesg's from 4.7rc2 and 4.7rc5 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ (rc5 complained about missing noveau firmware; I haven't tried the newest linux-firmware package yet, but haven't yet seen anything *not* working in rc5 that was working in rc2).
Other changes when using acpi=noirq that may or may not be relevant:
The computer will now poweroff when I do a shutdown, and restarts correctly (it used to just "hang" at the end of the shutdown sequence), and a bluetooth device shows up that I didn't know I had. However, although I seem to be able to suspend, I can't resume (no response when hitting power button). All in all an improvement though …
best regards,
Kevin Brubeck Unhammer
"Navin P.S" <[email protected]> čálii:
Quoted 102 lines
Quoted 16 lines · Kevin Brubeck Unhammer
Hi,
I have a Lenovo A740 (running Xubuntu 16.04) which, with kernel versions >= 4.3.0, tested up until 4.7.0, gives this on trying to boot:
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done. […]
done.
Gave up waiting for root device.and drops me into an (initramfs) shell, where my keyboard is unresponsive. The last kernel I tried which booted fine was 4.2.8.
Quoted 8 lines
I reported this at https://bugzilla.kernel.org/show_bug.cgi?id=118401
and, after some investigation, was asked to contactahci.c- AHCI SATA support. The attachments in that report show some output from initramfs (using a script in/etc/initramfs-tools/scripts/init-premountdue to the keyboard not working).What should I do to keep debugging this issue?
I have been working with Kevin on the bug 118401 .
I'll post the summary.
The kernel 4.2 works and he is able to boot the system. Kernel 4.4 and 4.6, 4.7 drops into initramfs shell for the same uuid. Upon further investigation cat/proc/devicesshowed no block devices other than zram and loop.The command/sbin/blkidon 4.6 and later didn't give any output whereas on 4.2 it does.Kernel 4.2 shows the ahci used count is 3
ahci 36864 3 - Live0x0000000000000000
libahci 32768 1 ahci, Live0x0000000000000000Where kernel 4.7 doesn't load the ahci module upon boot and upon modprobe ahci from the initramfs shell it shows the ahci count as 0. So it is not detecting the drive. Not sure why ?
Some more things to note from 4.2 dmesg it prints not sure if it is relevant.
[ 0.716610] ahci 0000:00:1f.2: version 3.0 [ 0.716620] ahci 0000:00:1f.2: can't find IRQ for PCI INT B;probably buggy MP table
[ 0.735267] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 4 ports 6Gbps
0x1impl SATA mode[ 0.746033] ata1: SATA max UDMA/133 abar m2048@0xb5618000 port
0xb5618100irq 44[ 1.068001] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)[ 1.134029] ata1.00: ATA-8: ST1000LM014-1EJ164-SSHD-8GB, LIV6, max UDMA/133 [ 1.134030] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 1.178470] ata1.00: configured for UDMA/133 [ 1.178620] scsi 0:0:0:0: Direct-Access ATA ST1000LM014-1EJ1 LIV6 PQ: 0 ANSI: 5 [ 1.178853] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 1.178855] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 1.178879] sd 0:0:0:0: [sda] Write Protect is off [ 1.178881] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00where as 4.6 and later doesn't print these messages.dmesg | grep ata[0-4] gives no output.
lspci on 4.2 gives this
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04) (prog-if 01 [AHCI 1.0])
Subsystem: Lenovo 8 Series SATA Controller 1 [AHCI mode]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 44
Region 0: I/O ports at 6088 [size=8]
Region 1: I/O ports at 6094 [size=4]
Region 2: I/O ports at 6080 [size=8]
Region 3: I/O ports at 6090 [size=4]
Region 4: I/O ports at 6060 [size=32]
Region 5: Memory atb5618000(32-bit, non-prefetchable) [size=2K]
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address:fee0400cData: 4181
Capabilities: [70] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mAPME(D0-,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
Kernel driver in use: ahci
Kernel modules: ahciRegards,
Navin
Quoted 22 lines · Kevin Brubeck Unhammer
Hi again,
Navin found a workaround: acpi=noirq (and pci=noacpi) lets me boot with the newer kernels.
Attached are dmesg's from 4.7rc2 and 4.7rc5 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ (rc5 complained about missing noveau firmware; I haven't tried the newest linux-firmware package yet, but haven't yet seen anything *not* working in rc5 that was working in rc2).Other changes when using acpi=noirq that may or may not be relevant:
The computer will now poweroff when I do a shutdown, and restarts correctly (it used to just "hang" at the end of the shutdown sequence), and a bluetooth device shows up that I didn't know I had. However, although I seem to be able to suspend, I can't resume (no response when hitting power button). All in all an improvement though …
Quoted 105 lines
best regards,
Kevin Brubeck Unhammer"Navin
P.S" <[email protected]> čálii:Quoted 98 lines
Quoted 16 lines · Kevin Brubeck Unhammer
Hi,
I have a Lenovo A740 (running Xubuntu 16.04) which, with kernel versions >= 4.3.0, tested up until 4.7.0, gives this on trying to boot:
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done. […]
done.
Gave up waiting for root device.and drops me into an (initramfs) shell, where my keyboard is unresponsive. The last kernel I tried which booted fine was 4.2.8.
Quoted 8 lines
I reported this at https://bugzilla.kernel.org/show_bug.cgi?id=118401
and, after some investigation, was asked to contactahci.c- AHCI SATA support. The attachments in that report show some output from initramfs (using a script in/etc/initramfs-tools/scripts/init-premountdue to the keyboard not working).What should I do to keep debugging this issue?
I have been working with Kevin on the bug 118401 .
I'll post the summary.
The kernel 4.2 works and he is able to boot the system. Kernel 4.4 and 4.6, 4.7 drops into initramfs shell for the same uuid. Upon further investigation cat/proc/devicesshowed no block devices other than zram and loop.The command/sbin/blkidon 4.6 and later didn't give any output whereas on 4.2 it does.Kernel 4.2 shows the ahci used count is 3
ahci 36864 3 - Live0x0000000000000000
libahci 32768 1 ahci, Live0x0000000000000000Where kernel 4.7 doesn't load the ahci module upon boot and upon modprobe ahci from the initramfs shell it shows the ahci count as 0. So it is not detecting the drive. Not sure why ?
Some more things to note from 4.2 dmesg it prints not sure if it is relevant.
[ 0.716610] ahci 0000:00:1f.2: version 3.0 [ 0.716620] ahci 0000:00:1f.2: can't find IRQ for PCI INT B;probably buggy MP table
[ 0.735267] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 4 ports 6Gbps
0x1impl SATA mode[ 0.746033] ata1: SATA max UDMA/133 abar m2048@0xb5618000 port
0xb5618100irq 44[ 1.068001] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)[ 1.134029] ata1.00: ATA-8: ST1000LM014-1EJ164-SSHD-8GB, LIV6, max UDMA/133 [ 1.134030] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 1.178470] ata1.00: configured for UDMA/133 [ 1.178620] scsi 0:0:0:0: Direct-Access ATA ST1000LM014-1EJ1 LIV6 PQ: 0 ANSI: 5 [ 1.178853] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 1.178855] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 1.178879] sd 0:0:0:0: [sda] Write Protect is off [ 1.178881] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00where as 4.6 and later doesn't print these messages.dmesg | grep ata[0-4] gives no output.
lspci on 4.2 gives this
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04) (prog-if 01 [AHCI 1.0])
Subsystem: Lenovo 8 Series SATA Controller 1 [AHCI mode]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 44
Region 0: I/O ports at 6088 [size=8]
Region 1: I/O ports at 6094 [size=4]
Region 2: I/O ports at 6080 [size=8]
Region 3: I/O ports at 6090 [size=4]
Region 4: I/O ports at 6060 [size=32]
Region 5: Memory atb5618000(32-bit, non-prefetchable) [size=2K]
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address:fee0400cData: 4181
Capabilities: [70] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mAPME(D0-,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
Kernel driver in use: ahci
Kernel modules: ahci
Hi,
The default kernel parametes doesn't detect disk whereas when you
pass kernel command line (acpi=noirq or pci=noacpi) the disk is detected and the machine is usable.
Should this be forwarded to linux-acpi list ?
This machine was usuable without any arguments like acpi=noirq and pci=noacpi in 4.2 .
What does this usually indicate buggy bios ?
I can see some parse execution error in dmesg attached.
Regards,
Navin
(cc'ing ACPI folks and retaining message body for context)
Quoted 138 lines · Navin P.S
Quoted 22 lines · Kevin Brubeck Unhammer
Hi again,
Navin found a workaround: acpi=noirq (and pci=noacpi) lets me boot with the newer kernels.
Attached are dmesg's from 4.7rc2 and 4.7rc5 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/ (rc5 complained about missing noveau firmware; I haven't tried the newest linux-firmware package yet, but haven't yet seen anything *not* working in rc5 that was working in rc2).Other changes when using acpi=noirq that may or may not be relevant:
The computer will now poweroff when I do a shutdown, and restarts correctly (it used to just "hang" at the end of the shutdown sequence), and a bluetooth device shows up that I didn't know I had. However, although I seem to be able to suspend, I can't resume (no response when hitting power button). All in all an improvement though …Quoted 105 lines
best regards,
Kevin Brubeck Unhammer"Navin
P.S" <[email protected]> čálii:Quoted 98 lines
Quoted 16 lines · Kevin Brubeck Unhammer
Hi,
I have a Lenovo A740 (running Xubuntu 16.04) which, with kernel versions >= 4.3.0, tested up until 4.7.0, gives this on trying to boot:
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done. […]
done.
Gave up waiting for root device.and drops me into an (initramfs) shell, where my keyboard is unresponsive. The last kernel I tried which booted fine was 4.2.8.
Quoted 8 lines
I reported this at https://bugzilla.kernel.org/show_bug.cgi?id=118401
and, after some investigation, was asked to contactahci.c- AHCI SATA support. The attachments in that report show some output from initramfs (using a script in/etc/initramfs-tools/scripts/init-premountdue to the keyboard not working).What should I do to keep debugging this issue?
I have been working with Kevin on the bug 118401 .
I'll post the summary.
The kernel 4.2 works and he is able to boot the system. Kernel 4.4 and 4.6, 4.7 drops into initramfs shell for the same uuid. Upon further investigation cat/proc/devicesshowed no block devices other than zram and loop.The command/sbin/blkidon 4.6 and later didn't give any output whereas on 4.2 it does.Kernel 4.2 shows the ahci used count is 3
ahci 36864 3 - Live0x0000000000000000
libahci 32768 1 ahci, Live0x0000000000000000Where kernel 4.7 doesn't load the ahci module upon boot and upon modprobe ahci from the initramfs shell it shows the ahci count as 0. So it is not detecting the drive. Not sure why ?
Some more things to note from 4.2 dmesg it prints not sure if it is relevant.
[ 0.716610] ahci 0000:00:1f.2: version 3.0 [ 0.716620] ahci 0000:00:1f.2: can't find IRQ for PCI INT B;probably buggy MP table
[ 0.735267] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 4 ports 6Gbps
0x1impl SATA mode[ 0.746033] ata1: SATA max UDMA/133 abar m2048@0xb5618000 port
0xb5618100irq 44[ 1.068001] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)[ 1.134029] ata1.00: ATA-8: ST1000LM014-1EJ164-SSHD-8GB, LIV6, max UDMA/133 [ 1.134030] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA [ 1.178470] ata1.00: configured for UDMA/133 [ 1.178620] scsi 0:0:0:0: Direct-Access ATA ST1000LM014-1EJ1 LIV6 PQ: 0 ANSI: 5 [ 1.178853] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 1.178855] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 1.178879] sd 0:0:0:0: [sda] Write Protect is off [ 1.178881] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00where as 4.6 and later doesn't print these messages.dmesg | grep ata[0-4] gives no output.
lspci on 4.2 gives this
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04) (prog-if 01 [AHCI 1.0])
Subsystem: Lenovo 8 Series SATA Controller 1 [AHCI mode]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin B routed to IRQ 44
Region 0: I/O ports at 6088 [size=8]
Region 1: I/O ports at 6094 [size=4]
Region 2: I/O ports at 6080 [size=8]
Region 3: I/O ports at 6090 [size=4]
Region 4: I/O ports at 6060 [size=32]
Region 5: Memory atb5618000(32-bit, non-prefetchable) [size=2K]
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address:fee0400cData: 4181
Capabilities: [70] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mAPME(D0-,D1-,D2-,D3hot+,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
Kernel driver in use: ahci
Kernel modules: ahciHi,
The default kernel parametes doesn't detect disk whereas when you
pass kernel command line (acpi=noirq or pci=noacpi) the disk is detected and the machine is usable.
Should this be forwarded to linux-acpi list ?
Quoted 6 lines
This machine was usuable without any arguments like acpi=noirq and pci=noacpi in 4.2 .
What does this usually indicate buggy bios ?
I can see some parse execution error in dmesg attached.
Yeah, looks like an IRQ routing problem. cc'd ACPI folks.
Thanks.
Signature · 1 line
tejun