-regressi...@lists.linux.dev as 'Linux' is redundant in the latter
case.
Signed-off-by: Thorsten Leemhuis
---
I was a bit unsure how to add that list to MAINTAINERS. I considered
adding a 'M:' with my name and email address there as well, but getting
CCed on a lot of regressio
bot.md).
Signed-off-by: Thorsten Leemhuis
---
Lo! Now that we have a mailing list for regressions I was inclined to
remove the "Make the report's subject start with '[REGRESSION]'" part
from the text. But in the end I left it, to make it obvious on other
lists that the
the MAINTAINERS
file should better go through a different maintainer.
Ciao, Thorsten
Thorsten Leemhuis (2):
MAINTAINERS: add regressions mailing list
docs: reporting-issues: make everyone CC the regressions list
.../admin-guide/reporting-issues.rst | 64
On 07.04.21 11:56, Greg KH wrote:
> On Wed, Apr 07, 2021 at 11:21:55AM +0200, Thorsten Leemhuis wrote:
>> Add the newly created regression mailing list finally created after it
>> already had been agreed on during the maintainers summit 2017 (see
>> https://lwn.net/Articles
On 07.04.21 12:00, Greg KH wrote:
> On Wed, Apr 07, 2021 at 11:21:56AM +0200, Thorsten Leemhuis wrote:
>> Make people CC the recently created mailing list dedicated to Linux
>> kernel regressions when reporting one. Some paragraphs had to be
>> reshuffled and slightly
-regressi...@lists.linux.dev as 'Linux' would have been redundant
in the latter case.
Signed-off-by: Thorsten Leemhuis
---
v1->v2
* use the approach suggested by Greg, which doesn't have a K: entry,
but that is likely not much of a help anyway
---
MAINTAINERS | 5 +
through a different maintainer.
Ciao, Thorsten
Thorsten Leemhuis (2):
MAINTAINERS: add regressions mailing list
docs: reporting-issues: make everyone CC the regressions list
.../admin-guide/reporting-issues.rst | 55 ---
MAINTAINERS
Make people CC the recently created mailing list dedicated to Linux
kernel regressions when reporting one. Some paragraphs had to be
reshuffled and slightly rewritten during the process, as the text
otherwise would have gotten unnecessarily hard to follow.
Signed-off-by: Thorsten Leemhuis
---
v1
On 08.04.21 19:31, Jonathan Corbet wrote:
> Thorsten Leemhuis writes:
>
>> +In case you performed a successful bisection, use the title of the change
>> that
>> +introduced the regression as the second part of your subject. Make the
>> report
>> +also menti
On 31.03.21 21:47, Jonathan Corbet wrote:
> Greg KH writes:
>
>> On Tue, Mar 30, 2021 at 04:13:04PM +0200, Thorsten Leemhuis wrote:
>>> Removing Documentation/admin-guide/reporting-bugs.rst will break links
>>> in some of the translations. I was uns
Move the 'this section is a placeholder for now and needs help by
someone with domain knowledge' note one section upwards to the place
where it belongs: the 'Decode failure messages' section.
Signed-off-by: Thorsten Leemhuis
---
Brown paper bag fixup :-/
---
.../a
Am 08.12.20 um 18:44 schrieb Jonathan Corbet:
On Fri, 4 Dec 2020 07:43:47 +0100
Thorsten Leemhuis wrote:
This series adds a new and mostly finished document describing how to report
issues with the Linux kernel to its developers.
OK, I have applied this series.
Great, many thx! When I
Am 19.11.20 um 01:17 schrieb Jonathan Corbet:
On Thu, 12 Nov 2020 18:58:58 +0100
Thorsten Leemhuis wrote:
That's also why this commit removes scripts/ver_linux as well: the
details it collects are only needed in some situations. And some (a
lot?) distributions do not ship it anyway; a b
Am 19.11.20 um 01:05 schrieb Jonathan Corbet:
On Thu, 12 Nov 2020 18:58:45 +0100
Thorsten Leemhuis wrote:
+If your kernel is tainted, study
+:ref:`Documentation/admin-guide/tainted-kernels.rst ` to find
+out why. Try to eliminate the reason. Often it's caused by one these three
+things:
Am 19.11.20 um 01:29 schrieb Jonathan Corbet:
On Sun, 15 Nov 2020 11:13:52 +0100
Thorsten Leemhuis wrote:
So I've not had a chance to try to read through the whole thing again,
will try to do so in the near future.
Great, thx, looking forward to it.
OK, I have made a *quick* pass th
Am 19.11.20 um 01:29 schrieb Jonathan Corbet:
On Sun, 15 Nov 2020 11:13:52 +0100
Thorsten Leemhuis wrote:
- Collapse the whole thing down to a patch adding reporting-bugs-v2.rst
(or some suitable name). I do wonder if it should also move to the
process manual as part of this; not
t/log/Documentation/admin-guide/reporting-bugs.rst
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/REPORTING-BUGS
Thorsten Leemhuis (3):
LICENSES: Add the CC-BY-4.0 license
docs: Add a new text describing how to report bugs
docs: make reporting-bugs.rst obsolete
Docum
s.rst.
Hence also add a note to reporting-bugs.rst, telling people they're
better off reading reporting-issues.rst instead.
reporting-bugs.rst is scheduled for removal once reporting-issues.rst
is considered ready.
Signed-off-by: Thorsten Leemhuis
---
Documentation/admin-guide/
/creativecommons.org/licenses/by/4.0/legalcode.txt
Signed-off-by: Thorsten Leemhuis
CC: Thomas Gleixner
CC: Greg Kroah-Hartman
CC: Christoph Hellwig
---
For context: Patch 2 of this series adds a text to the Documentation/ directory
which (for now) uses "GPL-2.0+ OR CC-BY-4.0", as I want
ttps://lkml.kernel.org/r/20201118172958.5b014...@lwn.net
Signed-off-by: Thorsten Leemhuis
---
Documentation/admin-guide/index.rst |1 +
.../admin-guide/reporting-issues.rst | 1626 +
2 files changed, 1627 insertions(+)
create mode 100644 Documentation/a
Am 24.11.20 um 10:18 schrieb Christoph Hellwig:
On Tue, Nov 24, 2020 at 09:00:01AM +0100, Thorsten Leemhuis wrote:
For context: Patch 2 of this series adds a text to the Documentation/ directory
which (for now) uses "GPL-2.0+ OR CC-BY-4.0", as I want to make it easy and
attractive for
Am 24.11.20 um 10:36 schrieb Christoph Hellwig:
On Tue, Nov 24, 2020 at 10:31:33AM +0100, Thorsten Leemhuis wrote:
Am 24.11.20 um 10:18 schrieb Christoph Hellwig:
On Tue, Nov 24, 2020 at 09:00:01AM +0100, Thorsten Leemhuis wrote:
For context: Patch 2 of this series adds a text to the
Am 24.11.20 um 13:11 schrieb Matthew Wilcox:
On Tue, Nov 24, 2020 at 11:07:41AM +0100, Thorsten Leemhuis wrote:
There is nothing special with this text, it's just that GPL is known to not
be really ideal for documentation. That makes it hard for people to reuse
parts of the docs outside o
linux/kernel/git/torvalds/linux.git/log/REPORTING-BUGS
Thorsten Leemhuis (3):
LICENSES: Add the CC-BY-4.0 license
docs: Add a new text describing how to report bugs
docs: make reporting-bugs.rst obsolete
Documentation/admin-guide/README.rst |4 +-
Documentation/admin-guide/bug-bisect.
ttps://lkml.kernel.org/r/20201118172958.5b014...@lwn.net
Signed-off-by: Thorsten Leemhuis
CC: Thomas Gleixner
CC: Greg Kroah-Hartman
CC: Christoph Hellwig
---
Documentation/admin-guide/index.rst |1 +
.../admin-guide/reporting-issues.rst | 1631 +
2 files ch
s.rst.
Hence also add a note to reporting-bugs.rst, telling people they're
better off reading reporting-issues.rst instead.
reporting-bugs.rst is scheduled for removal once reporting-issues.rst
is considered ready.
Signed-off-by: Thorsten Leemhuis
---
Documentation/admin-guide/
his bears pitfalls, hence point that risk out
and suggest to only use this license in combination with the GPLv2.
[1] https://lkml.kernel.org/r/20201201144314.ga14...@lst.de
Signed-off-by: Thorsten Leemhuis
CC: Thomas Gleixner
CC: Greg Kroah-Hartman
CC: Christoph Hellwig
---
LICE
Am 24.11.20 um 10:36 schrieb Christoph Hellwig:
On Tue, Nov 24, 2020 at 10:31:33AM +0100, Thorsten Leemhuis wrote:
Am 24.11.20 um 10:18 schrieb Christoph Hellwig:
On Tue, Nov 24, 2020 at 09:00:01AM +0100, Thorsten Leemhuis wrote:
For context: Patch 2 of this series adds a text to the
Am 01.12.20 um 15:43 schrieb Christoph Hellwig:
On Mon, Nov 30, 2020 at 07:51:37AM -0700, Jonathan Corbet wrote:
@Jonathan: thx for getting the ball rolling again!
We could also, if we saw fit, take the position that anything that has
been processed through the docs build is a derived product
ument
anyway once the last few details have been sorted out.
v2:
* inital version, starting straight with v2 to avoid confusion, as one of the
patches was submitted earlier already
Thorsten Leemhuis (2):
docs: reporting-issues.rst: move tainted check upwards
docs: reporting-issues.rst: shortcu
Provide a much shorter and easier process for users that deal with
regressions in stable and longterm kernels, as those should be reported
quickly.
Signed-off-by: Thorsten Leemhuis
CC: Randy Dunlap
---
v2
* revist, lots of small improvements in various places
v1
* https://lore.kernel.org/linux
ep.
Just moves text around, no other changes.
Signed-off-by: Thorsten Leemhuis
---
.../admin-guide/reporting-issues.rst | 84 +--
1 file changed, 42 insertions(+), 42 deletions(-)
diff --git a/Documentation/admin-guide/reporting-issues.rst
b/Documentation/admin-guide/
eport bugs,
even if they can't test vanilla mainline kernel.
Signed-off-by: Thorsten Leemhuis
CC: Randy Dunlap
---
With this I try to get rid of the last remaining parts that have a
'this needs discussion' box that's in the text. I hope I've found a
middle ground that eve
#x27;s approach more carefully.
Signed-off-by: Thorsten Leemhuis
---
v1:
- kind of a follow up to "[PATCH v1 (RFC)] docs: discourage users from using
bugzilla.kernel.org"[1] – I decided to break that idea down into smaller
pieces, which I guess is easier for everyone
[1
Am 20.11.20 um 22:58 schrieb Jonathan Corbet:
On Fri, 20 Nov 2020 11:46:07 +0100
Thorsten Leemhuis wrote:
Am 19.11.20 um 01:29 schrieb Jonathan Corbet:
On Sun, 15 Nov 2020 11:13:52 +0100
Thorsten Leemhuis wrote:
- Collapse the whole thing down to a patch adding reporting-bugs-v2.rst
Lo!
Pali Rohár wrote on 21.05.2016 16:46:
> […] Thorsten […] can you test this patch if it fixes your freeze problem at
> boottime and when using "sensors" program?
FWIW, I never saw either of those problems. I only saw the third issue
that was mentioned: the CPU fan speed is going up and down as
Pali Rohár wrote on 26.05.2016 17:51:
> On Thursday 26 May 2016 17:39:57 Thorsten Leemhuis wrote:
>> > I need to know if this patch fixes problem on Dell Studio XPS 8000
>> > and Dell Studio XPS 8100 machines, so we can revert git commits:
>> > 6220f4ebd7b4 (&qu
Pali Rohár wrote on 27.05.2016 11:47:
> On Friday 27 May 2016 10:00:05 Thorsten Leemhuis wrote:
>> Pali Rohár wrote on 26.05.2016 17:51:
>> > On Thursday 26 May 2016 17:39:57 Thorsten Leemhuis wrote:
>> >> > I need to know if this patch fixes problem on Dell Studio
Pali Rohár wrote on 27.05.2016 12:45:
> […]
> Looks like there are two different problems with dell-smm-hwmon driver:
> 1) Fan speed going randomly up and down without system freeze
> […]
> So for problem 1) I need to know:
>
> * Is it regression? […]
Yes, it is known to be a regression from f989
://lore.kernel.org/lkml/20181217152043.9989-1-li...@leemhuis.info/
Thorsten Leemhuis (2):
tools: create tools/debugging/ and add a script decoding
/proc/sys/kernel/tainted
docs: Revamp tainted-kernels.rst to make it more comprehensible
Documentation/admin-guide/tainted-kernels.rst | 159
that needs a
wider and more focused discussion with more stakeholders.
Signed-off-by: Thorsten Leemhuis
---
Documentation/admin-guide/tainted-kernels.rst | 159 +++---
Documentation/sysctl/kernel.txt | 50 +++---
2 files changed, 154 insertions(+), 55 deletions(-)
ay.
Signed-off-by: Randy Dunlap
Signed-off-by: Thorsten Leemhuis
---
tools/Makefile | 14 ++-
tools/debugging/Makefile| 16 +++
tools/debugging/kernel-chktaint | 202
3 files changed, 226 insertions(+), 6 deletions(-)
create mode 100644
Jonathan Corbet schrieb am 09.01.19 um 00:47:
> On Tue, 8 Jan 2019 20:40:05 +0100
> Thorsten Leemhuis wrote:
>
> OK, so we're so close... I think the patches are good; they are a welcome
> improvement to the documentation and the script looks great. Thanks for
> doing t
Lo! On 27.03.2018 20:33, Thorsten Leemhuis wrote:
> On 19.03.2018 16:49, Sasha Levin wrote:
>> From: Christoph Hellwig
>> [ Upstream commit 84676c1f21e8ff54befe985f4f14dc1edc10046b ]
> TWIMC: That commit (also reported by autosel for 4.14) triggered a
> regression in 4
On 26.03.2018 01:37, Linus Torvalds wrote:
> […] Anyway. Go out and test. And let's hope next week is nice and calm and
> I can release the final 4.16 next Sunday without any extra rc's.
>
>Linus
Hi! Find below my seventh regression report for Linux 4.16; it's a "the
final releas
Hi! On 22.02.2018 15:57, Artem Bityutskiy wrote:
> On Thu, 2018-02-22 at 16:54 +0200, Artem Bityutskiy wrote:
>> one of our test box Skylake servers does not boot with v4.16-rcX.
>> Bisection lead us to this commit:
>> 84676c1f21e8 genirq/affinity: assign vectors to all possible CPUs
>> Reverting t
Hi! On 11.03.2018 09:20, Martin Steigerwald wrote:
>
> Since 4.16-rc4 (upgraded from 4.15.2 which worked) I have an issue
> with SMART checks occassionally failing like this:
Martin (or someone else): Could you gibe a status update? I have this
issue on my list or regressions, but it's hard to fol
Lo! On 17.01.2017 15:34, Paul Menzel wrote:
> […]
>>> Paul, are you still having this issue?
>> Don't know about Paul, but I did a quick test with rc4 on my machine and
>> the issue is still there :-/
> I didn’t test Linux 4.10-rc4 yet, but I completed the bisection.
>
> ```
> 406e79385f3223d82272
Greg Kroah-Hartman wrote on 16.01.2017 12:05:
> On Sun, Jan 15, 2017 at 11:58:30AM +0100, Greg Kroah-Hartman wrote:
>> On Sun, Jan 15, 2017 at 07:19:03AM +, Winkler, Tomas wrote:
>> > > Subject: Re: [char-misc for 4.10-rc4 V2] mei: bus: enable OS version
>> > > only for SPT
>> > > and newer
>>
Lo! Paul Menzel wrote on 10.01.2017 15:08:
>
> Testing Linux 4.10-rc{1,2,3} the Dell XPS13 does not suspend with the
> attached configuration.
During quick tests I saw similar problems with the Fedora rawhide
configuration in 4.10-rc{1,2} (haven't tried rc3/mainline yet). My free
time was extremel
Hi! Here is my sixth regression report for Linux 4.7. It lists 8
regressions I'm currently aware of; 2 of them are new.
The report also mentions 3 regressions that were fixed since the last
report(¹). There were a few ones that were reported to me in the past
week (many thx for that!) and fixed a
On 05.07.2016 19:32, Linus Torvalds wrote:
> On Tue, Jul 5, 2016 at 9:30 AM, Josh Boyer wrote:
>> On Wed, Jun 22, 2016 at 11:57 AM, Quinn Tran wrote:
>>>
>>> - if (rsp->msix->cpuid != smp_processor_id()) {
>>> + if (rsp->msix && (rsp->msix->cpuid != smp_processor_id())) {
>>
>> Did th
Bruno Prémont wrote on 30.06.2016 17:00:
> In qla24xx_process_response_queue() rsp->msix->cpuid may trigger NULL
> pointer dereference when rsp->msix is NULL:
> […]
> The affected code was introduced by commit
> cdb898c52d1dfad4b4800b83a58b3fe5d352edde
> (qla2xxx: Add irq affinity notification).
>
On 23.06.2016 13:25, James Bottomley wrote:
> On Tue, 2016-06-21 at 17:00 -0400, James Bottomley wrote:
>> On Tue, 2016-06-21 at 18:44 +0300, Ville Syrjälä wrote:
>>> On Tue, Jun 21, 2016 at 09:53:15AM -0400, James Bottomley wrote:
On Mon, 2016-06-20 at 11:03 +0300, Jani Nikula wrote:
> Cc
On 14.06.2016 18:00, Andy Shevchenko wrote:
> On Tue, 2016-06-14 at 10:27 -0500, dinh.li...@anniebear.net wrote:
>>> On Mon, 2016-06-13 at 21:59 -0500, Dinh Nguyen wrote:
>>> I suppose this one, i.e. commit dd4e91d538b3 ("dmaengine: slave
>>> means at
>>> least one of DMA_SLAVE, DMA_CYCLIC"), solve
Hi! Here is my fourth regression report for Linux 4.7; a day earlier then usual.
It has 14 entries;
* 2 of them are new
* 9 regressions (not included here) were fixed since the last report(¹)
* 1 made it to the list after last Sunday (thx for telling me about it Kalle!),
but was fixed before
On 29.05.2016 19:00, Linus Torvalds wrote:
> […] Anyway, enough blathering. Go out and test. […]
And if you find any regressions in 4.7 pre-releases let me know via
regressi...@leemhuis.info I'll try to compile them into a list and post
it on LKML once a week similar to how Rafael did it until a f
Pali Rohár wrote on 27.05.2016 15:21:
> On Friday 27 May 2016 15:05:54 Thorsten Leemhuis wrote:
>> Pali Rohár wrote on 27.05.2016 12:45:
>> So I tried a few things
>> and came to the conclusion: the problem shows up as soon as
>> i8k_get_fan_type() (introduced in f989
FYI: I added this report to the list of regressions for Linux 4.9. I'll
watch this thread for further updates on this issue to document progress
in my weekly reports. Please let me know via regressi...@leemhuis.info
in case the discussion moves to a different place (bugzilla or another
mail thread
On 27.10.2016 10:10, Kalle Valo wrote:
> (Adding Thorsten because of a serious regression and Steven because he
> tried to fix something in the same commit)
Many thx.
I added this report to the list of regressions for Linux 4.9. I'll
watch this thread for further updates on this issue to document
FYI: I added this report to the list of regressions for Linux 4.9. I'll
watch this thread for further updates on this issue to document progress
in my weekly reports. Please let me know via regressi...@leemhuis.info
in case the discussion moves to a different place (bugzilla or another
mail thread
Hi! On 20.10.2016 07:55, Larry Finger wrote:
> Kernel 4.9-rc1 fails to boot on my PowerBook G4 Aluminum (32-bit PowerPC)
> with
> the following splat:
> Kernel Panic - not synching: Attempted to kill init: exitcode = 0x0200
>
Thx for CCing regressi...@leemhuis.info I added this report to the
Hi! Here is my first regression report for Linux 4.9. It lists 14
regressions I'm aware of.
As always: Are you aware of any other regressions? Then please let me
know (simply CC regressi...@leemhuis.info). And please tell me if there
is anything in the report that shouldn't be there.
Ciao, Thor
JFYI: I added this report to the list of regressions for Linux 4.9. I'll
watch this thread for further updates on this issue to document progress
in my weekly reports. Please let me know via regressi...@leemhuis.info
in case the discussion moves to a different place (bugzilla or another
mail thread
Hi! Here is my second regression report for Linux 4.9. It lists 14
regressions I'm aware of. 4 of them are new; 3 got fixed since last weeks
report.
As always: Are you aware of any other regressions? Then please let me
know (simply CC regressi...@leemhuis.info). And please tell me if there
is any
Lo! On 23.12.2016 13:36, Paul Menzel wrote:
>
> I heard that you both have a Dell XPS13. I got the “revision” 9360, and
> installed Debian Stretch/testing on it with Linux 4.8.15 and Linux 4.9-rc8.
>
> When pressing the power button the GNOME dialog, asking what to do
> (restart, power off, …) d
Lo! On 21.11.2016 14:51, Eric Dumazet wrote:
> On Mon, 2016-11-21 at 05:32 -0800, Eric Dumazet wrote:
>> Oh, this was definitely my intent of course, thanks for noticing this
>> typo ;)
> V2 is fixing this, and brings back NUMA spreading,
> (eg alloc_large_system_hash() done at boot time )
What th
Hi! Here is my fifth regression report for Linux 4.9. It lists 11
regressions I'm aware of. 4 of them are new; 6 got fixed since
the last report -- that was two weeks ago, because I yet again
didn't find any spare time to compile a report last Sunday :-/
As always: Are you aware of any other regr
Hi! Here is my fourth regression report for Linux 4.9. It lists 10
regressions I'm aware of. 6 of them are new; 11 got fixed (wow!)
since the last report -- that was two weeks ago, because I
didn't find any spare time to compile a report last Sunday :-/
As always: Are you aware of any other regre
Hi Christoph! Hi Michael!
(Mail roughly based on text from
https://bugzilla.kernel.org/show_bug.cgi?id=194911 )
I'm seeing random crashes during boot every few boot attempts when
running Linux 4.11-rc/mainline in a Fedora 26 guest under a CentOS7 host
(CPU: Intel(R) Pentium(R) CPU G3220) using KV
On 23.03.2017 15:56, Christoph Hellwig wrote:
> Does the patch from Jason in the
> "[REGRESSION] 07ec51480b5e ("virtio_pci: use shared interrupts for
> virtqueues") causes crashes in guest"
> thread fix the issue for you?
Ha, sorry, I'm travelling and wasn't aware that Laura earlier today did
wha
Tested-by: Richard W.M. Jones
> I've queued the fix, thanks everyone!
Thx. Feel free to add
Tested-by: Thorsten Leemhuis
as a kernel with that patch works well in my reboot tests so far.
Ciao, Thorsten
Lo! On 12.03.2017 02:55, Cameron Gutman wrote:
>
> Beginning in 4.11-rc1, it looks like RMI4 is binding to my XPS 13 9343's
> Synaptics touchpad and dropping some errors into dmesg. Here are the
> messages that seem RMI-related:
>
> rmi4_f34 rmi4-00.fn34: rmi_f34v7_probe: Unrecognized bootloader v
@Chao Yu/@Jaegeuk Kim: I'm considering to add this to the regressions
report for 4.11; or is there a reason why it shouldn't be considered a
regression? Ciao, Thorsten
On 08.03.2017 02:21, kernel test robot wrote:
>
> Greeting,
>
> We noticed a -33.7 regression of aim7.jobs-per-min due to commit
Lo! On 14.03.2017 06:10, Cameron Gutman wrote:
> On 03/13/2017 06:35 PM, Andrew Duggan wrote:
>> On 03/13/2017 06:15 AM, Benjamin Tissoires wrote:
>>> On Mar 13 2017 or thereabouts, Benjamin Tissoires wrote:
>>>> On Mar 13 2017 or thereabouts, Thorsten Leemhuis wrote:
On 06.03.2017 00:01, Pavel Machek wrote:
>>> mplayer stopped working after a while. Dmesg says:
>>>
>>> [ 3000.266533] cdc_ether 2-1.2:1.0 usb0: register 'cdc_ether' at
> Now I'm pretty sure it is a regression in v4.11-rc0. Any ideas what to
> try? Bisect will be slow and nasty :-(.
@Pavel, @Chris
Hi! Find below my first regression report for Linux 4.11. It lists 9
regressions I'm currently aware of.
As always: Are you aware of any other regressions? Then please let me
know (simply CC regressi...@leemhuis.info). And please tell me if there
is anything in the report that shouldn't be there.
On 31.05.2016 17:25, Greg KH wrote:
> On Tue, May 31, 2016 at 07:23:06AM -0400, William Breathitt Gray wrote:
>> On Tue, May 31, 2016 at 10:41:49AM +0200, Linus Walleij wrote:
>>> On Sat, May 28, 2016 at 12:08 AM, William Breathitt Gray
>>> wrote:
With the introduction of the ISA_BUS_API Kcon
Hi! Here is my second regression report for 4.7. It has 19 entries; 8 of
them are new; 8 regressions were fixed since the last report (those are
not included in this report) and I dropped 2 which turned out to not be
regressions after all (at least that's what I think right now).
FWIW, it's stil
On 01.11.2016 12:47, Jani Nikula wrote:
> On Tue, 01 Nov 2016, Martin Kepplinger wrote:
>> I'll come up with a nouveau system example and it was quite easy to bisect.
>> To quote the merge commit msg:
>> This also required some changes outside of the IOMMU code, but these are
>> acked by the res
On 31.10.2016 00:32, Larry Finger wrote:
> With the 4.9-rcX kernel, my Dell Latitude D600 laptop has a kernel panic on
> shutdown in routine radeon_connector_unregister(). This problem has been
> bisected to show that commit a481daa88fd4 ("drm/radeon: always apply pci
> shutdown callbacks") is a
JFYI: I added below report to the list of regressions for Linux 4.9.
I'll watch this thread for further updates on this issue to document
progress in my weekly reports. Please let me know via
regressi...@leemhuis.info in case the discussion moves to a different
place (bugzilla or another mail threa
Lo! On 01.11.2016 09:18, Paul Bolle wrote:
> On Sun, 2016-10-30 at 14:20 +0100, Thorsten Leemhuis wrote:
>> As always: Are you aware of any other regressions? Then please let me
>> know (simply CC regressi...@leemhuis.info).
> Do build regressions count?
That's a good que
Hi! On 26.10.2016 17:01, Andy Shevchenko wrote:
> On Wed, 2016-10-26 at 15:06 +0100, Bryan O'Donoghue wrote:
>> On Tue, 2016-10-25 at 08:19 +0200, Lukas Wunner wrote:
>
>> So the conclusion is to apply this patch now and go and look further @
>> locking in a separate series right ? There's not much
Hi! Here is my third regression report for Linux 4.9. It lists 17
regressions I'm aware of. 6 of them are new; 3 got fixed since
last weeks report (a fourth looks fixed as well). The console
problem ("console: don't prefer first registered [...]") got
reported to me multiple times, but the revert t
Lo! On 08.08.2016 10:29, kernel test robot wrote:
>
> FYI, we noticed a -5.1% regression of pixz.throughput due to commit:
>
> commit e6cbd7f2efb433d717af72aa8510a9db6f7a7e05 ("mm, page_alloc: remove fair
> zone allocation policy")
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux
Lo! Dave, below report made it to the list of regression for 4.8, but
afaics nothing happened after the initial report. Was it discussed (and
maybe even fixed?) elsewhere? Or is there some reason why it shouldn't
be on the list of regressions at all?
Ciao, Thorsten
On 13.08.2016 14:37, Peter Senn
Lo! Kefeng, below report made it to the list of regression for 4.8, but
afaics nothing happened after the initial report. Is there maybe some
reason why it shouldn't be on the list of regressions at all? Or was the
problem discussed elsewhere? Or is it even fixed already? I noticed
https://git.kern
Hi! Here is my second regression report for Linux 4.8. It lists 11
regressions. 5 of them are new; 5 mentioned in the last report two
weeks ago got fixed.
FWIW: A small detail: I did not include "Regression - SATA disks behind
USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks]"
(
Hi Rafael!
On 08.07.2016 01:43, Rafael J. Wysocki wrote:
>
> Please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
> acpi-4.7-rc7
>
> to receive ACPI fixes for v4.7-rc7 with top-most commit
> […]
> All of these fix recent regressions in ACPICA, in the ACPI PC
Hi! Here is my fifth regression report for Linux 4.7. It lists 10
regressions I'm currently aware of; 2 of them are new; 1 of those
seems to be a a side effect of a fix for another regression.
The report also mentions 3 regression that I removed from the list, as
it looks like those issues are no
Bruno Prémont wrote on 11.07.2016 09:17:
> On Fri, 8 Jul 2016 09:27:18 +0200 Thorsten Leemhuis wrote:
>> Bruno Prémont wrote on 30.06.2016 17:00:
>> > In qla24xx_process_response_queue() rsp->msix->cpuid may trigger NULL
>> > pointer dereference when rsp->msix
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 invol
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/2
On 02.06.2016 18:29, Al Viro wrote:
> On Thu, Jun 02, 2016 at 02:28:36PM +0800, Huang, Ying wrote:
>> "Huang, Ying" writes:
>
>> Here is the comparison result with perf profile information. You can
>> find it via searching 'perf-profile'.
> [snip]
> Looks like this load is hitting the arseloads
On 09.06.2016 01:29, Zanoni, Paulo R wrote:
> Em Ter, 2016-06-07 às 23:52 +0200, Michal Marek escreveu:
>> On Tue, Jun 07, 2016 at 02:10:28PM +, Zanoni, Paulo R wrote:
>> From b36fad65d61fffe4b662d4bfb1ed673c455a36a2 Mon Sep 17 00:00:00
>> 2001
>> From: Michal Marek
>> Date: Tue, 7 Jun 2016 11
On 15.06.2016 14:25, Joerg Roedel wrote:
> On Wed, Jun 01, 2016 at 12:10:08PM +0100, Chris Wilson wrote:
>> Between acquiring the this_cpu_ptr() and using it, ideally we don't want
>> to be preempted and work on another CPU's private data. this_cpu_ptr()
>> checks whether or not preemption is disab
On 02.06.2016 15:29, Daniel Wagner wrote:
>> Hmmm, Ok. I've been running the lockperf test and kernel builds all
>> day on a filesystem that is identical in shape and size to yours
>> (i.e. xfs_info output is the same) but I haven't reproduced it yet.
> I don't know if that is important: I run the
On 24.06.2016 16:19, George Spelvin wrote:
> Here's a regression you might add.
Thx, added.
> I only reported it to dri-devel,
> since it's DRI-specific, but since there's been thunderous silence
> for a few weeks, I'm trying to be a squeakier wheel.
Added the nouveau developers to CC, maybe i
Hi! Here is my third regression report for Linux 4.7. It has
24 entries; 9 of them are new; 4 regressions (not included here)
were fixed since the last report(¹).
Please let me know if a regression is missing in the list; or if
there is something on the list which shouldn't be there.
HTH, CU, T
101 - 200 of 343 matches
Mail list logo
