Matrox Mystique video card caused Kernel Panic on HP Visualize 785/B2000 with rebuilt 2.6.8 kernel
Hi,
Wonder if anyone has the exprience on compiling a working 2.6.8 kernel for
Matrox Mystique video card on an HPPA RISC workstation?
Basic h/w configuration are as follows:
1) HP Visualize 785/B2000 with 256 MB of memory, 400 MHz processor & 10 GB
disk;
2) HP 910 monitor with STI fxe video card (in trouble, I switched to ttys0
as the console);
3) Additional Matrox Mystique video card with Unisys monitor;
4) No HP/UX. Only Debian GNU/Linux;
Software configuration:
5) Sarge distribution from 27 April ISO images were used for the installation;
6) All packages installed updated/upgraded to the latest available (27 or
28 May);
7) Kernel source from "usr/src/kernel-source-2.6.8.tar.bz2";
8) Kernel patch for HPPA for 2.6.8 has been applied;
Built the kernel using instructions from "PARISC-LINUX: Building The Kernel
documentation". Having problems using the "Short Recipe to Build a Kernel"
as no initial RAM disk was created.
I had better luck in following their "The Old, Grotty Way To Build a
Kernel". I skipped the "make modules_install" step (the kernel
configuration file came with the source files did not select Loadable
Module Support and I chose to compile the Matrox acceleration and Mystique
support into the Kernel. I have also created the initial RAM disk by
"mkinitrd -o /usr/src/kernel-source-2.6.8/initrd.img-2.6.8 2.6.8".
Voila, the B2000 booted past the initial RAM disk for the first time,
discovered the built-in hardware, and the PCI Matrox Mystique card for the
first time, then disaster struck. Kernel panic after the discovery of
Matrox Mystique card. Can anyone advise me what went wrong?
The boot process and the Kernel panic and associated error messages are
appended next for your perusal.
Rgds,
Lee
ps. Boot messages captured:
Booting...
Boot IO Dependent Code (IODC) revision 0
HARD Booted.
palo ipl 1.5 root@c3k Fri May 14 16:17:38 MDT 2004
Partition Start(MB) End(MB) Id Type
1 1 31 f0 Palo
2 8427 8678 82 swap
3 32 157 83 ext2
4 158 8426 83 ext2
PALO(F0) partition contains:
0/vmlinux32 4968722 bytes @ 0x44000
Information: No console specified on kernel command line. This is normal.
PALO will choose the console currently used by firmware (serial).
Command line for kernel: 'root=/dev/sda4 HOME=/ console=ttyS0 TERM=vt102
palo_kernel=3/vmlinux'
Selected kernel: /vmlinux from partition 3
Selected ramdisk: /initrd.img from partition 3
ELF32 executable
Entry 00100228 first 00100000 n 2
Segment 0 load 00100000 size 2512588 mediaptr 0x1000
Segment 1 load 00366000 size 1159300 mediaptr 0x267000
Loading ramdisk 4874240 bytes @ 0fb48000...
Branching to kernel entry point 0x00100228. If this is the last
message you see, you may need to switch your console. This is
a common symptom -- search the FAQ and mailing list at parisc-linux.org
Linux version 2.6.8 (root@debianhppa) (gcc version 3.3.5 (Debian
1:3.3.5-12)) #1 Mon May 30 20:35:23 SGT 2005
FP[0] enabled: Rev 1 Model 16
The 32-bit Kernel has started...
Determining PDC firmware type: System Map.
model 00005d00 00000481 00000000 00000002 775714fc 100000f0 00000008
000000b2 000000b2
vers 00000204
CPUID vers 17 rev 8 (0x00000228)
capabilities 0x3
model 9000/785/B2000
Total Memory: 256 Mb
initrd: 1fb48000-1ffee000
initrd: reserving 0fb48000-0ffee000 (mem_max 10000000)
LCD display at f05d0008,f05d0000 registered
Built 1 zonelists
Kernel command line: root=/dev/sda4 HOME=/ console=ttyS0 TERM=vt102
palo_kernel=3/vmlinux
PID hash table entries: 16 (order 4: 128 bytes)
Console: colour dummy device 160x64
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 262144k available
Calibrating delay loop... 799.53 BogoMIPS
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
checking if image is initramfs...it isn't (ungzip failed); looks like an initrd
NET: Registered protocol family 16
EISA bus registered
Searching for devices...
Found devices:
1. Astro BC Runway Port at 0xfed00000 [10] { 12, 0x0, 0x582, 0x0000b }
2. Elroy PCI Bridge at 0xfed30000 [10/0] { 13, 0x0, 0x782, 0x0000a }
3. Elroy PCI Bridge at 0xfed32000 [10/1] { 13, 0x0, 0x782, 0x0000a }
4. Kazoo W+ at 0xfffa0000 [32] { 0, 0x0, 0x5d0, 0x00004 }
5. Memory at 0xfed10200 [49] { 1, 0x0, 0x09d, 0x00009 }
CPU(s): 1 x PA8600 (PCX-W+) at 400.000000 MHz
SBA found Astro 2.1 at 0xfed00000
lba version TR2.1 (0x2) found at 0xfed30000
PCI: Enabled native mode for NS87415 (pif=0x8f)
lba version TR2.1 (0x2) found at 0xfed32000
SCSI subsystem initialized
usbcore: registered new driver hub
matroxfb: Matrox Mystique (PCI) detected
Backtrace:
[<101f65d8>] pci_bus_write_config_dword+0x34/0x44
[<1028f41c>] initMatrox2+0x3a0/0x9b0
[<1028ff08>] matroxfb_probe+0x1c4/0x254
[<101f8038>] pci_device_probe_static+0x60/0x78
[<101f8080>] __pci_device_probe+0x30/0x38
[<101f80b4>] pci_device_probe+0x2c/0x58
[<10228b38>] bus_match+0x48/0x80
[<10228c94>] driver_attach+0x70/0xa4
[<102291a0>] bus_add_driver+0x9c/0xb8
[<102296a4>] driver_register+0x48/0x54
[<101f1364>] kobject_add+0x54/0x100
[<101f8374>] pci_register_driver+0x4c/0x60
[<10102fe8>] init+0x38/0x108
[<1010ec5c>] ret_from_kernel_thread+0x1c/0x24
Kernel Fault: Code=15 regs=106b05c0 (Addr=fd801fde)
YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001001111111100001111 Not tainted
r00-03 00000000 104a0810 1028f430 00800000
r04-07 104a09c0 104a09c0 103bc03c fd800000
r08-11 fffffff4 fd000000 104a0810 103bb810
r12-15 103a6010 3b9aca00 103a7010 1048a010
r16-19 f00008c4 f000017c f0000174 00000003
r20-23 02000000 fd800000 104a09c0 104a0810
r24-27 fd000000 104a120c 00800000 1038d010
r28-31 00000000 104a09c0 106b05c0 1028f41c
sr0-3 00000000 00000000 00000000 00000000
sr4-7 00000000 00000000 00000000 00000000
IASQ: 00000000 00000000 IAOQ: 1028ee5c 1028ee60
IIR: 62b33fbc ISR: 00000000 IOR: fd801fde
CPU: 0 CR30: 106b0000 CR31: 103f0000
ORIG_R28: 00000000
IAOQ[0]: matroxfb_getmemory+0x2c/0x168
IAOQ[1]: matroxfb_getmemory+0x30/0x168
RP(r2): initMatrox2+0x3b4/0x9b0
Kernel panic: Kernel Fault
Reply to: