[Bug 348731] Re: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/348731 Title: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/348731/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348731] Re: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
** Tags removed: ext4 -- 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped https://bugs.launchpad.net/bugs/348731 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348731] Re: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
** Tags added: ext4 -- 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped https://bugs.launchpad.net/bugs/348731 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348731] Re: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
It must be Murphy, it just happens again and NOT in DOCKING MODE!
So I can exclude Docking Station issues...
Here an excerpt of syslog:
Aug 2 13:17:15 beyond-laptop kernel: [36410.082309] ftdi_sio 4-1:1.0: FTDI USB
Serial Device converter detected
Aug 2 13:17:15 beyond-laptop kernel: [36410.082353] usb 4-1: Detected FT8U232AM
Aug 2 13:17:15 beyond-laptop kernel: [36410.082434] usb 4-1: FTDI USB Serial
Device converter now attached to ttyUSB0
Aug 2 13:17:15 beyond-laptop NetworkManager: (ttyUSB0): ignoring due
to lack of mobile broadband capabilties
Aug 2 13:20:01 beyond-laptop /USR/SBIN/CRON[10395]: (root) CMD ([ -x
/usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
Aug 2 13:25:02 beyond-laptop /USR/SBIN/CRON[10568]: (root) CMD ([ -x
/usr/lib/sysstat/sa1 ] && { [ -r "$DEFAULT" ] && . "$DEFAULT" ; [ "$ENABLED" =
"true" ] && exec /usr/lib/sysstat/sa1 $SA1_OPTIONS 1 1 ; })
Aug 2 13:30:01 beyond-laptop /USR/SBIN/CRON[10677]: (root) CMD ([ -x
/usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
Aug 2 13:30:33 beyond-laptop kernel: [37207.630925] [ cut here
]
Aug 2 13:30:33 beyond-laptop kernel: [37207.630935] kernel BUG at
/build/buildd/linux-2.6.28/mm/slub.c:2743!
Aug 2 13:30:33 beyond-laptop kernel: [37207.630940] invalid opcode: [#1]
SMP
Aug 2 13:30:33 beyond-laptop kernel: [37207.630947] last sysfs file:
/sys/devices/pci:00/:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda3/stat
Aug 2 13:30:33 beyond-laptop kernel: [37207.630954] Dumping ftrace buffer:
Aug 2 13:30:33 beyond-laptop kernel: [37207.630959](ftrace buffer empty)
Aug 2 13:30:33 beyond-laptop kernel: [37207.630962] CPU 0
I connected a processor charging station via USB - FTDI USB Serial
Device converter.
I made report according to the AMD64 Java to serial already here:
https://bugs.launchpad.net/ubuntu/+source/rxtx/+bug/361635. That is
solved on my side, since I can connect the device over Java to serial
bridge successfully.
But it still seems to be quit instable on the level below that.
It did run stable on former Ubuntu versions 8.10 AMD64 and 8.4 AMD64.
I hope that rings a bell to someone.
all the best,
cue
--
2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU
stopped
https://bugs.launchpad.net/bugs/348731
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348731] Re: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
** Attachment added: "lspci-vvnn.log" http://launchpadlibrarian.net/29792617/lspci-vvnn.log -- 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped https://bugs.launchpad.net/bugs/348731 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348731] Re: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
** Attachment added: "uname-a.log" http://launchpadlibrarian.net/29792612/uname-a.log -- 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped https://bugs.launchpad.net/bugs/348731 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348731] Re: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
** Attachment added: "version.log" http://launchpadlibrarian.net/29792634/version.log -- 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped https://bugs.launchpad.net/bugs/348731 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348731] Re: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
** Attachment added: "dmesg.log" http://launchpadlibrarian.net/29792624/dmesg.log -- 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped https://bugs.launchpad.net/bugs/348731 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348731] Re: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
I also discovered system freeze on my Thinkpad T61p since Ubuntu 9.4. I already tried to report the behaviour in https://bugs.launchpad.net/ubuntu/+bug/391085. Maybe it was not clear enough, sorry for my poor English. I could some how catch some error according to the kernel bug: Jul 21 01:23:33 beyond-laptop kernel: [ 6676.977905] [ cut here ] Jul 21 01:23:33 beyond-laptop kernel: [ 6676.977914] kernel BUG at /build/buildd/linux-2.6.28/mm/slub.c:2743! I attach the error.txt file which contains the whole log excerpt and the file requested in #5. The freezing happens when my Thinkpad is on the docking station. I hope it helps to help me/us. thanx, cue ** Attachment added: "kernelbug.txt" http://launchpadlibrarian.net/29792607/kernelbug.txt -- 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped https://bugs.launchpad.net/bugs/348731 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348731] Re: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
SOLVED (FOR ME!!) Rocko, Thanks for the comment. I solved the bug and I confirm it was related to the wireless card. I spent some time looking for help and I found that the bug was somewhat common, but difficult to identify given it does not impact wireless directly but gave random errors. I installed the linux wireless drivers (latest, May 30rd) from http://wireless.kernel.org/en/users/Download And the problem was solved!! (so far) Thanks everybody for the help. -- 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped https://bugs.launchpad.net/bugs/348731 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348731] Re: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
Kabe2007, are you using any ext4 partitions? My assumption is that this panic is something to do with ext4 rather than wireless since the backports modules did not stop these panics happening. I've still not had a crash since I started using the 2.6.30.rc series. There are, of course, multiple bugfixes for both ext4 and wireless in the 2.6.30 kernel. -- 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped https://bugs.launchpad.net/bugs/348731 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348731] Re: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
Same thing here - let me know how I may help. Not so often kernel panics, but random write errors into hard disk files (that resulted in 0 bye files and even once a lost ext3 partition) that start when I use the wireless network. In my case, it is related to the wireless card Intel 5100, and when I am using the network. I was doing fine with 8.10 and this started to happen with 9.04. I managed to "solve" the problem by disabling the wireless card (modprobe -r iwlagn) but of course that is not an optimum solution. There were several bugs that were exactly like this one (i.e. check bug 276990) but supposedly were already solved. I will start using the backport modules (as the other bug report described) and let everybody know if it helped. Any additional help appreciated. -- 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped https://bugs.launchpad.net/bugs/348731 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348731] Re: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
Just a note: I've been using 2.6.30.rc3 from the weekly builds for over a week now on both my PCs and haven't had a repeat of any kernel freezes. I tried 2.6.30.rc4 but the kernel oopses on X startup due to a bug in the bluetooth module, and this kills enough processes that X doesn't run properly. -- 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped https://bugs.launchpad.net/bugs/348731 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 348731] Re: 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped
** Summary changed: - kernel freeze in 2.6.28-11 + 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped ** Description changed: + [This bug have a netconsole log attached: + http://launchpadlibrarian.net/25957909/10.1.1.11-netconsole.log ] + The latest 2.6.28-11-generic#37 kernel (amd64) has frozen twice in the last 24 hours on my PC, ie locked up completely (with indicator lights flashing) and needing a hard reset by holding down the power button. 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: (wlan0): supplicant connection state: completed -> group handshake Mar 26 03:29:14 pegasus-jaunty NetworkManager: (wlan0): supplicant connection state: group handshake -> completed Mar 26 03:30:01 pegasus-jaunty /USR/SBIN/CRON[32557]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null) Mar 26 03:39:01 pegasus-jaunty /USR/SBIN/CRON[487]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -n 200 -r -0 rm) Mar 26 03:40:01 pegasus-jaunty /USR/SBIN/CRON[587]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null) Mar 26 03:50:01 pegasus-jaunty /USR/SBIN/CRON[1017]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null) 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). -- 2.6.28-11:ext4:hald:sys_open:security_file_alloc -> cascade of 'bugs' -> CPU stopped https://bugs.launchpad.net/bugs/348731 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
