From: "Glenn C. Hofmann" <ghofmann@pair.com>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3C905b partial lockup in 2.4.5-pre5 and up to 2.4.6-pre1
Date: Sun, 10 Jun 2001 00:08:50 -0500 [thread overview]
Message-ID: <3B22BA92.11992.4CE351@localhost> (raw)
In-Reply-To: <3B22CEF9.6DEB1A66@uow.edu.au>
Andrew,
Although I don't run
Redhat, your response
tells me that, even though I
was feeling that it was a
kernel problem, it could be
a userspace issue, which I
also suspected. Debian
updated their nettools
today, so I will see if that
helps in any way. Thanks
for your help. If you think
of anything else that might
be an issue, please let me
know.
Glenn C. Hofmann
Andrew wrote:
Date sent: Sun, 10 Jun 2001 11:35:53 +1000
From: Andrew Morton <andrewm@uow.edu.au>
Subject: Re: 3C905b partial lockup in 2.4.5-pre5 and up to 2.4.6-pre1
To: hofmang@ibm.net
Copies to: linux-kernel@vger.kernel.org
> "Glenn C. Hofmann" wrote:
> >
> > I have tried 2.4.5-pre2 up to 2.4.6-pre1 with the same results.
> > Everything boots great and I can login fine. When I try to assign
> > an IP via DHCP or ifconfig, the system sits and stares at me
> > indefinitely. 2.4.5-pre4 didn't compile for me, but pre3 works fine
> > and pre5 locks. There is keyboard response, and Alt-SysRq will tell
> > me that it knows I want it to sync the disks, but won't actually do
> > it. It will reboot, though. I can switch between terminals, but
> > cannot type anything at the login prompt.
> >
> > The board is a Abit KT7-RAID. I have waited to see if this issue
> > has been resolved and will recompile the newer kernels (AC and Linus
> > flavours) to see if it has cleared up, but wanted to see if maybe
> > there is something else I should look at. I can provide any more
> > information that might help, so please let me know. Thanks in
> > advance.
>
> There's a problem in some versions of `pump' where it gets
> confused and ends up spinning indefinitely. If you're using
> pump could you please try the latest RPM?
>
> If that doesn't help, and if you're unable to kill pump
> with ^C, and if other virtual consoles are not responding then
> it could be a kernel problem - try hitting sysrq-T and feeding
> the resulting logs through `ksymoops -m System.map'
> -
> 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/
next prev parent reply other threads:[~2001-06-10 5:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-09 17:45 3C905b partial lockup in 2.4.5-pre5 and up to 2.4.6-pre1 Glenn C. Hofmann
2001-06-10 1:35 ` Andrew Morton
2001-06-10 4:56 ` Glenn C. Hofmann
2001-06-10 5:08 ` Glenn C. Hofmann [this message]
2001-06-10 5:54 ` Ben LaHaise
2001-06-10 8:38 ` Russell King
2001-06-10 9:39 ` arjan
2001-06-10 16:06 ` Ben LaHaise
2001-06-10 16:34 ` Russell King
2001-06-10 16:47 ` Jeff Garzik
2001-06-10 22:23 ` Ben LaHaise
2001-06-11 0:53 ` David S. Miller
2001-06-11 13:03 ` Andrew Morton
2001-06-11 13:27 ` David S. Miller
2001-06-11 13:49 ` Jeff Garzik
2001-06-11 14:21 ` Andrew Morton
2001-06-11 16:05 ` Jeff Garzik
2001-06-11 3:17 ` Glenn C. Hofmann
2001-06-11 3:25 ` Jeff Garzik
2001-06-12 3:17 ` Glenn C. Hofmann
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=3B22BA92.11992.4CE351@localhost \
--to=ghofmann@pair.com \
--cc=andrewm@uow.edu.au \
--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