From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Nicolas Ross" <rossnick-lists@cybercat.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unable to handle kernel NULL pointer dereference
Date: Mon, 19 Jul 2004 21:07:06 -0700 [thread overview]
Message-ID: <20040719210706.0ccdeb80.rddunlap@osdl.org> (raw)
In-Reply-To: <033601c46dc5$dd5470a0$1a07a8c0@civic2k>
On Mon, 19 Jul 2004 15:23:25 -0400 Nicolas Ross wrote:
| Hi all !
|
| I have a firewall box, with a vanilla kernel from kernel.org. I've tried
| with 2.4.19 and 2.4.24. The system is RedHat 7.3 (it does the same thing
| with 8.0, and gcc 3)
|
| The kernel is pretty straigh-up, not much options, some net modules,
| iptables etc.
|
| The only thing out of the ordinary is a custom net/core/dev.c file to
| support a bandwith management module, wich isn't gpl and is pre-compiled.
|
| When issuing commands to configure the bandwith manager, I get :
|
| Unable to handle kernel NULL pointer dereference at virtual address 00000000
| printing eip:
| 00000000
| *pde = 00000000
| Oops: 0000
| CPU: 0
| EIP: 0010:[<00000000>] Tainted: P
What module makes it tainted? Can you reproduce problem without it?
| EFLAGS: 00010086
| eax: ddf5f948 ebx: ddf5e000 ecx: ddf5f980 edx: de9db400
| esi: c0000000 edi: ddf5f986 ebp: ddf5f9b8 esp: ddf5f92c
| ds: 0018 es: 0018 ss: 0018
| Process bwmgr (pid: 1120, stackpage=ddf5f000)
| Stack: e08c4431 de9db400 ddf5f980 00008946 fffffec4 11860f1f 00000000
| 0000000a
| 00000000 00000001 00000000 00000000 00000000 00000000 00000000
| 00000000
| 00000000 00bd0c00 00000000 00000000 90c8ebff 6e616c76 e08d0032
| defec800
| Call Trace: [<e08c4431>] [<e08d0032>] [<e08d58d7>] [<e08d68b5>]
| [<c012b346>]
| [<c0120ea3>] [<c012b346>] [<c012995a>] [<c0120ea3>] [<c0120f19>]
| [<c010f303>]
| [<c028407e>] [<e08d95f6>] [<c01216de>] [<c010f1b0>] [<c01071b4>]
| [<c0282bab>]
| [<c010f1b0>] [<c01071b4>] [<c0282bab>] [<e08af1f7>] [<e08c33ec>]
| [<c01a3a17>]
| [<c023af54>] [<c023b138>] [<c023315a>] [<c013e413>] [<c01070a3>]
|
| Code: Bad EIP value.
|
| After that the system still responds but isn't much usable, I have to
| reboot, not practicall...
|
| All of this was working with the exact same setup, but on a different MB,
| and kernel 2.4.19.
|
| Any hints on the source of this exception ?
Please run this oops message thru ksymoops and resend it.
See linux/Documentation/ oops-tracing.txt for details.
--
~Randy
next prev parent reply other threads:[~2004-07-20 4:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 19:23 Nicolas Ross
2004-07-20 4:07 ` Randy.Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-01 18:44 Eduard <master^shadow> Roccatello
2004-01-02 1:32 ` Greg KH
2004-01-03 9:47 ` Michael Stucki
2004-01-07 21:06 ` Greg KH
2002-04-05 7:42 Umaid Singh Rajpurohit
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=20040719210706.0ccdeb80.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rossnick-lists@cybercat.ca \
/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
Powered by JetHome