I had the same problem but I installed the 3.8.36.41 and now the
computer is not freeze anymore, however my computer now is power off...
yes is power off when the computer is under heavy ram usage. I disabled
zram (sudo service zram-config stop) and the computer not power off in
the same scenario.
Posts #51 and #53 are wrong: this bug is NOT FIXED in either 3.2.0-54.82
or 3.8.0-31.46 from the 12.04 (precise) repositories. There might be
something fixed about zram in there (as suggested by the changelog), but
the last sector of /dev/zram0 is still bad (as reported in #43), and
this will lead
For 1a, also uninstall zram-config if present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
System locks up, requires hard reset
To manage notifications about this bug go to:
I stand corrected - maybe. I wrote a program that allocates, sets, and
moves around more memory than my RAM. I added the zram0 as a swap, with
the bad sector included ('mkswap' without '-c'), and with higher
priority than the disk swap. I ran the program once only, because it
takes half an hour
This bug was fixed in the package linux - 3.2.0-54.82
---
linux (3.2.0-54.82) precise; urgency=low
[Steve Conklin]
* Release Tracking Bug
- LP: #1223490
[ Upstream Kernel Changes ]
* Revert zram: use zram-lock to protect zram_free_page() in swap free
notify path
This bug was fixed in the package linux - 3.5.0-41.64
---
linux (3.5.0-41.64) quantal; urgency=low
[Brad Figg]
* Release Tracking Bug
- LP: #1223451
[ Upstream Kernel Changes ]
* kernel-doc: bugfix - multi-line macros
- LP: #1223920
* Revert zram: use zram-lock
This bug was fixed in the package linux - 3.8.0-31.46
---
linux (3.8.0-31.46) raring; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1223406
* UBUNTU: [Config] KUSER_HELPERS=y for armhf
[ Upstream Kernel Changes ]
* Revert cpuidle: Quickly notice prediction
here is solution:
run mkswap with -c
mkswap -c /dev/zram0
(you can fix this in package zram-config, if you want :)
cat /etc/init/zram-config.conf | grep mkswap
mkswap /dev/zram${DEVNUMBER}
you need to change this line to:
mkswap -c /dev/zram${DEVNUMBER}
Explanation:
See:
modprobe
And some explanation (I use another bugreports)
Just comment here, #25 :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215513/comments/25
...
[ 1.659040] Adding 1025396k swap on /dev/zram0. Priority:100 extents:1
across:1025396k SS
[ 20.719906] Buffer I/O error on device zram0, logical
here is solution:
run mkswap with -c
mkswap -c /dev/zram0
(you can fix this in package zram-config, if you want :)
cat /etc/init/zram-config.conf | grep mkswap
mkswap /dev/zram${DEVNUMBER}
you need to change this line to:
mkswap -c /dev/zram${DEVNUMBER}
Explanation:
See:
modprobe
I love cats and, especially Kittens, but (Kitten_Geek), could you PLEASE
give an executive summary of your last three posts, in Command Line
System Admin language (as opposed to Kernel Hacker language)? Thanks
most Kindly! Kenneth Parker, Seattle, WA
--
You received this bug notification
Sorry, but what is the line length, to avoid word wrap?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
System locks up, requires hard reset
To manage notifications about this bug go
kitten_geek, would it help if I [figuratively] stroke your back? :-)
One line of a summary I recently published on # 1217189:
zram: There is little point creating a zram of greater than twice the
size of
memory since we expect a 2:1 compression ratio. Note that zram uses
about
I'm sorry, - my last posts duplicates; can somebody delete at least
comment 45? (it will be a good idea, to make possible to edit or delete
posts...)
Mr. Kennet Parker,
It seems that the issue might be in the initial guess at the size of
the Ram Disk, right?
I'm not sure, I am not
Sorry again! some typo: before swapon. And change in /etc/init/zram-
config.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
System locks up, requires hard reset
To manage
** Tags removed: verification-needed-precise verification-needed-quantal
** Tags added: verification-done-precise verification-done-quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
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
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 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
Dan,
My issue is with an old, but supposedly supported LTS release,
12.0.4 Server. SINCE it's a Server release, it assumes I know what
I'm doing (even to only setting up in Text mode, and letting me only
apt-get install what I ACTUALLY need to install, which means a working
X Server and FVWM.
Sorry, Dan, I misunderstood one part of your response to me. I never
had zram-config, until I did apt-get install zram-config, after
reading a work-around, earlier in the forum, by dac922.
zram-config did not fully configure (so is an incomplete install on
the Apt system. But, it's a MOST
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 different
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
** Tags removed: verification-raring-done
** Tags added: verification-done-raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
System locks up, requires hard reset
To manage
No locks after 3 days. Tagged as verification-raring-done.
** Tags removed: verification-needed-raring
** Tags added: verification-raring-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Hello Dan,
Thank you for your response. I find it somewhat amusing, since I do not
use zram0, or the zram system AT ALL on my server. I manually partition
the drive, (pretty much since I first started using Linux in the early
to mid 1990's), and manually configure a SWAP partition on it (using
** Branch linked: lp:ubuntu/precise-proposed/linux-ti-omap4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
System locks up, requires hard reset
To manage notifications about this bug
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
I've lost track of which bugs cause what here, but *not* looking good on
precise so far:
steved@xubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04.3 LTS
Release:12.04
Codename: precise
steved@xubuntu:~$ uname -a
Linux xubuntu
I also see that log messages on raring 64 bits, but no locks so far
since yesterday.
Sep 17 10:24:22 fede-desktop kernel: [ 24.899285] zram: module is from the
staging directory, the quality is unknown, you have been warned.
Sep 17 10:24:22 fede-desktop kernel: [ 24.899922] zram: Creating 2
When entering service zram-config stop, ubuntu said it couldn't find
zram-config.
I entered apt-get install zram-config under root. As part of its
install, it tried to run itself and got the above error messages (10 of
the buffer i/o error on device zram0, logical block 314223) and then
Thank you to dac922 for the suggestion service zram-config stop. I
believe this will be a great interim work around for me, allowing me to
use FVWM (which I like, due to the 9 desktops).
I still want to know about what script to edit, to lower the size of
zram0, so that it doesn't try to
Looks like a calculation error in /etc/init/zram-config.conf. How do
I find an earlier version of this (i.e. in kernel *.*.27 or before)?
Note that the /etc file will probably only be there if you apt-get
install zram-config.
To the person who released a fix: Is a fix to /etc/init/zram-
I'm running Ubuntu Server 12.0.4, rarely upgraded, due to sensitive
work. I did apt-get upgrade (plus direct apt-get install of kernel
packages, that are held back on upgrade).
I get the message buffer i/o error on device zram0, logical block
314223.
Due to this error, I'm leaving it in text
Kenneth, please read the previous commits. The error you see is fixed
upstream with this patch:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
stable.git/commit/?id=75c7caf5a052ffd8db3312fa7864ee2d142890c4
Luis, Brad:
I tested the kernel 3.8.0-31.46 in raring-proposed and see no
dac922,
First off, my Ubuntu 12.0.4 LTS Server was just upgraded to Kernel
vmlinuz-3.2.0-53-generic-pae. But I see in your post that you're
working on kernel 3.8.0-31.46. Am I supposed to upgrade 12.0.4, running
in production to kernel 3.8? Yikes!
In the last paragraph of your comment, you
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
** Branch linked: lp:ubuntu/quantal-proposed/linux-ti-omap4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
System locks up, requires hard reset
To manage notifications about this bug
See also https://lkml.org/lkml/2013/8/13/22 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
System locks up, requires hard reset
To manage notifications about this bug go to:
According to LKML discussion this was a regression of zram: avoid access
beyond the zram device, not zram: use zram-lock to protect zram_free_page()
in swap free notify path, reverted in Ubuntu 3.2.0-54.82:
https://lkml.org/lkml/2013/8/13/270
Also the fix applied in other trees was this:
oibaf, please see my comment #9 and #11. The regression you mentioned is
an additional one and was not the root cause for this bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
Indeed my problem was not the lock ups but just the warnings. But if
they are different problems bug #1217189 should not be a dup of this
one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Oibaf, dac922: thank you for your comments. Since bug #1217189 also
refers to possibly causing complete machine lockup (see title) I
decided to set it as a dup.
Anyway, I was actually convinced the fix pointed in comment #13 was
already in Raring but looks like I was wrong -- its in Quantal
Thanks, I was experiencing the problem on precise 3.2.0-54.82 where it
should also be applied. zram changes (including the one triggering the
problem) got backported to 3.2 series in 3.2.49:
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.2.49
This fix should eventully be applied
I sent a mail to Greg Kroah-Hartman asking to apply it in 3.2 series
also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
System locks up, requires hard reset
To manage notifications
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-raring-
needed' to 'verification-raring-done'.
If verification is not done by one week from today,
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-precise-
needed' to 'verification-precise-done'.
If verification is not done by one week from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-quantal-
needed' to 'verification-quantal-done'.
If verification is not done by one week from
A week seems like an extremely short time, especially for ALL releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
System locks up, requires hard reset
To manage notifications
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Quantal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Raring)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Saucy)
dac922, thanks a lot for your analysis. I've uploaded a test kernel
here:
http://people.canonical.com/~henrix/lp1215513/
(there are 2 directories, one for 32bits and another for 64bits)
Could the original bug reporter please also test it and report back?
This is a Raring kernel reverting
I have the same bug with two computers, both running with zram. 3.8.0-27
works fine, but 3.8.0-29 freezes from time to time (especially on high
RAM usage).
When doing service zram-config stop, I see no further freezes. Also, I found
a patch in linux upstream that could be related to this issue:
Just tried with rebuilding the zram driver with the upstream patch.
Either I have do something wrong, or the patch doesn't help. My second
try was to copy the unmodified zram driver from 3.8.0-27 to 3.8.0-29.
This seems to work.
--
You received this bug notification because you are a member of
Second try: I rebuild the zram driver with upstream patch and reverting this
patch:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;a=commitdiff;h=f56c0e44628257f97063089eb865d5eb2dfdd642
No freeze since a hour with heavy RAM usage.
--
You received this bug notification because you are a
I think zram is the cause. I had zram in both machines. I'm now running
3.8.0-29 without zram. No issues so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
System locks up,
After first day working without zram, no lock ups. Still running
3.8.0-29.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
System locks up, requires hard reset
To manage notifications
** Attachment added: lspci-vnvn.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215513/+attachment/3782800/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
The 3.8.0-30.43 kernel is now available in the -proposed repository.
Would it be possible for you to test this latest kernel and post back if
it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed.
Thank you in advance!
**
Got another lock up on 3.8.0-29.
Now I'm running 3.8.0-30-generic #43-Ubuntu SMP Wed Aug 21 21:07:22 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux.
I'll report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It locked again right after hitting enter in the shutdown dialog. The
screen stayed freezed for at least 20 minutes until i reset it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1215513
Title:
60 matches
Mail list logo
