[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#800154: marked as done (linux-source: custom built embedded kernel with slob-allocation runs too unstable, boot-problems)

Your message dated Sun, 27 Sep 2015 18:27:46 +0100
with message-id <1443374866.2517.1.camel@decadent.org.uk>
and subject line Re: Bug#800154: linux-source: custom built embedded kernel with slob-allocation runs too unstable, boot-problems
has caused the Debian Bug report #800154,
regarding linux-source: custom built embedded kernel with slob-allocation runs too unstable, boot-problems
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
800154: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800154
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Package: linux-source
Version: 3.16+63
Severity: normal

Dear Maintainer,

I have been using the custom aedl-kernel [config-3.16.7-ckt11-aedl.xz] on my dualcore
thin-client and tried to continue using it on my new PC, but it is not really workable.
It's behaving in an unstable way, for example when copying the contents of one compressed
BTRFS-partition to another one, it panicked. More often that, there are boot-problems,
especially upon a kernel-panic reboot hangs almost every time, it may be connected with
the LZO-compressed root-partition, but that normally works.
I rebuilt the kernel, leaving the
embedded-feature away and using slub instead [config-3.16.7-ckt11-adll.xz], it seems to be
doing well so far. I also compared that with the stock-kernel using phoronix-test-metrics,
but at least in the complex system test, there is not very much gain. This may be due to
the test being a non-interactive server-test mostly. Personally and subjectively I prefer
custom built AMD low-latency-kernels on the desktop, because, they make the system feel
more responsive.

The original installation-report was posted there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800127



- -- System Information:
Debian Release: 8.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.7-ckt11-aedl (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-source depends on:
ii  linux-source-3.16  3.16.7-ckt11-1+deb8u4

linux-source recommends no packages.

linux-source suggests no packages.

- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlYH9KQACgkQ5+rBHyUt5wt7OgCgkG15BhgxyaBDd+OVb+FVNvg4
ITQAoIiv+9GlrKGdp+sa/z+ZXdiaTMbx
=qBSU
-----END PGP SIGNATURE-----

Attachment: dmsg.txt.xz
Description: application/xz

Attachment: config-3.16.7-ckt11-adll.xz
Description: application/xz

Attachment: config-3.16.7-ckt11-aedl.xz
Description: application/xz


--- End Message ---
--- Begin Message --- 
Then don't use CONFIG_SLOB.  We're certainly not going to do anything
to fix it.

Ben.

-- 
Ben Hutchings
I say we take off; nuke the site from orbit.  It's the only way to be sure.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: