public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Leonard N. Zubkoff" <lnz@dandelion.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: DAC960 on IA/64
Date: Tue, 24 Jul 2001 14:59:03 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005897@msgid-missing> (raw)

  Date: Tue, 24 Jul 2001 14:58:14 +0200 (CEST)
  From: Martin Wilck <Martin.Wilck@fujitsu-siemens.com>

  Hi Leonard,

  I have made a very small step forward in debugging the problems.
  After reading this message from Linux to the LK mailinglist
  <http://www.uwsg.indiana.edu/hypermail/linux/kernel/0107.2/0533.html>
  I suspected that SMP may have something to do with it.

  So I repeated our test with the stock RedHat UP kernel (2.4.3),
  and with much less catastrophic results. I got no more hanging
  processes, no system crash, "just" some data errors that suggest
  that 18 512-byte blocks in a 2GB file were pointing at a wrong disk
  area (there were valid bit patterns there, but patterns that should
  appear elsewhere in the file).

  This may look like a VFS or ext2-related problem, but similar tests
  on other controllers have revealed nothing of the kind.

  Interestingly, the driver also reported
  no "vendor-specific" or other errors during the test.

  I cannot exclude 100% that this test went better than the previous
  tests simply by "luck", but it seems unlikely, because the system
  survived 12 hours of heavy copy-compare whereas it always showed
  uninterruptibly sleeping processes or even total crashes after
  ca. 5 hours with SMP.

  Hope that helps a bit, regards,
  Martin

Hmmm.  That's certainly a possibility, though I don't fully undertand yet the
form of the failure.  I posted a patch for Linux kernel 2.4.7 on my web page
last night that updates the 2.4.10 DAC960 driver to use the new completion
code.  Please try 2.4.7 with that patch and see if it works in UP or SMP.

		Leonard


                 reply	other threads:[~2001-07-24 14:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=marc-linux-ia64-105590693005897@msgid-missing \
    --to=lnz@dandelion.com \
    --cc=linux-ia64@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