Messages in this thread | | | Date | Fri, 25 Dec 2009 09:48:31 +0100 | Subject | Re: [2.6.33-rc2] ACPI problems on HP nc6400 notebook | From | Sedat Dilek <> |
| |
Hi,
as I suspected it is an ACPI issue while I tried to boot with "acpi=off".
I have taken new screenshots and added dmesg (acpi=off) and all messages in /var/log/* [1].
It is possible to load acpi kernel-module afterwards? Or it is not possible whenn loading with acpi=off?
@Len Brown: There are two photos showing thermal problems. Notebook did shut down in the night. But this was before 2.6.33-rc2.
I will not try a bisect (visting currently my brother and working with touchpad really sucks), but I will revert the wmi-related (wmi/hp-wmi) commits. There seems problems with wmi on other systems w/ 2.6.33-rc2 [2].
Kind Regards, - Sedat -
[1] http://files.iniza.org/linux-kernel/BUG_2.6.33-rc2/ [2] http://marc.info/?l=linux-kernel&m=126171951030608&w=2
On Fri, Dec 25, 2009 at 2:22 AM, Justin P. Mattock <justinmattock@gmail.com> wrote: > On 12/24/09 17:11, Sedat Dilek wrote: >> >> Hi, >> >> I build linux-2.6.33-rc2 on a Debian/sid 32-bit host. >> Unfortunately, this kernel falls in an unusable state (sort of loop) >> and does not a normal startup. >> >> With this setting (see below), I hoped to catch the early >> boot-messages (but, no success): >> >> # cat /etc/default/bootlogd >> # Run bootlogd at startup ? >> BOOTLOGD_ENABLE=Yes >> >> Finally, I could take a picture [1]. >> It seems to be that latest ACPI patches are breaking my system >> (speculating). >> >> Q: How can I log such early boot (error) messages to give a detailled log? >> >> Hope this helps fixing the problem. >> >> Kind Regards, >> - Sedat - >> >> >> [1] http://files.iniza.org/linux-kernel/DSCN2134.JPG >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html >> Please read the FAQ at http://www.tux.org/lkml/ >> > > you can try(if you have the port) > ohci1394_dma=early or the usb > early logging located in kernel hacking. > > but if this thing is hitting way early it > might be a bit more tricky. > > if you can try a bisect from the bad > kernel to the good. > > Justin P. Mattock > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |