From: Maxim Levitsky <maximlevitsky@gmail.com>
To: "Allan, Bruce W" <bruce.w.allan@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: [REGRESSION] e1000e stopped working
Date: Mon, 28 Jun 2010 20:14:07 +0300 [thread overview]
Message-ID: <1277745247.12841.1.camel@localhost.localdomain> (raw)
In-Reply-To: <8DD2590731AB5D4C9DBF71A877482A90015918F40A@orsmsx509.amr.corp.intel.com>
On Mon, 2010-06-28 at 10:04 -0700, Allan, Bruce W wrote:
> On Sunday, June 27, 2010 10:47 AM, Maxim Levitsky wrote:
> > On Sun, 2010-06-27 at 20:43 +0300, Maxim Levitsky wrote:
> >> On Sun, 2010-06-27 at 20:29 +0300, Maxim Levitsky wrote:
> >>> On Sun, 2010-06-27 at 20:27 +0300, Maxim Levitsky wrote:
> >>>> Just that,
> >>>>
> >>>> It doesn't receive anything from my internet router during DHCP.
> >>>>
> >>>>
> >>>> 00:19.0 Ethernet controller [0200]: Intel Corporation 82566DC
> >>>> Gigabit Network Connection [8086:104b] (rev 02) Subsystem: Intel
> >>>> Corporation Device [8086:0001] Control: I/O+ Mem+ BusMaster+
> >>>> SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> >>>> DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
> >>>> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0
> >>>> Interrupt: pin A routed to IRQ 47 Region 0: Memory at 50300000
> >>>> (32-bit, non-prefetchable) [size=128K] Region 1: Memory at
> >>>> 50324000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports
> >>>> at 30e0 [size=32] Capabilities: [c8] Power Management version 2
> >>>> Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA
> >>>> PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0
> >>>> DScale=1 PME- Capabilities: [d0] Message Signalled Interrupts:
> >>>> Mask- 64bit+ Queue=0/0 Enable+ Address: 00000000fee0100c Data:
> >>>> 41c9 Kernel driver in use: e1000e Kernel modules: e1000e
> >>>>
> >>>> I use vanilla tree, commit bf2937695fe2330bfd8933a2310e7bdd2581dc2e
> >>>>
> >>>>
> >>>> Best regards,
> >>>> Maxim Levitsky
> >>>>
> >>>
> >>> It appears to work now after reboot.
> >>> Will keep a look for this.
> >>>
> >>> Disregard for now.
> >>
> >>
> >> Just s2ram cycle, problem is back.
> >> Did full reboot (power off then on), same thing card doesn't work...
> >>
> >
> > Yep, s2ram sometimes 'fixes', sometimes breaks the card.
> > Something got broken in device initialization path.
> >
> > Best regards,
> > Maxim Levitsky
>
> What distro are you using? If RedHat, since you are using DHCP will you please try putting a "LINKDELAY=10" in the /etc/sysconfig/network-scripts/ifcfg-ethX config file.
>
I use ubuntu 9.10
> Is there anything in the system log that might help narrow down the issue?
Nothing, really nothing.
It seems to detect link, dhcp client sends requests, but doesn't recieve
a thing (even tried promisc mode - doesn't help)
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2010-06-28 17:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 17:27 [REGRESSION] e1000e stopped working Maxim Levitsky
2010-06-27 17:29 ` Maxim Levitsky
2010-06-27 17:43 ` Maxim Levitsky
2010-06-27 17:47 ` Maxim Levitsky
2010-06-28 17:04 ` Allan, Bruce W
2010-06-28 17:14 ` Maxim Levitsky [this message]
2010-06-29 1:09 ` Allan, Bruce W
2010-06-29 10:32 ` Maxim Levitsky
2010-06-29 18:37 ` Tantilov, Emil S
2010-06-30 22:59 ` Maxim Levitsky
2010-07-04 0:41 ` Maxim Levitsky
2010-07-04 22:48 ` [REGRESSION] e1000e stopped working [MANUALLY BISECTED] Maxim Levitsky
2010-07-05 8:13 ` Jeff Kirsher
2010-07-05 9:58 ` Maxim Levitsky
2010-07-12 15:56 ` Maxim Levitsky
2010-07-12 21:23 ` Tantilov, Emil S
2010-07-13 0:38 ` Maxim Levitsky
2010-07-14 22:56 ` Tantilov, Emil S
2010-07-14 23:33 ` Maxim Levitsky
2010-07-15 18:57 ` Maxim Levitsky
2010-07-15 19:02 ` Tantilov, Emil S
2010-07-15 19:09 ` Maxim Levitsky
2010-07-16 19:25 ` Maxim Levitsky
2010-07-16 23:23 ` Tantilov, Emil S
2010-07-17 13:54 ` Maxim Levitsky
2010-07-26 0:25 ` Maxim Levitsky
2010-07-28 7:04 ` Maxim Levitsky
2010-07-29 1:10 ` Jeff Kirsher
2010-08-01 2:08 ` Jeff Kirsher
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=1277745247.12841.1.camel@localhost.localdomain \
--to=maximlevitsky@gmail.com \
--cc=bruce.w.allan@intel.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).