All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Golds <jgolds@resilience.com>
To: Johannes Erdfelt <johannes@erdfelt.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>, Ketil Froyn <ketil@froyn.com>,
	linux-kernel@vger.kernel.org
Subject: Re: oops in uhci.c running 2.4.2-ac28
Date: Mon, 02 Apr 2001 16:16:58 -0700	[thread overview]
Message-ID: <3AC9086A.20E36D9F@resilience.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0104010313440.1135-100000@ns.froyn.org> <20010402185526.A4083@devserv.devel.redhat.com> <3AC8FDD8.4116E97@resilience.com> <20010402195048.H17651@sventech.com>

Johannes Erdfelt wrote:
> 
> On Mon, Apr 02, 2001, Jeff Golds <jgolds@resilience.com> wrote:
> > Let me show what I got with the 2.4.2 kernel with USB support enabled.
> >
> > Mar 19 14:10:00 Eng99 kernel: uhci: host controller halted. very bad
> > Mar 19 14:10:31 Eng99 last message repeated 108 times
> > Mar 19 14:11:37 Eng99 last message repeated 93 times
> > Mar 19 14:12:39 Eng99 last message repeated 87 times
> > Mar 19 14:13:40 Eng99 last message repeated 20 times
> > Mar 19 14:14:45 Eng99 last message repeated 42 times
> > Mar 19 14:15:46 Eng99 last message repeated 47 times
> > Mar 19 14:16:47 Eng99 last message repeated 127 times
> > Mar 19 14:17:50 Eng99 last message repeated 7074 times
> > Mar 19 14:18:51 Eng99 last message repeated 3342 times
> > Mar 19 14:19:52 Eng99 last message repeated 10948 times
> > Mar 19 14:20:00 Eng99 last message repeated 15
> > times
> >
> > This happens after simply fiddling around with ethernet settings (it's a
> > PCI ethernet card).  In fact, my syslog is FULL of these messages... my
> > syslog was 3x larger than usual.  The console is just about unusable
> > because of all the spam.
> >
> > Something seems terribly wrong with the uhci driver... I've disabled it
> > on my system and it's fine now (I don't need USB).
> 
> Do you get the same messages with the usb-uhci driver?
> 

Don't think I tried that one.

> > My system:
> > Slot 1 P3-850
> > VIA chipset MB (not sure of exact chipset, can find out if needed)
> 
> Some of the VIA chipsets have port aliasing problems supposedely. This
> may cause your controller to go insane like you've described.
> 
> JE
> 

That could explain the issue.  Fortunately, I don't need USB so I can
avoid the spam, I just thought someone might like to hear about it.

-Jeff

P.S.  Sorry for responding directly to you, Johannes.

-- 
Jeff Golds
jgolds@resilience.com

  reply	other threads:[~2001-04-03  0:14 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 [this message]
2001-04-03  7:59       ` Erik Oomen
2001-04-02 23:05   ` Johannes Erdfelt

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=3AC9086A.20E36D9F@resilience.com \
    --to=jgolds@resilience.com \
    --cc=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 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.