Can't see any other reference to this yet, but I keep getting a kernel bug and lock up when switching between vdr-xine output device and the output of my TT-2300C.
Anyone else seen this?
------------[ cut here ]------------ kernel BUG at mm/vmalloc.c:348! invalid opcode: 0000 [#1] SMP Modules linked in: via drm ledxmit_serial(U) ledxmit_dev(U) rfcomm l2cap bluetooth autofs4 nfs lockd nfs_acl sunrpc ipv6 dm_mirror dm_multipath dm_mod snd_via82xx gameport stv0297 snd_ac97_codec ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_pcm dvb_ttpci dvb_core snd_timer parport_pc snd_page_alloc saa7146_vv parport snd_mpu401_uart video_buf snd_rawmidi saa7146 snd_seq_device videodev v4l2_common snd v4l1_compat button via_rhine i2c_viapro ttpci_eeprom soundcore pcspkr mii firewire_ohci i2c_core firewire_core crc_itu_t sg sr_mod cdrom pata_via ata_generic sata_via libata sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd CPU: 0 EIP: 0060:[<c04747c0>] Not tainted VLI EFLAGS: 00210246 (2.6.23.1-49.fc8 #1) EIP is at __vunmap+0xa9/0xe3 eax: 00000000 ebx: 00000000 ecx: 2cba3000 edx: 00000001 esi: e7e491c0 edi: 00000001 ebp: f7d7c3d0 esp: ea566f28 ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 Process vdr (pid: 2500, ti=ea566000 task=eabdc610 task.ti=ea566000) Stack: f89b23ac f8ace9e0 f89bc3d0 f89b23ac f7d7c38c f89b23ac f7d7c38c f8d19000 f89bace2 00200246 e8365780 f89b2420 00000008 e8365780 c191dbb0 f7ef2ae0 c0481eda 00000000 00000000 c191dbb0 c1bd1800 f7ef2ae0 e8365780 f1580a80 Call Trace: [<f89bc3d0>] dvbdmx_release_ts_feed+0x78/0x7e [dvb_core] [<f89bace2>] dvb_demux_release+0x8d/0x148 [dvb_core] [<c0481eda>] __fput+0xbb/0x171 [<c047f84d>] filp_close+0x51/0x58 [<c04808de>] sys_close+0x6e/0xa5 [<c040518a>] syscall_call+0x7/0xb ======================= Code: 6b c0 c7 04 24 2b 8d 6a c0 e8 5c 97 fb ff 83 c4 14 5b 5e 5f e9 e0 24 f9 ff 31 db 85 ff 75 18 eb 30 8b 46 10 8b 04 98 85 c0 75 04 <0f> 0b eb fe 31 d2 43 e8 d5 1a ff ff 3b 5e 14 72 e5 f6 46 0c 10 EIP: [<c04747c0>] __vunmap+0xa9/0xe3 SS:ESP 0068:ea566f28
Have now tried this with xineliboutput as well - and get the following:
BUG: unable to handle kernel NULL pointer dereference at virtual address 00000084 printing eip: c05b46eb *pde = 225c2067 *pte = 00000000 Oops: 0000 [#1] SMP Modules linked in: via drm ledxmit_serial(U) ledxmit_dev(U) rfcomm l2cap bluetooth autofs4 nfs lockd nfs_acl sunrpc ipv6 dm_mirror dm_multipath dm_mod stv0297 snd_via82xx gameport snd_ac97_codec ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_pcm dvb_ttpci dvb_core parport_pc saa7146_vv snd_timer parport video_buf snd_page_alloc saa7146 snd_mpu401_uart videodev snd_rawmidi v4l2_common snd_seq_device v4l1_compat snd via_rhine button ttpci_eeprom pcspkr soundcore i2c_viapro mii firewire_ohci i2c_core firewire_core crc_itu_t sg sr_mod cdrom pata_via ata_generic sata_via libata sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd CPU: 0 EIP: 0060:[<c05b46eb>] Not tainted VLI EFLAGS: 00210246 (2.6.23.9-85.fc8 #1) EIP is at sk_free+0x15/0xc7 eax: 00000000 ebx: ea86f5d8 ecx: 07fc136a edx: 00000000 esi: 000000d0 edi: f7bfe0c0 ebp: 0000006c esp: e20dbd54 ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068 Process exe (pid: 5972, ti=e20db000 task=e20fc000 task.ti=e20db000) Stack: 00000000 00200282 c1888000 ea86f5d8 000000d0 c05d061d c04f6b28 e20dbf60 00000000 e135f200 7fffffff f7bfe0c0 00000000 e20dbf58 e135f200 c05d0dc7 00000000 e1d6f320 e20dbf3c d9291900 00000000 00000000 e20dbe68 00001754 Call Trace: [<c05d061d>] netlink_unicast+0x159/0x1b4 [<c04f6b28>] copy_from_user+0x32/0x5e [<c05d0dc7>] netlink_sendmsg+0x274/0x280 [<c05b242d>] sock_sendmsg+0xd0/0xeb [<c0427c6f>] default_wake_function+0x0/0xc [<c043d495>] autoremove_wake_function+0x0/0x35 [<c04264a6>] __wake_up+0x32/0x43 [<c05cffe6>] netlink_insert+0x10f/0x119 [<c04f6b28>] copy_from_user+0x32/0x5e [<c05b2d90>] sys_sendto+0x115/0x135 [<c05b342b>] sys_getsockname+0x9f/0xb0 [<c05b4ce1>] sock_init_data+0x83/0x187 [<c04a4316>] inotify_d_instantiate+0x4a/0x70 [<c048ff1a>] d_alloc+0x141/0x16f [<c048fdd5>] d_instantiate+0x5c/0x60 [<c05b2129>] sock_attach_fd+0x53/0xb2 [<c05b3788>] sys_socketcall+0x17b/0x261 [<c040518a>] syscall_call+0x7/0xb ======================= Code: ec ff eb 07 89 f0 e8 8d 8f ec ff 31 f6 5f 89 f0 5d 5b 5e 5f 5d c3 56 53 89 c3 83 ec 0c 8b 93 68 01 00 00 8b 80 cc 00 00 00 85 d2 <8b> b0 84 00 00 00 74 04 89 d8 ff d2 8b 93 f8 00 00 00 85 d2 74 EIP: [<c05b46eb>] sk_free+0x15/0xc7 SS:ESP 0068:e20dbd54 vdr[6543]: segfault at 00000250 eip 008aa360 esp bfd68614 error 4
Different this time - "kernel NULL pointer dereference" rather than "mm/vmalloc.c:348"
any ideas??