Yes, trying to get PCI Passthough working for an Apple OEM nVidia 6600 PCI-E card, on a x86 host in Qemu-PPC. Fcode looks like: (unnamed-fcode) [0xe34] 25615: (unnamed-fcode) [0xdff] 25616: (unnamed-fcode) [0x93d] 25617: b(lit) ( 0x010 ) 0xf 25618: <> ( 0x03d ) 25619: b?branch ( 0x014 ) 0x0026 ( =dec 38) 25620: (unnamed-fcode) [0x9bd] 25621: b(lit) ( 0x010 ) 0xff 25622: and ( 0x023 ) 25623: my-space ( 0x103 ) 25624: + ( 0x01e ) 25625: (unnamed-fcode) [0xa08] 25626: b(lit) ( 0x010 ) 0x6 25627: and ( 0x023 ) 25628: b(lit) ( 0x010 ) 0x4 25629: = ( 0x03c ) 25630: b?branch ( 0x014 ) 0x0009 () 25631: b(') ( 0x011 ) (unnamed-fcode) [0x9c1] 25632: b(to) ( 0x0c3 ) (unnamed-fcode) [0x9c0] 25633: b(>resolve) ( 0x0b2 ) 25634: b(>resolve) ( 0x0b2 ) 25635: (unnamed-fcode) [0xddf] 25636: (unnamed-fcode) [0xe04] 25637: (unnamed-fcode) [0xe38] 25638: (unnamed-fcode) [0xe06] 25639: (unnamed-fcode) [0xce5] 25640: (unnamed-fcode) [0xdb0] 25641: (unnamed-fcode) [0xe07] 25642: (unnamed-fcode) [0xe1a] 25643: (unnamed-fcode) [0xc5b] 25644: (unnamed-fcode) [0xe28] 25645: (unnamed-fcode) [0xe20] 25646: (unnamed-fcode) [0xdfa] 25647: (unnamed-fcode) [0xe37] 25648: (unnamed-fcode) [0xe2c] 25649: (unnamed-fcode) [0xe2d] 25650: b(") ( 0x012 ) ( len=0xb [11 bytes] ) " NVDA,Parent" 25651: device-name ( 0x201 ) 25652: 1 ( 0x0a6 ) 25653: encode-int ( 0x111 ) 25654: b(") ( 0x012 ) ( len=0xe [14 bytes] ) " #address-cells" 25655: property ( 0x110 ) 25656: 0 ( 0x0a5 ) 25657: encode-int ( 0x111 ) 25658: b(") ( 0x012 ) ( len=0xb [11 bytes] ) " #size-cells" 25659: property ( 0x110 ) 25660: (unnamed-fcode) [0x9c7] 25661: (unnamed-fcode) [0x93d] 25662: b(lit) ( 0x010 ) 0x35 25663: >= ( 0x042 ) 25664: b?branch ( 0x014 ) 0x000d ( =dec 13) 25665: 1 ( 0x0a6 ) 25666: (unnamed-fcode) [0x933] 25667: lshift ( 0x027 ) 25668: (unnamed-fcode) [0x935] 25669: or ( 0x024 ) 25670: b(to) ( 0x0c3 ) (unnamed-fcode) [0x935] 25671: b(>resolve) ( 0x0b2 ) 25672: (unnamed-fcode) [0x941] 25673: b(lit) ( 0x010 ) 0x10 25674: lshift ( 0x027 ) 25675: (unnamed-fcode) [0x935] 25676: or ( 0x024 ) 25677: encode-int ( 0x111 ) 25678: b(") ( 0x012 ) ( len=0xd [13 bytes] ) " NVDA,Features" 25679: property ( 0x110 ) 25680: 1 ( 0x0a6 ) 25681: encode-int ( 0x111 ) 25682: b(") ( 0x012 ) ( len=0xa [10 bytes] ) " NVDA,Level" 25683: property ( 0x110 ) 25684: 0 ( 0x0a5 ) 25685: 0 ( 0x0a5 ) 25686: (unnamed-fcode) [0xe2e] 25687: (unnamed-fcode) [0x9bc] 25688: (unnamed-fcode) [0x9c3] 25689: (unnamed-fcode) [0xe2e] 25690: encode+ ( 0x112 ) 25691: (unnamed-fcode) [0x9c0] 25692: (unnamed-fcode) [0x9c6] 25693: (unnamed-fcode) [0xe2e] 25694: encode+ ( 0x112 ) 25695: (unnamed-fcode) [0x9be] 25696: (unnamed-fcode) [0x9c4] 25697: (unnamed-fcode) [0xe2e] 25698: encode+ ( 0x112 ) 25699: (unnamed-fcode) [0x9bf] 25700: (unnamed-fcode) [0x9c5] 25701: (unnamed-fcode) [0xe2e] 25702: encode+ ( 0x112 ) 25703: b(") ( 0x012 ) ( len=3 ) " reg" 25704: property ( 0x110 ) 25705: 1 ( 0x0a6 ) 25706: encode-int ( 0x111 ) 25707: b(") ( 0x012 ) ( len=0xe [14 bytes] ) " #address-cells" 25708: property ( 0x110 ) 25709: 0 ( 0x0a5 ) 25710: encode-int ( 0x111 ) 25711: b(") ( 0x012 ) ( len=0xb [11 bytes] ) At the point where it breaks. On Sunday, December 17, 2017, 11:41:55 AM EST, Tarl Neustaedter tarl-b2@tarl.net wrote:
On 2017-Dec-17 11:29 , Jd Lyons wrote:
0 > 4010026 400 dump 4010026 c3 09 a9 0e 34 0d ff 09 3d 10 00 00 00 0f 3d 14 �.�.4.�.=.....=. 4010036 00 26 09 bd 10 00 00 00 ff 23 01 03 1e 0a 08 10 .&.�....�#...... 4010046 00 00 00 06 23 10 00 00 00 04 3c 14 00 09 11 09 ....#.....<..... 4010056 c1 c3 09 c0 b2 b2 0d df 0e 04 0e 38 0e 06 0c e5 ��.���.�...8...� 4010066 0d b0 0e 07 0e 1a 0c 5b 0e 28 0e 20 0d fa 0e 37 .�.....[.(. .�.7 4010076 0e 2c 0e 2d 12 0b 4e 56 44 41 2c 50 61 72 65 6e .,.-..NVDA,Paren 4010086 74 02 01 a6 01 11 12 0e 23 61 64 64 72 65 73 73 t..�....#address
That sure looks like Fcode for an nvidia card.
Looks like trouble when Openbios tries to build the device up in Name Space?
The code had just created an array property of some kind, maybe the "reg" property (if you looked back, you could probably figure out what it was). It looks like the next thing it's going to do is deal with some nvidia-specific features.
Either way, try "words" to see if it got around to doing any definitions. Also, since it blew up, at that point it's worth doing the "dev /pci ls" and see what got created.