It does on my system :
alpha 21164 at 516 MHz, 576 MB ram.
kernel 2.1.129, compiled with gcc-2.8.1, binutils 2.9.1.
matroxfb as a module, I got this :
Unable to handle kernel paging request at virtual address 000000000b001fde
insmod(444): Oops 0
pc = [<fffffe000008e938>] ra = [<fffffe000008f140>] ps = 0000
r0 = 0000000000000000 r1 = 0000000000000003 r2 = ffffffffffe00000
r3 = 0000000000000000 r4 = 000000000b000000 r5 = fffffe0000090e68
r6 = 000000000a000000 r7 = fffffc00004a7e80 r8 = fffffc0022bd0000
r9 = fffffe0000090e68 r10= 0000000000400000 r11= 000000000a000000
r12= fffffe0000090d18 r13= fffffe0000090fc0 r14= fffffc0022bd3dc8
r15= fffffc0022bd3f10
r16= 0000000000400000 r17= fffffc0022bd3dd0 r18= fffffe0000091718
r19= fffffc0022bd3d50 r20= fffffc0022bd3d48 r21= fffffc0000000000
r22= 0000000000000000 r23= 0000000000000001 r24= 0000000000000080
r25= 000000000000000a r27= fffffc000031a2d0 r28= 0000000000000000
gp = fffffe000009a858 sp = fffffc0022bd3d78
Code: 2fe00000 a48508c0 47e07401 <2c441fde> 20641fde 48230161 48430042 44220401 3c241fde
Trace: [<fffffc00003251bc>] [<fffffc0000310b48>]
The offending code is somewhere in matroxfb_getmemory() (I do not know
how to find symbol adresses in modules, therefore I looked for the code
in the assembly output of gcc -S on matroxfb.c -- it seems that one of
the mga_outb() triggers the oops). Passing "mem=4" as an argument to
modprobe did not help.
When compiled in the kernel, I get the oops at boot time, and the
machine halts. Other people use it, so I was asked not to disable
it for too long a time, and I could not handcopy the oops.
By the way, if someone had an Xserver for Alpha that could handle a
Matrox Millenium II with 4 MB of ram, and not crash when I use the
zooming function of xdvi, it would be really great.
Thanks for any help,
--Thomas Pornin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/