Messages in this thread | | | Date | Sat, 05 Feb 2011 19:35:46 +0100 | From | "R. Herbst" <> | Subject | Re: Sun GEM PPC32 Bug? |
| |
Am 04.02.2011 23:55, schrieb David Miller: > > I think we're simply not resetting enough when the RX FIFO overflow > happens. > > Just for fun I checked the OpenBSD GEM driver to see what they do. > When an overflow occurs, they bump the statistic, record the current > read and write fifo pointer registers, and schedule a watchdog timer > for 400ms into the future. > > If the watchdog timer sees that the RX FIFO overflow bit is still set > in the RX status register, and the RX FIFO read and write pointers > have not changed, it resets the entire chip. > > We unconditionally reset the RX MAC when an overflow occurs, that may > simply not be enough to unwedge this thing. > Is there a special Kernel parameter (sysctl.conf), that makes it possible to use the Network. So how it is now I can´t work with it. What can I do at the moment? -- 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/
| |