no battery)
>> and see if things act the same?
>>
>>
>>
>>
>> -Original Message-
>> From: Mark Bidewell [mailto:mbide...@gmail.com]
>> Sent: Thursday, November 08, 2012 11:25 AM
>> To: Duyck, Alexander H
>> Cc: e1000-devel@lists.sourceforge
l Message-
> From: Mark Bidewell [mailto:mbide...@gmail.com]
> Sent: Thursday, November 08, 2012 11:25 AM
> To: Duyck, Alexander H
> Cc: e1000-devel@lists.sourceforge.net; Ronciak, John
> Subject: Re: [E1000-devel] Possible Bug in e1000e driver
>
> Thanks I will give that a try.
@lists.sourceforge.net; Ronciak, John
Subject: Re: [E1000-devel] Possible Bug in e1000e driver
Thanks I will give that a try. I forgot to mention that e1000e does not
appear to fail to load. In the failure case, e1000e is still listed in
lsmod as a loaded module.
On Thu, Nov 8, 2012 at 2:17 PM
Thanks, I will try your driver change as soon as I can.
On Thu, Nov 8, 2012 at 2:30 PM, Alexander Duyck wrote:
> That is kind of what I figured. I am assuming that there is an error
> returned during e1000_probe that is causing the device to not show up as
> a network device.
>
> Thanks,
>
> A
That is kind of what I figured. I am assuming that there is an error
returned during e1000_probe that is causing the device to not show up as
a network device.
Thanks,
Alex
On 11/08/2012 11:25 AM, Mark Bidewell wrote:
> Thanks I will give that a try. I forgot to mention that e1000e does
> not
Thanks I will give that a try. I forgot to mention that e1000e does not
appear to fail to load. In the failure case, e1000e is still listed in
lsmod as a loaded module.
On Thu, Nov 8, 2012 at 2:17 PM, Alexander Duyck wrote:
> Looking over the code it looks like there is only one spot where th
Looking over the code it looks like there is only one spot where the
driver could be failing without displaying some sort of error message.
That would be at the register_netdev call.
If you look in the netdev.c file you should be able to find a tag named
"err_register:". It would greatly help wi
Yes, In the working case the log looks like:
Nov 3 12:26:00 cbidewell-desktop kernel: [1.400831] e1000e
:00:19.0: >irq 46 for MSI/MSI-X
Nov 3 12:26:00 cbidewell-desktop kernel: [1.705990] e1000e
:00:19.0: >eth0: (PCI Express:2.5GT/s:Width x1) 00:1c:c0:60:ee:1e
Nov 3 12:26:00 cb
Are you sure this is the failure case? I ask since it seems like the
e1000e is claiming the device and assigning it irq 47 for use with MSI
based on the snippet from the log below. I would have expected to see
an error stating that it failed to load the driver on the interface.
Thanks,
Alex
On
Thanks. Here is the logging in the failure case:
[1.139788] e1000e: Intel(R) PRO/1000 Network Driver - 2.0.0-k
[1.139791] e1000e: Copyright(c) 1999 - 2012 Intel Corporation.
[1.139828] e1000e :00:19.0: >setting latency timer to 64
[1.139899] e1000e :00:19.0: >Interrupt Thr
rs,
>> John
>>
>>
>>> -Original Message-
>>> From: Mark Bidewell [mailto:mbide...@gmail.com]
>>> Sent: Thursday, November 08, 2012 5:35 AM
>>> To: e1000-devel@lists.sourceforge.net
>>> Subject: [E1000-devel] Possible Bug in e1000e dr
k Bidewell [mailto:mbide...@gmail.com]
Sent: Thursday, November 08, 2012 8:29 AM
To: Ronciak, John
Cc: e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] Possible Bug in e1000e driver
Thank you, that is what I suspect but since it worked up until recently, I
thought it would be good to check.
hursday, November 08, 2012 5:35 AM
> > To: e1000-devel@lists.sourceforge.net
> > Subject: [E1000-devel] Possible Bug in e1000e driver
> >
> > My apologies if this is the wrong mailing list for this question, but
> > recently the 82566DC-2 NIC on my Intel DP35DP main
Thursday, November 08, 2012 5:35 AM
> To: e1000-devel@lists.sourceforge.net
> Subject: [E1000-devel] Possible Bug in e1000e driver
>
> My apologies if this is the wrong mailing list for this question, but
> recently the 82566DC-2 NIC on my Intel DP35DP mainboard stopped being
> re
My apologies if this is the wrong mailing list for this question, but
recently the 82566DC-2 NIC on my Intel DP35DP mainboard stopped being
recognized by linux (Ubuntu 12.04/12.10) although the card is still visible
in lspci. e1000e tries to load but does not bring up the card The issue
was at l
15 matches
Mail list logo
