kernel-packages team mailing list archive

[Kenneth Parker <1215513@xxxxxxxxxxxxxxxxxx>]

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
file type 82).  There never was a swap partition on zram0.  My concern
was finding the buffer I/O errors on my console for the first time (and
then seeing them repeated on my text root console (the only thing I
trusted, running on what appeared to be a badly broken Server).

In my first comment, I responded to the error message by entering "fdisk
/dev/ram0", followed by "p", which showed it to never being partitioned,
or anything (like a SWAP partition) being defined.  So it LOOKS like I
was never in danger of bug #1215513, but only experiencing the messages,
noted in But #1217189.  I'll add a message on that Bug, saying that,
some way or another, the error messages still appear after "fix" of
#1215513, which can CERTAINLY alarm production Linux administrators
anywhere, and cause loss of money in any case where the Server is
anything but something assisting non-profit volunteer work, where they
can be told they need to be patient and wait for their services.
(Actually, due to an early message by dac922, I was able to disable zram
services on a system that has no intention of using them).

Obviously, what happened was that the Kernel 3.8 work, IMPLEMENTING
zram0 swap was "back-ported" to the 3.2 Kernel tree, somewhere <=
vmlinuz-3.2.0-53-generic-pae!!!   :-O

Remember, my system is Ubuntu 12.0.4 LTS Server, which, in my opinion is
not in any condition for "stray zram swap" creation!  Fortunately,
somebody ported the package zram-config to 12.0.4, allowing me to get
it, which, in effect PERMANENTLY DISABLES the zram0 processes, because
they fail, during the install of zram-config, allowing "apt-get upgrade"
to state that it was not successful in the "install" of this package.

So I suggest that somebody on this forum (again, I'm too busy
administering Linux to normally submit fixes!) put some of this text in
some "FAQ file" somewhere, IN CASE somebody ELSE with Ubuntu 12.0.4
complains about  the Bug #1217189 Buffer I/O Error Message.

Forgive my dry humor in this post.  As a Linux admin, I'm trained to
"roll with the punches" and to consider the humor of life on Planet
Earth (and, forgive me for adding) the political system in the USA!!!
:-)

And this post will now be "cross posted" to  Bug #1217189 with a STRONG
suggestion that it NOT BE CLOSED as long as people are going to complain
about the Buffer I/O Error messages.

Thank you and best regards,

Kenneth Parker, Seattle, WA

--  I'm a Troubleshooter.  I look for Trouble and Shoot It!    :-)

-- 
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 “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Precise:
  Fix Committed
Status in “linux” source package in Quantal:
  Fix Committed
Status in “linux” source package in Raring:
  Fix Committed
Status in “linux” source package in Saucy:
  Fix Released

Bug description:
  Since I started using 3.8.0-29 I experienced system lock ups at random
  times. First one was while running Virtualbox (windows guest) but
  later have been without virtualbox running for example while shutting
  down or while reading a webpage.

  I could not find any relevant log, but I'd post any log file
  considered useful.

  This has hapened in 2 different machines (the one im reporting from is
  intel with intel graphics and the other is AMD with radeon graphics).
  Both 64 bits.

  Up until 3.8.0-27 inclusive I had not had a lockup in years in any of
  those machines. I have been running Ubuntu 64 bit since at least 2008
  in one of them.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-29-generic 3.8.0-29.42
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  fede       1829 F.... pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
  CurrentDmesg:
   
  Date: Thu Aug 22 12:49:35 2013
  HibernationDevice: RESUME=UUID=ee5b2280-eed3-41e2-8675-103fbdd703d1
  InstallationDate: Installed on 2012-12-03 (261 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IwConfig:
   eth0      no wireless extensions.
   
   lo        no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MarkForUpload: True
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=0d34a8a5-2002-47e8-9128-a35623612ec1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-29-generic N/A
   linux-backports-modules-3.8.0-29-generic  N/A
   linux-firmware                            1.106
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: Upgraded to raring on 2013-04-25 (118 days ago)
  dmi.bios.date: 09/11/2006
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: TS94610J.86A.0047.2006.0911.0110
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: D946GZIS
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD66165-501
  dmi.chassis.type: 2
  dmi.modalias: dmi:bvnIntelCorp.:bvrTS94610J.86A.0047.2006.0911.0110:bd09/11/2006:svn:pn:pvr:rvnIntelCorporation:rnD946GZIS:rvrAAD66165-501:cvn:ct2:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1215513/+subscriptions