mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Winn Johnston <winn_johnston@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: BUG: soft lockup detected on CPU#0!
Date: Fri, 12 May 2006 08:51:07 -0700 (PDT)	[thread overview]
Message-ID: <20060512155107.20047.qmail@web52903.mail.yahoo.com> (raw)
In-Reply-To: <20060511180320.49788.qmail@web52901.mail.yahoo.com>

I noticed another post the other day, and contacted
the indavidual who posted it. note his message below.

Hi Winn,
Latest news i had was a *hint* from Andrew Morton
telling me to try with kernel 2.6.17-rc3 and report if
the problem was gone or not. I've had no 
time to give it a try yet.Your problem seems similar
to mine, a few person argued that the message 
was bogus and that no harm was done but i guess they
did not read carefully the post since the consequences
are pretty bad.
Let me know if you manage to try with the latest rc of
the 2.6.17 kernel and if things are better.

ref:
http://groups.google.com/group/linux.kernel/browse_thread/thread/450966ffa3043609/59e6a2350b7690bf?lnk=st&q=kernel%3A+ide%3A+failed+opcode+was%3A+0xea%22+BUG%3A+soft+lockup+detected+on+CPU%230!%22&rnum=1&hl=en#59e6a2350b7690bf

--- Winn Johnston <winn_johnston@yahoo.com> wrote:

> Error:
> 
> kernel: hdi: drive_cmd: status=0xd0 { Busy }
> kernel: ide: failed opcode was: 0xea
> BUG: soft lockup detected on CPU#0!
> 
> the odd thing is the system experiences a hard
> lockup,
> so it is not a false positive. I am working on a
> trace, but it is hard to get.
> 
> My supervisor has asked me to help research this
> problem. We are using multiple ata cards in our
> backup
> machine. We have a Promiss sata 300tx4, and three
> ATA
> cards (3 SIG UltraATA 133 PCI) or (3 promise ultra
> 100tx2). We are experiencing hard lockups. The
> system
> resides on a scsi drive connected to the on board
> controler Adaptec AIC-7899P (Tyan S2462
> motherboard)the error is repeated for all drives
> connected to the promis cards, and the error
> continues
> until a lock up is eventualy reached.
> 
> Also, its in dma mode, not pio.
> PREEMPT_NONE is already set, so its not the
> preemption
> model
> 
> possibly related posts
>
http://www.ussg.iu.edu/hypermail/linux/kernel/0309.1/0444.html
> 
>
http://groups.google.com/group/linux.kernel/browse_thread/thread/450966ffa3043609/59e6a2350b7690bf?lnk=st&q=kernel%3A+ide%3A+failed+opcode+was%3A+0xea%22+BUG%3A+soft+lockup+detected+on+CPU%230!%22&rnum=1&hl=en#59e6a2350b7690bf
> 
> 
> 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam
> protection around 
> http://mail.yahoo.com 
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at 
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

  reply	other threads:[~2006-05-12 15:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11  2:25 Linux 2.6.16.16 Chris Wright
2006-05-11  2:29 ` Chris Wright
2006-05-11 10:34 ` Maciej Soltysiak
2006-05-11 11:07   ` Nick Warne
2006-05-11 16:50   ` Daniel Barkalow
2006-05-11 17:33   ` Chris Wright
2006-05-11 18:03     ` BUG: soft lockup detected on CPU#0! Winn Johnston
2006-05-12 15:51       ` Winn Johnston [this message]
2006-05-13 15:35     ` Linux 2.6.16.16 Ingo Oeser
2006-05-13 15:56       ` Adrian Bunk
2006-05-13 17:29         ` Nick Warne
2006-05-14  3:59           ` Greg KH
2006-05-14  5:17             ` Willy Tarreau
2006-05-15 17:57               ` Chris Wright
2006-05-14  7:46             ` Maciej Soltysiak
2006-05-15 16:30               ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
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
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-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=20060512155107.20047.qmail@web52903.mail.yahoo.com \
    --to=winn_johnston@yahoo.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

all inboxes | Powered by JetHome®