From: Mihai Moldovan <ionic@ionic.de>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Oops (NULL ptr deref) while loading some module
Date: Mon, 15 Jul 2013 05:48:37 +0200 [thread overview]
Message-ID: <51E37115.3030308@ionic.de> (raw)
In-Reply-To: <51E33A4F.4040500@ionic.de>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
* On 15.07.2013 01:54 AM, Mihai Moldovan wrote:
> This is obviously happening while booting and udev is loading *some* module, but
> I have no idea which module is affected as such.
Quick correction: actually, at that time udev hasn't even started. udev is being
started by my initramfs one good second later, so at the time of those Oopses,
the root fs wasn't even mounted yet. Maybe the initramfs, but I'm not too sure
either.
[ 4.769188] dracut: dracut-029
[ 4.789227] systemd-udevd[1984]: starting version 204
What is the kernel trying to modprobe? Off what location, exactly?
It can't be /, as that isn't even mounted yet.
The initramfs? Maybe, but this has NO modules packed up whatsoever. I just
double-checked.
root@valery/tmp/foo# ls lib/modules/3.10.1-OSS4.2-dirty
modules.alias modules.alias.bin modules.builtin modules.builtin.bin
modules.dep modules.dep.bin modules.devname modules.order modules.softdep
modules.symbols modules.symbols.bin
The initramfs is solely used for assembling the RAID arrays when booting and
does not include any modules.
I just upgraded to 3.10.1 and am still seeing this.
Interesting issue, isn't it? :)
Mihai
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4506 bytes --]
prev parent reply other threads:[~2013-07-15 3:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-14 23:54 Oops (NULL ptr deref) while loading some module Mihai Moldovan
2013-07-15 3:48 ` Mihai Moldovan [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=51E37115.3030308@ionic.de \
--to=ionic@ionic.de \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox