public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: Dale Blount <linux-kernel@dale.us>, linux-kernel@vger.kernel.org
Subject: Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
Date: Thu, 17 Feb 2005 11:58:18 +0100	[thread overview]
Message-ID: <20050217105818.GS6680@charite.de> (raw)
In-Reply-To: <20050216145548.53f67fec.akpm@osdl.org>

* Andrew Morton <akpm@osdl.org>:

> There have been a handful of reports - there's surely a race in there.
> 
> Unfortunately I've yet to see a report from which we can identify the
> offending line in the very large journal_commit_transaction() function.

:(

> 
> The best way to do that is to ensure that the kernel was built with
> CONFIG_DEBUG_INFO, note the offending EIP value, then do
> 
> # gdb vmlinux
> (gdb) l *0xc0<whatever>

I'm rebuilding the ac12 kernel which crashed on me after just one day
and will reboot it today.

-- 
Ralf Hildebrandt (i.A. des IT-Zentrum)          Ralf.Hildebrandt@charite.de
Charite - Universitätsmedizin Berlin            Tel.  +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin    Fax.  +49 (0)30-450 570-962
IT-Zentrum Standort CBF                 send no mail to spamtrap@charite.de

  reply	other threads:[~2005-02-17 10:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-15 14:56 Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction) Ralf Hildebrandt
2005-02-16 15:33 ` Jan Kara
2005-02-16 20:04   ` Ralf Hildebrandt
2005-02-16 21:54     ` Dale Blount
2005-02-16 22:00       ` Ralf Hildebrandt
2005-02-16 22:55       ` Andrew Morton
2005-02-17 10:58         ` Ralf Hildebrandt [this message]
2005-02-17 13:21           ` Ralf Hildebrandt
2005-02-17 15:51             ` Randy.Dunlap
2005-02-17 16:00               ` Ralf Hildebrandt

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=20050217105818.GS6680@charite.de \
    --to=ralf.hildebrandt@charite.de \
    --cc=linux-kernel@dale.us \
    --cc=linux-kernel@vger.kernel.org \
    /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