On Thursday 23 July 2009 17:18:24 Francesco Gringoli wrote: > On Jul 23, 2009, at 11:18 AM, Michael Buesch wrote: > > > On Thursday 23 July 2009 04:05:17 Larry Finger wrote: > >> Francesco Gringoli wrote: > >>> Larry, I think this could be one of the causes of the > >>> malfunctioning you > >>> reported before. If you have some time (and indeed if you feel like > >>> doing it :-) ) please test this firmware, it will be great. > >> > >> Francesco, > >> > >> The system ran about 30 minutes, then crashed. I missed the first > >> oops, but caught a kernel panic with formal traceback on my i386 > >> system: > >> > >> b43_dma_handle_txstatus + 0x1ee/0x2fa > >> b43_handle_txstatus + 0x45/0x52 > >> > >> The call in b43_dma_handle_status is at line 1405: > >> > >> unmap_descbuffer(ring, meta->dmaaddr, meta->skb->len, > >> 1); > >> > >> The oops was in drivers/net/wireless/b43/xmit.h:171 in the call to > >> b43_is_old_txhdr_format(). It appears that dev->fw.rev causes the > >> oops. > > > > How is that possible? Is the firmware clobbering random memory? > > I don't think that the value was modified by the firmware. It cannot > poke values into host memory ;-)
Oh yes it can. It has a DMA engine. > I suppose that the issue on pccard32 > hardware is not yet solved. Which issue? This crash does _not_ happen with proprietary firmware. The only way dev->fw.rev could crash is by dev being NULL. > I will get a closer look at how the > overflow condition should be handled correctly when reporting txstatus > to host. -- Greetings, Michael. _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
