Super, I was just looking for a way to build kernels in a Docker
container.
Maybe the Docker image could be modified to build dwarves for itself at
some point.
I think you can request more space for a PPA from launchpad.
--
You received this bug notification because you are a member of Kernel
P
Still seeing this spurious libc 2.33 dependency (I *assume* it's not the
kernel people who decide to change their libc policy in the middle of a
release series -- so it's spurious) in 5.10.35.
Are the Ubuntu / Canonical people notified? I'm not sure who takes care
of this "Mainline PPA" (which doe
It would be unfortunate for the "LTS" kernel version to not be
installable on LTS Ubuntu.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1926938
Title:
Recent mainline packages are built
Sorry, this is on Trusty amd64, with linux-lowlatency-lts-utopic
3.16.0.31.24
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-raring in Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to validate module signatur
I'm seeing this with linux-lowlatency-lts-utopic...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-raring in Ubuntu.
https://bugs.launchpad.net/bugs/1253155
Title:
Failure to validate module signature at boot time
Status in
In my PPA (https://launchpad.net/~danmbox/+archive/ppa) I've tried
backporting ocl-icd_2.0.2-1ubuntu1 (after backporting khronos-opencl-
headers), but it's not compilable (weird warnings-turned-into-errors)
--
You received this bug notification because you are a member of Kernel
Packages, which i
Brad, can you comment on the problems I've shown for 3.2 and 3.8 on
precise -lts kernels? Do you want to push through those kernels and then
have to deal with separate bugs. I know there's a lot of noise in this
thread, but there were some relevant tests and errors.
--
You received this bug notif
With linux-image-3.5.0-41-generic = 3.5.0-41.64~precise1 there are no
Buffer I/O errors, either with mkswap or mkfs.ext2
With linux-image-3.2.0-54-generic = 3.2.0-54.82 the errors are the same
as in linux-image-3.8.0-31-generic = 3.8.0-31.46~precise1
So the lts-quantal image is good, the others a
I've tested 3.8.0-31-generic (linux-image-3.8.0-31-generic =
3.8.0-31.46~precise1). To the admins: when asking us to test "the latest
in -proposed", please tell us which package and which version. It makes
it easier to interpret the record in the future, when the "latest in
proposed" may be differe
@Kenneth Parker: if your problem is that zram shows up EVEN AFTER dpkg
--purge zram-config, please **file a separate bug**. Note that "service
zram-config stop" stops zram after the system is up, which means it has
already potentially damaged your system. What you want is for the zram
module to nev
With 3.8.0-31-lowlatency, try this if you're willing to reboot:
rmmod zram; modprobe zram; echo -n 6710 > /sys/block/zram0/disksize;
mkswap /dev/zram0; dmesg -T | tail
It will bring you into a state where you can't rmmod zram (!).
# rmmod zram
ERROR: Removing 'zram': Device or resource busy
Kenneth, zram-config is a red herring. Even if you purge it completely
and set up zram manually,
modprobe zram
echo -n 67108864 > /sys/block/zram/size
mkswap /dev/zram0
swapon /dev/zram0
You still get the error messages and eventually the lock-ups. This is
not a script problem, it's a kernel prob
Since several bugs with much more details were merged into this one, the
most likely early warning of zram problems are messages like
Buffer I/O error on device zram0, logical block 257912 [repeated X
times]
You get those right after modprobing / formatting zram. If you don't see
those with the n
A week seems like an extremely short time, especially for ALL releases.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
System locks up, requires hard reset
Status in “lin
*** This bug is a duplicate of bug 1217189 ***
https://bugs.launchpad.net/bugs/1217189
I'm marking this as a duplicate of bug #1217189. I don't find @timg-
tpi's comment very reassuring. This is a critical bug for the LTS
release.
** This bug has been marked a duplicate of bug 1217189
Buff
apport information
** Attachment added: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812999/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
This bug also occurs on linux-lts-quantal, I think (I remember booting
to a lts-quantal kernel after seeing the raring bug). There was a
backport to zram on both branches that is causing this.
Note that in Bug #1218278, Tim Gardner (timg-tpi) wrote at #19: "There
will be a linux-lts-saucy shortly
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3813002/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3813004/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1217189
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3813003/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "Card0.Codecs.codec.1.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812994/+files/Card0.Codecs.codec.1.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
apport information
** Attachment added: "Card1.Amixer.values.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812995/+files/Card1.Amixer.values.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812993/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812996/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812991/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "AplayDevices.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812989/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3813001/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812998/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1217189
apport information
** Attachment added: "ArecordDevices.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812990/+files/ArecordDevices.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812997/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1217189
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3813000/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Card0.Amixer.values.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812992/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
apport information
** Attachment added: "AlsaDevices.txt"
https://bugs.launchpad.net/bugs/1217189/+attachment/3812988/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Tags added: apport-collected staging
** Description changed:
This is on linux-image-generic-lts-raring (which I recently upgraded to
3.8.0-29; the problem didn't occur before upgrading AFAIR)
I see this junk in my dmesg when creating / formatting a zram swap, and
@timg-tpi: Have you seen bug #1217189, involving machine lock-ups due to
this error, probably triggered after heavy swapping?
Do you have any suggestions as to why regular raring users seem
unaffected by this bug (or at least they're not complaining)?
--
You received this bug notification becaus
This might explain the reasons
https://lkml.org/lkml/2013/8/13/22
(assuming this was a change backported to 3.8 and 3.5 by Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1218278
Changed to Confirmed as per @jsalisbury's instructions, since
@konrad.hofer forgot to. In any case, I doubt raring (and thus linux-
lts-raring on precise) will upgrade to 3.11.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
might be related to bug #1217189 which raises the possibility of hard
machine LOCK-UPS due to zram errors. I've had several such lock-ups on
precise after the most recent linux-lts-raring updates (and none before
that) that seemed to go away after disabling zram.
** Changed in: linux (Ubuntu)
38 matches
Mail list logo
