Date: Sat, 15 Oct 2005 13:00:20 -0400 From: Gerard Seibert <gerard@seibercom.net> To: freebsd-questions@freebsd.org Subject: Re[2]: bizar problem with a Dell latitude D600's onboard nic Message-ID: <20051015124914.81FD.GERARD@seibercom.net> In-Reply-To: <4351257E.1020800@pandora.be> References: <20051015112229.315B.GERARD@seibercom.net> <4351257E.1020800@pandora.be>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, October 15, 2005 11:51:26 AM, Philip Keuleers <ph.keuleers@p= andora.be> Subject: Re: bizar problem with a Dell latitude D600's onboard nic Wrote these words of wisdom: > Gerard Seibert wrote: >=20 > >On Saturday, October 15, 2005 11:15:26 AM, Philip Keuleers <ph.keuleer= s@pandora.be> > >Subject: bizar problem with a Dell latitude D600's onboard nic > >Wrote these words of wisdom: > > > > =20 > > > >>Hi, > >> > >>I'm looking for some help with a problem I've been having with a Dell= =20 > >>D600 with a FreeBSD 5.2.1 install. A while ago I started getting netw= ork=20 > >>timeouts. In my message logs I found entries like this: > >> > >>Oct 10 14:35:04 loki kernel: bge0: PHY read timed out > >>Oct 10 14:35:04 loki last message repeated 2 times > >>Oct 10 14:35:09 loki kernel: bge0: watchdog timeout -- resetting > >>Oct 10 14:35:09 loki kernel: bge0: PHY read timed out > >>Oct 10 14:35:09 loki kernel: bge0: PHY read timed out > >>Oct 10 14:35:09 loki kernel: bge0: RX CPU self-diagnostics failed! > >>Oct 10 14:35:09 loki kernel: bge0: flow-through queue init failed > >>Oct 10 14:35:09 loki kernel: bge0: initialization failure > >>Oct 10 14:35:09 loki kernel: bge0: PHY read timed out > >>Oct 10 14:35:14 loki last message repeated 5 times > >>Oct 10 14:35:15 loki su: cz2nhc to root on /dev/ttyv0 > >>Oct 10 14:35:19 loki kernel: bge0: PHY read timed out > >>Oct 10 14:35:29 loki last message repeated 7 times > >>Oct 10 14:35:29 loki kernel: bge0: RX CPU self-diagnostics failed! > >>Oct 10 14:35:30 loki kernel: bge0: flow-through queue init failed > >>Oct 10 14:35:30 loki kernel: bge0: initialization failure > >>Oct 10 14:35:30 loki kernel: bge0: PHY read timed out > >>Oct 10 14:36:00 loki last message repeated 20 times > >> > >>Only a reboot managed to get the onboard nic back in working order=20 > >>again. I suspected hardware problems, called Dell support who couldn'= t=20 > >>help me unless I had win XP installed. So I switched disks with a=20 > >>colleage and lo and behold my bsd-disk in his laptop: no problem, his= =20 > >>disk in my laptop: no problem... Not telling Dell the whole story I=20 > >>managed to convince them my disk in someone elses laptop worked fine=20 > >>thus it must be hardware related. They replaced the systemboard and t= he=20 > >>laptop worked fine for about a week or two and the same problem came=20 > >>back... slowly increasing in frequency. At first it would be every fe= w=20 > >>days (I could live with that) but after a while it was every few hour= s=20 > >>(no way I could live with that). Even worse, at one point the nic=20 > >>wouldn't even show up in dmesg as if it wasn't there. > >>Called Dell again... same blabla.. no XP no help. They insisted I=20 > >>upgrade my bios ... so I did and everything worked again... for a day= =20 > >>and a half... the nic disappeared again. Tried both a linux and a XP=20 > >>live cd .. none see the nic. In my messages file I get > >> > >>Oct 14 18:11:02 loki kernel: pccard1: Card has no functions! > >>Oct 14 18:11:02 loki kernel: cbb1: PC Card card activation failed > >> > >>Does anyone have a bright idea of what is happening here? It looks li= ke=20 > >>a hardware issue to me but since the systemboard has already been=20 > >>replaced I'll need some good arguments to convince the Dell boys it's= =20 > >>not a FreeBSD issue. Or could it be ? > >>I'll gladly post any logs or output that could help ... just ask :-) > >> > >>In working order the nic is listed in a scanpci as > >> > >>pci bus 0x0002 cardnum 0x00 function 0x00: vendor 0x14e4 device 0x165= d > >>Broadcom Corporation NetXtreme BCM5705M Gigabit Ethernet > >> > >>pci bus 0x0002 cardnum 0x01 function 0x00: vendor 0x1217 device 0x711= 3 > >>O2 Micro, Inc. Device unknown > >> > >>pci bus 0x0002 cardnum 0x01 function 0x01: vendor 0x1217 device 0x711= 3 > >>O2 Micro, Inc. Device unknown > >> > >>Thanx in advance for your help > >> > >>Greetz, > >>Philip > >> =20 > >> > > > > > >***** REPLY SEPARATOR ***** > >On 10/11/2005 5:29:42 PM, Gerard Replied: > > > >Maybe I am missing something here, but if you switched disks and the > >problem did not resurface, why are you wasting Dell's time swapping ou= t > >hardware? If you are going to buy a computer system and install an OS > >that is not supported by the computer's manufacturer, you have to assu= me > >all risks and responsibilities involved with that system. All you are > >doing is wasting the time of the tech support people at Dell. They are > >obviously not trained to work systems with non Microsoft OS's. > > > >By the way, 5.2.1 is an old build. Why not try 5.4 instead. It might > >very well rectify your problem. > > > > =20 > > > I'm aware 5.2.1 is rather old and probably not the best release but it=20 > worked fine for me on this laptop since it was released. I also tried=20 > booting from a Freesbie live cd (based on FreeBSD 5.3) with the same=20 > results. > As for wasting Dell's time... just swapping disks with my collegue was = a=20 > test and at best a workaround, not a solution. On top of that I'm only=20 > wasting Dell's time if it is proven that FreeBSD is causing the problem= =20 > (wich is actually what I'm trying to determin). If it is hardware it IS= =20 > there problem... besides right now wether I boot it with FreeBSD, Linux= =20 > or XP the problem is there.... >=20 > anyway, I just wanted to ask a question ... not start a flame war > =20 > Greetz, > Philip >=20 ***** REPLY SEPARATOR ***** On 10/11/2005 5:29:42 PM, Gerard Replied: I am sorry, perhaps I am not fully comprehending your post. I thought you meant that after you swapped disks, the problems subsided. //quote// So I switched disks with a colleage and lo and behold my bsd-disk in his laptop: no problem, his disk in my laptop: no problem... //end quote// I assumed that the problem stopped. Technically, if it is a hardware problem, and that does not seem to be true at this point, it is not Dell's problem if you are using an OS other than what they certified the machine to be compatible with. Example: I had an old Compaq 5140 machine that had no problems with ACPI under Windows, but failed to utilize that function under FreeBSD. There was no way I could get Compaq to correct the situation since they never certified the machine to work with anything other than Windows. Anyway, I hope you can bring this situation to a satisfactory conclusion. --=20 Gerard Seibert gerard@seibercom.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051015124914.81FD.GERARD>