archive mirror
 help / color / mirror / Atom feed
From: jjs <>
To: linux kernel <>
Cc: Andrew Morton <>
Subject: 2.5.68-mm2+e100=trouble
Date: Fri, 25 Apr 2003 10:58:13 -0700	[thread overview]
Message-ID: <> (raw)

Hello -

This may be of interest...

kernel: 2.5.68-mm2

Linux distro: Red Hat 8.0 + updates

Celeron 1.2 Ghz on Intel Motherboard
512 MB RAM, 2x e100 ethernet

2.5.68-mm2 initially would not boot for me, and I noticed that
it was dying at the point where it was loading the e100 driver -

I booted -mm2 again specifying the eepro100 driver instead
and it came up fine.

To get another look at the e100 problem, I shut down networking
and removed the eepro100 module - all good, so far -

Then I said "modprobe e100" and the following oops occurred:

-------------------------- snip ------------------------------

Unable to handle kernel paging request at virtual address c048f190
 printing eip:
*pde = 00103027
*pte = 0048f000
Oops: 0000 [#1]
CPU:    0
EIP:    0060:[<c048f190>]    Not tainted VLI
EFLAGS: 00010286
EIP is at apply_alternatives+0x0/0xf0
eax: e0e215be   ebx: e0e0f618   ecx: 0000008b   edx: 00000076
esi: c03df35b   edi: e0e0f36e   ebp: d566defc   esp: d566dee0
ds: 007b   es: 007b   ss: 0068
Process modprobe (pid: 1524, threadinfo=d566c000 task=d58b8a00)
Stack: c011abe4 e0e21548 e0e215be e0e0f2d2 e0dff000 e0e0f3e8 000004d8 
       c0143f2b e0dff000 e0e0f3e8 e0e26280 00000018 e0e26280 00000001 
       00000000 00000500 000004d8 000002d0 e09d7000 e0e26280 00000013 
Call Trace:
 [<c011abe4>] module_finalize+0x94/0xa0
 [<c0143f2b>] load_module+0x6cb/0x910
 [<c014420b>] sys_init_module+0x9b/0x370
 [<c016df05>] sys_read+0x45/0x60
 [<c010a51b>] syscall_call+0x7/0xb

Code:  Bad EIP value.

             reply	other threads:[~2003-04-25 17:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25 17:58 jjs [this message]
2003-04-25 19:38 ` 2.5.68-mm2+e100=trouble Andrew Morton
2003-04-25 21:15 ` Fixed (Was: 2.5.68-mm2+e100=trouble) jjs
2003-04-25 18:23 2.5.68-mm2+e100=trouble jjs

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).