From: Dave Olien <dmo@osdl.org>
To: ccantwel@uci.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: DAC960 and latest kernels
Date: Wed, 17 Nov 2004 13:29:48 -0800 [thread overview]
Message-ID: <20041117212948.GA2154@osdl.org> (raw)
In-Reply-To: <20041117192018.GA25403@zee.ps.uci.edu>
I'll look into this. I'll see if I can reproduce any of these
problems locally and get back to you.
Dave
On Wed, Nov 17, 2004 at 11:20:18AM -0800, ccantwel@uci.edu wrote:
> It seems that I have found a very serious bug relating to the DAC960
> driver, it is present in 2.4.27 and 2.6.8.1 but I haven't tried any
> development kernels newer than that. This message is meant to inform
> the people who may be able to figure out what the problem is and
> repair the bug. If anyone wants to respond to me or has further
> information on this problem, please cc me directly, as I am not a
> member of this mailing list.
>
> There is a bug in latest released kernels for both 2.4 and 2.6
> trees that seems to relate to the DAC960 driver. I have tried
> 2.4.27 and 2.6.8.1 and both have the following problem. After
> replacing and testing every piece of hardware I've determined
> the problem is in the kernel and not the machine. Also, going
> back to kernel 2.4.17 makes everything work perfectly.
>
> When copying a large number of files over the network using nc
> and tar and also stress testing on the receiving side with
> frequent du commands where the data is being written to (not
> required for the problem but it seems to make it more likely
> to happen) the machine randomly hangs. Sometimes it crashes
> completely with an Unable to handle kernel paging request at
> virtual address, with various processes, and sometimes it just
> completely halts and responds to nothing even though it seems
> to sort of be running (answers on sockets but transfers no data,
> no more communication of any kind on other open sockets, entering
> a login name and enter on the console also hangs before the
> password prompt.
>
> Upon rebooting the filesystem that was being written to is corrupt.
> When this file system is XFS I can still inspect it. If it is
> reiser the machine will often hang trying to run fsck.reiserfs.
>
> In addition, after enough network tar copying I can stop the process,
> and even if it has not hung the machine often the filesystem has
> become corrupt. Since this happens with both xfs and reiser and
> there are paging problems too I believe it has to relate to the
> dac960 driver itself.
>
> I've also tried swapping DAC960 cards, and that doesn't matter,
> they both work perfectly in 2.4.17 and the problems occur in
> both cases in 2.4.27 and 2.6.8.1. I'm planning to try some
> more kernels in between to narrow down when the problem was
> introduced but I'm not a kernel developer and that is about the
> most I will be able to do.
>
> I think the DAC960 driver isn't used very often and also without this
> specific type of stress testing it is hard to realize the problem is
> occuring before the filesystem is irreperably corrupt weeks down the
> road, which is why this problem may have not been found yet. Without
> stress testing using tar the machine can go for weeks and act like it
> is fine.
>
> Again, if anyone has any information, please cc me when you reply as
> I am not a member of this list.
>
> Thank you
> -
> 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/
prev parent reply other threads:[~2004-11-17 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-17 19:20 DAC960 and latest kernels ccantwel
2004-11-17 21:29 ` Dave Olien [this message]
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=20041117212948.GA2154@osdl.org \
--to=dmo@osdl.org \
--cc=ccantwel@uci.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.