2.6.15-23-686 hangs a couple of times per week

Bug #49450 reported by Johan Walles
6
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned
linux-source-2.6.15 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I'm running the following kernel:
Linux version 2.6.15-23-686 (buildd@rothera) (gcc version 4.0.3 (Ubuntu 4.0.3-1ubuntu5)) #1 SMP PREEMPT Tue May 23 14:03:07 UTC 2006

A couple of times per week my system freezes and stops responding to ping.

Since I'm running X, I can't see if there's any message on some console when the hang occurs.

Since X hangs right after login if I run an SMP system (that was a regression from Hoary to Breezy), I'm booting with maxcpus=1.

Hanging while running on a single CPU kernel is a regression from Breezy.

I don't know what kind of information you need to be able to look into this, but I realize the above information isn't enough. What do you need? Is there some kind of kernel crash dump thingy I can use to get you information?

Revision history for this message
Dennis Kaarsemaker (dennis) wrote :

Rejecting bogus task

Changed in linux-image-2.6.15-23-686:
status: Unconfirmed → Rejected
Revision history for this message
Constantine Evans (cevans) wrote :

Check in /var/log/kern.log - it should contain the logs from the kernel.

Changed in linux-source-2.6.15:
status: Unconfirmed → Needs Info
Revision history for this message
Johan Walles (walles) wrote : Kernel logs

The last kernel hang was yesterday (june twelfth), at about 1300.

AFAICT there's no info about the hang recorded in the log files, but I'm attaching all my /var/log/kern.log* so you can have a look at them.

Assuming there's no info in the kernel log files, what's the next step?

Changed in linux-source-2.6.15:
status: Needs Info → Unconfirmed
Revision history for this message
Johan Walles (walles) wrote :

Got another one of these hangs right now.

Any idea about how to track this down?

I've worked around my X problems by disabling DRI, so I'm now properly SMP.

Revision history for this message
Johan Walles (walles) wrote :

Yet another crash. Help!

Revision history for this message
Johan Walles (walles) wrote :

2.6.15-26-686 has the same problem.

Revision history for this message
Johan Walles (walles) wrote : Re: 2.6.15-26-686 hangs a couple of times per week

YAC :-(.

Is there some documentation describing what to do about things like this? I can't be the only person who has ever been affected by something like this...

Revision history for this message
Johan Walles (walles) wrote : Alt-SysRq doesn't work either

At today's crash I tried Alt-SysRq S(ync) U(nmount) B(oot). Didn't work.

By watching my syslog I have verified that it works while the system is up and running. So the hang is in some place that prevents Alt-SysRq from doing its thing.

Help?

Revision history for this message
Johan Walles (walles) wrote :

I've run memtest86+ over night (14h?) and it didn't find any problems, so AFAICT this is more likely to be a kernel issue than a hardware issue.

Help!

Revision history for this message
Johan Walles (walles) wrote : 2.6.15-27-686 has the same problem.

2.6.15-27-686 also hangs intermittently for me.

Revision history for this message
Matt Marulla (matt-astronomydaily) wrote :

Same problem. Machine is a PII x 2, Intel 440BX chipset, ATI Radeon 7000.

Boots fine and is stable on 386 kernel, and on 2.6.15-23-686, 2.6.15-25-686, and 2.6.15-27-686 but only with the MAXCPUS=1 directive.

If allowed to boot without that directive; i.e., if allowed to go SMP, it crashes hard (complete lock-up requiring a power cycle) within 5 minutes.

Memory tests good and machine ran fine with both processor for several years under WinXP.

No obvious clues in the log files, but I have not exhaustively searched them all yet.

Revision history for this message
tokj (tokj-deactivatedaccount) wrote :

Does this hangs still occurs also with the latest updates?

Revision history for this message
Johan Walles (walles) wrote :

Nope. Running 2.6.17-11-generic works fine now.

Can you please point me to some document describing how I should have reported this problem? If this happens again I'd like to know what to do about it except waiting for the next release.

Revision history for this message
Motin (motin) wrote :

As per system crash reports, the kernel logs should be enough, as specified per https://help.ubuntu.com/community/DebuggingSystemCrash, but as the bug never reached a "Confirmed" status it didn't get the attention from the developer's it needed.

Closing the bug since a fix is released with Edgy according to OP. Thank you for your bugreport and hope we can help you in an earlier stage next time!

Changed in linux-source-2.6.15:
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.