From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-user+bounces-125444-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1QfiTS-0002s7-M2
for garchives@archives.gentoo.org; Sun, 10 Jul 2011 01:06:18 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 1FCB721C288
for <garchives@archives.gentoo.org>; Sun, 10 Jul 2011 01:06:18 +0000 (UTC)
Received: from mail-qw0-f53.google.com (mail-qw0-f53.google.com [209.85.216.53])
by pigeon.gentoo.org (Postfix) with ESMTP id 2034E21C1E8
for <gentoo-user@lists.gentoo.org>; Sun, 10 Jul 2011 00:12:34 +0000 (UTC)
Received: by qwb7 with SMTP id 7so1915653qwb.40
for <gentoo-user@lists.gentoo.org>; Sat, 09 Jul 2011 17:12:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type:content-transfer-encoding;
bh=GrqwT2FJ9faF3pt6kpglcsZbz7LR/raj4ZINNwCz0d4=;
b=G1CvPcSovEw8shXrw3016qEgfY6BTcPUSpstsN9og55L0j+zeJFtt3N0CM8QBTzVqe
52MW5/M4D1UTkC/LoD3Q7XZcXgVFZlyIaExyzDP/EQrtJ5Quw3r7BNz/k0+VJy3nDOrv
Ag9QiU+Tw26wMiNfHY9kYHEEoLq410oVpeLmM=
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.224.136.16 with SMTP id p16mr2679032qat.359.1310256754484;
Sat, 09 Jul 2011 17:12:34 -0700 (PDT)
Received: by 10.224.11.21 with HTTP; Sat, 9 Jul 2011 17:12:34 -0700 (PDT)
In-Reply-To: <4E18EA55.8030904@gmail.com>
References: <4E11EEF3.70804@gmail.com>
<iv5bs5$u2b$1@dough.gmane.org>
<4E168B0E.2070100@gmail.com>
<201107080702.58452.michaelkintzios@gmail.com>
<4E16B251.6080204@gmail.com>
<4E16B548.5050105@gmail.com>
<4E17B3C3.4010009@gmail.com>
<CALzub=pAqwNgW-fpt9LEbmzYU6nDqLpfAM04n+i-CvhHFPq1gw@mail.gmail.com>
<4E187F60.9080400@gmail.com>
<4E18ABC3.1090909@orlitzky.com>
<4E18C082.4070209@gmail.com>
<4E18C977.9070001@orlitzky.com>
<4E18D5A7.8040309@gmail.com>
<CAK2H+efvKnmh4aUyE+naJo+Pt1o4vpBNEShaBG16BRfB+dRDsA@mail.gmail.com>
<4E18EA55.8030904@gmail.com>
Date: Sat, 9 Jul 2011 17:12:34 -0700
Message-ID: <CAK2H+eeJnCSQFAG4=wLFMp=ceBgOxdm5d5-jd+s9ndD_vy6+tg@mail.gmail.com>
Subject: Re: [gentoo-user] Re: Firefox and kernel panics.
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Archives-Salt:
X-Archives-Hash: ab3dd1aaf479c304dcefcaae680762d9
On Sat, Jul 9, 2011 at 4:55 PM, Dale <rdalek1967@gmail.com> wrote:
> Mark Knecht wrote:
>>
>> And this is exactly why you should consider posting any information
>> your can find on LKML to let the heavy weight guys figure it out. As I
>> said earlier, I believe they will take you quite seriously. In general
>> I would also say that Firefox should be able to cause a kernel panic,
>> and since it is I know the kernel developers are going to be
>> interested in what's the root cause.
>>
>> I don't remember from earlier why you said it was a kernel panic, but
>> clearly it must be. How are you determining this? Do you have info in
>> a terminal? For a few problems I've had I've posted digital photos
>> I've taken and uploaded to FlickR. You might consider doing something
>> similar.
>>
>> Cheers,
>> Mark
>>
>>
>>
>
> The reason I said kernel panic is because someone else posted that when t=
he
> keyboard lights blink, that is a kernel panic. =C2=A0Sure enough, when Ne=
il told
> me how to set it up so that it would automatically reboot when the kernel
> panics, it does just that. =C2=A0I have no reason to think it is anything=
other
> than a kernel panic based on nothing but the kernel doing the reboot and =
the
> lights blinking.
>
> I would like to report this but I wouldn't even know where to start. =C2=
=A0If I
> had a lot more knowledge on how to help track it down, then that would be
> different. =C2=A0I'm not sure I can help much other than telling them Fir=
efox
> causes a kernel panic but I have no clue how or why.
>
> Then again, if one of the dev would hold my hand a little, I could copy a
> install over to my spare drive and then not have to worry about messing u=
p
> my main install. =C2=A0Fluxbox is OK but I like my KDE better. =C2=A0;-)
>
> My old rig was in the middle of a update and we just had a nasty little
> thunderstorm here. =C2=A0It was OOo of course. =C2=A0It was 7 hours into =
a 9 hour
> compile when the lights blinked. =C2=A0My old rig isn't on a UPS anymore.=
=C2=A0Neat
> huh? =C2=A0I'm glad for the rain tho. =C2=A0My garden needs it really rea=
lly bad.
>
> Dale
Yeah, if you can't report good clear info then it's just a waste of
everyone's time. No need to do that.
Not sure if it would work or even apply but there are some kernel
features, mostly I think used around boot time, that send kernel info
over either a serial port or more recently an Ethernet link to another
computer which then stays alove and captures whatever data gets
transmitted. If you were interested in learning about that (I am but
haven't had time. I used it years ago to give some LKML guys info they
needed to get an ATI chipset to work better) then we might be able to
dig into that off line.
On the other hand, if you're machine is working then it ain't broke, right?=
;-)
Cheers,
Mark