All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 61601] rootflags=noatime causes kernel panic when booting without initrd.
Date: Mon, 11 Aug 2014 04:17:44 +0000	[thread overview]
Message-ID: <bug-61601-13602-VNI8kZB2Zp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-61601-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=61601

--- Comment #9 from xerofoify@gmail.com ---
I need you to check if your system is running dual  initrd/ramload setup,
as the lines I am tracing to our ,
520         if (rd_doload==2) {
521             if (rd_load_disk(1)) {
522                 ROOT_DEV = Root_RAM1;
523                 root_device_name = NULL;
524             }
And you may be loading the wrong ram disk and this needs to be changed from 1
to 0.
Regards Nick

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2014-08-11  4:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-18 12:05 [Bug 61601] New: rootflags=noatime causes kernel panic when booting without initrd bugzilla-daemon
2013-11-13 14:50 ` [Bug 61601] " bugzilla-daemon
2013-11-15 19:39 ` bugzilla-daemon
2014-03-30 16:06 ` bugzilla-daemon
2014-04-07 15:27 ` bugzilla-daemon
2014-04-11 21:25 ` bugzilla-daemon
2014-06-24 18:41 ` bugzilla-daemon
2014-08-11  3:08 ` bugzilla-daemon
2014-08-11  3:09 ` bugzilla-daemon
2014-08-11  4:17 ` bugzilla-daemon [this message]
2014-08-11  5:06 ` bugzilla-daemon
2014-08-11  5:32 ` bugzilla-daemon
2014-08-11  7:04 ` bugzilla-daemon
2014-08-11 14:24 ` bugzilla-daemon
2014-08-12  5:02 ` bugzilla-daemon
2015-06-09  9:52 ` bugzilla-daemon
2015-06-09 21:35 ` bugzilla-daemon
2015-06-10 16:04 ` bugzilla-daemon
2016-07-22 14:05 ` bugzilla-daemon
2025-03-31 16:20 ` bugzilla-daemon
2025-04-03 10:14 ` bugzilla-daemon

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=bug-61601-13602-VNI8kZB2Zp@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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 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.