[Bug 448007] New: 11.1 Beta 5.2 hard-locks.
https://bugzilla.novell.com/show_bug.cgi?id=448007 Summary: 11.1 Beta 5.2 hard-locks. Product: openSUSE 11.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: robin.listas@telefonica.net QAContact: qa@suse.de Found By: --- The machine had been up for about an hour (doing nothing for half an hour while I made tea and beagle run in the backgroun). Gnome, gkrelm, 4 terms, thunderbird, firefox. I was going to report on some bugzillas that are waiting my feedback, when I was hit by bug 444780 (no firefox master password). So, instead, I started reading and then reporting on that one. Lock! Full system lock. No mouse, no clock update, keyboard caps-lock key does not activate led. Router led for this machine does not blink (ie, no network activity). No logs. No nothing. Root is reiserfs. This machine is rock solid under 11.0 For me, this blocks any further factory testing till solved. Sorry. This is also my production machine and I can't risk data loss. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c1 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |robin.listas@telefonica.net --- Comment #1 from Andreas Jaeger <aj@novell.com> 2008-11-25 08:23:48 MST --- Do you have any additional information about this? Please read the information at http://en.opensuse.org/Bugs/Kernel on how to give it. With the information given I fear we cannot help at all. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c2 --- Comment #2 from Carlos Robinson <robin.listas@telefonica.net> 2008-11-25 09:06:42 MST --- (In reply to comment #1 from Andreas Jaeger)
Do you have any additional information about this? Please read the information at http://en.opensuse.org/Bugs/Kernel on how to give it.
Notice that the machine is rock solid under 11.0, it is factory that crashes. Nothing there says how I can generate more info for a lock (Soft lockups and Hard lockups paragraphs). It is locked! There is no way to obtain info that I know of. The machine is entirely frozen.
With the information given I fear we cannot help at all.
If you tell me what exactly I can do, I'll try. For example, do you think that the kernel can be made to automatically log everything to a serial console, even if it crashes (or at least up to the crash)? It is not documented in your link above, it talks about oops. Was the problem that froze 11.0 systems with reiserfs after beagle activity entirely solved? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c3 Carlos Robinson <robin.listas@telefonica.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|robin.listas@telefonica.net | --- Comment #3 from Carlos Robinson <robin.listas@telefonica.net> 2008-12-02 04:17:15 MST --- I need info on exact procedure on how to produce info. The provided link is insufficient. I requested help on factory list, no workable result. This lock is similar or the same than Bug 434024 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |kernel-maintainers@forge.provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c4 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com Status|NEW |NEEDINFO Info Provider| |robin.listas@telefonica.net --- Comment #4 from Jeff Mahoney <jeffm@novell.com> 2008-12-08 09:16:26 MST --- Are you able to reproduce this using RC2? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c5 Carlos Robinson <robin.listas@telefonica.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|robin.listas@telefonica.net | --- Comment #5 from Carlos Robinson <robin.listas@telefonica.net> 2008-12-08 19:31:34 MST --- (In reply to comment #4 from Jeff Mahoney)
Are you able to reproduce this using RC2?
Er... how do I know if I have RC2? Afaik what I have is RC1 plus "zypper up" updates. I have "kernel-pae-2.6.27.7-4.4", which reports itself as built on Fri Nov 28 18:16:56 2008 NOT_nimrodel:~ # cat /etc/SuSE-release /etc/SuSE-brand openSUSE 11.1 (i586) VERSION = 11.1 openSUSE VERSION = 11.1 I can try with what I have, but I still do not know how to get useful info, oops or whatever from a locked machine. I have another machine here which I could connect via serial port, but I do not know how to tell the kernel to dump all klogd info there - if that is what is needed. I need help there. I did a kernel recompile (of the previous kernel) changing an option so that in case of locks the kernel logs extra info. But how can I read it? It locks! Do I configure inittab to accept a serial port connection, log in, and then run - what do I run? When I programmed on MsDos, we had a remote debugger via serial port. Does anything similar exists for the kernel that I could use? The only info I can currently produce is learning whether it locks within a reasonable time of usage. Even if it doesn't lock within three hours it is no proof. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c6 --- Comment #6 from Carlos Robinson <robin.listas@telefonica.net> 2008-12-21 07:57:49 MST --- The problem remains active in 11.1 GM. Moby on the mail list suggested ACL on reiserfs and Beagle, a bug that existed on 11.0 and reappeared on 11.1. Remember I did suggest reiserfs and Beagle right at the start of this report? Well, it is indeed Beagle. Again. :-/ So I disabled ACL and booted into 11.1 GM. While I logged only on text mode, it worked. Soon after I logged in Gnome, it crashed. I noticed that ping from auxiliary machine worked, ssh not. So I left two ssh sessions opened, with top and tailf messages. Sure, seconds after beagle run, crash! Then I removed Beagle (rpm -e -nodeps ...). I'm still running 11.1... so indeed Beagle and reiserfs is to blame, AGAIN. I hope you can solve this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 Carlos Robinson <robin.listas@telefonica.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major Summary|11.1 Beta 5.2 hard-locks. |11.1 GM hard-locks. Version|Factory |Final -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 Carlos Robinson <robin.listas@telefonica.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|11.1 GM hard-locks. |11.1 GM hard-locks (beagle and reiserfs problem) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c7 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aj@novell.com Severity|Major |Critical --- Comment #7 from Andreas Jaeger <aj@novell.com> 2008-12-21 14:23:49 MST --- Jeff, are you going to look into this? Btw. hard-lock is critical IMO. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c8 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |robin.listas@telefonica.net --- Comment #8 from Jeff Mahoney <jeffm@novell.com> 2008-12-21 17:22:36 MST --- If it's the same BUG at fs/reiserfs/journal.c:10xx bug, then yeah, I already have two bugs tracking this. Carlos, if you're looking to set up a serial console, all you need to do (for this purpose) is hook up the serial link and boot with console=tty0 console=ttyS0,<speed> Once booted, run klogconsole -r0 -l8 to ensure that all messages get dumped out. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c9 --- Comment #9 from Carlos Robinson <robin.listas@telefonica.net> 2008-12-21 18:20:01 MST --- Thanks. But do you still need that info, now that we know that is reiserfs and beagle activity? I have removed beagle from my system and it seems stable; I would have to reinstall beagle to reproduce the bug. I managed to have a ssh session running before the system locked, and got some info during it. I had "top" running, and this showed that beagle had just started to run. Unfortunately, I have lost that screenshot (auxiliary machine crashed later). I had another ssh tailing /var/log/messages, and the only info there is this (basically, nothing): +++ Dec 21 15:35:22 minas-morgul smartd[3697]: Device: /dev/hdd, SMART Usage Attribute: 194 Temperature_Celsius changed from 34 to 33 [K.[7mWaiting for data... (interrupt to abort).[27m [KDec 21 16:05:00 minas-morgul syslog-ng[2100]: Log statistics; dropped='pipe(/dev/xconsole)=0', dropped='pipe(/dev/tty10)=0', pro cessed='center(queued)=244', processed='center(received)=190', processed='destination(newsnotice)=0', processed='destination(acpid)=6', processed='destination(firewall)=19', processed='destination(null)=6', processed='destination(mail)=4', processed='desti nation(mailinfo)=4', processed='destination(console)=14', processed='destination(newserr)=0', processed ='destination(newscrit)=0 ', processed='destination(messages)=155', processed='destination(mailwarn)=0', processed='destination(localmessages)=0', processed='destination(netmgm)=0', processed='destination(mailerr)=0', processed='destination(xconsole)=14', p rocessed='destination(warn)=22', processed='source(src)=190' [K.[7mWaiting for data... (interrupt to abort).[27m [KDec 21 16:05:22 minas-morgul smartd[3697]: Device: /dev/hda, SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 74 to 73 Dec 21 16:05:22 minas-morgul smartd[3697]: Device: /dev/hda, SMART Usage Attribute: 194 Temperature_Celsius changed from 26 to 27 Dec 21 16:05:22 minas-morgul smartd[3697]: Device: /dev/hda, SMART Usage Attribute: 195 Hardware_ECC_Recovered changed from 54 to 52 [K.[7mWaiting for data... (interrupt to abort).[27m [KDec 21 16:05:23 minas-morgul smartd[3697]: Device: /dev/hdd, SMART Usage Attribute: 194 Temperature_Celsius changed from 33 to 32 [K.[7mWaiting for data... (interrupt to abort).[27m [KDec 21 16:35:22 minas-morgul smartd[3697]: Device: /dev/hda, SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 73 to 74 Dec 21 16:35:22 minas-morgul smartd[3697]: Device: /dev/hda, SMART Usage Attribute: 194 Temperature_Celsius changed from 27 to 26 [K.[7mWaiting for data... (interrupt to abort).[27m [KDec 21 16:35:22 minas-morgul smartd[3697]: Device: /dev/hdb, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 59 to 58 [K.[7mWaiting for data... (interrupt to abort).[27m ++- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c10 --- Comment #10 from Jeff Mahoney <jeffm@novell.com> 2008-12-21 18:29:13 MST --- If you wouldn't mind capturing it once. I know it seems obvious because it keeps happening to you, but I've been trying to reproduce this unsuccessfully for months. I converted my workstation back to using all reiserfs filesystems, with Beagle, etc running and I couldn't reproduce it. Some users hit it multiple times a day, others not at all. My main reason for asking for a trace is to ensure this actually *is* the bug that I'm already chasing instead of a different regression. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User moby@pcsn.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c11 Mobeen Azhar <moby@pcsn.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |moby@pcsn.net --- Comment #11 from Mobeen Azhar <moby@pcsn.net> 2008-12-21 18:47:05 MST --- This appears to be a re-manifestation of https://bugzilla.novell.com/show_bug.cgi?id=389656. I just upgraded to 11.1 from 11.0, and like a bad case of deja-vu, ran into the same hard freezes like I had with 11.0. For now, removing beagle seems to have "fixed" (6 hours and running) the issue, but not sure if it is just a matter of time before it reappears. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c12 --- Comment #12 from Carlos Robinson <robin.listas@telefonica.net> 2008-12-21 19:48:32 MST --- (In reply to comment #10 from Jeff Mahoney)
If you wouldn't mind capturing it once. I know it seems obvious because it keeps happening to you, but I've been trying to reproduce this unsuccessfully for months. I converted my workstation back to using all reiserfs filesystems, with Beagle, etc running and I couldn't reproduce it. Some users hit it multiple times a day, others not at all.
My main reason for asking for a trace is to ensure this actually *is* the bug that I'm already chasing instead of a different regression.
Ok, I will have a go tomorrow, time permitting. It is 3:43 AM here, and I'm to sleepy to fiddle with serial cables in the back of the computers, plus serial port settings in the console. O:-) Hope I find the cable... it is ages since I do this. It will be interesting :-) Question: You say: "hook up the serial link and boot with console=tty0 console=ttyS0,<speed>". Where do I type that, grub kernel line perhaps? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c13 --- Comment #13 from Carlos Robinson <robin.listas@telefonica.net> 2008-12-22 06:00:24 MST --- (In reply to comment #12 from Carlos Robinson)
Hope I find the cable... it is ages since I do this. It will be interesting :-)
I have the cable connected, both sides with minicom, and talking. So I'm ready. But I have another problem:
Question:
You say: "hook up the serial link and boot with console=tty0 console=ttyS0,<speed>".
Where do I type that, grub kernel line perhaps?
The problem is that I get no grub menu, so I can't enter any option to the kernel. Time ago I hibernated the machine, hibernation crashed on restore (bugzilla somenumber, solved), and now grub is set to auto-boot from the default kernel entry or something, without even displaying the grub menu. <http://lists.opensuse.org/opensuse/2008-12/msg01626.html> -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c14 --- Comment #14 from Jeff Mahoney <jeffm@novell.com> 2008-12-22 08:58:12 MST --- Just re-running grub-install should work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c15 Carlos Robinson <robin.listas@telefonica.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|robin.listas@telefonica.net | --- Comment #15 from Carlos Robinson <robin.listas@telefonica.net> 2008-12-22 09:14:45 MST --- Ok, I have good news and bad news. First, my grub problem: just removing '/boot/grub/default' did the trick. Now, to the problem. I managed to do the procedure, got the messages on the other machine on minicom log (by the way, that machine runs SuSE 7.3 - don't ever say that your old versions do not have their uses ;-) ). I "managed" to lock the machine (previously I had reinstalled beagle). The bad news is that there is no useful info on that log. See for yourselves... I'll attach later. At least nothing about the crash. The good news is that the kernel does not die. How do I know? Because I pinged the main machine and it responded. Because I run "nmap" on it, got port 22 open (on 11.1), and I saw the ports being scanned reported back via serial port to my 7.3 machine... so the kernel is alive. I tried to log in via ssh, but got no response. The other day I had an ssh session opened before the lock, and I had no response to the enter key. So, I can not enter commands. More ideas to test? I'll leave my 11.1 in "crashable" status and the serial cable connected. My main partition remains 11.0, so I can leave 11.1 alone. What about compiling a kernel with more debug info enabled? In that case, you'd better compile it with the appropriate options and I'll download and install it. If I have to compile a kernel, it takes nearly 4 hours to compile on my machine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c16 --- Comment #16 from Carlos Robinson <robin.listas@telefonica.net> 2008-12-22 09:25:13 MST --- Created an attachment (id=261959) --> (https://bugzilla.novell.com/attachment.cgi?id=261959) minicom capture of crash Has some [**** Comment: ..... ] lines. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User auxsvr@yahoo.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c17 John McManaman <auxsvr@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |auxsvr@yahoo.com --- Comment #17 from John McManaman <auxsvr@yahoo.com> 2009-01-03 06:03:02 MST --- Happy new year everybody! I've had 3 system hangs right after KDE and beagle start today, killing beagle allows the system to work normally with heavy disk IO. My system was working normally with beagle since 11.1 was released, yesterday I compiled and booted 2.6.28 from kernel.org (reiserfs statically linked) and I got several messages like: ReiserFS: sda2: warning: Invalid hash for xattr (user.Beagle) associated with [101 45992 0x0 SD] for many files, in the system log. These error messages never appear with the opensuse kernel, they always appear, if I remember correctly since 10.3, when I boot a vanilla kernel that I compile with reiserfs statically linked. After booting the vanilla kernel yesterday, shut down and boot the opensuse kernel today running beagle, the system hangs (SysRq-S doesn't work, SysRq-B works, all other IO looks dead). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.provo.novell.com |jeffm@novell.com Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User msa@gaugusch.at added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c18 Markus Gaugusch <msa@gaugusch.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msa@gaugusch.at --- Comment #18 from Markus Gaugusch <msa@gaugusch.at> 2009-01-17 12:27:25 MST --- Hi! This bug struck me too, and I was able to get a backtrace through serial console. Maybe it helps :) Pid: 5171, comm: beagled Tainted: P (2.6.27.7-9-pae #1) EIP: 0060:[<c01185ad>] EFLAGS: 00200297 CPU: 0 EIP is at __ticket_spin_lock+0x12/0x15 EAX: f9424fa4 EBX: f94177d3 ECX: dd19ddf8 EDX: 00000605 ESI: f9424fa8 EDI: f94253a8 EBP: dd19dcf4 ESP: dd19dc30 DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 CR0: 80050033 CR2: 00470040 CR3: 354cc000 CR4: 000006f0 DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 DR6: ffff0ff0 DR7: 00000400 [<c0353472>] _spin_lock+0x12/0x14 [<f9402a5a>] prepare_error_buf+0x1f/0x3dc [reiserfs] [<f9402ea6>] __reiserfs_warning+0x1f/0x96 [reiserfs] [<f9402fa0>] le_type+0x83/0x28d [reiserfs] [<f94031c6>] sprintf_le_key+0x1c/0x1a9 [reiserfs] [<f9402a7a>] prepare_error_buf+0x3f/0x3dc [reiserfs] [<f9402ea6>] __reiserfs_warning+0x1f/0x96 [reiserfs] [<f9412700>] reiserfs_xattr_get+0x246/0x262 [reiserfs] [<f941244b>] reiserfs_getxattr+0x57/0x6d [reiserfs] [<c01b59e6>] vfs_getxattr+0x8a/0x90 [<c01b5a7d>] getxattr+0x91/0xd9 [<c01b5b7c>] sys_lgetxattr+0x4a/0x5b [<c0104c9b>] sysenter_do_call+0x12/0x2f [<ffffe430>] 0xffffe430 ======================= -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User wied@x42.info added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c19 Markus Wied <wied@x42.info> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wied@x42.info --- Comment #19 from Markus Wied <wied@x42.info> 2009-01-18 11:39:35 MST --- Hello to all. I've got the same crash since I upgraded from version 10.3 to 11.1. I tried different parts of the beagle program suite: I even get a complete initial indexing with all extended attributes being present. But firefox with beagle-plugin enabled causes an immediate crash leaving the system in the previously described state. Sysrq u doesn't help and s neither. only b causes an instant reboot. I use the kernel 2.6.27.7-9-pae. I tried serial console and get a nearly identical output like the one in Comment #18. For me it helped to uninstall or deactivate the beagle firefox plugin. I don't have a clue what it does special or whether other beagle plugins trigger the fault as well. Normal indexing or queries alone do not seem to cause crashes till now. The system runs for about two weeks with this kernel now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c20 --- Comment #20 from Jeff Mahoney <jeffm@novell.com> 2009-01-20 08:37:06 MST --- I think it's probably the fsync load with firefox combined with the xattr access. The oops you posted is a different bug, though. It's because of the locking in prepare_error_bug. uniqueness2type ends up calling reiserfs_warning from inside reiserfs_warning, which causes a deadlock. Thanks for the report. I'll fix that one now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c21 --- Comment #21 from Carlos Robinson <robin.listas@telefonica.net> 2009-01-20 13:27:42 MST --- If the last reports are not the same problem I reported, is there something I can do to provide more info to help you solve the problem? I still have the serial cable attached, and I can reproduce the crash as soon as I log in graphical mode. Some one in the Spanish list "managed" to reproduce the problem on a virtual machine on vmware (Bug 467196). Maybe I could convince her to mail (surface mail, 6 GB) the VM to you, if that's any use :-? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User klaus@vink-slott.dk added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c22 --- Comment #22 from Klaus Slott <klaus@vink-slott.dk> 2009-01-31 13:12:34 MST --- Created an attachment (id=269092) --> (https://bugzilla.novell.com/attachment.cgi?id=269092) messages from ff reiserfs crash -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User klaus@vink-slott.dk added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c23 Klaus Slott <klaus@vink-slott.dk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |klaus@vink-slott.dk --- Comment #23 from Klaus Slott <klaus@vink-slott.dk> 2009-01-31 13:13:54 MST --- Not sure wether this is related, but after upgrade from 10.3 to 11.1 my system has degraded stability. Today Firefox broke down and cant be started again claiming another instance is still running - and indeed it is. klaus@zummer:~> ps ax | grep firefox 15876 ? D 0:00 /usr/lib64/firefox/firefox Cant be killed using kill -s 9 or kill -s 15 syslog says from the time off crash says: zummer kernel: kernel BUG at fs/reiserfs/journal.c:1034! I have attach the log from the event I have removed Beagle from the system several days ago, so that is not to blame. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c24 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |robin.listas@telefonica.net --- Comment #24 from Jeff Mahoney <jeffm@novell.com> 2009-02-01 09:53:36 MST --- Klaus, your problem is the same one as reported in bug #399966. Carlos, if it's just hard hanging like that, it's probably the same problem as reported in comment #18. I have a fix for that already in the git repository, and it will be included in the next update (soon). Please remember to do "klogconsole r0 -l8" when using the serial console. I don't think your minicom log contained all of the kernel messages. In the interim, could both of you try reproducing with kernel-debug from http://ftp.suse.com/pub/projects/kernel/kotd/HEAD/ ? This bug has been reported several times in different products and a comment in one of the other reports leads me to believe that memory corruption is the problem with the BUG at fs/reiserfs/journal.c:10xx reports. The -debug kernel enables SLAB debugging. The kotd kernel also contains the fix for comment #18. If you're using external modules, you'll run into some symbol dependency problems that will need to be resolved. That can't be helped. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c25 --- Comment #25 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-01 12:29:30 MST --- (In reply to comment #24)
Klaus, your problem is the same one as reported in bug #399966.
Carlos, if it's just hard hanging like that, it's probably the same problem as reported in comment #18.
I don't get kernel oopses. It simply freezes.
I have a fix for that already in the git repository, and it will be included in the next update (soon). Please remember to do "klogconsole r0 -l8"
I did that.
when using the serial console. I don't think your minicom log contained all of the kernel messages.
That log is all that came out. You can see the firewall messages still getting logged, an indication that the kernel is still somewhat alive, _after_ the lock-crash.
In the interim, could both of you try reproducing with kernel-debug from http://ftp.suse.com/pub/projects/kernel/kotd/HEAD/ ?
This bug has been reported several times in different products and a comment in one of the other reports leads me to believe that memory corruption is the problem with the BUG at fs/reiserfs/journal.c:10xx reports. The -debug kernel enables SLAB debugging. The kotd kernel also contains the fix for comment #18.
If you're using external modules, you'll run into some symbol dependency problems that will need to be resolved. That can't be helped.
I tried: zypper ar "http://ftp.suse.com/pub/projects/kernel/kotd/HEAD/i586/" "KOD_head" but it doesn't work: NOT_nimrodel:~ # zypper se --sort-by-repo --details kernel-debug Error building the cache: [KOD_head|http://ftp.suse.com/pub/projects/kernel/kotd/HEAD/i586/] Repository type can't be determined. Warning: Disabling repository 'KOD_head' because of the above error. Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+--------------------+---------+--------------+------+----------- | kernel-debug | package | 2.6.27.7-9.1 | i586 | Main-OSS | kernel-debug-base | package | 2.6.27.7-9.1 | i586 | Main-OSS | kernel-debug-extra | package | 2.6.27.7-9.1 | i586 | Main-OSS which means I will have to download and install manually the needed packages by rpm. What are the exact packages I need to install? This is what I have installed: NOT_nimrodel:~ # rpm -qa | grep -i kernel kernel-pae-base-2.6.27.7-9.1 linux-kernel-headers-2.6.27-2.28 kernel-pae-extra-2.6.27.7-9.1 kernel-pae-2.6.27.7-9.1 kernel-source-2.6.27.7-9.1 kerneloops-0.12-29.11 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c26 --- Comment #26 from Jeff Mahoney <jeffm@novell.com> 2009-02-01 12:49:21 MST --- The ftp site isn't an actual repository. http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/ contains a repository, but it's synced daily instead of after each commit. If it's just locking up, it could still be the same thing as comment #18. That describes a recursive spinlock. I'm not sure why it wouldn't output the oops, but the symptom is the same. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c27 --- Comment #27 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-01 13:33:57 MST --- (In reply to comment #26)
The ftp site isn't an actual repository.
http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/ contains a repository, but it's synced daily instead of after each commit.
Ok, I can install from http://ftp.suse.com/pub/projects/kernel/kotd/HEAD/, but please some one tell me the list of rpms I have to install. I simply do not know, because I don't see the exact names I have currently installed. I do not know what you want me to install.
If it's just locking up, it could still be the same thing as comment #18. That describes a recursive spinlock. I'm not sure why it wouldn't output the oops, but the symptom is the same.
My symptoms is a complete apparent freeze. Remote sessions freeze, local session freeze. Only thing that keeps working is the firewall. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c28 --- Comment #28 from Jeff Mahoney <jeffm@novell.com> 2009-02-01 14:26:57 MST --- Using the repository is fine. I added anything in the last day that's relevant. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c29 Carlos Robinson <robin.listas@telefonica.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|robin.listas@telefonica.net | --- Comment #29 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-01 15:47:02 MST --- I still need the list of rpms to install. I don't see a kernel-default-debug or kernel-pae-debug. I need you tell me what exactly to install. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c30 --- Comment #30 from Jeff Mahoney <jeffm@novell.com> 2009-02-01 20:49:02 MST --- It's kernel-debug{,-base,-extra}.rpm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c31 --- Comment #31 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-02 06:49:27 MST --- Thanks! But I get fatal problems (FATAL: Module reiserfs not found): NOT_nimrodel:~/Bugzilla/Bug_448007 # rpm -i kernel-debug.rpm kernel-debug-base.rpm kernel-debug-extra.rpm Setting up /lib/modules/2.6.27.13-HEAD_20090131033552_9af61a57-debug Scanning scripts ... Resolve dependencies ... Install symlinks in /lib/mkinitrd/setup ... Install symlinks in /lib/mkinitrd/boot ... Kernel image: /boot/vmlinuz-2.6.27.13-HEAD_20090131033552_9af61a57-debug Initrd image: /boot/initrd-2.6.27.13-HEAD_20090131033552_9af61a57-debug Root device: /dev/disk/by-id/ata-ST3160021A_5JS4VV1F-part14 (/dev/hdd14) (mounted on / as reiserfs) Resume device: /dev/disk/by-label/320_swap (/dev/hda5) FATAL: Module processor not found. WARNING: no dependencies for kernel module 'processor' found. FATAL: Module thermal not found. WARNING: no dependencies for kernel module 'thermal' found. FATAL: Module piix not found. WARNING: no dependencies for kernel module 'piix' found. FATAL: Module pata_acpi not found. WARNING: no dependencies for kernel module 'pata_acpi' found. FATAL: Module ata_generic not found. WARNING: no dependencies for kernel module 'ata_generic' found. FATAL: Module ide_pci_generic not found. WARNING: no dependencies for kernel module 'ide_pci_generic' found. FATAL: Module fan not found. WARNING: no dependencies for kernel module 'fan' found. FATAL: Module reiserfs not found. WARNING: no dependencies for kernel module 'reiserfs' found. FATAL: Module ide_disk not found. WARNING: no dependencies for kernel module 'ide-disk' found. FATAL: Module usbhid not found. WARNING: no dependencies for kernel module 'usbhid' found. Kernel Modules: dock scsi_mod libata ata_piix edd usbcore ohci-hcd uhci-hcd ehci-hcd Features: block usb resume.userspace resume.kernel Bootsplash: openSUSE (1024x768) 21680 blocks Setting up /lib/modules/2.6.27.13-HEAD_20090131033552_9af61a57-debug Scanning scripts ... Resolve dependencies ... Install symlinks in /lib/mkinitrd/setup ... Install symlinks in /lib/mkinitrd/boot ... Kernel image: /boot/vmlinuz-2.6.27.13-HEAD_20090131033552_9af61a57-debug Initrd image: /boot/initrd-2.6.27.13-HEAD_20090131033552_9af61a57-debug Root device: /dev/disk/by-id/ata-ST3160021A_5JS4VV1F-part14 (/dev/hdd14) (mounted on / as reiserfs) Resume device: /dev/disk/by-label/320_swap (/dev/hda5) Kernel Modules: hwmon thermal_sys processor thermal ide-core piix dock scsi_mod libata pata_acpi ata_piix ata_generic ide-pci-generic fan reiserfs edd ide-disk usbcore ohci-hcd uhci-hcd ehci-hcd ff-memless hid usbhid Features: block usb resume.userspace resume.kernel Bootsplash: openSUSE (1024x768) 23176 blocks Setting up /lib/modules/2.6.27.13-HEAD_20090131033552_9af61a57-debug Scanning scripts ... Resolve dependencies ... Install symlinks in /lib/mkinitrd/setup ... Install symlinks in /lib/mkinitrd/boot ... Kernel image: /boot/vmlinuz-2.6.27.13-HEAD_20090131033552_9af61a57-debug Initrd image: /boot/initrd-2.6.27.13-HEAD_20090131033552_9af61a57-debug Root device: /dev/disk/by-id/ata-ST3160021A_5JS4VV1F-part14 (/dev/hdd14) (mounted on / as reiserfs) Resume device: /dev/disk/by-label/320_swap (/dev/hda5) Kernel Modules: hwmon thermal_sys processor thermal ide-core piix dock scsi_mod libata pata_acpi ata_piix ata_generic ide-pci-generic fan reiserfs edd ide-disk usbcore ohci-hcd uhci-hcd ehci-hcd ff-memless hid usbhid Features: block usb resume.userspace resume.kernel Bootsplash: openSUSE (1024x768) 23176 blocks NOT_nimrodel:~/Bugzilla/Bug_448007 # -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c32 --- Comment #32 from Andreas Jaeger <aj@novell.com> 2009-02-02 06:55:40 MST --- The FATAL messages are only for the first iteration (installing the base package). Ignore it. Now you can reboot and run the kernel and report on problems. Thanks for testing! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c33 --- Comment #33 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-02 07:10:12 MST --- Ok, thanks. I'm currently on 11.0, running some long reiserfsck --rebuild-tree jobs (due to Bug 471382), and I have to wait for them to end. Several hours, I'm afraid. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c34 --- Comment #34 from Jeff Mahoney <jeffm@novell.com> 2009-02-02 12:44:32 MST --- Just as a note, I updated the HEAD branch to 2.6.29-rc3 today, so it should no longer be used to reproduce this bug. The SL111_BRANCH should be sufficient: http://download.opensuse.org/repositories/Kernel:/SL111_BRANCH/openSUSE_11.1... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c35 --- Comment #35 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-02 16:01:31 MST --- I have: kernel-debug-base-2.6.27.13-HEAD_20090131033552_9af61a57 Is that one adequate? I'm still busy, can't test yet. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c36 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |robin.listas@telefonica.net --- Comment #36 from Jeff Mahoney <jeffm@novell.com> 2009-02-02 16:36:06 MST --- Yes, that will work. It's just kernel versions starting with 2.6.29* that I'd like to avoid for now. Another reporter claimed that kernel-debug altered the timing enough on his system so that he couldn't reproduce anymore. I'd also be interested in seeing if you're able to reproduce it with kernel-vanilla. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c37 Carlos Robinson <robin.listas@telefonica.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|robin.listas@telefonica.net | --- Comment #37 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-03 07:05:28 MST --- Created an attachment (id=269639) --> (https://bugzilla.novell.com/attachment.cgi?id=269639) minicom capture log Well, it crashed, but I have data: BUG: spinlock recursion on CPU#0, beagled/9113 lock: f90fd090, .magic: dead4ead, .owner: beagled/9113, .owner_cpu: 0 Pid: 9113, comm: beagled Tainted: G 2.6.27.13-HEAD_20090131033552_9af61a57-debug #1 [<c0105280>] dump_trace+0x68/0x22c [<c0105c6f>] show_trace+0x1a/0x2e [<c034c428>] dump_stack+0x60/0x6a [<c0237781>] spin_bug+0x7d/0x88 [<c0237833>] _raw_spin_lock+0x35/0x11a [<c034e733>] _spin_lock+0xd/0xf [<f90d634a>] prepare_error_buf+0x21/0x39b [reiserfs] [<f90d674f>] __reiserfs_warning+0x1f/0x7e [reiserfs] [<f90d6825>] le_type+0x77/0x25b [reiserfs] [<f90d6a2c>] sprintf_le_key+0x23/0x199 [reiserfs] [<f90d636f>] prepare_error_buf+0x46/0x39b [reiserfs] [<f90d674f>] __reiserfs_warning+0x1f/0x7e [reiserfs] [<f90e6748>] reiserfs_xattr_get+0x20f/0x231 [reiserfs] [<f90e7155>] user_get+0x48/0x55 [reiserfs] [<f90e64c2>] reiserfs_getxattr+0x5e/0x76 [reiserfs] [<c01ad1a8>] vfs_getxattr+0x87/0x90 [<c01ad248>] getxattr+0x97/0xdb [<c01ad331>] sys_lgetxattr+0x3d/0x52 [<c01039cd>] sysenter_do_call+0x12/0x21 [<ffffe430>] 0xffffe430 ======================= About the timing, that's difficult to say. I'm affected by Bug 350980, and this kernel appears to be affected, too. I recorded small pauses (smaller than 2 seconds), but as the system crashed within a minute of the gnome session, it's difficult to say. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c38 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |robin.listas@telefonica.net --- Comment #38 from Jeff Mahoney <jeffm@novell.com> 2009-02-03 07:44:22 MST --- Sorry to create yet another bump for you, but can you use a kernel from http://download.opensuse.org/repositories/Kernel:/SL111_BRANCH/openSUSE_11.1... It turns out I didn't add the fix for that problem to the SLE11 tree until yesterday. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c39 --- Comment #39 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-03 08:58:05 MST --- Arghh! You'll owe me a coffee for this. Virtual, of course :-) Ok, I'm currently downloading the kernel-debug{,-base,-extra}.rpm from the i586 dir there: kernel-debug-2.6.27.13-9.1.i586.rpm kernel-debug-base-2.6.27.13-9.1.i586.rpm kernel-debug-extra-2.6.27.13-9.1.i586.rpm please verify those are the correct ones, it will be at least three hours before I can reboot - siesta takes precedence, then some errands ;-) (in case some one wonders, I install using 11.0 having 11.1 on a chroot, or I would not be able to even see the bugzilla) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c40 --- Comment #40 from Jeff Mahoney <jeffm@novell.com> 2009-02-03 09:02:18 MST --- Grr. Sorry, it turns out that build is nearly 3 weeks old. I don't know why it's not building. I'll post URLs to a good kernel in a minute. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c41 --- Comment #41 from Jeff Mahoney <jeffm@novell.com> 2009-02-03 09:12:57 MST --- http://ftp.suse.com/pub/people/jeffm/suse/testpkgs/448007/ contains the KOTD kernel for kernel-debug i586. The current SL111_BRANCH kernels are getting mistakenly named with _HEAD, but that problem is already fixed. We're just waiting for it to sync out to the ftp server. The kernel at the URL above is good to use. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c42 --- Comment #42 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-03 09:24:52 MST --- Ok, downloading: kernel-default-2.6.27.13-SL111_BRANCH_20090203134609_5784a3e1.i586.rpm kernel-default-base-2.6.27.13-SL111_BRANCH_20090203134609_5784a3e1.i586.rpm kernel-default-extra-2.6.27.13-SL111_BRANCH_20090203134609_5784a3e1.i586.rpm Are you sure these are correct? They seem small to me, the previous one exceeded 155 megs. I'm off for the moment, in any case. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c43 --- Comment #43 from Jeff Mahoney <jeffm@novell.com> 2009-02-03 09:31:48 MST --- I should think about starting to drink coffee in the morning. Of course those aren't the right ones. Thanks for paying more attention than I apparently am. :) The sizes are right, but I was looking to give you kernel-debug, not kernel-default. They only get to be ~ 150MB when you include -debuginfo, and you don't need that. That is only for use if you need to use gdb on the kernel, which we don't need to do. Try that URL again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c44 --- Comment #44 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-03 11:45:27 MST --- X-) Ok, I'm downloading: kernel-debug-2.6.27.13-SL111_BRANCH_20090203134609_5784a3e1.i586.rpm kernel-debug-2.6.27.13-SL111_BRANCH_20090203134609_5784a3e1.nosrc.rpm kernel-debug-base-2.6.27.13-SL111_BRANCH_20090203134609_5784a3e1.i586.rpm kernel-debug-extra-2.6.27.13-SL111_BRANCH_20090203134609_5784a3e1.i586.rpm I expect /these/ are the right ones, as I want to try in a while ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c45 Carlos Robinson <robin.listas@telefonica.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|robin.listas@telefonica.net | --- Comment #45 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-03 13:18:43 MST --- Ok, now I'm on my 11.1 test partition, gnome, and it hasn't crashed! :-) I started and xterm with 'top', another tailing /var/log/messages, gkrelmn, and then hands-off watching for beagle activity. It did not crash, but I saw this: Feb 3 21:01:52 minas-morgul kernel: REISERFS warning (device hdd14): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) associated with [1919251317 1634026030 0x656c67 UNKNOWN] Feb 3 21:01:57 minas-morgul kernel: REISERFS warning (device hdd14): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.Beagle) associated with [1919251317 1634026030 0x656c67 UNKNOWN] Is that interesting enough? >;-) minas-morgul:~ # mount /dev/hdd14 on / type reiserfs (rw,user_xattr) /proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/hda8 on /boot type ext2 (rw,acl,user_xattr) fusectl on /sys/fs/fuse/connections type fusectl (rw) securityfs on /sys/kernel/security type securityfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) gvfs-fuse-daemon on /home/cer/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=cer) /dev/hdd6 on /other/main type ext3 (rw,noatime,nodiratime,acl,user_xattr) /dev/hda11 on /other/main/home type xfs (rw,noatime,nodiratime) minas-morgul:~ # I'll send the minicom log when I return to 11.0 later this night. I expect to remain in this test partition (11.1) for some hours, to see what happens. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c46 --- Comment #46 from Jeff Mahoney <jeffm@novell.com> 2009-02-03 13:26:17 MST --- Ok, that confirms that you were running into the problem in comment #18, that has since been fixed. I suggest you run a reiserfsck on that partition. [1919251317 1634026030 0x656c67 UNKNOWN] ... is very wrong. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c47 --- Comment #47 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-03 14:00:51 MST --- (In reply to comment #46)
Ok, that confirms that you were running into the problem in comment #18, that has since been fixed. I suggest you run a reiserfsck on that partition.
[1919251317 1634026030 0x656c67 UNKNOWN] ... is very wrong.
You mean that I have an error in the filesystem, and that was triggering the fault? It is possible, that as I had so many crashes, there have been errors there, but surely, every time I return to 11.0 it runs an fsck on that partition (I see it flashing past). But I admit that a manual reiserfsck detects more errors than the automatic, on-boot, fsck. And... do you really want me to correct the error? I ask because once I get it corrected, I might not be able to reproduce this bug and check if it is really solved or not. I don't mind withholding the fsck some time, this is a test partition. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c48 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #48 from Jeff Mahoney <jeffm@novell.com> 2009-02-03 14:07:11 MST --- No, the testing portion for this bug is over. reiserfs_warning was re-entrant and trying to take a spinlock recursively. That's what your trace in comment #37 shows. Thanks for your patience in testing this. I'm going to close this one as FIXED. If you run into another problem, specifically one along the lines of BUG at fs/reiserfs/journal.c:10xx, please check bug #366699. If there is a corruption problem, leaving existing corruption in place isn't going to help fix it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c49 --- Comment #49 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-03 15:33:17 MST --- Ok, thanks. Just advise me when the fix reaches the standard 11.0 / 11.1 kernels. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User robin.listas@telefonica.net added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c50 --- Comment #50 from Carlos Robinson <robin.listas@telefonica.net> 2009-02-03 16:09:48 MST --- (In reply to comment #46)
Ok, that confirms that you were running into the problem in comment #18, that has since been fixed. I suggest you run a reiserfsck on that partition.
[1919251317 1634026030 0x656c67 UNKNOWN] ... is very wrong.
It appears there is no corruption in hdd14: nimrodel:~ # time nice reiserfsck /dev/hdd14 reiserfsck 3.6.19 (2003 www.namesys.com) .. Will read-only check consistency of the filesystem on /dev/hdd14 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Tue Feb 3 23:52:58 2009 ########### Replaying journal: Done. Reiserfs journal '/dev/hdd14' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. finished Comparing bitmaps..finished Checking Semantic tree: finished No corruptions found There are on the filesystem: Leaves 41984 Internal nodes 287 Directories 26308 Other files 239580 Data block pointers 2078827 (3168 of them are zero) Safe links 0 ########### reiserfsck finished at Wed Feb 4 00:00:36 2009 ########### real 7m40.966s user 0m28.842s sys 0m19.257s nimrodel:~ # -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c51 --- Comment #51 from Jeff Mahoney <jeffm@novell.com> 2009-02-03 16:41:28 MST --- Well, let me know if you run into that error again. It might be a different symptom of memory corruption. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User Ulrich.Windl@rz.uni-regensburg.de added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c52 Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Ulrich.Windl@rz.uni-regensb | |urg.de --- Comment #52 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> 2009-03-02 00:42:14 MST --- Adding a "mee to" (bug 478482) for a uniprocessor machine with ReiserFS over cryptotab... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User alvinga@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c53 alvin george <alvinga@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alvinga@gmail.com --- Comment #53 from alvin george <alvinga@gmail.com> 2009-03-02 02:06:16 MST --- had the same problem. but the freeze occurs within 2-3 minutes of logging into kde4/kde3 and starting firefox. system works fine as long as i am in text mode. when i log in to kde, and starts firefox, it freezes within 2-3 mins. upon freeze only sysrq works. no logs are available nor any oops message is printed. using sysrq, the state is similar to that in comment #37. and the stack trace is only upto the spinlock call. from the reiserfs calltree. and sysrq does not respond unless i switch to a text virtual terminal before the freeze occurs. firefox had the beagle extension enabled. and beagle was installed (by default). the sysrq task list shows two beagle processes. with one in the 'R' state with the cpu_time increasing indefinitely. now unistalled the beagle, disabled the firefox beagle extension. and it is running fine. hope this info helps. if it is a bug with the reiserfs module, where can i get the patch. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User lpechacek@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c54 Libor Pecháček <lpechacek@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gh55@heinzel.name --- Comment #54 from Libor Pecháček <lpechacek@novell.com> 2009-03-02 02:09:27 MST --- *** Bug 478482 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=478482 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User lpechacek@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c55 Libor Pecháček <lpechacek@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lpechacek@novell.com --- Comment #55 from Libor Pecháček <lpechacek@novell.com> 2009-03-02 02:13:41 MST --- Alvin, I think a better course of action is updating your kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c56 --- Comment #56 from Jeff Mahoney <jeffm@novell.com> 2009-03-02 08:55:51 MST --- If you're running into the spinlock problem, that has been fixed with the update (2.6.27.19-3.2) from several days ago. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User Ulrich.Windl@rz.uni-regensburg.de added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c57 Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #57 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> 2009-03-16 01:28:13 MST --- Bad news: The kernel froze again: After a shutdown terminated early without unmounting all the filesystems (that bus is fixed meanwhile) the machine was rebooted. Only about a minute after login, the system froze. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User Ulrich.Windl@rz.uni-regensburg.de added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c58 --- Comment #58 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> 2009-03-16 09:18:12 MST --- OK, the freeze with the current kernel seems less likely than with the last one, but there still seems to be a problem: Shortly after beagle started refreshing the index, I see this in syslog: Mar 16 08:16:05 GX150 su: (to beagleindex) root on none Mar 16 08:19:32 GX150 init: Trying to re-exec init Mar 16 08:19:54 GX150 shadow[5652]: default group changed - account=nobody, uid= 65534, gid=65533, old gid=65533, by=0 Mar 16 08:22:43 GX150 kernel: REISERFS warning (device dm-2): jdm-20002 reiserfs _xattr_get: Invalid hash for xattr (user.Beagle) associated with [1919251317 163 4026030 0x656c67 UNKNOWN] An a while later: Mar 16 08:30:18 GX150 kernel: REISERFS warning (device dm-2): journal-d1 flush_c ommit_list: [j_start=0, j_state=16, j_len=0, j_nonzerolen=0, j_commit_left=0, j_ older_commits_done=0, j_trans_id=2137424, j_timestamp=0, j_refcount=1 (a5a5a5a5b 4b4b4b4c3c3c3c3d2d2d2d2e1e1e1e196969696)]; trans_id = 2137424; journal->trans_id = 1761805; oldest live jl->j_trans_id = 1761610 Mar 16 08:30:18 GX150 kernel: Mar 16 08:30:18 GX150 kernel: ------------[ cut here ]------------ Mar 16 08:30:18 GX150 kernel: kernel BUG at fs/reiserfs/journal.c:1044! Mar 16 08:30:18 GX150 kernel: invalid opcode: 0000 [#1] SMP Mar 16 08:30:18 GX150 kernel: last sysfs file: /sys/devices/pci0000:00/0000:00:1 e.0/0000:01:0c.0/net/eth0/statistics/collisions [...] The Oops decodes like this: Mar 16 08:30:18 GX150 kernel: kernel BUG at fs/reiserfs/journal.c:1044! Mar 16 08:30:18 GX150 kernel: Pid: 9197, comm: evolution.bin Tainted: G (2.6.27.19-3.2-pae #1) Mar 16 08:30:18 GX150 kernel: EIP: 0060:[<d893a38b>] EFLAGS: 00210246 CPU: 0 Using defaults from ksymoops -t elf32-i386 -a i386 Mar 16 08:30:18 GX150 kernel: EAX: 0000015a EBX: 00209d50 ECX: c151bec4 EDX: d89 453a4 Mar 16 08:30:18 GX150 kernel: ESI: d6464be0 EDI: 00000000 EBP: 00000000 ESP: c15 1bee8 Mar 16 08:30:18 GX150 kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Mar 16 08:30:18 GX150 kernel: Stack: d44fe600 d89460f5 d8942980 d89460a9 d6464be 0 00209d50 001ae20d 001ae14a Mar 16 08:30:18 GX150 kernel: 00000001 d44fe600 00000001 d8ced000 d0d7685 c 00000000 c151bf6c d0d7685c Mar 16 08:30:18 GX150 kernel: 00000000 d8ced000 d44fe600 00000000 00209d5 0 d893cdbb d6464be0 d0d767b0 Mar 16 08:30:18 GX150 kernel: Call Trace: Mar 16 08:30:18 GX150 kernel: [<d893cdbb>] __commit_trans_jl+0x124/0x138 [reise rfs] Mar 16 08:30:18 GX150 kernel: [<d892a145>] reiserfs_sync_file+0x33/0x70 [reiser fs] Mar 16 08:30:19 GX150 kernel: [<c01aeb00>] do_fsync+0x41/0x6e Mar 16 08:30:19 GX150 kernel: [<c01aeb49>] __do_fsync+0x1c/0x2b Mar 16 08:30:19 GX150 kernel: [<c01049ad>] sysenter_do_call+0x12/0x21 Mar 16 08:30:19 GX150 kernel: [<ffffe430>] 0xffffe430 Mar 16 08:30:19 GX150 kernel: Code: 0c a9 60 94 d8 89 44 24 18 8b 44 24 24 c7 44 24 08 80 29 94 d8 c7 44 24 04 f5 60 94 d8 89 04 24 e8 e1 76 ff ff 83 7e 20 00 7 5 04 <0f> 0b eb fe 8b 54 24 2c 3b 5a 18 75 04 0f 0b eb fe ff 46 78 83
EIP; d893a38b <END_OF_CODE+182e538b/????> <=====
EBX; 00209d50 <phys_startup_32+109d50/c0000000>
Trace; d893cdbb <END_OF_CODE+182e7dbb/????> Trace; d892a145 <END_OF_CODE+182d5145/????> Trace; c01aeb00 <do_fsync+41/6e> Trace; c01aeb49 <__do_fsync+1c/2b> Trace; c01049ad <sysenter_do_call+12/21> Trace; ffffe430 <END_OF_CODE+3f9a9430/????> Code; d893a360 <END_OF_CODE+182e5360/????> 00000000 <_EIP>: Code; d893a360 <END_OF_CODE+182e5360/????> 0: 0c a9 or $0xa9,%al Code; d893a362 <END_OF_CODE+182e5362/????> 2: 60 pusha Code; d893a363 <END_OF_CODE+182e5363/????> 3: 94 xchg %eax,%esp Code; d893a364 <END_OF_CODE+182e5364/????> 4: d8 89 44 24 18 8b fmuls -0x74e7dbbc(%ecx) Code; d893a36a <END_OF_CODE+182e536a/????> a: 44 inc %esp Code; d893a36b <END_OF_CODE+182e536b/????> b: 24 24 and $0x24,%al Code; d893a36d <END_OF_CODE+182e536d/????> d: c7 44 24 08 80 29 94 movl $0xd8942980,0x8(%esp) Code; d893a374 <END_OF_CODE+182e5374/????> 14: d8 Code; d893a375 <END_OF_CODE+182e5375/????> 15: c7 44 24 04 f5 60 94 movl $0xd89460f5,0x4(%esp) Code; d893a37c <END_OF_CODE+182e537c/????> 1c: d8 Code; d893a37d <END_OF_CODE+182e537d/????> 1d: 89 04 24 mov %eax,(%esp) Code; d893a380 <END_OF_CODE+182e5380/????> 20: e8 e1 76 ff ff call ffff7706 <_EIP+0xffff7706> Code; d893a385 <END_OF_CODE+182e5385/????> 25: 83 7e 20 00 cmpl $0x0,0x20(%esi) Code; d893a389 <END_OF_CODE+182e5389/????> 29: 75 04 jne 2f <_EIP+0x2f> Code; d893a38b <END_OF_CODE+182e538b/????> <===== 2b: 0f 0b ud2a <===== Code; d893a38d <END_OF_CODE+182e538d/????> 2d: eb fe jmp 2d <_EIP+0x2d> Code; d893a38f <END_OF_CODE+182e538f/????> 2f: 8b 54 24 2c mov 0x2c(%esp),%edx Code; d893a393 <END_OF_CODE+182e5393/????> 33: 3b 5a 18 cmp 0x18(%edx),%ebx Code; d893a396 <END_OF_CODE+182e5396/????> 36: 75 04 jne 3c <_EIP+0x3c> Code; d893a398 <END_OF_CODE+182e5398/????> 38: 0f 0b ud2a Code; d893a39a <END_OF_CODE+182e539a/????> 3a: eb fe jmp 3a <_EIP+0x3a> Code; d893a39c <END_OF_CODE+182e539c/????> 3c: ff 46 78 incl 0x78(%esi) Code; d893a39f <END_OF_CODE+182e539f/????> 3f: 83 .byte 0x83 Mar 16 08:30:19 GX150 kernel: EIP: [<d893a38b>] flush_commit_list+0xa0/0x559 [re iserfs] SS:ESP 0068:c151bee8 Mar 16 08:30:19 GX150 kernel: WARNING: at kernel/exit.c:1008 do_exit+0x2e/0x2af( ) Mar 16 08:30:19 GX150 kernel: Pid: 9197, comm: evolution.bin Tainted: G D 2.6.27.19-3.2-pae #1 Mar 16 08:30:19 GX150 kernel: [<c01061cc>] dump_trace+0x6b/0x249 Mar 16 08:30:19 GX150 kernel: [<c0106ca3>] show_trace+0x20/0x39 Mar 16 08:30:19 GX150 kernel: [<c0347a23>] dump_stack+0x71/0x76 Mar 16 08:30:19 GX150 kernel: [<c0129cc0>] warn_on_slowpath+0x4d/0x70 Mar 16 08:30:19 GX150 kernel: [<c012d037>] do_exit+0x2e/0x2af Mar 16 08:30:19 GX150 kernel: [<c0349aaa>] oops_end+0x92/0x97 Mar 16 08:30:19 GX150 kernel: [<c0106af3>] do_invalid_op+0x81/0x8a Mar 16 08:30:19 GX150 kernel: [<c0349782>] error_code+0x72/0x80 Mar 16 08:30:19 GX150 kernel: [<d893a38b>] flush_commit_list+0xa0/0x559 [reiser fs] Mar 16 08:30:19 GX150 kernel: [<d893cdbb>] __commit_trans_jl+0x124/0x138 [reise rfs] Mar 16 08:30:19 GX150 kernel: [<d892a145>] reiserfs_sync_file+0x33/0x70 [reiser fs] Mar 16 08:30:19 GX150 kernel: [<c01aeb00>] do_fsync+0x41/0x6e Mar 16 08:30:19 GX150 kernel: [<c01049ad>] sysenter_do_call+0x12/0x21 Mar 16 08:30:19 GX150 kernel: [<ffffe430>] 0xffffe430 Warning (Oops_read): Code line not seen, dumping what data is available
EIP; d893a38b <END_OF_CODE+182e538b/????> <=====
3 warnings issued. Results may not be reliable. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User Ulrich.Windl@rz.uni-regensburg.de added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c59 --- Comment #59 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> 2009-03-16 09:19:54 MST --- A clarification for comment #58: When the kernel froze, there were no syslog messages at all. Those messages were found in the kernel that did not freeze yet. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=448007 User jeffm@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=448007#c60 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #60 from Jeff Mahoney <jeffm@novell.com> 2009-03-16 09:28:12 MST --- This isn't the same problem as the original report. It's #399966, which is also fixed - but not in an update yet. Please use a KOTD kernel from http://ftp.suse.com/pub/projects/kernel/kotd/SLE11_BRANCH. It contains the fix. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com