Re: Linux 5.10.25

2021-03-21 Thread Jamie Heilman
Jamie Heilman wrote: > Greg Kroah-Hartman wrote: > > On Sat, Mar 20, 2021 at 09:31:55PM +0000, Jamie Heilman wrote: > > > [ugh, resent with the lkml headers unbroken, sorry about the dupe] > > > > > > Greg Kroah-Hartman wrote: > > > > J. Bruce

Re: Linux 5.10.25

2021-03-21 Thread Jamie Heilman
Greg Kroah-Hartman wrote: > On Sat, Mar 20, 2021 at 09:31:55PM +0000, Jamie Heilman wrote: > > [ugh, resent with the lkml headers unbroken, sorry about the dupe] > > > > Greg Kroah-Hartman wrote: > > > J. Bruce Fields (2): > > > Revert "n

Re: Linux 5.10.25

2021-03-20 Thread Jamie Heilman
89] ---[ end trace 171bde4774bc9795 ]--- Can't readily reproduce it though, so likely a race condition or something that requires more state buildup than I have after a few minutes of uptime. Kernel config at http://audible.transient.net/~jamie/k/nfsd.config-5.10.25 in case you think this worth mor

Re: [kbuild-all] Re: [PATCH] gcov: fail build on gcov_info size mismatch

2021-03-15 Thread Jamie Heilman
Linus Torvalds wrote: > On Sun, Mar 14, 2021 at 7:32 PM Rong Chen wrote: > > > > It can be reproduced with '-a' option in dash: > > Oh, ok. That kind of explains it. > > 'dash' is trash. Please somebody make a bug report. > > > $ a="!" > > $ [ "$a" = ".size" ] > > $ [ "$a" =

Re: [Nouveau] nouveau regression post v5.8, still present in v5.10

2021-02-02 Thread Jamie Heilman
Jamie Heilman wrote: > Jamie Heilman wrote: > > Karol Herbst wrote: > > > fyi, there is a patch which solves a maybe related issue on your GPU, > > > mind giving it a try before we dig further? > > > https://gitlab.freedesktop.org/drm/nouveau/-/issues

Re: bisected regression in v5.11-rc1 snd-usb-audio

2021-01-23 Thread Jamie Heilman
Takashi Iwai wrote: > On Sat, 23 Jan 2021 12:08:02 +0100, > Jamie Heilman wrote: > > > > > If the problem is still seen with the very latest Linus tree and the > > > previous patch, please enable the dyndbg, e.g. pass dydbg=+p option to > > >

Re: bisected regression in v5.11-rc1 snd-usb-audio

2021-01-23 Thread Jamie Heilman
Takashi Iwai wrote: > On Fri, 22 Jan 2021 11:03:48 +0100, > Jamie Heilman wrote: > > > > Takashi Iwai wrote: > > > You seem hitting a firmware bug, and it doesn't look like the only > > > case. Interestingly, the backport of 5.11 USB-audio stuff on 5.3 >

Re: [Nouveau] nouveau regression post v5.8, still present in v5.10

2021-01-22 Thread Jamie Heilman
Jamie Heilman wrote: > Karol Herbst wrote: > > fyi, there is a patch which solves a maybe related issue on your GPU, > > mind giving it a try before we dig further? > > https://gitlab.freedesktop.org/drm/nouveau/-/issues/14#note_767791 > > So, I tried that. Tur

Re: [Nouveau] nouveau regression post v5.8, still present in v5.10

2021-01-22 Thread Jamie Heilman
problems; hopefully that version is free from issues, but we'll see... > On Thu, Jan 21, 2021 at 3:33 AM Jamie Heilman > wrote: > > > > Karol Herbst wrote: > > > On Wed, Jan 6, 2021 at 4:25 AM Jamie Heilman > > > wrote: > > > > > > > > Jam

Re: bisected regression in v5.11-rc1 snd-usb-audio

2021-01-22 Thread Jamie Heilman
rkaround, perform it only for the necessary devices; > currently MOTU devices are known to need the valid altset checks, so > filter out other devices. > > Fixes: 93db51d06b32 ("ALSA: usb-audio: Check valid altsetting at parsing > rates for UAC2/3") > Reported-by: Jamie He

bisected regression in v5.11-rc1 snd-usb-audio

2021-01-22 Thread Jamie Heilman
ps, I know---but none of this changes even if I plug it directly into my workstation's USB ports, I tried that). I'm happy to try any patches, or provide more details, just ask. -- Jamie Heilman http://audible.transient.net/~jamie/ [1] it's never been quite right, if you ever w

Re: [Nouveau] nouveau regression post v5.8, still present in v5.10

2021-01-20 Thread Jamie Heilman
Karol Herbst wrote: > On Wed, Jan 6, 2021 at 4:25 AM Jamie Heilman > wrote: > > > > Jamie Heilman wrote: > > > Jamie Heilman wrote: > > > > Karol Herbst wrote: > > > > > do you think you'd be able to do a kernel bisect in order to p

Re: [Nouveau] nouveau regression post v5.8, still present in v5.10

2021-01-05 Thread Jamie Heilman
Jamie Heilman wrote: > Jamie Heilman wrote: > > Karol Herbst wrote: > > > do you think you'd be able to do a kernel bisect in order to pinpoint > > > the actual commit causing it? Thanks > > > > No. I can't reproduce it reliably. I if I could, bisection w

Re: [Nouveau] nouveau regression post v5.8, still present in v5.10

2021-01-04 Thread Jamie Heilman
Jamie Heilman wrote: > Karol Herbst wrote: > > do you think you'd be able to do a kernel bisect in order to pinpoint > > the actual commit causing it? Thanks > > No. I can't reproduce it reliably. I if I could, bisection wouldn't > be a problem but as I can't

Re: [Nouveau] nouveau regression post v5.8, still present in v5.10

2021-01-04 Thread Jamie Heilman
here's essentially no chance. I know it regressed roughly in 5.8-rc1 only because that's what I was running when the first event occured. > On Sun, Dec 27, 2020 at 8:16 PM Jamie Heilman > wrote: > > > > Something between v5.8 and v5.9 has resulted in periodically losing video. > > U

nouveau regression post v5.8, still present in v5.10

2020-12-24 Thread Jamie Heilman
If there's more debugging I can do when this happens, I'd love to know what it is. kernel config: http://audible.transient.net/~jamie/k/nouveau.config-5.10.0 dmesg at boot: http://audible.transient.net/~jamie/k/nouveau.dmesg -- Jamie Heilman http://audible.transient.net/~jamie/

Re: [PATCH] kvm: x86/mmu: Fix is_tdp_mmu_check when using PAE

2020-11-11 Thread Jamie Heilman
* and the root HPA will not have a shadow page associated with it. > + */ > + if (!sp) > + return false; > + > return sp->tdp_mmu_page && sp->root_count; > } > > -- > 2.29.2.222.g5d2a92d10f8-goog > -- Jamie Heilman http://audible.transient.net/~jamie/

null pointer deref in kvm

2020-11-09 Thread Jamie Heilman
need anything else. -- Jamie Heilman http://audible.transient.net/~jamie/ # # Automatically generated file; DO NOT EDIT. # Linux/x86 5.10.0-rc2 Kernel Configuration # CONFIG_CC_VERSION_TEXT="gcc (Debian 10.2.0-16) 10.2.0" CONFIG_CC_IS_GCC=y CONFIG_GCC_VERSION=100200

Re: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

2016-05-03 Thread Jamie Heilman
Tadeusz Struk wrote: > On 05/03/2016 07:26 PM, Jamie Heilman wrote: > >>> Alrighty, presumably relevant bits: > >>> > > > >>> > > X.509: Cert Issuer: Build time autogenerated kernel key > >>> > > X.509: Cert Subject: Bu

Re: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

2016-05-03 Thread Jamie Heilman
Tadeusz Struk wrote: > On 05/03/2016 07:26 PM, Jamie Heilman wrote: > >>> Alrighty, presumably relevant bits: > >>> > > > >>> > > X.509: Cert Issuer: Build time autogenerated kernel key > >>> > > X.509: Cert Subject: Bu

Re: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

2016-05-03 Thread Jamie Heilman
David Howells wrote: > (cc'ing Tadeusz as he did the pkcs1 padding function) > > Jamie Heilman <ja...@audible.transient.net> wrote: > > > > > Problem loading in-kernel X.509 certificate (-2) > > > > > > ENOENT? Hmmm... The onl

Re: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

2016-05-03 Thread Jamie Heilman
David Howells wrote: > (cc'ing Tadeusz as he did the pkcs1 padding function) > > Jamie Heilman wrote: > > > > > Problem loading in-kernel X.509 certificate (-2) > > > > > > ENOENT? Hmmm... The only place that is generated is in the crypto layer.

Re: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

2016-05-03 Thread Jamie Heilman
Tadeusz Struk wrote: > Could you please check if this one fixes the problem for you: > https://patchwork.kernel.org/patch/8766361/ That patch is already present by 4.6-rc5 and the problem still exists, so no, it doesn't. -- Jamie Heilman http://audible.transient.net/~jamie/

Re: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

2016-05-03 Thread Jamie Heilman
Tadeusz Struk wrote: > Could you please check if this one fixes the problem for you: > https://patchwork.kernel.org/patch/8766361/ That patch is already present by 4.6-rc5 and the problem still exists, so no, it doesn't. -- Jamie Heilman http://audible.transient.net/~jamie/

Re: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

2016-05-03 Thread Jamie Heilman
Herbert Xu wrote: > On Sat, Apr 30, 2016 at 08:32:48AM +0000, Jamie Heilman wrote: > > I usually build my kernels to require module signatures and use > > automatic signing. As of v4.6-rc1 I'm getting this on boot: > > > > Problem loading in-kernel X.509 certifica

Re: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

2016-05-03 Thread Jamie Heilman
Herbert Xu wrote: > On Sat, Apr 30, 2016 at 08:32:48AM +0000, Jamie Heilman wrote: > > I usually build my kernels to require module signatures and use > > automatic signing. As of v4.6-rc1 I'm getting this on boot: > > > > Problem loading in-kernel X.509 certifica

Re: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

2016-05-03 Thread Jamie Heilman
2a06035504030c234275696c642074696d65206175746f67656e657261746564206b65726e656c206b6579" X.509: Request for key 'ex:008a32081403f1709a312c302a06035504030c234275696c642074696d65206175746f67656e657261746564206b65726e656c206b6579' err -11 full dmesg at http://audible.transient.net/~jamie/k/modsign.dmesg-debugging -- Jamie Heilman http://audible.transient.net/~jamie/

Re: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

2016-05-03 Thread Jamie Heilman
2a06035504030c234275696c642074696d65206175746f67656e657261746564206b65726e656c206b6579" X.509: Request for key 'ex:008a32081403f1709a312c302a06035504030c234275696c642074696d65206175746f67656e657261746564206b65726e656c206b6579' err -11 full dmesg at http://audible.transient.net/~jamie/k/modsign.dmesg-debugging -- Jamie Heilman http://audible.transient.net/~jamie/

v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

2016-04-30 Thread Jamie Heilman
to the crypto layer) For some reason after this commit my system keyring always ends up empty. I use the deb-pkg make target. My kernel config can be found at http://audible.transient.net/~jamie/k/modsign.config-4.6.0-rc5-guest Let me know if you need anything else. -- Jamie Heilman

v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

2016-04-30 Thread Jamie Heilman
to the crypto layer) For some reason after this commit my system keyring always ends up empty. I use the deb-pkg make target. My kernel config can be found at http://audible.transient.net/~jamie/k/modsign.config-4.6.0-rc5-guest Let me know if you need anything else. -- Jamie Heilman

Re: regression bisected; KVM: entry failed, hardware error 0x80000021

2014-12-25 Thread Jamie Heilman
Chen, Tiejun wrote: > On 2014/12/24 19:02, Jamie Heilman wrote: > >Chen, Tiejun wrote: > >>On 2014/12/23 15:26, Jamie Heilman wrote: > >>>Chen, Tiejun wrote: > >>>>On 2014/12/23 9:50, Chen, Tiejun wrote: > >>>>>On 2014/12/22 17:2

Re: regression bisected; KVM: entry failed, hardware error 0x80000021

2014-12-25 Thread Jamie Heilman
Chen, Tiejun wrote: On 2014/12/24 19:02, Jamie Heilman wrote: Chen, Tiejun wrote: On 2014/12/23 15:26, Jamie Heilman wrote: Chen, Tiejun wrote: On 2014/12/23 9:50, Chen, Tiejun wrote: On 2014/12/22 17:23, Jamie Heilman wrote: KVM internal error. Suberror: 1 emulation failure EAX=000de494

Re: regression bisected; KVM: entry failed, hardware error 0x80000021

2014-12-24 Thread Jamie Heilman
Chen, Tiejun wrote: > On 2014/12/23 15:26, Jamie Heilman wrote: > >Chen, Tiejun wrote: > >>On 2014/12/23 9:50, Chen, Tiejun wrote: > >>>On 2014/12/22 17:23, Jamie Heilman wrote: > >>>>KVM internal error. Suberror: 1 > >>>>emulation failu

Re: regression bisected; KVM: entry failed, hardware error 0x80000021

2014-12-24 Thread Jamie Heilman
Chen, Tiejun wrote: On 2014/12/23 15:26, Jamie Heilman wrote: Chen, Tiejun wrote: On 2014/12/23 9:50, Chen, Tiejun wrote: On 2014/12/22 17:23, Jamie Heilman wrote: KVM internal error. Suberror: 1 emulation failure EAX=000de494 EBX= ECX= EDX=0cfd ESI=0059 EDI

Re: regression bisected; KVM: entry failed, hardware error 0x80000021

2014-12-22 Thread Jamie Heilman
Chen, Tiejun wrote: > On 2014/12/23 9:50, Chen, Tiejun wrote: > >On 2014/12/22 17:23, Jamie Heilman wrote: > >>Chen, Tiejun wrote: > >>>On 2014/12/21 20:46, Jamie Heilman wrote: > >>>>With v3.19-rc1 when I run qemu-system-x86_64 -machine pc,accel=kv

Re: regression bisected; KVM: entry failed, hardware error 0x80000021

2014-12-22 Thread Jamie Heilman
Chen, Tiejun wrote: > On 2014/12/21 20:46, Jamie Heilman wrote: > >With v3.19-rc1 when I run qemu-system-x86_64 -machine pc,accel=kvm I > >get: > > > >KVM: entry failed, hardware error 0x8021 > > Looks some MSR writing issues such a failed entry. > >

Re: regression bisected; KVM: entry failed, hardware error 0x80000021

2014-12-22 Thread Jamie Heilman
Chen, Tiejun wrote: On 2014/12/23 9:50, Chen, Tiejun wrote: On 2014/12/22 17:23, Jamie Heilman wrote: Chen, Tiejun wrote: On 2014/12/21 20:46, Jamie Heilman wrote: With v3.19-rc1 when I run qemu-system-x86_64 -machine pc,accel=kvm I get: KVM: entry failed, hardware error 0x8021

Re: regression bisected; KVM: entry failed, hardware error 0x80000021

2014-12-22 Thread Jamie Heilman
Chen, Tiejun wrote: On 2014/12/21 20:46, Jamie Heilman wrote: With v3.19-rc1 when I run qemu-system-x86_64 -machine pc,accel=kvm I get: KVM: entry failed, hardware error 0x8021 Looks some MSR writing issues such a failed entry. If you're running a guest on an Intel machine without

regression bisected; KVM: entry failed, hardware error 0x80000021

2014-12-21 Thread Jamie Heilman
in so far that I can run kvm again without the aforementioned error, but I haven't tested it thoroughly beyond that. Let me know if you need more information or testing. -- Jamie Heilman http://audible.transient.net/~jamie/ -- To unsubscribe from this list: send the line "uns

regression bisected; KVM: entry failed, hardware error 0x80000021

2014-12-21 Thread Jamie Heilman
reverting this commit appears to fix the issue, in so far that I can run kvm again without the aforementioned error, but I haven't tested it thoroughly beyond that. Let me know if you need more information or testing. -- Jamie Heilman http://audible.transient.net/~jamie

Re: [3.7-rc5/rc6 regression] "drm/nvc0/disp: fix regression in vblank semaphore release" broke nouveau driver and mplayer

2012-11-17 Thread Jamie Heilman
-xorg-video-nouveau 1:1.0.1-3 and mplayer2 2.0-600-g95e81df w/the xv video output driver > git bisect identified the following culprit: > > 11d92561c81be2f4a7af37f035e1af294b960abe is the first bad commit I bisected to the same commit as well. -- Jamie Heilman http:

Re: [3.7-rc5/rc6 regression] drm/nvc0/disp: fix regression in vblank semaphore release broke nouveau driver and mplayer

2012-11-17 Thread Jamie Heilman
and mplayer2 2.0-600-g95e81df w/the xv video output driver git bisect identified the following culprit: 11d92561c81be2f4a7af37f035e1af294b960abe is the first bad commit I bisected to the same commit as well. -- Jamie Heilman http://audible.transient.net/~jamie

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-16 Thread Jamie Heilman
that was updated, but the > former was the one that the callback used. > > Symptoms were a long delay on utime(). This is because the utime() > generated a setattr which recalled a delegation, but the cb_recall was > ignored by the client because it had the wrong s

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-16 Thread Jamie Heilman
J. Bruce Fields wrote: > On Wed, Aug 15, 2012 at 01:58:54PM +0000, Jamie Heilman wrote: > > Jamie Heilman wrote: > > > I'll try to get full rcpdebug traces on client and server as the delay > > > is occuring in the hopes that helps pin things down, and post them > >

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-16 Thread Jamie Heilman
J. Bruce Fields wrote: On Wed, Aug 15, 2012 at 01:58:54PM +, Jamie Heilman wrote: Jamie Heilman wrote: I'll try to get full rcpdebug traces on client and server as the delay is occuring in the hopes that helps pin things down, and post them separately. OK, here are the logs

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-16 Thread Jamie Heilman
were a long delay on utime(). This is because the utime() generated a setattr which recalled a delegation, but the cb_recall was ignored by the client because it had the wrong security flavor. Cc: sta...@vger.kernel.org Reported-by: Jamie Heilman ja

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-15 Thread Jamie Heilman
Jamie Heilman wrote: > I'll try to get full rcpdebug traces on client and server as the delay > is occuring in the hopes that helps pin things down, and post them > separately. OK, here are the logs from client and server, where a run of my test program under strace -T resulted in: uti

v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-15 Thread Jamie Heilman
from http://marc.info/?l=linux-nfs=133950479803025 or face additional problems.) I'll try to get full rcpdebug traces on client and server as the delay is occuring in the hopes that helps pin things down, and post them separately. -- Jamie Heilman http://audible.transient.net/~j

v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-15 Thread Jamie Heilman
or face additional problems.) I'll try to get full rcpdebug traces on client and server as the delay is occuring in the hopes that helps pin things down, and post them separately. -- Jamie Heilman http://audible.transient.net/~jamie/ #include sys/types.h #include sys/stat.h

Re: v3.5 nfsd4 regression; utime sometimes takes 40+ seconds to return

2012-08-15 Thread Jamie Heilman
Jamie Heilman wrote: I'll try to get full rcpdebug traces on client and server as the delay is occuring in the hopes that helps pin things down, and post them separately. OK, here are the logs from client and server, where a run of my test program under strace -T resulted in: utime(utime