Question about dev_queue_xmit and guaranteed packet transmission

I noticed that Linux has been updated on later versions to always consume the skb in calls to dev_queue_xmit, and may even drop the skb after returning a return code of NETDEV_TX_OK which seems kind of broken. I have an application which requires guaranteed skb transmission and the following code

Re: [GIT PULL] MDB Linux Kernel Debugger v4.8 (for kbuild robot testing)

On 10/3/16, Jeffrey Merkey <jeffmer...@gmail.com> wrote: > On 10/3/16, Joe Perches <j...@perches.com> wrote: >> >> On Tue, 2016-10-04 at 13:29 +1100, Stephen Rothwell wrote: >>> Hi Joe, >> >> Hi Stephen. >> >>> On Mon,

Re: [GIT PULL] MDB Linux Kernel Debugger v4.8 (for kbuild robot testing)

On 10/3/16, Jeffrey Merkey wrote: > On 10/3/16, Joe Perches wrote: >> >> On Tue, 2016-10-04 at 13:29 +1100, Stephen Rothwell wrote: >>> Hi Joe, >> >> Hi Stephen. >> >>> On Mon, 03 Oct 2016 18:47:04 -0700 Joe Perches wrote: >>> >

Re: [GIT PULL] MDB Linux Kernel Debugger v4.8 (for kbuild robot testing)

On 10/3/16, Joe Perches <j...@perches.com> wrote: > > On Tue, 2016-10-04 at 13:29 +1100, Stephen Rothwell wrote: >> Hi Joe, > > Hi Stephen. > >> On Mon, 03 Oct 2016 18:47:04 -0700 Joe Perches <j...@perches.com> wrote: >> > >> >

Re: [GIT PULL] MDB Linux Kernel Debugger v4.8 (for kbuild robot testing)

On 10/3/16, Joe Perches wrote: > > On Tue, 2016-10-04 at 13:29 +1100, Stephen Rothwell wrote: >> Hi Joe, > > Hi Stephen. > >> On Mon, 03 Oct 2016 18:47:04 -0700 Joe Perches wrote: >> > >> > On Mon, 2016-10-03 at 18:17 -0600, Jeffrey Merkey wro

[GIT PULL] MDB Linux Kernel Debugger v4.8 (for kbuild robot testing)

Debugger to Linux Kernel v4.8 (2016-10-02 20:33:55 -0600) Jeffrey Merkey (1): Add MDB Debugger to Linux Kernel v4.8 Documentation/sysrq.txt|2 +- MAINTAINERS|6 + arch

[GIT PULL] MDB Linux Kernel Debugger v4.8 (for kbuild robot testing)

Debugger to Linux Kernel v4.8 (2016-10-02 20:33:55 -0600) Jeffrey Merkey (1): Add MDB Debugger to Linux Kernel v4.8 Documentation/sysrq.txt|2 +- MAINTAINERS|6 + arch

[GIT PULL] MDB Linux Kernel Debugger v4.8 (for kbuild robot testing)

Debugger to Linux Kernel v4.8 (2016-10-02 20:33:55 -0600) Jeffrey Merkey (1): Add MDB Debugger to Linux Kernel v4.8 Documentation/sysrq.txt|2 +- MAINTAINERS|6 + arch

[GIT PULL] MDB Linux Kernel Debugger v4.8 (for kbuild robot testing)

Debugger to Linux Kernel v4.8 (2016-10-02 20:33:55 -0600) Jeffrey Merkey (1): Add MDB Debugger to Linux Kernel v4.8 Documentation/sysrq.txt|2 +- MAINTAINERS|6 + arch

[ANNOUNCE] MDB Linux Kernel Debugger Linux v4.6

lines checked 0001-Add-MDB-Linux-Kernel-Debugger-to-Linux-v4.6.patch has no obvious style problems and is ready for submission. ---- Jeffrey Merkey (1): Add MDB Linux Kernel Debugger to Linux v4.6 Documentation/sys

[ANNOUNCE] MDB Linux Kernel Debugger Linux v4.6

-Linux-Kernel-Debugger-to-Linux-v4.6.patch has no obvious style problems and is ready for submission. Jeffrey Merkey (1): Add MDB Linux Kernel Debugger to Linux v4.6 Documentation/sysrq.txt|2

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/25/16, Stephen Rothwell <s...@canb.auug.org.au> wrote: > Hi Jeff, > > On Fri, 25 Mar 2016 17:01:27 -0600 Jeffrey Merkey <jeffmer...@gmail.com> > wrote: >> >> I went back and checked the code and as it turns out, none of the >> patches you nak'd are

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/25/16, Stephen Rothwell wrote: > Hi Jeff, > > On Fri, 25 Mar 2016 17:01:27 -0600 Jeffrey Merkey > wrote: >> >> I went back and checked the code and as it turns out, none of the >> patches you nak'd are in the current branch, there are different >> patche

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/25/16, Jeffrey Merkey <jeffmer...@gmail.com> wrote: > On 3/25/16, Jeffrey Merkey <jeffmer...@gmail.com> wrote: >> On 3/25/16, Jeffrey Merkey <jeffmer...@gmail.com> wrote: >>> On 3/25/16, Ingo Molnar <mi...@kernel.org> wrote: >>>>

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/25/16, Jeffrey Merkey wrote: > On 3/25/16, Jeffrey Merkey wrote: >> On 3/25/16, Jeffrey Merkey wrote: >>> On 3/25/16, Ingo Molnar wrote: >>>> >>>> * Stephen Rothwell wrote: >>>> >>>>> Hi Joe, >>>>> >&

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/25/16, Jeffrey Merkey <jeffmer...@gmail.com> wrote: > On 3/25/16, Jeffrey Merkey <jeffmer...@gmail.com> wrote: >> On 3/25/16, Ingo Molnar <mi...@kernel.org> wrote: >>> >>> * Stephen Rothwell <s...@canb.auug.org.au> wrote: >>> &

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/25/16, Jeffrey Merkey wrote: > On 3/25/16, Jeffrey Merkey wrote: >> On 3/25/16, Ingo Molnar wrote: >>> >>> * Stephen Rothwell wrote: >>> >>>> Hi Joe, >>>> >>>> On Mon, 14 Mar 2016 16:57:03 -0700 Joe Perches wrot

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/25/16, Jeffrey Merkey <jeffmer...@gmail.com> wrote: > On 3/25/16, Ingo Molnar <mi...@kernel.org> wrote: >> >> * Stephen Rothwell <s...@canb.auug.org.au> wrote: >> >>> Hi Joe, >>> >>> On Mon, 14 Mar 2016 16:57:03 -0700 Joe Perc

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/25/16, Jeffrey Merkey wrote: > On 3/25/16, Ingo Molnar wrote: >> >> * Stephen Rothwell wrote: >> >>> Hi Joe, >>> >>> On Mon, 14 Mar 2016 16:57:03 -0700 Joe Perches wrote: >>> > >>> > On Mon, 2016-03-14 at 17:50

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/25/16, Ingo Molnar <mi...@kernel.org> wrote: > > * Stephen Rothwell <s...@canb.auug.org.au> wrote: > >> Hi Joe, >> >> On Mon, 14 Mar 2016 16:57:03 -0700 Joe Perches <j...@perches.com> wrote: >> > >> > On Mon, 2016-03-14 at 17:50

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/25/16, Ingo Molnar wrote: > > * Stephen Rothwell wrote: > >> Hi Joe, >> >> On Mon, 14 Mar 2016 16:57:03 -0700 Joe Perches wrote: >> > >> > On Mon, 2016-03-14 at 17:50 -0600, Jeffrey Merkey wrote: >> > > The following changes sin

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/17/16, Joe Perches <j...@perches.com> wrote: > On Thu, 2016-03-17 at 23:31 -0600, Jeffrey Merkey wrote: >> On 3/16/16, Jeffrey Merkey <jeffmer...@gmail.com> wrote: >> > On 3/15/16, Theodore Ts'o <ty...@mit.edu> wrote: >> > > On Tue, Mar 15,

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/17/16, Joe Perches wrote: > On Thu, 2016-03-17 at 23:31 -0600, Jeffrey Merkey wrote: >> On 3/16/16, Jeffrey Merkey wrote: >> > On 3/15/16, Theodore Ts'o wrote: >> > > On Tue, Mar 15, 2016 at 01:03:39PM +1100, Stephen Rothwell wrote: >> > > &g

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/15/16, Theodore Ts'o wrote: > On Tue, Mar 15, 2016 at 01:03:39PM +1100, Stephen Rothwell wrote: >> We don't generally PGP (GPG) sign commits in the kernel tree (so "-S" >> is not required), just tags. However we always require that anyone who >> handles a patch adds a

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/15/16, Theodore Ts'o wrote: > On Tue, Mar 15, 2016 at 01:03:39PM +1100, Stephen Rothwell wrote: >> We don't generally PGP (GPG) sign commits in the kernel tree (so "-S" >> is not required), just tags. However we always require that anyone who >> handles a patch adds a Signed-off-by line to

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/16/16, Jeffrey Merkey <jeffmer...@gmail.com> wrote: > On 3/15/16, Theodore Ts'o <ty...@mit.edu> wrote: >> On Tue, Mar 15, 2016 at 01:03:39PM +1100, Stephen Rothwell wrote: >>> We don't generally PGP (GPG) sign commits in the kernel tree (so "-S" >

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/16/16, Jeffrey Merkey wrote: > On 3/15/16, Theodore Ts'o wrote: >> On Tue, Mar 15, 2016 at 01:03:39PM +1100, Stephen Rothwell wrote: >>> We don't generally PGP (GPG) sign commits in the kernel tree (so "-S" >>> is not required), just tags. Howe

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/14/16, Stephen Rothwell <s...@canb.auug.org.au> wrote: > Hi Joe, > > On Mon, 14 Mar 2016 16:57:03 -0700 Joe Perches <j...@perches.com> wrote: >> >> On Mon, 2016-03-14 at 17:50 -0600, Jeffrey Merkey wrote: >> > The following changes since commit >

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/14/16, Stephen Rothwell wrote: > Hi Joe, > > On Mon, 14 Mar 2016 16:57:03 -0700 Joe Perches wrote: >> >> On Mon, 2016-03-14 at 17:50 -0600, Jeffrey Merkey wrote: >> > The following changes since commit >> > b562e44f507e863c6792946e4e1b1449fbbac85d: >

[GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

problems and is ready for submission. Jeffrey Merkey (1): Add MDB Debugger to linux v4.5 Documentation/sysrq.txt|2 +- MAINTAINERS|6 + arch/x86/include/asm/bug.h

[GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

problems and is ready for submission. Jeffrey Merkey (1): Add MDB Debugger to linux v4.5 Documentation/sysrq.txt|2 +- MAINTAINERS|6 + arch/x86/include/asm/bug.h

[GIT PULL v4.6 UPDATED] Add MDB Kernel Debugger Linux v4.6

. Jeffrey Merkey (3): Add MDB Kernel Debugger for Linux to Linus' Tree Add Kconfig.debug options for build Add kbuild-test-robot fixes for CONFIG_VT Documentation/sysrq.txt|2 +- MAINTAINERS

[GIT PULL v4.6 UPDATED] Add MDB Kernel Debugger Linux v4.6

. Jeffrey Merkey (3): Add MDB Kernel Debugger for Linux to Linus' Tree Add Kconfig.debug options for build Add kbuild-test-robot fixes for CONFIG_VT Documentation/sysrq.txt|2 +- MAINTAINERS

[GIT PULL v4.6] Add MDB Kernel Debugger to Linux Kernel v4.6

. Jeffrey Merkey (3): Add MDB Kernel Debugger for Linux to Linus' Tree Add Kconfig.debug options for build Add kbuild-test-robot fixes for CONFIG_VT Documentation/sysrq.txt|2 +- MAINTAINERS

[GIT PULL v4.6] Add MDB Kernel Debugger to Linux Kernel v4.6

. Jeffrey Merkey (3): Add MDB Kernel Debugger for Linux to Linus' Tree Add Kconfig.debug options for build Add kbuild-test-robot fixes for CONFIG_VT Documentation/sysrq.txt|2 +- MAINTAINERS

[PATCH] Add fix case for open braces

Some quite excellent fixes from Joe Perches that belong back in the original. Submitting to Joe for inclusion. Joe was the original author of these fixes that save a lot of time rewriting code. Thanks Joe. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.com> --- scripts/checkpatch.p

[PATCH] Add fix case for open braces

Some quite excellent fixes from Joe Perches that belong back in the original. Submitting to Joe for inclusion. Joe was the original author of these fixes that save a lot of time rewriting code. Thanks Joe. Signed-off-by: Jeffrey Merkey --- scripts/checkpatch.pl | 23

Re: [PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

>> So, if you disable 'sysctl_hardlockup_all_cpu_backtrace' and enable >> 'hardlockup_panic', you should be able to achieve what you want, no? >> >> But you mentioned you wanted to recover? Hence avoiding the panic? >> >> Cheers, >> Don >> > > Yes. Avoiding the panic is what I wanted to do.

Re: [PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

On 2/3/16, Don Zickus wrote: > On Wed, Feb 03, 2016 at 10:23:42AM -0700, Jeffrey Merkey wrote: >> > Hmm, I am confused here. So you are saying because we are in the nmi >> > handler you can not break into the system? The nmi handler prints some >> > stuff to th

Re: [PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

On 2/3/16, Don Zickus wrote: > On Tue, Feb 02, 2016 at 03:40:34PM -0700, Jeffrey Merkey wrote: >> > >> > Please remember to add version history, so I can tell what changed. >> > >> >> What command do I give to git when it creates the patch from

Re: [PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

> Hmm, I am confused here. So you are saying because we are in the nmi > handler you can not break into the system? The nmi handler prints some > stuff to the screen, pokes the other cpus to print stuff to the screen and > then returns to a normal operation. Unless you are saying the act of >

Re: [PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

On 2/3/16, Don Zickus <dzic...@redhat.com> wrote: > On Wed, Feb 03, 2016 at 10:23:42AM -0700, Jeffrey Merkey wrote: >> > Hmm, I am confused here. So you are saying because we are in the nmi >> > handler you can not break into the system? The nmi handler prints so

Re: [PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

>> So, if you disable 'sysctl_hardlockup_all_cpu_backtrace' and enable >> 'hardlockup_panic', you should be able to achieve what you want, no? >> >> But you mentioned you wanted to recover? Hence avoiding the panic? >> >> Cheers, >> Don >> > > Yes. Avoiding the panic is what I wanted to do.

Re: [PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

> Hmm, I am confused here. So you are saying because we are in the nmi > handler you can not break into the system? The nmi handler prints some > stuff to the screen, pokes the other cpus to print stuff to the screen and > then returns to a normal operation. Unless you are saying the act of >

Re: [PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

On 2/3/16, Don Zickus <dzic...@redhat.com> wrote: > On Tue, Feb 02, 2016 at 03:40:34PM -0700, Jeffrey Merkey wrote: >> > >> > Please remember to add version history, so I can tell what changed. >> > >> >> What command do I give to git when it creates

Re: [PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

On 2/2/16, Jeffrey Merkey wrote: >> Because when you catch a bug in the hard lockup detector the system >> just sits there hard hung and you are not able to get into a debugger >> console since the system has crashed and the watchdog code has already >> killed off the oth

Re: [PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

> Because when you catch a bug in the hard lockup detector the system > just sits there hard hung and you are not able to get into a debugger > console since the system has crashed and the watchdog code has already > killed off the other processors and locked up all the NMI interrupt > handlers,

Re: [PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

> > Please remember to add version history, so I can tell what changed. > What command do I give to git when it creates the patch from git format-patch that outputs what you are looking for or do I have to add that manually. The diff of files changed? > > I am not sure I am a fan of this. You

Re: [PATCH v4 4/4] pr_emerg add WARN_XX() debugger options

On 2/2/16, Maciej W. Rozycki wrote: > On Mon, 1 Feb 2016, Jeffrey Merkey wrote: > >> If a debugger is loaded it will not crash, just enter the debugger. >> But yes, it will int3 if set and no debugger has been loaded to handle >> the int3 condition. Hmmm. Maybe its bet

Re: [PATCH v4 4/4] pr_emerg add WARN_XX() debugger options

On 2/2/16, Maciej W. Rozycki <ma...@linux-mips.org> wrote: > On Mon, 1 Feb 2016, Jeffrey Merkey wrote: > >> If a debugger is loaded it will not crash, just enter the debugger. >> But yes, it will int3 if set and no debugger has been loaded to handle >> the int3 condi

Re: [PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

> > Please remember to add version history, so I can tell what changed. > What command do I give to git when it creates the patch from git format-patch that outputs what you are looking for or do I have to add that manually. The diff of files changed? > > I am not sure I am a fan of this. You

Re: [PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

> Because when you catch a bug in the hard lockup detector the system > just sits there hard hung and you are not able to get into a debugger > console since the system has crashed and the watchdog code has already > killed off the other processors and locked up all the NMI interrupt > handlers,

Re: [PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

On 2/2/16, Jeffrey Merkey <jeffmer...@gmail.com> wrote: >> Because when you catch a bug in the hard lockup detector the system >> just sits there hard hung and you are not able to get into a debugger >> console since the system has crashed and the watchdog code has already

[PATCH v5 1/3] Add BUG_XX() debugging options

allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- arch/x86/include/asm/bug.h

[PATCH v5 2/3] Add BUG_XX() debugging options Kconfig.debug

allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- lib/Kconfig.debug | 11

[PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- kernel/watchdog.c | 10

Re: [PATCH v4 4/4] pr_emerg add WARN_XX() debugger options

On 2/1/16, Steven Rostedt wrote: > On Mon, 1 Feb 2016 16:35:52 -0700 > Jeffrey Merkey wrote: >> --- >> include/linux/printk.h | 8 >> 1 file changed, 8 insertions(+) >> >> diff --git a/include/linux/printk.h b/include/linux/printk.h >> inde

[PATCH v4 1/4] Add BUG_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- arch/x86/include

[PATCH v4 2/4] Add WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- include/asm

[PATCH v4 3/4] Add BUG_XX() and WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- lib

[PATCH v4 4/4] pr_emerg add WARN_XX() debugger options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- include/linux

[PATCH v3 4/4] pr_emerg add WARN_XX() debugger options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- include/linux

[PATCH v3 1/4] Add BUG_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- arch/x86/include

[PATCH v3 2/4] Add WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- include/asm

[PATCH v3 3/4] Add BUG_XX() and WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- lib

Re: [PATCH v2 4/4] Add WARN() function call to hard-soft lockup

>> >> +WARN(1, "Watchdog detected hard LOCKUP on cpu %d", this_cpu); >> + > > So we repeat the same exact print message and dump the same stack again as > we do a few lines above? That doesn't make any sense. > > Cheers, > Don > Agreed. I'll go back and work on it. Jeff

[PATCH v2 2/4] Add WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- include/asm

[PATCH v2 4/4] Add WARN() function call to hard-soft lockup

time option also allows conditional breakpoints to be set in the kernel where these macros have been previously placed. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey

[PATCH v2 3/4] Add BUG_XX() and WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- lib

[PATCH v2 1/4] Add BUG_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- arch/x86/include

Re: [PATCH 1/4] Add BUG_XX() debugging options

On 2/1/16, Jeffrey Merkey wrote: > On 2/1/16, kbuild test robot wrote: >> Hi Jeffrey, >> >> [auto build test WARNING on v4.5-rc2] >> [also build test WARNING on next-20160201] >> [cannot apply to tip/x86/core] >> [if your patch is applied to the wrong git

Re: [PATCH 1/4] Add BUG_XX() debugging options

tem] > > url: > https://github.com/0day-ci/linux/commits/Jeffrey-Merkey/Add-BUG_XX-debugging-options/20160202-040506 > config: x86_64-randconfig-x012-201605 (attached as .config) > reproduce: > # save the attached .config to linux build tree > make ARCH=

[PATCH 3/4] Add BUG_XX() and WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- lib

[PATCH 4/4] Add WARN() function call to hard-soft lockup

time option also allows conditional breakpoints to be set in the kernel where these macros have been previously placed. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey

[PATCH 1/4] Add BUG_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- arch/x86/include

[PATCH 2/4] Add WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey --- include/asm

[PATCH v2 4/4] Add WARN() function call to hard-soft lockup

time option also allows conditional breakpoints to be set in the kernel where these macros have been previously placed. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey

Re: [PATCH 1/4] Add BUG_XX() debugging options

On 2/1/16, Jeffrey Merkey <jeffmer...@gmail.com> wrote: > On 2/1/16, kbuild test robot <l...@intel.com> wrote: >> Hi Jeffrey, >> >> [auto build test WARNING on v4.5-rc2] >> [also build test WARNING on next-20160201] >> [cannot apply to tip/x86/core]

Re: [PATCH v2 4/4] Add WARN() function call to hard-soft lockup

>> >> +WARN(1, "Watchdog detected hard LOCKUP on cpu %d", this_cpu); >> + > > So we repeat the same exact print message and dump the same stack again as > we do a few lines above? That doesn't make any sense. > > Cheers, > Don > Agreed. I'll go back and work on it. Jeff

[PATCH v2 2/4] Add WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

[PATCH v2 3/4] Add BUG_XX() and WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

[PATCH 3/4] Add BUG_XX() and WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

[PATCH 4/4] Add WARN() function call to hard-soft lockup

time option also allows conditional breakpoints to be set in the kernel where these macros have been previously placed. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey

[PATCH 1/4] Add BUG_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

[PATCH 2/4] Add WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

Re: [PATCH 1/4] Add BUG_XX() debugging options

; help improving the system] > > url: > https://github.com/0day-ci/linux/commits/Jeffrey-Merkey/Add-BUG_XX-debugging-options/20160202-040506 > config: x86_64-randconfig-x012-201605 (attached as .config) > reproduce: > # save the attached .config to linux build tree >

[PATCH v3 4/4] pr_emerg add WARN_XX() debugger options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

[PATCH v4 4/4] pr_emerg add WARN_XX() debugger options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

[PATCH v4 3/4] Add BUG_XX() and WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

[PATCH v4 1/4] Add BUG_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

[PATCH v4 2/4] Add WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

[PATCH v3 3/4] Add BUG_XX() and WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

[PATCH v3 1/4] Add BUG_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

[PATCH v3 2/4] Add WARN_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

[PATCH v5 3/3] Add BUG_XX() debugging hard/soft lockup detection

allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

[PATCH v5 1/3] Add BUG_XX() debugging options

allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.com> ---

[PATCH v5 2/3] Add BUG_XX() debugging options Kconfig.debug

allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.com> --

Re: [PATCH v4 4/4] pr_emerg add WARN_XX() debugger options

On 2/1/16, Steven Rostedt <rost...@goodmis.org> wrote: > On Mon, 1 Feb 2016 16:35:52 -0700 > Jeffrey Merkey <jeffmer...@gmail.com> wrote: >> --- >> include/linux/printk.h | 8 >> 1 file changed, 8 insertions(+) >> >> diff --git a/include/

[PATCH v2 1/4] Add BUG_XX() debugging options

option also allows conditional breakpoints to be set in the kernel with these currently used macros. This addition is extremely useful for debugging hard and soft lockups real time and quickly from a console debugger, and other areas of the kernel. Signed-off-by: Jeffrey Merkey <jeffmer...@gmail.

Re: [PATCH 01/31] Add hard/soft lockup debugger entry points

On 1/29/16, Ingo Molnar wrote: > > * Jeffrey Merkey wrote: > >> On 1/28/16, Thomas Gleixner wrote: >> > On Thu, 28 Jan 2016, Jeffrey Merkey wrote: >> >> On 1/28/16, Thomas Gleixner wrote: >> >> > I'm probably missing something obvious here.

  1   2   3   >