All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Horton <phorton@bitbox.co.uk>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp>, linux-mips@linux-mips.org
Subject: Re: Tulip driver broken on Cobalt RaQ1 in 2.6
Date: Fri, 24 Aug 2007 10:04:03 +0100	[thread overview]
Message-ID: <46CE9F03.7040207@bitbox.co.uk> (raw)
In-Reply-To: <20070824080215.GA31646@deprecation.cyrius.com>

Martin Michlmayr wrote:
> * Yoichi Yuasa <yoichi_yuasa@tripeaks.co.jp> [2007-08-24 13:36]:
>> What error occurs on Raq1?
> 
> There is no error, but I never get a DHCP response:
> 
> Listening on LPF/eth0/00:10:e0:00:27:5c
> Sending on   LPF/eth0/00:10:e0:00:27:5c
> Sending on   Socket/fallback/fallback-net
> DHCPREQUEST on eth0 to 255.255.255.255 port 67
> eth0: Setting full-duplex based on MII#1 link partner capability of 45e1.
> DHCPREQUEST on eth0 to 255.255.255.255 port 67
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 17
> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
> No DHCPOFFERS received.
> 

What does /proc/interrupts show after this ?

Does the networking work in CoLo ?

The "PCI retry count" thing is a red herring. There's no device at 06.0 
so that's why you get the message. The kernel used to explicitly skip 
this device when PCI retries were disabled otherwise it would hang. When 
I enabled the PCI retry counter there was no need to skip it, you just 
get the debug.

P.

  reply	other threads:[~2007-08-24  9:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23 20:37 Tulip driver broken on Cobalt RaQ1 in 2.6 Martin Michlmayr
2007-08-24  3:22 ` Markus Gothe
2007-08-24  4:36 ` Yoichi Yuasa
2007-08-24  8:02   ` Martin Michlmayr
2007-08-24  9:04     ` Peter Horton [this message]
2007-08-24 11:24       ` Martin Michlmayr

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=46CE9F03.7040207@bitbox.co.uk \
    --to=phorton@bitbox.co.uk \
    --cc=linux-mips@linux-mips.org \
    --cc=tbm@cyrius.com \
    --cc=yoichi_yuasa@tripeaks.co.jp \
    /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.