mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Kris Karas <ktk@enterprise.bidmc.harvard.edu>
Cc: linux-usb-devel@lists.sourceforge.net,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19pre2++ USB EHCI-HCD -> auto-reboot
Date: Sun, 21 Apr 2002 19:43:10 -0700	[thread overview]
Message-ID: <109b01c1e9a7$71ada460$6800000a@brownell.org> (raw)

> I need some tips on how to debug (or help others debug) a problem
> I am seeing with the EHCI-HCD driver introduced in 2.4.19-pre2.

Hmm ... that "auto-reboot" has to stop before you can get
much of anywhere!  I've not seen that kind of failure since
ehci-hcd was first starting to enumerate devices.

I'd hope that running against 2.5.8 (which has a somewhat
more current EHCI driver in any case), with lots of kernel
debugging features (notably slab debugging, which also
poisons the pci_pool memory used by the USB HCDs),
would give you a more friendly failure mode.  Basically
the same stuff exists on 2.4.19-pre, but you will need
to tweak the PCIPOOL_DEBUG stuff in drivers/pci/pci.c
to make the extra poisoning happen.  KDB can help too.

Once a few more tidbits of info become available, I can
help figure out what's up.  (To be honest, it's been quite a
while since anyone has reported anything but success with
ehci-hcd.  Some variety is perversely refreshing ... :)

- Dave




             reply	other threads:[~2002-04-22  2:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-22  2:43 David Brownell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-21 23:49 Kris Karas
2002-04-22  1:41 ` Greg KH

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='109b01c1e9a7$71ada460$6800000a@brownell.org' \
    --to=david-b@pacbell.net \
    --cc=ktk@enterprise.bidmc.harvard.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®