Bug 2333
Summary: | T30 random lockups with ACPI enabled | ||
---|---|---|---|
Product: | ACPI | Reporter: | Taavi Burns (taavi) |
Component: | Power-Processor | Assignee: | Len Brown (lenb) |
Status: | REJECTED UNREPRODUCIBLE | ||
Severity: | high | CC: | acpi-bugzilla, bunk, harry_mysooru |
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.4.x, 2.6.x | Subsystem: | |
Regression: | --- | Bisected commit-id: |
Description
Taavi Burns
2004-03-19 11:14:17 UTC
does pci=noacpi help? in addition, is Cisco Aironet 350 MiniPCI a PCMCIA card? please disable the processor driver and see if the machine becomes more stable. thanks, -Len First try ACPI without the ACPI processor driver. Thanks for the tip, Len! Is pci=noacpi different than not compiling ACPI into the kernel? If it is different, then no, I have not tried it. I will do so and see what happens. The Cisco Aironet 350 is a MiniPCI card, not PCMCIA. The T30 has a MiniPCI slot accesible via a panel on the bottom of the laptop. Support for this card was integrated in to kernel 2.6.3 (from patches by Fabrice Bellet) using the standard airo.ko driver. It was previously a source of instability, though that no longer appears to be the case (as the laptop did not crash using the card for a week, when ACPI was not compiled into the kernel). http://www.pcisig.com/specifications/conventional/mini_pci Since disabling the processor driver, the laptop has been stable for a few weeks! Let me know if you need any debug work done to try to fix the hangs when the processor driver is enabled. Thanks! if you disable Cisco Aironet 350 MiniPCI wireless card and load processor module, what is the result? I want to check if there is conflict between the card and processor driver. thanks. When things were crashing, my first thought was the Cisco MiniPCI card. I physically removed it from the system, but the lockups continued to occur. I would have had the processor module compiled and loaded at that point. any change in linux 2.6.10? There was no answer to Len's question whether this problem is still present in more recent kernels. Please reopen this bug if it's still present in 2.6.13-rc1-mm1. There was no answer to Len's question whether this problem is still present in more recent kernels. Please reopen this bug if it's still present in 2.6.13-rc1-mm1. |