How to report bugs for release candidates?

How to report bugs for release candidates?

[Martin Kletzander]

Hi everyone,

I was usually using Bugzilla when I wanted to report something, but what
if, for example, I can't boot 4.11-rc3?  Is bugzilla fast enough for
such type of regressions?  Can I attach any more information than debug
output over netconsole?  Even that is assuming I will get any, which
might not be the case since it doesn't get anywhere.  I'm booting
directly from UEFI, so the EFI stub implementation might be related to
that.  I'd really like to know how to debug some of these things, but
that's probably for later.

Thanks for letting me know and have a nice day,
Martin

How to report bugs for release candidates?

[Greg KH]

On Sat, Mar 25, 2017 at 11:16:56AM +0100, Martin Kletzander wrote:
> Hi everyone,
> 
> I was usually using Bugzilla when I wanted to report something, but what
> if, for example, I can't boot 4.11-rc3?  Is bugzilla fast enough for
> such type of regressions?

Yes, but it's even better if you just use email, sending the crash
information to the developers, and mailing list, where the issue is.
You can use scripts/get_maintainer.pl to find who to send stuff to.

Also, if you can use 'git bisect' to figure out what patch causes the
problem, that's even better.  Then you can email the people who wrote
and approved the patch, and the subsystem mailing list.

thanks,

greg k-h

How to report bugs for release candidates?

[Nicholas Mc Guire]

On Sun, Mar 26, 2017 at 10:15:17AM +0200, Greg KH wrote:
> On Sat, Mar 25, 2017 at 11:16:56AM +0100, Martin Kletzander wrote:
> > Hi everyone,
> > 
> > I was usually using Bugzilla when I wanted to report something, but what
> > if, for example, I can't boot 4.11-rc3?  Is bugzilla fast enough for
> > such type of regressions?
> 
> Yes, but it's even better if you just use email, sending the crash
> information to the developers, and mailing list, where the issue is.
> You can use scripts/get_maintainer.pl to find who to send stuff to.
> 
> Also, if you can use 'git bisect' to figure out what patch causes the
> problem, that's even better.  Then you can email the people who wrote
> and approved the patch, and the subsystem mailing list.
>
interesting - been sending patches to the LoC author(s) (via gib blame)
and those listed by scripts/get_maintainers -f PATH/TO/filename
but not to anyone that provided a *-by tag - should that really be
done routinely ?

thx!
hofrat

How to report bugs for release candidates?

[Ozgur Karatas]

25.03.2017, 13:17, "Martin Kletzander" <mk@linux.com>:
> Hi everyone,

Hello,

> I was usually using Bugzilla when I wanted to report something, but what
> if, for example, I can't boot 4.11-rc3? Is bugzilla fast enough for
> such type of regressions? Can I attach any more information than debug
> output over netconsole? Even that is assuming I will get any, which
> might not be the case since it doesn't get anywhere. I'm booting
> directly from UEFI, so the EFI stub implementation might be related to
> that. I'd really like to know how to debug some of these things, but
> that's probably for later.

So, may be a better method to report bug on the e-mail. if you have a very important bug, please add to kernel maintainer. 
Maintainer's can not answer sometimes but everytime read to e-mail.

Please indicate your importance, if it bug affected to everyone, very important.

> Thanks for letting me know and have a nice day,
> Martin

Regards,

Ozgur