Return-Path: Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) Subject: Re: Oops in rfcomm_sock_getsockopt on net-next as of 20131111 From: Marcel Holtmann In-Reply-To: <874n7j6xei.fsf@nemi.mork.no> Date: Mon, 11 Nov 2013 20:05:04 +0900 Cc: "linux-bluetooth@vger.kernel.org development" , netdev@vger.kernel.org Message-Id: <43866609-6219-4A87-A868-557CE1C673BD@holtmann.org> References: <874n7j6xei.fsf@nemi.mork.no> To: =?iso-8859-1?Q?Bj=F8rn_Mork?= Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Bjorn, > I got this when I booted my laptop with todays net-next: > > [ 16.064546] BUG: unable to handle kernel paging request at 00000c8bfd080975 > [ 16.064558] IP: [] rfcomm_sock_getsockopt+0x62/0x251 [rfcomm] > [ 16.064561] PGD 0 > [ 16.064564] Oops: 0000 [#1] SMP > [ 16.064637] Modules linked in: rfcomm bnep xt_hl binfmt_misc ip6table_filter ip6_tables x_tables nfsd nfs_acl nfs lockd fscache sunrpc 8021q garp stp llc tun loop fuse iTCO_wdt iTCO_vendor_support snd_hda_codec_conexant arc4 snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss iwlmvm mac80211 snd_pcm snd_page_alloc thinkpad_acpi nvram snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq iwlwifi coretemp uvcvideo cdc_mbim cdc_wdm videobuf2_vmalloc videobuf2_memops cdc_ncm kvm_intel videobuf2_core snd_seq_device psmouse usbnet lpc_ich videodev kvm snd_timer evdev serio_raw mfd_core mii cfg80211 i2c_i801 snd soundcore battery ac i915 i2c_algo_bit drm_kms_helper drm i2c_core acpi_cpufreq video wmi processor button btusb bluetooth rfkill ext4 crc16 jbd2 mbcache nbd sg sd_mod crc_t10dif sr_mod cdrom crct10dif_common ahci libahci microcode libata scsi_mod thermal thermal_sys ehci_pci uhci_hcd ehci_hcd e1000e usbcore ptp pps_core usb_common > [ 16.064656] CPU: 1 PID: 3153 Comm: bluetoothd Not tainted 3.12.0+ #136 > [ 16.064658] Hardware name: LENOVO 2776LEG/2776LEG, BIOS 6EET55WW (3.15 ) 12/19/2011 > [ 16.064660] task: ffff88022e50a440 ti: ffff8800b78b4000 task.ti: ffff8800b78b4000 > [ 16.064669] RIP: 0010:[] [] rfcomm_sock_getsockopt+0x62/0x251 [rfcomm] > [ 16.064670] RSP: 0018:ffff8800b78b5ed8 EFLAGS: 00010246 > [ 16.064672] RAX: 00000c8bfd080975 RBX: ffff8800b688b140 RCX: 00007fff7ae042f8 > [ 16.064674] RDX: 0000000000000003 RSI: 0000000000000012 RDI: ffff8800b688b140 > [ 16.064676] RBP: ffff8800b78b5f28 R08: 00007fff7ae042fc R09: 00007fff7ae042f8 > [ 16.064678] R10: 00007fff7ae042f8 R11: ffff8800b83ec180 R12: ffff8800b78bc800 > [ 16.064680] R13: 00007fff7ae042f8 R14: 0000000000000003 R15: ffff8800b78bc800 > [ 16.064682] FS: 00007f020d523740(0000) GS:ffff88023b000000(0000) knlGS:0000000000000000 > [ 16.064685] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > [ 16.064687] CR2: 00000c8bfd080975 CR3: 00000000b78a2000 CR4: 00000000000007e0 > [ 16.064688] Stack: > [ 16.064692] ffff8800b78b5f08 00007fff7ae042fc ffffffff8139b647 00007fff7ae04570 > [ 16.064696] ffff8800b78b5f50 ffff8800b688b140 0000000000000012 0000000000000003 > [ 16.064700] 0000000000000011 00007f020e6abce0 ffff8800b78b5f78 ffffffff812b8215 > [ 16.064701] Call Trace: > [ 16.064708] [] ? sysret_check+0x1b/0x56 > [ 16.064714] [] SyS_getsockopt+0x79/0x99 > [ 16.064718] [] system_call_fastpath+0x16/0x1b > [ 16.064756] Code: a0 31 c0 48 c7 c7 08 e0 7f a0 e8 35 45 9f e0 41 83 ff 12 0f 85 1e 01 00 00 4c 8b 7b 20 f6 05 a6 7a 00 00 04 49 8b 87 18 05 00 00 <4c> 8b 20 74 18 4c 89 fa 48 c7 c6 8f b9 7f a0 31 c0 48 c7 c7 30 > [ 16.064763] RIP [] rfcomm_sock_getsockopt+0x62/0x251 [rfcomm] > [ 16.064764] RSP > [ 16.064766] CR2: 00000c8bfd080975 > [ 16.064769] ---[ end trace f71c8d4720ff0e6f ]--- > > > I am using standard Debian startup scripts AFAIK, doing: > > /usr/bin/rfcomm -f /etc/bluetooth/rfcomm.conf bind all > > where my rfcomm.conf is completely empty except for comments. The > reported userspace version is > > RFCOMM configuration utility ver 4.99 > > Let me know if there is any other information you need to debug this > further. known issue. Check 0be087f56118b67479b6e1a542d1dcf54fa83615 from bluetooth-next tree. We just have not pushed that through wireless-next and net-next yet. Regards Marcel