From: fauxpas@temp123.org
To: Mikael Pettersson <mikpe@user.it.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IOAPIC on Via KT266a
Date: Sat, 1 Mar 2003 12:22:51 -0500 [thread overview]
Message-ID: <20030301172251.GA30143@temp123.org> (raw)
In-Reply-To: <15967.28629.35699.473056@gargle.gargle.HOWL>
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
On Fri, Feb 28, 2003 at 03:19:01PM +0100, Mikael Pettersson wrote:
> This is almost certainly a hardware problem: your machine's APIC bus
> is corrupting messages, or some other agent than the CPU is creating
> corrupt messages. This isn't exactly unheard of for non-Intel chipsets.
Hmmm... windows seems to have a workaround for at least part of the
problem, I spent the last day trying to confuse the APIC unsuccessfully
on that system. Could it be a problem with the uhci driver perhaps?
The only two persistant symptoms are the usb failure and the slew of
messages.
The APIC errors I receive are mostly 02(02) but a good deal of
02(01), 01(02) and 01(01). Checksum errors galore.
This only happens with IO-APIC is enabled throughout:
hub.c: new USB device 00:11.2-1, assigned address 2
usb_control/bulk_msg: timeout
usb.c: USB device not accepting new address=2 (error=-110)
hub.c: new USB device 00:11.2-1, assigned address 3
b.c: USB device not accepting new address=3 (error=-110)
hub.c: new USB device 00:11.2-2, assigned address 4
usb_control/bulk_msg: timeout
usb.c: USB device not accepting new address=4 (error=-110)
hub.c: new USB device 00:11.2-2, assigned address 5
usb_control/bulk_msg: timeout
usb.c: USB device not accepting new address=5 (error=-110)
--
Josh Litherland (fauxpas@temp123.org)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-03-01 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 16:52 IOAPIC on Via KT266a fauxpas
2003-02-28 14:19 ` Mikael Pettersson
2003-03-01 17:22 ` fauxpas [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=20030301172251.GA30143@temp123.org \
--to=fauxpas@temp123.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@user.it.uu.se \
/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.