mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frank van Maarseveen <frankvm@xs4all.nl>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: 2.4.22/2.4.23 Oops in try_to_free_buffers() on X restart.
Date: Wed, 24 Dec 2003 12:12:26 +0100	[thread overview]
Message-ID: <20031224111226.GA18986@iapetus.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0312151000430.5362-100000@logos.cnet>

> > Got a new kernel oops. Same machine as the previous reported oops
> > in journal_try_to_free_buffers(). Something seems definately wrong
> > in 2.4.23.
> > 
> > Marcelo, I'll follow your suggestion te revert a particular change.

The 2.4.23 problems I'm experiencing are not a regression. Patch reversal
didn't solve it and 2.4.22 seems to suffer as well. Somehow RedHat 9 plus
some desktop triggers the problem, almost always when X is started for the
second time the day after the crash (probably some things got paged out in between).

2.4.22 Oops:

aksymoops 2.4.9 on i686 2.4.22-x90.  Options used
     -V (default)
     -k /var/log/ksyms.1 (specified)
     -l /proc/modules (default)
     -o /lib/modules/2.4.22-x90/ (default)
     -m /boot/System.map-2.4.22-x90 (specified)

No modules in ksyms, skipping objects
Dec 24 11:36:57 tornio kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000018
Dec 24 11:36:57 tornio kernel: c013a213
Dec 24 11:36:57 tornio kernel: *pde = 00000000
Dec 24 11:36:57 tornio kernel: Oops: 0000
Dec 24 11:36:57 tornio kernel: CPU:    0
Dec 24 11:36:57 tornio kernel: EIP:    0010:[<c013a213>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Dec 24 11:36:57 tornio kernel: EFLAGS: 00010217
Dec 24 11:36:57 tornio kernel: eax: 00000000   ebx: c11795a0   ecx: 000001d0   edx: 00000000
Dec 24 11:36:57 tornio kernel: esi: 00000000   edi: c2bb75d8   ebp: c11cbf1c   esp: c11cbf0c
Dec 24 11:36:57 tornio kernel: ds: 0018   es: 0018   ss: 0018
Dec 24 11:36:57 tornio kernel: Process kswapd (pid: 4, stackpage=c11cb000)
Dec 24 11:36:57 tornio kernel: Stack: c11795a0 000001d0 0000001d c11795a0 c11cbf2c c0138690 c2bb75d8 c11795a0
Dec 24 11:36:57 tornio kernel:        c11cbf60 c012f512 c11795a0 000001d0 00000020 000001d0 00000020 00000020
Dec 24 11:36:57 tornio kernel:        c11ca000 00000062 000003d5 000001d0 c03b2ad4 c11cbf84 c012f765 00000006
Dec 24 11:36:57 tornio kernel: Call Trace:    [<c0138690>] [<c012f512>] [<c012f765>] [<c012f7cc>] [<c012f8e2>]
Warning (Oops_read): Code line not seen, dumping what data is available


>>EIP; c013a213 <try_to_free_buffers+13/10c>   <=====

Trace; c0138690 <try_to_release_page+48/54>
Trace; c012f512 <shrink_cache+1e6/2fc>
Trace; c012f765 <shrink_caches+55/84>
Trace; c012f7cc <try_to_free_pages_zone+38/5c>
Trace; c012f8e2 <kswapd_balance_pgdat+4e/a0>


Notice that both journal_try_to_free_buffers() and this time
try_to_free_buffers() is Oopsing.


-- 
Frank

      parent reply	other threads:[~2003-12-24 11:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-10  8:48 2.4.23 Oops in journal_try_to_free_buffers Frank van Maarseveen
2003-12-15 11:02 ` 2.4.23 Oops Frank van Maarseveen
2003-12-15 12:03   ` Marcelo Tosatti
2003-12-15 12:20     ` Frank van Maarseveen
2003-12-24 11:12     ` Frank van Maarseveen [this message]

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=20031224111226.GA18986@iapetus.localdomain \
    --to=frankvm@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /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®