From: Johannes Erdfelt <johannes@erdfelt.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Ketil Froyn <ketil@froyn.com>, linux-kernel@vger.kernel.org
Subject: Re: oops in uhci.c running 2.4.2-ac28
Date: Mon, 2 Apr 2001 19:05:42 -0400 [thread overview]
Message-ID: <20010402190541.F17651@sventech.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0104010313440.1135-100000@ns.froyn.org> <20010402185526.A4083@devserv.devel.redhat.com>
In-Reply-To: <20010402185526.A4083@devserv.devel.redhat.com>; from Pete Zaitcev on Mon, Apr 02, 2001 at 06:55:26PM -0400
On Mon, Apr 02, 2001, Pete Zaitcev <zaitcev@redhat.com> wrote:
> > Date: Sun, 1 Apr 2001 03:35:03 +0200 (CEST)
> > From: Ketil Froyn <ketil@froyn.com>
> > To: <linux-kernel@vger.kernel.org>
>
> > While running kernel 2.4.2-ac28, I switched on spinlock debugging and
> > verbose BUG() reporting (I always use sysrq). Anyway, while running this I
> > got an oops after about 2 or 3 minutes running, several times, exact same
> > place each time, which I traced back to rh_int_timer_do().
> > This was in uhci.c (I used CONFIG_USB_UHCI_ALT). [...] I
> > recompiled with usb-uhci.c instead (CONFIG_USB_UHCI), and now I don't get
> > the oops any more.
>
> I am behind usb-uhci for a reason. Alan bounced your report
> to me but I do not see a case for action...
What do you mean by "behind".
Have you tried the latest patches for uhci.c?
JE
prev parent reply other threads:[~2001-04-02 23:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-01 1:35 oops in uhci.c running 2.4.2-ac28 Ketil Froyn
2001-04-02 22:55 ` Pete Zaitcev
2001-04-02 22:31 ` Jeff Golds
2001-04-02 23:50 ` Johannes Erdfelt
2001-04-02 23:16 ` Jeff Golds
2001-04-03 7:59 ` Erik Oomen
2001-04-02 23:05 ` Johannes Erdfelt [this message]
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=20010402190541.F17651@sventech.com \
--to=johannes@erdfelt.com \
--cc=ketil@froyn.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox