[indiana-discuss] build 111a: happyface boot - pressing escape key reboots machine
James Cornell
sparcdr at gmail.com
Sun May 3 00:50:51 PDT 2009
On 5/3/2009 2:40 AM, Jürgen Keil wrote:
> There is not much visible information in the public
> description text for 6834260...
>
> I'm getting the following panic under VirtualBox 2.2.2 when
> I press a key during a build 111a happyface boot; is that the
> same problem?
>
>
>> ::status
>>
> debugging crash dump vmcore.0 (64-bit) from opensolaris
> operating system: 5.11 snv_111a (i86pc)
> panic message: lock_set_spl: ffffff00c66632d9 lock held and only one CPU
> dump content: kernel pages only
>
>
>> $C
>>
> ffffff00020bf9b0 vpanic()
> ffffff00020bfa20 lock_set_spl_spin+0x20c(ffffff00c66632d9, c, ffffff00c66632dc, 5)
> ffffff00020bfa80 mutex_vector_enter+0x45e(ffffff00c66632d8)
> ffffff00020bfad0 kbtrans_streams_key+0x38(ffffff00c66631c0, 29, 1)
> ffffff00020bfb00 kb8042_process_key+0x40(fffffffffbd3b740, 6e, 1)
> ffffff00020bfb40 kb8042_received_byte+0xe9(fffffffffbd3b740, 81)
> ffffff00020bfb70 kb8042_intr+0x6a(fffffffffbd3b740)
> ffffff00020bfbb0 i8042_intr+0xea(ffffff00c6668940)
> ffffff00020bfc00 av_dispatch_autovect+0x7c(1)
> ffffff00020bfc40 dispatch_hardint+0x33(1, 0)
> ffffff0002197860 switch_sp_and_call+0x13()
> ffffff00021978b0 do_interrupt+0x9e(ffffff00021978c0, 3cf)
> ffffff00021978c0 _interrupt+0xba()
> ffffff00021979c0 vgatext`vgatext_setfont+0x12c(ffffff00c69d5000)
> ffffff00021979e0 vgatext`vgatext_init+0x6f(ffffff00c69d5000)
> ffffff0002197a00 vgatext`vgatext_kdsettext+0x19(ffffff00c69d5000)
> ffffff0002197a30 vgatext`vgatext_kdsetmode+0x6b(ffffff00c69d5000, 2)
> ffffff0002197ad0 vgatext`do_gfx_ioctl+0xef(4b0a, 2, 80200000, ffffff00c69d5000)
> ffffff0002197b50 vgatext_ioctl+0x84(6300000000, 4b0a, 2, 80200000, ffffff00c5f24d88, ffffff0002197be4)
> ffffff0002197b90 cdev_ioctl+0x45(6300000000, 4b0a, 2, 80200000, ffffff00c5f24d88, ffffff0002197be4)
> ffffff0002197bd0 ldi_ioctl+0xb0(ffffff00c9bce008, 4b0a, 2, 80000000, ffffff00c5f24d88, ffffff0002197be4)
> ffffff0002197c00 progressbar_key_abort+0x67(ffffff00c7048550)
> ffffff0002197c40 progressbar_key_abort_thread+0x6f(ffffff00c66631c0)
> ffffff0002197c50 thread_start+8()
>
>
>> ::cpuinfo -v
>>
> ID ADDR FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD PROC
> 0 fffffffffbc36f80 1b 2 0 104 no no t-5 ffffff00020bfc60 sched
> | | |
> RUNNING <--+ | +--> PIL THREAD
> READY | 5 ffffff00020bfc60
> EXISTS | - ffffff0002197c60 sched
> ENABLE |
> +--> PRI THREAD PROC
> 60 ffffff00024abc60 sched
> 10 ffffff00c7b85c80 svc.configd
>
>
>> ::ptree
>>
> fffffffffbc2c030 sched
> ffffff00c6aa3a48 fsflush
> ffffff00c6aa46a8 pageout
> ffffff00c6aa5308 init
> ffffff00c9e45198 rmvolmgr
> ffffff00cee0b6c0 hald
> ffffff00cee0aa60 hald-runner
> ffffff00c800edf0 hald-addon-stora
> ffffff00c800c8d0 hald-addon-acpi
> ffffff00cee078e0 hald-addon-cpufr
> ffffff00c9e48318 hald-addon-netwo
> ffffff00c9e44538 VBoxService
> ffffff00cee09e00 dbus-daemon
> ffffff00cee08540 cron
> ffffff00c9e476b8 picld
> ffffff00c800d530 rcm_daemon
> ffffff00c800b010 syseventd
> ffffff00c9e438d8 powerd
> ffffff00c6aa2de8 nscd
> ffffff00c9e46a58 dhcpagent
> ffffff00c800fa50 devfsadm
> ffffff00c6a9fc68 kcfd
> ffffff00c8011310 nwamd
> ffffff00c6a9f008 dlmgmtd
> ffffff00c6aa1528 svc.configd
> ffffff00c6aa2188 svc.startd
> ffffff00c80106b0 net-routing-setu
> ffffff00c6aa08c8 grep
> ffffff00cee0c320 nawk
> ffffff00c9e42018 routeadm
>
>
>> ::msgbuf
>>
> MESSAGE
> ACPI: FACS @ 0x3fff0170/0x0040
> ACPI: APIC @ 0x3fff01b0/0x0040 (v 2 VBOX VBOXAPIC 0x00000001 ASL 0x00000061)
> NOTICE: ACPI HPET table query failed
>
> NOTICE: amd_iommu: No AMD IOMMU ACPI IVRS table
> pseudo-device: acpippm0
> acpippm0 is /pseudo/acpippm at 0
> pseudo-device: ppm0
> ppm0 is /pseudo/ppm at 0
> pci0 at root: space 0 offset 0
> pci0 is /pci at 0,0
> IDE device at targ 0, lun 0 lastlun 0x0
> model VBOX HARDDISK
> ATA/ATAPI-6 supported, majver 0x7e minver 0x22
> PCI-device: ide at 0, ata0
> ata0 is /pci at 0,0/pci-ide at 1,1/ide at 0
> UltraDMA mode 2 selected
> Disk0: <Vendor 'Gen-ATA ' Product 'VBOX HARDDISK '>
> cmdk0 at ata0 target 0 lun 0
> cmdk0 is /pci at 0,0/pci-ide at 1,1/ide at 0/cmdk at 0,0
> root on rpool/ROOT/opensolaris fstype zfs
> SMBIOS v2.5 loaded (256 bytes)
> /cpus (cpunex0) online
> pseudo-device: dld0
> dld0 is /pseudo/dld at 0
> 8042 device: keyboard at 0, kb8042 # 0
> kb80420 is /isa/i8042 at 1,60/keyboard at 0
> 8042 device: mouse at 1, mouse8042 # 0
> mouse80420 is /isa/i8042 at 1,60/mouse at 1
> NOTICE: MPO disabled because memory is interleaved
>
> cpu0: x86 (AuthenticAMD 40FB2 family 15 model 75 step 2 clock 2208 MHz)
> cpu0: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
> workaround applied for cpu erratum #122
> WARNING: BIOS microcode patch for AMD Athlon(tm) 64/Opteron(tm) processor
> erratum 131 was not detected; updating your system's BIOS to a version
> containing this microcode patch is HIGHLY recommended or erroneous system
> operation may occur.
>
> workaround applied for cpu issue #6336786
> pseudo-device: zfs0
> zfs0 is /pseudo/zfs at 0
> pseudo-device: devinfo0
> devinfo0 is /pseudo/devinfo at 0
> xsvc0 at root: space 0 offset 0
> xsvc0 is /xsvc at 0,0
> pseudo-device: pseudo1
> pseudo1 is /pseudo/zconsnex at 1
> ISA-device: fdc0
> pseudo-device: llc10
> llc10 is /pseudo/llc1 at 0
> ISA-device: ecpp0
> ecpp0 is /isa/lp at 1,378
> NOTICE: e1000g0 registered
> Intel(R) PRO/1000 Network Connection, Driver Ver. 5.3.8
> ISA-device: pit_beep0
> pit_beep0 is /isa/pit_beep
> fd0 at fdc0
> fd0 is /isa/fdc at 1,3f0/fd at 0,0
> pseudo-device: fcsm0
> fcsm0 is /pseudo/fcsm at 0
> pseudo-device: fcp0
> fcp0 is /pseudo/fcp at 0
> pseudo-device: ramdisk1024
> ramdisk1024 is /pseudo/ramdisk at 1024
> pseudo-device: lockstat0
> lockstat0 is /pseudo/lockstat at 0
> pseudo-device: lofi0
> lofi0 is /pseudo/lofi at 0
> pseudo-device: profile0
> profile0 is /pseudo/profile at 0
> pseudo-device: systrace0
> systrace0 is /pseudo/systrace at 0
> pseudo-device: fbt0
> fbt0 is /pseudo/fbt at 0
> pseudo-device: sdt0
> sdt0 is /pseudo/sdt at 0
> pseudo-device: fasttrap0
> fasttrap0 is /pseudo/fasttrap at 0
> pseudo-device: power0
> power0 is /pseudo/power at 0
> pseudo-device: srn0
> srn0 is /pseudo/srn at 0
> pseudo-device: dcpc0
> dcpc0 is /pseudo/dcpc at 0
> pseudo-device: ucode0
> ucode0 is /pseudo/ucode at 0
> pseudo-device: nvidia255
> nvidia255 is /pseudo/nvidia at 255
> pseudo-device: fssnap0
> fssnap0 is /pseudo/fssnap at 0
> pseudo-device: winlock0
> winlock0 is /pseudo/winlock at 0
> pseudo-device: nsmb0
> nsmb0 is /pseudo/nsmb at 0
> pseudo-device: pm0
> pm0 is /pseudo/pm at 0
> pseudo-device: pool0
> pool0 is /pseudo/pool at 0
> IP Filter: v4.1.9, running.
> pseudo-device: lx_systrace0
> lx_systrace0 is /pseudo/lx_systrace at 0
> PCI-device: pci80ee,cafe at 4, vboxguest0
> vboxguest0 is /pci at 0,0/pci80ee,cafe at 4
> ATAPI device at targ 0, lun 0 lastlun 0x0
> model VBOX CD-ROM
> ATA/ATAPI-6 supported, majver 0x7e minver 0x22
> PCI-device: ide at 1, ata1
> ata1 is /pci at 0,0/pci-ide at 1,1/ide at 1
> UltraDMA mode 2 selected
> sd0 at ata1: target 0 lun 0
> sd0 is /pci at 0,0/pci-ide at 1,1/ide at 1/sd at 0,0
> dump on /dev/zvol/dsk/rpool/dump size 512 MB
> NOTICE: e1000g0 link up, 1000 Mbps, full duplex
> device pciclass,030000 at 2(display#0) keeps up device sd at 0,0(sd#0), but the latter is not power managed
>
> panic[cpu0]/thread=ffffff00020bfc60:
> lock_set_spl: ffffff00c66632d9 lock held and only one CPU
>
>
> ffffff00020bfa20 unix:lock_set_spl_spin+20c ()
> ffffff00020bfa80 unix:mutex_vector_enter+45e ()
> ffffff00020bfad0 kbtrans:kbtrans_streams_key+38 ()
> ffffff00020bfb00 kb8042:kb8042_process_key+40 ()
> ffffff00020bfb40 kb8042:kb8042_received_byte+e9 ()
> ffffff00020bfb70 kb8042:kb8042_intr+6a ()
> ffffff00020bfbb0 i8042:i8042_intr+ea ()
> ffffff00020bfc00 unix:av_dispatch_autovect+7c ()
> ffffff00020bfc40 unix:dispatch_hardint+33 ()
> ffffff0002197860 unix:switch_sp_and_call+13 ()
> ffffff00021978b0 unix:do_interrupt+9e ()
> ffffff00021978c0 unix:cmnint+ba ()
> ffffff00021979c0 vgatext:vgatext_setfont+12c ()
> ffffff00021979e0 vgatext:vgatext_init+6f ()
> ffffff0002197a00 vgatext:vgatext_kdsettext+19 ()
> ffffff0002197a30 vgatext:vgatext_kdsetmode+6b ()
> ffffff0002197ad0 vgatext:do_gfx_ioctl+ef ()
> ffffff0002197b50 vgatext:vgatext_ioctl+84 ()
> ffffff0002197b90 genunix:cdev_ioctl+45 ()
> ffffff0002197bd0 genunix:ldi_ioctl+b0 ()
> ffffff0002197c00 unix:progressbar_key_abort+67 ()
> ffffff0002197c40 kbtrans:progressbar_key_abort_thread+6f ()
> ffffff0002197c50 unix:thread_start+8 ()
>
> syncing file systems...
> done
> dumping to /dev/zvol/dsk/rpool/dump, offset 65536, content: kernel
>
>
>
>> Jan Setje-Eilers wrote:
>>
>>> Since We'll need to integrate a fix into on, this is being tracked in
>>> bugster under 6834260. As soon as it shows up externally it should be
>>> available as:
>>>
>>> http://defect.opensolaris.org/bz/show_bug.cgi?id=6834260
>>>
>> make that:
>> http://bugs.opensolaris.org/view_bug.do?bug_id=6834260
>>
>> the other url is for bugster bugs.
>> jan
>>
>>
>>> -jan
>>>
>>> Jan Setje-Eilers wrote:
>>>
>>>> We've managed to get the reset to reproduce with bits that allowed
>>>> for kmdb interaction, and understand what the problem is. I'll get a
>>>> bug logged shortly.
>>>>
>>>> -jan
>>>>
>>>> Joanmarie Diggs wrote:
>>>>
>>>>> Hi Jan.
>>>>>
>>>>> On Fri, 2009-04-24 at 17:05 -0700, Jan
>>>>>
>> Setje-Eilers wrote:
>>
>>>>> [snip]
>>>>>
>>>>>> I've yet to see a system that happens to have
>>>>>>
>> a serial port on
>>
>>>>>> which this can be reproduced, so there's no
>>>>>>
>> particularly good way to
>>
>>>>>> debug this as it seems to happen before dumps
>>>>>>
>> are available.
>>
>>>>> [snip]
>>>>>
>>>>> I have one box with a serial port and I can
>>>>>
>> reproduce this bug on it.
>>
>>>>> The trick, as has been mentioned in other
>>>>>
>> messages in this thread, is
>>
>>>>> hitting escape at just the right time.
>>>>>
>>>>> I also have a serial cable, a USB to serial
>>>>>
>> adapter, a null modem
>>
>>>>> adapter, and a laptop which I can connect to this
>>>>>
>> box using that
>>
>>>>> cabling. What I lack is any knowledge whatsoever
>>>>>
>> as to what I would need
>>
>>>>> to do to get the desired output which would
>>>>>
>> enable someone to debug it.
>>
>>>>> I'm an end user. That said, I *can* follow
>>>>>
>> instructions. :-) Therefore,
>>
>>>>> if no one else has a box with a serial port on
>>>>>
>> which this bug can be
>>
>>>>> reproduced, feel free to email me with the exact
>>>>>
>> steps I would need to
>>
>>>>> take to get you what you need, and I'd be happy
>>>>>
>> to do it.
>>
>>>>> Take care.
>>>>> --Joanie
>>>>>
>>>>
>>>
>> _______________________________________________
>> indiana-discuss mailing list
>> indiana-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
>>
Doesn't happen on VMware Fusion 2/Workstation 6.5, only VirtualBox
(Tested 2.2.0 and 2.2.2)
For me, removing the graphical parameter from the boot entry, watching
the system boot shows this:
http://www.deviantptr.net/images/opensolaris/opensolaris-vbox-smf-bug.png
James
More information about the indiana-discuss
mailing list