Kernel Bug Tracker – Bug 16097
3.0.4 on Samsung P460: reset after "Waiting for /dev to be fully populated"
Last modified: 2015-02-19 15:50:00 UTC
Subject : 2.6.34 on Samsung P460: reset after "Waiting for /dev to be fully populated"
Submitter : Harald Dunkel <email@example.com>
Date : 2010-05-25 9:12
Message-ID : 4BFB947E.firstname.lastname@example.org
References : http://marc.info/?l=linux-kernel&m=127477877432254&w=2
This entry is being used for tracking a regression from 2.6.33. Please don't
close it until the problem is fixed in the mainline.
How comes that this bug report has been closed? Is it fixed?
I just figured out that loading the "processor" acpi module triggers the problem (using 2.6.35).
It was closed due to the lack of response. Reopened now.
Sorry for the delay. Here is some more data:
Its a Samsung P460 model AA03DE, firmware version 07LQ.
I actually tried 3 laptops of this kind. All show the problem, so I doubt its a hardware failure.
An old P460 model AA01DE boots fine. Unfortunately I am not allowed to change the BIOS of this one.
Created attachment 27339 [details]
Are you able to also provide the acpidump output for the AA01DE?
Created attachment 27348 [details]
acpidump for P460 model AA01DE
Attached. Hope this helps.
It looks like the AA03DE introduces an extra SMM trap related to the processor code, but it's not obvious to me why this would make a difference. I know it's a significant amount of work, but would it be possible for you to bisect between the last working kernel and 2.6.34? I suspect that you can limit it to drivers/acpi.
I will check. I found an old Knoppix CD of 2004 to start with.
Wasn't there a note somewhere about some laptops changing the processor state in SMM, bypassing the operating system? Unfortunately I haven't found it anymore.
Booting old CDs there is one thing I found out: Seems that this problem is restricted to amd64. The i386 kernel included in Debian Testing works fine on the AA03DE. The amd64 version doesn't.
The AA01DE laptop works with both amd64 and i386.
(In reply to comment #8)
> I know it's
> a significant amount of work, but would it be possible for you to bisect
> between the last working kernel and 2.6.34? I suspect that you can limit it to
2.6.24 (found on Ubuntu 8.04.4) still doesn't work. The CPU is of 2009, so I doubt that this bisect thing will reveal something new.
is there any version of Linux that boots the processor module
on this machine? If not, we should clear the regression flag.
on the failing system, please try booting with "idle=poll".
By now I haven't found any kernel without this problem yet.
"idle=poll" seems to work for 126.96.36.199 (amd64). The processor module is loaded. On the next reboot the laptop gets stuck in the bios, but I wouldn't blame Linux for this. I have to turn it off and on again.
If I omit the "idle=poll", then the laptop does a reset on loading the processor module, as before.
Hope this helps.
I provided the requested information 5 months ago. Any news about this?
Update: Using 3.0.4 "idle=poll" doesn't help anymore.