All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laura Abbott <labbott@redhat.com>
To: Ron Murray <rjmx@rjmx.net>, Christoph Lameter <cl@linux.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Pekka Enberg <penberg@kernel.org>,
	David Rientjes <rientjes@google.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: PROBLEM: 4.1.4 -- Kernel Panic on shutdown
Date: Sun, 9 Aug 2015 06:48:54 -0700	[thread overview]
Message-ID: <55C75A46.6030308@redhat.com> (raw)
In-Reply-To: <55C5645D.1080508@rjmx.net>

On 08/07/2015 07:07 PM, Ron Murray wrote:
> On 08/07/2015 10:55 AM, Laura Abbott wrote:
>>
>> There was a similar report about a crash on reboot with 4.1.3[1]
>> where that reporter linked it to a bluetooth mouse. Hopefully this
>> isn't a red herring but it might be a similar report?
>>
>> Thanks,
>> Laura
>>
>> [1]https://bugzilla.redhat.com/show_bug.cgi?id=1248741
>>
> Thanks for the suggestion. I don't have a bluetooth mouse (although it
> is wireless), but I do have a bluetooth keyboard. And -- surprise! -- I
> don't get a crash when I leave the keyboard turned off.
>
> It seems to me that there are at least two possibilities here:
>
> 1. Something in the bluetooth stack causes some kind of memory corruption
>
> or
>
> 2. The corruption is caused by something else, and using bluetooth
> shifts it into a memory range where it causes crashes (we already know
> that it's very touchy).
>
> Do you know if the original poster in the Red Hat bug report solved the
> problem, or did he just give up using bluetooth?
>
> Suggestions for further faultfinding appreciated.
>
>   .....Ron
>
>


There was a report of HID corruption, can you try the patch at
https://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?id=0621809e37936e7c2b3eac9165cf2aad7f9189eb

Thanks,
Laura

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2015-08-09 13:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05  4:12 PROBLEM: 4.1.4 -- Kernel Panic on shutdown Ron Murray
2015-08-05 16:09 ` Christoph Lameter
2015-08-05 16:24   ` Peter Zijlstra
2015-08-05 16:32     ` Christoph Lameter
2015-08-05 16:36       ` Peter Zijlstra
2015-08-05 17:01         ` Christoph Lameter
2015-08-06  1:44           ` Ron Murray
2015-08-06  3:31             ` Christoph Lameter
2015-08-07  0:08               ` Ron Murray
2015-08-07 14:55                 ` Laura Abbott
2015-08-08  2:07                   ` Ron Murray
2015-08-09 13:48                     ` Laura Abbott [this message]
2015-08-10  1:30                       ` Ron Murray
2015-08-05 18:38     ` Ron Murray
2015-08-05 19:06       ` Christoph Lameter
2015-08-05 19:27         ` Ron Murray
2015-08-05 19:34           ` Christoph Lameter
2015-08-05 21:30             ` Ron Murray
2015-08-05 16:57   ` Ron Murray
2015-08-05 17:06     ` Christoph Lameter

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=55C75A46.6030308@redhat.com \
    --to=labbott@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=penberg@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rientjes@google.com \
    --cc=rjmx@rjmx.net \
    /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: link
Be 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.