Bug#394742: linux-image-2.6.17-2-686: Bluetooth related panic
On Mon, Oct 23, 2006 at 12:33:39PM -0600, dann frazier wrote:
> Thanks Mikko. Can you reproduce with the 2.6.18 kernel in sid? It
> should install fine on an etch system, and is the kernel we plan to
> ship in etch.
Yes. Exact steps in this case: boot to run level 2, login as root on
virtual terminal 2, run screen, 'pon gprs-bt', open another shell to
ping some host, open a third shell to do 'telinit 1'. Running 'pon
gprs-bt' inside an X session didn't crash this time. Hand written trace
from camera shots:
release_dev: rfcomm1: read/write wait queue active!
...[gazillion times]
BUG: unable to handel kernel NULL pointer dereference at virtual address 00000005
printing eip:
00000005
*pde = 00000000
Oops: 0000 [#3]
SMP:
Modules linkde in: ...
CPU: 0
EIP: 0060:[<00000005>] Not tainted VLI
EFLAGS: 00010012 (2.6.18-1-686 #1)
EIP is at 0x5
eax: ca84df28 ebx: ca84df28 ecx: 00000000 edx: 00000003
esi: ca3d1ab0 edi: 00000001 ebp: ca24fc50 esp: ca24fc30
ds: 007b es: 007b ss: 0068
Process pppd (pid: 3166, ti=ca24e000 task=ca3d1030 task.ti=ca24e000)
Stack: ...
Call Trace:
[<c011624d>] __wake_up_common+0x2f/0x53
[<c011669e>] __wake_up+0x2a/0x3d
[<c01f8d5b>] release_dev+0x239/0x5ee
[<c0220a1d>] _spin_lock_bh+0x8/0x18
...[too much hex for my fingers and eyes] lock_sock+0x89/0x91
lock_sock+0x89/0x91
inet6_destroy_sock+0x22/0x3a [ipv6]
tty_release+0xf/0x18
__fput+0x8a/0x13f
flip_close+0x4e/0x54
put_files_struct+0x65/0xa7
do_exit+0x1d1/0x714
die+0x1e2/0x28a
die+0x265/0x28a
do_page_fault+0x3b4/0x481
do_page_fault+0x0/0x481
error_code+0x39/0x40
cp_new_stat+0xed/0x152
rfcomm_tty_chars_in_buffer+0x8/0x19 [rfcomm]
tty_wait_until_sent+0x74/0xb9
default_wake_funtion+0x0/0xc
n_tty_ioctl+0x0/0x40d
set_termios+0xbe/0x2e9
do_path_lookup+0x20a/0x255
path_lookup+0xf/0x11
n_tty_ioctl++xb4d/0xbac
unix_dgram_connect+0x6a/0x137
sys_connect+0x7d/0xa9
do_wp_page+0x12b/0x344
inotify_d_instantiate+0x36/0x59
__handle_mm_fault+0x6d8/0x740
do_ioctl+0x47/0x5d
vfs_ioctl+0x24a/0x25c
sys_ioctl+0x48/0x5f
syscall_call+0x7/0xb
Code: Bad EIP value.
EIP: [<00000005>] 0x5 SS:ESP 0068:ca24fc30
<1>Fixing recursive fault but reboot is needed!
Reply to: