Jason Wood wrote: >> From: Larry Finger <[EMAIL PROTECTED]> >> Please send the entire output of dmesg. Perhaps that will show where >> the problem is. >> >> Larry > > > I've attached 2 files, dmesg.2.6.21.4 after running modprobe bcm43xx, > and dmesg.2.6.21.4.works where it decided to work. I get similar > results under 2.6.22.1, when it works the module is loaded > automatically, otherwise I get nothing.
Analysis of the two dmesg outputs cannot be completed as your kernel is compiled with a very small log buffer and it is wrapping around; however, I see enough to suspect some kind of race condition in the bus setup. I see a device with different IRQ's between the good/bad boots. That shouldn't happen. I do not think you are having hardware problems, and I'm pretty sure it is not a bcm43xx problem. Is it possible for you to upgrade to a 2.6.22 or 2.6.23-rc2 kernel? If so, please do. Whatever bug we are chasing may have already been fixed. If it is not possible to upgrade, I would like you to add the option 'log_buf_len=262144' when you boot. That will increase the size of the log buffer so that we see everything. Then send me the dmesg output from a good and a bad boot. Another thing to try is the boot option 'maxcpus=0'. That will run it as a unit processor system and eliminate a lot of potential problems with SMP. I'm particularly interested in knowing if it always works with this option, or if it also fails sometimes. What is the make/model of your laptop? I probably have that info somewhere, but I'm lazy. In addition, are your running a 32- or 64-bit system? Thanks, Larry _______________________________________________ Bcm43xx-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
