From: Christoph Pfister <christophpfister@gmail.com>
To: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: soft lockup detected on CPU#0!
Date: Tue, 7 Aug 2007 10:49:23 +0200 [thread overview]
Message-ID: <200708071049.23226.christophpfister@gmail.com> (raw)
In-Reply-To: <19a3b7a80707271304g231860b8g690a32b12cac5835@mail.gmail.com>
Hi Michal,
Am Freitag, 27. Juli 2007 22:04 schrieb Christoph Pfister:
> Hi Michal,
>
> 2007/7/27, Michal Piotrowski <michal.k.k.piotrowski@gmail.com>:
> > Hi Christoph,
> >
> > On 25/07/07, Christoph Pfister <christophpfister@gmail.com> wrote:
> > > Hi,
> > >
> > > After burning a dvd I had to eject it and found that message in dmesg.
> > > Syslog snippet and dmesg attached.
> > > System is 2.6.21 (debian version), running a p4, issue reproducible.
> >
> > Does this happen on the latest -stable?
> > http://eu.kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.1.tar.bz2
Doesn't happen there anymore.
> I'm on holiday really soon - but will try when I'm back :)
>
> > > Thanks for taking care of this,
> > >
> > > Christoph
> >
> > Regards,
> > Michal
>
> Christoph
Thanks,
Christoph
next prev parent reply other threads:[~2007-08-07 8:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 19:41 BUG: soft lockup detected on CPU#0! Christoph Pfister
2007-07-27 19:30 ` Michal Piotrowski
2007-07-27 20:04 ` Christoph Pfister
2007-08-07 8:49 ` Christoph Pfister [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-14 11:19 CIJOML
2007-05-09 12:41 Ralf Hildebrandt
2006-06-02 1:02 Marc Koschewski
2006-06-02 1:04 ` Marc Koschewski
2006-06-02 1:54 ` Andrew Morton
2006-05-11 17:33 Linux 2.6.16.16 Chris Wright
2006-05-11 18:03 ` BUG: soft lockup detected on CPU#0! Winn Johnston
2006-05-12 15:51 ` Winn Johnston
2006-03-05 12:26 Norbert Wegener
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=200708071049.23226.christophpfister@gmail.com \
--to=christophpfister@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
/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