[Bug 687368] New: Loop device gets stuck when using vm-install to create Xen domU
https://bugzilla.novell.com/show_bug.cgi?id=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c0 Summary: Loop device gets stuck when using vm-install to create Xen domU Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: jfunk@funktronics.ca QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=424801) --> (http://bugzilla.novell.com/attachment.cgi?id=424801) /var/log/messages User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.29 SUSE/12.0.731.0 (KHTML, like Gecko) Chrome/12.0.731.0 Safari/534.29 The loop device of a domU seems to get stuck when using vm-install to install a domU, specifically CentOS 5. I tried this on two different machines, and I am getting the same result. Reproducible: Always Steps to Reproduce: 1. Open vm-install 2. Create a new virtual machine, select RHEL5 as the type, paravirt mode, default disk image file, and this installation URL: http://centos.mirror.facebook.net/5/os/x86_64/ 3.Complete the installation Actual Results: Once the OS is installed, the domU reboots, and never comes back. The loop device appears to be stuck at this point. If I do a "losetup -a" the command goes into D state and never returns. Expected Results: The domU should have rebooted. After the losetup hang, I sent a few commands to /proc/sysrq-trigger. The results are near the bottom. The loop0, umount, and losetup call traces are particularly interesting. -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c1 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@novell.com --- Comment #1 from Jeff Mahoney <jeffm@novell.com> 2011-04-15 15:25:21 UTC --- BUG: unable to handle kernel paging request at ffff8800559ab000 IP: [<ffffffff8000f4f9>] __sanitize_i387_state+0x29/0x120 PGD 2515067 PUD 2717067 PMD 27c4067 PTE 0 Oops: 0000 [#1] SMP last sysfs file: /sys/devices/xen-backend/vbd-1-51712/statistics/wr_sect CPU 0 Modules linked in: loop nls_iso8859_1 nls_cp437 vfat fat fuse usbbk gntdev netbk blkbk blkback_pagemap blktap domctl xenbus_be evtchn snd_pcm_oss snd_mixer_oss snd_seq edd nfs lockd fscache nfs_acl auth_rpcgss sunrpc ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi af_packet bridge stp llc sr_mod aoe 8250_pnp snd_hda_codec_hdmi snd_hda_codec_realtek joydev hdj_mod usbhid snd_rawmidi hid snd_seq_device usb_storage uas snd_hda_intel snd_hda_codec snd_hwdep snd_pcm r8169 snd_timer sg 8250 snd i2c_i801 xhci_hcd iTCO_wdt floppy soundcore pcspkr iTCO_vendor_support serio_raw serial_core snd_page_alloc shpchp pci_hotplug ext4 jbd2 crc16 linear i915 drm_kms_helper drm i2c_algo_bit i2c_core video ehci_hcd output usbcore button dm_snapshot dm_mod xenblk cdrom xennet fan processor thermal thermal_sys hwmon Pid: 523, comm: 21-cifs Not tainted 2.6.37.1-1.2-xen #1 H67MA-D2H-B3/H67MA-D2H-B3 RIP: e030:[<ffffffff8000f4f9>] [<ffffffff8000f4f9>] __sanitize_i387_state+0x29/0x120 RSP: e02b:ffff880027ccdd98 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff8800559aae00 RCX: ffff880027ccdfd8 RDX: ffff88006dbd6100 RSI: 0000000000000200 RDI: ffff88006dbd6100 RBP: ffff88006dbd6100 R08: ffff880027ccdf58 R09: 0000000000000000 R10: 0000000000000000 R11: 00000000ffffffff R12: 0000000000000011 R13: ffff880027ccdf58 R14: 00007fff4ee17f40 R15: 00007fff4ee17d78 FS: 00007f25bf39f700(0000) GS:ffff8801e50f2000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: ffff8800559ab000 CR3: 000000009be3d000 CR4: 0000000000002660 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process 21-cifs (pid: 523, threadinfo ffff880027ccc000, task ffff88006dbd6100) Stack: 00007fff4ee17f40 ffff88006dbd6100 0000000000000011 ffffffff8000f8ba ffff880027ccdee8 ffff88006dbd6658 0000000000000011 ffffffff80006a22 ffff8801d9400e40 ffff88006dbd6100 ffff880027ccde68 000000116dbd6100 Call Trace: [<ffffffff8000f8ba>] save_i387_xstate+0x1aa/0x210 [<ffffffff80006a22>] __setup_rt_frame+0x2f2/0x370 [<ffffffff80006dd1>] handle_signal+0x201/0x2b0 [<ffffffff80006f09>] do_signal+0x89/0x1b0 [<ffffffff800070b5>] do_notify_resume+0x65/0x90 [<ffffffff8000770e>] int_signal+0x12/0x17 [<00007f25be85c090>] 0x7f25be85c090 Code: 00 00 41 54 55 53 48 8b 9f 10 05 00 00 48 85 db 0f 84 9c 00 00 00 48 8b 47 08 f6 40 14 01 0f 85 ef 00 00 00 48 8b 05 87 55 89 00 <48> 8b ab 00 02 00 00 48 89 c2 48 21 ea 48 39 d0 74 75 48 89 e8 RIP [<ffffffff8000f4f9>] __sanitize_i387_state+0x29/0x120 RSP <ffff880027ccdd98> CR2: ffff8800559ab000 ---[ end trace 76f7156fa9c86faa ]--- -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c2 --- Comment #2 from Jeff Mahoney <jeffm@novell.com> 2011-04-15 15:34:28 UTC --- (gdb) list *__sanitize_i387_state+0x29 0x59 is in __sanitize_i387_state (/home/jeffm/src/scratch/trees/linux-2.6.37-openSUSE-11.4/arch/x86/kernel/xsave.c:52). 47 if (!fx) 48 return; 49 50 BUG_ON(task_thread_info(tsk)->status & TS_USEDFPU); 51 52 xstate_bv = tsk->thread.fpu.state->xsave.xsave_hdr.xstate_bv; 53 54 /* 55 * None of the feature bits are in init state. So nothing else 56 * to do for us, as the memory layout is upto date. -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |rjw@novell.com |ovo.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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c3 Rafael Wysocki <rjw@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #3 from Rafael Wysocki <rjw@novell.com> 2011-04-15 22:49:27 UTC --- So it looks like tsk->thread.fpu.state is NULL, but I'm not quite sure what scenario may lead to 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c4 --- Comment #4 from Jan Beulich <jbeulich@novell.com> 2011-04-26 09:48:08 UTC --- Not NULL, but pointing to memory that is (no longer?) present. Without /var/log/boot.msg (or whatever its equivalent is on Centos) we won't be able to tell whether the page was there initially. Quite possibly a dangling pointer, particularly because the stack trace seems to indicate attempts to use xsave, support for which is off by default in the hypervisor (and the kernel shouldn't even detect its availability) mostly because it's incompatible with live migration up to and including Xen 4.1.0. -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c5 Lele Forzani <lele@windmill.it> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lele@windmill.it Severity|Normal |Major --- Comment #5 from Lele Forzani <lele@windmill.it> 2011-04-26 20:04:20 UTC --- I am seeing what looks like the same behaviour trying to install openSUSE 11.4 in PV on opensuse 11.4 xen. Repeatable: always. -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c Rafael Wysocki <rjw@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW AssignedTo|rjw@novell.com |jbeulich@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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c6 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |NEEDINFO Found By|--- |Community User InfoProvider| |jfunk@funktronics.ca --- Comment #6 from Jan Beulich <jbeulich@novell.com> 2011-04-28 07:56:36 UTC --- Please provide the information asked for in #4 plus a complete hypervisor log. -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c7 Roger Cruz <roger.cruz@virtualcomputer.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roger.cruz@virtualcomputer. | |com --- Comment #7 from Roger Cruz <roger.cruz@virtualcomputer.com> 2011-05-17 18:47:29 UTC --- (In reply to comment #4)
Not NULL, but pointing to memory that is (no longer?) present. Without /var/log/boot.msg (or whatever its equivalent is on Centos) we won't be able to tell whether the page was there initially.
Quite possibly a dangling pointer, particularly because the stack trace seems to indicate attempts to use xsave, support for which is off by default in the hypervisor (and the kernel shouldn't even detect its availability) mostly because it's incompatible with live migration up to and including Xen 4.1.0.
Hi Jan, We've been seeing the same type of exception and same stack trace when running with 2.6.38 PV-OPS kernel on top of Xen 4.0. Unfortunately, all I have is a picture of the stack trace so it won't help you with the information you asked for here. My question for you is regarding this statement "attempts to use xsave, support for which is off by default in the hypervisor"... How can I confirm that xsave support is turned off? This code only gets excuted when the xsaveopt feature is present in the CPU and when in dom0 I do a 'cat /proc/cpuinfo', I can see the xsaveopt capability is turned on so the dom0 kernel is using it. flags : fpu de tsc msr pae cx8 apic sep cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl nonstop_tsc aperfmperf pni pclmulqdq est ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes avx hypervisor lahf_lm ida arat epb xsaveopt pln pts dts -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c8 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|jfunk@funktronics.ca | --- Comment #8 from Jan Beulich <jbeulich@novell.com> 2011-05-18 07:53:21 UTC --- Ah, indeed, that's the key point: While the xsave feature flag is clear, the xsaveopt one is set, allowing the code to do things it shouldn't. As a temporary workaround it should be possible for you to simply pass "noxsave" (or "noxsaveopt") on the kernel (not Xen) command line. -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c9 --- Comment #9 from Roger R. Cruz <roger.cruz@virtualcomputer.com> 2011-05-18 15:04:46 UTC --- Hi Jan, Thanks for looking into this. I am still wondering, though, why it doesn't work even when the flag is ON and recognized by the PV OPS kernel. Looking at the kernel code, it seems that there is code to handle the XSAVEOPT capability. Why is that we get a page for the fpu.state whose PTE is 0? And why wouldn't this problem happen all the time. It is very sporadic for us as to when it happens... I was investigating this issue as a page that was incorrectly removed from dom0 to give to a booting domain (ballooning feature is enabled). Could this be a possibility? It explains why the PTE is zero and only appears to happen when we start guests which take up all the available memory. Thanks Roger -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c10 --- Comment #10 from Jan Beulich <jbeulich@novell.com> 2011-05-18 15:19:57 UTC --- (In reply to comment #9)
Thanks for looking into this. I am still wondering, though, why it doesn't work even when the flag is ON
Which "the flag"? You said you run on 4.0, and I turning on xsave support in that hypervisor is, hmm, adventurous (depending on how many post-4.0 patches you have backported).
and recognized by the PV OPS kernel. Looking at
I generally can't comment on the pv-ops kernel (and in particular, as none of our products contains one, here - this would be better discussed on e.g. xen-devel).
the kernel code, it seems that there is code to handle the XSAVEOPT capability. Why is that we get a page for the fpu.state whose PTE is 0? And why wouldn't this problem happen all the time. It is very sporadic for us as to when it happens...
As said originally - perhaps just a dangling pointer that once in a while refers to a page ballooned out of Dom0. -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c11 --- Comment #11 from Roger R. Cruz <roger.cruz@virtualcomputer.com> 2011-05-18 15:30:07 UTC ---
"While the xsave feature flag is clear, the xsaveopt one is set, allowing the code to do things it shouldn't."
I was referring to the xsaveopt flag which shows up in my /proc/cpuinfo. We are running 4.0.1 and we have back-ported a few bug fixes from mainline.
"As said originally - perhaps just a dangling pointer that once in a while refers to a page ballooned out of Dom0"
Yes, that is what it feels like based on the fact that some VMs couldn't start because there wasn't enough memory, Thanks again. Roger R. Cruz -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c12 --- Comment #12 from Jan Beulich <jbeulich@novell.com> 2011-05-18 15:47:16 UTC --- (In reply to comment #11)
I was referring to the xsaveopt flag which shows up in my /proc/cpuinfo. We are running 4.0.1 and we have back-ported a few bug fixes from mainline.
As per what you indicated earlier? There was no "xsave" feature shown, and that tells me that you didn't enable xsave in the hypervisor. Hence you can't expect Dom0 to be able to use anything xsave related. (Yes, the hypervisor shouldn't expose xsaveopt without xsave, and I submitted a patch to that respect earlier today. And yes, it seems bogus that the kernel uses the xsaveopt feature indication without qualifying with the xsave one, but that's the way it got coded, so we've got to work around this in the Xen bits.) -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c13 --- Comment #13 from Roger R. Cruz <roger.cruz@virtualcomputer.com> 2011-05-18 17:45:41 UTC --- Cool. Thanks for your help. I'll work-around it for now and pick up your Xen patch later. -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c14 --- Comment #14 from Roger R. Cruz <roger.cruz@virtualcomputer.com> 2011-05-23 14:58:57 UTC --- Hi Jan, As an FYI, I'm just letting you know that I backported your Xen patch as posted in the xen-devel mailing list and shown below as lines 817-820 and I still get the xsaveopt flag to show in my PV-OPS kernel's /proc/cpuinfo. Using the noxsaveopt in the command line does turn it off and gets around my crash. Thanks Roger 810 if ( !cpu_has_apic ) 811 __clear_bit(X86_FEATURE_EXTAPICSPACE % 32, &c); 812 __clear_bit(X86_FEATURE_OSVW % 32, &c); 813 __clear_bit(X86_FEATURE_IBS % 32, &c); 814 __clear_bit(X86_FEATURE_SKINIT % 32, &c); 815 __clear_bit(X86_FEATURE_WDT % 32, &c); 816 break; 817 case 0xd: /* XSAVE */ 818 if (cpu_has_xsave) 819 break; 820 /* fall through */ 821 case 5: /* MONITOR/MWAIT */ -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c15 --- Comment #15 from Jan Beulich <jbeulich@novell.com> 2011-05-23 15:54:42 UTC --- Is your pv-ops kernel running as a DomU or as Dom0? The code path modified is only used for Dom0 - everything else is controlled via settings in the domain's configuration (which may need to have its defaults adjusted, but the tools are outside of my realm). -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c16 --- Comment #16 from Roger R. Cruz <roger.cruz@virtualcomputer.com> 2011-05-23 18:26:06 UTC --- The kernel is used as our dom0 controller. It has no xen configuration per-se. Just the grub command line which configures the dom0_mem. R. -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c17 --- Comment #17 from Jan Beulich <jbeulich@novell.com> 2011-05-24 08:38:01 UTC --- In that case could you instrument the changed code path to check whether it gets executed. Oh, and actually on 4.0.x the change needs to look a little different anyway - see http://xenbits.xen.org/hg/xen-4.0-testing.hg/rev/c6034ee9b46e. Finally, I'm sure you realize that we don't really support you with running your own (pv-ops or else) Dom0 kernel (hence the whole discussion doesn't really belong here, but on xen-devel instead). -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c18 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #18 from Jan Beulich <jbeulich@novell.com> 2011-06-27 11:31:56 UTC --- A workaround kernel patch was just committed. -- 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=687368 https://bugzilla.novell.com/show_bug.cgi?id=687368#c19 Swamp Workflow Management <swamp@suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:11.4:42361 --- Comment #19 from Swamp Workflow Management <swamp@suse.de> 2011-08-02 08:01:02 UTC --- Update released for: kernel-debug, kernel-debug-base, kernel-debug-base-debuginfo, kernel-debug-debuginfo, kernel-debug-debugsource, kernel-debug-devel, kernel-debug-devel-debuginfo, kernel-default, kernel-default-base, kernel-default-base-debuginfo, kernel-default-debuginfo, kernel-default-debugsource, kernel-default-devel, kernel-default-devel-debuginfo, kernel-desktop, kernel-desktop-base, kernel-desktop-base-debuginfo, kernel-desktop-debuginfo, kernel-desktop-debugsource, kernel-desktop-devel, kernel-desktop-devel-debuginfo, kernel-devel, kernel-docs, kernel-ec2, kernel-ec2-base, kernel-ec2-base-debuginfo, kernel-ec2-debuginfo, kernel-ec2-debugsource, kernel-ec2-devel, kernel-ec2-devel-debuginfo, kernel-ec2-extra, kernel-ec2-extra-debuginfo, kernel-pae, kernel-pae-base, kernel-pae-base-debuginfo, kernel-pae-debuginfo, kernel-pae-debugsource, kernel-pae-devel, kernel-pae-devel-debuginfo, kernel-source, kernel-source-vanilla, kernel-syms, kernel-trace, kernel-trace-base, kernel-trace-base-debuginfo, kernel-trace-debuginfo, kernel-trace-debugsource, kernel-trace-devel, kernel-trace-devel-debuginfo, kernel-vanilla, kernel-vanilla-base, kernel-vanilla-base-debuginfo, kernel-vanilla-debuginfo, kernel-vanilla-debugsource, kernel-vanilla-devel, kernel-vanilla-devel-debuginfo, kernel-vmi, kernel-vmi-base, kernel-vmi-base-debuginfo, kernel-vmi-debuginfo, kernel-vmi-debugsource, kernel-vmi-devel, kernel-vmi-devel-debuginfo, kernel-xen, kernel-xen-base, kernel-xen-base-debuginfo, kernel-xen-debuginfo, kernel-xen-debugsource, kernel-xen-devel, kernel-xen-devel-debuginfo, preload-kmp-default, preload-kmp-desktop Products: openSUSE 11.4 (debug, i586, 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.
participants (1)
-
bugzilla_noreply＠novell.com