On 11/14/2009 08:45 PM, Michael Buesch wrote: > On Saturday 14 November 2009 12:24:24 Oncaphillis wrote: >> On 11/13/2009 08:20 PM, Larry Finger wrote: >>> On 11/13/2009 11:46 AM, Oncaphillis wrote: >>> >>>> Thanks for the tip. But it still hangs >>> >>> We still need to know where it hangs. If you boot to console mode (type a 3 >>> on >>> the option line in GRUB), does it boot? If it does not, what is the last >>> line >>> shown on the console? If your distro shows a splash screen while booting, >>> get >>> rid of it by typing an ESC after booting starts, or eliminate the >>> "splash=silent" option on the boot line. >>> >>> If the previous boot works, log into your usual account. That should still >>> work. >>> Next you should type the command startx and immediately press the keys >>> CRTL-ALT-F10. That is hold the CTRL and ALT keys while pressing the F10 >>> key. The >>> display should shift to the log console. When the computer freezes, report >>> what >>> you see on the screen. It will not scroll, nor can you save it. Write it >>> down by >>> hand or take a picture. >>> >>> Report what happens. If some of these steps don't work on your computer, >>> please >>> tell what distro you are using. >>> >>> Larry >>> >> So now I've stripped down the kernel quite a lot and added as many >> debug options that seem to make sense to me. No ACPI at all and no >> network device driver except for b43, including low eneregy optins, >> and PIO mode. If I leave out the b43 driver the kernel boots just >> fine. If I include it I get the following on the screen: >> >> >> http://oncaphillis.net/IMG_0214.JPG >> >> So it seems to me it doesn't even reach the loading of p43.ko >> but gets stuck in the cfg80211 layer. > > Well, there's a TSC message after that, which is completely unrelated to > cfg80211. > It could possibly be sleeping in the CRDA call and executes the TSC stuff in > parallel (given that the TSC message is only a few microseconds later). > I don't really know how parallelization is done here (if any). > >> Any further hints how to proceed in debugging this. > > Do you have cfg80211/mac80211 built-in or as modules? The TSC message after > the cfg80211 message might indicate that it's built-in.
It used to be build in, but I successfully built and inserted all components (including b43) as a module (see my previous message ). > > It's basically impossible to tell what's going on here. You could do a git > bisection > to track down the bad commit. > > _______________________________________________ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
