From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 111151] [pata_amd][pata_acpi] Internal base address register error prevents initialization of PATA drive
Date: Sat, 23 Jan 2016 12:15:27 +0000 [thread overview]
Message-ID: <bug-111151-11633-RvAzmKlSKz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-111151-11633@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=111151
--- Comment #5 from Andreas E <andi3@gmx.net> ---
OK, I will.
Let me think...when booting FAILED, it stopped at the initramfs prompt.
I'm not sure if initramfs supports lspci, but I can try.
Also thought of forcing the system into a certain runlevel in both cases.
The Ubuntus have a very crazy "trick" to stop booting in mid-air: have an
additional drive defined in /etc/fstab which you physically disconnect.
Ubuntu will then issue the well-known "A starting job has been running for...1m
30s" and eventually give up, sardonically "welcoming" you to emergency mode.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-01-23 12:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 19:55 [Bug 111151] New: [pata_amd][pata_acpi] Internal base address register error prevents initialization of PATA drive bugzilla-daemon
2016-01-22 20:57 ` [Bug 111151] " bugzilla-daemon
2016-01-23 1:17 ` bugzilla-daemon
2016-01-23 1:38 ` bugzilla-daemon
2016-01-23 11:43 ` bugzilla-daemon
2016-01-23 12:15 ` bugzilla-daemon [this message]
2016-01-23 17:09 ` bugzilla-daemon
2016-01-23 18:58 ` bugzilla-daemon
2016-01-23 21:09 ` bugzilla-daemon
2016-01-23 21:13 ` bugzilla-daemon
2016-01-23 23:09 ` bugzilla-daemon
2016-01-23 23:29 ` bugzilla-daemon
2016-02-04 22:43 ` bugzilla-daemon
2016-02-04 22:44 ` 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-111151-11633-RvAzmKlSKz@https.bugzilla.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 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.