Messages in this thread |  | | Date | Wed, 15 Nov 2006 21:51:03 -0800 | From | Ray Lee <> | Subject | Re: bcm43xx regression 2.6.19rc3 -> rc5, rtnl_lock trouble? |
| |
Larry Finger wrote: > Ray Lee wrote: >> Michael Buesch wrote: >>> On Wednesday 15 November 2006 20:01, Ray Lee wrote: >>>> Suggestions? Requests for <shudder> even more info? >>> Yeah, enable bcm43xx debugging. >> >> Sigh, didn't even think to look for that. Okay, enabled and compiling >> a new kernel. This will take a few days to trigger, if the pattern holds, so >> in the meantime, any *other* thoughts? > > Which chip and revision do you have? Send me your equivalent of the line > "bcm43xx: Chip ID 0x4306, rev 0x2".
bcm43xx: Chip ID 0x4306, rev 0x3
Also, another thing I wasn't clear about in my first email was that the netdev watchdog timeouts are new with rc5:
$ zgrep 'NETDEV WATCH' /var/log/messages{,.0,.1.gz} | cut -d: -f2| cut -c 1-6 | uniq -c 1249 Nov 13 6 Nov 6 1 Nov 7 3 Nov 8 2 Nov 9 5717 Nov 10 5652 Nov 11 5 Oct 29 3 Oct 30 3 Oct 31 4 Nov 1 1 Nov 2 1 Nov 3
I booted into 2.6.19-rc5 on November 10th. Previous to that was 2.6.19-rc3. There really does seem to be something suspicious with that patch, yes?
Thanks,
Ray - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |