[Bug 671551] New: Regular kernel traps
https://bugzilla.novell.com/show_bug.cgi?id=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c0 Summary: Regular kernel traps Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: jimoe@sohnen-moe.com QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=413711) --> (http://bugzilla.novell.com/attachment.cgi?id=413711) A set of kernel traps from </var/logm User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 Over the last month or so I have been seeing a kernel traps that leave the system unstable; a reboot is necessary. This is since I have upgraded to kernel 2.6.34.7-0.7-desktop x86_64. There is a complication that the Oracle VirtualBox may be the cause but I cannot say for certain. I am attaching a set of trap data from the </var/log/messages> file over the last 4 weeks. It does not include every one; there were a number of similar entries that I left out. Reproducible: Always Steps to Reproduce: I cannot predict when this will occur. Only that it has happened about 1 - 2 per week over the last 4 weeks. Actual Results: I do not know how to reproduce the 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c1 Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |jslaby@novell.com InfoProvider| |jimoe@sohnen-moe.com --- Comment #1 from Jiri Slaby <jslaby@novell.com> 2011-02-14 10:12:54 UTC --- (In reply to comment #0)
Over the last month or so I have been seeing a kernel traps that leave the system unstable; a reboot is necessary. This is since I have upgraded to kernel 2.6.34.7-0.7-desktop x86_64.
Many of them are due to broken fglrx. Could you retry without that module? -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c2 --- Comment #2 from James Moe <jimoe@sohnen-moe.com> 2011-03-07 19:10:21 UTC --- Created an attachment (id=417904) --> (http://bugzilla.novell.com/attachment.cgi?id=417904) system log containing a variety of failures. Starting on Mar 6 22:31 there is a long series of kernel traps. It culminates on Mar 7 01:58 with a system freeze due to a paging failure. The paging failure occurred when gzip started to compress a tar file. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c3 --- Comment #3 from James Moe <jimoe@sohnen-moe.com> 2011-03-07 19:16:16 UTC ---
Many of them are due to broken fglrx.
Those failures only occur at startup. I forgot to mention in the previous comment (#2) that the uploaded "messages" file is where to look for the kernel traps. Note: Due to Thunderbird's habit of aperiodically resetting my preferences, I missed the timely arrival of this request. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #417904|application/octet-stream |text/plain mime type| | -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c4 --- Comment #4 from Jiri Slaby <jslaby@novell.com> 2011-03-10 16:19:56 UTC --- (In reply to comment #3)
Many of them are due to broken fglrx.
Those failures only occur at startup.
I forgot to mention in the previous comment (#2) that the uploaded "messages" file is where to look for the kernel traps.
The logs are still tainted by fglrx. Can you reproduce it without that module? The module is not needed for X to run. just for 3D. If yes, it seems like somebody holds a i_block_reservation_lock. Could you grab dmesg after: echo t >/proc/sysrq-trigger. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c5 --- Comment #5 from James Moe <jimoe@sohnen-moe.com> 2011-03-10 18:12:21 UTC --- I'll see about removing fglrx. I am attaching the dmesg output. Whatever "echo t >/proc/sysrq-trigger" did, it produced so much output that the dmesg buffer overflowed. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c6 --- Comment #6 from James Moe <jimoe@sohnen-moe.com> 2011-03-10 18:13:40 UTC --- Created an attachment (id=418668) --> (http://bugzilla.novell.com/attachment.cgi?id=418668) post-"echo t >/proc/sysrq-trigger" dmesg output -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c Jiri Slaby <jslaby@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jimoe@sohnen-moe.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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c7 --- Comment #7 from James Moe <jimoe@sohnen-moe.com> 2011-03-19 18:03:27 UTC --- Created an attachment (id=420345) --> (http://bugzilla.novell.com/attachment.cgi?id=420345) dmesg output from recent kernel trap, untainted The traps have not been happening as often as when I first created the report. The dmesg attachment records one that occurred this morning (2011-03-19 09:08:36). Despite the dearth of traps, the system stability is still very poor; I rarely get 4 days of uptime (I'm currently at 4 days 11 min) before applications (mainly firefox, thunderbird and VirtualBox) stop functioning. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c8 --- Comment #8 from James Moe <jimoe@sohnen-moe.com> 2011-03-19 18:05:35 UTC --- I forgot to mention: I removed fglrx about 7 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c9 --- Comment #9 from James Moe <jimoe@sohnen-moe.com> 2011-03-19 19:23:39 UTC --- It finally reached un-usability. Applications spontaneously crashed or refused to open, nothing written to the system log. After the reboot, all is functioning again. And it crashed during shutdown. Is there a way to save or recover that crash data? -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c10 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com AssignedTo|kernel-maintainers@forge.pr |jack@novell.com |ovo.novell.com | --- Comment #10 from Jeff Mahoney <jeffm@novell.com> 2011-04-20 02:54:47 UTC --- Since virtualbox is involved and it seems like it's random memory corruption, I'm inclined to blame virtualbox. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c11 Jan Kara <jack@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |jimoe@sohnen-moe.com --- Comment #11 from Jan Kara <jack@novell.com> 2011-04-20 16:57:43 UTC --- Yeah. The traces are all over the mm/fs code and seem to be caused by memory corruption. For example: BUG: unable to handle kernel paging request at 000000000000ff18 IP: [<ffffffff81244674>] __lookup+0x94/0xc0 PGD 50bed067 PUD 55fad067 PMD 0 Oops: 0000 [#1] PREEMPT SMP last sysfs file: /sys/devices/virtual/net/vboxnet0/statistics/collisions CPU 3 Modules linked in: vboxnetadp vboxnetflt vboxdrv fuse ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device edd nls_utf8 cifs ip6t_REJECT nf_conntrack_ipv6 fglrx(P) ip6table_raw xt_NOTRACK ipt_REJECT xt_state iptable_raw iptable_filter cpufreq_conservative cpufreq_userspace cpufreq_powersave powernow_k8 mperf ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables ip6table_filter ip6_tables x_tables loop dm_mod firewire_ohci firewire_core crc_itu_t ppdev parport_pc ohci1394 sr_mod cdc_acm parport snd_hda_codec_atihdmi usb_storage cdrom sg k10temp pcspkr ieee1394 i2c_piix4 r8169 button floppy snd_hda_codec_realtek edac_core edac_mce_amd asus_atk0110 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_timer snd soundcore snd_page_alloc wmi ext4 jbd2 crc16 sd_mod fan processor ata_generic sym53c8xx scsi_transport_spi ahci pata_atiixp libata scsi_mod thermal thermal_sys [last unloaded: vboxd rv] Pid: 29453, comm: VBoxSVC Tainted: P 2.6.34.7-0.7-desktop #1 M3A78-EM/System Product Name RIP: 0010:[<ffffffff81244674>] [<ffffffff81244674>] __lookup+0x94/0xc0 RSP: 0018:ffff88005a67fcb8 EFLAGS: 00010202 RAX: 0000000000000000 RBX: 0000000000000040 RCX: 0000000000000000 RDX: 0000000000324101 RSI: ffff88005a67fde0 RDI: 000000000000ff00 RBP: ffffffffffffffc0 R08: ffff88005a67fcd8 R09: 000000000000000b R10: 0000000000000001 R11: 0000000000000001 R12: ffff88005a67fdc8 R13: ffff88009edf08f0 R14: 0000000000ffffff R15: ffff88005a67fcd8 FS: 00007f5ae5864710(0000) GS:ffff880001f80000(0000) knlGS:00000000f39feb70 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 000000000000ff18 CR3: 000000003a622000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff4ff0 DR7: 0000000000000400 Process VBoxSVC (pid: 29453, threadinfo ffff88005a67e000, task ffff88005a7e0700) Stack: 0000000000000003 000000000000000e ffffffff812447d7 ffffea0002b8bb80 <0> 0000000000324000 ffff88005a67fdc8 ffff88012394c9f8 000000000000000e <0> 00000000003206e7 0000000000000000 0000000000000000 ffffffff810da86c Call Trace: [<ffffffff812447d7>] radix_tree_gang_lookup_slot+0x67/0xa0 .. We have spotted 0xff00 where should have been either NULL or a pointer. Other traces are similar (some trigger kernel assertions instead of making kernel dereference invalid address). Catching memory corruption is always tricky. I guess running without Virtual Box is out of question since that is what puts the load to the machine, isn't it? You could debug this a bit further by enabling some kernel debugging options (I can tell you which if you are interested) so that we see whether we'll be able to catch the code which is corrupting memory. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c12 --- Comment #12 from James Moe <jimoe@sohnen-moe.com> 2011-04-21 18:35:20 UTC --- Yes, I am interested in solving this problem. I have also submitted a similar report with multiple instances of the crashes on the VirtualBox Defect Report site. There has been zero (0) response. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c13 --- Comment #13 from Jan Kara <jack@novell.com> 2011-04-21 22:38:58 UTC --- OK, where do you get Virtual Box kernel modules from? You need to compile kernel with CONFIG_DEBUG_SLAB and CONFIG_DEBUG_PAGEALLOC options and you'll also need to recompile Virtual Box modules against this kernel... I can build the kernel for you, that's not a problem but I'm not sure about Virtual Box drivers. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c14 --- Comment #14 from James Moe <jimoe@sohnen-moe.com> 2011-04-23 05:10:09 UTC --- Ah. You have gone way past my skill set. I download the pre-built packages for openSuse. That is one for each minor version of openSuse: 11.1, 11.2, 11.3, 11.4. Hmm. Part of the installation process (re-)builds the VirtualBox kernel modules. Would that be all that is necessary to work with a debug linux 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c15 --- Comment #15 from James Moe <jimoe@sohnen-moe.com> 2011-05-10 17:26:20 UTC --- I've grown pretty tired of this problem. If you can supply a debug kernel (my current kernel is 2.6.34.8-0.2-desktop x86_64), I can re-install the VBox distribution which rebuilds the kernel drivers. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c16 --- Comment #16 from James Moe <jimoe@sohnen-moe.com> 2011-05-10 17:28:13 UTC --- Oh! And instructions on how to install and use the debug 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c17 --- Comment #17 from Jan Kara <jack@novell.com> 2011-05-10 20:00:03 UTC --- Sorry, I forgot about this. So http://beta.suse.com/private/jack/671551/ contains (or soon will) a debug kernel package. You just install rpms (kernel-debug-2.6.34.9-201105102339.x86_64.rpm and kernel-debug-base-2.6.34.9-201105102339.x86_64.rpm should be enough) and boot the kernel. Then you'll need to re-install the VBox so that modules get rebuilt (the old ones won't be able to load into this kernel). And then you can try running your standard load and see whether the kernel spits some unusual messages. Note that the machine is probably going to be slower with this kernel because it does a lot of additional checks etc. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c18 --- Comment #18 from James Moe <jimoe@sohnen-moe.com> 2011-05-11 17:10:26 UTC --- It did not go well. The Vbox kernel build requires the development package which did not want to install:
rpm -i kernel-debug-devel-2.6.34.9-201105102339.x86_64.rpm error: Failed dependencies: kernel-devel = 2.6.34.9-201105102339 is needed by kernel-debug-devel-2.6.34.9-201105102339.x86_64
which I find confusing since:
uname -rm 2.6.34.9-201105102339-debug x86_64
-- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c19 --- Comment #19 from Jeff Mahoney <jeffm@novell.com> 2011-05-11 18:07:49 UTC --- You need kernel-devel as well. kernel-$flavor-devel contains the per-flavor files. kernel-devel contains the files shared across all flavors. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c20 --- Comment #20 from James Moe <jimoe@sohnen-moe.com> 2011-05-11 20:38:41 UTC --- Where do I find kernel-debug-2.6.34.9-201105102339? (I found lots of distributions for fc13.) (I thought I had sent this question earlier. I guess not.) -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c21 --- Comment #21 from Jiri Slaby <jslaby@novell.com> 2011-05-11 20:48:59 UTC --- (In reply to comment #20)
Where do I find kernel-debug-2.6.34.9-201105102339? (I found lots of distributions for fc13.)
Do you need the devel package at all? I don't think so, so just ignore it and install only kernel-debug-2* (you don't even need the -base package). -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c22 --- Comment #22 from James Moe <jimoe@sohnen-moe.com> 2011-05-11 21:00:06 UTC ---
Do you need the devel package at all? I don't think so...
Yes, since the VBox kernel build requires it. The kernel-debug-2* and kernel-kernel-debug-base-2* are insufficient, and kernel-debug-devel-2* requires kernel-devel-2*. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c23 --- Comment #23 from Jan Kara <jack@novell.com> 2011-05-12 12:36:05 UTC --- Ah, I didn't know you need also kernel-devel. I've added these packages to the directory. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c24 --- Comment #24 from James Moe <jimoe@sohnen-moe.com> 2011-05-13 05:40:43 UTC --- I rebuilt the VBox drivers. Unfortunately the system freezes after only a few minutes of operation. Nothing was recorded in any log that I could find. Not usable. When it did freeze, apparently the CPU usage max'ed out: I could here the CPU fan going faster and faster as the CPU heated up. You did mention that the system may be slower; I did not really notice any performance loss; I have quad athlon. What was happening is that one core was running at nearly 100% while the others were "idling" at 30%; I did not expect that. The usual values, even with two VMs running, is typically less that 8% for each core. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c25 --- Comment #25 from Jan Kara <jack@novell.com> 2011-05-17 12:11:25 UTC --- Hmm, wasn't there anything even in the VGA console? I'd expect the kernel had oopsed making the system unusable but leaving something in the VGA console (console 10 under SUSE)... If you cannot switch to VGA console after the system freezes, perhaps you can switch to it after starting the load before the machine freezes? If you'll see something there, just take a picture of it with digital camera and attach it here. Also what does mean frozen? Does the machine react to pressing caps-lock or ping? -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c26 --- Comment #26 from James Moe <jimoe@sohnen-moe.com> 2011-05-17 20:10:21 UTC ---
Hmm, wasn't there anything even in the VGA console?
I do not know what you mean here.
Also what does mean frozen?
AFAICT, non-functional. No response to the keyboard, capslock or numlock had no effect; no mouse pointer movement; no video updates, the screen was completely static. I did not try to ping it from another computer. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c27 --- Comment #27 from Jan Kara <jack@novell.com> 2011-05-18 12:52:16 UTC --- (In reply to comment #26)
Hmm, wasn't there anything even in the VGA console?
I do not know what you mean here. I suppose you are running system with X right? So if you press ctrl-alt-f10, you will be put to a text console with syslog. If kernel spits out something just before it dies, it's likely to be visible in this console. So it would be good if you can start your reproduction load and then switch to this console to see what kernel writes before it dies.
Also what does mean frozen?
AFAICT, non-functional. No response to the keyboard, capslock or numlock had no effect; no mouse pointer movement; no video updates, the screen was completely static. I did not try to ping it from another computer. OK, so the kernel probably died with interrupts disabled. Good to know.
-- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c28 --- Comment #28 from Jan Kara <jack@suse.com> 2011-08-30 23:00:50 UTC --- Any news here? -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c29 --- Comment #29 from James Moe <jimoe@sohnen-moe.com> 2011-08-31 03:03:24 UTC --- Nothing has changed, really. Occasionally there are kernel traps; more often it is that Firefox or Thunderbird start to crash randomly and sometimes simply cannot restart. A reboot solves that and all is good for 1 - 4 days. I suppose we could go through the debug kernel exercise again. Maybe it will be more stable now. Currently the system is: - opensuse v11.4 - Linux 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c30 --- Comment #30 from Jan Kara <jack@suse.com> 2011-09-01 14:52:25 UTC --- Yeah, the trouble is that most likely the problem is in VBox (the whole excercise is just about catching it in action to have a proof) and I cannot do much about it. So if you want to put more pressure on VBox guys and help them debug the problem, you could try getting some corruption report from -debug kernel flavor and reporting it to them. -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c31 --- Comment #31 from Jan Kara <jack@suse.com> 2011-12-08 12:06:53 UTC --- I guess I'll close this bug since the problem is most likely in VBox. Or James, do you want to run with debug kernel? I can build it for you, you'll have to rebuild VBox modules... -- 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=671551 https://bugzilla.novell.com/show_bug.cgi?id=671551#c32 Jan Kara <jack@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|jimoe@sohnen-moe.com | Resolution| |INVALID --- Comment #32 from Jan Kara <jack@suse.com> 2011-12-20 12:11:12 UTC --- Most likely a memory corruption caused by VBox... -- 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