It asks to use irqpoll option but when that is used the machine gets awfully slow(it takes ages to load up the desktop, and after it is not stable. It freezes some time later) The following Call Trace came up. [ 448.967897] irq 17: nobody cared (try booting with the "irqpoll" option) [ 448.967901] Pid: 0, comm: swapper Not tainted 2.6.37-020637rc3-generic #201011220905 [ 448.967902] Call Trace: [ 448.967908] <IRQ> [<ffffffff810d2d2b>] __report_bad_irq+0x2b/0xa0 [ 448.967922] [<ffffffff810d2ed7>] note_interrupt+0x107/0x150 [ 448.967927] [<ffffffff810d3a23>] handle_fasteoi_irq+0xc3/0x140 [ 448.967936] [<ffffffff8100e924>] handle_irq+0x24/0x40 [ 448.967940] [<ffffffff815ac93b>] do_IRQ+0x6b/0xe0 [ 448.967944] [<ffffffff815a4c53>] ret_from_intr+0x0/0x11 [ 448.967945] <EOI> [<ffffffff8131e0ce>] ? intel_idle+0xee/0x190 [ 448.967951] [<ffffffff8131e0b1>] ? intel_idle+0xd1/0x190 [ 448.967953] [<ffffffff815a4644>] ? _raw_spin_lock_irqsave+0x34/0x50 [ 448.967958] [<ffffffff81487fbd>] cpuidle_idle_call+0x8d/0x130 [ 448.967962] [<ffffffff8100a764>] cpu_idle+0xa4/0x120 [ 448.967966] [<ffffffff81588252>] rest_init+0x72/0x80 [ 448.967970] [<ffffffff81abff0a>] start_kernel+0x29a/0x380 [ 448.967973] [<ffffffff81abf140>] ? early_idt_handler+0x0/0x71 [ 448.967975] [<ffffffff81abf32a>] x86_64_start_reservations+0x6a/0xa0 [ 448.967977] [<ffffffff81abf44c>] x86_64_start_kernel+0xcc/0xf0 [ 448.967978] handlers: [ 448.967979] [<ffffffffa027dcf0>] (ath_isr+0x0/0x260 [ath9k]) [ 448.967990] Disabling IRQ #17 The computer is an ASUS K42JC notebook, it wasn't stable with 2.6.35-22 and 2.6.35-23 kernels supplied by Ubuntu(stable and testing). It is stable with 2.6.37(didn't freeze).
Hi, Does this issue only happen after the system is resumed from s3 state? Will you please do the following test and see whether the issue still can be reproduced? 1. echo freeezer > /sys/power/pm_test 2. echo mem > /sys/power/state 3. wait until the system is resumed and then see whether it will complain that "IRQ XX: nobody cared" 4. echo devices/platform/processors/core > /sys/power/pm_test one by one and go to the step 2. It will be great if you can attach the output of /proc/interrupts when the issue happens. Please also attach the output of acpidump, lspci -vxxx. Thanks. Yakui
Created attachment 39042 [details] output of acpidump
Created attachment 39052 [details] dmesg after the testing
Created attachment 39062 [details] /proc/interrupts after testing
Created attachment 39072 [details] lspci -vxxx
Hi, Thanks for the early reply. That comes up when the system is going down to sleep mode. I tested the way you asked and it resumed OK in all attempts but the dmesg is full of ACPI errors and some others. I don't know how to get the interrupts while this happens but I got a file from cat /proc/interrupts > intr just after I tested the system. All other files that you requested are attached. PS: I got these too, [ 480.743714] Booting Node 0 Processor 3 APIC 0x5 [ 480.923299] ACPI Exception: AE_BAD_PARAMETER, Returned by Handler for [EmbeddedControl] (20101013/evregion-474) [ 480.923340] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.ST87] (Node ffff88013f8647d0), AE_BAD_PARAMETER (20101013/psparse-537) [ 480.923352] ACPI Error: Method parse/execution failed [\LIMT] (Node ffff88013f86c5f0), AE_BAD_PARAMETER (20101013/psparse-537) [ 480.923362] ACPI Error: Method parse/execution failed [\_PR_.CPU0._PPC] (Node ffff88013f870ac8), AE_BAD_PARAMETER (20101013/psparse-537) [ 480.923371] ACPI Error: Method parse/execution failed [\_PR_.CPU3._PPC] (Node ffff88013f870cd0), AE_BAD_PARAMETER (20101013/psparse-537) [ 480.923384] ACPI Exception: AE_BAD_PARAMETER, Evaluating _PPC (20101013/processor_perflib-144) Thanks, Madura
(In reply to comment #6) > Hi, > > Thanks for the early reply. That comes up when the system is going down to > sleep mode. I tested the way you asked and it resumed OK in all attempts but > the dmesg is full of ACPI errors and some others. I don't know how to get the > interrupts while this happens but I got a file from cat /proc/interrupts > > intr > just after I tested the system. > > All other files that you requested are attached. > > PS: > I got these too, > [ 480.743714] Booting Node 0 Processor 3 APIC 0x5 > [ 480.923299] ACPI Exception: AE_BAD_PARAMETER, Returned by Handler for > [EmbeddedControl] (20101013/evregion-474) > [ 480.923340] ACPI Error: Method parse/execution failed > [\_SB_.PCI0.SBRG.EC0_.ST87] (Node ffff88013f8647d0), AE_BAD_PARAMETER > (20101013/psparse-537) > [ 480.923352] ACPI Error: Method parse/execution failed [\LIMT] (Node > ffff88013f86c5f0), AE_BAD_PARAMETER (20101013/psparse-537) > [ 480.923362] ACPI Error: Method parse/execution failed [\_PR_.CPU0._PPC] > (Node ffff88013f870ac8), AE_BAD_PARAMETER (20101013/psparse-537) > [ 480.923371] ACPI Error: Method parse/execution failed [\_PR_.CPU3._PPC] > (Node ffff88013f870cd0), AE_BAD_PARAMETER (20101013/psparse-537) > [ 480.923384] ACPI Exception: AE_BAD_PARAMETER, Evaluating _PPC > (20101013/processor_perflib-144) > > Thanks, > Madura I'm seeing the error while hibernating, while going down for sleep the terminal screen stays not responsive. It doesn't resume after a hibernate or a sleep. But the in the above test it resumed accordingly.
> The computer is an ASUS K42JC notebook, it wasn't stable with 2.6.35-22 and > 2.6.35-23 kernels supplied by Ubuntu(stable and testing). It is stable with > 2.6.37(didn't freeze). Exactly what do you mean by 'not stable'? is there any known linux release where this machine *was* stable?
(In reply to comment #8) > > The computer is an ASUS K42JC notebook, it wasn't stable with 2.6.35-22 and > > 2.6.35-23 kernels supplied by Ubuntu(stable and testing). It is stable with > > 2.6.37(didn't freeze). > > Exactly what do you mean by 'not stable'? > > is there any known linux release where this machine *was* stable? Hi, What I meant by 'not stable' is that the machine freezes randomly, only a hard reboot makes the it usable again. Yes! It is stable with 2.6.37-rc3(2.6.37-020637rc3-generic).
so you mean in 2.6.37-rc kernel, the irq error and the hang issue are gone. Only the ACPI error messages there, right? please attach the files in /sys/firmware/acpi/tables/dynamic/ by running command like this "cat /sys/firmware/acpi/tables/dynamic/SSDT1 > ssdt1.dat".
(In reply to comment #10) > so you mean in 2.6.37-rc kernel, the irq error and the hang issue are gone. > Only the ACPI error messages there, right? > > please attach the files in /sys/firmware/acpi/tables/dynamic/ by running > command like this "cat /sys/firmware/acpi/tables/dynamic/SSDT1 > ssdt1.dat". Exactly, btw the machine is currently at repair due to a BIOS update failure I'll reply as soon as I get it back.
It's great that kernel bugzilla is back. can you please verify if the problem still exists in the latest upstream kernel?
bug closed as there is no response from the bug reporter. please feel free to reopen it if the problem still exists in the latest upstream kernel.