diff options
author | Felix Fietkau <nbd@openwrt.org> | 2010-07-10 00:48:37 +0000 |
---|---|---|
committer | Felix Fietkau <nbd@openwrt.org> | 2010-07-10 00:48:37 +0000 |
commit | fbff44c98ad73009c9f3f17521ad8ac1d9453607 (patch) | |
tree | 5172e568b9b6d17439e487e0af60a9bea2e6d99f /target/linux/brcm47xx/patches-2.6.33/211-b44_timeout_spam.patch | |
parent | 482557bc886ac4f031f4e784e2466367fd47d65c (diff) | |
download | mtk-20170518-fbff44c98ad73009c9f3f17521ad8ac1d9453607.zip mtk-20170518-fbff44c98ad73009c9f3f17521ad8ac1d9453607.tar.gz mtk-20170518-fbff44c98ad73009c9f3f17521ad8ac1d9453607.tar.bz2 |
Get rid of the b44 'BUG! Timeout waiting for bit 80000000 of register 428 to clear.' spam.
more and more users are getting confused by this, and consider it a regression in brcm47xx,
because brcm-2.4 was not showing this message. It's not particularly interesting for debugging,
most of the time it only happens because of an unconnected port.
SVN-Revision: 22110
Diffstat (limited to 'target/linux/brcm47xx/patches-2.6.33/211-b44_timeout_spam.patch')
-rw-r--r-- | target/linux/brcm47xx/patches-2.6.33/211-b44_timeout_spam.patch | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/target/linux/brcm47xx/patches-2.6.33/211-b44_timeout_spam.patch b/target/linux/brcm47xx/patches-2.6.33/211-b44_timeout_spam.patch new file mode 100644 index 0000000..dbd46ae --- /dev/null +++ b/target/linux/brcm47xx/patches-2.6.33/211-b44_timeout_spam.patch @@ -0,0 +1,17 @@ +--- a/drivers/net/b44.c ++++ b/drivers/net/b44.c +@@ -189,11 +189,13 @@ static int b44_wait_bit(struct b44 *bp, + udelay(10); + } + if (i == timeout) { +- printk(KERN_ERR PFX "%s: BUG! Timeout waiting for bit %08x of register " ++#if 0 ++ printk(KERN_DEBUG PFX "%s: BUG! Timeout waiting for bit %08x of register " + "%lx to %s.\n", + bp->dev->name, + bit, reg, + (clear ? "clear" : "set")); ++#endif + return -ENODEV; + } + return 0; |