From: Edward Muller <emuller@learningpatterns.com>
To: Pozsar Balazs <pozsy@sch.bme.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Unknown bridge resource
Date: 12 Dec 2001 19:36:31 -0500 [thread overview]
Message-ID: <1008203791.2354.3.camel@akira.learningpatterns.com> (raw)
In-Reply-To: <Pine.GSO.4.30.0112130004310.5686-100000@balu>
In-Reply-To: <Pine.GSO.4.30.0112130004310.5686-100000@balu>
I just upgraded to 2.4.16 today and I noticed the same thing.
I'm using an IBM Thinkpad T20 if it makes a difference.
I'd gladly give more information it it helps.
On Wed, 2001-12-12 at 18:08, Pozsar Balazs wrote:
>
> Hi all,
>
> During boot, i got these two lines in dmesg:
> Unknown bridge resource 0: assuming transparent
> Unknown bridge resource 2: assuming transparent
>
> What do they mean?
>
>
> ps: I noticed these because they are written on the console even if quiet
> mode is on. There was a patch for 2.4-ac, but it seems that it somehow
> lost... :(
>
> --
> Balazs Pozsar
>
> -
> 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/
--
-------------------------------
Edward Muller
Director of IS
973-715-0230 (cell)
212-487-9064 x115 (NYC)
http://www.learningpatterns.com
-------------------------------
next prev parent reply other threads:[~2001-12-13 0:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 23:08 Unknown bridge resource Pozsar Balazs
2001-12-13 0:36 ` Edward Muller [this message]
2001-12-13 2:52 ` Juergen Sawinski
2001-12-13 7:26 ` Pozsar Balazs
2001-12-13 23:14 ` Edward Muller
-- strict thread matches above, loose matches on Subject: below --
2001-12-05 21:41 Unknown Bridge Resource William N. Zanatta
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=1008203791.2354.3.camel@akira.learningpatterns.com \
--to=emuller@learningpatterns.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pozsy@sch.bme.hu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox