[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: machine crash



The fact that it happens at 6:25 AM tells me it's probably a cron job.  In a
default Debian installation, the files in /etc/cron.daily/ are run every day
at 6:25 AM.

I would look there first, to try to find the process that is causing
problems.

-- Kevin

----- Original Message -----
From: Petr [Dingo] Dvorak
To: debian-user mailing list
Sent: Friday, June 08, 2001 11:51 AM
Subject: machine crash


Hey there,

Today morning my machine locked up after 8 days of flawless run, before that
it
went down twice always between 6 and 6:30 am, before that it ran for over 80
days since the last power outage, i can't for the life of me figure out what
is
going on, the message on console display said something about 'unable to
handle
kernels null pointer at 0x00000004'.

the kernel version is 2.2.18pre21, it was installed off of official debian
cd's
[2000-12-07]

this is what was in messages log [i stripped rest of the dates]:

Jun  8 06:25:14 warlord kernel:

Oops: 0002
CPU:    0
EIP:    0010:[fat_clear_inode+26/36]
EFLAGS: 00010282
eax: 00000000   ebx: c1336000   ecx: c1336000   edx: 00000000
esi: 00001e79   edi: c082feac   ebp: c0001400   esp: c082fe70
ds: 0018   es: 0018   ss: 0018
Process find (pid: 2969, process nr: 86, stackpage=c082f000)
Stack: c1336000 c10908e4 c013426d c1336000 c082feac 00022684 ffffebdb
c01344da
       c082feac c02b67d8 00022684 c030314c c0001400 c314e08e c0145fb8
c3177e68
       c1dfa290 c0134528 00000c03 c02b67d8 00022684 c030314c c0001400
c53dae80
Call Trace: [dispose_list+29/80] [try_to_free_inodes+214/252]
[ext2_find_entry+416/684] [grow_inodes+32/408] [get_new_inode+185/292]
[iget4+113/124] [iget+17/24]
        [ext2_lookup+90/140] [real_lookup+77/160] [lookup_dentry+268/428]
[__namei+38/88] [sys_newlstat+13/96] [system_call+52/56]
Code: 89 50 04 89 02 5b c3 8d 76 00 53 8b 5c 24 08 8b 83 90 00 00


I'm at loss here, the log from messages file looks like it had something to
do
with the drives and the one that was on console looked like it was null
pointer, beside that i have no idea how to find out which process it was or
anything,

any help would be appreciated.


                                                Dingo.


                                      ).|.(
                                    '.'___'.'
                                   ' '(>~<)' '
   -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-ooO-=(_)=-Ooo-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Petr [Dingo] Dvorak                                 dingo@pdragon.org
    Coder - Purple Dragon MUD                       pdragon.org port 3333
   -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-[ 369D93 ]=-=-
      Debian version 2.2.18pre21, up 9 min, 4 users, load average: 0.43
   -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-



--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org




Reply to: