On Tuesday 07 November 2006 22:20, Melameth, Daniel D. wrote: > STeve Andre' wrote: > > On Monday 06 November 2006 22:10, Melameth, Daniel D. wrote: > > > I'm having the same issue with 4.0 -stable--well, a bastardized copy > > > of -stable that also contains ral, cardbus and related changes from > > > -current. I've used more than one fxp card as well as more than one > > > ral card and the issue stays the same--fxp0: warnings and timeouts > > > and, eventually under load or after a few days, the box locks up > > > with no apparent panic and ddb.console=1 provides no help. If I > > > recall correctly, the issue also exists if I replace fxp with xl. > > > It would appear so long as there are two Cardbus cards in this box, > > > this issue occurs--as fxp plus wi is rock solid. > > > > > > How do I troubleshoot this further? > > > > [snip] > > > > Ugh. This brings back some memories. I'm pretty sure it was a sat > > pro that I had some cardbus problems with some time ago. I believe I > > did a bios update, which changed things; better but not perfect. So > > try that, and look in the bios settings for anything that can tweak > > the cardbus slots. Given my experiences with this, I'm thinking > > there is a good chance that your problem lies in the laptop itself. > > Good luck. > > Yea, I figured as much/was afraid of that. Thanks for sharing.
Thinking on this a little more, you might, just might see a difference between booting up with the cards, and inserting the cards after booting, or some combination of one card in and one card inserted post boot. I dimly remember doing that and wondering what was going on, so that might affect your results. Also change the speed of the system if you can to see what that does. I think you are likely out of luck here, but something truly screwy might help you. Ah, and you mention backporting some of the ral code--have you tried running -current on it? Can't hurt... --STeve Andre'
