On Thursday 29 June 2006 17:22, Larry Finger wrote: > Michael Buesch wrote: > > On Thursday 29 June 2006 10:24, Paul Collins wrote: > >> Michael Buesch <[EMAIL PROTECTED]> writes: > >> > >>> On Monday 26 June 2006 14:43, Michael Buesch wrote: > >>>> Try to get more logs. > >>>> I suggest to do a netconsole for logging. > >>> Also note that current softmac trees have a patch missing. > >>> It seems it got lost somewhere after my merge request. > >>> I already contacted John in private for this, but no reply, yet. > >>> The patch is attached. Maybe it fixes your issue. > >> On a preempt kernel I can trigger the hang easily, > > > > How? I need to reproduce it to get a clue and fix it. :) > > I have no idea where it might come from (I don't even know > > what exactly happens). > > > > And please provide a _full_ dmesg log without comments inbetween > > after triggering the hang (with a full Controller Restart cycle). > > > > I am having what I think is a similar problem, although my system does not > hang. I cannot send dmesg > output as the buffer is quickly filled with the channel assertion messages > you see below, but here > is the relevant section of /var/log/messages. > > Jun 29 01:22:08 larrylap kernel: NETDEV WATCHDOG: wlan0: transmit timed out > Jun 29 01:22:08 larrylap kernel: bcm43xx: Controller RESET (TX timeout) ... > Jun 29 01:22:08 larrylap kernel: ACPI: PCI interrupt for device 0000:02:00.0 > disabled > Jun 29 01:22:08 larrylap kernel: PCI: Enabling device 0000:02:00.0 (0000 -> > 0002) > Jun 29 01:22:08 larrylap kernel: ACPI: PCI Interrupt 0000:02:00.0[A] -> Link > [LNKA] -> GSI 11 > (level, low) -> IRQ 11 > Jun 29 01:22:08 larrylap kernel: bcm43xx: Chip ID 0x4306, rev 0x2 > Jun 29 01:22:08 larrylap kernel: bcm43xx: Number of cores: 6 > Jun 29 01:22:08 larrylap kernel: bcm43xx: Core 0: ID 0x800, rev 0x2, vendor > 0x4243, enabled > Jun 29 01:22:08 larrylap kernel: bcm43xx: Core 1: ID 0x812, rev 0x4, vendor > 0x4243, enabled > Jun 29 01:22:08 larrylap kernel: bcm43xx: Core 2: ID 0x80d, rev 0x1, vendor > 0x4243, enabled > Jun 29 01:22:08 larrylap kernel: bcm43xx: Core 3: ID 0x807, rev 0x1, vendor > 0x4243, disabled > Jun 29 01:22:08 larrylap kernel: bcm43xx: Core 4: ID 0x804, rev 0x7, vendor > 0x4243, enabled > Jun 29 01:22:08 larrylap kernel: bcm43xx: Core 5: ID 0x812, rev 0x4, vendor > 0x4243, disabled > Jun 29 01:22:08 larrylap kernel: bcm43xx: Ignoring additional 802.11 core. > Jun 29 01:22:08 larrylap kernel: bcm43xx: PHY connected > Jun 29 01:22:08 larrylap kernel: bcm43xx: Detected PHY: Version: 1, Type 2, > Revision 1 > Jun 29 01:22:08 larrylap kernel: bcm43xx: Detected Radio: ID: 2205017f > (Manuf: 17f Ver: 2050 Rev: 2) > Jun 29 01:22:08 larrylap kernel: bcm43xx: Radio turned off > Jun 29 01:22:08 larrylap kernel: bcm43xx: Radio turned off > Jun 29 01:22:08 larrylap kernel: bcm43xx: Controller restarted > Jun 29 01:23:08 larrylap kernel: bcm43xx: ASSERTION FAILED (channel >= 1 && > channel <= 14) at: > drivers/net/wireless/bcm43xx/bcm43xx_radio.c:79:channel2freq_bg()
WTF is that??? How is that possible to happen? Are you sure you have an unmodified tree? > Jun 29 01:24:08 larrylap kernel: bcm43xx: ASSERTION FAILED (channel >= 1 && > channel <= 14) at: > drivers/net/wireless/bcm43xx/bcm43xx_radio.c:79:channel2freq_bg() > Jun 29 01:25:08 larrylap kernel: bcm43xx: ASSERTION FAILED (channel >= 1 && > channel <= 14) at: > drivers/net/wireless/bcm43xx/bcm43xx_radio.c:79:channel2freq_bg() > > These continue until the interface is brought down. My kernel is > 2.6.17-g569df601-dirty from > Linville's tree, is preemptible and all recent patches are installed. > > Larry > > -- Greetings Michael. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
