Re: [BUG]: WARNING: CPU: 5 PID: 0 at net/sched/sch_generic.c:442 dev_watchdog+0x24d/0x260

On 4/13/21 11:07 PM, Heiner Kallweit wrote: On 13.04.2021 22:59, Xose Vazquez Perez wrote: A non-recurring bug, on 5.11.12-300.fc34.x86_64 (Fedora kernel). Thanks. 0c:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet

[BUG]: WARNING: CPU: 5 PID: 0 at net/sched/sch_generic.c:442 dev_watchdog+0x24d/0x260

A non-recurring bug, on 5.11.12-300.fc34.x86_64 (Fedora kernel). Thanks. 0c:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) [2.968280] libphy: r8169: probed [2.968844] r8169 :0c:00.0

Re: [dm-devel] [PATCH v4 0/2] Historical Service Time Path Selector

On 5/11/20 6:39 PM, Gabriel Krisman Bertazi wrote: This fourth version of HST applies the suggestion from Mikulas Patocka to do the ktime_get_ns inside the mpath map_bio instead of generic device-mapper code. This means that struct dm_mpath_io gained another 64bit field. For the request-based

Re: [PATCH] x86/mm: Prevent bogus warnings with "noexec=off"

e the warning depend on NX set in __supported_pte_mask. > > Reported-by: Xose Vazquez Perez And Tested-by: Xose Vazquez Perez > Signed-off-by: Thomas Gleixner > --- > arch/x86/mm/dump_pagetables.c |3 ++- > arch/x86/mm/ioremap.c |2 +- > 2 files changed, 3

Re: bug disabling NX (noexec=off)

On 4/14/19 11:59 AM, Thomas Gleixner wrote: > On Sat, 13 Apr 2019, Xose Vazquez Perez wrote: >> [0.00] NX (Execute Disable) protection: disabled by kernel command >> line option >> [0.00] [ cut here ] >> [0.00] attempte

bug disabling NX (noexec=off)

Hi, Intel Core i3-2120 + kernel-5.0.7 x86_64 from Fedora: [0.00] microcode: microcode updated early to revision 0x2e, date = 2018-04-10 [0.00] Linux version 5.0.7-300.fc30.x86_64 (mockbu...@bkernel04.phx2.fedoraproject.org) (gcc version 9.0.1 20190312 (Red Hat 9.0.1-0.10)

git: cover letter and automatic Cc: [was Re: [PATCH 23/45] sched: add do_sched_yield() helper; remove in-kernel call to sched_yield()]

Linus Torvalds wrote: > On Thu, Mar 22, 2018 at 10:29 AM, Peter Zijlstra wrote: >> >> But why !? Either Cc me on more of the series such that the whole makes >> sense, or better yet, write a proper Changelog. > > This is a common issue. We should encourage people to always

git: cover letter and automatic Cc: [was Re: [PATCH 23/45] sched: add do_sched_yield() helper; remove in-kernel call to sched_yield()]

Linus Torvalds wrote: > On Thu, Mar 22, 2018 at 10:29 AM, Peter Zijlstra wrote: >> >> But why !? Either Cc me on more of the series such that the whole makes >> sense, or better yet, write a proper Changelog. > > This is a common issue. We should encourage people to always send at > least the

[PATCH] trivial: remove exec bit from random files

These are not scripts. Cc: Jiri Kosina <triv...@kernel.org> Cc: linux-kernel@vger.kernel.org Signed-off-by: Xose Vazquez Perez <xose.vazq...@gmail.com> --- arch/nios2/boot/dts/10m50_devboard.dts | 0 arch/nios2/configs/10m50_defconfig

[PATCH] trivial: remove exec bit from random files

These are not scripts. Cc: Jiri Kosina Cc: linux-kernel@vger.kernel.org Signed-off-by: Xose Vazquez Perez --- arch/nios2/boot/dts/10m50_devboard.dts | 0 arch/nios2/configs/10m50_defconfig | 0 arch/sh/boot/dts/j2_mimas_v2.dts

checkpatch.pl: how to run --fix-inplace for just only one warning/error

Hi, Maybe it's tricky, but could it be possible? For example for: ERROR: space prohibited after that open parenthesis '(' Any hint? Thank you.

checkpatch.pl: how to run --fix-inplace for just only one warning/error

Hi, Maybe it's tricky, but could it be possible? For example for: ERROR: space prohibited after that open parenthesis '(' Any hint? Thank you.

Re: [PATCH 2/3] staging/rtl8192e: use s8 instead of char

Arnd Bergmann wrote: > rtlwifi, but I found the older r8712u device to work fine with > the staging/rtl8712 driver. A replacement for "staging/rtl8712", with MAC80211 support, is available at: https://github.com/chunkeey/rtl8192su Also a fullmac/cfg80211 driver(r92su) is

Re: [PATCH 2/3] staging/rtl8192e: use s8 instead of char

Arnd Bergmann wrote: > rtlwifi, but I found the older r8712u device to work fine with > the staging/rtl8712 driver. A replacement for "staging/rtl8712", with MAC80211 support, is available at: https://github.com/chunkeey/rtl8192su Also a fullmac/cfg80211 driver(r92su) is available at the same

Re: [PATCH] sparc64: Swap registers for fault code and address in mna trap

Hisashi Kanda wrote: > In fact, BUG() in do_sparc64_fault occurred in modified version > of linux-2.6.25.8 on SPARC64VIIIfx. I'm misunderstanding that > the same problem remains in the latest. Fujitsu K computer, with SPARC64 VIIIfx, runs a heavily modified 2.6.25.8 kernel. And maybe also

Re: [PATCH] sparc64: Swap registers for fault code and address in mna trap

Hisashi Kanda wrote: > In fact, BUG() in do_sparc64_fault occurred in modified version > of linux-2.6.25.8 on SPARC64VIIIfx. I'm misunderstanding that > the same problem remains in the latest. Fujitsu K computer, with SPARC64 VIIIfx, runs a heavily modified 2.6.25.8 kernel. And maybe also

Re: [PATCH 1/3] MAINTAINERS: Remove asterisk from EFI directory names

On 05/13/2016 05:23 PM, Joe Perches wrote: > The meaning of * is all the files in a particular > directory but not any subdirectories. Then "*" is only relevant for these entries: drivers/char/* drivers/misc/* drivers/net/wireless/ath/* fs/* drivers/cpuidle/* < This is a bug, it should be

Re: [PATCH 1/3] MAINTAINERS: Remove asterisk from EFI directory names

On 05/13/2016 05:23 PM, Joe Perches wrote: > The meaning of * is all the files in a particular > directory but not any subdirectories. Then "*" is only relevant for these entries: drivers/char/* drivers/misc/* drivers/net/wireless/ath/* fs/* drivers/cpuidle/* < This is a bug, it should be

Re: [PATCH 1/3] MAINTAINERS: Remove asterisk from EFI directory names

Matt Fleming wrote: > Mark reported that having asterisks on the end of directory names > confuses get_maintainer.pl when it encounters subdirectories, and that If this's a get_maintainer.pl bug, it should also happen in: F: arch/arm64/boot/dts/qcom/* F: arch/mips/bcm47xx/* F:

Re: [PATCH 1/3] MAINTAINERS: Remove asterisk from EFI directory names

Matt Fleming wrote: > Mark reported that having asterisks on the end of directory names > confuses get_maintainer.pl when it encounters subdirectories, and that If this's a get_maintainer.pl bug, it should also happen in: F: arch/arm64/boot/dts/qcom/* F: arch/mips/bcm47xx/* F:

Re: [PATCH v2] carl9170: Clarify kconfig text

Christian Lamparter wrote: > Sure, but this could be a different patch then. I think Intel devices > (iwlwifi, iwlegacy and ipw2x00) have a similar text about "download > firmware from this device from our homepage here" too. So if we want, > we can remove them altogether? linux-firmware.git

Re: [PATCH v2] carl9170: Clarify kconfig text

Christian Lamparter wrote: > Sure, but this could be a different patch then. I think Intel devices > (iwlwifi, iwlegacy and ipw2x00) have a similar text about "download > firmware from this device from our homepage here" too. So if we want, > we can remove them altogether? linux-firmware.git

Re: [PATCH kernel.org] change 3.12 EOL

Jiri Slaby wrote: > diff --git a/content/releases.rst b/content/releases.rst > index 28ebf47834..14494a64cd 100644 > --- a/content/releases.rst > +++ b/content/releases.rst > @@ -44,7 +44,7 @@ Longterm > 4.1 Sasha Levin 2015-06-21 Sep, 2017 > 3.18 Sasha Levin

Re: [PATCH kernel.org] change 3.12 EOL

Jiri Slaby wrote: > diff --git a/content/releases.rst b/content/releases.rst > index 28ebf47834..14494a64cd 100644 > --- a/content/releases.rst > +++ b/content/releases.rst > @@ -44,7 +44,7 @@ Longterm > 4.1 Sasha Levin 2015-06-21 Sep, 2017 > 3.18 Sasha Levin

Re: Generic kernel features that need architecture(mips) support

On 06/10/2015 04:58 PM, Ralf Baechle wrote: > How are the documentation files in Documentation/features/ maintained? > They were automatically generated so I wonder if I have to take care > of anything. CC: Ingo and related ml. -- To unsubscribe from this list: send the line "unsubscribe

Re: Generic kernel features that need architecture(mips) support

On 06/10/2015 04:58 PM, Ralf Baechle wrote: How are the documentation files in Documentation/features/ maintained? They were automatically generated so I wonder if I have to take care of anything. CC: Ingo and related ml. -- To unsubscribe from this list: send the line unsubscribe

Re: [PATCH RESEND] firmware: Update information in linux.git about adding firmware

t; README in linux-firmware.git added by Xose Vazquez Perez > . > > Signed-off-by: Ben Hutchings > --- > firmware/README.AddingFirmware | 14 -- > 1 file changed, 12 insertions(+), 2 deletions(-) > > diff --git a/firmware/README.AddingFirmware b/firmware/READ

Re: [PATCH RESEND] firmware: Update information in linux.git about adding firmware

in the README in linux-firmware.git added by Xose Vazquez Perez xose.vazq...@gmail.com. Signed-off-by: Ben Hutchings b...@decadent.org.uk --- firmware/README.AddingFirmware | 14 -- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/firmware/README.AddingFirmware b

Re: [RFC] Fix Free Software Foundation address in file headers

Jeff Kirsher wrote: > This came up when John Fastabend got a patch to fix up the headers in > the drivers/scsi/ directory and so I did a quick search of the network > drivers and found several instances in the file headers where an old FSF > address remains. The old address is: > > 59 Temple

Re: [RFC] Fix Free Software Foundation address in file headers

Jeff Kirsher wrote: This came up when John Fastabend got a patch to fix up the headers in the drivers/scsi/ directory and so I did a quick search of the network drivers and found several instances in the file headers where an old FSF address remains. The old address is: 59 Temple Place -

[PATCH -rc1] s390: increase the NR_CPUS limit

In current models, maximum number of active cores is 101. Cc: Martin Schwidefsky Cc: Heiko Carstens Cc: Cc: Cc: Signed-off-by: Xose Vazquez Perez --- arch/s390/Kconfig | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig index

[PATCH -rc1] s390: increase the NR_CPUS limit

In current models, maximum number of active cores is 101. Cc: Martin Schwidefsky schwidef...@de.ibm.com Cc: Heiko Carstens heiko.carst...@de.ibm.com Cc: linux...@de.ibm.com Cc: linux-s...@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: Xose Vazquez Perez xose.vazq...@gmail.com

[PATCH] linux-firmware: add MISSING file

to document the reason why a firmware is not present Cc: Daniel Drake Cc: Ulrich Kunitz Cc: David Woodhouse Cc: Ben Hutchings Cc: Cc: Signed-off-by: Xose Vazquez Perez --- MISSING | 20 1 file changed, 20 insertions(+) create mode 100644 MISSING diff --git a/MISSING

[PATCH] linux-firmware: add MISSING file

Vazquez Perez xose.vazq...@gmail.com --- MISSING | 20 1 file changed, 20 insertions(+) create mode 100644 MISSING diff --git a/MISSING b/MISSING new file mode 100644 index 000..f228099 --- /dev/null +++ b/MISSING @@ -0,0 +1,20

what's about 2.2 kernel?

hi, time to release a final 2.2.27 and close the 2.2 tree ??? The latest 2.2 version : 2.2.26 2004-02-25 00:28 UTC The latest prepatch 2.2 : 2.2.27-rc2 2005-01-12 23:55 UTC regards, -- Politicos de mierda, yo no soy un terrorista. - To unsubscribe from this list: send the line

what's about 2.2 kernel?

hi, time to release a final 2.2.27 and close the 2.2 tree ??? The latest 2.2 version : 2.2.26 2004-02-25 00:28 UTC The latest prepatch 2.2 : 2.2.27-rc2 2005-01-12 23:55 UTC regards, -- Politicos de mierda, yo no soy un terrorista. - To unsubscribe from this list: send the line

Re: [BUG] ISIC + 2.6.22 (via-rhine)

Arjan van de Ven wrote: = [ INFO: inconsistent lock state ] 2.6.22 #1 - inconsistent {in-hardirq-W} -> {hardirq-on-W} usage. swapper/0 [HC0[0]:SC1[1]:HE1:SE0] takes: (>lock){++..}, at: [] rhine_tx_timeout+0x6f/0xf4 [via_rhine]

[BUG] ISIC + 2.6.22 (via-rhine)

hi, Running ISIC -- IP Stack Integrity Checker ( http://isic.sf.net ), in Fedora-7-i386 with 2.6.22, the NIC stopped to send packages. But one second latter it began to send out more of them. dmesg shows the bug. command is: # tcpsic -s rand -d 172.26.0.2 -I100 driver is:

[BUG] ISIC + 2.6.22 (via-rhine)

hi, Running ISIC -- IP Stack Integrity Checker ( http://isic.sf.net ), in Fedora-7-i386 with 2.6.22, the NIC stopped to send packages. But one second latter it began to send out more of them. dmesg shows the bug. command is: # tcpsic -s rand -d 172.26.0.2 -I100 driver is:

Re: [BUG] ISIC + 2.6.22 (via-rhine)

Arjan van de Ven wrote: = [ INFO: inconsistent lock state ] 2.6.22 #1 - inconsistent {in-hardirq-W} - {hardirq-on-W} usage. swapper/0 [HC0[0]:SC1[1]:HE1:SE0] takes: (rp-lock){++..}, at: [f8c890db] rhine_tx_timeout+0x6f/0xf4

[PATCH 2.6.12 1/1] docs: updated some code docs

Updated docs about how to write and submit patches/code. diff -Nuar old/Documentation/CodingStyle new/Documentation/CodingStyle --- old/Documentation/CodingStyle 2005-07-26 00:10:55.0 +0200 +++ new/Documentation/CodingStyle 2005-07-25 23:58:37.0 +0200 @@ -422,10 +422,13 @@ URL:

[PATCH 2.6.12 1/1] docs: updated some code docs

Updated docs about how to write and submit patches/code. diff -Nuar old/Documentation/CodingStyle new/Documentation/CodingStyle --- old/Documentation/CodingStyle 2005-07-26 00:10:55.0 +0200 +++ new/Documentation/CodingStyle 2005-07-25 23:58:37.0 +0200 @@ -422,10 +422,13 @@ URL: