From: Christian Kujau <evil@g-house.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Manfred Spraul <manfred@colorfullife.com>
Subject: Re: forcedeth as a module only?
Date: Sat, 18 Jun 2005 00:36:25 +0200 [thread overview]
Message-ID: <42B35069.9010202@g-house.de> (raw)
In-Reply-To: <42B34D12.70008@g-house.de>
Christian Kujau schrieb:
> Manfred Spraul schrieb:
>>
>>Could you try the attached patch? It polls for link changes instead of
>>relying on the irq. Additionally, I have enabled some debug output.
oh jolly, i think it worked!
eth0: forcedeth.c: subsystem: 01462:0250 bound to 0000:00:05.0
netconsole: device eth0 not up yet, forcing it
eth0: no link detected by phy - falling back to 10HD.
eth0: no link during initialization.
eth0: nv_update_linkspeed: PHY advertises 0x0de1, lpa 0x41e1.
eth0: changing link setting from 66536/0 to 65636/1.
eth0: link up.
netconsole: network logging started
[...]
eth0: nv_update_linkspeed: PHY advertises 0x0de1, lpa 0x41e1.
...
the last line gets repeated a couple of times, that must be the printk you
enabled.
thank you!
Christian.
(it's always stunning how a bugreport with that sparse details can lead to
a working kernel patch. cool.)
--
BOFH excuse #303:
fractal radiation jamming the backbone
next prev parent reply other threads:[~2005-06-17 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200506171804.j5HI4qoh027680@dbl.q-ag.de>
[not found] ` <42B31749.90208@g-house.de>
2005-06-17 20:47 ` forcedeth as a module only? Manfred Spraul
2005-06-17 22:22 ` Christian Kujau
2005-06-17 22:36 ` Christian Kujau [this message]
2005-06-18 10:44 ` marvin24
2005-06-18 12:53 ` Manfred Spraul
2005-06-17 17:41 Christian Kujau
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=42B35069.9010202@g-house.de \
--to=evil@g-house.de \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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 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.