Call Trace on boot

[Will Backman]

On Thu, 2004-04-01 at 16:52, Zach Wilkinson wrote:
> ----- Original Message ----- 
> From: "Will Backman" <whb at ceimaine.org>
> To: "For testers of Fedora Core development releases"
> <fedora-test-list at redhat.com>
> Sent: Thursday, April 01, 2004 4:43 PM
> Subject: Re: Call Trace on boot
> 
> 
> > On Thu, 2004-04-01 at 16:38, Zach Wilkinson wrote:
> > > ----- Original Message ----- 
> > > From: "Alan Cox" <alan at redhat.com>
> > > To: "For testers of Fedora Core development releases"
> > > <fedora-test-list at redhat.com>
> > > Sent: Thursday, April 01, 2004 4:26 PM
> > > Subject: Re: Call Trace on boot
> > >
> > >
> > > > On Thu, Apr 01, 2004 at 04:22:51PM -0500, Zach Wilkinson wrote:
> > > > > That's OK, it seems to work anyway.  No show stopper.
> > > > > Besides, not being a engineer, I doubt I'm eligible to file a bug
> > > report.
> > > >
> > > > Anyone can file a bug report.
> > >
> > > Uhh, are you sure that's a good policy?  Seems like there would be a lot
> of
> > > potential for abuse.
> > >
> > It has been working for years in many projects.  I've been amazed at how
> > quickly people respond to good bug reports.  Bugzilla is good at
> > requiring a reasonable level of detail to prevent "my computer doesn't
> > work" reports, which are more common in a list like this.
> 
> I think I fall into this category.  I don't understand Call Traces well
> enough to fill out a bug report.  Hell, I don't know even know how to use
> GDB.
> Definitely over my head.
> 
I've been in over my head also (which is fairly easy), and often someone
will respond to the bug with helpful tips on how to produce useful data.
See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=56011 for an
example of how nice these folks are.