From: emf <i@mindlace.net>
To: emf <i@mindlace.net>
Cc: linux-kernel@vger.kernel.org, c-d.hailfinger.kernel.2004@gmx.net
Subject: Re: segfaults, kernel panic using forcedeth nvidia 4
Date: Mon, 28 Aug 2006 16:49:07 -0400 [thread overview]
Message-ID: <44F356C3.3040806@mindlace.net> (raw)
In-Reply-To: <44F06BB0.4090200@mindlace.net>
OK, I've got some oops output... if someone could give me the faintest
idea as to what is wrong, I would be much obliged.
http://mindlace.net/tmp/latest_segfault.txt
emf wrote:
> Hello!
>
> I'm using debian's 2.6.17-2-amd64 (after having these issues with 2.6.16).
>
> I'm running software raid 5 and LVM on the partition in question; the
> machine is connected to my server via gigabit ethernet over the onboard
> nforce4 ethernet- my motherboard is Gigabyte GA-M51GM-S2G Socket AM2
> NVIDIA GeForce 6100, and the CPU is a AMD Sempron 64 2800+.
>
> When I try to rsync from my old server, I get user-land segfaults (bash
> and sh, mostly) and the machine hangs. This happens with straight scp as
> well, and it is 100% replicable. The error messages look like:
>
> sh[5325]: segfault at 0000000081cc893a rip 00002ae181c2bf02 rsp
> 00007fffff927c58 error 4
>
> I've now successfully tried copying a large number of files via a
> machine connected through a 100mbit connection, without issue.
>
> This leads me to think that it's forcedeth having the problem, but I had
> also thought that perhaps I'm asking too much of the md/lvm subsystem.
>
> I've ordered another gigabit ethernet card and a new AMD64x2 cpu, so I
> should be able to test these issues more cleanly.
>
> In the meantime, is there anything I can do to diagnose these issues?
>
> Thanks (and please cc me; I'm not a kernel-type by default.)
>
> ~ethan fremen
>
prev parent reply other threads:[~2006-08-28 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-26 15:41 segfaults, kernel panic using forcedeth nvidia 4 emf
2006-08-28 20:49 ` emf [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=44F356C3.3040806@mindlace.net \
--to=i@mindlace.net \
--cc=c-d.hailfinger.kernel.2004@gmx.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