From: Jon Mason <mason@myri.com> To: Justin Piszcz <jpiszcz@lucidpixels.com> Cc: Eric Dumazet <eric.dumazet@gmail.com>, Jesse Brandeburg <jesse.brandeburg@gmail.com>, Alan Piszcz <ap@solarrain.com>, NetDEV list <netdev@vger.kernel.org>, xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: 3.1-rc4: spectacular kernel errors / filesystem crash Date: Tue, 13 Sep 2011 10:35:29 -0500 [thread overview] Message-ID: <CAMaF-rN-qeXBDoc9=7kwu40Wj8=G8YuPKWXPRhOuhdYX_VO34w@mail.gmail.com> (raw) In-Reply-To: <alpine.DEB.2.02.1109130722210.21380@p34.internal.lan> On Tue, Sep 13, 2011 at 9:54 AM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote: > > > On Tue, 13 Sep 2011, Eric Dumazet wrote: > >> Please Justin make sure you pulled commit >> commit ed2888e906b56769b4ffabb9c577190438aa68b8 >> Author: Jon Mason <mason@myri.com> >> Date: Thu Sep 8 16:41:18 2011 -0500 >> >> PCI: Remove MRRS modification from MPS setting code >> >> Modifying the Maximum Read Request Size to 0 (value of 128Bytes) has >> massive negative ramifications on some devices. Without knowing which >> devices have this issue, do not modify from the default value when >> walking the PCI-E bus in pcie_bus_safe mode. Also, make pcie_bus_safe >> the default procedure. >> >> Tested-by: Sven Schnelle <svens@stackframe.org> >> Tested-by: Simon Kirby <sim@hostway.ca> >> Tested-by: Stephen M. Cameron <scameron@beardog.cce.hp.com> >> Reported-and-tested-by: Eric Dumazet <eric.dumazet@gmail.com> >> Reported-and-tested-by: Niels Ole Salscheider >> <niels_ole@salscheider-online. >> References: https://bugzilla.kernel.org/show_bug.cgi?id=42162 >> Signed-off-by: Jon Mason <mason@myri.com> >> Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org> >> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> > > Hello, > > I found this commit here: > http://permalink.gmane.org/gmane.linux.kernel.pci/11700 This is an early version of the patch. This is the patch that you want: https://github.com/torvalds/linux/commit/ed2888e906b56769b4ffabb9c577190438aa68b8 It appears that this patch didn't make it to lkml or linux-pci list due to kernel.org DNS being down when it was sent. Thanks, Jon > > Applied: > # patch -p1 < ../ed2888e906b56769b4ffabb9c577190438aa68b8.txt patching file > drivers/pci/probe.c > > I will update this thread if the problem recurs, can someone also please > advise > which DEBUG options I should have enabled to catch further SLAB/RCU issues? > > So far, I have the following enabled: > > CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y > CONFIG_HAVE_DMA_API_DEBUG=y > CONFIG_X86_DEBUGCTLMSR=y > CONFIG_DEBUG_FS=y > CONFIG_DEBUG_KERNEL=y > CONFIG_DEBUG_SLAB=y > CONFIG_DEBUG_SLAB_LEAK=y > CONFIG_DEBUG_KMEMLEAK=y > CONFIG_DEBUG_STACK_USAGE=y > CONFIG_DEBUG_BUGVERBOSE=y > CONFIG_DEBUG_INFO=y > CONFIG_DEBUG_VM=y > CONFIG_DEBUG_VIRTUAL=y > CONFIG_DEBUG_MEMORY_INIT=y > CONFIG_DEBUG_PER_CPU_MAPS=y > CONFIG_DEBUG_PAGEALLOC=y > CONFIG_DEBUG_STACKOVERFLOW=y > CONFIG_DEBUG_RODATA=y > > Thanks, > > Justin. > > -- > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >
WARNING: multiple messages have this Message-ID (diff)
From: Jon Mason <mason@myri.com> To: Justin Piszcz <jpiszcz@lucidpixels.com> Cc: Eric Dumazet <eric.dumazet@gmail.com>, NetDEV list <netdev@vger.kernel.org>, linux-kernel@vger.kernel.org, xfs@oss.sgi.com, Jesse Brandeburg <jesse.brandeburg@gmail.com>, Alan Piszcz <ap@solarrain.com> Subject: Re: 3.1-rc4: spectacular kernel errors / filesystem crash Date: Tue, 13 Sep 2011 10:35:29 -0500 [thread overview] Message-ID: <CAMaF-rN-qeXBDoc9=7kwu40Wj8=G8YuPKWXPRhOuhdYX_VO34w@mail.gmail.com> (raw) In-Reply-To: <alpine.DEB.2.02.1109130722210.21380@p34.internal.lan> On Tue, Sep 13, 2011 at 9:54 AM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote: > > > On Tue, 13 Sep 2011, Eric Dumazet wrote: > >> Please Justin make sure you pulled commit >> commit ed2888e906b56769b4ffabb9c577190438aa68b8 >> Author: Jon Mason <mason@myri.com> >> Date: Thu Sep 8 16:41:18 2011 -0500 >> >> PCI: Remove MRRS modification from MPS setting code >> >> Modifying the Maximum Read Request Size to 0 (value of 128Bytes) has >> massive negative ramifications on some devices. Without knowing which >> devices have this issue, do not modify from the default value when >> walking the PCI-E bus in pcie_bus_safe mode. Also, make pcie_bus_safe >> the default procedure. >> >> Tested-by: Sven Schnelle <svens@stackframe.org> >> Tested-by: Simon Kirby <sim@hostway.ca> >> Tested-by: Stephen M. Cameron <scameron@beardog.cce.hp.com> >> Reported-and-tested-by: Eric Dumazet <eric.dumazet@gmail.com> >> Reported-and-tested-by: Niels Ole Salscheider >> <niels_ole@salscheider-online. >> References: https://bugzilla.kernel.org/show_bug.cgi?id=42162 >> Signed-off-by: Jon Mason <mason@myri.com> >> Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org> >> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> > > Hello, > > I found this commit here: > http://permalink.gmane.org/gmane.linux.kernel.pci/11700 This is an early version of the patch. This is the patch that you want: https://github.com/torvalds/linux/commit/ed2888e906b56769b4ffabb9c577190438aa68b8 It appears that this patch didn't make it to lkml or linux-pci list due to kernel.org DNS being down when it was sent. Thanks, Jon > > Applied: > # patch -p1 < ../ed2888e906b56769b4ffabb9c577190438aa68b8.txt patching file > drivers/pci/probe.c > > I will update this thread if the problem recurs, can someone also please > advise > which DEBUG options I should have enabled to catch further SLAB/RCU issues? > > So far, I have the following enabled: > > CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y > CONFIG_HAVE_DMA_API_DEBUG=y > CONFIG_X86_DEBUGCTLMSR=y > CONFIG_DEBUG_FS=y > CONFIG_DEBUG_KERNEL=y > CONFIG_DEBUG_SLAB=y > CONFIG_DEBUG_SLAB_LEAK=y > CONFIG_DEBUG_KMEMLEAK=y > CONFIG_DEBUG_STACK_USAGE=y > CONFIG_DEBUG_BUGVERBOSE=y > CONFIG_DEBUG_INFO=y > CONFIG_DEBUG_VM=y > CONFIG_DEBUG_VIRTUAL=y > CONFIG_DEBUG_MEMORY_INIT=y > CONFIG_DEBUG_PER_CPU_MAPS=y > CONFIG_DEBUG_PAGEALLOC=y > CONFIG_DEBUG_STACKOVERFLOW=y > CONFIG_DEBUG_RODATA=y > > Thanks, > > Justin. > > -- > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-09-13 15:42 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-11 9:40 3.1-rc4: spectacular kernel errors / filesystem crash Justin Piszcz 2011-09-11 9:40 ` Justin Piszcz 2011-09-13 3:59 ` Jesse Brandeburg 2011-09-13 3:59 ` Jesse Brandeburg 2011-09-13 4:05 ` Eric Dumazet 2011-09-13 4:05 ` Eric Dumazet 2011-09-13 14:54 ` Justin Piszcz 2011-09-13 14:54 ` Justin Piszcz 2011-09-13 14:58 ` Eric Dumazet 2011-09-13 14:58 ` Eric Dumazet 2011-09-13 15:35 ` Jon Mason [this message] 2011-09-13 15:35 ` Jon Mason 2011-09-13 15:42 ` Justin Piszcz 2011-09-13 15:42 ` Justin Piszcz 2011-09-13 15:51 ` Jon Mason 2011-09-13 15:51 ` Jon Mason 2011-09-13 16:32 ` Justin Piszcz 2011-09-13 16:32 ` Justin Piszcz
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAMaF-rN-qeXBDoc9=7kwu40Wj8=G8YuPKWXPRhOuhdYX_VO34w@mail.gmail.com' \ --to=mason@myri.com \ --cc=ap@solarrain.com \ --cc=eric.dumazet@gmail.com \ --cc=jesse.brandeburg@gmail.com \ --cc=jpiszcz@lucidpixels.com \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=xfs@oss.sgi.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.