From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 14708] Option remap63 for OnTrack diskmanager not work - kernel panic, unable to mount root filesystem
Date: Tue, 1 Dec 2009 00:28:58 GMT [thread overview]
Message-ID: <200912010028.nB10Swwf021262@demeter.kernel.org> (raw)
In-Reply-To: <bug-14708-11633@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=14708
--- Comment #1 from David S. Miller <davem@davemloft.net> 2009-12-01 00:28:58 ---
From: bugzilla-daemon@bugzilla.kernel.org
Date: Tue, 1 Dec 2009 00:22:58 GMT
> http://bugzilla.kernel.org/show_bug.cgi?id=14708
>
> Summary: Option remap63 for OnTrack diskmanager not work -
> kernel panic, unable to mount root filesystem
This was intentionally removed see:
commit d708c40da83a86551556999e924e27fdc43dad71
Author: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Date: Sat Mar 22 16:40:22 2008 +0100
ide: mark "hdx=remap" and "hdx=remap63" kernel parameters as obsoleted
Mark "hdx=remap" and "hdx=remap63" kernel parameters as obsoleted
(they are layering violation and should be dealt with in the same
way as done by libata - device-mapper should be used instead).
Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-12-01 0:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 0:22 [Bug 14708] New: Option remap63 for OnTrack diskmanager not work - kernel panic, unable to mount root filesystem bugzilla-daemon
2009-12-01 0:28 ` David Miller
2009-12-01 0:28 ` bugzilla-daemon [this message]
[not found] <bug-14708-11633@https.bugzilla.kernel.org/>
2010-11-14 23:14 ` [Bug 14708] " bugzilla-daemon
2012-06-18 12:51 ` bugzilla-daemon
2012-06-18 12:51 ` 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=200912010028.nB10Swwf021262@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).