public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Bonilla <abonilla@linuxwireless.org>
To: Lars Roland <lroland@gmail.com>
Cc: Christian Kujau <evil@g-house.de>,
	Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: tg3 in 2.6.12-rc6 and Cisco PIX SMTP fixup
Date: Thu, 16 Jun 2005 19:26:45 -0500	[thread overview]
Message-ID: <42B218C5.9020406@linuxwireless.org> (raw)
In-Reply-To: <4ad99e0505061617052f427ed6@mail.gmail.com>

Lars Roland wrote:

>On 6/17/05, Christian Kujau <evil@g-house.de> wrote:
>  
>
>>Lars Roland schrieb:
>>    
>>
>>>It does not seams to be limited to braodcom cards. 3com and Intel e100
>>>cards does the exact same stunt on kernels never than 2.6.8.1. Intel
>>>e1000 and realtek 8139 cards do however work.
>>>      
>>>
>>hm - tricky, i think. because no kernel oopses, nothing to look at in the
>>syslog (yes?),
>>    
>>
>
>Nothing anywhere, even tcpdump just seams to get cut off - I have not
>been debugging ethernet drivers for years, getting a little rusty at
>that, so nothing there yet.
>
>  
>
>>various nic drivers affected, others not...in cases like
>>these only Documentation/BUG-HUNTING comes to my mind: if 2.6.8.1 works,
>>and 2.6.12-rc6 does not, we'll need to find out the kernelversion which
>>introduced this behaviour.
>>    
>>
>
>That I can give you, kernel 2.6.8.1 works but 2.6.9 does not (at least
>not with tg3 and tulip cards).
>
>
>Regards.
>
>Lars Roland
>
>  
>
one question,

    Can I know what is the problem? I have 2 tg3 adapters, lots of 
e100's and some Cisco PIX and devices.

I can try to reproduce it and see if anyone has something to say about it.

Let me know,

.Alejandro

  reply	other threads:[~2005-06-17  1:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16 12:45 tg3 in 2.6.12-rc6 and Cisco PIX SMTP fixup Lars Roland
2005-06-16 21:57 ` Christian Kujau
2005-06-16 21:59   ` David S. Miller
2005-06-16 22:41     ` Jesper Juhl
2005-06-16 22:46       ` David S. Miller
2005-06-16 22:14   ` Lars Roland
2005-06-16 23:54     ` Christian Kujau
2005-06-17  0:05       ` Lars Roland
2005-06-17  0:26         ` Alejandro Bonilla [this message]
2005-06-17  1:47           ` Lars Roland
2005-06-17  1:22             ` Alejandro Bonilla
2005-06-17 13:06             ` Valdis.Kletnieks
2005-06-17 13:18               ` Lars Roland
2005-06-17 13:33                 ` Alejandro Bonilla
2005-06-17 13:40                   ` Lars Roland
2005-06-17 14:03                     ` Alejandro Bonilla
2005-06-17 13:52                   ` Valdis.Kletnieks
2005-06-17 22:50                     ` Lincoln Dale
2005-06-18  5:29                       ` Lars Roland
2005-06-18 23:22                         ` Alejandro Bonilla
2005-06-19 13:16                           ` Lars Roland
2005-06-17 13:55                   ` Valdis.Kletnieks
2005-06-17  4:46         ` Willy Tarreau
2005-06-17 12:45           ` Lars Roland

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=42B218C5.9020406@linuxwireless.org \
    --to=abonilla@linuxwireless.org \
    --cc=evil@g-house.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lroland@gmail.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