From: Chuck Ebbert <76306.1226@compuserve.com>
To: Dave Jones <davej@redhat.com>
Cc: Greg KH <greg@kroah.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.18.5 usb/sysfs bug.
Date: Sat, 16 Dec 2006 00:47:09 -0500 [thread overview]
Message-ID: <200612160050_MC3-1-D538-EA63@compuserve.com> (raw)
In-Reply-To: <20061215213715.GB15792@redhat.com>
On Fri, 15 Dec 2006 16:37:15 -0500, Dave Jones wrote:
> > Can you enable CONFIG_USB_DEBUG and send the log info that happens right
> > before this oops?
>
> Gah, and here it is, actually attached this time.
> BUG: unable to handle kernel NULL pointer dereference at virtual address 0000000b
> EIP is at sysfs_hash_and_remove+0x18/0xfd
That's strange. Remove_files called sysfs_hash_and_remove()
with dir==0xfffffff3 (-13 decimal.)
static void remove_files(struct dentry * dir,
const struct attribute_group * grp)
{
struct attribute *const* attr;
for (attr = grp->attrs; *attr; attr++)
sysfs_hash_and_remove(dir,(*attr)->name); <========
}
> Process pcscd (pid: 2678, ti=f6d28000 task=f7dbe1f0 task.ti=f6d28000)
> Stack: c0634109 fffffff3 f7063414 c069cf0c fffffff3 fffffff3 f7063414 c04a7f69
> c069cf00 f70632b0 c04a7fb8 f7063208 f70473a0 f7063208 c055572f f70632b0
> c05513ff f7063208 f7000640 00000001 f703f788 c055142e f6d28ed4 c058800c
> Call Trace:
> [<c04a7f69>] remove_files+0x15/0x1e
> [<c04a7fb8>] sysfs_remove_group+0x46/0x5c
> [<c055572f>] device_pm_remove+0x2b/0x62
> [<c05513ff>] device_del+0x11a/0x141
> [<c055142e>] device_unregister+0x8/0x10
> [<c058800c>] usb_remove_ep_files+0x5b/0x7b
> [<c0587b82>] usb_remove_sysfs_intf_files+0x1d/0x54
> [<c0585b5c>] usb_set_interface+0x135/0x1bf
> [<c0586047>] usb_unbind_interface+0x4a/0x6a
> [<c0552a38>] __device_release_driver+0x60/0x78
> [<c0552c85>] device_release_driver+0x2b/0x3a
> [<c057e4f5>] usb_driver_release_interface+0x3b/0x63
> [<c058833d>] releaseintf+0x4b/0x5b
> [<c058ab8d>] usbdev_release+0x67/0x9e
> [<c0470402>] __fput+0xba/0x188
> [<c046dc61>] filp_close+0x52/0x59
> [<c0404013>] syscall_call+0x7/0xb
What is pcscd?
Earlier in bootup you got this:
hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0004
uhci_hcd 0000:00:1d.0: port 2 portsc 008a,00
hub 1-0:1.0: port 2, status 0100, change 0003, 12 Mb/s
usb 1-2: USB disconnect, address 2
usb 1-2: usb_disable_device nuking all URBs
uhci_hcd 0000:00:1d.0: shutdown urb f7ed7540 pipe 40408280 ep1in-intr
usb 1-2: unregistering interface 1-2:1.0
usbdev1.2_ep81: ep_device_release called for usbdev1.2_ep81
usb 1-2:1.0: uevent
usb 1-2: unregistering device
usbdev1.2_ep00: ep_device_release called for usbdev1.2_ep00
usb_remove_ep_files() is in the call trace, so this may be related?
--
MBTI: IXTP
next reply other threads:[~2006-12-16 5:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 5:47 Chuck Ebbert [this message]
2006-12-16 14:18 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2006-12-17 7:43 Chuck Ebbert
2006-12-15 17:50 Dave Jones
2006-12-15 17:53 ` Greg KH
2006-12-15 21:36 ` Dave Jones
2006-12-15 21:37 ` Dave Jones
2006-12-16 1:47 ` Pete Zaitcev
2006-12-16 3:05 ` Dave Jones
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=200612160050_MC3-1-D538-EA63@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=davej@redhat.com \
--cc=greg@kroah.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®