[Bug 576681] New: Installation hangs at Loading basic drivers
http://bugzilla.novell.com/show_bug.cgi?id=576681 http://bugzilla.novell.com/show_bug.cgi?id=576681#c0 Summary: Installation hangs at Loading basic drivers Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 1 Platform: i586 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ingesvensson@orion.vokby.se QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) At installation under VirtualBox the processor goes up to 100% CPU and installation halts at Loading basic drivers. Reproducible: Always Steps to Reproduce: 1.Boot from DVD 2.Choose installation 3.Press Esc after Kernel is loaded. Actual Results: Installation halts Expected Results: Installation should have continued -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c
yang xiaoyu
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c
Lukas Ocilka
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c1
Steffen Winterfeldt
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c2
Steffen Winterfeldt
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c3
Steffen Winterfeldt
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c4
--- Comment #4 from Inge Svensson
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c5
--- Comment #5 from Paul Hands
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c6
--- Comment #6 from Steffen Winterfeldt
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c7
--- Comment #7 from Paul Hands
Can you check on consoles 3 and 4 what the last thing is it does?
How do I do that in VBox? If I try the crtl-alt-Fx key combination, it's not trapped by VBox, and is passed to the host, which switched consoles quite happily :-) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c8
--- Comment #8 from Steffen Winterfeldt
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c9
Jeff Mahoney
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c10
--- Comment #10 from Paul Hands
You're looking for 'host-key'+Fn (Right Ctrl, I think). Thanks, I learned something new!
I got a lot more from the alternate consoles..... Startup... Loading basic drivers...[ 13.477542] ide-cd driver 5.00 [ 13.550907] ide-gd driver 1.18 [ 13.685910] st: Version 20081215, fixed bufsize 32768, s/g segs 256 [ 14.300451] NET: Registered protocol family 17 [ 16.582221] NET: Registered protocol family 10 [ 77.313486] BUG: soft lockup - CPU#0 stuck for n61s! [insmod:377] [ 77.313797] Modules linked in: ipv6(+) af_packet st ide_gd_mod ide_cd_mod sr_mod cdrom sg ide_pci_generic piix ide_core ata_generic ata_piix ahci parport_pc floppy parport battery ac rtc_cmos rtc_core rtc_lib thermal button processor thermal_sys pcnet32 hwmon libata edd squashfs loop [ 77.313797] [ 77.313797] Pid: 377, comm insmod Not tainted (2.6.32-3-default #1) VirtualBox [ 77.313797] EIP: 0060:[<c08e9ef5>] EFLAGS: 00010286 CPU: 0 [ 77.313797] EIP is at pcpu_populate_chunk+0x95/0x410 [ 77.313797] EAX: 00000000 EBX: 00000800 ECX: 00000200 EDX: 00000000 [ 77.313797] ESI: 00000000 EDI: fec00000 EBP: c0e360a0 ESP: c2731e88 [ 77.313797] DS: 007b ES: 007b GS: 0033 SS: 0060 [ 77.313797] CR0: 8005003b CR2: fec00000 CR3: 0271b000 CR4: 000006d0 [ 77.313797] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000 [ 77.313797] DR6: 00000000 DR7: 00000000 [ 77.313797] Call Trace: [ 77.313797] [<c08ea88b>] pcpu_alloc+0x30b/0x3f0 [ 77.313797] [<c0b56f76>] snmp_mib_init+0x16/0x60 [ 77.313797] [<f828f9b3>] smnp6_alloc_dev+0x53/0x80 [ipv6] [ 77.313797] [<f829064e>] ipv6_add_dev+0xce/0x2b0 [ipv6] [ 77.313797] [<f7c2b2c6>] addrconf_init+0x3e/0x12e [ipv6] [ 77.313797] [<f7c2b178>] inet6_init+0x178/0x27e [ipv6] [ 77.313797] [<c080112f>] do_one_initcall+0x2f/0x190 [ 77.313797] [<c0873fd4>] sys_init_module+0xb4/0x230 [ 77.313797] [<c0803075>] syscall_call+0x7/0xb [ 77.313797] [<b780070e>] 0xb780070e This then repeats ad infinitum.... Please don't put too much faith in the accuracy of the above - I transcribed it by hand! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c11
--- Comment #11 from Steffen Winterfeldt
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c12
--- Comment #12 from Paul Hands
You could have just made a screenshot. :-)
Oops, now I feel like an idiot :-). I made a screenshot to transcribe. It's now attached. Paul -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c13
--- Comment #13 from Paul Hands
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c14
Jeff Mahoney
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c15
--- Comment #15 from Paul Hands
That was the only iteration of the 2.6.32 kernel for openSUSE 11.3. Can you reproduce with a kernel from http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/ ?
Hi Jeff, I'm not sure how to apply one of those kernel rpms to the iso image I have, but I'd love to learn. Any pointers? Paul -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c16
--- Comment #16 from Paul Hands
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c
Paul Hands
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c17
--- Comment #17 from Inge Svensson
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c18
Rastislav Krupansky
Workaround: Boot with less than 700 MB RAM see https://bugzilla.novell.com/show_bug.cgi?id=574463
No, workaround doesn´t still work. Milestone 3 has the same issue :-( I can confirm it on livecd´s. Btw, a similar issue is in VMware also (at least in my case) To Jeff: kernel is 2.6.33-5 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c19
--- Comment #19 from Jeff Mahoney
I'm not sure how to apply one of those kernel rpms to the iso image I have, but I'd love to learn. Any pointers?
Yes, but it needs an already running system. There's an 'install-initrd' package that allows you to regenerate the initrd to match the kernel package you want to use. Then you can replace the kernel and initrd on the install media with it and re-burn it. It will probably be easier to not bother with the live cd for this stage of testing. You're not getting far enough into the boot cycle for it to matter. Instead, download the internet install iso. It's a lot smaller and it's easier to drop in the replacement kernel and initrd and remake the iso than it is to rebuild the entire live cd with a new kernel. Also I only know how to do the first part. :) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c20
Jeff Mahoney
(In reply to comment #17)
Workaround: Boot with less than 700 MB RAM see https://bugzilla.novell.com/show_bug.cgi?id=574463
No, workaround doesn´t still work. Milestone 3 has the same issue :-( I can confirm it on livecd´s. Btw, a similar issue is in VMware also (at least in my case)
If you're able to reproduce with VB and VMware, can you also reproduce with kvm? I ask because it's possible to start KVM with -kernel and -initrd parameters that will make testing loads faster. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c21
--- Comment #21 from Rastislav Krupansky
(In reply to comment #18)
(In reply to comment #17)
Workaround: Boot with less than 700 MB RAM see https://bugzilla.novell.com/show_bug.cgi?id=574463
No, workaround doesn´t still work. Milestone 3 has the same issue :-( I can confirm it on livecd´s. Btw, a similar issue is in VMware also (at least in my case)
If you're able to reproduce with VB and VMware, can you also reproduce with kvm? I ask because it's possible to start KVM with -kernel and -initrd parameters that will make testing loads faster.
Sorry, i´d try it, but i use VB and VMware on Microsoft Windows and i have no experience with KVM. Someone else for testing in KVM? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c22
Vojtech Zeisek
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c23
--- Comment #23 from Vojtech Zeisek
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c24
Vojtech Zeisek
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c25
Vadim Plessky
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c26
Michal Seben
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c27
--- Comment #27 from Michal Seben
Confirmed that booting with ipv6.disable=1 results in a successful boot.
With this new information, while trawling I found this message on the lkml
http://lkml.org/lkml/2010/1/10/84 http://bugzilla.kernel.org/show_bug.cgi?id=15042
Larry Finger :
The only relevance to nmi_watchdog is that vboxdrv turns off that watchdog when loading a VM. Perhaps a real machine and other kinds of VM work around a race condition through the use of the watchdog, but VB has this disabled. I'm grasping at straws here.
The first reference you quote above talks about a race between ipv6.ko loading/initializing and the starting of sshd. Does the kernel on the NET install iso actually start sshd? If so, perhaps a sleep 10 at the start of the sshd script would avoid the problem.
I checked the log while booting with 700 MB VM. In that case, the system does not try to load ipv6. There must be some kind of free RAM test that skips the load. Without IPV6, the load succeeds.
-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c28
Michal Seben
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c29
--- Comment #29 from Paul Hands
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c30
Jeff Mahoney
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c31
--- Comment #31 from Vadim Plessky
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c32
--- Comment #32 from Vadim Plessky
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c33
--- Comment #33 from Vadim Plessky
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c34
Jiri Bohac
Created an attachment (id=341021) --> (http://bugzilla.novell.com/attachment.cgi?id=341021) [details] Screenshot of the hang, showing 2 cycles of the repeat
This looks similar to the symptoms discussed in http://www.mail-archive.com/linuxppc-dev@lists.ozlabs.org/msg37042.html, but that one was believed to be a PPC problem (?!) -> CCing Tejun Heo anyway. This bug also reminded me that I was planning to make CONFIG_IPV6=y for all kernel flavours (Bug #561611). Did that just now. If this really were some kind of race between IPv6 initialization and the socket syscall (as suggested by Bug #574463, Comment 9), having IPV6=y will work around this. Bug #574463, Comment 10:
I checked the log while booting with 700 MB VM. In that case, the system does not try to load ipv6. There must be some kind of free RAM test that skips the load. Without IPV6, the load succeeds.
Huh? I really doubt we have any check like that in the installation system. I will have a look. I will dig into this more next week. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c35
--- Comment #35 from Michal Seben
What is visible from Xorg.0.log file is that mouse driver is not loaded
(II) config/hal: Adding input device VirtualBox Guest Service (II) LoadModule: "vboxmouse" (II) Loading /usr/lib/xorg/modules/input/vboxmouse_drv.so (II) Module vboxmouse: vendor="Sun Microsystems Inc." compiled for 0.0.0, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 4.0 (EE) module ABI major version (4) doesn't match the server's version (7) (II) UnloadModule: "vboxmouse" (II) Unloading /usr/lib/xorg/modules/input/vboxmouse_drv.so (EE) Failed to load module "vboxmouse" (module requirement mismatch, 0) (EE) No input driver matching `vboxmouse' (EE) config/hal: NewInputDeviceRequest failed (15)
It explains why mouse is not visible on X screen. But why X itself (KDM4 login?) is not visible?..
Hi Vadim ! these bugs with X and vbox mouse driver should be fixed in Milestone 4 see bnc#584085 and bnc#587980 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c36
--- Comment #36 from Paul Hands
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c37
--- Comment #37 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c38
--- Comment #38 from Vadim Plessky
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c39
--- Comment #39 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c40
--- Comment #40 from Tejun Heo
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c41
--- Comment #41 from Vadim Plessky
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c42
--- Comment #42 from Stephan Kulow
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c43
--- Comment #43 from Vadim Plessky
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c44
--- Comment #44 from Michal Seben
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c45
--- Comment #45 from Michal Seben
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c46
--- Comment #46 from Michal Seben
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c
Michal Seben
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c
Michal Seben
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c
Bernhard Wiedemann
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c47
--- Comment #47 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c48
--- Comment #48 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c49
--- Comment #49 from Jiri Bohac
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c50
--- Comment #50 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c51
--- Comment #51 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c52
--- Comment #52 from Rastislav Krupansky
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c53
--- Comment #53 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c54
--- Comment #54 from Inge Svensson
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c55
--- Comment #55 from Rastislav Krupansky
Obviously, VB on Windows is a different beast. I also have 3.1.6, but on an x86_64 openSUSE 11.2 host. It still boots with the workaround.
When it starts booting, press the ESC key (if you see the splash scree), then press the special key + f4. For me the special key is the right CTRL. Note what you see here when it hangs and/or crashes.
on attached screenshot is full output what i can see -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c56
--- Comment #56 from Vadim Plessky
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c57
--- Comment #57 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c58
--- Comment #58 from Rastislav Krupansky
@Rastislav: I think you are trying to boot the Live CD. The "ipv6.disable=1" trick works for the NET install CD and the DVD. The top line of the picture you posted shows that "ipv6.disable=1" is not a valid identifier. In addition, the NET install CD does not use the Kiwi CD boot system. It boots a normal kernel.
Yes, you are right, i´m trying LiveCD. I thought workaround works for liveCD also. @Vadim: You can post your experiences with VMware into bug 574857. This bug is filed for VMware and tracked by VMware people. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c59
--- Comment #59 from Vadim Plessky
(In reply to comment #32)
What is visible from Xorg.0.log file is that mouse driver is not loaded
(II) config/hal: Adding input device VirtualBox Guest Service (II) LoadModule: "vboxmouse" (II) Loading /usr/lib/xorg/modules/input/vboxmouse_drv.so (II) Module vboxmouse: vendor="Sun Microsystems Inc." compiled for 0.0.0, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 4.0 (EE) module ABI major version (4) doesn't match the server's version (7) (II) UnloadModule: "vboxmouse" (II) Unloading /usr/lib/xorg/modules/input/vboxmouse_drv.so (EE) Failed to load module "vboxmouse" (module requirement mismatch, 0) (EE) No input driver matching `vboxmouse' (EE) config/hal: NewInputDeviceRequest failed (15)
It explains why mouse is not visible on X screen. But why X itself (KDM4 login?) is not visible?..
Hi Vadim ! these bugs with X and vbox mouse driver should be fixed in Milestone 4 see bnc#584085 and bnc#587980
Hi Michal! I confirm that bug with X and 'vboxmouse' has been fixed in OpenSUSE 11.3 Milestone4. Installation of KDE Live CD has been done in VirtualBox 3.1.6 (hosted in Windows Vista). No additional tuning, like ipv6.disable=1, was necessary. ------------------------ X.Org X Server 1.7.6 Release Date: 2010-03-17 X Protocol Version 11, Revision 0 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux linux-yd5w 2.6.33-6-default #1 SMP 2010-02-25 20:06:12 +0100 i686 .. (II) config/hal: Adding input device VirtualBox Guest Service (II) LoadModule: "vboxmouse" (II) Loading /usr/lib/xorg/modules/input/vboxmouse_drv.so (II) Module vboxmouse: vendor="Sun Microsystems Inc." compiled for 0.0.0, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 7.0 (**) Load address of symbol "VBOXMOUSE" is 0xb4b45200 (**) VirtualBox Guest Service: always reports core events (**) VirtualBox Guest Service: Device: "/dev/vboxguest" (II) XINPUT: Adding extended input device "VirtualBox Guest Service" (type: MOUSE) (**) VirtualBox Guest Service: (accel) keeping acceleration scheme 1 (**) VirtualBox Guest Service: (accel) acceleration profile 0 (II) VirtualBox Guest Service: On. (II) VirtualBox Guest Service: Off. (II) Open ACPI successful (/var/run/acpid.socket) (II) VirtualBox Guest Service: On. ------------------------ In order to verify it, I had to kill existing installation of 11.3 Milestone3 (start from MS4 Live CD, and make complete new install to HDD) BUT: bug 574857 - Can´t start and install live cd in VMware is still present in Milestone 4. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c60
--- Comment #60 from Jiri Bohac
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c61
--- Comment #61 from Jiri Bohac
Is your VB the OSE version? I'm running the pre-compiled variety as I need pass-thru for USB devices.
I was using OSE, yes. But now I tried with the pre-compiled version and still could not reproduce the problem :( -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c62
--- Comment #62 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c63
--- Comment #63 from Michal Seben
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c64
--- Comment #64 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c65
--- Comment #65 from Tejun Heo
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c66
--- Comment #66 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c67
--- Comment #67 from Jiri Bohac
[ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0]) ... [ 44.781407] * pcpu debug:going to memset: chunk=e8e71140, cpu=0, off=8832, size=64, addr=fec00000
Yes, I also thought this was the reason at first, but I think the IOAPIC address refers to a physical address, while the allocated memory that memset faults on is at virtual address fec00000, right?
2.6.34-rcX has a random memory corruption bug which is showing up as various boot failures. Yinghai has a patch.
http://thread.gmane.org/gmane.linux.kernel/963616/focus=964914
This looks pretty deterministic, It fails at exactly the same place for more people.
-rc3 has the fix which got committed to suse kernel repo a couple of days ago. It should soon appear on Factory.
Also, this bug is probably going to stop appearing with the new kernel in Factory, because I recently switched IPv6 to be compiled-in. Most likely, this bug is not related to IPv6 at all and it is just a coincidence that the order in which the install CD image loads kernel modules makes IPv6 be the first one to need a new allocation of pcpu data and trigger this bug. With IPv6 compiled in, this order is going to change and the bug will either be triggered by something else or will not show at all. But even if this bug disappears, I think it is worth finding out what the cause was, before it causes other headaches in a different situation. More debugging soon, I currently have some more urgents bugs to deal with. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c68
--- Comment #68 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c69
--- Comment #69 from Tejun Heo
Yes, I also thought this was the reason at first, but I think the IOAPIC address refers to a physical address, while the allocated memory that memset faults on is at virtual address fec00000, right?
Indeed, but it still gets on my nerves that they share the same address.
2.6.34-rcX has a random memory corruption bug which is showing up as various boot failures. Yinghai has a patch.
http://thread.gmane.org/gmane.linux.kernel/963616/focus=964914
This looks pretty deterministic, It fails at exactly the same place for more people.
On the same configuration, this will cause the same failure. Given that virtual envs end up being the same on multiple configurations, I still think this could be the culprit. Maybe it's a good idea to test w/ -rc3 with ipv6 compiled as module or -rc2 w/ only Yinghai's fix applied? Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c70
--- Comment #70 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c71
--- Comment #71 from Michal Seben
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c72
--- Comment #72 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c73
Michal Seben
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c74
--- Comment #74 from Paul Hands
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c75
--- Comment #75 from Larry Finger
http://bugzilla.novell.com/show_bug.cgi?id=576681
http://bugzilla.novell.com/show_bug.cgi?id=576681#c76
--- Comment #76 from Bernhard Wiedemann
participants (1)
-
bugzilla_noreply@novell.com