On Mon, Mar 10, 2008 at 09:39:36AM +0100, Daniel Gerzo wrote: > Hello Pyun, > > Monday, March 10, 2008, 2:55:26 AM, you wrote: > > > On Sat, Mar 08, 2008 at 05:07:10PM +0100, Daniel Gerzo wrote: > >> Hello, > >> > >> Saturday, March 8, 2008, 12:11:03 AM, has been written: > >> > >> > Hello Pyun, > >> > >> > Friday, March 7, 2008, 5:38:15 AM, you wrote: > >> > >> >> I guess your issue is not related with bus_dma fixes but improper > >> >> handling of link state. Try attached patch and let me know how it > >> >> goes. > >> > >> > The attached patch didn't help, the box is again in the same status. > >> > Can I provide you with some more detailed debugging info, or do you > >> > have some other ideas what could be fixed? > >> > >> > I could probably manage a remote access to that box, but no remote > >> > console is available, and I don't know exactly how to trigger this > >> > scenario, but I think it depends on the amount of traffic being sent > >> > over the device. > >> > >> If I won't hear from anybody in next 24 hours, I will have to replace > >> the network device in this box, in order to get it running properly. > >> > >> However, I don't consider this step as a right solution and I would > >> rather better like to have it fixed in the driver. > >> > > > Yes, I'd like to. > > By any chance, does the system have more than 4GB memory? > > Well it does have exactly 4GB. Attached, I am sending you the output > of dmesg, pciconf and dmidecode utilities. > > The machine has been rebooted yesterday, but I haven't replaced (well > re(4) is an onboard interface so better term would be disabled) the > given NIC, but at the moment, it works fine. I suppose it will stop > working in next 24 hours... > Since you're using MSI, would you try attached patch? Sorry, I don't have PCIe based hardware and RealTek's datasheet for PCIe variants is too poor to get useful information. -- Regards, Pyun YongHyeon
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:28 UTC