From: Andrew Morton <akpm@osdl.org>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: ce@ruault.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] kernel 2.6.15.4: soft lockup detected on CPU#0!
Date: Thu, 16 Feb 2006 12:20:45 -0800 [thread overview]
Message-ID: <20060216122045.7a664bc6.akpm@osdl.org> (raw)
In-Reply-To: <58cb370e0602160533n3325ba03yfedaf4e55278521d@mail.gmail.com>
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
>
> On 2/16/06, Andrew Morton <akpm@osdl.org> wrote:
> > Charles-Edouard Ruault <ce@ruault.com> wrote:
> > >
> > > i was trying to rip a CD when the whole machine started to freeze
> > > periodicaly, i then looked at the logs and found the following :
> > >
> > > Feb 12 19:23:39 ruault kernel: hdc: irq timeout: status=0x80 { Busy }
> > > Feb 12 19:23:39 ruault kernel: ide: failed opcode was: unknown
> > > Feb 12 19:23:39 ruault kernel: hdd: status timeout: status=0x80 { Busy }
> > > Feb 12 19:23:39 ruault kernel: ide: failed opcode was: unknown
> > > Feb 12 19:23:39 ruault kernel: hdd: drive not ready for command
> >
> > No idea what caused that.
> >
> > > Feb 12 19:23:39 ruault kernel: BUG: soft lockup detected on CPU#0!
> >
> > The following was merged today. Hopefully it suppresses this false
> > positive.
>
> Unfortunately it won't. Charles' problem is different (and the BUG
> output is different!) - soft lockup got triggered for PIO handling in
> ide-cd driver. This patch fixes the problem only for generic ATA PIO
> routines (disks and [P]IDENTIFY), ATAPI PIO still needs fixing
> (ide-cd/floppy/tape/scsi drivers).
argh. We do need to bop that warning on the head - it's consuming people's
time and causing unneeded concern.
> Andrew, there is no "high level" function for ATAPI PIO as
> ide_pio_datablock() for ATA PIO so fixing soft lockup false positives
> would require going through all drivers and adding bunch of
> touch_softlockup_watchdog() or using sledge-hammer approach
> and touching watchdog in ide-iops.c:atapi_[input,output]_bytes().
Send fixup patch, please?
next prev parent reply other threads:[~2006-02-16 20:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 18:50 Charles-Edouard Ruault
2006-02-14 11:41 ` Folkert van Heusden
2006-02-14 16:32 ` Lee Revell
2006-02-15 15:07 ` Folkert van Heusden
2006-02-15 18:19 ` Lee Revell
2006-02-16 1:38 ` Alan Cox
2006-02-17 22:56 ` Lee Revell
2006-02-16 2:51 ` Andrew Morton
2006-02-16 9:44 ` Charles-Edouard Ruault
2006-02-16 10:36 ` Folkert van Heusden
2006-02-16 10:46 ` Andrew Morton
2006-02-16 11:18 ` Charles-Edouard Ruault
2006-02-16 12:57 ` Alan Cox
2006-02-16 13:33 ` Bartlomiej Zolnierkiewicz
2006-02-16 20:20 ` Andrew Morton [this message]
2006-02-17 11:47 ` Bartlomiej Zolnierkiewicz
2006-02-17 13:08 ` [patch] timer-irq-driven soft-watchdog, cleanups Ingo Molnar
2006-02-17 14:46 ` Bartlomiej Zolnierkiewicz
2006-02-17 19:52 ` Ingo Molnar
2006-02-17 20:11 ` Ingo Molnar
2006-02-17 22:15 ` Bartlomiej Zolnierkiewicz
2006-03-13 14:48 ` Charles-Edouard Ruault
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=20060216122045.7a664bc6.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bzolnier@gmail.com \
--cc=ce@ruault.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
Powered by JetHome