All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Mark Lord <lkml@rtr.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	marcel@holtmann.org
Subject: Re: [BUG] usb/core/hub.c loops forever on resume from ram due to bluetooth
Date: Sun, 13 May 2007 02:27:01 -0700	[thread overview]
Message-ID: <20070513092701.GD11249@suse.de> (raw)
In-Reply-To: <464080C1.6010105@rtr.ca>

On Tue, May 08, 2007 at 09:53:05AM -0400, Mark Lord wrote:
>  Greg ?
> 
>  The oddball thing here is that on a UP machine with a UP kernel,
>  this (below) was never an issue.
> 
>  After moving the drive to a dual-core machine and rebuilding
>  the kernel with SMP=y, the problem becomes a killer here.
>  The two machines are nearly identical, apart from the CPUs.
> 
>  The failing machine is a Dell Inspiron 9400,
>  and mine isn't the only unit that has this issue.

Ok, I'll take a patch to keep the loop from going forever, but the main
issue here is that there is probably a hardware failure somewhere.

Care to resend the patch with proper formatting?

thanks,

greg k-h

  reply	other threads:[~2007-05-14  1:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 23:28 [BUG] usb/core/hub.c loops forever on resume from ram due to bluetooth Mark Lord
2007-05-02 19:59 ` [linux-usb-devel] " Alan Stern
2007-05-02 21:39   ` Mark Lord
2007-05-03 13:33     ` Alan Stern
2007-05-03 13:44       ` Mark Lord
2007-05-03 14:46         ` Alan Stern
2007-05-08 13:53 ` Mark Lord
2007-05-13  9:27   ` Greg KH [this message]
2007-05-14 23:48     ` Mark Lord
2007-05-22 23:53       ` patch usb-hub.c-loops-forever-on-resume-from-ram-due-to-bluetooth.patch added to gregkh-2.6 tree gregkh

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=20070513092701.GD11249@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=marcel@holtmann.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 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.