mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.8-rc2 crashes
Date: Wed, 28 Jul 2004 07:20:21 -0400	[thread overview]
Message-ID: <200407280720.21518.gene.heskett@verizon.net> (raw)
In-Reply-To: <20040727192615.GG12308@parcelfarce.linux.theplanet.co.uk>

Greetings;

I just had another crash/lockup, running 2.6.8-rc2-bk3
At the instant, I was looking thru the menu's of the new
kde3.3-beta2, in the window decoration, themes etc menu,
where it got 14% loaded in a 60 megabyte file and it went
away.

>From the log (the whole Oops section this time):
Jul 28 06:48:50 coyote kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
Jul 28 06:48:50 coyote kernel:  printing eip:
Jul 28 06:48:50 coyote kernel: c0164136
Jul 28 06:48:50 coyote kernel: *pde = 3ce74067
Jul 28 06:48:50 coyote kernel: Oops: 0002 [#1]
Jul 28 06:48:50 coyote kernel: PREEMPT
Jul 28 06:48:50 coyote kernel: Modules linked in: eeprom snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss snd_bt87x snd_intel8
x0 snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd forcedeth sg
Jul 28 06:48:50 coyote kernel: CPU:    0
Jul 28 06:48:50 coyote kernel: EIP:    0060:[<c0164136>]    Not tainted
Jul 28 06:48:50 coyote kernel: EFLAGS: 00010216   (2.6.8-rc2-bk3-nf2)
Jul 28 06:48:50 coyote kernel: EIP is at prune_dcache+0x36/0x1c0
Jul 28 06:48:50 coyote kernel: eax: c0364638   ebx: 00000080   ecx: e85fe134   edx: 00000000
Jul 28 06:48:50 coyote kernel: esi: 00000000   edi: c198b000   ebp: 00000080   esp: c198bef8
Jul 28 06:48:50 coyote kernel: ds: 007b   es: 007b   ss: 0068
Jul 28 06:48:50 coyote kernel: Process kswapd0 (pid: 66, threadinfo=c198b000 task=c1978050)
Jul 28 06:48:50 coyote kernel: Stack: c198bef8 c198bef8 00000080 00000000 c198b000 f7ffea60 c01646df 00000080
Jul 28 06:48:50 coyote kernel:        c013a9ab 00000080 000000d0 0001f03f 021edf00 00000000 00000118 00000000
Jul 28 06:48:51 coyote kernel:        c0363624 00000001 00000007 c0363500 c013bd51 00000020 000000d0 00000000
Jul 28 06:48:51 coyote kernel: Call Trace:
Jul 28 06:48:51 coyote kernel:  [<c01646df>] shrink_dcache_memory+0x1f/0x50
Jul 28 06:48:51 coyote kernel:  [<c013a9ab>] shrink_slab+0x14b/0x190
Jul 28 06:48:51 coyote kernel:  [<c013bd51>] balance_pgdat+0x1b1/0x200
Jul 28 06:48:51 coyote kernel:  [<c013be67>] kswapd+0xc7/0xe0
Jul 28 06:48:51 coyote kernel:  [<c0114570>] autoremove_wake_function+0x0/0x60
Jul 28 06:48:52 coyote kernel:  [<c0103f9e>] ret_from_fork+0x6/0x14
Jul 28 06:48:52 coyote kernel:  [<c0114570>] autoremove_wake_function+0x0/0x60
Jul 28 06:48:52 coyote kernel:  [<c013bda0>] kswapd+0x0/0xe0
Jul 28 06:48:52 coyote kernel:  [<c0102251>] kernel_thread_helper+0x5/0x14
Jul 28 06:48:52 coyote kernel: Code: 89 02 89 49 04 89 09 a1 3c 46 36 c0 0f 18 00 90 ff 0d 44 46
Jul 28 06:48:52 coyote kernel:  <6>note: kswapd0[66] exited with preempt_count 1
Jul 28 06:48:52 coyote kernel:
Jul 28 06:48:52 coyote kernel:  [<c030d2fc>] schedule+0x47c/0x490
Jul 28 06:48:52 coyote kernel:  [<c018797e>] ext3_ordered_writepage+0x10e/0x1c0
Jul 28 06:48:52 coyote kernel:  [<c0139d78>] __pagevec_release+0x28/0x40
Jul 28 06:48:52 coyote kernel:  [<c016ece1>] mpage_writepages+0x1b1/0x350
Jul 28 06:48:52 coyote kernel:  [<c0187870>] ext3_ordered_writepage+0x0/0x1c0
Jul 28 06:48:52 coyote kernel:  [<c0135714>] do_writepages+0x44/0x50
Jul 28 06:48:52 coyote kernel:  [<c016d3b1>] __sync_single_inode+0x71/0x210
Jul 28 06:48:52 coyote kernel:  [<c01860f3>] ext3_put_inode+0x13/0x30
Jul 28 06:48:52 coyote kernel:  [<c016d77e>] sync_sb_inodes+0x16e/0x290
Jul 28 06:48:52 coyote kernel:  [<c016da0e>] sync_inodes_sb+0x7e/0xa0
Jul 28 06:48:52 coyote kernel:  [<c016db3b>] sync_inodes+0x2b/0xa0
Jul 28 06:48:52 coyote kernel:  [<c014e034>] do_sync+0x44/0x80
Jul 28 06:48:52 coyote kernel:  [<c014e07f>] sys_sync+0xf/0x20
Jul 28 06:48:52 coyote kernel:  [<c011653f>] panic+0xff/0x110
Jul 28 06:48:52 coyote kernel:  [<c0118d5f>] do_exit+0x3ff/0x420
Jul 28 06:48:52 coyote kernel:  [<c01114f0>] do_page_fault+0x0/0x519
Jul 28 06:48:52 coyote kernel:  [<c0104968>] die+0xf8/0x100
Jul 28 06:48:52 coyote kernel:  [<c01116cb>] do_page_fault+0x1db/0x519
Jul 28 06:48:52 coyote kernel:  [<c0105dd2>] do_IRQ+0x102/0x1a0
Jul 28 06:48:52 coyote kernel:  [<c030d10e>] schedule+0x28e/0x490
Jul 28 06:48:52 coyote kernel:  [<c01114f0>] do_page_fault+0x0/0x519
Jul 28 06:48:52 coyote kernel:  [<c0104271>] error_code+0x2d/0x38
Jul 28 06:48:52 coyote kernel:  [<c0164596>] select_parent+0x56/0xb0
Jul 28 06:48:52 coyote kernel:  [<c0164600>] shrink_dcache_parent+0x10/0x30
Jul 28 06:48:52 coyote kernel:  [<c017b177>] proc_pid_flush+0x17/0x30
Jul 28 06:48:52 coyote kernel:  [<c011765d>] release_task+0x13d/0x1e0
Jul 28 06:48:52 coyote kernel:  [<c01190fb>] wait_task_zombie+0x15b/0x1c0
Jul 28 06:48:52 coyote kernel:  [<c0119513>] sys_wait4+0x213/0x260
Jul 28 06:48:52 coyote kernel:  [<c01132e0>] default_wake_function+0x0/0x20
Jul 28 06:48:52 coyote kernel:  [<c01132e0>] default_wake_function+0x0/0x20
Jul 28 11:00:39 coyote syslogd 1.4.1: restart.
--------------
Note restart time, but my script worked, the system 
time is now properly set later in the bootup.  Nice.

Ok, so which direction do I go, bk2, or bk4, for the next test?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.23% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.

  parent reply	other threads:[~2004-07-28 11:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27 16:33 Gene Heskett
2004-07-27 13:37 ` Denis Vlasenko
2004-07-27 14:29 ` viro
2004-07-27 17:02   ` Gene Heskett
2004-07-27 16:51     ` Randy.Dunlap
2004-07-27 17:43       ` Gene Heskett
2004-07-27 17:32         ` Randy.Dunlap
2004-07-27 18:02           ` Gene Heskett
2004-07-27 17:50             ` Randy.Dunlap
2004-07-27 18:36               ` Gene Heskett
2004-07-27 18:42               ` Gene Heskett
2004-07-27 19:23                 ` viro
2004-07-27 22:17                   ` Gene Heskett
2004-07-27 21:40             ` Matt Mackall
2004-07-27 22:21               ` Gene Heskett
2004-07-27 17:15   ` Gene Heskett
2004-07-27 19:26     ` viro
2004-07-27 22:24       ` Gene Heskett
2004-07-27 22:25       ` Gene Heskett
2004-07-28 11:20       ` Gene Heskett [this message]
2004-07-28 11:38         ` Andy Whitcroft
2004-07-28 12:52           ` Gene Heskett
2004-07-27 17:31   ` Gene Heskett
2004-07-28 23:26     ` Gene Heskett
2004-07-29 12:53       ` Gene Heskett

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=200407280720.21518.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

all inboxes | Powered by JetHome®