Michael Chan wrote:
Walt wrote:
Nope, it was the second one: Skip phy power down...
Let me know if can test any patches, etc.
It doesn't make sense. This code should have no effect on your
5702
Wait -- new developments! You are right, it wasn't that code
at all. I've concluded
From: walt [EMAIL PROTECTED]
Date: Sun, 26 Mar 2006 08:35:50 -0800
Can you think of which of those recent changes might be
a likely candidate?
I think you'll need to use something like git bisect to narrow down
the changeset.
-
To unsubscribe from this list: send the line unsubscribe netdev in
David S. Miller
From: walt [EMAIL PROTECTED]
Date: Sun, 26 Mar 2006 08:35:50 -0800
Can you think of which of those recent changes might be
a likely candidate?
I think you'll need to use something like git bisect to narrow down
the changeset.
Try this patch first before git bisect:
Michael Chan wrote:
On Thu, 2006-03-23 at 14:16 -0800, walt wrote:
tg3.c:v3.53 (Mar 22, 2006)
PCI: Enabling device :00:09.0 (0014 - 0016)
ACPI: PCI Interrupt :00:09.0[A] - GSI 18 (level, low) - IRQ 17
tg3: Could not obtain valid ethernet address, aborting.
ACPI: PCI interrupt for
Walt wrote:
Nope, it was the second one: Skip phy power down...
Let me know if can test any patches, etc.
It doesn't make sense. This code should have no effect on your
5702. With or without this patch, the 5702 will be powered down
the same with tg3_writephy(tp, MII_BMCR, BMCR_PDOWN) if WOL
Michael Chan wrote:
Walt wrote:
Nope, it was the second one: Skip phy power down...
It doesn't make sense. This code should have no effect on your
5702. With or without this patch, the 5702 will be powered down
the same with tg3_writephy(tp, MII_BMCR, BMCR_PDOWN) if WOL
is not enabled
On Fri, 24 Mar 2006, walt wrote:
Michael Chan wrote:
Walt wrote:
Nope, it was the second one: Skip phy power down...
It doesn't make sense. This code should have no effect on your
5702. With or without this patch, the 5702 will be powered down
the same with tg3_writephy(tp,
On Fri, 2006-03-24 at 14:06 -0800, walt wrote:
I confess I'm a bit confused by your question. I have no idea
why an ifdown would be executed during boot, but the startup
scripts are so complicated that I can't understand what they do.
The best thing to do is probably to disable all the
On Thu, 2006-03-23 at 14:16 -0800, walt wrote:
I update from Linus's git repository every morning, and today
I got this error:
tg3.c:v3.53 (Mar 22, 2006)
PCI: Enabling device :00:09.0 (0014 - 0016)
ACPI: PCI Interrupt :00:09.0[A] - GSI 18 (level, low) - IRQ 17
tg3: Could not
On Thu, 23 Mar 2006, walt wrote:
Hi,
I emailed Dave Miller, who re-directed me to this mail list.
I update from Linus's git repository every morning, and today
I got this error:
tg3.c:v3.53 (Mar 22, 2006)
PCI: Enabling device :00:09.0 (0014 - 0016)
ACPI: PCI Interrupt
10 matches
Mail list logo
