mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Giglio <jgiglio@vt.edu>
To: linux-kernel@vger.kernel.org
Cc: bradlist@bradm.net
Subject: 3ware 7810 and Tyan 2462 Tiger MP lockup
Date: Fri, 3 May 2002 19:08:09 -0400	[thread overview]
Message-ID: <20020503190809.7cb8c052.jgiglio@vt.edu> (raw)

Bradley McLean had posted a while back (3/30/02) about problems with 3ware 7810 cards and Tyan Tiger MP.  He had indicated that updating his drivers and changing a PCI riser card around fixed the problem.

I have recently encountered the problem with the newest drivers and no PCI riser cards.  It only seems to happen when using XFS, and when directly accessing the 3ware card through /dev/sda.  The symptoms are the same, hard lockup, no ping, no nothing, during heavy I/O. An added twist is that the file system is very corrupt upon rebooting.

I have sent a message to the XFS list, but I thought I'd drop a note in here that the problem is still persisting, since it is not likely a problem in XFS proper that is causing the initial lockup, considering that others had the problem with any file system previously.  It was suggested by Alan Cox that this may be an APIC issue, it happened for me with or without noapic specified.

Please CC me on replies to list.  

Thanks,
Jason

>From: Bradley McLean (bradlist@bradm.net)
>Subject: Hard hang on 3Ware7850, Dual AthlonMP, Tyan2462

>I've been following the various discussions of athlon MP problems. We too have systems that consistently hard lock up.
>Running RH7.2 with kernel.org kernels, versions 2.4.17, 2.4.18,
>or 2.4.18 plus the IO-APIC patch posted for 2.4.19pre3.
>Using the latest (release 7.4, driver version 19) 3ware code. Tyan 2462, 3.5 GB
>(2) AMD MP1900+
>(6) WB1200JB Symptoms:  Either under heavy read, or heavy write, system locks up.  No ping, no keyboard.

             reply	other threads:[~2002-05-03 23:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03 23:08 Jason Giglio [this message]
2002-05-03 23:47 ` Jeff V. Merkey

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=20020503190809.7cb8c052.jgiglio@vt.edu \
    --to=jgiglio@vt.edu \
    --cc=bradlist@bradm.net \
    --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®