public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: sys-kernel/gentoo-sources-3.0 and oldconfig
Date: Sat, 23 Jul 2011 09:35:02 -0500	[thread overview]
Message-ID: <4E2ADC16.50300@gmail.com> (raw)
In-Reply-To: <1311420052.4522.3.camel@localhost.localdomain>

Albert Hopkins wrote:
>
> On Saturday, July 23 at 05:33 (-0500), Dale said:
>
>    
>> But sometimes major changes can fix things and do things completely
>> different which can lead to other issues being fixed.  Seamonkey did
>> the
>> same when they did their major redo.
>>
>> Bad thing is, the kernel panics are at it again.  I had a little bit
>> of
>> time to download a video or two but here we go again.
>>
>> Back to the normal reboots I guess.  :-(
>>
>>      
> Yeah but typically.. or maybe my experience is completely different than
> most, but typically major releases center on new features and not fixing
> bugs, and major releases tend to create a whole lot more new bugs than
> fixes (which is why many people hold out for for<major_release>.1) :P
>
> Anyway, here's something... did you actually report a bug?  If a tree
> falls in the forest...
>
>    

I haven't filed a bug because at the moment we have not been able to 
figure out exactly what is causing it.  I know it is a kernel panic but 
not what part.  Seamonkey and Firefox works until I start to download 
something then there is a kernel panic.  While is causes a panic with 
Seamonkey or Firrefox, emerge can download for hours with not one 
problem.  Is it a network card driver or something else?  We don't 
know.  I just keep trying different things until I can find something 
that works then hopefully can figure out what changed.

I'm thinking about going back to the oldest kernel I can.  The oldest I 
have tried is 2.6.38 but .32 is still in the tree.

There is a whole thread, or two, on this tho.

Dale

:-)  :-)



  reply	other threads:[~2011-07-23 14:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-22 22:54 [gentoo-user] sys-kernel/gentoo-sources-3.0 and oldconfig Dale
2011-07-22 23:09 ` Stefan G. Weichinger
2011-07-22 23:29   ` Dale
2011-07-22 23:28 ` Hilco Wijbenga
2011-07-22 23:29 ` [gentoo-user] " Nikos Chantziaras
2011-07-22 23:42   ` Dale
2011-07-23  2:04     ` Albert Hopkins
2011-07-23  6:10       ` Dale
2011-07-23  7:10         ` Neil Bothwick
2011-07-23  7:17           ` Dale
2011-07-23  8:10             ` Adam Carter
2011-07-23  8:37               ` Dale
2011-07-23  9:00                 ` Dale
2011-07-23 10:23         ` Albert Hopkins
2011-07-23 10:33           ` Dale
2011-07-23 11:20             ` Albert Hopkins
2011-07-23 14:35               ` Dale [this message]
2011-07-23 18:30                 ` Albert Hopkins
2011-07-23 18:51                   ` Dale
2011-07-24 16:05                     ` Neil Bothwick
2011-07-24 18:13                       ` Dale
2011-07-24 23:27                         ` Peter Humphrey
2011-07-24 23:44                           ` Dale
2011-07-24 14:11                   ` [gentoo-user] " Stroller
2011-07-24 14:46                     ` Albert Hopkins
2011-07-22 23:39 ` Mark Knecht

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=4E2ADC16.50300@gmail.com \
    --to=rdalek1967@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