From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "R. J. Wysocki" <rjwysocki@sisk.pl>,
ak@muc.de, linux-kernel@vger.kernel.org
Subject: Re: 2.6.6-mm2(-mm1,-bk1): SMP bug on dual AMD64
Date: Fri, 14 May 2004 16:17:12 -0700 [thread overview]
Message-ID: <20040514231712.GA18108@kroah.com> (raw)
In-Reply-To: <20040514160524.57dd9de4.akpm@osdl.org>
On Fri, May 14, 2004 at 04:05:24PM -0700, Andrew Morton wrote:
> "R. J. Wysocki" <rjwysocki@sisk.pl> wrote:
> >
> > I've just compiled the 2.6.6-mm2 kernel (with gcc-3.4) and tried to run it.
> > Well, it generally works, but there seems to be an SMP bug that may be
> > triggered with the help of a USB storage device (please see the attached
> > log). The device works fine in spite of it, though.
> >
> > This bug seems to be present in the 2.6.6-mm1 and 2.6.6-bk1, but it is not
> > present in the 2.6.6, apparently.
> >
> > My system is a dual Opteron and I use an add-on USB 2.0 card based on the NEC
> > chipset (the .config is attached).
>
> The WARN_ON() backtrace is unrelated to USB - it is due to SCSI calling
> vmalloc/vfree with interrupts disabled. People are working on that.
>
> As for this:
>
> May 14 23:57:09 chimera kernel: usb usb2: string descriptor 0 read error: -108
> May 14 23:57:09 chimera last message repeated 2 times
>
> It has been reported before and I assume people are working it, but it
> would be nice to have confirmation of that...
It should be fixed in the patches I just sent to Linus.
thanks,
greg k-h
prev parent reply other threads:[~2004-05-14 23:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 22:22 2.6.6-mm2(-mm1,-bk1): SMP bug on dual AMD64 R. J. Wysocki
2004-05-14 23:05 ` Andrew Morton
2004-05-14 23:17 ` Greg KH [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=20040514231712.GA18108@kroah.com \
--to=greg@kroah.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjwysocki@sisk.pl \
/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