From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 206405] kernel crash during boot debian server on qemu+kvm
Date: Thu, 20 Feb 2020 20:34:49 +0000 [thread overview]
Message-ID: <bug-206405-11633-gHUzPMarTb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206405-11633@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206405
--- Comment #5 from anthony (antdev66@gmail.com) ---
(In reply to b.zolnierkie from comment #4)
> On 2/19/20 10:25 PM, bugzilla-daemon@bugzilla.kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=206405
> >
> > --- Comment #3 from anthony (antdev66@gmail.com) ---
> > same problem in version 5.5.5
>
> Hi,
>
> Please check v5.6-rc2 and if it doesn't help please try to do
> bisection between v5.4 and v5.5 kernel versions as described in:
>
> Documentation/admin-guide/bug-bisect.rst
>
> Also could you please explain what prevents you from migration to
> libata drivers (CONFIG_ATA) from the IDE subsystem (CONFIG_IDE, it
> has been deprecated many years ago and is scheduled for removal)?
>
> Best regards,
> --
> Bartlomiej Zolnierkiewicz
> Samsung R&D Institute Poland
> Samsung Electronics
Hello,
I have tested version 5.6-rc2 but I get the same result.
As for IDE drivers, they were enabled due to previous configurations.
However, following your suggestion, I recompiled the 5.5.5 kernel with
CONFIG_IDE disabled and the problem no longer occurs.
This does not explain the reason for the crash, but I solved the problem.
Thanks,
Antonio
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2020-02-20 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 15:54 [Bug 206405] New: kernel crash during boot debian server on qemu+kvm bugzilla-daemon
2020-02-04 21:21 ` [Bug 206405] " bugzilla-daemon
2020-02-11 20:56 ` bugzilla-daemon
2020-02-19 21:25 ` bugzilla-daemon
2020-02-20 13:30 ` Bartlomiej Zolnierkiewicz
2020-02-20 13:30 ` bugzilla-daemon
2020-02-20 20:34 ` bugzilla-daemon [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=bug-206405-11633-gHUzPMarTb@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 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).