On Saturday 22 November 2008 12:59:27 Yuval Hager wrote: > On Saturday 22 November 2008, Peter Stuge wrote: > > Yuval Hager wrote: > > > When the wireless is working: > > > 00: e4 14 12 43 06 01 10 00 02 00 80 02 08 00 00 00 > > > 10: 04 c0 ff fd 00 00 00 00 00 00 00 00 00 00 00 00 > > > 30: 00 00 00 00 40 00 00 00 00 00 00 00 0a 01 00 00 > > > > > > After it fails: > > > 00: e4 14 12 43 00 00 10 00 02 00 80 02 00 00 00 00 > > > 10: 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > > > 30: 00 00 00 00 40 00 00 00 00 00 00 00 00 01 00 00 > > > > Differences: > > > > 04h bit 1: A value of 1 allows the device to respond to Memory Space > > addresses. 04h bit 2: A value of 1 allows the device to behave as a bus > > master. 04h bit 8: A value of 1 enables the SERR# driver. > > > > 0ch bit 3: System cacheline size in units of DWORDs. > > > > 10h: BAR0 (memory mapped address for device) > > > > 3ch bits 7:0: Interrupt Line > > > > Basically the card has been deconfigured. This should never happen. > > > > Try the following (somewhat naive) command to see if it starts > > working again: > > > > setpci -d 14e4:4312 c.l=8 10.l=fdffc004 4.w=0106 > > > > Nope, that doesn't work. > At first I get the same register reads as in the beginning, but no network > access. When I try to restart the interface, I get "Fatal DMA error" > and "Controller RESET (DMA error)". Trying to unload and reload the modules > leads to a complete lockup.
Ok, kind of expected. Can you turn on _all_ kernel-hacking options for memory debugging? -- Greetings Michael. _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
