Re: ibook G3,current kernel panic

Hello,

>
>Hmm, weird.
>Please run 'ofctl -p' and mail me the output 

I tried to run 'ofctl -p',but no 'ofctl' on 3.1.
4.99.22 kernel stops 'db>' ,so I can't run 'ofctl'.

But I found 'dmesg' is available on 'db>',and noticed one
thing.
No 'ofb0' is found, 'macfb0' is detected.

Here is several lines of dmesg.
------------------------------------------------------------
--------------

NetBSD 4.99.22 (GENERIC) #0: Sun Jul 8 14:49:40 JST 2007
        pen4pen4.masafumi:
/usr/obj/sys/arch/macppc/compile/GENERIC
total memory = 192 MB
avail memory = 175 MB
timecounter: Timecounters tich every 10.000 msec
init_interrupt: found OpenPIC  pa 0x80040000, 0x80040000
mainbus0 (root)
cpu0 at mainbus0: 750 (Revision 0.2), ID 0 (primary)
cpu0: HID0
8090x0a4<EMCP,DOZE,DPM,ICE,DCE,SGE,BTIC,BHT>,powersave
: 1
cpu0: 466.67 MHZ, 512KB WB L2 cache
uni_n0 at mainbus0 address 0xf8000000
ki2c0 at uni_n0 address 0xf8001000
iic0 at ki2c0: I2C bus
uninorth0 at mainbus0
pci0 at uninorth0 bus 0
pci0: i/o space, memory space enabled
pchb0 at pci0 dev 11 function 0
pchb0: Apple Computer UniNorth AGP Interface (rev. 0x00)
machfb0 at pci0 dev 16 function 0: ATI Technologies Rage
Mobility M3 (AGP) (rev.
 0x02)
machfb0: 64 MB aperture at 0x94000000, 16 KB registers at
0x90000000
machfb0: 16384 KB (unknown type) 14.318 MHz, maximum RAMDAC
clock 230 MHz
machfb0: chip ID mismatch, 0xff7f != 0x4c46

------------------------------------------------------------
----------------------
I am wondering that kernel without 'machfb0' works ?

Thanks.

Masafumi Hotta

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Jul 13, 2007, at 10:33, Masafumi Hotta wrote:

>> Hmm, weird.
>> Please run 'ofctl -p' and mail me the output
>
> I tried to run 'ofctl -p',but no 'ofctl' on 3.1.
> 4.99.22 kernel stops 'db>' ,so I can't run 'ofctl'.

ofctl works on 3.1, the ioctl()s it uses have been present
in NetBSD  
for ages. Just build it from a 4.0 source tree. The version
in -current  
uses proplib soo building it on 3.1 might be a little more
of an  
effort.

> But I found 'dmesg' is available on 'db>',and
noticed one thing.
> No 'ofb0' is found, 'macfb0' is detected.

Eh, macfb is a mac68k thing ;)

> Here is several lines of dmesg.
> machfb0 at pci0 dev 16 function 0: ATI Technologies
Rage Mobility M3  
> (AGP) (rev.
>  0x02)
> machfb0: 64 MB aperture at 0x94000000, 16 KB registers
at 0x90000000
> machfb0: 16384 KB (unknown type) 14.318 MHz, maximum
RAMDAC clock 230  
> MHz
> machfb0: chip ID mismatch, 0xff7f != 0x4c46
>
>
------------------------------------------------------------
----------- 
> -----------
> I am wondering that kernel without 'machfb0' works ?

It should.
Looks like what you have is based on a Rage XL which is
known broken  
for now :/
I thought I had machfb explicitly not match that kind of
hardware but  
apparently I'm wrong - I'll fix that. Unfortunately I don't
have the  
hardware to debug this problem :(
So, just disable machfb in your kernel config and ofb should
take over  
again.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRpec2MpnzkX8Yg2nAQI/2wf/TG0INEWCIuW8RAhQIRApHwOfPHLA
6FOQ
Mtn4UvO93D/2LHDFLDgslIh9som5i+W99ZHaC0s5EXu4tipiusB4ZZsuJF03
vk4m
tngtjW41iV3qSY3vNQjHBK/zc9y8OF24oGhUD3TR/eObJ9mUDI2YD20WDX5D
gFjo
i9jAuf8BDUlW/q1ywQKGAr7STN+W28SbexpVHEKQNSO9v7UWS3gugDTm1oRW
A48L
mg4YMkZdM8QRjelupcafY4/9gvJnAn7yHlFthiMSHvA4kZxLJidsnmPD5fzL
C4Zv
K4PmJGMPQdBBOIOOgJY97VU1/jxYq7F0vuzJnOtdkJ9BjQiYiXoqeg==
=J5/3
-----END PGP SIGNATURE-----