From: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel BUG
Date: Tue, 4 Nov 2008 18:01:32 +0100 [thread overview]
Message-ID: <200811041801.32638.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <20081104084035.0b2f7267@osage.osagesoftware.com>
On Dienstag 04 November 2008, David Relson wrote:
> On Tue, 4 Nov 2008 11:33:09 -0200
>
> Jorge Peixoto de Morais Neto wrote:
> > >> 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.
>
> ... [snip]....
>
> > >> 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?
>
> At the moment I'm trying to capture the full BUG output. Once I have
> that, I'll report it and (likely) switch to a different kernel
> version with hopes of having a reliable system once again.
>
>
> David
install vanilla-sources.
if crash happens again, report to lkml. Joining is not necessary nor
recommended.
next prev parent reply other threads:[~2008-11-04 17:01 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
2008-11-04 13:40 ` David Relson
2008-11-04 17:01 ` Volker Armin Hemmann [this message]
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=200811041801.32638.volker.armin.hemmann@tu-clausthal.de \
--to=volker.armin.hemmann@tu-clausthal.de \
--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