linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karel Kulhavy <clock@atrey.karlin.mff.cuni.cz>
To: linux-kernel@vger.kernel.org
Subject: Hangup on nforce2 UDMA
Date: Tue, 12 Aug 2003 11:10:56 +0200	[thread overview]
Message-ID: <20030812091056.GA13487@atrey.karlin.mff.cuni.cz> (raw)

Hello

Could you please try if your nforce2 MCP southbridge is also possible
to be crashed the way I describe lower?

I have nforce2 motherboard Soltek SL75FRN2-L with MCP southbridge. Using
2.4.21 with AMD 74xx driver for IDE. If I leave the UDMA5 (UATA-100)
setting BIOS leaves on the IDE disk I can hangup the machine almost
deterministically with

cat /dev/hda > /dev/null 

performed just after hard reset and subsequent boot. It hangs after max.
a minute or so. If it doesn't work, try hard reset and again, then
putting this script into /root/crash:

( a=0; while true; do echo $a; a=`/usr/bin/expr $a + 1`; sleep 1; done ) &
cat /dev/hda > /dev/null

then adding this into your lilo.conf:

image=/boot/vmlinuz
        label=crash
        append="init=/bin/bash /root/crash"
        read-only

and finally lilo -D crash and reboot and hard reset. Repeat several
times if the crash doesn't occur on the first try.

keyboard lights don't work, alt-sysrq-b doesn't work, power off doesn't
work. Reset works. I tried NMI watchog but both with nmi_watchdog=1 and
nmi_watchdog=2 I get NMI 14 or 15 in /proc/interrupts and it doesn't
increment in 5 second intervals. Without nmi_watchdog I get NMI 0 in
/proc/interrupts. Enabling NMI watchdog and waiting 5 seconds after the
crash does nothing.

When UDMA is disabled in BIOS, I get lower performance of 17MB/s instead
of 40MB/s. I have also tried IGNORE word93 Validation BITS and AMD Viper
ATA-66 Override and none helped.

Cl<

             reply	other threads:[~2003-08-12  9:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-12  9:10 Karel Kulhavy [this message]
2003-08-12 15:42 ` Hangup on nforce2 UDMA zipa24

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=20030812091056.GA13487@atrey.karlin.mff.cuni.cz \
    --to=clock@atrey.karlin.mff.cuni.cz \
    --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;
as well as URLs for NNTP newsgroup(s).