Re: OHCI patch - please test [was Re: USB issues with Apollo KT133A mobo]
On Thu, Dec 12, 2002 at 07:27:07PM -0500, Brian F. Feldman wrote: > Josef Karthauser <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > If you're an ohci user can you please test this patch out for inclusion > > in 5.0. I need to know that it doesn't break anything - the reports are > > that it fixes broken ohci :). > > For what it's worth, it doesn't fix the umass(4) crashing issue. Anyone > wanna trade their uhci-based PCI USB adapter for an ohci based USB 2.0 > adapter? Which umass crashing issue? -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: OHCI patch - please test [was Re: USB issues with Apollo KT133A mobo]
Josef Karthauser <[EMAIL PROTECTED]> wrote: > Hi all, > > If you're an ohci user can you please test this patch out for inclusion > in 5.0. I need to know that it doesn't break anything - the reports are > that it fixes broken ohci :). For what it's worth, it doesn't fix the umass(4) crashing issue. Anyone wanna trade their uhci-based PCI USB adapter for an ohci based USB 2.0 adapter? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
OHCI patch - please test [was Re: USB issues with Apollo KT133A mobo]
Hi all,
If you're an ohci user can you please test this patch out for inclusion
in 5.0. I need to know that it doesn't break anything - the reports are
that it fixes broken ohci :).
Joe
--
Josef Karthauser ([EMAIL PROTECTED]) http://www.josef-k.net/
FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/
Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/
An eclectic mix of fact and theory. =
Index: ohci.c
===
RCS file: /home/ncvs/src/sys/dev/usb/ohci.c,v
retrieving revision 1.113
diff -u -r1.113 ohci.c
--- ohci.c 30 Sep 2002 17:50:16 - 1.113
+++ ohci.c 1 Dec 2002 21:04:36 -
@@ -1810,7 +1810,7 @@
SPLUSBCHECK;
/* XXX */
- for (p = head; p == NULL && p->next != sed; p = p->next)
+ for (p = head; p != NULL && p->next != sed; p = p->next)
;
if (p == NULL)
panic("ohci_rem_ed: ED not found\n");
msg48225/pgp0.pgp
Description: PGP signature
Re: USB issues with Apollo KT133A mobo
On Fri, 2002-12-06 at 10:04, Darryl Okahata wrote: > > I have motherboards where this fix doesn't work :( > > You have tried -current, right? (I assume that you have, but I > just want to make sure.) Cliff mentioned that -current works for him, > but 4.7 doesn't. Hmm, no.. It wasn't really an option at the time.. Now I've replaced the boards with other ones which work fine. > I haven't searched the archives very hard, but I could only find a > reference to the "VIA patch" being applied to -current (Soren's post > of around December 26, 2001). I haven't tried rummaging through the CVS > logs. I've always assumed that the VIA patch was MFC'd, but I can't any > verification of this. It was MFC'd - I ended up hand MFC'ing it to try out, but it wasn't successful :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB issues with Apollo KT133A mobo
"Daniel O'Connor" <[EMAIL PROTECTED]> wrote: > > Many (most? all?) KT133A-based motherboards have a known issue with > > the PCI bus that often results in an IDE transfer problem. However, > > this was fixed (IIRC) in FreeBSD around the 4.5/4.6 timeframe (maybe > > earlier). [ Hmmm. You're probably seeing another problem with 4.7. ] > > I have motherboards where this fix doesn't work :( You have tried -current, right? (I assume that you have, but I just want to make sure.) Cliff mentioned that -current works for him, but 4.7 doesn't. I haven't searched the archives very hard, but I could only find a reference to the "VIA patch" being applied to -current (Soren's post of around December 26, 2001). I haven't tried rummaging through the CVS logs. I've always assumed that the VIA patch was MFC'd, but I can't any verification of this. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB issues with Apollo KT133A mobo
On Fri, 2002-12-06 at 02:48, Darryl Okahata wrote: > > a rock under 5.0-DP2, which is why I'm sticking with it despite other > > potential bugs. I can burn CDs now! > > Many (most? all?) KT133A-based motherboards have a known issue with > the PCI bus that often results in an IDE transfer problem. However, > this was fixed (IIRC) in FreeBSD around the 4.5/4.6 timeframe (maybe > earlier). [ Hmmm. You're probably seeing another problem with 4.7. ] I have motherboards where this fix doesn't work :( According to the board vendor you're supposed to use the latest Via drivers (ahahaha..) Tinkering with various PCI and AGP options (eg turning features off) makes it more stable, but they still hang :( I have other KT133 based boards which work flawlessly because the BIOS does the fix. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB issues with Apollo KT133A mobo
"Cliff L. Biffle" <[EMAIL PROTECTED]> wrote: > Could be. The ATA controller was also flaking out under 4.7, but is solid as > a rock under 5.0-DP2, which is why I'm sticking with it despite other > potential bugs. I can burn CDs now! Many (most? all?) KT133A-based motherboards have a known issue with the PCI bus that often results in an IDE transfer problem. However, this was fixed (IIRC) in FreeBSD around the 4.5/4.6 timeframe (maybe earlier). [ Hmmm. You're probably seeing another problem with 4.7. ] > In the discussion link you sent me, they discuss the controller disabling the > port due to excessive current draw...would it re-enable the port when I > simply un/replug the mouse? Normally I'd expect that to require a reboot. > (The mouse does come back when I remove it and reinsert it, and generally X > doesn't even notice.) I don't know how FreeBSD handles it. Under Windows, a dialog box pops up when an overcurrent situation occurs, and the box contains a button that'll reset and re-enable the bus. > The KT133 discussion suggests it's a hardware problem, which wouldn't surprise > me...this particular mobo is a very early Athlon board, and the chipset may > be buggy. Motherboards using the VIA KT133A chipset generally do not have a good reputation. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB issues with Apollo KT133A mobo
On Wednesday 04 December 2002 05:40 pm, Josef Karthauser wrote: > Is it ohci? If so can you try this patch? > > Joe Hey Joe -- fancy meeting you here. :-) Nope, the KT133 has two UHCI controllers. What I'm going to do next (which I should have done before) is try the following variables: 1. Does the mouse die if it's the only thing plugged in AND is buffered by a powered hub? (iirc, yes, but needs testing) 2. Does the secondary controller work? (The ports stub out in a header on the board, but I've brought them out and will test.) If (1) is true, that (imho) eliminates the current-draw question. If (2) is true, that points to hardware problems with the primary controller. (Forgot I had two. *grin*) -Cliff L. Biffle To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB issues with Apollo KT133A mobo
On Wednesday 04 December 2002 05:11 pm, Darryl Okahata wrote: > 1. IIRC, USB ports on KT133A motherboards were buggy (???). Could be. The ATA controller was also flaking out under 4.7, but is solid as a rock under 5.0-DP2, which is why I'm sticking with it despite other potential bugs. I can burn CDs now! > 2. Drawing too much power from the USB ports can cause the ports to shut >down. The absolute maximum limit is 500mA, which isn't much (some >2.5" USB hard disks can draw MUCH more, which violates the spec, and >sometimes works, and sometimes doesn't). The behavior persists with just an optical USB mouse, which can't possibly be sucking more than a few dozen mills. (I hope.) In the discussion link you sent me, they discuss the controller disabling the port due to excessive current draw...would it re-enable the port when I simply un/replug the mouse? Normally I'd expect that to require a reboot. (The mouse does come back when I remove it and reinsert it, and generally X doesn't even notice.) The KT133 discussion suggests it's a hardware problem, which wouldn't surprise me...this particular mobo is a very early Athlon board, and the chipset may be buggy. -Cliff L. Biffle To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: USB issues with Apollo KT133A mobo
On Wed, Dec 04, 2002 at 04:00:15PM -0700, Cliff L. Biffle wrote:
> Hi all.
> I'm running 5.0-DP2 on a motherboard with the Apollo KT133A chipset. (I
> believe it's an ASUS, but it doesn't seem to be labelled.) The USB
> controller (described by dmesg as a VIA 83C572) periodically blows its brains
> out.
>
Is it ohci? If so can you try this patch?
Joe
--
Josef Karthauser ([EMAIL PROTECTED]) http://www.josef-k.net/
FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/
Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/
An eclectic mix of fact and theory. =
Index: ohci.c
===
RCS file: /home/ncvs/src/sys/dev/usb/ohci.c,v
retrieving revision 1.113
diff -u -r1.113 ohci.c
--- ohci.c 30 Sep 2002 17:50:16 - 1.113
+++ ohci.c 1 Dec 2002 21:04:36 -
@@ -1810,7 +1810,7 @@
SPLUSBCHECK;
/* XXX */
- for (p = head; p == NULL && p->next != sed; p = p->next)
+ for (p = head; p != NULL && p->next != sed; p = p->next)
;
if (p == NULL)
panic("ohci_rem_ed: ED not found\n");
msg48114/pgp0.pgp
Description: PGP signature
Re: USB issues with Apollo KT133A mobo
"Cliff L. Biffle" <[EMAIL PROTECTED]> wrote: > More specifically, all USB devices lose power. The device nodes stay in /dev > and there are no notices to dmesg about the loss until I unplug and replug > them, at which time it says 'port error: restarting port N' where N is > generally 0, depending on which controller it is. It then redetects my > hardware. 1. IIRC, USB ports on KT133A motherboards were buggy (???). 2. Drawing too much power from the USB ports can cause the ports to shut down. The absolute maximum limit is 500mA, which isn't much (some 2.5" USB hard disks can draw MUCH more, which violates the spec, and sometimes works, and sometimes doesn't). Here's another discussion on this: http://groups.google.com/groups?hl=en&lr=lang_en&ie=UTF-8&threadm=ajedc5%24bej%241%40paris.btinternet.com&rnum=1 -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
USB issues with Apollo KT133A mobo
Hi all. I'm running 5.0-DP2 on a motherboard with the Apollo KT133A chipset. (I believe it's an ASUS, but it doesn't seem to be labelled.) The USB controller (described by dmesg as a VIA 83C572) periodically blows its brains out. More specifically, all USB devices lose power. The device nodes stay in /dev and there are no notices to dmesg about the loss until I unplug and replug them, at which time it says 'port error: restarting port N' where N is generally 0, depending on which controller it is. It then redetects my hardware. This also happened on 4.5 and above, so it might very well be a hardware problem on my end. Since I'm not getting any helpful error messages from my system, my question is this: what debugging switches, if any, should I turn on to see what's going on? Are there any known issues with this controller? Should I just sup to -current? Thanks! -Cliff L. Biffle To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
