kernel-packages team mailing list archive

[Kenneth Parker <1215513@xxxxxxxxxxxxxxxxxx>]

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.  (Be honest, folks!  How many of you have run that in
the last decade?  LOL!)

My situation is different than yours, as I'm running a late, "security
fix" for Kernel 3.2.  As such, there IS NO software, to run zram0, just
some sort of boot code, probably in the Kernel.  So /dev/zram0 was "sort
of" set up, as it was "defined", but not configured.  So bug #1217189
MUST be re-opened, for the older Kernels, and because it adversely
affects a LTS release!

I posted a message on 1217189, but here is a capsule summary:
/dev/zram0 is set up, so I can do fdisk on it, but no partitions exist,
because the bootup code is following MY instructions to only use the
Disk SWAP I defined for it.  HOWEVER, since the messages come up, it's
defined, so the actual RAM to run the server is less.  So, what I
encountered, when I rebooted it (when I was able to get Stand-alone time
on it), let the messages come up, bring up FVWM and some of my heavy
resource programs, such as Hercules (IBM Mainframe emulator) and Turnkey
MVS, which runs an older, "public domain" (even if IBM doesn't like it,
they must "abide by it", because there is no copyright code, like there
is in, say, MVS/ESA or z/OS, the heavily protected releases).

My experience was heavy use of the Disk SWAP partition, to the level of
Thrashing.  So, while these Emulators were running (but slowly), I went
into Root (which I do, as a Linux Administrator, even though Ubuntu
"frowns on it" and "prefers Sudo"!  LOL!)   And then, I brought down
zram0, using instructions, earlier in this forum.  GUESS WHAT?  It went
back to normal, with all RAM access being IN THE RAM, rather than in
SWAP.  This test went SO FAST, I was able to reboot again, and go back
into production, with two hours to spare.  [Pat on back.  "At-a-boy",
but no raise].   :-)

So, if zram0 is coming up, with the messages, but your systems are not
freezing, you may still be getting Performance Hits, instead of only
"ugly error messages".

I repeat:  Please re-open #1217189, for older kernels, which are getting
ZRAM kernel code, even if not trying to define the RamDisks.

Thank you and best regards,

Kenneth Parker, Seattle, WA
 --  I'm a Troubleshooter.  I Look for Trouble and Shoot it.
   <Joke told to Seattle Police>Don't worry about the "Shoot it" part.  
     I do not own a gun, mainly because I  could not hit the
     broad side of a barn!</Joke told to Seattle Police>

-- 
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