From: Otavio Salvador <otavio@debian.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: oops when using git gc --auto
Date: Tue, 26 Feb 2008 11:21:39 -0300 [thread overview]
Message-ID: <87lk57yf0s.fsf@ossystems.com.br> (raw)
In-Reply-To: <200802270033.31297.nickpiggin@yahoo.com.au> (Nick Piggin's message of "Wed\, 27 Feb 2008 00\:33\:31 +1100")
Nick Piggin <nickpiggin@yahoo.com.au> writes:
> On Wednesday 27 February 2008 00:22, Otavio Salvador wrote:
>> Hello,
>>
>> Today I got this oops, someone has an idea of what's going wrong?
>>
>> Unable to handle kernel paging request at 0000020000000000 RIP:
>> [<ffffffff802735c3>] find_get_pages+0x3c/0x69
>
> At this point, the most likely candidate is a memory corruption
> error, probably hardware. Can you run memtest86 for a few hours
> to get a bit more confidence in the hw (preferably overnight)?
Those memories are new, but I can try. No problem. Will get back to
you by tomorrow.
> I did recently see another quite similar corruption in the
> pagecache radix-tree, though. Coincidence maybe?
I hope not.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
next prev parent reply other threads:[~2008-02-26 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 13:22 oops when using git gc --auto Otavio Salvador
2008-02-26 13:33 ` Nick Piggin
2008-02-26 14:21 ` Otavio Salvador [this message]
2008-02-26 19:36 ` Otavio Salvador
2008-02-27 20:01 ` Otavio Salvador
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=87lk57yf0s.fsf@ossystems.com.br \
--to=otavio@debian.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.