On Fri, 2007-09-07 at 17:38 -0400, Rob Hussey wrote: > I took some pictures of the screen with DEBUG_KOBJECT enabled. It's > tough to get it all though, since the messages don't really fit on one > screen. I played around with the vga= line, and was able to get the > scrolling to stop at different points (the stack trace and all appears > about 1 msec after booting, so this was my only choice). The pictures > can be found here: > http://www.healthcarelinen.com/misc/ > > These two are probably the best: > http://www.healthcarelinen.com/misc/101_1988.jpg > http://www.healthcarelinen.com/misc/101_1992.jpg > > Hopefully the pictures have what you need. The line kobject phy0: registering. parent: <NULL>, set: devices points out what I thought was the problem. However, I don't understand why it happens. In rt2500pci we see: rt2500pci_probe_hw_mode: SET_IEEE80211_DEV(rt2x00dev->hw, &rt2x00dev_pci(rt2x00dev)->dev); which expands to set_wiphy_dev(hw->wiphy, dev); which expands to wiphy->dev.parent = dev; it is called from rt2500pci_probe_hw which in turn is called from rt2x00lib_probe_dev, which later calls rt2x00lib_probe_hw which is what calls ieee80211_register_hw which is the path leading to the bug. But there's no way &rt2x00dev_pci(rt2x00dev)->dev can be NULL! Sorry, I don't see right now how this can happen. Anybody have a better idea? johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
