mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Norris <haphazard@kc.rr.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.0-test7 usbserial oops
Date: Sat, 11 Oct 2003 14:35:59 -0500	[thread overview]
Message-ID: <20031011193558.GA1404@glitch.localdomain> (raw)
In-Reply-To: <20030911033054.GA1375@glitch.localdomain>

[-- Attachment #1: Type: text/plain, Size: 661 bytes --]

On Wed, Sep 10, 2003 at 10:30:55PM -0500, Greg Norris wrote:
> I'm seeing a consistent oops with usbserial under 2.6.0-test5, which
> occurs when I try to sync my pda using pilot-link.  The module seems to
> load (via hotplug) without any difficulty, and the sync itself works
> fine... the oops occurs when the module is unloaded.  Once this
> happens, it requires a reboot to get usb working again.

In case anyone was wondering, this problem still occurs with
2.6.0-test7.  I've attached all the relevant information which I'm
aware of, and would be happy to provide additional details/testing if
requested.  Suggestions would, of course, be quite welcome.


[-- Attachment #2: oops.decoded --]
[-- Type: text/plain, Size: 3924 bytes --]

ksymoops 2.4.9 on i686 2.6.0-test7.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.6.0-test7/ (default)
     -m /boot/System.map-2.6.0-test7 (specified)

Error (regular_file): read_ksyms stat /proc/ksyms failed
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Unable to handle kernel NULL pointer dereference at virtual address 000000d1
c020127f
*pde = 00000000
Oops: 0000 [#1]
CPU:    0
EIP:    0060:[<c020127f>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010206
eax: 00000005   ebx: f765c000   ecx: 00000000   edx: f75fba00
esi: c02e0ac8   edi: c02e0ae0   ebp: c1bdddf8   esp: c1bdddf4
ds: 007b   es: 007b   ss: 0068
Stack: c02e0ae0 c1bdde14 f8aa130b f75fba00 f8aa37e0 f8aa3393 f765c0d8 f765c0a4 
       c1bdde2c c01da849 f765c080 c1bdde34 c01dab61 f765c0a4 c1bdde44 c01b3ba0 
       f765c0a4 f765c000 00000001 f75fb680 c1bdde68 f8aa126c f765c0a4 f8aa37e0 
Call Trace:
 [<f8aa130b>] port_release+0x66/0xc5 [usbserial]
 [<c01da849>] device_release+0x5a/0x5e
 [<c01dab61>] device_del+0x6a/0x90
 [<c01b3ba0>] kobject_cleanup+0x73/0x75
 [<f8aa126c>] destroy_serial+0x189/0x1c2 [usbserial]
 [<c01b3ba0>] kobject_cleanup+0x73/0x75
 [<f8aa21bb>] usb_serial_disconnect+0x37/0x7e [usbserial]
 [<c01fbadb>] usb_unbind_interface+0x78/0x7a
 [<c01dbb47>] device_release_driver+0x62/0x64
 [<c01dbc6b>] bus_remove_device+0x54/0x93
 [<c01dab56>] device_del+0x5f/0x90
 [<c0201fe1>] usb_disable_device+0x73/0xae
 [<c01fc5dd>] usb_disconnect+0xa0/0xef
 [<c01fec61>] hub_port_connect_change+0x323/0x328
 [<c01fe5af>] hub_port_status+0x3a/0xa0
 [<c01fef59>] hub_events+0x2f3/0x371
 [<c01ff004>] hub_thread+0x2d/0xc2
 [<c010930e>] ret_from_fork+0x6/0x14
 [<c011bc92>] default_wake_function+0x0/0x2e
 [<c01fefd7>] hub_thread+0x0/0xc2
 [<c0107309>] kernel_thread_helper+0x5/0xb
Code: 8b 80 cc 00 00 00 85 c0 74 07 8b 40 20 85 c0 75 09 b8 ed ff 


>>EIP; c020127f <usb_unlink_urb+14/39>   <=====

>>ebx; f765c000 <__crc_redraw_screen+2e3c1f/48b3be>
>>edx; f75fba00 <__crc_redraw_screen+28361f/48b3be>
>>esi; c02e0ac8 <ktype_device+0/c>
>>edi; c02e0ae0 <devices_subsys+0/60>
>>ebp; c1bdddf8 <__crc_ide_handler_parser+12e5ff/2a0c6b>
>>esp; c1bdddf4 <__crc_ide_handler_parser+12e5fb/2a0c6b>

Trace; f8aa130b <__crc_pm_idle+19148c/2b7e5e>
Trace; c01da849 <device_release+5a/5e>
Trace; c01dab61 <device_del+6a/90>
Trace; c01b3ba0 <kobject_cleanup+73/75>
Trace; f8aa126c <__crc_pm_idle+1913ed/2b7e5e>
Trace; c01b3ba0 <kobject_cleanup+73/75>
Trace; f8aa21bb <__crc_pm_idle+19233c/2b7e5e>
Trace; c01fbadb <usb_unbind_interface+78/7a>
Trace; c01dbb47 <device_release_driver+62/64>
Trace; c01dbc6b <bus_remove_device+54/93>
Trace; c01dab56 <device_del+5f/90>
Trace; c0201fe1 <usb_disable_device+73/ae>
Trace; c01fc5dd <usb_disconnect+a0/ef>
Trace; c01fec61 <hub_port_connect_change+323/328>
Trace; c01fe5af <hub_port_status+3a/a0>
Trace; c01fef59 <hub_events+2f3/371>
Trace; c01ff004 <hub_thread+2d/c2>
Trace; c010930e <ret_from_fork+6/14>
Trace; c011bc92 <default_wake_function+0/2e>
Trace; c01fefd7 <hub_thread+0/c2>
Trace; c0107309 <kernel_thread_helper+5/b>

Code;  c020127f <usb_unlink_urb+14/39>
00000000 <_EIP>:
Code;  c020127f <usb_unlink_urb+14/39>   <=====
   0:   8b 80 cc 00 00 00         mov    0xcc(%eax),%eax   <=====
Code;  c0201285 <usb_unlink_urb+1a/39>
   6:   85 c0                     test   %eax,%eax
Code;  c0201287 <usb_unlink_urb+1c/39>
   8:   74 07                     je     11 <_EIP+0x11>
Code;  c0201289 <usb_unlink_urb+1e/39>
   a:   8b 40 20                  mov    0x20(%eax),%eax
Code;  c020128c <usb_unlink_urb+21/39>
   d:   85 c0                     test   %eax,%eax
Code;  c020128e <usb_unlink_urb+23/39>
   f:   75 09                     jne    1a <_EIP+0x1a>
Code;  c0201290 <usb_unlink_urb+25/39>
  11:   b8 ed ff 00 00            mov    $0xffed,%eax


1 error issued.  Results may not be reliable.

[-- Attachment #3: kern.log.gz --]
[-- Type: application/octet-stream, Size: 29040 bytes --]

[-- Attachment #4: config.gz --]
[-- Type: application/octet-stream, Size: 6096 bytes --]

  parent reply	other threads:[~2003-10-11 19:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11  3:30 2.6.0-test5 " Greg Norris
2003-09-11  4:46 ` Greg KH
2003-09-12 21:20   ` Cliff White
2003-10-11 19:35 ` Greg Norris [this message]
2003-10-23  2:43   ` 2.6.0-test7 " Greg Norris
     [not found] <3F60B4AB.7060109@kmlinux.fjfi.cvut.cz>
2003-09-11 17:57 ` Re: 2.6.0-test5 " Greg KH
2003-09-11 22:32   ` Greg Norris
2003-09-18  4:09     ` Greg KH
2003-09-19  1:39       ` Greg Norris

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=20031011193558.GA1404@glitch.localdomain \
    --to=haphazard@kc.rr.com \
    --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

all inboxes | Powered by JetHome®