public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Tim Waugh <twaugh@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Gigabit Ethernet support for forcedeth
Date: Fri, 30 Jul 2004 19:29:44 +0200	[thread overview]
Message-ID: <410A8588.6020208@colorfullife.com> (raw)
In-Reply-To: <20040730171606.GE8175@redhat.com>

Tim Waugh wrote:

>On Fri, Jul 30, 2004 at 06:52:15PM +0200, Manfred Spraul wrote:
>
>  
>
>>The log is very odd - why are there two lines with
>>
>>    
>>
>>>forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.28.
>>>      
>>>
>>Did you rmmod/insmod the driver twice?
>>    
>>
>
>I think it's just the way that ifup works.  I'm not entirely sure why
>the line appears twice.
>
>  
>
>>Could you manually insmod the driver, wait for two seconds and then call 
>>ifup?
>>    
>>
>
>Aha.  That works fine.
>
>So here is how to make it fail:
>
>/sbin/modprobe forcedeth; \
>/sbin/ip link set dev eth0 up
>
>All subsequent runs of 'ethtool eth0' show:
>
>Settings for eth0:
>        Supports Wake-on: g
>        Wake-on: d
>        Link detected: no
>
>regardless of how long I leave it.
>
>So is this a driver problem or a problem with the way /sbin/ifup
>works?
>
>  
>
Driver problem.
The driver assumes that the nic generates an NVREG_IRQ_LINK interrupt 
with NvRegMIIStatus & NVREG_MIISTAT_LINKCHANGE on a link change. It 
seems your nic doesn't generate that.

Could you try modprobe forcedeth;sleep 5;ip link set dev eth0 up. Then 
pull out the network cable and check if the driver noticed that with 
ethtool. Plug in back in and check again. With dprintk enabled. Then 
send me the kernel log and the ethtool output.

And add the lspci -vxx -s 00:05.0. Probably I'll make the timer 
dependant on nForce 1-3 and exclude the nForce 3 Gb nics: they don't 
need it.

--
    Manfred

  reply	other threads:[~2004-07-30 17:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 10:04 [PATCH] Gigabit Ethernet support for forcedeth Tim Waugh
     [not found] ` <410A4A1C.4040608@colorfullife.com>
2004-07-30 16:20   ` Tim Waugh
2004-07-30 16:52     ` Manfred Spraul
2004-07-30 17:16       ` Tim Waugh
2004-07-30 17:29         ` Manfred Spraul [this message]
2004-08-02 11:51           ` Tim Waugh
  -- strict thread matches above, loose matches on Subject: below --
2004-06-30  5:44 Manfred Spraul
2004-06-30  6:10 ` Jeff Garzik
2004-06-30 16:11   ` Manfred Spraul
2004-06-30 18:55     ` Manfred Spraul
2004-07-02 15:51       ` Jeff Garzik
2004-07-02 19:29         ` Manfred Spraul
2004-07-03  6:17           ` Jeff Garzik
2004-07-04 18:27 ` Pavel Machek

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=410A8588.6020208@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=twaugh@redhat.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