Re: linux-5.10.11 build failure

2021-02-01 Thread Chris Clayton
Hi Greg, On 29/01/2021 15:14, Josh Poimboeuf wrote: > On Fri, Jan 29, 2021 at 12:09:53PM +0100, Greg Kroah-Hartman wrote: >> On Fri, Jan 29, 2021 at 11:03:26AM +0000, Chris Clayton wrote: >>> >>> >>> On 29/01/2021 10:11, Greg Kroah-Hartman wrote: >>&

Re: linux-5.10.11 build failure

2021-01-28 Thread Chris Clayton
On 28/01/2021 15:52, Josh Poimboeuf wrote: > On Thu, Jan 28, 2021 at 11:24:47AM +, Thomas Backlund wrote: >> Den 28.1.2021 kl. 12:05, skrev Chris Clayton: >>> >>> On 28/01/2021 09:34, Greg Kroah-Hartman wrote: >>>> On Thu, Jan 28, 2021 at 09:17:10

Re: linux-5.10.11 build failure

2021-01-28 Thread Chris Clayton
On 28/01/2021 14:41, Greg Kroah-Hartman wrote: > On Thu, Jan 28, 2021 at 01:38:25PM +0000, Chris Clayton wrote: >> Thanks, Thomas. >> >> On 28/01/2021 11:24, Thomas Backlund wrote: >>> Den 28.1.2021 kl. 12:05, skrev Chris Clayton: >>>> >>

Re: linux-5.10.11 build failure

2021-01-28 Thread Chris Clayton
Thanks, Thomas. On 28/01/2021 11:24, Thomas Backlund wrote: > Den 28.1.2021 kl. 12:05, skrev Chris Clayton: >> >> On 28/01/2021 09:34, Greg Kroah-Hartman wrote: >>> On Thu, Jan 28, 2021 at 09:17:10AM +, Chris Clayton wrote: >>>> Hi, >>>> &

Re: linux-5.10.11 build failure

2021-01-28 Thread Chris Clayton
On 28/01/2021 09:34, Greg Kroah-Hartman wrote: > On Thu, Jan 28, 2021 at 09:17:10AM +0000, Chris Clayton wrote: >> Hi, >> >> Building 5.10.11 fails on my (x86-64) laptop thusly: >> >> .. >> >> AS arch/x86/entry/thunk_64.o >> CC arch

linux-5.10.11 build failure

2021-01-28 Thread Chris Clayton
Hi, Building 5.10.11 fails on my (x86-64) laptop thusly: .. AS arch/x86/entry/thunk_64.o CC arch/x86/entry/vsyscall/vsyscall_64.o AS arch/x86/realmode/rm/header.o CC arch/x86/mm/pat/set_memory.o CC arch/x86/events/amd/core.o CC arch/x86/kernel/fpu/init.o

Re: [PATCH] misc: rtsx: do not setting OC_POWER_DOWN reg in rtsx_pci_init_ocp()

2020-10-15 Thread Chris Clayton
Hi Greg, On 18/09/2020 15:35, Chris Clayton wrote: > Mmm, gmail on android seems to have snuck some html into my reply, so here > goes again... > > On 14/09/2020 16:58, Greg KH wrote: >> On Sun, Sep 13, 2020 at 09:40:56AM +0100, Chris Clayton wrote: >>> Hi Greg and

Re: [PATCH] misc: rtsx: do not setting OC_POWER_DOWN reg in rtsx_pci_init_ocp()

2020-09-18 Thread Chris Clayton
Mmm, gmail on android seems to have snuck some html into my reply, so here goes again... On 14/09/2020 16:58, Greg KH wrote: > On Sun, Sep 13, 2020 at 09:40:56AM +0100, Chris Clayton wrote: >> Hi Greg and Arnd, >> >> On 24/08/2020 04:00, ricky...@realtek.com wrot

Re: [PATCH] misc: rtsx: do not setting OC_POWER_DOWN reg in rtsx_pci_init_ocp()

2020-09-14 Thread Chris Clayton
Thanks Bjorn. On 13/09/2020 17:49, Bjorn Helgaas wrote: > On Sun, Sep 13, 2020 at 09:40:56AM +0100, Chris Clayton wrote: >> Hi Greg and Arnd, >> >> On 24/08/2020 04:00, ricky...@realtek.com wrote: >>> From: Ricky Wu >>> >>> this power savin

Re: [PATCH] misc: rtsx: do not setting OC_POWER_DOWN reg in rtsx_pci_init_ocp()

2020-09-13 Thread Chris Clayton
s://bugzilla.kernel.org/show_bug.cgi?id=204003 Signed-off-by: Chris Clayton bede03a579b3 introduced a bug which leaves the rts5229 PCI Express card reader on the Intel NUC6CAYH box. My main point, however, is that the patch is also needed in the 5.4 (longterm) and 5.8 (stable) series kernel

Re: PATCH: rtsx_pci driver - don't disable the rts5229 card reader on Intel NUC boxes

2020-08-22 Thread Chris Clayton
Hi Ricky. On 05/08/2020 13:48, Chris Clayton wrote: > Hi Ricky >> >> Ah, OK. I'll prepare the patch and send it to you once I've tested it. >> > > Please see the patch included below. As you suggested, it removes the code > that does the OC power dow

Re: PATCH: rtsx_pci driver - don't disable the rts5229 card reader on Intel NUC boxes

2020-08-05 Thread Chris Clayton
Hi Ricky On 05/08/2020 06:51, Chris Clayton wrote: > Thanks, Ricky. > > On 05/08/2020 03:35, 吳昊澄 Ricky wrote: >> >> >>> -Original Message- >>> From: Chris Clayton [mailto:chris2...@googlemail.com] >>> Sent: Tuesday, August 04, 2020 7:52

Re: PATCH: rtsx_pci driver - don't disable the rts5229 card reader on Intel NUC boxes

2020-08-04 Thread Chris Clayton
Thanks, Ricky. On 05/08/2020 03:35, 吳昊澄 Ricky wrote: > > >> -Original Message----- >> From: Chris Clayton [mailto:chris2...@googlemail.com] >> Sent: Tuesday, August 04, 2020 7:52 PM >> To: 吳昊澄 Ricky; gre...@linuxfoundation.org >> Cc: LKML; rdun...@infra

Re: PATCH: rtsx_pci driver - don't disable the rts5229 card reader on Intel NUC boxes

2020-08-04 Thread Chris Clayton
On 04/08/2020 11:46, 吳昊澄 Ricky wrote: >> -Original Message- >> From: Chris Clayton [mailto:chris2...@googlemail.com] >> Sent: Tuesday, August 04, 2020 4:51 PM >> To: 吳昊澄 Ricky; gre...@linuxfoundation.org >> Cc: LKML; rdun...@infradead.org; philqua...@gmail

Re: PATCH: rtsx_pci driver - don't disable the rts5229 card reader on Intel NUC boxes

2020-08-04 Thread Chris Clayton
On 04/08/2020 09:08, 吳昊澄 Ricky wrote: >> -Original Message- >> From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org] >> Sent: Tuesday, August 04, 2020 3:49 PM >> To: 吳昊澄 Ricky >> Cc: Chris Clayton; LKML; rdun...@infradead.org; philqua.

Re: PATCH: rtsx_pci driver - don't disable the rts5229 card reader on Intel NUC boxes

2020-08-02 Thread Chris Clayton
e you signed off the patch that caused the regression, I believe it is your bug. Thanks. Chris > >> -Original Message- >> From: Chris Clayton [mailto:chris2...@googlemail.com] >> Sent: Monday, August 03, 2020 3:59 AM >> To: LKML; 吳昊澄 Ricky; gre...@linuxfoundatio

Re: PATCH: rtsx_pci driver - don't disable the rts5229 card reader on Intel NUC boxes

2020-08-02 Thread Chris Clayton
Sorry, I should have said that the patch is against 5.7.12. It applies to upstream, but with offsets. On 02/08/2020 20:48, Chris Clayton wrote: > bede03a579b3 introduced a bug which leaves the rts5229 PCI Express card > reader on my Intel NUC6CAYH box. > > The bug is in drivers/mis

PATCH: rtsx_pci driver - don't disable the rts5229 card reader on Intel NUC boxes

2020-08-02 Thread Chris Clayton
g/show_bug.cgi?id=204003 Signed-off-by: Chris Clayton bede03a579b3 introduced a bug which leaves the rts5229 PCI Express card reader on my Intel NUC6CAYH box. The bug is in drivers/misc/cardreader/rtsx_pcr.c. A call to rtsx_pci_init_ocp() was added to rtsx_pci_init_hw(). At the call poi

Re: Linux 5.3.6

2019-10-13 Thread Chris Clayton
On 12/10/2019 21:55, Gabriel C wrote: > Am Sa., 12. Okt. 2019 um 21:16 Uhr schrieb Chris Clayton > : >> >> >>> I'm announcing the release of the 5.3.6 kernel. >> >> >> 5.3.6 build fails here with: >> >> arch/x86/entry/vdso/vdso64.so

Re: Linux 5.3.6

2019-10-12 Thread Chris Clayton
1 make[3]: *** Deleting file 'arch/x86/entry/vdso/vdso64.so.dbg' make[2]: *** [scripts/Makefile.build:497: arch/x86/entry/vdso] Error 2 make[1]: *** [scripts/Makefile.build:497: arch/x86/entry] Error 2 make[1]: *** Waiting for unfinished jobs.... Chris Clayton

Re: [PATCH] timekeeping/vsyscall: Prevent math overflow in BOOTTIME update

2019-08-22 Thread Chris Clayton
presentation avoids a 64bit division in the > update code. > I've tested resume from both suspend and hibernate and this patch fixes the problem I reported. Tested-by: Chris Clayton > Fixes: 44f57d788e7d ("timekeeping: Provide a generic update_vsyscall() > implementation")

Re: PROBLEM: 5.3.0-rc* causes iwlwifi failure

2019-08-22 Thread Chris Clayton
Thanks, Stuart. On 18/08/2019 11:55, Stuart Little wrote: > On Sun, Aug 18, 2019 at 09:17:59AM +0100, Chris Clayton wrote: >> >> >> On 17/08/2019 22:44, Stuart Little wrote: >>> After some private coaching from Serge Belyshev on git-revert I can confirm >>&

Regression in 5.3-rc1 and later

2019-08-21 Thread Chris Clayton
Hi everyone, Firstly, apologies to anyone on the long cc list that turns out not to be particularly interested in the following, but you were all marked as cc'd in the commit message below. I've found a problem that isn't present in 5.2 series or 4.19 series kernels, and seems to have arrived i

Re: iwlwifi: microcode SW error detected

2019-08-20 Thread Chris Clayton
On 18/08/2019 09:21, Chris Clayton wrote: > > > On 17/08/2019 08:19, Chris Clayton wrote: >> Hi. >> >> I just found the following error in the output from dmesg. >> >> [ 4023.460058] iwlwifi :02:00.0: Microcode SW error detected. Restarting >&g

linux-5.3.0-rc5: new build warning

2019-08-18 Thread Chris Clayton
Hi, I've just built 5.3.0-rc5 and a warning that I do not recall having seen before was emitted: ... HOSTCC scripts/extract-cert HOSTCC /mnt/kernel/linux/tools/objtool/fixdep.o HOSTLD arch/x86/tools/relocs HOSTLD /mnt/kernel/linux/tools/objtool/fixdep-in.o LINK /mnt/kernel/li

Re: iwlwifi: microcode SW error detected

2019-08-18 Thread Chris Clayton
On 17/08/2019 08:19, Chris Clayton wrote: > Hi. > > I just found the following error in the output from dmesg. > > [ 4023.460058] iwlwifi :02:00.0: Microcode SW error detected. Restarting > 0x0. Since reporting, I've found that this problem is being explored in

Re: PROBLEM: 5.3.0-rc* causes iwlwifi failure

2019-08-18 Thread Chris Clayton
On 17/08/2019 22:44, Stuart Little wrote: > After some private coaching from Serge Belyshev on git-revert I can confirm > that reverting that commit atop the current tree resolves the issue (the wifi > card scans for and finds networks just fine, no dmesg errors reported, etc.). > I've repor

iwlwifi: microcode SW error detected

2019-08-17 Thread Chris Clayton
Hi. I just found the following error in the output from dmesg. [ 4023.460058] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x0. [ 4023.460178] iwlwifi :02:00.0: Start IWL Error Log Dump: [ 4023.460179] iwlwifi :02:00.0: Status: 0x0080, count: 6 [ 4023.460180] iwlwifi

Re: [PATCH v2] x86/boot: save fields explicitly, zero out everything else

2019-08-10 Thread Chris Clayton
ware, email, browsing, listening to music, watching video) without problem. Tested-by: Chris Clayton > Suggested-by: Thomas Gleixner > Suggested-by: H. Peter Anvin > Signed-off-by: John Hubbard > --- > arch/x86/include/asm/bootparam_utils.h | 62 +++--- &g

Re: Warnings whilst building 5.2.0+

2019-08-06 Thread Chris Clayton
On 09/07/2019 12:39, Chris Clayton wrote: > > > On 09/07/2019 11:37, Enrico Weigelt, metux IT consult wrote: >> On 09.07.19 08:06, Chris Clayton wrote: >> >> Hi, >> >>> I've pulled Linus' tree this morning and, after running 'make ol

Re: Warnings whilst building 5.2.0+

2019-07-09 Thread Chris Clayton
On 09/07/2019 11:37, Enrico Weigelt, metux IT consult wrote: > On 09.07.19 08:06, Chris Clayton wrote: > > Hi, > >> I've pulled Linus' tree this morning and, after running 'make oldconfig', >> tried a build. During that build I got the >> fol

Warnings whilst building 5.2.0+

2019-07-08 Thread Chris Clayton
Hi, I've pulled Linus' tree this morning and, after running 'make oldconfig', tried a build. During that build I got the following warnings, which look to me like they should be fixed. 'git describe' shows v5.2-915-g5ad18b2e60b7 and my compiler is the 20190706 snapshot of gcc 9. In file include

Re: R8169: Network lockups in 4.18.{8,9,10} (and 4.19 dev)

2018-10-11 Thread Chris Clayton
On 11/10/2018 13:23, Maciej S. Szmigiero wrote: > On 11.10.2018 10:24, Chris Clayton wrote: >> On 11/10/2018 01:12, Maciej S. Szmigiero wrote: >>> On 11.10.2018 00:49, Chris Clayton wrote: >>>>> Now, knowing the "right" value you can experiment wit

Re: R8169: Network lockups in 4.18.{8,9,10} (and 4.19 dev)

2018-10-11 Thread Chris Clayton
On 11/10/2018 01:12, Maciej S. Szmigiero wrote: > On 11.10.2018 00:49, Chris Clayton wrote: >>> Now, knowing the "right" value you can experiment with what rtl_init_rxcfg() >>> writes (under the "default:" label for your NIC model). >>&g

Re: R8169: Network lockups in 4.18.{8,9,10} (and 4.19 dev)

2018-10-10 Thread Chris Clayton
OK, right kernel/module used this time. Please see findings below. On 10/10/2018 01:24, Maciej S. Szmigiero wrote: > On 09.10.2018 22:36, Heiner Kallweit wrote: >> On 09.10.2018 16:40, Chris Clayton wrote: >>> Thanks to Maciej and Heiner for their replies. >>> >&g

Re: R8169: Network lockups in 4.18.{8,9,10} (and 4.19 dev)

2018-10-10 Thread Chris Clayton
Too late at night to be doing this stuff. Clicked send instead of saving a draft. Sorry, please ignore. On 10/10/2018 23:30, Chris Clayton wrote: > OK, right kernel/module used this time. Please see findings below. > > On 10/10/2018 01:24, Maciej S. Szmigiero wrote: >> On 0

Re: R8169: Network lockups in 4.18.{8,9,10} (and 4.19 dev)

2018-10-10 Thread Chris Clayton
OK, right kernel/module used this time. Please see findings below. On 10/10/2018 01:24, Maciej S. Szmigiero wrote: > On 09.10.2018 22:36, Heiner Kallweit wrote: >> On 09.10.2018 16:40, Chris Clayton wrote: >>> Thanks to Maciej and Heiner for their replies. >>> >&g

Re: R8169: Network lockups in 4.18.{8,9,10} (and 4.19 dev)

2018-10-10 Thread Chris Clayton
later. Chris On 10/10/2018 09:09, Chris Clayton wrote: > > > On 10/10/2018 01:24, Maciej S. Szmigiero wrote: >> On 09.10.2018 22:36, Heiner Kallweit wrote: >>> On 09.10.2018 16:40, Chris Clayton wrote: >>>> Thanks to Maciej and Heiner for their replies

Re: R8169: Network lockups in 4.18.{8,9,10} (and 4.19 dev)

2018-10-10 Thread Chris Clayton
On 10/10/2018 01:24, Maciej S. Szmigiero wrote: > On 09.10.2018 22:36, Heiner Kallweit wrote: >> On 09.10.2018 16:40, Chris Clayton wrote: >>> Thanks to Maciej and Heiner for their replies. >>> >>> On 09/10/2018 13:32, Maciej S. Szmigiero wrote: >>&

Re: R8169: Network lockups in 4.18.{8,9,10} (and 4.19 dev)

2018-10-09 Thread Chris Clayton
On 09/10/2018 22:39, Heiner Kallweit wrote: > On 09.10.2018 16:40, Chris Clayton wrote: >> Thanks to Maciej and Heiner for their replies. >> >> On 09/10/2018 13:32, Maciej S. Szmigiero wrote: >>> On 07.10.2018 21:36, Chris Clayton wrote: >>>> Hi

Re: R8169: Network lockups in 4.18.{8,9,10} (and 4.19 dev)

2018-10-09 Thread Chris Clayton
Thanks to Maciej and Heiner for their replies. On 09/10/2018 13:32, Maciej S. Szmigiero wrote: > On 07.10.2018 21:36, Chris Clayton wrote: >> Hi again, >> >> I didn't think there was anything in 4.19-rc7 to fix this regression, but >> tried it anyway. I can c

Re: R8169: Network lockups in 4.18.{8,9,10} (and 4.19 dev)

2018-10-07 Thread Chris Clayton
s the failure is almost immediate - e.g. my home page doesn't get displayed in the browser. Pinging one of my ISPs name servers doesn't fail quite so quickly but the reported time increases from 14-15ms to more than 1000ms. Chris On 04/10/2018 09:41, Chris Clayton wrote: > Hi Heine

Re: R8169: Network lockups in 4.18.{8,9,10} (and 4.19 dev)

2018-10-04 Thread Chris Clayton
Hi Heiner, Here's the reply to your questions. Sorry for the delay. On 28/09/2018 23:13, Heiner Kallweit wrote: > On 29.09.2018 00:00, Chris Clayton wrote: >> Thanks Maciej. >> >> On 28/09/2018 16:54, Maciej S. Szmigiero wrote: >>> Hi, >>> >&g

Re: R8169: Network lockups in 4.18.{8,9,10} (and 4.19 dev)

2018-09-29 Thread Chris Clayton
Sorry, sent by accident. Note to self - don't attempt email until after second cup of coffee. On 29/09/2018 08:25, Chris Clayton wrote: > > > On 28/09/2018 23:13, Heiner Kallweit wrote: >> On 29.09.2018 00:00, Chris Clayton wrote: >>> Thanks Maciej. >>

Re: R8169: Network lockups in 4.18.{8,9,10} (and 4.19 dev)

2018-09-29 Thread Chris Clayton
On 28/09/2018 23:13, Heiner Kallweit wrote: > On 29.09.2018 00:00, Chris Clayton wrote: >> Thanks Maciej. >> >> On 28/09/2018 16:54, Maciej S. Szmigiero wrote: >>> Hi, >>> >>>> Hi, >>>> >>>> I upgraded my kernel to 4.1

Re: R8169: Network lockups in 4.18.{8,9,10} (and 4.19 dev)

2018-09-28 Thread Chris Clayton
Thanks Maciej. On 28/09/2018 16:54, Maciej S. Szmigiero wrote: > Hi, > >> Hi, >> >> I upgraded my kernel to 4.18.10 recently and have since been experiencing >> network problems after resuming from a >> suspend to RAM or disk. I previously had 4.18.6 and that was OK. >> >> The pattern of the pro

Re: [PATCH V2] mfd: rtsx: release IRQ during shutdown

2018-01-03 Thread Chris Clayton
t it registered during probe. This is causing > the ACPI layer to complain that the shared IRQ is in use while freeing > IRQ. > > This code releases the IRQ to prevent resource leak and eliminate the > warning. > > Link: https://bugzilla.kernel.org/show_bug.cgi?id=198

Re: Oops on 4.15-rc[123] on shutdown/reboot

2017-12-11 Thread Chris Clayton
On 11/12/17 17:17, Bjorn Helgaas wrote: > [+cc linux-pci] > > On Mon, Dec 11, 2017 at 11:29:50AM -0500, Sinan Kaya wrote: >> Hi Chris, >> >>> >>> I'm more than happy to provide additional diagnostics and test proposed >>> fixes. As a starter for ten, I've attached the >>> output from 'lspci -v'.

Re: Oops on 4.15-rc[123] on shutdown/reboot

2017-12-11 Thread Chris Clayton
On 11/12/17 17:24, Sinan Kaya wrote: > On 12/11/2017 12:06 PM, Chris Clayton wrote: >> Here's the output of dmesg for 4.15.0-rc3. I'll open a bugzilla later and >> add this and the lspci output that I sent with >> my original repoart. > > This was helpful

Re: Oops on 4.15-rc[123] on shutdown/reboot

2017-12-11 Thread Chris Clayton
On 11/12/17 16:29, Sinan Kaya wrote: > Hi Chris, > >> >> I'm more than happy to provide additional diagnostics and test proposed >> fixes. As a starter for ten, I've attached the >> output from 'lspci -v'. If, however, you need to see the backtrace, I'll >> need some advice on how to capture t

Oops on 4.15-rc[123] on shutdown/reboot

2017-12-11 Thread Chris Clayton
I've been getting an oops when shutting down my laptop (with /sbin/halt) or rebooting it (/sbin/reboot or /usr/sbin/kexec). Unfortunately, I can't provide the backtrace because it is on the screen for only a moment before the system shuts down/reboots. I have however, bisected it and the outcome

"PM / QoS: Fix device resume latency PM QoS" breaks sound

2017-10-28 Thread Chris Clayton
Hi, I pulled the latestchanges from Linus' tree this evening and have found that with the new kernel, sound is not working on my laptop. More precisely, the built-in speakers don't produce any sound. Sound does work when I use ear-plugs in the headphone socket. It also works via a bluetooth spea

Re: [PATCH 4.12 004/106] scsi: sg: fix SG_DXFER_FROM_DEV transfers

2017-08-10 Thread Chris Clayton
gth bigger than 0. This fixes a regression introduced by commit > 28676d869bbb ("scsi: sg: check for valid direction before starting the > request") > > Signed-off-by: Johannes Thumshirn > Fixes: 28676d869bbb ("scsi: sg: check for valid direction before starting the

Re: [PATCH v2] scsi: sg: fix SG_DXFER_FROM_DEV transfers

2017-07-07 Thread Chris Clayton
si: sg: check for valid direction before starting the request") > I've tested this new patch and the Nero applications can still find the optical drives on my laptop. Tested-by: Chris Clayton > Signed-off-by: Johannes Thumshirn > Fixes: 28676d869bbb ("scsi: sg: chec

4.7.0-rc7+: Oops during boot with USB pen drive inserted

2016-07-21 Thread Chris Clayton
Hi, With Linus' latest and greatest, I get an opps when I boot my laptop with a pen drive inserted in any USB port. The oops message is: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2) The oops seems to be 100% repeatable. If a USB pen drive is not inserted, the

Re: 4.5 Regression - mouse not working after resume from suspend

2016-02-18 Thread Chris Clayton
oblem. On 15/02/16 23:40, Chris Clayton wrote: > Hi, > > Is there anything else I can do to help diagnose this regression. > > To summarise my BT mouse does not work after resuming from suspend to disk or > ram. IT works perfectly in earlier 4.4, > 4.3 and 4.2 kernels. I bisect

Re: 4.5 Regression - mouse not working after resume from suspend

2016-02-06 Thread Chris Clayton
On 06/02/16 11:38, Chris Clayton wrote: > > > On 06/02/16 08:37, Chris Clayton wrote: >> There seems to be a regression in resuming my laptop from a suspend to RAM >> or disk. The symptom is that my bluetooth >> mouse doesn't work after the resume. The

Re: 4.5 Regression - mouse not working after resume from suspend

2016-02-06 Thread Chris Clayton
On 06/02/16 08:37, Chris Clayton wrote: > There seems to be a regression in resuming my laptop from a suspend to RAM or > disk. The symptom is that my bluetooth > mouse doesn't work after the resume. The kernel is built after a pull of > Linus' tree this morning

4.5 Regression - mouse not working after resume from suspend

2016-02-06 Thread Chris Clayton
There seems to be a regression in resuming my laptop from a suspend to RAM or disk. The symptom is that my bluetooth mouse doesn't work after the resume. The kernel is built after a pull of Linus' tree this morning (v4.5-rc2-340-g5af9c2e). Attached is the output from dmesg showing the boot, susp

Re: EXT4: new warnings from 4.3.0-rc2

2015-09-21 Thread Chris Clayton
On 09/21/15 15:55, Chris Clayton wrote: > Thanks Ortwin. > > On 09/21/15 14:27, Ortwin Glück wrote: >>> [2.481399] EXT4-fs (sda2): couldn't mount as ext3 due to feature >>> incompatibilities >>> [2.482426] EXT4-fs (sda2): couldn't mount

Re: EXT4: new warnings from 4.3.0-rc2

2015-09-21 Thread Chris Clayton
Thanks Ortwin. On 09/21/15 14:27, Ortwin Glück wrote: >> [2.481399] EXT4-fs (sda2): couldn't mount as ext3 due to feature >> incompatibilities >> [2.482426] EXT4-fs (sda2): couldn't mount as ext2 due to feature >> incompatibilities > > As the kernel doesn't know which FS your root is,

EXT4: new warnings from 4.3.0-rc2

2015-09-21 Thread Chris Clayton
Hi, I've just built and booted 4.3.0-rc2 and I'm seeing the following new messages on the console during boot up: [2.481399] EXT4-fs (sda2): couldn't mount as ext3 due to feature incompatibilities [2.482426] EXT4-fs (sda2): couldn't mount as ext2 due to feature incompatibilities They

Re: [PATCH] iommu: prompt for IOMMU_IO_PGTABLE_LPAE on ARM archs only

2015-02-16 Thread Chris Clayton
On 02/16/15 16:32, Will Deacon wrote: > Hi Chris, > > On Sun, Feb 15, 2015 at 11:17:19AM +0000, Chris Clayton wrote: >> When running "make oldconfig" for an x86_64 kernel, I was prompted for a >> setting for IOMMU_IO_PGTABLE_LPAE. From the prompt and the help text

[PATCH] iommu: prompt for IOMMU_IO_PGTABLE_LPAE on ARM archs only

2015-02-15 Thread Chris Clayton
ng a cross-compiled x86_64 kernel in an x86 user space. The resultant kernel boots fine and I am running it now. Fixes: e1d3c0fd701df831169b116cd5c5d6203ac07f70 Cc: will.dea...@arm.com Signed-off-by: Chris Clayton --- linux/drivers/iommu/Kconfig.orig2015-02-15 09:44:01.235927248 + +++ lin

Re: BUG in 3.19.0-rc3+

2015-01-11 Thread Chris Clayton
t;>b: eb 9a jmp0xffa7 >>>d: 66 data16 >>>e: 0f .byte 0xf >>>f: 1f (bad) >>> 10: 84 00 test %al,(%rax) >>> 12: 00 00

Re: BUG in 3.19.0-rc3+

2015-01-11 Thread Chris Clayton
On 01/11/15 09:52, Oded Gabbay wrote: > > > On 01/11/2015 11:37 AM, Konstantin Khlebnikov wrote: >> On Sun, Jan 11, 2015 at 11:16 AM, Chris Clayton >> wrote: >>> Hi, >>> >>> I've done the bisect and the outcome is below, but, because I a

Re: BUG in 3.19.0-rc3+

2015-01-11 Thread Chris Clayton
Hi, I've done the bisect and the outcome is below, but, because I almost always forget to mention it, I'll say here that I am running a 32 bit user space on a 64 bit kernel. On 01/10/15 20:17, Chris Clayton wrote: > Hi, > > I'm getting a bug a BUG report from a

BUG in 3.19.0-rc3+

2015-01-10 Thread Chris Clayton
Hi, I'm getting a bug a BUG report from a kernel built from a pull (earlier today) of the current development kernel (running git describe gives v3.19-rc3-169-geb74926). So that I have useable wireless networking, I have also applied the latest seven iwlwifi patches from the wireless-drivers git

Re: [tip:x86/urgent] x86: Use $(OBJDUMP) instead of plain objdump

2014-12-01 Thread Chris Clayton
Hi, Is it planned to get this fix through in time for release of 3.18? It appears to have been in -next for a week. Chris On 11/23/14 20:24, tip-bot for Chris Clayton wrote: > Commit-ID: e2e68ae688b0a3766cd75aedf4ed4e39be402009 > Gitweb: http://git.kernel.o

[tip:x86/urgent] x86: Use $(OBJDUMP) instead of plain objdump

2014-11-24 Thread tip-bot for Chris Clayton
Commit-ID: e2e68ae688b0a3766cd75aedf4ed4e39be402009 Gitweb: http://git.kernel.org/tip/e2e68ae688b0a3766cd75aedf4ed4e39be402009 Author: Chris Clayton AuthorDate: Sat, 22 Nov 2014 09:51:10 + Committer: Thomas Gleixner CommitDate: Sun, 23 Nov 2014 21:21:53 +0100 x86: Use $(OBJDUMP

[PATCH]: cross-compiling x86_64 kernel on i386 user-space fails

2014-11-22 Thread Chris Clayton
there too. CC: Junjie Mao CC: Kees Cook CC: Thomas Gleixner CC: Ingo Molnar Signed-off-by: Chris Clayton --- --- linux/arch/x86/boot/compressed/Makefile~2014-11-22 08:56:50.359706324 + +++ linux/arch/x86/boot/compressed/Makefile 2014-11-22 09:04:06.615693435 + @@ -76,7 +76,7

Re: Networking problem with 3.11-rc6+

2013-09-03 Thread Chris Clayton
On 08/20/13 22:54, Francois Romieu wrote: Chris Clayton : [...] [0.207094] acpi PNP0A08:00: ACPI _OSC support notification failed, disabling PCIe ASPM [0.207155] acpi PNP0A08:00: Unable to request _OSC control (_OSC support mask: 0x08) [...] [5.311191] r8169 :07:00.0

Networking problem with 3.11-rc6+

2013-08-20 Thread Chris Clayton
Hello, I've just booted my laptop and found that networking was broken. Pings of other devices on my home network failed. A reboot has restored networking, but I thought I should report the problem anyway. I'll have no time tomorrow, but on Thursday I'll do a few boots to ascertain how repeat

Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner

2013-07-09 Thread Chris Clayton
Hello again, Bjorn. On 04/01/13 18:28, Bjorn Helgaas wrote: Hi Chris, The current Linux acpiphp driver doesn't do anything unless it finds devices with _EJ0 or _RMV methods, and your DSDT has neither. But I think that implementation is incorrect because I'm not convinced that those methods

Re: linux-3.9.0-rc1+: Output from "make kernelrelease"contains incorrect data

2013-04-03 Thread Chris Clayton
On 04/03/13 15:32, Michal Marek wrote: On 1.4.2013 11:28, Chris Clayton wrote: Ping! This is still happening with 3.9-rc5. [chris:~/kernel/linux]$ make bzImage ... Kernel: arch/x86/boot/bzImage is ready (#14) [chris:~/kernel/linux]$ make kernelrelease scripts/kconfig/conf --silentoldconfig

Re: linux-3.9.0-rc1+: Output from "make kernelrelease"contains incorrect data

2013-04-01 Thread Chris Clayton
x27;m assuming that the output from 'make kernelrelease' should be the string that represents the kernel release and only that string. Chris On 03/09/13 19:38, Chris Clayton wrote: In Linus' current tree, the first time the command "make kernelrelease" is run after building

Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner

2013-03-19 Thread Chris Clayton
4:20 PM, Bjorn Helgaas wrote: On Sat, Mar 9, 2013 at 2:20 AM, Chris Clayton wrote: On 03/08/13 22:57, Bjorn Helgaas wrote: Thanks. I opened this bug report: https://bugzilla.kernel.org/show_bug.cgi?id=54981 to keep track of your logs. Hi Chris, The current Linux acpiphp driver doesn'

linux-3.9.0-rc1+: Output from "make kernelrelease"contains incorrect data

2013-03-09 Thread Chris Clayton
In Linus' current tree, the first time the command "make kernelrelease" is run after building a kernel, the output contains some unwanted text. Subsequent uses of the command produce the expected output. This appears to be a regression - 3.8.2 does not have this problem. This is easily demonst

Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner

2013-03-09 Thread Chris Clayton
Hi Bjorn, On 03/08/13 22:57, Bjorn Helgaas wrote: [+cc Rafael, in case the _OSC thing rings a bell with him] On Fri, Mar 8, 2013 at 3:44 AM, Chris Clayton wrote: On 03/08/13 00:39, Bjorn Helgaas wrote: On Thu, Mar 7, 2013 at 1:21 PM, Chris Clayton wrote: On 03/07/13 17:30, Bjorn Helgaas

kernel 3.6.7: sysfs: cannot create duplicate filename warnings

2013-02-06 Thread Chris Clayton
Hi, I've been investigating problem with my Hauppauge WinTV HVR-1400 TV card (an expresscard) [1], and I've come across warnings produced when I unload and then reload the cx23885 driver. Attached is the output from dmesg that shows the card being detected (by the PCI express hotplug driver)

Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner

2013-01-31 Thread Chris Clayton
Hi Martin, On 01/28/13 21:02, Martin Mokrejs wrote: Hi Chris, Chris Clayton wrote: Hi Martin, On 01/28/13 12:12, Martin Mokrejs wrote: Chris Clayton wrote: [snip] [chris:~]$ cat /proc/cmdline root=/dev/sda5 pciehp_ports=native ro resume=/dev/sda6

Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner

2013-01-28 Thread Chris Clayton
Hi Martin, On 01/28/13 12:12, Martin Mokrejs wrote: Chris Clayton wrote: [snip] [chris:~]$ cat /proc/cmdline root=/dev/sda5 pciehp_ports=native ro resume=/dev/sda6 ^^ **typo** I've run the test again with pcie_ports=native and the directorie

Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner

2013-01-28 Thread Chris Clayton
[snip] [chris:~]$ cat /proc/cmdline root=/dev/sda5 pciehp_ports=native ro resume=/dev/sda6 ^^ **typo** I've run the test again with pcie_ports=native and the directories now get populated. Even better though, is that when I plug in the card, hotplug **w

Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner

2013-01-28 Thread Chris Clayton
[no one screamed, so linux-media ml dropped] Hi Martin, On 01/28/13 10:56, Martin Mokrejs wrote: Chris Clayton wrote: Hi Yijing, On 01/28/13 02:40, Yijing Wang wrote: Hi Chris, Sorry for the delay reply. It seems like my reply last night was missed. From the sysinfo you provide

Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner

2013-01-28 Thread Chris Clayton
opulate the directories without pci_slot? Thanks again. /sys/bus/pci_express/devices: total 0 /sys/bus/pci_express/drivers: total 0 drwxr-xr-x 2 root root 0 Jan 27 13:17 pciehp/ On 2013/1/28 6:53, Chris Clayton wrote: Thanks again, Martin. Firstly, maybe we should remove the linux-media list fro

Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner

2013-01-27 Thread Chris Clayton
Thanks again, Martin. Firstly, maybe we should remove the linux-media list from the copy list. I imagine this hotplug stuff is just noise to them. [snip] Do you have any other express card around to try if it works at all? Try that always after a cold boot. Not at the moment, but I ordered

Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner

2013-01-27 Thread Chris Clayton
On 01/27/13 14:26, Martin Mokrejs wrote: Chris Clayton wrote: On 01/27/13 12:18, Yijing Wang wrote: 于 2013-01-27 19:19, Chris Clayton 写道: Hi Yijing On 01/27/13 02:45, Yijing Wang wrote: 于 2013-01-27 4:54, Chris Clayton 写道: Hi Martin, On 01/24/13 19:21, Martin Mokrejs wrote: Hi Chris

Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner

2013-01-27 Thread Chris Clayton
On 01/27/13 12:18, Yijing Wang wrote: 于 2013-01-27 19:19, Chris Clayton 写道: Hi Yijing On 01/27/13 02:45, Yijing Wang wrote: 于 2013-01-27 4:54, Chris Clayton 写道: Hi Martin, On 01/24/13 19:21, Martin Mokrejs wrote: Hi Chris, try to include in kernel only acpiphp and omit pciehp. Don&#

Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner

2013-01-27 Thread Chris Clayton
Hi Martin, On 01/26/13 21:14, Martin Mokrejs wrote: Hi Chris, Chris Clayton wrote: Hi Martin, On 01/24/13 19:21, Martin Mokrejs wrote: Hi Chris, try to include in kernel only acpiphp and omit pciehp. Don't use modules but include them statically. And try, in addition, check wh

Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner

2013-01-26 Thread Chris Clayton
with the card inserted (or by writing 1 to/sys/bus/pci/rescan). There seem to be a few reports on this in the kernel bugzilla, so I'll look through them and see what's being done. Thanks again. Chris Martin Chris Clayton wrote: Hi, I've today taken delivery of a WinTV-HVR-140

Re: [RFT PATCH v2 4/5] mm: provide more accurate estimation of pages occupied by memmap

2012-12-04 Thread Chris Clayton
On 12/03/12 23:17, Andrew Morton wrote: On Sun, 02 Dec 2012 19:55:09 + Chris Clayton wrote: On 11/29/12 10:52, Chris Clayton wrote: On 11/28/12 23:52, Andrew Morton wrote: On Wed, 21 Nov 2012 23:09:46 +0800 Jiang Liu wrote: Subject: Re: [RFT PATCH v2 4/5] mm: provide more

Re: [RFT PATCH v2 4/5] mm: provide more accurate estimation of pages occupied by memmap

2012-12-02 Thread Chris Clayton
On 12/02/12 19:55, Chris Clayton wrote: On 11/29/12 10:52, Chris Clayton wrote: On 11/28/12 23:52, Andrew Morton wrote: On Wed, 21 Nov 2012 23:09:46 +0800 Jiang Liu wrote: Subject: Re: [RFT PATCH v2 4/5] mm: provide more accurate estimation of pages occupied by memmap How are people

Re: [RFT PATCH v2 4/5] mm: provide more accurate estimation of pages occupied by memmap

2012-12-02 Thread Chris Clayton
On 11/29/12 10:52, Chris Clayton wrote: On 11/28/12 23:52, Andrew Morton wrote: On Wed, 21 Nov 2012 23:09:46 +0800 Jiang Liu wrote: Subject: Re: [RFT PATCH v2 4/5] mm: provide more accurate estimation of pages occupied by memmap How are people to test this? "does it boot"?

Re: [RFT PATCH v2 4/5] mm: provide more accurate estimation of pages occupied by memmap

2012-11-29 Thread Chris Clayton
On 11/28/12 23:52, Andrew Morton wrote: On Wed, 21 Nov 2012 23:09:46 +0800 Jiang Liu wrote: Subject: Re: [RFT PATCH v2 4/5] mm: provide more accurate estimation of pages occupied by memmap How are people to test this? "does it boot"? I've been running kernels with Gerry's 5 patches appl

Re: [RFT PATCH v1 0/5] fix up inaccurate zone->present_pages

2012-11-26 Thread Chris Clayton
On 11/22/12 09:23, Chris Clayton wrote: This patchset has only been tested on x86_64 with nobootmem.c. So need help to test this patchset on machines: 1) use bootmem.c 2) have highmem This patchset applies to "f4a75d2e Linux 3.7-rc6" from git://git.kernel.org/pub/scm/linux/kernel/gi

Re: [RFT PATCH v1 0/5] fix up inaccurate zone->present_pages

2012-11-22 Thread Chris Clayton
This patchset has only been tested on x86_64 with nobootmem.c. So need help to test this patchset on machines: 1) use bootmem.c 2) have highmem This patchset applies to "f4a75d2e Linux 3.7-rc6" from git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git I've applied the five patches

Re: [RFT PATCH v1 0/5] fix up inaccurate zone->present_pages

2012-11-18 Thread Chris Clayton
Hi Gerry. On 11/18/12 16:07, Jiang Liu wrote: The commit 7f1290f2f2a4 ("mm: fix-up zone present pages") tries to resolve an issue caused by inaccurate zone->present_pages, but that fix is incomplete and causes regresions with HIGHMEM. And it has been reverted by commit 5576646 revert "mm: fix-up

Re: [PATCH] mm: fix a regression with HIGHMEM introduced by changeset 7f1290f2f2a4d

2012-11-15 Thread Chris Clayton
ither freezing or rebooting) after a suspend to disk. Tested-by: Chris Clayton From: Andrew Morton Subject: revert "mm: fix-up zone present pages" Revert commit 7f1290f2f2a4d2c3f1b7ce8e87256e052ca23125 Author: Jianguo Wu AuthorDate: Mon Oct 8 16:33:06 2012 -0700 Commit:

Re: [PATCH] mm: fix a regression with HIGHMEM introduced by changeset 7f1290f2f2a4d

2012-11-06 Thread Chris Clayton
es for highmem zone because bootmem allocator never allocates pages from them. So fix the regression by skipping highmem in function reset_zone_present_pages() and fixup_zone_present_pages(). Signed-off-by: Jiang Liu Signed-off-by: Jianguo Wu Reported-by: Maciej Rutecki Tested-by: Maciej Rutecki Cc

linux-3.7.0-rc3+: Warning found in log files

2012-11-05 Thread Chris Clayton
Hi, Whilst browsing the log file on my laptop (looking for diagnostics for a problem I have resuming from a suspend to disc), I spotted the warning below. I see that vlc is mentioned. I did have a problem yesterday when, through vlc's UPNP functionality, I was unable to play a video stored o

  1   2   >