4.7-rc3: Reported regressions from 4.7

4.7-rc3: Reported regressions from 4.7

[Thorsten Leemhuis]

Hi! As announced last week in http://article.gmane.org/gmane.linux.kernel/2233992 
I'll try to write regression reports for 4.7. Find the first one below. Obviously
it looks a bit differently then those that Rafael wrote in the past. And I didn't
automatically send out mails to the persons involved. But well, you have to start 
somewhere and it's better than nothing afaics. I'll manually send mails where I
think a poke is needed to get things rolling again (those contain a "todo-knurd:" 
in the note as small reminder for myself). 

Let me know if a regression in missing in the list. Or if there is something on the
list which shouldn't be there. Right now it contains 21 entries. 

HTH, CU, knurd

----

Description:    ath10k no longer authenticates and freezes system
Report:         https://bugzilla.kernel.org/show_bug.cgi?id=119151
Latest status:  http://thread.gmane.org/gmane.linux.kernel.wireless.general/152513/focus=152535
Date repo/stat: 2016-05-27 / 2016-06-02
Notes:          forgotten? or is this related to http://thread.gmane.org/gmane.linux.kernel.wireless.general/152112/focus=152511 ?

Description:    Commit 51e68d055cba (x86 isa: add back X86_32 dependency on CONFIG_ISA), added to restrict the ISA bus driver to only X86_32, causes several drivers intended for X86_64 to be restricted to X86_32 as well.
Report:         http://thread.gmane.org/gmane.linux.kernel.gpio/17016/
Latest status:  http://thread.gmane.org/gmane.linux.kernel.gpio/17016/focus=2231443
Date repo/stat: 2016-05-28 / 2016-05-31
Notes:          got lost? (todo-knurd: poke the right people)

Description:    Bad flicker on skylake HQD due to code in the 4.7 merge window
Report:         http://thread.gmane.org/gmane.linux.kernel/2230377
Latest status:  http://thread.gmane.org/gmane.linux.kernel/2230377/focus=90911
Date repo/stat: 2016-05-30 / 2016-05-30
Notes:          unknown; reporter is a developer, no assistance needed afaics 

Description:    Qemu CD ROM emulation stopped working
Report:         http://thread.gmane.org/gmane.linux.scsi/113900
Latest status:  http://thread.gmane.org/gmane.linux.scsi/114282/focus=2241548
Date repo/stat: 2016-05-31 / 2016-06-11
Notes:          under discussion

Description:    Dedicated wakeirqs may not work on omaps for the first resume
Report:         https://bugzilla.kernel.org/show_bug.cgi?id=119341
Latest status:  n/a
Date repo/stat: 2016-05-31 / n/a
Notes:          Really a regression? Reporter is a developer, no assistance needed afaics 

Description:    we noticed reaim.jobs_per_min -49.1% regression
Report:         http://thread.gmane.org/gmane.linux.kernel/2231025/
Latest status:  http://thread.gmane.org/gmane.linux.kernel/2231025/focus=2233571
Date repo/stat: 2016-05-31 / 2016-06-02
Notes:          current status unknown

Description:    ASUS Q500A: corrupted keycodes on dualboot system
Report:         https://bugzilla.kernel.org/show_bug.cgi?id=119391
Latest status:  https://bugzilla.kernel.org/show_bug.cgi?id=119391#c15
Date repo/stat: 2016-05-31 / 2016-06-12
Notes:          in progress

Description:    xhci: fix platform quirks overwrite regression in 4.7-rc1
Report:         http://thread.gmane.org/gmane.linux.usb.general/142949/focus=142952
Latest status:  n/a
Date repo/stat: 2016-06-01 / n/a
Notes:          got lost? (todo-knurd: poke the right people)

Description:    NULL pointer dereference with BCM4350 wireless device
Report:         https://bugzilla.kernel.org/show_bug.cgi?id=119451
Latest status:  7.6.
Date repo/stat: 2016-06-01 / 2016-06-07
Notes:          likely fixed in mainline by https://git.kernel.org/torvalds/c/31143e2933

Description:    Asus keyboard backlight broken, /sys/class/leds/asus::kbd_backlight gone
Report:         https://bugzilla.kernel.org/show_bug.cgi?id=119531
Latest status:  n/a
Date repo/stat: 2016-06-02 / n/a
Notes:          help reporter to get in contact with the right people (todo-knurd)

Description:    795ae7a0de: pixz.throughput -9.1% regression
Report:         http://thread.gmane.org/gmane.linux.kernel/2233056/
Latest status:  http://thread.gmane.org/gmane.linux.kernel/2233056/focus=2238208
Date repo/stat: 2016-06-02 / 2016-06-08
Notes:          wip

Description:    IPoIB lock inversion complaint
Report:         https://bugzilla.kernel.org/show_bug.cgi?id=119561
Latest status:  https://bugzilla.kernel.org/show_bug.cgi?id=119561#c2
Date repo/stat: 2016-06-02 / 2016-06-02
Notes:          might be fixed already

Description:    RadeonSI get a huge performance dip with used with the nine state tracker
Report:         https://bugzilla.kernel.org/show_bug.cgi?id=119631
Latest status:  https://bugzilla.kernel.org/show_bug.cgi?id=119631#c3
Date repo/stat: 2016-06-04 / 2016-06-07
Notes:          waiting for feedback from reporter

Description:    rtl8188eu driver from staging has regressed after the staging 4.7-rc1 pull-req
Report:         http://thread.gmane.org/gmane.linux.drivers.driver-project.devel/89186
Latest status:  n/a
Date repo/stat: 2016-06-05 / n/a
Notes:          got lost? (todo-knurd: poke the right people)

Description:    [lkp] [mm] 5c0a85fad9: unixbench.score -6.3% regression
Report:         http://thread.gmane.org/gmane.linux.kernel/2235794
Latest status:  http://thread.gmane.org/gmane.linux.kernel/2235794/focus=2241602
Date repo/stat: 2016-06-06 / 2016-06-12
Notes:          wip

Description:    System hang possibly due to brcmfmac regression
Report:         https://bugzilla.kernel.org/show_bug.cgi?id=119761
Latest status:  https://bugzilla.kernel.org/show_bug.cgi?id=119761#c1
Date repo/stat: 2016-06-07 / 2016-06-12
Notes:          told reporter to check if its a dup of https://bugzilla.kernel.org/show_bug.cgi?id=119451 which liekly is fixed

Description:    mmc_select_hs200() regression in v4.7-rc.
Report:         http://thread.gmane.org/gmane.linux.kernel/2237440
Latest status:  http://thread.gmane.org/gmane.linux.kernel/2237440/focus=2238598
Date repo/stat: 2016-06-07 / 2016-06-08
Notes:          wip

Description:    Regression in kbuild: fix if_change and friends to consider argument 
Report:         http://thread.gmane.org/gmane.linux.kbuild.devel/14981/
Latest status:  http://thread.gmane.org/gmane.linux.kbuild.devel/14981/focus=15000
Date repo/stat: 2016-06-07 / 2016-06-09
Notes:          wip

Description:    BUG: using smp_processor_id() in preemptible [00000000] code] when using a USB Mass Storage device
Report:         http://thread.gmane.org/gmane.linux.usb.general/143504
Latest status:  http://thread.gmane.org/gmane.linux.usb.general/143504/focus=153011
Date repo/stat: 2016-06-09 / 2016-06-09
Notes:          likely fixed in mainline

Description:    BUG: unable to handle kernel NULL pointer dereference in drm_connector_cleanup nouveau when Xorg server is started
Report:         https://bugzilla.kernel.org/show_bug.cgi?id=119861
Latest status:  n/a
Date repo/stat: 2016-06-09 / n/a
Notes:          if nothing happens in the next few days send reporter to freedesktop.org, as that's afaics what the nouveau developers use (todo-knurd)

Description:    Notebook Clevo N350DW i5-6500T freezes on shutdown (but reboots fine)
Report:         https://bugzilla.kernel.org/show_bug.cgi?id=119871
Latest status:  n/a
Date repo/stat: 2016-06-09 / n/a
Notes:          reporter needs assistance, as more details are needed to get this debugged

Re: 4.7-rc3: Reported regressions from 4.7

[Borislav Petkov]

Hey thl,

On Sun, Jun 12, 2016 at 07:22:17PM +0200, Thorsten Leemhuis wrote:
> Hi! As announced last week in http://article.gmane.org/gmane.linux.kernel/2233992 
> I'll try to write regression reports for 4.7. Find the first one below.

looks good, thanks for volunteering.

So I'm wondering, would it make more sense to have a web page somewhere
which carries all those and gets updated when status ot any tracked
regression changes?

So that people can look at it and get the latest on the regressions
front instead of trying to find a possibly outdated mail to lkml?

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

Re: 4.7-rc3: Reported regressions from 4.7

[Takashi Iwai]

On Mon, 13 Jun 2016 10:07:48 +0200,
Borislav Petkov wrote:
> 
> Hey thl,
> 
> On Sun, Jun 12, 2016 at 07:22:17PM +0200, Thorsten Leemhuis wrote:
> > Hi! As announced last week in http://article.gmane.org/gmane.linux.kernel/2233992 
> > I'll try to write regression reports for 4.7. Find the first one below.
> 
> looks good, thanks for volunteering.

Indeed, it's really appreciated!

> So I'm wondering, would it make more sense to have a web page somewhere
> which carries all those and gets updated when status ot any tracked
> regression changes?
> 
> So that people can look at it and get the latest on the regressions
> front instead of trying to find a possibly outdated mail to lkml?

Another idea is to use "Keywords" or "Tags" field in each bugzilla
entry.  Then you can let bugzilla showing up the all such entries.


Takashi

Re: 4.7-rc3: Reported regressions from 4.7

[Thorsten Leemhuis]

Takashi Iwai wrote on 13.06.2016 10:20:
> On Mon, 13 Jun 2016 10:07:48 +0200,
> Borislav Petkov wrote:
>> On Sun, Jun 12, 2016 at 07:22:17PM +0200, Thorsten Leemhuis wrote:
>> > Hi! As announced last week in http://article.gmane.org/gmane.linux.kernel/2233992 
>> > I'll try to write regression reports for 4.7. Find the first one below.
>> looks good, thanks for volunteering.
> Indeed, it's really appreciated!

thx!

>> So I'm wondering, would it make more sense to have a web page somewhere
>> which carries all those and gets updated when status ot any tracked
>> regression changes?

Yeah, that would be the good approach, but that would take some time and
work to set up.

> Another idea is to use "Keywords" or "Tags" field in each bugzilla
> entry.  Then you can let bugzilla showing up the all such entries.

Which would mean that all regressions need to get an entry in
bugzilla.kernel.org. I'm not sure if that's a wise approach, as some
developers/subsystems don't use it afaics: some use other bug trackers,
others just use mailing lists and might not be too happy if they'd have
to deal with bugzilla.

Obviously I could file tracking bugs in our bugzilla. But I wonder if
that is worth the work; and it could lead to confusion once a regression
reporter puts some crucial information into the tracking bug entry
instead of posting it to the proper place where the developers discuss
the problem.

CU, knurd

Re: 4.7-rc3: Reported regressions from 4.7

[Borislav Petkov]

On Mon, Jun 13, 2016 at 12:59:26PM +0200, Thorsten Leemhuis wrote:
> and it could lead to confusion once a regression reporter puts some
> crucial information into the tracking bug entry instead of posting it
> to the proper place where the developers discuss the problem.

Right, this is where a single webpage would help when collecting all the
relevant data/links for a regression, regardless of the bugtracker.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

Re: 4.7-rc3: Reported regressions from 4.7

[Takashi Iwai]

On Mon, 13 Jun 2016 13:02:21 +0200,
Borislav Petkov wrote:
> 
> On Mon, Jun 13, 2016 at 12:59:26PM +0200, Thorsten Leemhuis wrote:
> > and it could lead to confusion once a regression reporter puts some
> > crucial information into the tracking bug entry instead of posting it
> > to the proper place where the developers discuss the problem.
> 
> Right, this is where a single webpage would help when collecting all the
> relevant data/links for a regression, regardless of the bugtracker.

Well, Rafael created a bugzilla entry for tracking in the past, so
using bugzilla as tracking tool works in general.  It doesn't mean
it's the best option, of course, though.

In anyway, the only question is whether Thorsten feels comfortable or
not.


thanks,

Takashi

Re: 4.7-rc3: Reported regressions from 4.7

[Borislav Petkov]

On Mon, Jun 13, 2016 at 01:53:34PM +0200, Takashi Iwai wrote:
> Well, Rafael created a bugzilla entry for tracking in the past, so
> using bugzilla as tracking tool works in general.  It doesn't mean
> it's the best option, of course, though.

So I don't care whether it is buzgilla or some other central place which
can show you all regressions at once and Thorsten can edit it quickly so
that interested parties can get the latest status of a regression and
not waste time with stale emails.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

Re: 4.7-rc3: Reported regressions from 4.7

[Rafael J. Wysocki]

On Monday, June 13, 2016 03:36:48 PM Borislav Petkov wrote:
> On Mon, Jun 13, 2016 at 01:53:34PM +0200, Takashi Iwai wrote:
> > Well, Rafael created a bugzilla entry for tracking in the past, so
> > using bugzilla as tracking tool works in general.  It doesn't mean
> > it's the best option, of course, though.
> 
> So I don't care whether it is buzgilla or some other central place which
> can show you all regressions at once and Thorsten can edit it quickly so
> that interested parties can get the latest status of a regression and
> not waste time with stale emails.

I used kernel BZ entries for two reasons.

First, some of the bugs were in the kernel BZ already, so they could be added
to the tracked list very easily when it was in BZ itself.  Second, some people
actually used BZ entries created by me to work on the bugs going forward (for
storing logs, acpidumps and similar).

Thanks,
Rafael

Re: 4.7-rc3: Reported regressions from 4.7

[Borislav Petkov]

On Mon, Jun 13, 2016 at 03:53:20PM +0200, Rafael J. Wysocki wrote:
> I used kernel BZ entries for two reasons.
> 
> First, some of the bugs were in the kernel BZ already, so they could be added
> to the tracked list very easily when it was in BZ itself.  Second, some people
> actually used BZ entries created by me to work on the bugs going forward (for
> storing logs, acpidumps and similar).

Could be useful too, especially if we mark all entries with some keyword
like "regression" or somesuch and then search for it to geget all
regressions.

@Thorsten: well, if you do use bugzilla, you have everything there and
ready to use :)

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

Re: 4.7-rc3: Reported regressions from 4.7

[Rafael J. Wysocki]

On Monday, June 13, 2016 03:53:35 PM Borislav Petkov wrote:
> On Mon, Jun 13, 2016 at 03:53:20PM +0200, Rafael J. Wysocki wrote:
> > I used kernel BZ entries for two reasons.
> > 
> > First, some of the bugs were in the kernel BZ already, so they could be added
> > to the tracked list very easily when it was in BZ itself.  Second, some people
> > actually used BZ entries created by me to work on the bugs going forward (for
> > storing logs, acpidumps and similar).
> 
> Could be useful too, especially if we mark all entries with some keyword
> like "regression" or somesuch and then search for it to geget all
> regressions.

There is a "regression" flag in the kernel BZ already.  Guess why. ;-)

> @Thorsten: well, if you do use bugzilla, you have everything there and
> ready to use :)

I may be able to find some scripts I used with that a few years ago (although
they aren't pretty).

Thanks,
Rafael