2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[This bug have a netconsole log attached: http://
The latest 2.6.28-
The first time I was using it (I was moving the mouse), but the second time it was just idling when it locked some time between 3:50 and 7:44 am, as shown in the syslog:
Mar 26 03:29:14 pegasus-jaunty NetworkManager: <info> (wlan0): supplicant connection state: completed -> group handshake
Mar 26 03:29:14 pegasus-jaunty NetworkManager: <info> (wlan0): supplicant connection state: group handshake -> completed
Mar 26 03:30:01 pegasus-jaunty /USR/SBIN/
Mar 26 03:39:01 pegasus-jaunty /USR/SBIN/
Mar 26 03:40:01 pegasus-jaunty /USR/SBIN/
Mar 26 03:50:01 pegasus-jaunty /USR/SBIN/
Mar 26 07:44:10 pegasus-jaunty syslogd 1.5.0#5ubuntu3: restart.
This is on the latest Jaunty. It's a Dell XPS M1530 that was running nvidia 185.13 the first time it locked up, and 180.41 the second time. There's no information in any of the logs - syslog shows the last message at 3:50.
Prior to this, I haven't had any lockups for quite some time (it was the iwlagn driver causing it in Intrepid but that bug was fixed some time ago).
description: | updated |
summary: |
- kernel freeze in 2.6.28-11 + 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> + CPU stopped |
tags: | added: ext4 |
tags: | removed: ext4 |
Could you do:
apport-collect 348731
please? I think sudo is not mandatory... but I am not sure. 348731 being the number of this bug.
This is a trick on Jaunty to add the infos that would have been added if you would have done:
ubuntu-bug -p linux
to report the bug.