David S. Miller wrote: > From: Jeff Garzik <jgarzik@mandrakesoft.com> > Date: Thu, 07 Mar 2002 15:19:40 -0500 > > Ben Greear wrote: > > In case you are using intel's 1.8.37 driver, I can cause a kernel panic > > in it by trying to reset the transceiver through MII IOCTLs.. I've > > been passing email with their support, so hopefully it will be resolved > > soon. > ... > Anyway, this is e100 version 2.0.19, with lots of changes by the Intel > folks at my request. > > Ben, I'm going to put your report in the same classification > as "root cat'd crap into /dev/kmem and the kernel crashed". > > If you are programming the PHY directly with MII IOCTLs you are on > your own. I personally refuse to monitor how the user pokes at the > MII in my drivers to try and cope with the user putting the PHY into a > weird state that the driver would otherwise never need to deal with. > > It is not a bug, pure and simple. It crashed my kernel, and no other driver has done that yet, so I consider it a bug. The reason I tried the MII ioctl was because the chip was locked up (couldn't receive packets), so the MII crash may be a symptom of the first. At any rate, the driver I was testing from Intel's site was not stable. I have yet to try the e100 that Jeff sent out, but his later email made it sound pretty experimental. I'll look forward to poking at it when it goes into the 2.4 series, but if using the MII interface makes it unstable, I will not be able to use it. Thanks, Ben -- Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com> President of Candela Technologies Inc http://www.candelatech.com ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
