Hello,
I get kernel NULL-pointers when I close my video application ('studio') and
then, X usually locks.
Only way to get back into the machine is ssh'ing and typing 'reboot' (after
examining dmesg, of course) or resetting the box. The
keyboard/mouse/video-card are locked by X, it seems, there's no way to
'free' then and killing X remotely doesn't seem to help anything. Rebooting
is the only thing that helped me so far. And rebooting should be for
changing hardware ;-).
The video editor uses zoran hardware to playback the video (using Serguei
Miridonov's zoran driver, version 0.8, for a Miro/Pinnacle DC10+). The
video editor closes 'nicely', i.e. it returns control to the terminal and
gives the quit message. Directly after returning control to the terminal, X
locks up.
I was using X 4.01 (am just upgrading to 4.03 to retest it in there) with
kernel 2.4.4, and I'm using the XFree 'nv' driver. The video editor uses
the video4linux/Xvideo extension in Xfree to display video in the
(gtk-)application.
The kernel says (dmesg):
-------------------------------------------------------
DC10plus[0]: ioctl VIDIOCGAUDIO not supported
DC10plus[0]: ioctl VIDIOCGFREQ not supported
DC10plus[0]: jpg_qbuf: buffers not yet allocated
Unable to handle kernel NULL pointer dereference at virtual address
00000000
printing eip:
c01114f8
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c01114f8>]
EFLAGS: 00010006
eax: c4481980 ebx: 00000000 ecx: 00000000 edx: c4481984
esi: c70f9ecf edi: c5efc054 ebp: c70f9d6c esp: c70f9d50
ds: 0018 es: 0018 ss: 0018
Process studio (pid: 788, stackpage=c70f9000)
Stack: c4481984 00000001 00000282 00000001 c4481980 c70f9ecf c3c47241
c4481000
c01688b3 c1227ed0 00000002 c5c0e000 00000046 00000000 c70f9d94
00000046
c5c0e000 00000001 c011b2fb c5c0e000 00000202 00000000 0011b385
0000001d
Call Trace: [<c01688b3>] [<c011b2fb>] [<c013c346>] [<c015b3b5>]
[<c01225bc>] [<c01dc377>] [<c016b25d>]
[<c01679c0>] [<c0169415>] [<c016565e>] [<c01692b0>] [<c012ef56>]
[<c0106c37>]
Code: 8b 01 85 45 f0 74 4f 31 c0 9c 5e fa c7 01 00 00 00 00 8b 51
Unable to handle kernel NULL pointer dereference at virtual address
00000000
printing eip:
c01114f8
*pde = 055dc067
*pte = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c01114f8>]
EFLAGS: 00013012
eax: c3f33ee4 ebx: 00000000 ecx: 00000000 edx: c3f33ee8
esi: c409c0e0 edi: c5efc00c ebp: c5c0fdf4 esp: c5c0fdd8
ds: 0018 es: 0018 ss: 0018
Process X (pid: 706, stackpage=c5c0f000)
Stack: c3f33ee8 00000001 00003286 00000001 c3f33ee4 c409c0e0 c6370ec0
c409c0e0
c01accb9 00000000 c15df780 00000040 c6370ec0 c15df780 00000040
c01ddc15
c409c0e0 00000040 c5c0fe34 c409c134 00000000 c409c0e0 c409c420
00000000
Call Trace: [<c01accb9>] [<c01ddc15>] [<c01aa3ac>] [<c01ad21b>]
[<c01aa6c3>] [<c01aa75b>] [<c012f11c>]
[<c01aa516>] [<c011137b>] [<c012f283>] [<c0106c37>]
Code: 8b 01 85 45 f0 74 4f 31 c0 9c 5e fa c7 01 00 00 00 00 8b 51
DC10plus[0]: timeout: codec isr=0x04, csr=0x04
-------------------------------------------------------------------
I ran ksymoops on these thingies, although I'm not really sure whether it
has any use since it's not really an oops (or is it?). They are attached as
log[45].
Is this X, kernel or my application? (since it crashes X and the kernel
gives errors too, I guess it's a combination?)
Anyway, if I could get rid of this I'd be very happy, it's always bad to
see your self-written application crash the box.
-- Ronald
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 15 2001 - 21:00:22 EST