[udo: Re: PROBLEM: "parport0: Timed out" another dump with 2.4.0-test2]

[Udo Held]

----- Forwarded message from udo -----

Date: Thu, 29 Jun 2000 18:43:25 +0200
To: Tim Waugh <[e-mail]>
Subject: Re: PROBLEM: "parport0: Timed out" another dump with 2.4.0-test2
User-Agent: Mutt/1.2i
In-Reply-To: <[e-mail]>; from [e-mail] on Thu, Jun 29, 2000 at 05:25:12PM +0100

Hi!

On Thu, Jun 29, 2000 at 05:25:12PM +0100, Tim Waugh wrote:
> On Thu, Jun 29, 2000 at 06:16:07PM +0200, Udo Held wrote:
> 
> > I'm not able to use it. While compiling it, it throws out errors and
> > the kerneldump.
> Just compiling the modules?  I.e. no vmware modules loaded at all
> while the oops happens?

If I look closer it seems to be while loading. I pasted some
information while doing vmware-config.pl

Building the vmmon module.

make: Entering directory `/tmp/vmware-config0/vmmon-only'
make[1]: Entering directory `/tmp/vmware-config0/vmmon-only'
make[2]: Entering directory `/tmp/vmware-config0/vmmon-only/driver-2.4.0-test3'
make[2]: Leaving directory `/tmp/vmware-config0/vmmon-only/driver-2.4.0-test3'
make[2]: Entering directory `/tmp/vmware-config0/vmmon-only/driver-2.4.0-test3'
.././linux/driver.c:123: warning: initialization from incompatible pointer type
.././linux/driver.c:124: warning: initialization from incompatible pointer type
.././linux/driver.c:126: warning: initialization from incompatible pointer type
.././linux/driver.c:128: warning: initialization from incompatible pointer type
{standard input}: Assembler messages:
{standard input}:8: Warning: Ignoring changed section attributes for .modinfo
make[2]: Leaving directory `/tmp/vmware-config0/vmmon-only/driver-2.4.0-test3'
make[1]: Leaving directory `/tmp/vmware-config0/vmmon-only'
make: Leaving directory `/tmp/vmware-config0/vmmon-only'
The module loads perfectly in the running kernel.
Building the vmnet module.

make: Entering directory `/tmp/vmware-config0/vmnet-only'
driver.c:104: warning: initialization from incompatible pointer type
driver.c:105: warning: initialization from incompatible pointer type
driver.c:107: warning: initialization from incompatible pointer type
driver.c:108: warning: initialization from incompatible pointer type
driver.c:110: warning: initialization from incompatible pointer type
driver.c:112: warning: initialization from incompatible pointer type
{standard input}: Assembler messages:
{standard input}:8: Warning: Ignoring changed section attributes for .modinfo

Starting VMware services:
   Virtual machine monitor                                             done
   Virtual ethernet                                                    done
   Bridged networking on /dev/vmnet0Unable to handle kernel NULL pointer dereference at virtual address 0000005d
 printing eip:
c884c2b5
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c884c2b5>]
EFLAGS: 00010286
eax: 00000001   ebx: c247aa20   ecx: c7e56d40   edx: c247aa20
esi: 00000000   edi: c2c57380   ebp: 00000001   esp: c31f5f58
ds: 0018   es: 0018   ss: 0018
Process vmnet-bridge (pid: 4785, stackpage=c31f5000)
Stack: c247aa20 00000000 c0120604 00000000 bfffc000 c75ced40 c012eb83 c012eb74
       c247aa20 00000001 00000003 c011b068 c247aa20 c2c57380 c75ced40 c31f4000
       00000100 bffffd40 c2c574a0 c011b681 c2c57380 c31f4000 400f2ddc 00000001
Call Trace: [<c0120604>] [<c012eb83>] [<c012eb74>] [<c011b068>] [<c011b681>] [<c011b7ee>] [<c010ae54>]
Code: 8b 58 5c 85 db 75 1c 83 c4 f4 68 80 f1 84 c8 e8 a3 cb 8c f7
                                                                      failed
   Host-only networking on /dev/vmnet1 (background)                    done

If you want I can do the ksymoops again.

Cheers
Udo

----- End forwarded message -----