From: Russell Coker <russell@coker.com.au>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 3.16.0 Debian kernel hang
Date: Sat, 5 Dec 2015 01:26:09 +1100 [thread overview]
Message-ID: <201512050126.09510.russell@coker.com.au> (raw)
In-Reply-To: <56619AC3.5000309@gmail.com>
On Sat, 5 Dec 2015 12:53:07 AM Austin S Hemmelgarn wrote:
> > The only reason I'm not running Unstable kernels on my Debian systems is
> > because I run some Xen servers and upgrading Xen is problemmatic. Linode
> > is moving from Xen to KVM so I guess I should consider doing the
> > same. If I migrate my Xen servers to KVM I can use newer kernels with
> > less risk.
>
> That's interesting, that must be something with how they do kernel
> development in Debian, because I've never had any issues upgrading
> either Xen or Linux on any of the systems I've run Xen on, and I
> directly track mainline (with a small number of patches) for Linux, and
> stay relatively close to mainline with Xen (Gentoo doesn't have all that
> many patches on top of the regular release for Xen, aside from XSA
> patches).
I don't think that Debian does anything wrong in this regard. It's just that
my experience of Xen is that it is fragile at the best of times. The fact
that Red Hat packaged the Xen kernel in the Linux kernel package is a major
indication of Xen problems IMHO, the concept of Xen is that it shouldn't be
tied to a Linux kernel.
If you haven't had Xen issues then I think you have been lucky.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2015-12-04 14:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 10:00 3.16.0 Debian kernel hang Russell Coker
2015-12-04 13:08 ` Austin S Hemmelgarn
2015-12-04 13:42 ` Russell Coker
2015-12-04 13:53 ` Austin S Hemmelgarn
2015-12-04 14:26 ` Russell Coker [this message]
2015-12-04 16:13 ` Austin S Hemmelgarn
2015-12-05 12:44 ` Duncan
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=201512050126.09510.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@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