mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vincent Touquet <vincent.touquet@pandora.be>
To: Vincent Touquet <vincent.touquet@pandora.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Bug report] System lockups on Tyan S2469 and lots of io [smp boot time problems too :(]
Date: Tue, 8 Jul 2003 23:16:22 +0200	[thread overview]
Message-ID: <20030708211621.GB17673@ns.mine.dnsalias.org> (raw)
In-Reply-To: <20030707124747.GF7233@ns.mine.dnsalias.org>

Another way to lockup the system:
dd if=/dev/zero of=/array/file bs=1024k count=10000

So now I didn't even use any code that came near ide
(unless you take into account swapping ?)

The process ends again in a hangup:
Jul  8 22:54:55 kalimero kernel: 3w-xxxx: scsi0: AEN drain failed,
retrying.
Jul  8 22:54:55 kalimero kernel: 3w-xxxx: scsi0: Controller errors, card
not responding, check all cabling.
Jul  8 22:54:55 kalimero kernel: 3w-xxxx: scsi0: Reset sequence failed.
Jul  8 22:54:55 kalimero kernel: 3w-xxxx: scsi0: Unit #0: Command
(f7c1cc00) timed out, resetting card.

Some interesting bits in the traces show the scsi being in a limbo:
Jul  8 22:54:55 kalimero kernel: kupdated      D 00000046  5052     7
1             8     6 (L-TLB)
Jul  8 22:54:55 kalimero kernel: Call Trace:
[call_reschedule_interrupt+5/11] [__down+192/352] [__down_failed+11/20]
[.text.lock.super+279/518] [sync_old_buffers+102/336]
Jul  8 22:54:55 kalimero kernel:   [kupdate+418/480] [kupdate+0/480]
[arch_kernel_thread+46/64] [kupdate+0/480]
Jul  8 22:54:55 kalimero kernel: scsi_eh_0     R F7C64080  5760     8
1             9     7 (L-TLB)
Jul  8 22:54:55 kalimero kernel: Call Trace:
[tw_scsi_eh_abort+504/768] [scsi_try_to_abort_command+136/208]
[__down_interruptible+373/416]
[scsi_unjam_host+2045/2672] [scsi_error_handler+376/608]
Jul  8 22:54:55 kalimero kernel:   [arch_kernel_thread+46/64]
[scsi_error_handler+0/608]

And of course the dd process is in state 'D'...

I should start browsing the sources for these scsi_* functions.

I would really like to know if I'm looking at a software or a hardware
issue here.

best regards,

Vincent

  reply	other threads:[~2003-07-08 20:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-06 21:02 Vincent Touquet
2003-07-07  0:30 ` Vincent Touquet
2003-07-07  0:52   ` Andrew Morton
2003-07-07  1:08     ` Vincent Touquet
2003-07-07  0:54   ` Vincent Touquet
2003-07-07  2:19     ` Andrew Morton
2003-07-07  8:32       ` Vincent Touquet
2003-07-07 11:43       ` joe briggs
2003-07-07 11:08         ` Vincent Touquet
2003-07-07 12:47 ` Vincent Touquet
2003-07-08 21:16   ` Vincent Touquet [this message]
2003-07-07 16:14 ` Vincent Touquet
2003-07-07 16:15   ` Vincent Touquet
2003-07-07 16:48     ` Vincent Touquet
2003-07-08 10:19 ` Vincent Touquet
2003-07-08 13:59   ` joe briggs
2003-07-08 13:10     ` Vincent Touquet
2003-07-08 16:14 ` Vincent Touquet
2003-07-08 16:41   ` Vojtech Pavlik
2003-07-08 16:51     ` Vincent Touquet

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=20030708211621.GB17673@ns.mine.dnsalias.org \
    --to=vincent.touquet@pandora.be \
    --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®