Re: 2.6.13-rc4-git4: bluetooth oops on pcmcia shutdown
Andreas Steinmetz <[EMAIL PROTECTED]> wrote: > > The attached bluetooth oops can be reliably reproduced on my x86_64 > laptop. It happens when hciattach is still running while a sequence of > "cardctl eject" and then "killproc /sbin/cardmgr" is executed. > Though this seems to point to preempt I could manage to cause similar > oopses on non-preemptible kernels a while ago. Again, it doesn't look like we'll have a quick fix for this, so a bugzilla entry would be appreciated, please. It would help if you can identify an earlier 2.6 kernel which didn't have the bug, thanks. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.13-rc4-git4: bluetooth oops on pcmcia shutdown
Andreas Steinmetz [EMAIL PROTECTED] wrote: The attached bluetooth oops can be reliably reproduced on my x86_64 laptop. It happens when hciattach is still running while a sequence of cardctl eject and then killproc /sbin/cardmgr is executed. Though this seems to point to preempt I could manage to cause similar oopses on non-preemptible kernels a while ago. Again, it doesn't look like we'll have a quick fix for this, so a bugzilla entry would be appreciated, please. It would help if you can identify an earlier 2.6 kernel which didn't have the bug, thanks. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.13-rc4-git4: bluetooth oops on pcmcia shutdown
The attached bluetooth oops can be reliably reproduced on my x86_64 laptop. It happens when hciattach is still running while a sequence of "cardctl eject" and then "killproc /sbin/cardmgr" is executed. Though this seems to point to preempt I could manage to cause similar oopses on non-preemptible kernels a while ago. -- Andreas Steinmetz SPAMmers use [EMAIL PROTECTED] Unable to handle kernel NULL pointer dereference at 0014 RIP: {uart_flush_buffer+43} PGD 0 Oops: 0002 [1] PREEMPT CPU 0 Modules linked in: hci_usb serial_cs pcmcia yenta_socket rsrc_nonstatic pcmcia_core ehci_hcd uhci_hcd parport_pc parport snd_via82xx_modem snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss hfc_usb ipaq usbhid pl2303 usbserial usb_storage snd_via82xx gameport sd_mod snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device hisax isdn nls_iso8859_15 nls_cp850 ip_conntrack_ftp ipt_state ip_conntrack ipt_ULOG iptable_filter ipt_REJECT ip_tables nfsd exportfs lockd sunrpc autofs4 cifs sbp2 Pid: 2995, comm: hciattach Not tainted 2.6.13-rc4-git4-gringo RIP: 0010:[] {uart_flush_buffer+43} RSP: 0018:81001c0b9b68 EFLAGS: 00010013 RAX: RBX: 810002208c80 RCX: 81001e6d3018 RDX: RSI: 81001c0b9b58 RDI: 0001 RBP: 81001e6d3000 R08: 81003f01ce98 R09: 0001 R10: R11: 0246 R12: 81003d76ba80 R13: 8052e6c0 R14: R15: FS: 2af3edb0() GS:8061c800() knlGS:556d16b0 CS: 0010 DS: ES: CR0: 8005003b CR2: 0014 CR3: 1b1a2000 CR4: 06e0 Process hciattach (pid: 2995, threadinfo 81001c0b8000, task 81001f94f4a0) Stack: 0292 81003db82200 81001e6d3000 803567ac 81003db82200 81002614ac00 803567e4 8052e6c0 80356931 Call Trace:{hci_uart_flush+92} {hci_uart_close+20} {hci_uart_tty_close+49} {release_dev+1805} {free_hot_cold_page+239} {free_pgd_range+1078} {_atomic_dec_and_lock+38} {dput+35} {tty_release+17} {__fput+178} {filp_close+110} {put_files_struct+115} {do_exit+522} {__dequeue_signal+501} {do_group_exit+269} {get_signal_to_deliver+1515} {do_signal+159} {thread_return+0} {thread_return+220} {lock_timer_base+49} {del_timer+104} {schedule_timeout+156} {process_timeout+0} {sysret_signal+28} {ptregscall_common+103} Code: c7 40 14 00 00 00 00 c7 40 10 00 00 00 00 ff 34 24 9d bf 01 RIP {uart_flush_buffer+43} RSP CR2: 0014 <1>Fixing recursive fault but reboot is needed! scheduling while atomic: hciattach/0x0001/2995 Call Trace:{schedule+122} {do_exit+246} {do_unblank_screen+21} {do_page_fault+1807} {error_exit+0} {uart_flush_buffer+43} {uart_flush_buffer+39} {hci_uart_flush+92} {hci_uart_close+20} {hci_uart_tty_close+49} {release_dev+1805} {free_hot_cold_page+239} {free_pgd_range+1078} {_atomic_dec_and_lock+38} {dput+35} {tty_release+17} {__fput+178} {filp_close+110} {put_files_struct+115} {do_exit+522} {__dequeue_signal+501} {do_group_exit+269} {get_signal_to_deliver+1515} {do_signal+159} {thread_return+0} {thread_return+220} {lock_timer_base+49} {del_timer+104} {schedule_timeout+156} {process_timeout+0} {sysret_signal+28} {ptregscall_common+103}
2.6.13-rc4-git4: bluetooth oops on pcmcia shutdown
The attached bluetooth oops can be reliably reproduced on my x86_64 laptop. It happens when hciattach is still running while a sequence of cardctl eject and then killproc /sbin/cardmgr is executed. Though this seems to point to preempt I could manage to cause similar oopses on non-preemptible kernels a while ago. -- Andreas Steinmetz SPAMmers use [EMAIL PROTECTED] Unable to handle kernel NULL pointer dereference at 0014 RIP: 802cc1fb{uart_flush_buffer+43} PGD 0 Oops: 0002 [1] PREEMPT CPU 0 Modules linked in: hci_usb serial_cs pcmcia yenta_socket rsrc_nonstatic pcmcia_core ehci_hcd uhci_hcd parport_pc parport snd_via82xx_modem snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss hfc_usb ipaq usbhid pl2303 usbserial usb_storage snd_via82xx gameport sd_mod snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device hisax isdn nls_iso8859_15 nls_cp850 ip_conntrack_ftp ipt_state ip_conntrack ipt_ULOG iptable_filter ipt_REJECT ip_tables nfsd exportfs lockd sunrpc autofs4 cifs sbp2 Pid: 2995, comm: hciattach Not tainted 2.6.13-rc4-git4-gringo RIP: 0010:[802cc1fb] 802cc1fb{uart_flush_buffer+43} RSP: 0018:81001c0b9b68 EFLAGS: 00010013 RAX: RBX: 810002208c80 RCX: 81001e6d3018 RDX: RSI: 81001c0b9b58 RDI: 0001 RBP: 81001e6d3000 R08: 81003f01ce98 R09: 0001 R10: R11: 0246 R12: 81003d76ba80 R13: 8052e6c0 R14: R15: FS: 2af3edb0() GS:8061c800() knlGS:556d16b0 CS: 0010 DS: ES: CR0: 8005003b CR2: 0014 CR3: 1b1a2000 CR4: 06e0 Process hciattach (pid: 2995, threadinfo 81001c0b8000, task 81001f94f4a0) Stack: 0292 81003db82200 81001e6d3000 803567ac 81003db82200 81002614ac00 803567e4 8052e6c0 80356931 Call Trace:803567ac{hci_uart_flush+92} 803567e4{hci_uart_close+20} 80356931{hci_uart_tty_close+49} 802b108d{release_dev+1805} 80159a7f{free_hot_cold_page+239} 80163876{free_pgd_range+1078} 802617f6{_atomic_dec_and_lock+38} 8018f863{dput+35} 802b1191{tty_release+17} 80177642{__fput+178} 80175cbe{filp_close+110} 80132813{put_files_struct+115} 801331da{do_exit+522} 8013b745{__dequeue_signal+501} 80133dad{do_group_exit+269} 8013d8eb{get_signal_to_deliver+1515} 8010ce9f{do_signal+159} 80408174{thread_return+0} 80408250{thread_return+220} 80139b31{lock_timer_base+49} 80139be8{del_timer+104} 80408f6c{schedule_timeout+156} 8013a7c0{process_timeout+0} 8010db2f{sysret_signal+28} 8010de17{ptregscall_common+103} Code: c7 40 14 00 00 00 00 c7 40 10 00 00 00 00 ff 34 24 9d bf 01 RIP 802cc1fb{uart_flush_buffer+43} RSP 81001c0b9b68 CR2: 0014 1Fixing recursive fault but reboot is needed! scheduling while atomic: hciattach/0x0001/2995 Call Trace:80407caa{schedule+122} 801330c6{do_exit+246} 802bf5c5{do_unblank_screen+21} 8011d95f{do_page_fault+1807} 8010e399{error_exit+0} 802cc1fb{uart_flush_buffer+43} 802cc1f7{uart_flush_buffer+39} 803567ac{hci_uart_flush+92} 803567e4{hci_uart_close+20} 80356931{hci_uart_tty_close+49} 802b108d{release_dev+1805} 80159a7f{free_hot_cold_page+239} 80163876{free_pgd_range+1078} 802617f6{_atomic_dec_and_lock+38} 8018f863{dput+35} 802b1191{tty_release+17} 80177642{__fput+178} 80175cbe{filp_close+110} 80132813{put_files_struct+115} 801331da{do_exit+522} 8013b745{__dequeue_signal+501} 80133dad{do_group_exit+269} 8013d8eb{get_signal_to_deliver+1515} 8010ce9f{do_signal+159} 80408174{thread_return+0} 80408250{thread_return+220} 80139b31{lock_timer_base+49} 80139be8{del_timer+104} 80408f6c{schedule_timeout+156} 8013a7c0{process_timeout+0} 8010db2f{sysret_signal+28} 8010de17{ptregscall_common+103}