Hi! Find below my second regression report for Linux 4.13. It lists 10
regressions I'm currently aware of (albeit in one case it's not entirely
clear yet if it's a regression in 4.13). One regression got fixed since
last weeks report. You can also find the report at
http://bit.ly/lnxregrep413 where I try to update it every now and then.
As always: Are you aware of any other regressions? Then please let me
know. For details see http://bit.ly/lnxregtrackid And please tell me if
there is anything in the report that shouldn't be there.
Ciao, Thorsten
P.S.: Thx to all those that CCed me on regression reports or provided
other input, it makes compiling these reports a whole lot easier!
== Current regressions ==
[x86/mm/gup] e585513b76: will-it-scale.per_thread_ops -6.9% regression
(2017-07-10)
http://lkml.kernel.org/r/20170710024020.GA26389@yexl-desktop
Status: Asked on the list, but issue still gets ignored by everyone
Cause: https://git.kernel.org/torvalds/c/e585513b76
Note: I'm a bit unsure if adding this issue to this list was a good idea.
Null dereference in rt5677_i2c_probe() (2017-07-17)
https://bugzilla.kernel.org/show_bug.cgi?id=196397
Linux-Regression-ID: lr#96bd63
Status: Patch is available in in asoc-next as commit ddc9e69b9dc2, but
was not part of the changes to this subsystem that got merged a few days ago
Cause: https://git.kernel.org/torvalds/c/a36afb0ab6
Latest: https://bugzilla.kernel.org/show_bug.cgi?id=196397#c6 (2017-07-17)
[I945GM] Pasted text not shown after mouse middle-click (2017-07-17)
https://bugs.freedesktop.org/show_bug.cgi?id=101819
Linux-Regression-ID: lr#d672f3
Status: could not get reproduced yet
Note: looks like it's getting ignored
Latest: https://bugs.freedesktop.org/show_bug.cgi?id=101819#c8 (2017-07-17)
[Dell xps13 9630] Could not be woken up from suspend-to-idle via usb
keyboard (2017-07-24)
https://bugzilla.kernel.org/show_bug.cgi?id=196459
Linux-Regression-ID: lr#bd29ab
Status: it's a tracking bug, looks like issue is handled by Intel devs
already
Cause: https://git.kernel.org/torvalds/c/33e4f80ee6
Note: suspend-to-idle is rare
[lkp-robot] [Btrfs] 28785f70ef: xfstests.generic.273.fail (2017-07-26)
https://lkml.kernel.org/r/20170726062352.GC4877@yexl-desktop
Linux-Regression-ID: lr#a7d273
Status: Seems it gets ignored by everyone
Cause: https://git.kernel.org/torvalds/c/28785f70ef
Xen HVM guest with KASLR enabled wouldn't boot any longer (2017-07-28)
https://lkml.kernel.org/r/[email protected]
Status: WIP, patches up for review, but were not part of the changes to
this subsystem that got merged a few days ago
bio-integrity: Fix regression if profile verify_fn is NULL (2017-08-02)
https://lkml.kernel.org/r/[email protected]
Linux-Regression-ID: lr#35498d
Status: Discussion ongoing how to fix it properly
Latest: https://lkml.kernel.org/r/[email protected] (2017-08-02)
CIFS mount error -112 (2017-08-06)
https://bugzilla.kernel.org/show_bug.cgi?id=196599
Linux-Regression-ID: lr#60efe5
Status: Brand new
== Waiting for reporter ==
NULL pointer deref in networking (2017-07-29)
https://bugzilla.kernel.org/show_bug.cgi?id=196529
Linux-Regression-ID: lr#084be9
Status: maybe reporter lost interest
SGI UV300/UV300: kernel BUG at arch/x86/mm/init_64.c:350! during boot
(2017-08-02)
https://bugzilla.kernel.org/show_bug.cgi?id=196561
Status: not 100% sure if this is a regression
Note: related to https://bugzilla.kernel.org/show_bug.cgi?id=196565 ?
== Fixed since last weeks report ==
Dell XPS 13 9360: Touchscreen does not report events (2017-07-28)
https://bugzilla.kernel.org/show_bug.cgi?id=196519
Linux-Regression-ID: lr#fe68bb
Status: Fixed in rc3
== Legend ==
First few lines -> short summary followed by date and a link to the
report that lead to inclusion in this report
Cause -> commit that causes this regression
Status -> short start summary written by regression tracker
Note -> additional note written by regression tracker
Latest -> most recent and informative point where issue was discussed
See also -> other places where this issue was or is discussed
Everything apart from the description and the link to the report is
optional.
EOF
Hi!
> Hi! Find below my second regression report for Linux 4.13. It lists 10
> regressions I'm currently aware of (albeit in one case it's not entirely
> clear yet if it's a regression in 4.13). One regression got fixed since
> last weeks report. You can also find the report at
> http://bit.ly/lnxregrep413 where I try to update it every now and then.
>
> As always: Are you aware of any other regressions? Then please let me
> know. For details see http://bit.ly/lnxregtrackid And please tell me if
> there is anything in the report that shouldn't be there.
There's compile-time regression in et8ek8, with patch available.
On 2017-06-08 02:01, Arnd Bergmann wrote:
> This one got applied twice, causing a build error with clang:
>
> drivers/media/i2c/et8ek8/et8ek8_driver.c:1499:1: error: redefinition
> of '__mod_of__et8ek8_of_table_device_table'
>
> Fixes: 9ae05fd1e791 ("[media] et8ek8: Export OF device ID as module
aliases")
> Signed-off-by: Arnd Bergmann <[email protected]>
> Acked-by: Sakari Ailus <[email protected]>
> Acked-by: Pavel Machek <[email protected]>
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Hi!
Perhaps you should get [email protected] alias, or something like that?
> As always: Are you aware of any other regressions? Then please let me
> know. For details see http://bit.ly/lnxregtrackid And please tell me if
> there is anything in the report that shouldn't be there.
I am using wake-on-lan quite a bit, and it stopped working. I'll move
to -rc4 and test there; but if anyone already has some ideas, let me
know.
Hardware is thinkpad X220
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
Connection (rev 04)
> Ciao, Thorsten
>
> P.S.: Thx to all those that CCed me on regression reports or provided
> other input, it makes compiling these reports a whole lot easier!
>
> == Current regressions ==
>
> [x86/mm/gup] e585513b76: will-it-scale.per_thread_ops -6.9% regression
> (2017-07-10)
> http://lkml.kernel.org/r/20170710024020.GA26389@yexl-desktop
> Status: Asked on the list, but issue still gets ignored by everyone
> Cause: https://git.kernel.org/torvalds/c/e585513b76
> Note: I'm a bit unsure if adding this issue to this list was a good idea.
>
> Null dereference in rt5677_i2c_probe() (2017-07-17)
> https://bugzilla.kernel.org/show_bug.cgi?id=196397
> Linux-Regression-ID: lr#96bd63
> Status: Patch is available in in asoc-next as commit ddc9e69b9dc2, but
> was not part of the changes to this subsystem that got merged a few days ago
> Cause: https://git.kernel.org/torvalds/c/a36afb0ab6
> Latest: https://bugzilla.kernel.org/show_bug.cgi?id=196397#c6 (2017-07-17)
>
> [I945GM] Pasted text not shown after mouse middle-click (2017-07-17)
> https://bugs.freedesktop.org/show_bug.cgi?id=101819
> Linux-Regression-ID: lr#d672f3
> Status: could not get reproduced yet
> Note: looks like it's getting ignored
> Latest: https://bugs.freedesktop.org/show_bug.cgi?id=101819#c8 (2017-07-17)
>
> [Dell xps13 9630] Could not be woken up from suspend-to-idle via usb
> keyboard (2017-07-24)
> https://bugzilla.kernel.org/show_bug.cgi?id=196459
> Linux-Regression-ID: lr#bd29ab
> Status: it's a tracking bug, looks like issue is handled by Intel devs
> already
> Cause: https://git.kernel.org/torvalds/c/33e4f80ee6
> Note: suspend-to-idle is rare
>
> [lkp-robot] [Btrfs] 28785f70ef: xfstests.generic.273.fail (2017-07-26)
> https://lkml.kernel.org/r/20170726062352.GC4877@yexl-desktop
> Linux-Regression-ID: lr#a7d273
> Status: Seems it gets ignored by everyone
> Cause: https://git.kernel.org/torvalds/c/28785f70ef
>
> Xen HVM guest with KASLR enabled wouldn't boot any longer (2017-07-28)
> https://lkml.kernel.org/r/[email protected]
> Status: WIP, patches up for review, but were not part of the changes to
> this subsystem that got merged a few days ago
>
> bio-integrity: Fix regression if profile verify_fn is NULL (2017-08-02)
> https://lkml.kernel.org/r/[email protected]
> Linux-Regression-ID: lr#35498d
> Status: Discussion ongoing how to fix it properly
> Latest: https://lkml.kernel.org/r/[email protected] (2017-08-02)
>
> CIFS mount error -112 (2017-08-06)
> https://bugzilla.kernel.org/show_bug.cgi?id=196599
> Linux-Regression-ID: lr#60efe5
> Status: Brand new
>
>
> == Waiting for reporter ==
>
> NULL pointer deref in networking (2017-07-29)
> https://bugzilla.kernel.org/show_bug.cgi?id=196529
> Linux-Regression-ID: lr#084be9
> Status: maybe reporter lost interest
>
> SGI UV300/UV300: kernel BUG at arch/x86/mm/init_64.c:350! during boot
> (2017-08-02)
> https://bugzilla.kernel.org/show_bug.cgi?id=196561
> Status: not 100% sure if this is a regression
> Note: related to https://bugzilla.kernel.org/show_bug.cgi?id=196565 ?
>
>
> == Fixed since last weeks report ==
>
> Dell XPS 13 9360: Touchscreen does not report events (2017-07-28)
> https://bugzilla.kernel.org/show_bug.cgi?id=196519
> Linux-Regression-ID: lr#fe68bb
> Status: Fixed in rc3
>
>
> == Legend ==
>
> First few lines -> short summary followed by date and a link to the
> report that lead to inclusion in this report
> Cause -> commit that causes this regression
> Status -> short start summary written by regression tracker
> Note -> additional note written by regression tracker
> Latest -> most recent and informative point where issue was discussed
> See also -> other places where this issue was or is discussed
>
> Everything apart from the description and the link to the report is
> optional.
>
> EOF
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
On Tuesday, August 8, 2017 11:00:53 AM CEST Pavel Machek wrote:
> Hi!
>
> Perhaps you should get [email protected] alias, or something like that?
>
> > As always: Are you aware of any other regressions? Then please let me
> > know. For details see http://bit.ly/lnxregtrackid And please tell me if
> > there is anything in the report that shouldn't be there.
>
> I am using wake-on-lan quite a bit, and it stopped working. I'll move
> to -rc4 and test there; but if anyone already has some ideas, let me
> know.
>
> Hardware is thinkpad X220
>
> 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
> Connection (rev 04)
I guess this is ACPI S3 suspend?
Thanks,
Rafael
On Wed 2017-08-09 02:45:54, Rafael J. Wysocki wrote:
> On Tuesday, August 8, 2017 11:00:53 AM CEST Pavel Machek wrote:
> > Hi!
> >
> > Perhaps you should get [email protected] alias, or something like that?
> >
> > > As always: Are you aware of any other regressions? Then please let me
> > > know. For details see http://bit.ly/lnxregtrackid And please tell me if
> > > there is anything in the report that shouldn't be there.
> >
> > I am using wake-on-lan quite a bit, and it stopped working. I'll move
> > to -rc4 and test there; but if anyone already has some ideas, let me
> > know.
> >
> > Hardware is thinkpad X220
> >
> > 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
> > Connection (rev 04)
>
> I guess this is ACPI S3 suspend?
ACPI S3, right. Machine still wakes up properly when I hit a key on
USB keyboard.
Does wake on LAN work on you, on any hardware?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[You seem to have a stale linux-pm address in your address book,
I replaced it with the current one in the CC list.]
On Wednesday, August 9, 2017 8:42:31 AM CEST Pavel Machek wrote:
> On Wed 2017-08-09 02:45:54, Rafael J. Wysocki wrote:
> > On Tuesday, August 8, 2017 11:00:53 AM CEST Pavel Machek wrote:
> > > Hi!
> > >
> > > Perhaps you should get [email protected] alias, or something like that?
> > >
> > > > As always: Are you aware of any other regressions? Then please let me
> > > > know. For details see http://bit.ly/lnxregtrackid And please tell me if
> > > > there is anything in the report that shouldn't be there.
> > >
> > > I am using wake-on-lan quite a bit, and it stopped working. I'll move
> > > to -rc4 and test there; but if anyone already has some ideas, let me
> > > know.
> > >
> > > Hardware is thinkpad X220
> > >
> > > 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
> > > Connection (rev 04)
> >
> > I guess this is ACPI S3 suspend?
>
> ACPI S3, right. Machine still wakes up properly when I hit a key on
> USB keyboard.
OK, so my guess would be a driver issue. What driver is this, igb?
> Does wake on LAN work on you, on any hardware?
Yes it does, I checked two machines earlier today, both work.
Can you enable dynamic debug in device_pm.c and send a dmesg output
with that covering a suspend-resume cycle?
Thanks,
Rafael
On Wed, 9 Aug 2017, Rafael J. Wysocki wrote:
> [You seem to have a stale linux-pm address in your address book,
> I replaced it with the current one in the CC list.]
>
> On Wednesday, August 9, 2017 8:42:31 AM CEST Pavel Machek wrote:
>> On Wed 2017-08-09 02:45:54, Rafael J. Wysocki wrote:
>>> On Tuesday, August 8, 2017 11:00:53 AM CEST Pavel Machek wrote:
>>>> Hi!
>>>>
>>>> Perhaps you should get [email protected] alias, or something like that?
>>>>
>>>>> As always: Are you aware of any other regressions? Then please let me
>>>>> know. For details see http://bit.ly/lnxregtrackid And please tell me if
>>>>> there is anything in the report that shouldn't be there.
>>>>
>>>> I am using wake-on-lan quite a bit, and it stopped working. I'll move
>>>> to -rc4 and test there; but if anyone already has some ideas, let me
>>>> know.
>>>>
>>>> Hardware is thinkpad X220
>>>>
>>>> 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
>>>> Connection (rev 04)
>>>
>>> I guess this is ACPI S3 suspend?
>>
>> ACPI S3, right. Machine still wakes up properly when I hit a key on
>> USB keyboard.
>
> OK, so my guess would be a driver issue. What driver is this, igb?
>
>> Does wake on LAN work on you, on any hardware?
>
> Yes it does, I checked two machines earlier today, both work.
>
> Can you enable dynamic debug in device_pm.c and send a dmesg output
> with that covering a suspend-resume cycle?
82579 is e1000e
--
Hisashi T Fujinaka - [email protected]
On Wed, Aug 9, 2017 at 11:15 PM, Hisashi T Fujinaka <[email protected]> wrote:
> On Wed, 9 Aug 2017, Rafael J. Wysocki wrote:
>
>> [You seem to have a stale linux-pm address in your address book,
>> I replaced it with the current one in the CC list.]
>>
>> On Wednesday, August 9, 2017 8:42:31 AM CEST Pavel Machek wrote:
>>>
>>> On Wed 2017-08-09 02:45:54, Rafael J. Wysocki wrote:
>>>>
>>>> On Tuesday, August 8, 2017 11:00:53 AM CEST Pavel Machek wrote:
>>>>>
>>>>> Hi!
>>>>>
>>>>> Perhaps you should get [email protected] alias, or something like
>>>>> that?
>>>>>
>>>>>> As always: Are you aware of any other regressions? Then please let me
>>>>>> know. For details see http://bit.ly/lnxregtrackid And please tell me
>>>>>> if
>>>>>> there is anything in the report that shouldn't be there.
>>>>>
>>>>>
>>>>> I am using wake-on-lan quite a bit, and it stopped working. I'll move
>>>>> to -rc4 and test there; but if anyone already has some ideas, let me
>>>>> know.
>>>>>
>>>>> Hardware is thinkpad X220
>>>>>
>>>>> 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
>>>>> Connection (rev 04)
>>>>
>>>>
>>>> I guess this is ACPI S3 suspend?
>>>
>>>
>>> ACPI S3, right. Machine still wakes up properly when I hit a key on
>>> USB keyboard.
>>
>>
>> OK, so my guess would be a driver issue. What driver is this, igb?
>>
>>> Does wake on LAN work on you, on any hardware?
>>
>>
>> Yes it does, I checked two machines earlier today, both work.
>>
>> Can you enable dynamic debug in device_pm.c and send a dmesg output
>> with that covering a suspend-resume cycle?
>
>
> 82579 is e1000e
Hmm. That also is there in my venerable Thoshiba Portege R500 which
wakes on LAN with 4.13-rc4. So the driver is off the hook I guess.
Hi!
> >[You seem to have a stale linux-pm address in your address book,
> >I replaced it with the current one in the CC list.]
Thanks, fixed.
> >>ACPI S3, right. Machine still wakes up properly when I hit a key on
> >>USB keyboard.
> >
> >OK, so my guess would be a driver issue. What driver is this, igb?
> >
> >>Does wake on LAN work on you, on any hardware?
> >
> >Yes it does, I checked two machines earlier today, both work.
> >
> >Can you enable dynamic debug in device_pm.c and send a dmesg output
> >with that covering a suspend-resume cycle?
>
> 82579 is e1000e
Thanks for all the help.
I now realized what was going on: I had badly inserted ethernet
cable; machine just connected to wifi, and everything worked... except
wake on LAN.
Sorry for the noise,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
On Wed, Aug 9, 2017 at 11:56 PM, Pavel Machek <[email protected]> wrote:
> Hi!
>
>> >[You seem to have a stale linux-pm address in your address book,
>> >I replaced it with the current one in the CC list.]
>
> Thanks, fixed.
>
>> >>ACPI S3, right. Machine still wakes up properly when I hit a key on
>> >>USB keyboard.
>> >
>> >OK, so my guess would be a driver issue. What driver is this, igb?
>> >
>> >>Does wake on LAN work on you, on any hardware?
>> >
>> >Yes it does, I checked two machines earlier today, both work.
>> >
>> >Can you enable dynamic debug in device_pm.c and send a dmesg output
>> >with that covering a suspend-resume cycle?
>>
>> 82579 is e1000e
>
> Thanks for all the help.
>
> I now realized what was going on: I had badly inserted ethernet
> cable; machine just connected to wifi, and everything worked... except
> wake on LAN.
>
> Sorry for the noise,
No worries. ;-)
On 8/6/17 9:59 AM, Thorsten Leemhuis wrote:
> Hi! Find below my second regression report for Linux 4.13. It lists 10
> regressions I'm currently aware of (albeit in one case it's not entirely
> clear yet if it's a regression in 4.13). One regression got fixed since
> last weeks report. You can also find the report at
> http://bit.ly/lnxregrep413 where I try to update it every now and then.
>
> As always: Are you aware of any other regressions? Then please let me
> know. For details see http://bit.ly/lnxregtrackid And please tell me if
> there is anything in the report that shouldn't be there.
>
> Ciao, Thorsten
>
> P.S.: Thx to all those that CCed me on regression reports or provided
> other input, it makes compiling these reports a whole lot easier!
>
> == Current regressions ==
>
> [x86/mm/gup] e585513b76: will-it-scale.per_thread_ops -6.9% regression
> (2017-07-10)
> http://lkml.kernel.org/r/20170710024020.GA26389@yexl-desktop
> Status: Asked on the list, but issue still gets ignored by everyone
> Cause: https://git.kernel.org/torvalds/c/e585513b76
> Note: I'm a bit unsure if adding this issue to this list was a good idea.
>
> Null dereference in rt5677_i2c_probe() (2017-07-17)
> https://bugzilla.kernel.org/show_bug.cgi?id=196397
> Linux-Regression-ID: lr#96bd63
> Status: Patch is available in in asoc-next as commit ddc9e69b9dc2, but
> was not part of the changes to this subsystem that got merged a few days ago
> Cause: https://git.kernel.org/torvalds/c/a36afb0ab6
> Latest: https://bugzilla.kernel.org/show_bug.cgi?id=196397#c6 (2017-07-17)
>
> [I945GM] Pasted text not shown after mouse middle-click (2017-07-17)
> https://bugs.freedesktop.org/show_bug.cgi?id=101819
> Linux-Regression-ID: lr#d672f3
> Status: could not get reproduced yet
> Note: looks like it's getting ignored
> Latest: https://bugs.freedesktop.org/show_bug.cgi?id=101819#c8 (2017-07-17)
>
> [Dell xps13 9630] Could not be woken up from suspend-to-idle via usb
> keyboard (2017-07-24)
> https://bugzilla.kernel.org/show_bug.cgi?id=196459
> Linux-Regression-ID: lr#bd29ab
> Status: it's a tracking bug, looks like issue is handled by Intel devs
> already
> Cause: https://git.kernel.org/torvalds/c/33e4f80ee6
> Note: suspend-to-idle is rare
>
> [lkp-robot] [Btrfs] 28785f70ef: xfstests.generic.273.fail (2017-07-26)
> https://lkml.kernel.org/r/20170726062352.GC4877@yexl-desktop
> Linux-Regression-ID: lr#a7d273
> Status: Seems it gets ignored by everyone
> Cause: https://git.kernel.org/torvalds/c/28785f70ef
We're not ignoring it. It's that this part of allocation seems to be a
collection of bugs that approximate a correct result, and we're
addressing them individually. This patch by itself is correct but
uncovered a couple of underlying issues.
-Jeff
--
Jeff Mahoney
SUSE Labs