Qemu SPARC64 Panics on Sun Solaris 5.8 - BOP_ALLOC failed

Bug #1905037 reported by Morteza NourelahiAlamdari
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QEMU
Expired
Undecided
Unassigned

Bug Description

Hi,

Running Sun Solaris 5.8 by SPARC64, will panic by "BOP_ALLOC failed":

$ qemu-system-sparc64 \
  -drive file=sparc.qcow2,if=ide,bus=0,unit=0 \
  -drive file=sun5.8.no1.iso,format=raw,if=ide,bus=1,unit=0,media=cdrom,readonly=on \
  -boot d
$ qemu-system-sparc64 -M sun4u -boot d -cdrom sun5.8.no1.iso -net nic -net user -m 2048

Both commands will raise this error:

OpenBIOS for Sparc64
Configuration device id QEMU version 1 machine id 0
kernel cmdline
CPUs: 1 x SUNW,UltraSPARC-IIi
UUID: 00000000-0000-0000-0000-000000000000
Welcome to OpenBIOS v1.1 built on Oct 28 2019 17:08
  Type 'help' for detailed information
Trying cdrom:f...
Not a bootable ELF image
Not a bootable a.out image

Loading FCode image...
Loaded 5936 bytes
entry point is 0x4000
Evaluating FCode...
open isn't unique.
Alloc of 0x2000 bytes at 0x16000 refused.

panic[cpu0]/thread=10408000: BOP_ALLOC failed

0000000010406ea0 unix:boot_alloc+44 (2000, 2000, 1000, 30000016000, 31002afd100, 30000014000)
  %l0-3: 000000001041b2d0 0000030ffffff138 0000000000000001 000000001044bdc0
  %l4-7: 000000001044af18 000000001044aef8 000000001044bd20 000000000000000b
0000000010406f50 unix:segkmem_alloc+30 (30000016000, 2000, 0, 0, 1044efe0, 1044b300)
  %l0-3: 0000030ffffff5c0 ffffffffffffe000 0000000000000000 000000001044bdc0
  %l4-7: 000000001044af18 000000001044aef8 000000001044f840 000000001004a438
0000000010407010 genunix:vmem_xalloc+3e4 (1044ea18, 1044ee20, ffffffffffffffff, ffffffffffffffff, 0, 0)
  %l0-3: 000000001004a3b4 ffffffffffffe000 000000001044ea18 0000000000002000
  %l4-7: 0000000000000000 0000000000000000 0000000000002000 000000001044ea38
0000000010407140 genunix:kmem_slab_create+8c (0, 0, 2000, 300000043c0, 0, 1044ea18)
  %l0-3: 0000000000000000 0000030ffffff220 0000000000000000 000000001044bdc0
  %l4-7: 000000001044af18 00000300000043c0 000000001044f840 0000000000007fa3
0000000010407230 genunix:kmem_cache_alloc+180 (0, 0, 0, 300000043c0, 0, 0)
  %l0-3: 0000030000004740 ffffffffffffe000 000000001044ea18 0000000000002000
  %l4-7: 0000030ffffff220 0000000000000000 0000000000002000 000000001044ea38
00000000104072e0 genunix:kmem_slab_create+130 (200, 30000014000, 2000, 3000000da40, 0, 200)
  %l0-3: 0000000000000000 ffffffffffffe000 000000001044ea18 0000000000002000
  %l4-7: 0000030fffffef68 000003000000da40 0000000000002000 000000001044ea38
00000000104073d0 genunix:kmem_cache_alloc+180 (0, 0, 0, 3000000da40, 0, 0)
  %l0-3: 000003000000ddc0 0000000000000000 0000000000010000 ffffffffffffffff
  %l4-7: 0000030000013fc8 00000300000052c0 0000030000013fc8 0000030000013fc0
0000000010407480 genunix:kmem_alloc+2c (2000, 0, 2000, 3000000da40, 0, 30000013fb8)
  %l0-3: 0000030000005640 0000000010147bfa 0000000000000000 0000000000000020
  %l4-7: 0000000010446678 0000000010452543 0000000000000000 0000000000000000
0000000010407530 krtld:kobj_zalloc+c (2000, 1000, 2000, 300000052c0, f0, 0)
  %l0-3: 000003000000e740 ffffffffffffffc0 000000001044f8e0 00000000000003c0
  %l4-7: 000000001044aa70 0000000000000000 0000000000000000 000000000000000b
00000000104075e0 krtld:kobj_open_file+38 (2000, 30000011f88, 104397f0, 0, 0, 1)
  %l0-3: 0000000000000008 0000000000000000 0000000000000000 0000000000000000
  %l4-7: 0000000000000008 000000001004a3b4 0000000010452538 000000001004a438
0000000010407690 genunix:mod_read_system_file+70 (10437c00, 2000, 1, 0, 26, 1043a0d8)
  %l0-3: 0000000000004000 0000000000000008 0000000000004008 0000000000000000
  %l4-7: 0000000000002000 000000001004a3b4 0000000010451670 000000001004a438
00000000104077b0 genunix:kmem_init+1b8 (10471b50, 0, 0, 91, 1, 291)
  %l0-3: 000000001041dc00 0000000000002000 000000001004a3b4 000000001004a438
  %l4-7: 0000000010418590 0000000000001fff 000000001040d970 0000000000007fa3
0000000010407880 unix:startup_memlist+b14 (10418400, 30000016080, 30000000000, 10418668, 2000, 30000016000)
  %l0-3: 0000000000000103 0000000010423c00 0000000000000020 0000031002c00000
  %l4-7: 0000000010418400 000000001041d000 000000001041c000 000000001041b000
0000000010407970 unix:startup+c (10428c00, 0, 0, 1, 0, ffffffffffffffff)
  %l0-3: 0000000010026090 000000000000d925 0000000000000afd 0000000000000000
  %l4-7: 0000000010472880 00000000002e8c43 00000000000beafd 0000000000000afd
0000000010407a20 genunix:main+4 (1040d400, 2000, 10407ec0, 10408030, fff2, 10052a0c)
  %l0-3: 0000000010408000 0000000000000001 0000000000000015 0000000000000f36
  %l4-7: 0000000010429618 0000000010472880 00000000000d7438 0000000000000540

skipping system dump - no dump device configured
rebooting...
BOOTpanic - kernel: prom_reboot: reboot call returned!
EXIT

I'm not sure, but I think changes in this issue https://bugs.launchpad.net/qemu/+bug/1892540 might fix this one as well.

Tags: sparc
Revision history for this message
Thomas Huth (th-huth) wrote :

The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.

Changed in qemu:
status: New → Incomplete
Revision history for this message
Thomas Huth (th-huth) wrote :

Sorry, wrong ticket, this is not an old one, so setting this to incomplete already was a mistake.

Changed in qemu:
status: Incomplete → New
Revision history for this message
Thomas Huth (th-huth) wrote : Moved bug report

This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:

 https://gitlab.com/qemu-project/qemu/-/issues/293

Changed in qemu:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.