public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: David CHANIAL <david.ml@euro-web.fr>
Cc: linux-kernel@vger.kernel.org, romieu@fr.zoreil.com
Subject: Re: weird bug on r8169 with usb
Date: Wed, 25 Jun 2008 03:31:25 +0200	[thread overview]
Message-ID: <1214357485.701.4.camel@localhost> (raw)
In-Reply-To: <200806250031.24804.david.ml@euro-web.fr>

Added cc to a person that might have some info

On Wed, 2008-06-25 at 00:31 +0200, David CHANIAL wrote:
> Le Wednesday 25 June 2008 00:18:37 David CHANIAL, vous avez écrit :
> > # dmesg | grep eth0 # without the bug
> 
> excuse my error (copy/paste error),
> without the bug, the output is :
> 
> # dmesg | grep eth0 # without the bug
> eth0: RTL8168c/8111c at 0xf8828000, 00:1e:8c:c4:66:7d, XID 3c2000c0 IRQ 18
> r8169: eth0: link up
> r8169: eth0: link up
> eth0: no IPv6 routers present
> 
> Note that i can boot without the usb devices
> eth0 is usable, i plug usb devices and eth0 continue to be fully usable.
> the bug occur only when i boot with the usb devices.

I believe this is not actually about usb, i've had some issues too (and
still have them) - look back a few months on lkml, you will find the
thread.

btw, sorry Francois for not coming back to you, but i sortof forgot
since the noapic thing works around it.

But i can confirm that 2.6.26 doesent fix it.

This bug seems to still hit lots of people.
> 
> Best regards,

mvh.
Kasper Sandberg


  reply	other threads:[~2008-06-25  1:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 22:18 weird bug on r8169 with usb David CHANIAL
2008-06-24 22:31 ` David CHANIAL
2008-06-25  1:31   ` Kasper Sandberg [this message]
2008-06-25 18:55     ` Francois Romieu
2008-06-25 21:41       ` Kasper Sandberg
2008-06-25 18:52 ` Francois Romieu
2008-06-26  7:18   ` David CHANIAL
2008-07-08  8:29 ` David CHANIAL

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=1214357485.701.4.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=david.ml@euro-web.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=romieu@fr.zoreil.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