From: "Jorge Peixoto de Morais Neto" <please.no.spam.here@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel BUG
Date: Tue, 4 Nov 2008 11:33:09 -0200 [thread overview]
Message-ID: <38af3d670811040533l51e29fbexe30adfa0c45b4b0f@mail.gmail.com> (raw)
In-Reply-To: <d07a70780811040517h2fa23ecep18cfd97b169b4a86@mail.gmail.com>
>>
>> For about a week, my workstation has been crashing every day or so.
>> Typically it happens late at night while BackupPC is backing up a hard
>> drive. With "tail -F /var/log/messages" running I saw EXT3 mentioned a
>> few days ago and started suspecting a hard drive problem.
>>
>> Last night it happened again. This time my "tail ..." window was
>> opened full screen so I saw all the messages and know more. Here's
>> part of what I wrote down (until I got tired of writing):
>>
>> BUG unable to handle kernel NULL pointer dereference at 0000008
>> IP ffffff8027ce14 free_block+0xb4/0x160
>> PGD 11b638067 PUD 11b631067 PMD 0
>> Oops 0002[1]SMP
>> ...
>> Call Trace
>> 8027cac0 cache_flusharray+0x60/0xe0
>> 8027cc46 kmem_cache_free
>>
>> I'm running a 2.6.25-gentoo-r7
>>
>> To learn more about what's happening (and to more easily record
>> all the kernel messages), I'm now running "tail -F /var/log/messages"
>> from a second machine (via an SSH session).
>>
>> Questions:
>>
>> Is there a better way to capture the full BUG output???
>> Once I have the full BUG output, what's the next useful thing to do?
>>
> join the lkml (linux kernel mailing list) and let them know about it?
>
For a patched kernel like gentoo-sources, wouldn't it be appropriate
better to file a bug report at Gentoo's bugzilla?
next prev parent reply other threads:[~2008-11-04 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 12:43 [gentoo-user] Kernel BUG David Relson
2008-11-04 13:17 ` Hazen Valliant-Saunders
2008-11-04 13:33 ` Jorge Peixoto de Morais Neto [this message]
2008-11-04 13:40 ` David Relson
2008-11-04 17:01 ` Volker Armin Hemmann
2008-11-04 13:36 ` Zhang Le
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=38af3d670811040533l51e29fbexe30adfa0c45b4b0f@mail.gmail.com \
--to=please.no.spam.here@gmail.com \
--cc=gentoo-user@lists.gentoo.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