From: Michael Buesch <mb@bu3sch.de>
To: Olaf Hering <olh@suse.de>
Cc: Erik Mouw <erik@harddisk-recovery.com>, netdev@vger.kernel.org
Subject: Re: Linux v2.6.17-rc4
Date: Fri, 12 May 2006 22:54:19 +0200 [thread overview]
Message-ID: <200605122254.19615.mb@bu3sch.de> (raw)
In-Reply-To: <20060512112318.GA2115@suse.de>
On Friday 12 May 2006 13:23, you wrote:
> > > I got assertion failures in the bcm43xx driver:
> > >
> > > bcm43xx: Chip ID 0x4318, rev 0x2
> >
> > That is expected an non-fatal.
>
> Is this one in the same category?
> [ 79.087115] bcm43xx: WARNING: Writing invalid LOpair (low: 46, high: 104, index: 123)
> [ 47.361435] bcm43xx: Chip ID 0x4318, rev 0x2
^^^^^^
Yes, same problem.
--
Greetings Michael.
next prev parent reply other threads:[~2006-05-12 20:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 23:44 Linux v2.6.17-rc4 Linus Torvalds
2006-05-12 6:39 ` Andrew Morton
2006-05-12 11:39 ` Stefan Schweizer
2006-05-15 5:57 ` Benjamin Herrenschmidt
2006-05-12 10:24 ` Erik Mouw
2006-05-12 10:44 ` Michael Buesch
2006-05-12 11:23 ` Olaf Hering
2006-05-12 20:54 ` Michael Buesch [this message]
2006-05-12 11:47 ` Erik Mouw
2006-05-12 20:58 ` Michael Buesch
2006-05-12 12:50 ` Andi Kleen
2006-05-12 13:04 ` Johannes Stezenbach
2006-05-12 17:45 ` Jan Engelhardt
2006-05-12 21:19 ` Alistair John Strachan
2006-05-14 7:57 ` Ayaz Abdulla
2006-05-15 5:27 ` Alistair John Strachan
2006-05-20 19:11 ` Alistair John Strachan
2006-05-15 17:49 ` Alan Cox
2006-05-15 18:41 ` [PATCH] slab: Fix kmem_cache_destroy() on NUMA Roland Dreier
2006-05-15 21:47 ` Christoph Lameter
2006-05-16 4:22 ` Pekka Enberg
2006-05-16 11:57 ` Or Gerlitz
2006-05-16 17:09 ` Linux v2.6.17-rc4 Jan Engelhardt
2006-05-16 17:25 ` Jan Engelhardt
2006-05-17 7:53 ` Avuton Olrich
2006-05-17 8:33 ` Avuton Olrich
2006-05-17 9:37 ` Con Kolivas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200605122254.19615.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=erik@harddisk-recovery.com \
--cc=netdev@vger.kernel.org \
--cc=olh@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.