← Back to team overview

kernel-packages team mailing list archive

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



Getting help how to make tests with upstream kernels, I did find the step,
where using NONE of the few kernels BEFORE that point I have NO xorg error,
while using ANY of the few kernels AFTER that point I HAVE xorg error.

        before 3.13 upstream 3.12.33-031233-generic has NO error

        v3.13.11.6-trusty 13-Aug-2014 and before is OK

        v3.13.11.7-trusty 18-Sep-2014 and after has the ERROR

        after  3.13 upstream 3.14.25-031425-generic has the ERROR

                    upstream 3.18.0-031800rc5-generic has the ERROR

Reinstalling a formerly purged NON-upstream Ubuntu kernel, and investigating
the release date of the kernel packages, I could verify, that the critical
kernel change step is exactly at the correspondig point.

        3.13.0-36-generic 04-Sep-2014 and before is OK

        3.13.0-37-generic 25-Sep-2014 and after has the ERROR

        3.16.0-24-generic ... has the ERROR

All of these kernels were tested with the SAME Ubuntu 14.10 systems, and the
only difference between them was that wich kernel is booted.  In case of
Ubuntu 14.04 I had the critical point EXACTLY at this same place.


Intalling upstream v3.13.11.7-trusty kernel, I catched the folowing

        Running depmod.

        depmod: ERROR: Module 'hci_vhci' has devname (vhci) but lacks
        major and minor information. Ignoring.

        update-initramfs: deferring update (hook will be called later)


Trying out two dozens of different kernels, now I can give a bit better
description of the nature of the graphic error depending on kernel version.

3/a: except for few cases, the keyboard shortcuts work, they can invoke
programs assigned to them, ... naturally I can not use them, because I can
not see them.

3/b: almost alway the option to go Ctrl-Alt-F1 and apply Ctrl-Alt-Del is
alive, while almost never can I read anything even on the caracter terminal,
... except for the case, if the crash of the graphic view arrives a bit (few
seconds) later, and I have a narrow time slot to escape to the character

3/c: if the crash is later, then it is exactly when I first move the

3/d: I left the most important experinece to the end:

the graphical view crash has four different states, the middle two of them
are new views for me, due to the new kernels I tried out:

    -1- as if an oldtimer CRT was not able to correctly position the
        horisontal sync, and hence the picture is horisontally rotated, and
        this state is different from all the other erratic state in that I
        can invoke and use graphical programs, hard to use, because of the
        rotation: going rightward out I arrive and enter at the left edge

    -2- as if an oldtimer CRT can not catch at all an inappropriate
        horisontal sync, far beyond its frequency limit

    -3- the essentially almost homogenous white view is patched of
        very small very intesively blinking regions

    -4- at the top a very few lines reflect the original content of the top
        unity line, but the rest is white and STILL, no blinking, ... let us
        mention, that my background is white, but NOTHING can occur in this
        area, this is a dead white area

Originally an immediate or soon -4-, and immediate or soon -1- soon -4- were
the typical scenarios.

Trying out additional kernels, the additional possibilities are: inmediate
or soon -3-, and immediate or soon -1- soon -2- soon -3-.

Perhaps I should draw a state transition picture.

Thanks for the help,

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  kernel dependent deterministic view crash on X startup

Status in “linux” package in Ubuntu:

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.
  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
   [   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
   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
  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)
  _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
   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.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: