kernel-packages team mailing list archive

[Karlchen <1105900@xxxxxxxxxxxxxxxxxx>]

Hello, folks.

I know it has been a really long time since I have last posted in this
bug report which after all has been opened by me.

Ubuntu 12.04 Kernel 3.2.0-37
----------------------------------------
In post #17 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1105900/comments/17)  I confirmed that starting with kernel 3.2.0-37 the reported problem/bug had been fixed.
As far as I can tell this is true for all later 3.2.0-x kernels, too.
On my Ubuntu 12.04, by now Ubuntu 12.04.3, the problem has never occurred again. And currently, I am on kernel 3.2.0-55.
Summary: Bug fixed in kernel 3.2.0-37 and all later kernels.

Ubuntu 12.10 Kernel 3.5.0-23
-----------------------------------------
In post #18 (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1105900/comments/18) I had stated that the problem still persisted. This was right with respect to the symptoms. This was wrong with respect to the cause.
Starting with 3.5.0.23 the "filesystem / busy" during the shutdown and the need to perform an fsck during startup has no longer been caused by the kernel.

As I know by now - shame on me for needing more than 6 months to find out - the remaining symptoms were caused by a shutdown problem which is discussed e.g. in these two Launchpad bug reports:
+ Upstartification of /etc/init.d/networking has lost deconfiguring-networking event causing bad side-effects
   (https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1061639)
+ In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot
   (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987)

So whoever is still experiencing an unclean root filesystem on each
startup should check those two bug reports.

>From my point of view: Kernel bug fixed in kernel 3.5.0-23 and all later
kernels.

Kind regards,
Karl


** Changed in: linux (Ubuntu)
       Status: Confirmed => Fix Released

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

Title:
  Latest Kernel Version 3.2.0-36 Causing EXT4-fs Errors

Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  System: Ubuntu 12.04.1 x64 Unity desktop
  ---
  lsb_release -rd; uname -a
  Description:	Ubuntu 12.04.1 LTS
  Release:	12.04
  Linux Voyager 3.2.0-36-generic #57-Ubuntu SMP Tue Jan 8 21:44:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
  --
  Have not experienced any severe problems with this system from Aug 2012 till Jan 20 2013, when kernel 3.2.0-35 was still the active kernel.
  2013-01-20  21:01 kernel 3.2.0-36 was installed by the Ubuntu updater. No installation problems occurred.
  Ever since K3.2.0-36 was the active kernel, the following problem occurred:

  On every restart error messages like these could be read in /var/log/syslog:
  syslog:Jan 22 00:44:37 Voyager kernel: [    3.624421] EXT4-fs (sda5): orphan cleanup on readonly fs
  syslog:Jan 22 00:44:37 Voyager kernel: [    3.652470] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2886456
  syslog:Jan 22 00:44:37 Voyager kernel: [    3.652671] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2886232
  syslog:Jan 22 00:44:37 Voyager kernel: [    3.652688] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2886450
  syslog:Jan 22 00:44:37 Voyager kernel: [    3.678434] EXT4-fs (sda5): ext4_orphan_cleanup: deleting unreferenced inode 2369342
  syslog:Jan 22 00:44:37 Voyager kernel: [    3.689458] EXT4-fs (sda5): 4 orphan inodes deleted
  syslog:Jan 22 00:44:37 Voyager kernel: [    3.689462] EXT4-fs (sda5): recovery complete

  This happens no matter whether the system is rebooted (warm reboot) or
  shutdown and restarted later (cold reboot).

  The relevant thing is that in the session which is shutdown the active kernel has to be K3.2.0-36.
  The error will be detected in the next session started after reboot.

  The workaround was going back to K3.2.0-35. During the first reboot
  the errors left behind by the previous K3.2.0-36 session were cleaned
  up. From then on sticking with K3.2.0-35 the errors would not return
  after any reboot.

  Conclusion:
  ----------------
  Telling from the symptoms Ubuntu 12.04.1 with K3.2.0-36 does not umount the root filesystem properly or does some other bad thing to leave behind orphaned inodes.
  Returning to K3.2.0-35 will work around the problem

  Note:
  -------
  (1) I have seen this problem on 3 different machines (different hardware) running Ubuntu 12.04.1 x64 and Ubuntu 12.04.1 x86.
        So it is not a problem caused by a flaw of one special machine.
  (2) I have seen the same problem after updating Ubuntu 12.10 from K3.5.0-17 to K3.5.0-22. This suggests some change in the
        latest kernel editions  which is common to the current Ubuntu kernels may be involved.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-36-generic 3.2.0-36.57
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
  Uname: Linux 3.2.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  karl       2234 F.... pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfdff4000 irq 44'
     Mixer name	: 'Realtek ALC888'
     Components	: 'HDA:10ec0888,1462735b,00100001'
     Controls      : 45
     Simple ctrls  : 21
  Date: Sat Jan 26 10:50:56 2013
  HibernationDevice: RESUME=UUID=20f6167d-0136-4d21-a1d9-fb36954a0815
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
  IwConfig:
   lo        no wireless extensions.

   eth0      no wireless extensions.
  MachineType: MEDIONPC MS-7358
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-36-generic root=UUID=7eb4fefd-d144-4bdb-9848-199970e85265 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/karl not ours.
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-36-generic N/A
   linux-backports-modules-3.2.0-36-generic  N/A
   linux-firmware                            1.79.1
  RfKill:

  SourcePackage: linux
  StagingDrivers: zram
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7358
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd07/24/2007:svnMEDIONPC:pnMS-7358:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7358:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7358
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

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