linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: root@mauve.demon.co.uk
To: greg@kroah.com (Greg KH)
Cc: root@mauve.demon.co.uk, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test2 pegasus USB ethernet system lockup.
Date: Tue, 5 Aug 2003 20:46:22 +0100 (BST)	[thread overview]
Message-ID: <200308051946.UAA24947@mauve.demon.co.uk> (raw)
In-Reply-To: <20030803041144.GA18501@kroah.com> from "Greg KH" at Aug 02, 2003 09:11:44 PM

> 
> On Sun, Aug 03, 2003 at 01:22:07AM +0100, root@mauve.demon.co.uk wrote:
> > Occasionally I also get 
> > Aug  1 01:47:37 mauve kernel: Debug: sleeping function called from invalid context at drivers/usb/core/hcd.c:1350
> 
> This is fixed in Linus's tree.
> 
> > I am unable to say if lights are flashing on the keyboard, as there are 
> > no lights on the keyboard.
> 
> Can you use a serial debug console and/or the nmi watchdog to see if you
> can capture where things went wrong?


I have not gotten any results from nmi watchdog (unable to get it working)
or serial console (I have found that the kernel has stopped responding to
DMA requests, as a sound playing at the time just loops at the size of the
DMA buffer).

However, I have found another way to trigger it.
Simply 
rmmod pegasus
while there is a configured interface on it, will cause the exact same
symptoms.

I intend to try various kernel versions when I can.


      parent reply	other threads:[~2003-08-05 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-03  0:22 2.6.0-test2 pegasus USB ethernet system lockup root
2003-08-03  4:11 ` Greg KH
2003-08-03 13:58   ` root
2003-08-03 16:30     ` root
2003-08-05 19:46   ` root [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=200308051946.UAA24947@mauve.demon.co.uk \
    --to=root@mauve.demon.co.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).