← Back to team overview

kernel-packages team mailing list archive

[Bug 1386534] Re: kernel dependent deterministic view crash on X startup

 

Due to your careful question, it turned out, that I have made very serious error!

When installing your "Utopic test kernel with commit b47f210 reverted"

        I did not install the linux-image-extra...

I tried to check whether I did same kind of error earlier.

In case of 3.13.0-36-generic, 3.13.0-36-generic and 3.16.0-28-generic,
and in general, if the installation source was an Ubuntu release, then
the extra was there always.

In case of kernel-PPA, following the
https://wiki.ubuntu.com/Kernel/MainlineBuilds tips ( comment here: #30),
I installed the headers as well, while I did NOT installed the kernel
extra, since there is no such separated stuff.  I tested quite a lot of
kernels.

But, do I see correctly, that a size of greater than 50MB of kernel
binary package means, that that package contains the extras as well?  I
see, when there is a separate extra package, then the normal and extra
package together is slighly larger than the single "over 50MB" kernel
binary package,  this is why I think that this kind of single package
contains the extras as well.

Then I got 4 different kernels upto diverse commits, but since they are
gone from the URL you gave me, I can not RETEST them, ... while I am
suspicious that I did not install the extras, but may happen that I
installed on the base of "why not if it is there", simply I do not
remember.

Now in case of the latest kernel, which is already an "Utopic test
kernel with commit b47f210 reverted", I am sure, that I did NOT install
extras.

However this kernel without the extras, --- due to it's revision number
collision with the similar kernel of the normal Ubuntu release, --- is
sensitive to whether the packages of the normal Ubuntu kernels are there
or not.

In my #42 comment: the extras of the normal release kerlen of the same
version number was there, while the extras you provided were NOT
installed, and in this case I get the usual error.

But, if I remove any trace of the normal release kernel, and then I
install your kernel with extras, then IT WORKS, ... actually I write
this comment using your latest kerenel provided me!

I try to prevent this kernel from updating by the automatic updating
system of Ubuntu.

Is installing linux-image-### and linux-image-extra-### enough to get
rid of the other kernel with same version number, or what I have to do
to make a clean install of the kernels you gave me?

In short: 3.13.0-36-generic works, 3.13.0-37-generic has the issue,
official 3.16.0-28-generic also has the issue, but YOUR
3.16.0-28-generic WORKS.

I really excuse myself for my big error and WASTING YOUR TIME, and
naturally I am ready to repeat former tests, if you could provide those
packages again.

This week I prepared to formulate my thanks that regardless of we know
each other you give your time and knowledge, ... and jut in this week I
had to discover my error vasting resources.  I advocate the free
softwares approximately since two and half decades, as a university
staff, so in theory I understand the importance and the meaning of this
global movement, ... but it is very touching to have such an abstract
and at the same time personal experinece, that someone from the mankind
whom I even don't know on which continent is resident, helps.

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

Title:
  kernel dependent deterministic view crash on X startup

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36

  The phenomenon: just when the user interface starts at the end of the
  Ununtu startup, the screen reamins in one solid color (very light
  grey, this is the everage of my colors), except for the topmost 3-4
  scan lines, where one can see some sort of vibrating content.
  Sometimes there is a 1-3 seconds of normal operation just at the
  start, when Ctrl-Alt-F2 works, and swithing there one can work in the
  character terminal forever.  But as soon as the disorder in the X view
  appears, even the Ctrl-Alt-F2 console change does not work visually,
  however a blindly stroken Ctr-Alt-Del is correctly executed.

  What I know: (1) on the core i3 based laptop there is no trace of this
  kind of view crash, while in case of the Phenom x6 1100t and Radeon HD
  6570 based desktop machine the problem is fully deterministic.  (2)
  the problem is distro independet, i.e.:  I have it with Ubuntu 14.04 +
  kernel 3.13.0-37-generic, and also with Ubuntu 14.10 +
  3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel
  3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic.
  (3) In case of Ubuntu 14.04 in average every second or third boot gave
  a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2,
  while in case of Ubuntu 14.10 there is no such a short time slot when
  I could escape.  (4) my configuration is set to fall into my only user
  account directly, I will do experiments, whether the problem is there,
  if the startup is without falling into an account.

  If I can, I will apport log files with produced with the
  3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic.

  I try to send the remaining information after my work day, now I have to leave, sorry.
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDmesg:
   [   11.299825] init: plymouth-upstart-bridge main process ended, respawning
   [   11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: Unknown unit: user@1000.service
   [   11.329706] systemd-logind[1615]: Failed to start user service: Unknown unit: user@1000.service
   [   11.332093] systemd-logind[1615]: New session c1 of user prohlep.
   [   11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.
  DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroRelease: Ubuntu 14.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Device [1682:3195]
  InstallationDate: Installed on 2014-06-26 (124 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: System manufacturer System Product Name
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Tags:  utopic ubuntu compiz-0.9
  Uname: Linux 3.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 07/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Oct 28 21:34:24 2014
  xserver.configfile: default
  xserver.devices:
   input        Power Button         KEYBOARD, id 6
   input        Power Button         KEYBOARD, id 7
   input        A4Tech PS/2+USB Mouse MOUSE, id 8
   input        Cypress Cypress USB Keyboard / PS2 Mouse KEYBOARD, id 9
   input        Cypress Cypress USB Keyboard / PS2 Mouse KEYBOARD, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1
  xserver.video_driver: radeon

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