From: "Gary White (Network Administrator)" <admin@netpathway.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.5-ac16 kernel panic
Date: Wed, 20 Jun 2001 17:59:34 -0500 [thread overview]
Message-ID: <3B312AD6.38D20AFB@netpathway.com> (raw)
In-Reply-To: <3B3116A3.E89360DE@netpathway.com> <E15CqDS-0000DG-00@the-village.bc.nu>
Sorry I was so long getting back. I had to step out
of the office for a minute. Here is the debug message.
Initializing RT netlink socket
kernel BUG at ioremap.c:73
invalid operand: 0000
> > 2.4.5-ac16 patch applied to clean 2.4.5 tree. 2.4.5-ac15 boots
> > with no problem.
>
> Yes I screwed up the bootflag handling
>
> > EIP: 0010:[<c01112cf>]
> > EFLAGS: 00010286
> > eax: 007ec000 ebx: e0800000 ecx: 3f7ec000 edx: c0101000
>
> Can you build with kernel debug enabled and then say Y to all the debug options
> and give me the BUG() message where that next build dies. I think I know whats
> up I want to be sure
>
> -
> 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/
--
Gary White Network Administrator
admin@netpathway.com Internet Pathway
Voice 601-776-3355 Fax 601-776-2314
next prev parent reply other threads:[~2001-06-20 23:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 17:31 Linux 2.4.5-ac16 Alan Cox
2001-06-19 20:01 ` Linux 2.4.5-ac16 (linux_booted_ok: only on Intel implemented) Martin Frey
2001-06-19 20:22 ` Alan Cox
2001-06-20 21:33 ` Linux 2.4.5-ac16 kernel panic Gary White (Network Administrator)
2001-06-20 22:12 ` Alan Cox
2001-06-20 22:59 ` Gary White (Network Administrator) [this message]
2001-06-21 0:48 ` Gav
2001-06-21 11:42 ` Linux 2.4.5-ac16 Christoph Rohland
[not found] <E15Czfx-0000x5-00@the-village.bc.nu>
2001-06-21 15:08 ` Linux 2.4.5-ac16 kernel panic Gary White (Network Administrator)
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=3B312AD6.38D20AFB@netpathway.com \
--to=admin@netpathway.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;
as well as URLs for NNTP newsgroup(s).