> "Linus" == Linus Torvalds writes:
Linus> It's not in my tree, at least.
Not in scsi-fixes either. I have been waiting for a "real" patch
submission with one or more Tested-by: tags. I generally don't queue
something that comes with a "try this untested workaround" patch
description.
Quinn
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
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 this wind up going into an official commit somewhere?
On Wed, Jun 22, 2016 at 11:57 AM, Quinn Tran wrote:
> Johannes, Martin,
>
> Based on the screen shot/call trace, it looks like this adapter is not using
> MSIX. It defaulted back to MSI or INTx interrupt. The code made an
> assumption of MSIX is available. There is no point in go through t
Am Sonntag, den 26.06.2016, 14:52 +0200 schrieb Thorsten Leemhuis:
> On 24.06.2016 16:19, George Spelvin wrote:
> >
> > Here's a regression you might add.
> Thx, added.
>
Probably the same bug as
https://bugzilla.kernel.org/show_bug.cgi?id=119861 and already fixed in
the last -rc.
Regards,
Lu
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
Linus Torvalds writes:
> On Thu, Jun 23, 2016 at 9:13 AM, Quinn Tran wrote:
>>
>>
>> QT: setting up the interrupt vector does not mean the interrupt starts
>> firing immediately.
>
> Actually, it very much can mean that. If the interrupt can possibly be
> shared, there is a very real possibilit
On Thu, Jun 23, 2016 at 9:13 AM, Quinn Tran wrote:
>
>
> QT: setting up the interrupt vector does not mean the interrupt starts firing
> immediately.
Actually, it very much can mean that. If the interrupt can possibly be
shared, there is a very real possibility of it fiding immediately.
Now, wi
-Original Message-
From: Johannes Thumshirn
Date: Thursday, June 23, 2016 at 12:22 AM
To: Quinn Tran
Cc: "Martin K. Petersen" , Linus Torvalds
, Josh Boyer ,
Thorsten Leemhuis , linux-kernel
, linux-scsi
Subject: Re: Reported regressions for 4.7 as of Sunday, 2016-06-
[+ Cc linux-s...@vger.kernel.org ]
On Wed, Jun 22, 2016 at 03:57:35PM +, Quinn Tran wrote:
> Johannes, Martin,
>
> Based on the screen shot/call trace, it looks like this adapter is not using
> MSIX. It defaulted back to MSI or INTx interrupt. The code made an
> assumption of MSIX is a
* then set it here.
*/
Regards,
Quinn Tran
-Original Message-
From: Johannes Thumshirn
Date: Wednesday, June 22, 2016 at 4:51 AM
To: "Martin K. Petersen"
Cc: Linus Torvalds , Josh Boyer
, Thorsten Leemhuis ,
linux-kernel , Quinn Tran
Subject: Re: Reported regressions
On Tue, Jun 21, 2016 at 09:25:18PM -0400, Martin K. Petersen wrote:
> > "Linus" == Linus Torvalds writes:
>
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1348342
>
> This first one appears to be a crash in a USB sound doodad and not
> qla2xxx. Also, this appears to be where the 4.5.5 -> 4
Thorsten Leemhuis writes:
> 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 rep/stat: 2016-05-27 / 20
inux-kernel
, Quinn Tran
Subject: Re: Reported regressions for 4.7 as of Sunday, 2016-06-19
>>>>>> "Linus" == Linus Torvalds writes:
>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=1348342
>
>This first one appears to be a crash in a USB sound
> "Linus" == Linus Torvalds writes:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1348342
This first one appears to be a crash in a USB sound doodad and not
qla2xxx. Also, this appears to be where the 4.5.5 -> 4.5.6 notion comes
from. So we can probably ignore 4.5.5 as the last good revisio
On Tue, Jun 21, 2016 at 4:40 PM, Linus Torvalds
wrote:
> On Tue, Jun 21, 2016 at 4:11 AM, Josh Boyer wrote:
>> On Sun, Jun 19, 2016 at 10:52 AM, Thorsten Leemhuis
>> wrote:
>>> Description:BUG: unable to handle kernel NULL pointer dereference […]
>>> qla24xx_process_response_queue+0x49/0x4b
On Tue, Jun 21, 2016 at 4:11 AM, Josh Boyer wrote:
> On Sun, Jun 19, 2016 at 10:52 AM, Thorsten Leemhuis
> wrote:
>> Description:BUG: unable to handle kernel NULL pointer dereference […]
>> qla24xx_process_response_queue+0x49/0x4b0 [qla2xxx]
>> Report: https://bugzilla.kernel.org/sho
On Sun, Jun 19, 2016 at 10:52 AM, Thorsten Leemhuis
wrote:
> Description:BUG: unable to handle kernel NULL pointer dereference […]
> qla24xx_process_response_queue+0x49/0x4b0 [qla2xxx]
> Report: https://bugzilla.kernel.org/show_bug.cgi?id=120201
> Latest status: n/a
> Date rep/stat:
Another important one is the rename regression in XFS and ext4 that
I suspect is due the VFS changes in 4.7:
http://oss.sgi.com/pipermail/xfs/2016-June/049138.html
http://oss.sgi.com/pipermail/xfs/2016-June/049309.html
possibly related:
http://marc.info/?l=linux-kernel&m=146605889024559&w=2
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
20 matches
Mail list logo
