|
From: Zameer A. <za...@sy...> - 2002-12-12 16:03:38
|
Hi Eric,
>But you say it appears to lock up? Hmm....
>Confirmation that etherboot actually locks up, (no response to esc)
>as opposed to something else would be interesting.
I meant unresponsive. Pardon my English. When I press Esc, the etherboot
fires again and probes the card successfully and prints the following message.
{Start of messages}
Boot from (N)etwork (D)isk (F)loppy or from (L)ocal?
Probing pci nic...
[E1000]Ethernet addr: 00:08:74:A3:D2:B3
Searching for server (DHCP)...
{Pressing Esc}
<abort>
Probing pci nic...
Probing isa nic...
No adapter found
<sleep>
Boot from (N)etwork (D)isk (F)loppy or from (L)ocal?
Probing pci nic...
[E1000]Ethernet addr: 00:08:74:A3:D2:B3
Searching for server (DHCP)...
{End of Messages}
>Which version of the linux driver work?
I installed RH8.0 and the default kernel seems to work.
ver 2.4.18-14
<snip>
[root@lion root]# lsmod | grep e1000
e1000 55916 1
[root@lion root]# uname -a
Linux lion 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux
</snip>
>What is the PCI ID? i.e. the very specific model.
Here it is ...
01:0c.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller
(rev 02)
The full listing is here....
<snip>
00:00.0 Host bridge: Intel Corp. 82845G/GL [Brookdale-G] Chipset Host Bridge
(rev 01)
00:02.0 VGA compatible controller: Intel Corp. 82845G/GL [Brookdale-G]
Chipset Integrated Graphics Device (rev 01)
00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 01)
00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 01)
00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 01)
00:1d.7 USB Controller: Intel Corp. 82801DB USB EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corp. 82801DB ISA Bridge (LPC) (rev 01)
00:1f.1 IDE interface: Intel Corp. 82801DB ICH4 IDE (rev 01)
00:1f.3 SMBus: Intel Corp. 82801DB SMBus (rev 01)
00:1f.5 Multimedia audio controller: Intel Corp. 82801DB AC'97 Audio (rev 01)
01:0c.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller
(rev 02)
</snip>
>Is this copper or fiber?
Normal RJ45 connector so its copper.
>What kind of switch are you plugged into, and how fast is it?
Its a small home style brewed network. Only Linksys hubs in the picture.
Summarizing.
As a standalone Linux clien, the machine has no problems getting its DHCP
address of the server. It fails when booted via etherboot.
Method of booting Etherboot : CD Image (These dells lack a floppy drive)
|
|
From: Zameer A. <za...@sy...> - 2002-12-12 21:24:59
|
Hi eric, Here are my findings >lspci -n gives the information I was looking for. >I expect it is 8086:100e, but I am not certain. Yes, it is what you said. [root@lion root]# lspci | grep Ethernet 01:0c.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02) [root@lion root]# lspci -n | grep 01:0c.0 01:0c.0 Class 0200: 8086:100e (rev 02) >Is this a 10Mbit hub >or a 100Mbit hub? Its a 100Mbit hub. >There is a >#define DEBUG 0 >at the top of file. Could you change that to >#define DEBUG 3 > > And then send the output? I downloaded the source, made above changes and generated the floppy in the following manner. $sudo cat boot1a.s bin32/e1000.lzimg > sudo /dev/fd0 Results in the same behaviour.. Etherboot waits in the new line after Searching for server (DHCP)... _ Any ideas? Do I need to specify any PCI specific lines to etherboot? Is the way I generated floppy correct? Thanks, Zameer A. |
|
From: <ebi...@ln...> - 2002-12-12 21:37:34
|
Zameer Ahmed <za...@sy...> writes: > > >There is a > >#define DEBUG 0 > >at the top of file. Could you change that to > >#define DEBUG 3 > > > > And then send the output? > I downloaded the source, made above changes and generated the floppy in the > following manner. > > > $sudo cat boot1a.s bin32/e1000.lzimg > sudo /dev/fd0 > > Results in the same behaviour.. Etherboot waits in the new line after > > Searching for server (DHCP)... Does etherboot print out more information? All I would expect is a long stream of extra print statements before it gets to this point. I would at least have a clue what the driver is thinking at this point. I don't know what good it will do me but it is certainly a possibility. > > Any ideas? > > Do I need to specify any PCI specific lines to etherboot? > Is the way I generated floppy correct? It looks correct except the bit about redirecting it into sudo. You can modify EXTRAVERSION in the makefile if you want to be certain you are running your newly compiled version. Eric |
|
From: <ebi...@ln...> - 2002-12-13 03:31:31
|
Zameer Ahmed <za...@sy...> writes: > Searching for server (DHCP)... > _ > How very odd I just reproduced this. Then I turned the machine off and back on and the problem went away... Eric |
|
From: <ebi...@ln...> - 2002-12-13 04:56:38
|
ebi...@ln... (Eric W. Biederman) writes:
> Zameer Ahmed <za...@sy...> writes:
>
>
> > Searching for server (DHCP)...
> > _
> >
>
> How very odd I just reproduced this. Then I turned the machine off and back
> on and the problem went away...
And I think I see what is going on.
There is this loop in the transmit function:
while (!(txp->upper.data & E1000_TXD_STAT_DD)) {
udelay (10); /* give the nic a chance to write to the register */
poll_interruptions();
}
And if you never see any dots on the line after
"Searching for server (DHCP)..."
Then the transmit function never returns.
With that being the only loop that must be where it is hanging.
As to what causes it to hang I do not yet know.
Given that we call functions that may modify memory in arbitrary
ways I do not see the compiler over optimizing this, but
on some random compiles I have seen it hang there...
Eric
|
|
From: Zameer A. <za...@sy...> - 2002-12-16 15:20:26
|
Hi Eric,
>And I think I see what is going on.
>There is this loop in the transmit function:
>
> while (!(txp->upper.data & E1000_TXD_STAT_DD)) {
> udelay (10); /* give the nic a
> chance to write to the register */
> poll_interruptions();
> }
I tried some recompiling with 5.1.3 release at the Etherboot site and it
seems like its working. I now thing the that the floppy generated from the
www.rom-o-matic.com site is buggy. Also gcc-3.2.7 is buggy and it might over
zeleously optimize binary. I will play with this later.
For now I have got the e1000 problems go away and Thanks very much for your
help.
Thanks,
Zameer A.
|
|
From: <ebi...@ln...> - 2002-12-17 04:05:00
|
Zameer Ahmed <za...@sy...> writes:
> Hi Eric,
>
> >And I think I see what is going on.
> >There is this loop in the transmit function:
> >
> > while (!(txp->upper.data & E1000_TXD_STAT_DD)) {
> > udelay (10); /* give the nic a
> > chance to write to the register */
> > poll_interruptions();
> > }
>
>
> I tried some recompiling with 5.1.3 release at the Etherboot site and it
> seems like its working. I now thing the that the floppy generated from the
> www.rom-o-matic.com site is buggy. Also gcc-3.2.7 is buggy and it might over
> zeleously optimize binary. I will play with this later.
Given that there is no gcc-3.2.7 I suspect it is quite an unreliable compiler...
I do not think it is a compiler problem in this case, but rather a selection
of options that will either make the problem more or less likely to happen.
> For now I have got the e1000 problems go away and Thanks very much for your
> help.
Welcome.
Eric
|
|
From: <ebi...@ln...> - 2002-12-12 17:56:58
|
Zameer Ahmed <za...@sy...> writes:
> Hi Eric,
>
> >But you say it appears to lock up? Hmm....
> >Confirmation that etherboot actually locks up, (no response to esc)
> >as opposed to something else would be interesting.
>
> I meant unresponsive. Pardon my English. When I press Esc, the etherboot
> fires again and probes the card successfully and prints the following message.
>
> {Start of messages}
<snip>
> {End of Messages}
So the driver finds the link, and it thinks everything is fine.
> >Which version of the linux driver work?
> I installed RH8.0 and the default kernel seems to work.
> ver 2.4.18-14
>
> <snip>
> [root@lion root]# lsmod | grep e1000
> e1000 55916 1
> [root@lion root]# uname -a
> Linux lion 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux
> </snip>
>
> >What is the PCI ID? i.e. the very specific model.
> Here it is ..
lspci -n gives the information I was looking for.
I expect it is 8086:100e, but I am not certain.
> >What kind of switch are you plugged into, and how fast is it?
> Its a small home style brewed network. Only Linksys hubs in the picture.
I wonder if there are some problems working with hubs. I haven't
tried it on anything less than a 10/100 switch. Is this a 10Mbit hub
or a 100Mbit hub?
>
> Summarizing.
> As a standalone Linux clien, the machine has no problems getting its DHCP
> address of the server. It fails when booted via etherboot.
>
> Method of booting Etherboot : CD Image (These dells lack a floppy drive)
No big deal except it makes changes a little harder to test.
There is a
#define DEBUG 0
at the top of file. Could you change that to
#define DEBUG 3
And then send the output?
I don't know that the debugging information would help but since it is not obvious
what is wrong that is all there is to debug with at the moment.
Eric
|
