Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1312987 > unrolled thread
| Started by | Borislav Petkov <bp@alien8.de> |
|---|---|
| First post | 2016-01-20 09:30 +0100 |
| Last post | 2016-01-20 09:30 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [patch 00/14] x86/irq: Plug various vector cleanup races Borislav Petkov <bp@alien8.de> - 2016-01-20 09:30 +0100
| From | Borislav Petkov <bp@alien8.de> |
|---|---|
| Date | 2016-01-20 09:30 +0100 |
| Subject | Re: [patch 00/14] x86/irq: Plug various vector cleanup races |
| Message-ID | <qSWjo-3N7-7@gated-at.bofh.it> |
On Tue, Jan 19, 2016 at 10:57:35PM -0500, Joe Lawrence wrote:
> Unfortunately I only have a single box to run these tests in what
> amounts to an after-hours effort. I started testing back in 4.3 but
> avoided moving forward to avoid the 4.4 development cycle (and
> incidental issues that it might have muddled the waters). That said,
> what would be the best way to proceed?
>
> Change device removal tests to avoid proprietary drivers.
Right, I'd tend to suggest that. tglx says you could also try enabling
CONFIG_DEBUG_OBJECTS and CONFIG_DEBUG_OBJECTS_TIMERS and collect full
dmesg from when the corruption happens. That might give us some more
insights as to what happens.
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
Back to top | Article view | linux.kernel
csiph-web