From: Andrew Ruthven <puck@catalyst.net.nz>
To: linux-kernel@vger.kernel.org
Subject: [oops] in bluetooth
Date: Mon, 28 May 2007 21:38:09 +1200 [thread overview]
Message-ID: <1180345089.819.28.camel@lamb> (raw)
[-- Attachment #1: Type: text/plain, Size: 4381 bytes --]
[Please Cc replies to me, I'll try and keep an eye on the acrhives, but
no guarantees]
Hi,
Just a follow-up to Marcel regarding Pavel's bluetooth oops. I've had
the same issue with both 2.6.21 and 2.6.21.2 (skipped .1). I'm able to
reproduce the oops.
My scenario is connecting from a Treo650 via bluetooth to access the
Internet by my ADSL link.
The first connection after booting worked just fine, but every attempt
after that failed with a oops.
Changing to 2.6.22-rc3 as suggested by Marcel however works just fine.
Here is an except from kern.log for the failure with the 2.6.21.2
kernel:
May 26 13:01:32 chimaera kernel: BUG: unable to handle kernel NULL
pointer dereference at virtual address 00000008
May 26 13:01:32 chimaera kernel: printing eip:
May 26 13:01:32 chimaera kernel: c01892e4
May 26 13:01:32 chimaera kernel: *pde = 00000000
May 26 13:01:32 chimaera kernel: Oops: 0000 [#1]
May 26 13:01:32 chimaera kernel: Modules linked in: ppp_deflate bsd_comp
ppp_async crc_ccitt ppp_generic slhc lirc_serial lirc_de
v rfcomm l2cap nfsd exportfs thermal fan button processor ac ip6t_LOG
nf_conntrack_ipv6 xt_limit ip6table_filter ip6_tables sit t
unnel4 tun bitrev crc32 ipt_MASQUERADE ipt_REJECT xt_multiport
ipt_recent xt_state xt_mark xt_MARK ipt_LOG xt_tcpudp iptable_mang
le iptable_filter iptable_nat ip_tables nf_nat nf_conntrack_ipv4
nf_conntrack nfnetlink x_tables nfs lockd nfs_acl sunrpc ipv6 pa
rport_pc parport e100 3c59x mii hci_usb bluetooth uhci_hcd usbcore
deflate zlib_deflate zlib_inflate twofish twofish_common serpe
nt aes blowfish des cbc ecb blkcipher sha256 sha1 md5 af_key
snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_p
cm snd_timer snd soundcore snd_page_alloc hostap_pci hostap
ieee80211_crypt
May 26 13:01:32 chimaera kernel: CPU: 0
May 26 13:01:32 chimaera kernel: EIP: 0060:[<c01892e4>] Not
tainted VLI
May 26 13:01:32 chimaera kernel: EFLAGS: 00010286 (2.6.21.2-chimaera
#1)
May 26 13:01:32 chimaera kernel: EIP is at sysfs_move_dir+0x24/0x130
May 26 13:01:32 chimaera kernel: eax: ccfd72f0 ebx: 00000000 ecx:
00000000 edx: d7e7f760
May 26 13:01:32 chimaera kernel: esi: d7e95dac edi: c03073fb ebp:
d7e7f760 esp: c9f95e70
May 26 13:01:32 chimaera kernel: ds: 007b es: 007b fs: 00d8 gs:
0033 ss: 0068
May 26 13:01:32 chimaera kernel: Process pppd (pid: 9595, ti=c9f94000
task=c1368590 task.ti=c9f94000)
May 26 13:01:32 chimaera kernel: Stack: c0307409 c37e4e68 c37e4e68
c03073fb cce0ca60 c37e4e68 c03073fb d7e7f760
May 26 13:01:32 chimaera kernel: c01c22f4 d5d309c0 c03073fb
cce0ca60 d5d309c0 d5d309c0 00000000 c37e4e00
May 26 13:01:32 chimaera kernel: 00000000 d6ae60f0 d7e7f760
c02240f1 c37e4e68 d49580a0 c5a0b800 d6ae60f0
May 26 13:01:32 chimaera kernel: Call Trace:
May 26 13:01:32 chimaera kernel: [<c01c22f4>] kobject_move+0xa4/0x130
May 26 13:01:32 chimaera kernel: [<c02240f1>] device_move+0x51/0x110
May 26 13:01:32 chimaera kernel: [<d8ac4f11>] rfcomm_tty_close
+0x51/0x80 [rfcomm]
May 26 13:01:32 chimaera kernel: [<c020d8c6>] release_dev+0x146/0x620
May 26 13:01:32 chimaera kernel: [<c01022e8>] do_notify_resume
+0x438/0x6e0
May 26 13:01:32 chimaera kernel: [<c01c4248>] rb_insert_color+0x68/0xc0
May 26 13:01:32 chimaera kernel: [<c012940d>] ktime_get_ts+0x1d/0x50
May 26 13:01:32 chimaera kernel: [<c01292a9>] hrtimer_nanosleep
+0xa9/0x100
May 26 13:01:32 chimaera kernel: [<c020dda7>] tty_release+0x7/0x10
May 26 13:01:32 chimaera kernel: [<c01533e1>] __fput+0x91/0x160
May 26 13:01:32 chimaera kernel: [<c01509b7>] filp_close+0x47/0x80
May 26 13:01:32 chimaera kernel: [<c0151cfa>] sys_close+0x6a/0xa0
May 26 13:01:32 chimaera kernel: [<c0102878>] syscall_call+0x7/0xb
May 26 13:01:32 chimaera kernel: =======================
May 26 13:01:33 chimaera kernel: Code: 8d bc 27 00 00 00 00 55 57 56 53
83 ec 10 89 44 24 04 8b 40 24 85 c0 0f 84 ea 00 00 00 85
d2 8b 58 30 0f 84 f2 00 00 00 8b 72 30 <8b> 43 08 31 ff 3b 46 08 75 10
e9 c3 00 00 00 8b 43 08 83 c0 68
May 26 13:01:33 chimaera kernel: EIP: [<c01892e4>] sysfs_move_dir
+0x24/0x130 SS:ESP 0068:c9f95e70
Cheers!
--
Andrew Ruthven, Wellington, New Zealand
At work: andrew.ruthven@catalyst.net.nz
At home: andrew@etc.gen.nz
GPG fpr: 34CA 12A3 C6F8 B156 72C2 D0D7 D286 CE0C 0C62 B791
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-05-28 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 9:38 Andrew Ruthven [this message]
2007-05-31 17:49 ` [oops] in bluetooth Chuck Ebbert
-- strict thread matches above, loose matches on Subject: below --
2007-05-18 14:13 Pavel Machek
2007-05-18 14:19 ` Marcel Holtmann
2007-05-18 15:01 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1180345089.819.28.camel@lamb \
--to=puck@catalyst.net.nz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox