From: Ian Kumlien <pomac@vapor.com>
To: Linux-kernel@vger.kernel.org
Subject: [OOPS] ANSI/IEEE 802.2 LLC type 2 Support
Date: Sat, 27 Aug 2005 23:45:12 +0200 [thread overview]
Message-ID: <1125179112.24161.11.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
Hi,
Today my firewall just up and oopsed after about a month of uptime.
It has to be something new that was introduced to my lan or so since
it's the local interface that oopsed... I generally don't care about
this part but i thought that it might be good to inform you guys.
The option mentioned in the subject is the only thing my other boxes
don't have (ie all other boxes has just about the same kernel config)
and judging from the Call trace i assumed it was that.
The oops message was captured using a digital camera (and yes that
monitor is dirty =))
http://pomac.netswarm.net/misc/kernel-panic.jpg
PS. I could recreate the oops severaltimes until i put eth1 down, but i
haven't been able to since then (switched to rc7 without the LLC
option).
DS.
--
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2005-08-27 21:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1125179112.24161.11.camel@localhost \
--to=pomac@vapor.com \
--cc=Linux-kernel@vger.kernel.org \
/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