From: Stefan Assmann <sassmann@kpanic.de>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: RIP [<ffffffff812c3b77>] ext4_release_file+0x37/0xc0 with 4.5-rc6 when resuming from suspend
Date: Tue, 8 Mar 2016 09:33:43 +0100 [thread overview]
Message-ID: <56DE8E67.2060909@kpanic.de> (raw)
In-Reply-To: <56DD3C65.8010304@kpanic.de>
On 07.03.2016 09:31, Stefan Assmann wrote:
> On 06.03.2016 20:10, Theodore Ts'o wrote:
>> On Sat, Mar 05, 2016 at 11:24:46AM +0100, Stefan Assmann wrote:
> It is 4.5-rc6 without any changes.
>
>> I don't see anything in ext4_release_file() that would obviously be a
>> potential problem after a suspend/reasume. One possibly is that some
>> other piece of code is corrupting memory.
>>
>>> [ 882.459687] CPU: 7 PID: 5299 Comm: dhclient Tainted: G W 4.5.0-0.rc6.git1.1.vanilla.knurd.1.fc23.x86_64 #1
>>
>> Is it always dhclient which is trying to exit?
>
> Most of the time the screen just stays black, so it's hard to tell. But
> while trying to reproduce just now I hit a null pointer exception in
> anon_vma_interval_tree_remove(), which happened right after initializing
> the exact same USB hub. Your corruption theory is getting more likely.
It's not a USB problem. I disconnected the USB hub and the corruption
remained. However, the backtrace was preceded by
[ 32.778070] snd_hda_codec_hdmi hdaudioC0D0: HDMI: pin nid 4 not registered
After making sure snd_hda_codec_hdmi did not get loaded during boot I've
not experienced the issue anymore. Of course I've only tried this a few
times so far, but it looks promising.
Anyway thanks for taking a look, I'll probably follow up on this with
the sound folks.
Stefan
prev parent reply other threads:[~2016-03-08 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 10:24 RIP [<ffffffff812c3b77>] ext4_release_file+0x37/0xc0 with 4.5-rc6 when resuming from suspend Stefan Assmann
2016-03-06 19:10 ` Theodore Ts'o
2016-03-07 8:31 ` Stefan Assmann
2016-03-08 8:33 ` Stefan Assmann [this message]
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=56DE8E67.2060909@kpanic.de \
--to=sassmann@kpanic.de \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.