From: Harm Verhagen <h.verhagen@chello.nl>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops on booting 2.4.4
Date: Fri, 25 May 2001 01:14:41 +0200 [thread overview]
Message-ID: <3B0D95E1.518EB8B7@chello.nl> (raw)
In-Reply-To: <mailman.990573660.4187.linux-kernel2news@redhat.com> <200105230307.f4N378P19951@devserv.devel.redhat.com>
Pete Zaitcev wrote:
> > May 23 02:46:24 localhost kernel: Process kudzu (pid: 219,
> > stackpage=c7845000)
> > May 23 02:46:24 localhost kernel: Stack: c12607e0 00000400 00000400
> > c73aa000 c122a060 c122a05c c122a058 c88fbb20
> > May 23 02:46:24 localhost kernel: 000003f1 000003f1 c014ab80
> > c73aa3f1 c7845f9c 00000000 00000400 ffffffea
> > May 23 02:46:24 localhost kernel: c7f43f60 00000400 bffff4b8
> > c7f2e220 c12607e0 00000000 00000000 c73aa000
> > May 23 02:46:24 localhost kernel: Call Trace: [<c88fbb20>]
> > [proc_file_read+184/464] [sys_read+142/196] [system_call+51/56]
> > May 23 02:46:24 localhost kernel: Call Trace: [<c88fbb20>] [<c014ab80>]
> > [<c012e83e>] [<c0106aeb>]
>
> A module deregistered incorrectly, or has a race between
> post-load activities and unload. One way or another it left
> a dangling proc entry.
>
> The oops does not provide off-stack information, so it's impossible
> to tell what particular modules is the culprit.
>
> > May 23 02:46:24 localhost kernel: hub.c: USB new device connect on
> > bus1/2, assigned device number 2
> > May 23 02:46:24 localhost kernel: usb.c: USB device 2 (vend/prod
> > 0x4a9/0x2204) is not claimed by any active driver.
>
> What is this thing you have on USB? Try to run without it.
>
> -- Pete
It's a canon usb scanner.
running with or without it does not make any difference.
kind regards,
Harm
next prev parent reply other threads:[~2001-05-24 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.990573660.4187.linux-kernel2news@redhat.com>
2001-05-23 3:07 ` Oops on booting 2.4.4 Pete Zaitcev
2001-05-24 23:14 ` Harm Verhagen [this message]
2001-05-23 1:20 Harm Verhagen
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=3B0D95E1.518EB8B7@chello.nl \
--to=h.verhagen@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.