I tested two shutdown (one stay blocked one night and the other did not finish as well)
I have the following messages:
Will now halt
hub:4-0:1.0: hub_port_status_failed (err 110) repeated twice
My config did not change for almost one year...
As I use ketchup to update my source tree, to be sure I did a make mroper in the buildir and the source dir and rebuild from scratch.
The USB error message vanished but the hang is still there (2 hangs out of 3 shutdowns).
I cannot supply any more info as I have no more access to the problematic computer for more than a week.
I tried on othr compuers but I do not have the hang.
Created attachment 42192 [details]
Created attachment 42202 [details]
Created attachment 42212 [details]
Created attachment 42222 [details]
Still fails on rc_-git2
Present in 2.6.37. I upgraded the BIOS to latest available just in case it does something with ACPI but no chnage.
I have a lenovo 3000 n200 and the bug present at me also from rc2. It's still happening on 2.6.37 stable, but it only happens ~4 out of 5 times.
I don't see any messages like "hub:4-0:1.0: hub_port_status_failed (err 110)", it's totally silent.
The SysRq keys are not working at all.
I can also attach my configs if you want, but if I'll have time I'll try to bisect, and report back.
I forgot to mention that I'm on x64, so it's not 386 specific.
Confirm, NB Samsung X120 (X86_64) doesn't shutdown.
Asus N61JQ hangs at shutdown too.
Confirm, Fujitsu S6410/S6510
Created attachment 45652 [details]
call trace screen shot
seconds after power off, some debug info printed on screen, and here's the screen shot.
Confirm, Toshiba Satellite A200-1N1, x86_64.
(In reply to comment #13)
> Created an attachment (id=45652) [details]
> call trace screen shot
> seconds after power off, some debug info printed on screen, and here's the
> screen shot.
> archlinux x86_64.
same issue on HP 420 laptop (arch x86_64)
Exact same issue with almost exact same error as lyman.
Running Arch Linux 2.6.37-ARCH x86_64
Sorry, probably should add: Problem occurs on my Acer 1420p laptop.
I can confirm.
|Linux bigBang 2.6.37-ARCH #1 SMP PREEMPT Sat Jan 29 20:00:33 CET 2011 x86_64
|Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz GenuineIntel GNU/Linux
I'm on an HP6910p laptop.
Can any of you run "git bisect" of commits between 2.6.36 and 2.6.37 to find
that introduced the problem (if the problem is 100% reproducible, that should
be readily doable)?
At me it's not 100% reproducible, it's around 50% on average.
@Rafael: same for me (not 100% reproducible). It actually hasn't happened since last week, though it did 3 shutdowns in a row, I believe. It has not happened this week yet.
For me it's 100% reproducible. I've also started a bisect though it will take a while to finish. It takes about 25 minutes for a clean build. Maybe I should try with a custom config to speed things up.
For me its one out of 5 (once per week). Not really eassy to bisect.
Created attachment 48222 [details]
a3c08e5d80c54e32423efbba113b02942c91f726 is the first bad commit
First-Bad-Commit : a3c08e5d80c54e32423efbba113b02942c91f726
Can you please check if the problem is fixed by
Author: Thomas Gleixner <email@example.com>
Date: Sat Feb 12 11:51:03 2011 +0100
x86: Readd missing irq_to_desc() in fixup_irq()
(from the Linus' tree)?
Yes, it was fixed (for me at least) since v2.6.38-rc5. The fix must have been pulled into the tree a few hours after I started bisecting :(
Yes, it was fixed (for me at least) since v2.6.38-rc5. The fix must have been pushed into the tree a few hours after I started bisecting :(