Hi Feng,
During testing, a kernel bug was identified with the suspend/resume
functionality on instances running in a public cloud [0]. This bug is a
regression introduced in v6.8-rc1. After a kernel bisect, the following
commit was identified as the cause of the regression:
fd27ef6b
From: Joseph Salisbury
There is not a consistent pattern for checking Hyper-V hypercall status.
Existing code uses a number of variants. The variants work, but a consistent
pattern would improve the readability of the code, and be more conformant
to what the Hyper-V TLFS says about hypercall
From: Joseph Salisbury
This patch makes no functional changes. It simply moves hv_do_rep_hypercall()
out of arch/x86/include/asm/mshyperv.h and into asm-generic/mshyperv.h
hv_do_rep_hypercall() is architecture independent, so it makes sense that it
should be in the architecture independent
The following commit has been merged into the x86/hyperv branch of tip:
Commit-ID: dfc53baae3c6a165a35735b789e3e083786271d6
Gitweb:
https://git.kernel.org/tip/dfc53baae3c6a165a35735b789e3e083786271d6
Author:Joseph Salisbury
AuthorDate:Sat, 26 Sep 2020 07:26:26 -07:00
From: Joseph Salisbury
In the architecture independent version of hyperv-tlfs.h, commit c55a844f46f958b
removed the "X64" in the symbol names so they would make sense for both x86 and
ARM64. That commit added aliases with the "X64" in the x86 version of
hyperv-tlfs.h
so th
uffer()
to not include the log level, enabling more information that *is* useful to
fit in the page.
Requesting in stable kernels, since many kernels running in production are
stable releases.
Cc: sta...@vger.kernel.org
Signed-off-by: Joseph Salisbury
---
drivers/hv/vmbus_drv.c | 2 +-
1 file ch
-Original Message-
From: Michael Kelley
Sent: Friday, June 26, 2020 6:24 PM
To: Joseph Salisbury ; KY Srinivasan
; Haiyang Zhang ; Stephen Hemminger
; sas...@kernel.org; wei@kernel.org
Cc: linux-hyp...@vger.kernel.org; linux-kernel@vger.kernel.org;
sta...@vger.kernel.org
Subject
Thanks for the feedback, Michael. I'll send a v2.
Thanks,
Joe
-Original Message-
From: Michael Kelley
Sent: Friday, June 26, 2020 4:53 PM
To: Joseph Salisbury ; KY Srinivasan
; Haiyang Zhang ; Stephen Hemminger
; sas...@kernel.org; wei@kernel.org
Cc: linu
ing in production are
stable releases.
Cc: sta...@vger.kernel.org
Signed-off-by: Joseph Salisbury
---
drivers/hv/vmbus_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
index 9147ee9d5f7d..d69f4efa3719 100644
--- a/driv
Thanks for the feedback. I'll probably update each patch subject with the
module names as well. I'll send a v2 for all three.
Thanks,
Joe
-Original Message-
From: Michael Kelley
Sent: Monday, April 22, 2019 11:16 PM
To: Joseph Salisbury ; KY Srinivasan
; Haiyang Zhang
Signed-off-by: Joseph Salisbury
---
drivers/hv/vmbus_drv.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
index aa25f3bcbdea..1cb9408b0d40 100644
--- a/drivers/hv/vmbus_drv.c
+++ b/drivers/hv/vmbus_drv.c
@@ -2174,6 +2174,7 @@ static void
Signed-off-by: Joseph Salisbury
---
drivers/input/serio/hyperv-keyboard.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/input/serio/hyperv-keyboard.c
b/drivers/input/serio/hyperv-keyboard.c
index a8b9be3e28db..7935e52b5435 100644
--- a/drivers/input/serio/hyperv-keyboard.c
+++ b
Signed-off-by: Joseph Salisbury
---
drivers/hid/hid-hyperv.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/hid/hid-hyperv.c b/drivers/hid/hid-hyperv.c
index 704049e62d58..d3311d714d35 100644
--- a/drivers/hid/hid-hyperv.c
+++ b/drivers/hid/hid-hyperv.c
@@ -614,5 +614,7 @@ static
Hi David,
A kernel bug report was opened against Ubuntu [0]. This bug is a
regression introduced in v4.15-rc4. The following commit was identified
as the cause of the regression:
2dc0b46b5ea3 ("libata: sata_down_spd_limit should return if
driver has not recorded sstatus speed")
I was h
Hi Daniel,
A kernel bug report was opened against Ubuntu [0]. It was found the
following patch introduced the regression:
da9970668948 ("usb: xhci: Add XHCI_TRUST_TX_LENGTH for Renesas uPD720201")
The bug reporter claims there is a typo in the patch that caused the
regression. I built a test k
On 05/04/2018 07:14 AM, Rafael J. Wysocki wrote:
> On Thursday, May 3, 2018 11:29:18 PM CEST Rafael J. Wysocki wrote:
>> On Thu, May 3, 2018 at 9:11 PM, Bjorn Helgaas wrote:
>>> On Thu, May 03, 2018 at 02:29:02PM -0400, Joseph Salisbury wrote:
>>>> On 05/02/2018 06:
On 05/02/2018 06:41 AM, Rafael J. Wysocki wrote:
> On Tue, May 1, 2018 at 9:55 PM, Bjorn Helgaas wrote:
>> On Tue, May 01, 2018 at 10:34:29AM +0200, Rafael J. Wysocki wrote:
>>> On Mon, Apr 30, 2018 at 4:22 PM, Joseph Salisbury
>>> wrote:
>>>> On 04/16
On 05/02/2018 06:41 AM, Rafael J. Wysocki wrote:
> On Tue, May 1, 2018 at 9:55 PM, Bjorn Helgaas wrote:
>> On Tue, May 01, 2018 at 10:34:29AM +0200, Rafael J. Wysocki wrote:
>>> On Mon, Apr 30, 2018 at 4:22 PM, Joseph Salisbury
>>> wrote:
>>>> On 04/16
Hi Harry,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found the following commit introduced the bug:
commit 4562236b3bc0a28aeb6ee93b2d8a849a4c4e1c7c
Author: Harry Wentland
Date: Tue Sep 12 15:58:20 2017 -0400
drm/amd/dc: Add dc display driver (v2)
On 04/16/2018 11:58 AM, Rafael J. Wysocki wrote:
> On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury
> wrote:
>> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote:
>>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury
>>> wrote:
>>>> Hi Rafael,
>&g
On 04/16/2018 11:58 AM, Rafael J. Wysocki wrote:
> On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury
> wrote:
>> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote:
>>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury
>>> wrote:
>>>> Hi Rafael,
>&g
On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote:
> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury
> wrote:
>> Hi Rafael,
>>
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following tw
Hi Rafael,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following two commits resolved
this bug:
0ce3fcaff929 ("PCI / PM: Restore PME Enable after config space restoration")
0847684cfc5f("PCI / PM: Simplify device wakeup settings code"
Signed-off-by: Joseph Salisbury
---
drivers/md/bcache/bcache.h | 1 +
drivers/md/bcache/super.c | 53 +-
2 files changed, 44 insertions(+), 10 deletions(-)
diff --git a/drivers/md/bcache/bcache.h b/drivers/md/bcache/bcache.h
index 02619ca..8ed7e7a 100644
On 01/17/2018 05:55 PM, Thomas Gleixner wrote:
> On Wed, 17 Jan 2018, Joseph Salisbury wrote:
>> On 01/16/2018 01:59 PM, Thomas Gleixner wrote:
>>
>> Testing of your patch shows that your patch resolves the bug. Thanks
>> for the assistance! Is this something y
On 01/16/2018 01:59 PM, Thomas Gleixner wrote:
> On Tue, 16 Jan 2018, Yu, Fenghua wrote:
>>> From: Thomas Gleixner [mailto:t...@linutronix.de]
>> Is this a Haswell specific issue?
>>
>> I run the following test forever without issue on Broadwell and 4.15.0-rc6
>> with rdt mounted:
>> for ((;;)) do
On 01/16/2018 01:59 PM, Thomas Gleixner wrote:
> On Tue, 16 Jan 2018, Yu, Fenghua wrote:
>>> From: Thomas Gleixner [mailto:t...@linutronix.de]
>> Is this a Haswell specific issue?
>>
>> I run the following test forever without issue on Broadwell and 4.15.0-rc6
>> with rdt mounted:
>> for ((;;)) do
that ASAP?
>>
>> On Sun, 14 Jan 2018, Thomas Gleixner wrote:
>>
>>> On Fri, 12 Jan 2018, Joseph Salisbury wrote:
>>>
>>>> Hi Vikas,
>>>>
>>>> A kernel bug report was opened against Ubuntu [0]. After a k
Hi Vikas,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit 24247aeeabe99eab13b798c2dec066dd6f07
Author: Vikas Shivappa
Date: Tue Aug 15 18:00:43 2017 -0700
x86/intel_rdt/cqm: Improve l
Hi Eric,
A kernel bug report was opened against Ubuntu [0]. It was found that
reverting the following commit resolved this bug:
commit b2504a5dbef3305ef41988ad270b0e8ec289331c
Author: Eric Dumazet
Date: Tue Jan 31 10:20:32 2017 -0800
net: reduce skb_warn_bad_offload() noise
The regr
Hi Christoph,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
909657615d9b ("scsi: libsas: allow async aborts")
The regression was introduced as of v4.12-rc1, and it still exists in
4.14 mainline
Hi Ben,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit da2ba564a6dcf46df4f828624ff55531ff11d5b0
Author: Ben Skeggs
Date: Thu Apr 6 10:35:26 2017 +1000
drm/nouveau: initial support (displ
On 04/27/2017 06:29 PM, Don Bowman wrote:
> On 26 April 2017 at 15:06, Joseph Salisbury
> wrote:
>> Hi Don,
>>
>> Can you see if this bug started happening in v4.11-rc3? Since your
>> running Ubuntu, a kernel is already available here:
>> http://kernel.ubunt
Hi Don,
Can you see if this bug started happening in v4.11-rc3? Since your
running Ubuntu, a kernel is already available here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc3/
If v4.11-rc2 is good and -rc3 is bad, I can help you bisect between the two.
Thanks,
Joe
On 04/25/2017 09:0
ed with REPORTLUN and that works correctly.
>
> Patch needs to go in current 4.11, it is safe but not necessary in older
> kernels.
>
> Signed-off-by: Stephen Hemminger
> Reviewed-by: K. Y. Srinivasan
> Reviewed-by: Christoph Hellwig
>
ed with REPORTLUN and that works correctly.
>
> Patch needs to go in current 4.11, it is safe but not necessary in older
> kernels.
>
> Signed-off-by: Stephen Hemminger
> Reviewed-by: K. Y. Srinivasan
> Reviewed-by: Christoph Hellwig
>
Hi Long Li,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit 40630f462824ee24bc00d692865c86c3828094e0
Author: Long Li
Date: Wed Dec 14 18:46:03 2016 -0800
scsi: storvsc: properly set resid
Hi Ben,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit aeaa881f9b17823028b464893b89c42db797b717
Author: Ben Gamari
Date: Tue Oct 4 11:43:30 2016 -0700
Input: ALPS - set DualPoint flag fo
On 02/02/2017 03:36 PM, Laura Abbott wrote:
> On 02/02/2017 12:17 PM, Joseph Salisbury wrote:
>> Hi Matt,
>>
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following commit reso
On 02/02/2017 03:57 PM, Greg KH wrote:
> On Thu, Feb 02, 2017 at 02:58:16PM -0500, Joseph Salisbury wrote:
>> On 02/02/2017 01:23 PM, Greg KH wrote:
>>> On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
>>>> Hello,
>>>
On 02/02/2017 03:36 PM, Laura Abbott wrote:
> On 02/02/2017 12:17 PM, Joseph Salisbury wrote:
>> Hi Matt,
>>
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following commit reso
Hi Matt,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit 1297667083d5442aafe3e337b9413bf02b114edb
Author: Matt Fleming
Date: Mon Sep 19 13:09:09 2016 +0100
x86/efi: Only map RAM into EFI
On 02/02/2017 01:23 PM, Greg KH wrote:
> On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
>> Hello,
>>
>> Please consider reverting commit
>> 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release.
> What release can I remove it from?
&g
the following thread:
https://lkml.org/lkml/2017/1/6/467
Sincerely,
Joseph Salisbury
Hi Luke,
A kernel bug report was opened against Ubuntu [0]. This bug was fixed
by the following commit in v4.7-rc1:
commit 4c63c2454eff996c5e27991221106eb511f7db38
Author: Luke Dashjr
Date: Thu Oct 29 08:22:21 2015 +
btrfs: bugfix: handle FS_IOC32_{GETFLAGS,SETFLAGS,GETVERSION} in
On 10/18/2016 07:56 AM, Vincent Guittot wrote:
> Le Tuesday 18 Oct 2016 à 12:34:12 (+0200), Peter Zijlstra a écrit :
>> On Tue, Oct 18, 2016 at 11:45:48AM +0200, Vincent Guittot wrote:
>>> On 18 October 2016 at 11:07, Peter Zijlstra wrote:
So aside from funny BIOSes, this should also show up
Dietmar Eggemann
>>>> wrote:
>>>>> On 13/10/16 17:48, Vincent Guittot wrote:
>>>>>> On 13 October 2016 at 17:52, Joseph Salisbury
>>>>>> wrote:
>>>>>>> On 10/13/2016 06:58 AM, Vincent Guittot wrote:
>>>
On 10/13/2016 06:58 AM, Vincent Guittot wrote:
> Hi,
>
> On 12 October 2016 at 18:21, Joseph Salisbury
> wrote:
>> On 10/12/2016 08:20 AM, Vincent Guittot wrote:
>>> On 8 October 2016 at 13:49, Mike Galbraith wrote:
>>>> On Sat, 2016-10-08 at 13:37 +
>>>> On Fri, Oct 07, 2016 at 03:38:23PM -0400, Joseph Salisbury wrote:
>>>>>> Hello Peter,
>>>>>>
>>>>>> A kernel bug report was opened against Ubuntu [0]. After a
>>>>>> kernel
>>>>>> bisect, it
>>>> On Fri, Oct 07, 2016 at 03:38:23PM -0400, Joseph Salisbury wrote:
>>>>>> Hello Peter,
>>>>>>
>>>>>> A kernel bug report was opened against Ubuntu [0]. After a
>>>>>> kernel
>>>>>> bisect, it
On 10/07/2016 03:57 PM, Linus Torvalds wrote:
> On Fri, Oct 7, 2016 at 12:38 PM, Joseph Salisbury
> wrote:
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following commit resolved this bug:
> Hmm. Interesting,
Hello Peter,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit 3d30544f02120b884bba2a9466c87dba980e3be5
Author: Peter Zijlstra
Date: Tue Jun 21 14:27:50 2016 +0200
sched/fair: Apply more PE
Hi Bjorn,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit 1302fcf0d03e6ea74846c7fee14736306ab2ce4b
Author: Bjorn Helgaas
Date: Sat Aug 30 07:23:01 2014 -0600
PCI: Configure *all* devices, n
BugLink: http://bugs.launchpad.net/bugs/1498667
As reported in BugLink, this device has an issue with Linux Power
Management so adding a quirk. This quirk was reccomended by Alan Stern:
http://lkml.iu.edu/hypermail/linux/kernel/1606.2/05590.html
Signed-off-by: Joseph Salisbury
Cc: stable
On 07/06/2016 09:02 PM, Greg KH wrote:
> On Wed, Jul 06, 2016 at 08:58:14PM -0400, Joseph Salisbury wrote:
>> BugLink: http://bugs.launchpad.net/bugs/1498667
>>
>> As reported in BugLink, this device has an issue with Linux Power
>> Management so adding a quirk. Th
BugLink: http://bugs.launchpad.net/bugs/1498667
As reported in BugLink, this device has an issue with Linux Power
Management so adding a quirk. This quirk was reccomended by Alan Stern:
http://lkml.iu.edu/hypermail/linux/kernel/1606.2/05590.html
Signed-off-by: Joseph Salisbury
Cc: stable
On 07/06/2016 07:10 PM, Greg KH wrote:
> On Wed, Jul 06, 2016 at 05:53:47PM -0400, Joseph Salisbury wrote:
>> BugLink: http://bugs.launchpad.net/bugs/1498667
>>
>> As reported in BugLink, this device has an issue with Linux Power Management
>> so
>> adding a quir
BugLink: http://bugs.launchpad.net/bugs/1498667
As reported in BugLink, this device has an issue with Linux Power Management so
adding a quirk. This quirk was reccomended by Alan Stern:
http://lkml.iu.edu/hypermail/linux/kernel/1606.2/05590.html
Signed-off-by: Joseph Salisbury
Cc: stable
On 06/28/2016 11:40 AM, Alan Stern wrote:
> On Tue, 28 Jun 2016, Joseph Salisbury wrote:
>
>> On 06/24/2016 08:06 AM, Joseph Salisbury wrote:
>>> On 06/22/2016 12:14 PM, Greg KH wrote:
>>>> On Wed, Jun 22, 2016 at 11:38:43AM -0400, Joseph Salisbury wrote:
>>
On 06/28/2016 11:40 AM, Alan Stern wrote:
> On Tue, 28 Jun 2016, Joseph Salisbury wrote:
>
>> On 06/24/2016 08:06 AM, Joseph Salisbury wrote:
>>> On 06/22/2016 12:14 PM, Greg KH wrote:
>>>> On Wed, Jun 22, 2016 at 11:38:43AM -0400, Joseph Salisbury wrote:
>>
On 06/24/2016 08:06 AM, Joseph Salisbury wrote:
> On 06/22/2016 12:14 PM, Greg KH wrote:
>> On Wed, Jun 22, 2016 at 11:38:43AM -0400, Joseph Salisbury wrote:
>>> Hi Rupesh,
>>>
>>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>>
On 06/22/2016 12:14 PM, Greg KH wrote:
> On Wed, Jun 22, 2016 at 11:38:43AM -0400, Joseph Salisbury wrote:
>> Hi Rupesh,
>>
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following commit reso
Hi Rupesh,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit a8425292816ceaa8c49e29d2114e85d85a73e080
Author: Rupesh Tatiya
Date: Tue Apr 14 16:36:55 2015 +0530
usb: Enable LPM for USB 2.01
c6e30c01bd6bbc691)
Signed-off-by: Joseph Salisbury
---
net/bridge/br_fdb.c | 16
net/bridge/br_input.c | 8
net/bridge/br_private.h | 3 ++-
3 files changed, 18 insertions(+), 9 deletions(-)
diff --git a/net/bridge/br_fdb.c b/net/bridge/br_fdb.c
index 62c444d.
BugLink: http://bugs.launchpad.net/bugs/1581585
Hello,
Please consider including upstream commit
c65c7a306610ee7c13669a8f5601b472c19dc6f1
in the next v3.13.y-ckt release. It was included in the mainline tree as of
v3.14-rc3. It has been tested and confirmed to resolve
http://bugs.launchpad.ne
Revert "usb: hub: do not clear BOS field during reset device"
Sincerely,
Joseph Salisbury
Replying to thread:
https://lkml.org/lkml/2016/2/26/1090
> -Original Message-
> From: James Bottomley [mailto:james.bottom...@hansenpartnership.com]
> Sent: Thursday, January 28, 2016 7:37 AM
> To: Olaf Hering
> Cc: KY Srinivasan ; Haiyang Zhang
> ; linux-kernel@vger.kernel.org; linux-
>
On 05/06/2016 04:46 PM, Boris Ostrovsky wrote:
> On 05/06/2016 03:38 PM, Joseph Salisbury wrote:
>> On 05/06/2016 03:13 PM, Boris Ostrovsky wrote:
>>> On 05/06/2016 02:48 PM, Thomas Gleixner wrote:
>>>> Yuck. That dies with a divide error. And that looks like XEN is
On 05/06/2016 03:38 PM, Joseph Salisbury wrote:
> On 05/06/2016 02:48 PM, Thomas Gleixner wrote:
>> On Fri, 6 May 2016, Joseph Salisbury wrote:
>>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>>> bisect, it was found that reverting the followi
On 05/06/2016 02:48 PM, Thomas Gleixner wrote:
> On Fri, 6 May 2016, Joseph Salisbury wrote:
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following commit resolved this bug:
>>
>> commit 1f12e32f4cd52
On 05/06/2016 03:13 PM, Boris Ostrovsky wrote:
> On 05/06/2016 02:48 PM, Thomas Gleixner wrote:
>> On Fri, 6 May 2016, Joseph Salisbury wrote:
>>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>>> bisect, it was found that reverting the followi
Hi Thomas,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit 1f12e32f4cd5243ae46d8b933181be0d022c6793
Author: Thomas Gleixner
Date: Mon Feb 22 22:19:15 2016 +
x86/topology: Create logic
Hello Christoph,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit 64d513ac31bd02a3c9b69ef0f36c196f9a9d
Author: Christoph Hellwig
Date: Thu Oct 8 09:28:04 2015 +0100
scsi: use host wide
On 03/28/2016 02:39 PM, Joseph Salisbury wrote:
> On 03/02/2016 04:58 PM, Joseph Salisbury wrote:
>> On 02/29/2016 04:33 AM, Jani Nikula wrote:
>>> On Wed, 24 Feb 2016, Joseph Salisbury
>>> wrote:
>>>> Hi Sonika,
>>>>
>>>> A k
nd did not
require any reverts. Thanks for the quick response!
Testing results in comment #39: http://pad.lv/1554003
>
>
>
>
>
>
> -Original Message-
> From: Joseph Salisbury
> Date: Monday, April 11, 2016 at 11:41 AM
> To: Quinn Tran
> Cc: Dept-Eng QL
needed.
>
> In the mean time, I will download 4.5 rc4 to re-verify.
>
> Regards,
> Quinn Tran
>
>
>
>
>
>
> -Original Message-
> From: Joseph Salisbury
> Date: Monday, April 11, 2016 at 10:26 AM
> To: Quinn Tran
> Cc: Dept-Eng QLA2xxx Upstr
Hello Quinn,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit cdb898c52d1dfad4b4800b83a58b3fe5d352edde
Author: Quinn Tran
Date: Thu Dec 17 14:57:05 2015 -0500
qla2xxx: Add irq affinity no
On 03/02/2016 04:58 PM, Joseph Salisbury wrote:
> On 02/29/2016 04:33 AM, Jani Nikula wrote:
>> On Wed, 24 Feb 2016, Joseph Salisbury wrote:
>>> Hi Sonika,
>>>
>>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>>> bisect, it
fi off and blue for wifi on, but it is the opposite. This bug was
reported in the following bug report:
http://pad.lv/972604
Fixes: 09c9bae26b0d3c9472cb6ae45010460a2cee8b8d ("ath5k: add led pin
configuration for compaq c700 laptop")
Signed-off-by: Joseph Salisbury
Cc: st
On 02/29/2016 04:33 AM, Jani Nikula wrote:
> On Wed, 24 Feb 2016, Joseph Salisbury wrote:
>> Hi Sonika,
>>
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following commit reso
rter.
> Are you referring to the same issue as Oleksandr reported where a single link
> dvi/hdmi cable didn’t work and dual link worked?
I'm not sure if this is the exact issue or not. I'll review the other
thread and compare.
>
> Regards,
> Sonika
>
> -
Hi Sonika,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit 237ed86c693d8a8e4db476976aeb30df4deac74b
Author: Sonika Jindal
Date: Tue Sep 15 09:44:20 2015 +0530
drm/i915: Check live status
da362b09e42ee0bcaf0356afee6078b4f324baff
Author: Eric W. Biederman
Date: Tue Oct 7 12:19:53 2014 -0700
umount: Do not allow unmounting rootfs.
Sincerely,
Joseph Salisbury
On 02/05/2016 05:30 PM, Rainer Weikusat wrote:
> The present unix_stream_read_generic contains various code sequences of
> the form
>
> err = -EDISASTER;
> if ()
> goto out;
>
> This has the unfortunate side effect of possibly causing the error code
> to bleed through to the final
>
> out:
>
On 02/05/2016 02:59 PM, Rainer Weikusat wrote:
> Joseph Salisbury writes:
>> Hi Rainer,
>>
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following commit resolved this bug:
>>
>> commit 3
Hi Rainer,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit 3822b5c2fc62e3de8a0f33806ff279fb7df92432
Author: Rainer Weikusat
Date: Wed Dec 16 20:09:25 2015 +
af_unix: Revert 'lock_inte
50a9eea694ab8e0779069e0a4e0b12e145521468
Author: Doron Tsur
Date: Thu Nov 12 19:35:27 2015 +0200
net/mlx5e: Max mtu comparison fix
Sincerely,
Joseph Salisbury
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordo
e81107d4c6bd098878af9796b24edc8d4a9524fd
Author: Kosuke Tatsukawa
Date: Fri Oct 2 08:27:05 2015 +
tty: fix stall caused by missing memory barrier in drivers/tty/n_tty.c
Commit e81107d4 does not apply cleanly to v3.13.y-ckt, so I performed a
backport, which is
in email 1/1.
Sincerely,
Joseph Salisbury
Kroah-Hartman
[jsalisbury: Backported to 3.13.y:
- Use wake_up_interruptible(), not wake_up_interruptible_poll()
- There are only two spurious uses of waitqueue_active() to remove]
Signed-off-by: Joseph Salisbury
---
drivers/tty/n_tty.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
Hi Jarkko,
A kernel bug report was opened against Ubuntu [0] and in bugzilla[1]. A
kernel bisect was performed, and it identified the following commit as
the first bad commit:
commit 0dc553652102c55a43eb1ab52e2049e478469f53
Author: Jarkko Sakkinen
Date: Fri Dec 12 11:46:35 2014 -0800
tpm
On 07/14/2015 11:17 PM, Jiang Liu wrote:
> On 2015/7/15 1:22, Joseph Salisbury wrote:
>> On 07/13/2015 10:42 PM, Jiang Liu wrote:
>>> On 2015/7/14 3:36, Joseph Salisbury wrote:
>>>> Hello Jiang,
>>>>
>>>> A kernel bug report was opened ag
On 07/13/2015 10:42 PM, Jiang Liu wrote:
> On 2015/7/14 3:36, Joseph Salisbury wrote:
>> Hello Jiang,
>>
>> A kernel bug report was opened against Ubuntu [0]. It was found that
>> reverting the following commit resolves this bug:
>>
>> commit cd68f6bd53c
On 07/13/2015 10:42 PM, Jiang Liu wrote:
> On 2015/7/14 3:36, Joseph Salisbury wrote:
>> Hello Jiang,
>>
>> A kernel bug report was opened against Ubuntu [0]. It was found that
>> reverting the following commit resolves this bug:
>>
>> commit cd68f6bd53c
Hello Jiang,
A kernel bug report was opened against Ubuntu [0]. It was found that
reverting the following commit resolves this bug:
commit cd68f6bd53cf89d1d5ed889b8af65e9c3574a079
Author: Jiang Liu
Date: Mon Oct 27 16:11:52 2014 +0800
x86, irq, acpi: Get rid of special handling of GSI for
On 12/19/2012 05:20 PM, Joseph Salisbury wrote:
> On 12/19/2012 04:07 PM, Milan Broz wrote:
>> Does this help?
>>
>> dm-crypt: never use write same
>>
>> Ciphertext device is not compatible with WRITE SAME,
>> disable it for all dmcrypt devices.
>>
>
: factor out ah flushing
The bug reporter states this bug is only happening with the 3.19 kernel,
these commits may not be needed in other stable kernels.
Sincerely,
Joseph Salisbury
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Drivers: hv: vmbus: Correcting truncation error for constant
HV_CRASH_CTL_CRASH_NOTIFY
Commit 96c1d05 does not apply cleanly to v3.14.y, so I performed a backport,
which is in email 1/1.
Sincerely,
Joseph Salisbury
Nick Meier (1):
Drivers: hv: vmbus: Add support for VMBus panic notifier
96c1d0581d00f7abe033350edb021a9d947d8d81)
Signed-off-by: Joseph Salisbury
---
drivers/hv/hyperv_vmbus.h | 11 +++
drivers/hv/vmbus_drv.c| 40
2 files changed, 51 insertions(+)
diff --git a/drivers/hv/hyperv_vmbus.h b/drivers/hv/hyperv_vmbus.h
index e055176
-Hartman
(backported from commit 96c1d0581d00f7abe033350edb021a9d947d8d81)
Signed-off-by: Joseph Salisbury
---
drivers/hv/hyperv_vmbus.h | 11 +++
drivers/hv/vmbus_drv.c| 40
2 files changed, 51 insertions(+)
diff --git a/drivers/hv
Drivers: hv: vmbus: Correcting truncation error for constant
HV_CRASH_CTL_CRASH_NOTIFY
Commit 96c1d05 does not apply cleanly to v3.13.y-ckt, so I performed a
backport, which is
in email 1/1.
Sincerely,
Joseph Salisbury
Nick Meier (1):
Drivers: hv: vmbus: Add support for VMBus panic
1 - 100 of 262 matches
Mail list logo
