Kernel NULL pointer, over my head...

Kernel NULL pointer, over my head...

[Jamie Harris]

Morning all,

Sorry for the big cross post but I don't have the first clue about where
to send this one.  I get this from my stock 2.2.18 kernel in
/var/log/syslog:

May  1 05:27:36 mnemosyne kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000000
May  1 05:27:36 mnemosyne kernel: current->tss.cr3 = 00362000, %cr3 =
00362000
May  1 05:27:36 mnemosyne kernel: *pde = 00000000
May  1 05:29:36 mnemosyne kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000000
May  1 05:29:36 mnemosyne kernel: current->tss.cr3 = 036dc000, %cr3 =
036dc000
May  1 05:29:36 mnemosyne kernel: *pde = 00000000
May  1 05:30:28 mnemosyne kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000000
May  1 05:30:28 mnemosyne kernel: current->tss.cr3 = 00ca7000, %cr3 =
00ca7000
May  1 05:30:28 mnemosyne kernel: *pde = 00000000


This time it seemed to be caused by running tar on a file, but I've
noticed a similar error in the past but they've never made anything fall
over.  The tar process appeared to die but then again so did the telnet
session so I don't know in what order they went down.  I tried 3 times
just to check it wasn't a fluke...  What other details would be useful??

Cheers Jamie...

PS I'm not on the linux-kernel list so please post to me directly...


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 ***    Slowly and surely the UNIX crept up on the Nintendo user...    ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/ED d-(++) s:+ a- C+++>++++$ U+++>$ P++++ L+++>+++++ E+(---) W++ N o?
K? w(++++) O- M V? PS PE? Y PGP- t+ 5 X- R- tv- b++ DI++ D+++ G e++ h*
r++>+++ y+++
------END GEEK CODE BLOCK------

More!! Kernel NULL pointer, over my head...

[Jamie Harris]

OK...

a 'tar xvfz myFile.tar.gz' results in the following in /var/log/syslog

May  1 05:58:11 mnemosyne kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000000
May  1 05:58:11 mnemosyne kernel: current->tss.cr3 = 01e55000, %cr3 =
01e55000
May  1 05:58:11 mnemosyne kernel: *pde = 00000000

however this time I'm using a different file.  I can however sucessfully
do the following
	gzip -d ; tar xvf myFile.tar.gz

Don't know if that gives anyone any hints...  I haven't changed any
software on the system recently so I don't think it can be a bad tar or
gzip binary.  I get the same for root and non-privileged users.

thanks again.

Jamie...

On Tue, 1 May 2001, Jamie Harris wrote:

> Morning all,
>
> Sorry for the big cross post but I don't have the first clue about where
> to send this one.  I get this from my stock 2.2.18 kernel in
> /var/log/syslog:
>
> May  1 05:27:36 mnemosyne kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000000
> May  1 05:27:36 mnemosyne kernel: current->tss.cr3 = 00362000, %cr3 =
> 00362000
> May  1 05:27:36 mnemosyne kernel: *pde = 00000000
> May  1 05:29:36 mnemosyne kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000000
> May  1 05:29:36 mnemosyne kernel: current->tss.cr3 = 036dc000, %cr3 =
> 036dc000
> May  1 05:29:36 mnemosyne kernel: *pde = 00000000
> May  1 05:30:28 mnemosyne kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000000
> May  1 05:30:28 mnemosyne kernel: current->tss.cr3 = 00ca7000, %cr3 =
> 00ca7000
> May  1 05:30:28 mnemosyne kernel: *pde = 00000000
>
>
> This time it seemed to be caused by running tar on a file, but I've
> noticed a similar error in the past but they've never made anything fall
> over.  The tar process appeared to die but then again so did the telnet
> session so I don't know in what order they went down.  I tried 3 times
> just to check it wasn't a fluke...  What other details would be useful??
>
> Cheers Jamie...
>
> PS I'm not on the linux-kernel list so please post to me directly...

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 ***    Slowly and surely the UNIX crept up on the Nintendo user...    ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/ED d-(++) s:+ a- C+++>++++$ U+++>$ P++++ L+++>+++++ E+(---) W++ N o?
K? w(++++) O- M V? PS PE? Y PGP- t+ 5 X- R- tv- b++ DI++ D+++ G e++ h*
r++>+++ y+++
------END GEEK CODE BLOCK------

Re: More!! Kernel NULL pointer, over my head... (DOH!)

[Jamie Harris]

Erin Jones wrote:
> 
> are you sure this works:
> gzip -d ; tar xvf myFile.tar.gz?????
> shouldn't it be
> gzip -cd myFile.tar.gz | tar xvf -

I think I have proven myself unworth of your help by producing the
above, obvious to everyone, else cockup.  As unworthy as I am, here I go
again...

As suggested by Phil on Bristol LUG I've fsck'd my filesystems.  Got
something interesting in the process though.  Booted using some
Slackware 7.1 (2.2.16) disks to fsck / and got similar errors to those
already described :(  Yet the system came up...  As there wasn't any
swap configured I can pretty much rule that out, and I had not attempted
to mount any file systems...  These are the same disks I used to carry
out the inital install and I did't get problems then...  I am starting
to think Hardware but have been told that a copy of ksymoops might shed
some more light...

Thanks again.


Jamie...

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 ***    Slowly and surely the UNIX crept up on the Nintendo user...   
***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-----BEGIN GEEK CODE BLOCK-----Version: 3.1
GCS/ED d-(++) s:+ a- C+++>++++$ U+++>$ P++++ L+++>+++++ E+(---) W++ N o?
K? w(++++) O- M V? PS PE? Y PGP- t+ 5 X- R- tv- b++ DI++ D+++ G e++ h*
r++>+++ y+++
------END GEEK CODE BLOCK------