hard lockup/crash -- random

[David Tansey]

I have to type this quickly. Sometimes my system runs for an hour, sometimes less. It crashed while I was preparing my last bug report.

I am using this kernel: linux-image-2.6.15-21-686

It was a clean install from the dapper beta liveCD. been updating since.

I use one "odd" module -- ath_hal/ath_pci. Though my network seems to work fine so i don't think it's my wireless card.

I have saved my logs in a tar file if you want to look at any. I looked at syslog and some others (lXorg.log, etc) and couldn't find anything that would have caused the crash. In fact, as far as I can tell, nothing at all was even logged. The last thing I get is a "MARK" in the syslog.

Let me know how I might debug this.

[William Grant (wgrant)]

What actually happens when it crashes? Just a complete lock-up? What hardware is in your machine (especially the graphics card)?

If you could try without using the ath_hal or ath_pci modules for a while and see if it crashes, it would probably be helpful.

[David Tansey (djtansey)]

I will try to use it later today without the ath modules. Just so you know the non-default software I'm using, I am using network-manager. Can't think of anything else...

When it locks up the mouse everything just becomes unresponsive. I'll be dragging my mouse over a browser tab and it will stop moving. Have had times when I'm using the terminal and what I'm typing will stop showing up.

[Sitsofe Wheeler (sitsofe)]

Can you attach using the Add Attachment link at the left of the Malone website your
/etc/X11/xorg.conf
file?

[David Tansey (djtansey)]

Here is my xorg.conf. It is the default values except I added the one 1280x1024 resolution option.

I have not had it lock up on me yet today. I left it for an hour or so with ath_* and wlan unloaded. I now have them loaded again. We'll see what happens.

[David Tansey (djtansey)]

This might be a network-manager problem. I removed the applet and killed the NetworkManger process. I haven't had a lockup since. I might have upgraded the kernel since then... Can't remember.

I will try loading it network manager again and seeing what happens to try to isolate the problem. I will keep you all updated.

[David Tansey (djtansey)]

It is indeed network-manager. I uninstalled it and haven't had a problem since. I reinstalled it this morning and had my system lockup within 10 minutes of starting nm-applet.

Should I move this to network-manager, or is that something only you guys can do?

[David Tansey (djtansey)]

I have filed a bug #43282 with network-manager

[Carthik Sharma (carthik)]

David,
Does this still occur with a more recent kernel, with Edgy Beta for example? Thanks in advance.

[David Tansey (djtansey)]

I just installed network-manager and network-manager-gnome and rebooted. GDM wouldn't start. I could get into the first terminal (Alt-F1.) I tried to stop and start gdm -- same thing. Screen went blank as if it was switching terminal, but never came up. Foolishly, I didn't check the gdm logs. dmesg didn't have anything relevant.

I dpkg --purge'd the two packages and rebooted and gdm loaded fine. I am using edgy with linux-image-2.6.17-10-386. I am happy to do whatever you ask to test my machine.

[Carthik Sharma (carthik)]

This seems to be a bug that has been affecting the user through Dapper. Any help from more knowledgeable kernel debuggers/developers would be great.

Thank you.

[Brian Murray (brian-murray)]

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

[Sergio Zanchetta (primes2h)]

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Ralph Janke (txwikinger)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.