From: M Taylor <mctylr@privacy.nb.ca>
To: "Gunnar Widell (ESE)" <Gunnar.Widell@ese.ericsson.se>
Cc: linux-hams@vger.kernel.org
Subject: Re: ax25/baycom/kernel(?) problem.
Date: Tue, 25 Mar 2003 14:12:54 +0000 [thread overview]
Message-ID: <20030325141254.A3089@pull.privacy.nb.ca> (raw)
In-Reply-To: <1F55F6582266314A85A55F6241509B670395F455@Esealnt863.al.sw.ericsson.se>; from Gunnar.Widell@ese.ericsson.se on Tue, Mar 25, 2003 at 08:34:59AM +0100
On Tue, Mar 25, 2003 at 08:34:59AM +0100, Gunnar Widell (ESE) wrote:
> > Something like this-
> > <0>Kernel panic: Aiee, killing interupt handler!
> > In interrupt handler - not syncing
>
> Yes, this is what I get.
> At the last stop last nigth it happened when I did:
>
> ifconfig bcsf0 down
>
> So, why are some 2.4.19 or 2.4.20 kernels working fine?
> Maybe I have too much junk compiled into it...
Unfortunately only your computer knows, and unless you can help
us by giving us more details, all we can do is guess.
Excerpt from the linux kernel mailing list FAQ
<http://www.tux.org/lkml/#s4-3> read
"# How do I post an Oops?"
"I think I found a bug, how do I report it?"
and "What information should go in a bug report?"
and in your linux kernel source:
Documentation/oops-tracing.txt
REPORTING-BUGS
You should also test your system, by running that linux kernel
withOUT AX.25 loaded for a period of time under normal use
conditions, so that you are confident that the problem is AX.25 related
and not a) bad hardware, b) other kernel/userland software problems.
I hope this helps
ve1mct
next prev parent reply other threads:[~2003-03-25 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 7:34 ax25/baycom/kernel(?) problem Gunnar Widell (ESE)
2003-03-25 14:12 ` M Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-24 9:22 Gunnar Widell (ESE)
2003-03-25 1:35 ` Shane Deering
2003-03-25 1:58 ` Bob Nielsen
2003-03-25 2:54 ` Shane Deering
2003-03-25 3:09 ` Andrew Bates
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=20030325141254.A3089@pull.privacy.nb.ca \
--to=mctylr@privacy.nb.ca \
--cc=Gunnar.Widell@ese.ericsson.se \
--cc=linux-hams@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