netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: [Bugme-new] [Bug 16293] New: 82545GM in newest kernel not working.
       [not found] <bug-16293-10286@https.bugzilla.kernel.org/>
@ 2010-07-01 21:00 ` Andrew Morton
  2010-07-01 21:40   ` Tantilov, Emil S
  0 siblings, 1 reply; 3+ messages in thread
From: Andrew Morton @ 2010-07-01 21:00 UTC (permalink / raw)
  To: netdev, Jeff Kirsher, Jesse Brandeburg, Bruce Allan,
	Alex Duyck <alexander.h.duyck
  Cc: bugzilla-daemon, bugme-daemon, lukas.valach


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Fri, 25 Jun 2010 17:48:43 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=16293
> 
>            Summary: 82545GM in newest kernel not working.
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 2.6.32.15
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: high
>           Priority: P1
>          Component: Network
>         AssignedTo: drivers_network@kernel-bugs.osdl.org
>         ReportedBy: lukas.valach@zoznam.sk
>         Regression: No
> 
> 
> lspci:
> 
> 01:01.0 Ethernet controller: Intel Corporation 82545GM Gigabit Ethernet
> Controller (rev 04)
> 01:02.0 Ethernet controller: Intel Corporation 82545GM Gigabit Ethernet
> Controller (rev 04)
> 02:01.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
> Controller (rev 03)
> 02:01.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
> Controller (rev 03)
> 
> All interface are correctly configured. In kernel <2.6.26 get all OK, in newest
> kernels network interfaces are not working. Problem is in driver e1000. Tested
> on 2.6.31,2.6.32,2.6.34 and 2.6.35rc.

A somewhat old e1000 regression?

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: [Bugme-new] [Bug 16293] New: 82545GM in newest kernel not working.
  2010-07-01 21:00 ` [Bugme-new] [Bug 16293] New: 82545GM in newest kernel not working Andrew Morton
@ 2010-07-01 21:40   ` Tantilov, Emil S
       [not found]     ` <web-435085375@be3.mail.zoznam.sk>
  0 siblings, 1 reply; 3+ messages in thread
From: Tantilov, Emil S @ 2010-07-01 21:40 UTC (permalink / raw)
  To: Andrew Morton, netdev@vger.kernel.org, Kirsher, Jeffrey T,
	"Brandeburg, Jesse" <jesse.brandeburg
  Cc: bugzilla-daemon@bugzilla.kernel.org,
	bugme-daemon@bugzilla.kernel.org, lukas.valach@zoznam.sk

Andrew Morton wrote:
> (switched to email.  Please respond via emailed reply-to-all, not via
> the bugzilla web interface).
> 
> On Fri, 25 Jun 2010 17:48:43 GMT
> bugzilla-daemon@bugzilla.kernel.org wrote:
> 
>> https://bugzilla.kernel.org/show_bug.cgi?id=16293
>> 
>>            Summary: 82545GM in newest kernel not working.           
>>            Product: Drivers Version: 2.5
>>     Kernel Version: 2.6.32.15
>>           Platform: All
>>         OS/Version: Linux
>>               Tree: Mainline
>>             Status: NEW
>>           Severity: high
>>           Priority: P1
>>          Component: Network
>>         AssignedTo: drivers_network@kernel-bugs.osdl.org
>>         ReportedBy: lukas.valach@zoznam.sk
>>         Regression: No
>> 
>> 
>> lspci:
>> 
>> 01:01.0 Ethernet controller: Intel Corporation 82545GM Gigabit
>> Ethernet Controller (rev 04) 01:02.0 Ethernet controller: Intel
>> Corporation 82545GM Gigabit Ethernet Controller (rev 04) 02:01.0
>> Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
>> Controller (rev 03) 02:01.1 Ethernet controller: Intel Corporation
>> 82546GB Gigabit Ethernet Controller (rev 03)  
>> 
>> All interface are correctly configured. In kernel <2.6.26 get all
>> OK, in newest kernels network interfaces are not working. Problem is
>> in driver e1000. Tested on 2.6.31,2.6.32,2.6.34 and 2.6.35rc.
> 
> A somewhat old e1000 regression?

I ran a quick test on net-next with 82545GM NICs and was able to pass traffic without issues.

Would it be possible to get more information about the system/setup:

1. full lspci output (lspci -vvv)
2. ethtool -i ethX
3. ethtool -d ethX
4. ethtool -e ethX
5. dmesg  - after loading the driver and configuring the interfaces
6. kernel config

A better description of the issue would help as well. What exactly fails - ping?

Thanks,
Emil

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: [Bugme-new] [Bug 16293] New: 82545GM in newest kernel not working.
       [not found]     ` <web-435085375@be3.mail.zoznam.sk>
@ 2010-07-06 21:16       ` Tantilov, Emil S
  0 siblings, 0 replies; 3+ messages in thread
From: Tantilov, Emil S @ 2010-07-06 21:16 UTC (permalink / raw)
  To: lukas.valach@zoznam.sk; +Cc: NetDev

>-----Original Message-----
>From: lukas.valach@zoznam.sk [mailto:lukas.valach@zoznam.sk]
>Sent: Tuesday, July 06, 2010 12:35 PM
>To: Tantilov, Emil S
>Subject: Re: [Bugme-new] [Bug 16293] New: 82545GM in newest kernel not
>working.
>
>Hi,
>
>ping has 100% packet loss. Link is up. Lspci --vvv is OK, when have kernel
>2.6.26.

Could you provide the information I asked in the previous email?

1. full lspci output (lspci -vvv)
2. ethtool -i ethX
3. ethtool -d ethX
4. ethtool -e ethX
5. dmesg - after loading the driver and configuring the interfaces
6. kernel config

Are you using a network adapter or is the interface on the motherboard?

Also please copy netdev to your replies.

Thanks,
Emil


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-07-06 21:16 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <bug-16293-10286@https.bugzilla.kernel.org/>
2010-07-01 21:00 ` [Bugme-new] [Bug 16293] New: 82545GM in newest kernel not working Andrew Morton
2010-07-01 21:40   ` Tantilov, Emil S
     [not found]     ` <web-435085375@be3.mail.zoznam.sk>
2010-07-06 21:16       ` Tantilov, Emil S

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).