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 13:51:55 -0500	[thread overview]
Message-ID: <4E2B184B.6010905@gmail.com> (raw)
In-Reply-To: <1311445820.5163.2.camel@localhost.localdomain>

Albert Hopkins wrote:
>
> On Saturday, July 23 at 09:35 (-0500), Dale said:
>
>    
>> Albert Hopkins wrote:
>>      
> [...]
>    
>>> 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.
>>      
> Well, if you knew what was causing it, then you wouldn't need to report
> a bug as you could just fix it yourself :P
>
> Look, you know it's a kernel panic.  You know kernels aren't supposed to
> panic.  You know fairly well how to repeat the bug, so I don't see
> anything getting int he way of you reporting it.  That's my take on it
> anyway.
>
> -a
>
>    

It is a good point.  I would like to be able to give some more details 
other than when I try to download a file in Firefox or Seamonkey, I get 
a kernel panic.  That's not really a lot of info to give them and I'm 
not sure what they could do with the little info.  Since it is using the 
network, is it a nic driver?  Is it a problem with the video drivers 
since it is sometimes opening/closing a new window when it does it too?  
Could it be something totally unrelated to those two?

I don't mind filing bug reports but I like to be able to say more than 
it is broke.  ;-)  I'm thinking about taking a nic out of my old machine 
and putting in here.  That would narrow that down at least.

You are right, this is not like Linux.  It is rare that I have any sort 
of trouble like this.  I guess hal and xorg was the worst so far.  At 
least right now my keyboard and mouse are working.  lol

Dale

:-)  :-)



  reply	other threads:[~2011-07-23 18:53 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
2011-07-23 18:30                 ` Albert Hopkins
2011-07-23 18:51                   ` Dale [this message]
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=4E2B184B.6010905@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