Bug 43039
Summary: | Acer Aspire 5560G Laptop: link online but device misclassified: only with some kernel configs | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Matthew Stapleton (matthew4196) |
Component: | Serial ATA | Assignee: | Jeff Garzik (jgarzik) |
Status: | NEW --- | ||
Severity: | normal | CC: | alan, jlee, szg00000, tj |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.0.0 - 3.3.1 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
dmesg.txt
config-3.2.0-21-generic Server-kernel-3.0-gentoo_x86-64_smp.config HardenedServer-kernel-3.2-gentoo_x86-64_smp.config testkernel-3.0-rev3.config testkernel-3.2_basedonserver_x86_64_mainline250.config testkernel-3.2_ubuntu250.config |
Description
Matthew Stapleton
2012-04-04 01:48:41 UTC
Created attachment 72803 [details]
dmesg.txt
This a dmesg log from one of the Ubuntu kernels with the timeout problem
Created attachment 72804 [details]
config-3.2.0-21-generic
standard Desktop Ubuntu kernel config that causes timeouts
Created attachment 72805 [details]
Server-kernel-3.0-gentoo_x86-64_smp.config
My custom server kernel config for kernel series 3.0 that works without timeouts on the laptop.
Created attachment 72806 [details]
HardenedServer-kernel-3.2-gentoo_x86-64_smp.config
My custom hardened server kernel config for kernel series 3.2 that works without timeouts on the laptop. Even though this is configured for grsecurity I just loaded it on mainline 3.2.14 without any extra patches for this laptop timeout test.
Hmmm... this could have been caused by the recent engine start change. Can you please try 3.3.1? Thanks. Same timeout with 3.3.1 and Ubuntu config. Works okay with custom Hardened 3.2 config. I also have also just tried 3.0 mainline with Ubuntu 3.2.0-21=generic config and got the timeout. Created attachment 72929 [details]
testkernel-3.0-rev3.config
Tried another config which disables EFI and EDD options and still getting the timeout.
On kernel 3.0 x86_64, I think I have narrowed the problem down. Setting CONFIG_HZ from 1000 to 250 causes the timeout if I try the load kernel from a power cycle boot up. Sometimes I don't get the timeout if the kernel was loaded from a soft reboot. Is there anything immediately obvious why changing CONFIG_HZ would cause ahci ports to timeout? I just tried a few more x64_64 kernel builds with various configs. Configs are attached below. Created attachment 72949 [details]
testkernel-3.2_basedonserver_x86_64_mainline250.config
Tried this config with Mainline 3.3.2 and got the timeout. I also tested the same config with CONFIG_HZ changed to 1000 and 100 and both those HZ configs didn't timeout.
Created attachment 72950 [details]
testkernel-3.2_ubuntu250.config
Tried this config with Mainline 3.4-rc3 and got the timeout. I also tested the same config with CONFIG_HZ changed to 1000 and that didn't timeout.
I just tried kernel: 2.6.27 with CONFIG_HZ=250 and got the timeout there as well. Also, trying nohz=off on the command line doesn't help. Is there any more info I can provide to help solve the problem? Not that I can think of - other than classifying your machine is having utterly outweirded us not much obvious to progress this. |