** This bug is no longer a duplicate of bug 1215513
System locks up, requires hard reset
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Buffer I/O error on device zram0 (possibly
Gathering all related bugs into this one (as most active) also de-
duplicating them from Hang bug which obviously doesn't provide a fix
and probably not related since none of my systems hangs but still report
zram block errors.
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1215513 ***
https://bugs.launchpad.net/bugs/1215513
I'm turning myself from a verbose senior citizen, to an efficient
system admin, with customer support experience.
Attached to this comment is a short extract of /var/log/kern.log, with
only the lines,
*** This bug is a duplicate of bug 1215513 ***
https://bugs.launchpad.net/bugs/1215513
@sea7kenp I agree with you. @henrix says that kernel 3.2.0.54 for Ubuntu
12.04 should be bug free, but I'm still experiencing the error messages
on boot. There have been no lock-ups since the update of the
*** This bug is a duplicate of bug 1215513 ***
https://bugs.launchpad.net/bugs/1215513
Damian, the fdisk /dev/ram0 was a typo, because I was NOT in any
condition to do copy/paste from the system, undergoing the zram0
issue. My actual number is different : 314224, but my situation is
the
*** This bug is a duplicate of bug 1215513 ***
https://bugs.launchpad.net/bugs/1215513
I STRONGLY suggest that this is NOT a duplicate of bug #1215513, as a
fix was distributed that fixes the System Locks Up part, but leaves
this error message.
In my first comment, both on this Bug and on
*** This bug is a duplicate of bug 1215513 ***
https://bugs.launchpad.net/bugs/1215513
I got this, right after apt-get upgrade (plus direct installs of
kernel). The message shows up on bootup. My system has not locked up
yet, which is why I prefer this to bug 1215513.
In my case, the
*** This bug is a duplicate of bug 1215513 ***
https://bugs.launchpad.net/bugs/1215513
I also posted comments in Bug #1215513. I got a workaround there:
service zram-config stop.
I posted a question about what script (probably in the ramdisk portion
of the boot) sets up zram0, so I can
*** This bug is a duplicate of bug 1215513 ***
https://bugs.launchpad.net/bugs/1215513
Something to add to prior comment: Ubuntu 12.0.4 Server, running in
Text mode (at least for now, as I have not brought up FVWM yet, due to
this error. I'm thinking the hard stop in 1215513 is because of
*** This bug is a duplicate of bug 1215513 ***
https://bugs.launchpad.net/bugs/1215513
** This bug has been marked a duplicate of bug 1215513
System locks up, requires hard reset
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am also having this issue on 3.2.0-53-powerpc-smp . Rather than
reverting a commit, there is a patch on LKML:
https://lkml.org/lkml/2013/8/12/399
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The bug seems to affect also
Kubuntu 13.04 - Kernel version 3.8.0-29
Kubuntu 13.04 - Kernel version 3.8.0-30
No problem with 3.8.0-28 kernel...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
A simple workaround is to blacklist the zram module, and update your
initramfs:
1. create a text file /etc/modprobe.d/blacklist-zram.conf:
blacklist zram
2. enter command
update-initramfs -c -k all
After reboot, the zram module will not be loaded anymore.
You can also temporarily unload the
Damian, I believe you refer to 3.2.0-54.82, which is the 12.04 kernel
currently in the -proposed pocket. This kernel should already contain
the fix for this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This seems to be a duplicate of bug #1215513. Could the people running
Raring try the test kernel here:
http://people.canonical.com/~henrix/lp1215513/
(there are 64bits and 32bits kernels)
The faulty commit has been reverted in all the kernels (including
Precise and Quantal).
--
You received
@henrix Is 3.2.0.54 already bug-free (for 12.04)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Buffer I/O error on device zram0 (possibly causing complete machine
lockup)
To
Like Hans, I'm seeing this on 12.04 LTS. linux-image-3.2.0-53-generic-
pae seems to enable zram by default, which results in lots of
scheduling while atomic errors in syslog and occasional lockups
(machine still responds to ping, but not ssh, desktop frozen.)
This seems like a pretty critical
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
Ah, I didn't know about apport-collect, I've added my data as Bug
#1223273, and marked it as a duplicate ..
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
meanwhile: rolling back to kernel 3.2.0.52 - can't wait 'til release of
13.10 - error is critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Buffer I/O error on device zram0
@danmbox: It is. So another fix is just swapoff, right? It doesn't help
with error messages on boot, but should prevent lock-ups when system is
already on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@damian-sawicki: yes, but once such memory errors DO occur, I think your
system is basically compromised; you don't know when it will crash (*)
and you don't know what else gets corrupted before the lock-up (why not
filesystem errors, security etc?). That's why I would cut this at the
root.
(*)
@all:
dmesg | grep zram
[1.820314] zram: module is from the staging directory, the quality is
unknown, you have been warned.
[1.820596] zram: num_devices not specified. Using default: 1
[1.820643] zram: Creating 1 devices ...
[1.864606] Adding 1922976k swap on /dev/zram0.
@all:
after today's updating kernel 3.2.0.52 to 3.2.0.53 there is this message (about
5 times) in syslog:
kernel: [ 30.459194] Buffer I/O error on device zram0, logical block 480744
...
starting the old kernel 3.2.0.52 shows no message like this.
--
You received this bug notification
@all: sorry, i forgot my
DistroRelease: Ubuntu 12.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Buffer I/O error on device zram0 (possibly causing complete machine
lockup)
@danmbox: Still having the issue after dpkg --purge. I'll try your
method with breaking the modules.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Buffer I/O error on device zram0
The way to list your swaps is swapon -s. If zram0 is listed, something
still enables it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Buffer I/O error on device zram0 (possibly
@damian-sawicki: a lot of people have zram due to the zram-config
package, which you must remove with dpkg --purge zram-config (otherwise
it won't go away completely). But in my case zram *still* starts up, and
I can't track what sets it up. I think the easy solution is to break the
zram modules
Bug #1218278 might be a duplicate (though it doesn't talk about lock-
ups). Apparently this is fixed in 3.11, though I don't see how this
helps with raring and linux-lts-raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@damian-sawicki: do you also get lock-ups?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Buffer I/O error on device zram0 (possibly causing complete machine
lockup)
To manage
The same here on Kernel Linux 3.2.0-53-generic-pae
dmesg | grep zram
[1.324402] zram: module is from the staging directory, the quality is
unknown, you have been warned.
[1.324654] zram: num_devices not specified. Using default: 1
[1.324656] zram: Creating 1 devices ...
[
@danmbox Yes. I don't know if they are related to the above logs (often
displayed on boot - btw. for some time I don't have ubuntu logo and
animation on boot, but just text Ubuntu 12.04 and 4 sparkling dots),
but both - errors about zram0 and lock-ups - started recently.
--
You received this bug
@variona So, no lock-ups after downgrading? You should also test the
NEWER kernel WITHOUT enabling zram and see if the crashes still occur.
I've run 3.8.0-29 WITHOUT zram for almost a day (not quite enough to
give it a clean pass)
--
You received this bug notification because you are a member of
After multiple machine lock downs (no way to ping it) switching back to
3.5.0-37-generic results in:
dmesg | grep zram
[0.829615] zram: module is from the staging directory, the quality is
unknown, you have been warned.
[0.829907] zram: num_devices not specified. Using default: 1
[
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-lts-raring (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
I also experienced the complete machine lock up.
dmesg | grep zram
[0.842160] zram: module is from the staging directory, the quality is
unknown, you have been warned.
[0.842454] zram: num_devices not specified. Using default: 1
[0.842457] zram: Creating 1 devices ...
[1.015211]
Affects me with 3.5.0-39-generic Kernel on an AMD64X2 machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Buffer I/O error on device zram0 (possibly causing complete machine
38 matches
Mail list logo
