Re: PROBLEM: network driver causes kernel panic
From: Jeff Garzik (jgarzik_at_pobox.com)
Date: 06/04/04
- Previous message: David Ford: "Re: [boot hang] 2.6.7-rc2, VIA VT8237"
- Next in thread: Mikael Pettersson: "Re: PROBLEM: network driver causes kernel panic"
- Maybe reply: Mikael Pettersson: "Re: PROBLEM: network driver causes kernel panic"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 04 Jun 2004 16:47:13 -0400 To: Mikael Pettersson <mikpe@csd.uu.se>
Mikael Pettersson wrote:
> This confirms that eth1 is a 21041 driven by the de2104x driver.
>
> I've seen something very similar to Casey's problem, on a PowerMac
> with a built-in 21041. Booting it with no network cable connected
> causes a timer to hit a BUG() in de2104x about a second after
> the device is ifup:d.
>
> The 2.4 kernel's tulip driver works just fine.
>
> I reported this last year, but nothing happened.
Well, I'm very interested in debugging it. There were a flurry of
de2104x patches in the past year, I thought that took care of the issues.
Please email details to netdev@oss.sgi.com and jgarzik@pobox.com...
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: David Ford: "Re: [boot hang] 2.6.7-rc2, VIA VT8237"
- Next in thread: Mikael Pettersson: "Re: PROBLEM: network driver causes kernel panic"
- Maybe reply: Mikael Pettersson: "Re: PROBLEM: network driver causes kernel panic"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
