From: Francois Romieu <romieu@fr.zoreil.com>
To: Hans-Frieder Vogt <hfvogt@arcor.de>
Cc: linux-kernel@vger.kernel.org, jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: 2.6.9-rc1-bk11+ and 2.6.9-rc1-mm3,4 r8169: freeze during boot (FIX included)
Date: Tue, 14 Sep 2004 00:02:09 +0200 [thread overview]
Message-ID: <20040913220209.GA13175@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <200409131443.34374.hfvogt@arcor.de>
Hans-Frieder Vogt <hfvogt@arcor.de> :
[...]
> no oops (BUG_ON not triggered)! System boots up as normal, but just after I
...
> log in on the console the system freezes, i.e., keyboard does not react any
> more and the system is not accessible via network.
- do the keyboard leds or the magic sysrq answer (I assume you boot without X) ?
- does it make a difference if you boot with the network cable unpluged (i.e.
fine until pluged then dead when first packet comes in) ?
> The time from the moment I log in to the time when the system freezes varies,
> but is in the order of 5s.
First packet probably. Can you verify this point ?
> There is no difference whether NAPI is enabled or not.
I will welcome lspci -vx + gcc version + objdump -S of the r8169 module.
--
Ueimor
next prev parent reply other threads:[~2004-09-13 22:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-12 22:35 Hans-Frieder Vogt
2004-09-12 23:26 ` Francois Romieu
2004-09-13 12:43 ` Hans-Frieder Vogt
2004-09-13 22:02 ` Francois Romieu [this message]
2004-09-13 23:31 ` Hans-Frieder Vogt
2004-09-15 22:40 ` Hans-Frieder Vogt
2004-09-15 23:09 ` Francois Romieu
2004-09-15 23:32 ` Hans-Frieder Vogt
2004-09-16 7:02 ` Francois Romieu
2004-09-16 18:20 ` Jon Mason
2004-09-17 15:43 ` Jon Mason
2004-09-17 16:01 ` Francois Romieu
2004-09-19 21:17 ` Andy Lutomirski
2004-09-19 21:39 ` Francois Romieu
2004-09-19 23:51 ` Andy Lutomirski
2004-09-20 2:56 ` Jeff Garzik
2004-09-20 7:17 ` Francois Romieu
2004-09-20 17:59 ` Jeff Garzik
2004-09-20 21:15 ` Francois Romieu
2004-09-20 16:06 ` Jon Mason
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=20040913220209.GA13175@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=hfvogt@arcor.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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
all inboxes | Powered by JetHome®