public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <safemode@comcast.net>
To: Ed Sweetman <safemode@comcast.net>
Cc: Pierre Ossman <drzeus-list@drzeus.cx>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	LKML <linux-kernel@vger.kernel.org>,
	jgarzik@pobox.com
Subject: Re: 2.6.12 breaks 8139cp
Date: Fri, 24 Jun 2005 22:18:41 -0400	[thread overview]
Message-ID: <42BCBF01.206@comcast.net> (raw)
In-Reply-To: <42BCBB60.7000508@comcast.net>

this is in the changefile to 2.6.11.   This seems to be the real 
culprit.  I guarantee you if this patch is reverted, there will be no 
problems.

<romieu@fr.zoreil.com>
	[PATCH] r8169: hint for Tx flow control
	
	return 1 in start_xmit() when the required descriptors are not available
	and wait for more room.
	
	Signed-off-by: Francois Romieu <romieu@fr.zoreil.com>




Ed Sweetman wrote:

> Pierre Ossman wrote:
>
>> Bjorn Helgaas wrote:
>>
>>  
>>
>>> Your 2.6.11 dmesg mentions the VIA IRQ fixup, but the 2.6.12 one
>>> doesn't.  I bet something's broken there.
>>>
>>> Can you try the attached debugging patch?  And please collect the
>>> output of lspci, too.
>>>
>>>
>>>   
>>
>>
>> I tried the attached patch and it had no effect. I also tried porting
>> the 2.6.11 way of handling the VIA quirk but it didn't have any effect.
>> I'll try a more complete port tomorrow (it was a bit of a hack this 
>> time).
>>
>>  
>>
> 2.6.11-mm4 doesn't work. So i'm guessing 2.6.11 wont work either which 
> may be why backporting it's via fixes didn't do anything.  I'm gonna 
> try vanilla and if that by some crazy chance works, then it'll be 
> fairly easy to see what change did it since mm has a nice Changelog.
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


  reply	other threads:[~2005-06-25  2:19 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-22 21:03 2.6.12 breaks 8139cp Pierre Ossman
2005-06-22 21:34 ` Bjorn Helgaas
2005-06-23  7:50   ` Pierre Ossman
2005-06-23 12:59     ` Felipe W Damasio
2005-06-23 17:43     ` Bjorn Helgaas
2005-06-23 22:14       ` Pierre Ossman
2005-06-25  2:03         ` Ed Sweetman
2005-06-25  2:18           ` Ed Sweetman [this message]
2005-06-25  2:32             ` Ed Sweetman
2005-06-25  3:15               ` Jeff Garzik
2005-06-25 10:34           ` Pierre Ossman
2005-06-26 13:31             ` Ed Sweetman
2005-06-28  6:28         ` Pierre Ossman
2005-06-28 12:32           ` Pierre Ossman
2005-06-28 14:09             ` Kylene Jo Hall
2005-06-28 14:40               ` Pierre Ossman
2005-06-28 15:08                 ` Kylene Jo Hall
2005-06-28 16:51                   ` Pierre Ossman
2005-06-28 17:03                     ` Kylene Jo Hall
2005-06-29  7:03                       ` Pierre Ossman
2005-06-28 17:23                   ` Chris Wright
2005-06-28 20:29                     ` 2.6.12 breaks 8139cp [PATCH 1 of 2] Kylene Jo Hall
2005-06-28 20:34                       ` Chris Wright
2005-06-28 22:10                         ` Kylene Jo Hall
2005-06-29  8:22                           ` Pierre Ossman
2005-06-29 14:32                             ` Kylene Jo Hall
     [not found]                               ` <20050705153512.GJ9046@shell0.pdx.osdl.net>
2005-07-07 20:01                                 ` Kylene Jo Hall
2005-07-08  6:14                                   ` Chris Wright
2005-06-28 20:30                     ` 2.6.12 breaks 8139cp [PATCH 2 " Kylene Jo Hall
2005-06-23 17:17 ` 2.6.12 breaks 8139cp Roberto Oppedisano
2005-06-23 18:00   ` Bjorn Helgaas
2005-06-23 20:38     ` Ed Sweetman
2005-06-23 20:55       ` Bjorn Helgaas
2005-06-23 21:14         ` Ed Sweetman
2005-06-23 21:07     ` Roberto Oppedisano
  -- strict thread matches above, loose matches on Subject: below --
2005-06-26 13:46 Nick Warne

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=42BCBF01.206@comcast.net \
    --to=safemode@comcast.net \
    --cc=bjorn.helgaas@hp.com \
    --cc=drzeus-list@drzeus.cx \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    /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