-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jack Vogel wrote:
| I have reproduced the problem, you are correct. Thank you for
| persisting thru my doubts :)
Always persisting to help improving FreeBSD. Another odd thing I noticed
today:
When dual-booting Windows on the same machine and
I fought with this issue all day today, trying to root cause it, and while I
don't have a solution I do have a better understanding of it.
I was wrong about it being the interrupt handler, at least if there's any
issue with it its not the primary cause. I actually found out using a
Fedora Live CD
Jack Vogel wrote:
I didn't mean the NIC EEPROM, but the system BIOS, make sure you are
running the version that Jeremy said he was, if that matches you might go
look at settings in the BIOS that are about management.
I'm now running the latest BIOS for my X60 version 2.22 with the same
On Wed, Aug 13, 2008 at 3:04 AM, Markus Vervier [EMAIL PROTECTED] wrote:
Jack Vogel wrote:
I didn't mean the NIC EEPROM, but the system BIOS, make sure you are
running the version that Jeremy said he was, if that matches you might go
look at settings in the BIOS that are about management.
On Wed, Aug 13, 2008 at 8:22 AM, Jack Vogel [EMAIL PROTECTED] wrote:
On Wed, Aug 13, 2008 at 3:04 AM, Markus Vervier [EMAIL PROTECTED] wrote:
Jack Vogel wrote:
I didn't mean the NIC EEPROM, but the system BIOS, make sure you are
running the version that Jeremy said he was, if that matches
On Wed, Aug 13, 2008 at 12:04:59PM +0200, Markus Vervier wrote:
Jack Vogel wrote:
I didn't mean the NIC EEPROM, but the system BIOS, make sure you are
running the version that Jeremy said he was, if that matches you might go
look at settings in the BIOS that are about management.
I'm now
For what it's worth, I have a T60 that dual boots 6.3-R/amd64 and 7.0-R/i386
and neither install has this problem. I can cold boot it with the NIC
unplugged, plug in a cable, I get a link light and ifconfig em0 goes to
active, dhclient em0 gets an IP successfully.
Did you try to run
On Friday 08 August 2008 06:31:24 pm Jack Vogel wrote:
OK, I just got access to a machine, am going to install and see if I
can repro this
this afternoon.
Jack
For what it's worth, I have a T60 that dual boots 6.3-R/amd64 and 7.0-R/i386
and neither install has this problem. I can cold boot
On Mon, Aug 11, 2008 at 08:19:46AM +, Josh Paetzel wrote:
On Friday 08 August 2008 06:31:24 pm Jack Vogel wrote:
OK, I just got access to a machine, am going to install and see if I
can repro this
this afternoon.
Jack
For what it's worth, I have a T60 that dual boots 6.3-R/amd64
On Mon, Aug 11, 2008 at 7:02 AM, Jeremy Chadwick [EMAIL PROTECTED] wrote:
On Mon, Aug 11, 2008 at 08:19:46AM +, Josh Paetzel wrote:
On Friday 08 August 2008 06:31:24 pm Jack Vogel wrote:
OK, I just got access to a machine, am going to install and see if I
can repro this
this afternoon.
Jack Vogel wrote:
Seems possibly a BIOS thing, if not that bad cable, bad link partner maybe??
I had the problem with all sorts of switches / cables. How can I dump my
EEPROM settings if that helps?
--
Markus
___
freebsd-stable@freebsd.org
On Mon, Aug 11, 2008 at 1:32 PM, Markus Vervier [EMAIL PROTECTED] wrote:
Jack Vogel wrote:
Seems possibly a BIOS thing, if not that bad cable, bad link partner
maybe??
I had the problem with all sorts of switches / cables. How can I dump my
EEPROM settings if that helps?
I didn't mean the
Hi,
I just stumbled upon this thread. I experience the exact same behaviour
as Martin on my Thinkpad X60:
Thinkpad X60 Model: 1706GMG
BIOS-Version 2.15 (7BETD4WW)
FreeBSD 7.0 STABLE amd64 (from about two weeks ago) - same situtation on
7.0-RELEASE i386
--
Markus
me too 's are of little help. Please elaborate on your exact same, since
each person's perception will be slightly different.
So far I have heard nothing that sounds like a driver issue.
Jack
On Fri, Aug 8, 2008 at 5:50 AM, Markus Vervier [EMAIL PROTECTED] wrote:
Hi,
I just stumbled upon
Jack Vogel schrieb:
me too 's are of little help. Please elaborate on your exact same, since
each person's perception will be slightly different.
Hi Jack,
maybe read it like: Thinkpad X60 1706GMG affected too, so the problem is
not specific to Martins machine.
I can write the same
At 01:56 PM 8/8/2008, Markus Vervier wrote:
3) Boot FreeBSD. Let it pass the DHCP phase (ifconfig_em0=DHCP) until
login appears.
4) Attach the cable to the NIC.
5) Voila... no link.
--
If you manually type,
dhclient em0
does it work for you then ?
---Mike
Mike Tancsa schrieb:
If you manually type,
dhclient em0
No, even if I type ifconfig em0 down ifconfig em0 up it won´t work.
The interface just gets no link until I reload the driver with a cable
plugged.
--
Markus
___
freebsd-stable@freebsd.org
OK, I just got access to a machine, am going to install and see if I
can repro this
this afternoon.
Jack
On Fri, Aug 8, 2008 at 10:56 AM, Markus Vervier [EMAIL PROTECTED] wrote:
Jack Vogel schrieb:
me too 's are of little help. Please elaborate on your exact same,
since
each person's
Am Mon, 4 Aug 2008 12:12:24 -0700
schrieb Jack Vogel [EMAIL PROTECTED]:
OK, so your EEPROM is does not have the bug. As I was
saying before, I would like to see what back to back behavior is.
And, BTW, back to back does NOT mean hook to the switch,
that's the very thing that is suspicious.
Am Sat, 02 Aug 2008 23:50:10 +0200
schrieb Torfinn Ingolfsen [EMAIL PROTECTED]:
On Sat, 02 Aug 2008 22:40:46 +0200
Martin [EMAIL PROTECTED] wrote:
good point, no. The problem appears when the first thing called on
this interface is dhclient (caused by ifconfig_em0=DHCP). I could
So, if
Am Sat, 2 Aug 2008 16:01:35 -0700
schrieb Jack Vogel [EMAIL PROTECTED]:
Hi,
After I typed /etc/rc.d/netif restart, I waited until I get
giving up message. Then I plugged the cable in. After about 30
seconds the link LED was on. I noticed that at this point I
couldn't get an address using
On Mon, Aug 04, 2008 at 10:53:35AM +0200, Martin wrote:
Am Sat, 2 Aug 2008 16:01:35 -0700
schrieb Jack Vogel [EMAIL PROTECTED]:
After I typed /etc/rc.d/netif restart, I waited until I get
giving up message. Then I plugged the cable in. After about 30
seconds the link LED was on. I
On Sat, 2 Aug 2008 10:34:47 -0700
Jack Vogel [EMAIL PROTECTED] wrote:
Telling me what kind of NIC it is isn't going to help, 82573's are
working the world over :) What exactly is your laptop, what model,
is the NIC a LOM (on the motherboard) or some addin.
Hi Jack,
this is a Lenovo Thinkpad
Martin [EMAIL PROTECTED] wrote:
On Sat, 02 Aug 2008 12:55:53 +0200
Torfinn Ingolfsen [EMAIL PROTECTED] wrote:
Just to be sure: also if the first command you try on the interface is
'ifconfig up'?
Hello Torfinn,
good point, no. The problem appears when the first thing called on this
2008/8/4 Jeremy Chadwick [EMAIL PROTECTED]:
On Mon, Aug 04, 2008 at 11:00:16AM +0100, Chris Rees wrote:
Martin [EMAIL PROTECTED] wrote:
On Sat, 02 Aug 2008 12:55:53 +0200
Torfinn Ingolfsen [EMAIL PROTECTED] wrote:
Just to be sure: also if the first command you try on the interface is
On Mon, Aug 04, 2008 at 11:00:16AM +0100, Chris Rees wrote:
Martin [EMAIL PROTECTED] wrote:
On Sat, 02 Aug 2008 12:55:53 +0200
Torfinn Ingolfsen [EMAIL PROTECTED] wrote:
Just to be sure: also if the first command you try on the interface is
'ifconfig up'?
Hello Torfinn,
good
On Mon, Aug 04, 2008 at 11:34:48AM +0200, Martin wrote:
On Sat, 2 Aug 2008 10:34:47 -0700
Jack Vogel [EMAIL PROTECTED] wrote:
Telling me what kind of NIC it is isn't going to help, 82573's are
working the world over :) What exactly is your laptop, what model,
is the NIC a LOM (on the
Am Mon, 4 Aug 2008 03:23:07 -0700
schrieb Jeremy Chadwick [EMAIL PROTECTED]:
When I return to work on Wednesday night, I'll try to reproduce what
you see (we have Juniper, Cisco, Extreme, and Netgear switches
there), then bring the laptop home and test against a D-Link switch,
as well as my
Am Mon, 4 Aug 2008 12:51:38 +0200
schrieb Martin [EMAIL PROTECTED]:
I'm trying some other things here. Before you waste time on
PEBKAC problems ;) (which I now suspect to be). Let me try to install
the latest GENERIC on my laptop first.
I've build fresh world and then kernel (GENERIC
The focus here on the laptop distracted me, but someone else at work
reminded me. Its very important that you run the EEPROM fix for
the 82573 that i posted a long while back, search in email archive
for it. Its a DOS executable that will patch your EEPROM.
I am not sure if the Lenova's need it,
Jack Vogel wrote, on 8/4/2008 9:18 AM:
The focus here on the laptop distracted me, but someone else at work
reminded me. Its very important that you run the EEPROM fix for
the 82573 that i posted a long while back, search in email archive
for it. Its a DOS executable that will patch your
Thanks for the pointer Royce, and yes that's the issue, and if you want
to boot Linux and use that instead of DOS then more power to you.
Cheers,
Jack
On Mon, Aug 4, 2008 at 10:35 AM, Royce Williams [EMAIL PROTECTED] wrote:
Jack Vogel wrote, on 8/4/2008 9:18 AM:
The focus here on the laptop
Jack Vogel wrote, on 8/4/2008 9:54 AM:
On Mon, Aug 4, 2008 at 10:35 AM, Royce Williams [EMAIL PROTECTED] wrote:
Jack Vogel wrote, on 8/4/2008 9:18 AM:
The focus here on the laptop distracted me, but someone else at work
reminded me. Its very important that you run the EEPROM fix for
the 82573
Right, the Linux driver implemented the ability to write as well as read
the eeprom, I've always been hesitant to add that. But for some it
will be easier to boot Linux and run the script.
Thanks for adding the URL Royce.
Jack
On Mon, Aug 4, 2008 at 11:15 AM, Royce Williams [EMAIL PROTECTED]
On Mon, 04 Aug 2008 09:35:21 -0800
Royce Williams [EMAIL PROTECTED] wrote:
Jack Vogel wrote, on 8/4/2008 9:18 AM:
The focus here on the laptop distracted me, but someone else at work
reminded me. Its very important that you run the EEPROM fix for
the 82573 that i posted a long while back,
OK, so your EEPROM is does not have the bug. As I was
saying before, I would like to see what back to back behavior is.
And, BTW, back to back does NOT mean hook to the switch,
that's the very thing that is suspicious. It means NIC to NIC,
no DHCP, assigned addresses. And then see that you pass
On Mon, Aug 04, 2008 at 10:18:50AM -0700, Jack Vogel wrote:
The focus here on the laptop distracted me, but someone else at work
reminded me. Its very important that you run the EEPROM fix for
the 82573 that i posted a long while back, search in email archive
for it. Its a DOS executable that
On Sat, 02 Aug 2008 07:00:15 +0200
Martin [EMAIL PROTECTED] wrote:
Once again. I made a mistake describing the problem. I'm really sorry
for this. The interface actually appears in the ifconfig list, but I
cannot get it up. It always shows no carrier. No matter what I try.
Just to be sure:
On Fri, Aug 1, 2008 at 9:47 PM, Martin [EMAIL PROTECTED] wrote:
On Fri, 1 Aug 2008 09:24:53 -0700
Jack Vogel [EMAIL PROTECTED] wrote:
If the poster gives me EXACT hardware list I will see about repro'ing the
problem inhouse. We do not do much of anything with laptops but I
will see. Oh and a
On Sat, 02 Aug 2008 12:55:53 +0200
Torfinn Ingolfsen [EMAIL PROTECTED] wrote:
Just to be sure: also if the first command you try on the interface is
'ifconfig up'?
Hello Torfinn,
good point, no. The problem appears when the first thing called on this
interface is dhclient (caused by
On Sat, 02 Aug 2008 22:40:46 +0200
Martin [EMAIL PROTECTED] wrote:
good point, no. The problem appears when the first thing called on
this interface is dhclient (caused by ifconfig_em0=DHCP). I could
So, if you don't automatically configure the interface, but instead do
something like:
On Sat, Aug 2, 2008 at 1:40 PM, Martin [EMAIL PROTECTED] wrote:
On Sat, 02 Aug 2008 12:55:53 +0200
Torfinn Ingolfsen [EMAIL PROTECTED] wrote:
Just to be sure: also if the first command you try on the interface is
'ifconfig up'?
Hello Torfinn,
good point, no. The problem appears when the
Hello,
I don't remember anymore when I reported it the first time. I think it
was around 4.x or something like that. The em(4) bug is still there
after years.
Hasn't anyone really noticed yet that em(4) only appears when you boot
FreeBSD with the interface physically attached to a switch for
Hasn't anyone really noticed yet that em(4) only appears when you boot
FreeBSD with the interface physically attached to a switch for example?
If you attach it later, after boot up, the interface won't power up and
appear in the interface list (ifconfig)?
I'm afraid I don't see your problem
On Fri, Aug 01, 2008 at 02:20:05PM +0200, Martin wrote:
I don't remember anymore when I reported it the first time. I think it
was around 4.x or something like that. The em(4) bug is still there
after years.
Hasn't anyone really noticed yet that em(4) only appears when you boot
FreeBSD with
Hi,
On 1 Aug 2008, at 13:20, Martin wrote:
Hello,
I don't remember anymore when I reported it the first time. I think it
was around 4.x or something like that. The em(4) bug is still there
after years.
Hasn't anyone really noticed yet that em(4) only appears when you boot
FreeBSD with the
On Fri, 1 Aug 2008, Martin wrote:
I don't remember anymore when I reported it the first time. I think it was
around 4.x or something like that. The em(4) bug is still there after years.
Hasn't anyone really noticed yet that em(4) only appears when you boot
FreeBSD with the interface
If the poster gives me EXACT hardware list I will see about repro'ing the
problem inhouse. We do not do much of anything with laptops but I
will see. Oh and a pciconf would help too.
Jack
On Fri, Aug 1, 2008 at 7:43 AM, Robert Watson [EMAIL PROTECTED] wrote:
On Fri, 1 Aug 2008, Martin wrote:
On Fri, 1 Aug 2008 09:24:53 -0700
Jack Vogel [EMAIL PROTECTED] wrote:
If the poster gives me EXACT hardware list I will see about repro'ing the
problem inhouse. We do not do much of anything with laptops but I
will see. Oh and a pciconf would help too.
Hi Jack,
pciconf -lv gives me:
[EMAIL
On Fri, 1 Aug 2008 05:42:24 -0700
Jeremy Chadwick [EMAIL PROTECTED] wrote:
Hi Jeremy,
Most commonly what you're reporting is the result of a switch upstream
which isn't fully compatible or properly doing 802.3u auto-neg.
It is attached to a cheap switch here. Also at my office it is not
50 matches
Mail list logo
