X-POP3-Rcpt: mlehmann AT universe DOT sgh-net DOT de
Message-ID: <34D047B1.CFB36DA@medchem2.pharmazie.uni-halle.de>
29 Jan 1998 10:11:14 +0100
From: Mathias Weigt <p5iba AT medchem2 DOT pharmazie DOT uni-halle DOT de>
X-Mailer: Mozilla 4.03 [de] (Win95; I)
MIME-Version: 1.0
To: beastium <beastium-list AT Desk DOT nl>
Subject: Problems with the Kernel DEC driver
References: <Pine DOT LNX DOT 3 DOT 96 DOT 980128185755 DOT 782A-100000 AT sanitarium DOT fdf DOT net> <19980129024043 DOT 04684 AT cerebro DOT laendle>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: Marc Lehmann <pcg AT goof DOT com>
Status: RO
X-Status: A
Content-Length: 2025
Lines: 48

Servus !

I compiled Kernel -2.0.33 and it seems to work fine.
But there is the driver fo my DEC PCI network adapter which refuses to
work.
If I compile it into the kernel the kernel freezes at boottime.
When compiling as a module (de4x5.o) I get the following message when I
try to load it:

Jan 29 10:01:21 MadXen kernel: loading device 'eth0'...
Jan 29 10:01:21 MadXen kernel: Unable to handle kernel paging request at
virtual address f3344544
Jan 29 10:01:21 MadXen kernel: current->tss.cr3 = 03977000, Xr3 =
03977000
Jan 29 10:01:21 MadXen kernel: *pde = 00000000
Jan 29 10:01:21 MadXen kernel: Oops: 0000
Jan 29 10:01:21 MadXen kernel: CPU:    0
Jan 29 10:01:21 MadXen kernel: EIP:    0010:[<04837a7c>]
Jan 29 10:01:21 MadXen kernel: EFLAGS: 00010206
Jan 29 10:01:21 MadXen kernel: eax: 03979e8c   ebx: 00000000   ecx:
00000005   edx: 00000005
Jan 29 10:01:21 MadXen kernel: esi: 03979e8c   edi: 33344544   ebp:
03979e8c   esp: 03979e5c
Jan 29 10:01:21 MadXen kernel: ds: 0018   es: 0018   fs: 002b   gs:
002b   ss: 0018
Jan 29 10:01:21 MadXen kernel: Process insmod (pid: 81, process nr: 10,
stackpage=03979000)
Jan 29 10:01:21 MadXen kernel: Stack: 0008c9f0 00006100 00000006
0008c9f0 ffffffff 00000046 0016ffff 00002300
Jan 29 10:01:21 MadXen kernel:        00000046 00001000 03979e94
00000000 3f3f5f5f 0016003f 0483b984 0483b98a
Jan 29 10:01:21 MadXen kernel:        0483b990 0483b996 0483b99c
001b7c67 04834b7b 03979ed8 00006d80 0008c9f0
Jan 29 10:01:21 MadXen kernel: Call Trace: [n_tty_ioctl+618/1143]
[show_floppy+280/617] [<0483b984>] [<0483b98a>] [<0483b990>]
[<0483b996>] [<0483b99c>]
Jan 29 10:01:21 MadXen kernel:        [<04834b7b>] [<0483b2ba>]
[register_netdev+97/230] [<04833000>] [<0483b1d4>] [<0483b1f7>]
[sys_init_module+926/988] [<04833000>]
Jan 29 10:01:21 MadXen kernel:        [<0483b1c0>] [<0483b20f>]
[do_page_fault+0/792] [error_code+64/80] [system_call+85/128]
Jan 29 10:01:21 MadXen kernel: Code: f3 a6 74 0a 96 46 80 78 ff 00 75 ed
31 c0 85 c0 75 08 43 83

What can I do ?

Mathias Weigt