netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	netdev@vger.kernel.org, akpm@linux-foundation.org,
	David Gundersen <gundy@iinet.net.au>,
	Edward Hsu <edward_hsu@realtek.com.tw>,
	Sylvain Le Gall <sylvain@le-gall.net>,
	Roel.Teuwen@advalvas.be
Subject: Re: Pull request for 'r8169-for-jeff-20070919' branch
Date: Thu, 20 Sep 2007 17:26:40 -0400	[thread overview]
Message-ID: <46F2E590.1070704@redhat.com> (raw)
In-Reply-To: <20070920204437.GB13512@electric-eye.fr.zoreil.com>

On 09/20/2007 04:44 PM, Francois Romieu wrote:
> Chuck Ebbert <cebbert@redhat.com> :
> [...]
>> People are still reporting hangs with this card in 2.6.22.6, are there
>> any fixes appropriate for that?
> 
> $ grep 2.6.22.6 ~/Mail/linux/bugs/pending
> $ grep 2.6.22.6 ~/Mail/romieu
> [nothing besides Sylvain's success with 2.6.22.6 + the r8169 test driver]
> $ less +/2.6.22.6 ~/Mail/linux/netdev/200709 
> [nada]
> $ less +/816[89] ~/Mail/linux/kernel/200737
> [...]
> 
> /me scratches head...
> 
> The answer is probably "not yet".
> 
> Can you refresh my memory with some #BZ or an url ?
> 

Looking again, it may not be r8169's fault, but it is involved. It
used to hang and could be restarted by pulling the cable and reinserting
it, but now it just locks solid:

https://bugzilla.redhat.com/show_bug.cgi?id=252955

Will ask the reporter to test with a different adapter.


  reply	other threads:[~2007-09-20 21:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-19 19:56 Pull request for 'r8169-for-jeff-20070919' branch Francois Romieu
2007-09-20 20:04 ` Chuck Ebbert
2007-09-20 20:44   ` Francois Romieu
2007-09-20 21:26     ` Chuck Ebbert [this message]
2007-09-20 22:16       ` Sylvain Le Gall
2007-09-21  7:08       ` Francois Romieu

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=46F2E590.1070704@redhat.com \
    --to=cebbert@redhat.com \
    --cc=Roel.Teuwen@advalvas.be \
    --cc=akpm@linux-foundation.org \
    --cc=edward_hsu@realtek.com.tw \
    --cc=gundy@iinet.net.au \
    --cc=jeff@garzik.org \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    --cc=sylvain@le-gall.net \
    /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;
as well as URLs for NNTP newsgroup(s).