On Thursday 12 November 2009 19:45:45 Andrew Benton wrote: > On 12/11/09 17:14, Larry Finger wrote: > > I guess I'm a failure at writing diagnostic patches. Until there is a DMA > > error, > > the only effect of the patch is to add a little extra time to the routine > > that > > fills in the descriptor structure, and it adds to the data and code size. > > If any > > of those changes have the effect of "fixing" your problem, then we have > > severe > > difficulties. I expect that you will get the error sooner or later. > > > > Well to provoke it a little I recompiled with all the options on the > ACPI menu set to y and now it fails to connect like so:- > > > Nov 12 18:40:38 doughnut kernel: wlan0: deauthenticating from > 00:1e:2a:27:7e:62 by local choice (reason=3) > Nov 12 18:40:38 doughnut kernel: wlan0: direct probe to AP 00:1e:2a:27:7e:62 > (try 1) > Nov 12 18:40:38 doughnut kernel: wlan0: direct probe responded > Nov 12 18:40:38 doughnut kernel: wlan0: authenticate with AP > 00:1e:2a:27:7e:62 (try 1) > Nov 12 18:40:38 doughnut kernel: wlan0: authenticated > Nov 12 18:40:38 doughnut kernel: wlan0: associate with AP 00:1e:2a:27:7e:62 > (try 1) > Nov 12 18:40:38 doughnut kernel: wlan0: RX AssocResp from 00:1e:2a:27:7e:62 > (capab=0x411 status=0 aid=1) > Nov 12 18:40:38 doughnut kernel: wlan0: associated > Nov 12 18:40:40 doughnut ntpd[514]: frequency initialized -66.915 PPM from > /home/boot/ntp.drift > Nov 12 18:40:43 doughnut kernel: b43-phy0 ERROR: Fatal DMA error: 0x00000800, > 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000 > Nov 12 18:40:43 doughnut kernel: b43-phy0: Controller RESET (DMA error) ... > Nov 12 18:40:43 doughnut kernel: b43: Dump of last 20 DMA descriptors > Nov 12 18:40:43 doughnut kernel: b43: Descr. 0: 0x0 0x930 0x364BD020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 1: 0x0 0x930 0x364BF020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 2: 0x0 0x930 0x364B7020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 3: 0x0 0x930 0x364B6020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 4: 0x0 0x930 0x364B5020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 5: 0x0 0x930 0x364B4020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 6: 0x0 0x930 0x364A8020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 7: 0x0 0x930 0x364AF020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 8: 0x0 0x930 0x364AE020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 9: 0x60000000 0x74 0x36972428 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 10: 0x80000000 0x6E 0x36A1595A > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 11: 0x0 0x930 0x364AD020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 12: 0x0 0x930 0x364AC020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 13: 0x0 0x930 0x364AB020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 14: 0x0 0x930 0x364AA020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 15: 0x0 0x930 0x364A9020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 16: 0x0 0x930 0x36517020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 17: 0x0 0x930 0x36516020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 18: 0x0 0x930 0x36515020 > 0x80000000 > Nov 12 18:40:43 doughnut kernel: b43: Descr. 19: 0x0 0x930 0x36514020 > 0x80000000
This looks OK. I guess there's something fishy going on in our descriptor memory allocation. We have some very weird workarounds in there which I still think are wrong. I'll try to rewrite that stuff and send a patch for testing later... -- Greetings, Michael. _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
