shutting down the x-server with dri support on a i830M graficcard the kernel produce an oops and left the screen black. Aug 31 18:16:45 mobile kernel: printing eip: Aug 31 18:16:45 mobile kernel: c0124e20 Aug 31 18:16:45 mobile kernel: Oops: 0000 Aug 31 18:16:45 mobile kernel: CPU: 0 Aug 31 18:16:45 mobile kernel: EIP: 0010:[unlock_page+4/100] Not tainted Aug 31 18:16:45 mobile kernel: EIP: 0010:[<c0124e20>] Not tainted Aug 31 18:16:45 mobile kernel: EFLAGS: 00013246 Aug 31 18:16:45 mobile kernel: eax: 01000000 ebx: 01000000 ecx: c1510ba8 edx: 00000000 Aug 31 18:16:45 mobile kernel: esi: dd789000 edi: dea37800 ebp: 00000000 esp: de5d3ee4 Aug 31 18:16:45 mobile kernel: ds: 0018 es: 0018 ss: 0018 Aug 31 18:16:45 mobile kernel: Process X (pid: 4077, stackpage=de5d3000) Aug 31 18:16:45 mobile kernel: Stack: c1510ba8 dd789000 e0934d9f c1510ba8 de6a88c0 dda3e000 e0934def dea37800 Aug 31 18:16:45 mobile kernel: dd789000 de5d3f34 bffff924 de5d3f78 e09353da dea37800 00000040 dea37800 Aug 31 18:16:45 mobile kernel: df65ed60 40446440 00000000 dea37800 00000002 00000000 00000000 00000000 Aug 31 18:16:45 mobile kernel: Call Trace: [hid:__insmod_hid_S.bss_L96+672703/77201149] [hid:__insmod_hid_S.bss_L96+67 Aug 31 18:16:45 mobile kernel: Call Trace: [<e0934d9f>] [<e0934def>] [<e09353da>] [<e0930de2>] [<c013cf87>] Aug 31 18:16:45 mobile kernel: [system_call+51/56] Aug 31 18:16:45 mobile kernel: [<c010857b>] Aug 31 18:16:45 mobile kernel: Aug 31 18:16:45 mobile kernel: Code: 0f b6 43 1b 8b 14 85 1c c5 31 c0 69 c3 01 00 37 9e 8b 8a 98 without dri support there are no problems with i830M graficcards. is there a chance to get xfree working with dri? on SuSE 8.0 there are no problems with this card an xfree 4.2.0.
what kernel?
vanilla kernel 2.4.19 with acpi patches and also vanilla kernel 2.4.19 without acpi patches
That isn't a bug that we here at gentoo will be handling, I do however suggest you try the lolo-sources-2.4.19.9_rc2 kernel and see if you still have the problem. If the bug still exists, then you can report it to the kernel developers.
Hi guys, Brandon you are right. It's not a X bug, it's a kernel bug. Kernel 2.4.20-pre5 solves the problem.