*** This bug is a duplicate of bug 1246664 ***
https://bugs.launchpad.net/bugs/1246664
[2.440692] zram: module is from the staging directory, the quality is
unknown, you have been warned.
[2.441048] zram: num_devices not specified. Using default: 1
[2.441050] zram: Creating 1 devi
*** This bug is a duplicate of bug 1246664 ***
https://bugs.launchpad.net/bugs/1246664
I dist-upgraded mu ubuntu 12.04 LTS this morning and after reboot I got:
[ 14.666280] zram: module is from the staging directory, the quality is
unknown, you have been warned.
[ 14.667040] zram: Creatin
*** This bug is a duplicate of bug 1246664 ***
https://bugs.launchpad.net/bugs/1246664
Made this a dup of bug 1246664 since there is some progress there.
** This bug has been marked a duplicate of bug 1246664
"Buffer I/O error on device zram0, logical block 515067"
--
You received this b
@oibaf I don't know, because I didn't use this computer for a while and
upgraded directly from -54 to -56.
I reported the bug here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1246664
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
@Damian: is this a regression of -56? Do -55 works fine? If so you may
want to report it here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242901
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
For some reason I also cannot do it. Maybe you could open a new bug?
--
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
Title:
Buffer I/O error on device zram0
Status in “linux” pac
@oibaf I'm afraid I don't have necessary permissions to change the
status. Could you do it for me?
--
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
Title:
Buffer I/O error on devic
You may want to reopen "linux (Ubuntu)" if it's not fixed for you. I
tried myself on a friend machine 3.2.0-55 and the message didn't show
up.
--
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
@oibaf I've just installed the newest updates and now have kernel
3.2.0-56-generic-pae (12.04 32-bit), but the error message still
appears. I haven't used this computer recently, so it is hard to tell if
there is a problem with lock-ups. But, as I said before, after updating
to 3.2.0-54 I didn't ex
** Changed in: linux-lts-raring (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
After some days with the updated 3.8 kernel I never see this issue
anymore.
Upstream 3.2.52 reverted a patch already reverted on 3.2.0-54:
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.2.52
I'll close this if no one experience other problems.
--
You received this bug notification bec
There is a new raring kernel (3.8.0-32) with a zram fix (see bug
1233227). With it the "Buffer I/O error on device zram0" warning is no
longer shown.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
Hence why I said I/O errors on *write*. If the block dev layer reports
an error to the VM on page-out, it knows the data hasn't been correctly
written.
I'm not sure zram actually allocates the whole amount of memory it's
configured to use, initially:
steved@xubuntu:~$ free
total
Mel, the reason I do NOT believe this is a duplicate of # 1215513 is
that many get error messages (including I/O errors in some cases)
WITHOUT a hang. But any time I see I/O error on any disk, whether
"hardware, ram or simulated [i.e. network]", there's a chance of data
corruption, even without cr
Been a long time since I looked at the relevant bits of the kernel
source, but errors when _writing_ to swap devices should be quite
manageble, I would have thought - simply mark the block/page as bad and
go looking for another free location. It'll be _read_ errors that cause
problems!
Some info h
IMO, this bug *is* a duplicate of #1215513. The real problem is that the
zram kernel module creates a block device with a bad sector at the end.
When you try to swap on it, anything can happen, from system lockdowns
to program crashes to nothing (e.g., if you have so much RAM you never
get to use t
See comment #47.
--
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
Title:
Buffer I/O error on device zram0
Status in “linux” package in Ubuntu:
Confirmed
Status in “linux-lts-rar
** Summary changed:
- Buffer I/O error on device zram0 (possibly causing complete machine lockup)
+ Buffer I/O error on device zram0
--
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
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 K
** 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Buffer I/O error on device zram0
*** 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, r
*** 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
t
*** 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 k
*** 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 B
*** 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 pos
*** 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 Logic
*** 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 Kernel
Packages, which is subscribed to linu
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
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 mod
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
@henrix Is 3.2.0.54 already bug-free (for 12.04)?
--
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
Title:
Buffer I/O error on device zram0 (possibly causing complete machine
lock
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
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1217189
Title:
Buffer I/O error on device
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
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 Kernel
Packages, which is subscribed to linux in Ubun
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
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 pr
39 matches
Mail list logo
