After last Kernel Update (3.2.0-44) system hangs on startup

[Juergen N]

My system hangs when I startup. The login screen shows up, but when I try to enter the password, after 1-3 chars the system hangs (keyboard and mouse freeze, system does not respond to anything except reset).

I now started the system with the older 3.2.0-41 kernel and it works.

I also attach a dmesg-file from a previous startup. The only thing I noticed myself are the odd NFSD-messages at the end, which I did not find in the newer dmesg (with patch 41 kernel).

Ubuntu 12.04.2 LTS

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-41.66-generic 3.2.42
Uname: Linux 3.2.0-41-generic i686
NonfreeKernelModules: tusbd nvidia
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: i386
Date: Sat May 25 17:03:19 2013
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.ISO-8859-1
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to precise on 2012-08-24 (274 days ago)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: juergen 4135 F.... pulseaudio
 /dev/snd/pcmC0D0p: juergen 4135 F...m 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 0xfc220000 irq 47'
   Mixer name : 'Realtek ALC663'
   Components : 'HDA:10ec0663,17341157,00100001'
   Controls : 34
   Simple ctrls : 17
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=84d3ad5c-6cf4-42ec-ac6b-98d4e6327ec7
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427)
IwConfig:
 lo no wireless extensions.

 virbr0 no wireless extensions.

 eth0 no wireless extensions.
MachineType: FUJITSU SIEMENS ESPRIMO P7935
MarkForUpload: True
NonfreeKernelModules: tusbd nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.ISO-8859-1
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-41-generic root=UUID=d6205c74-66aa-4ee3-84d8-89e0aaa3028d ro quiet splash
ProcVersionSignature: Ubuntu 3.2.0-41.66-generic 3.2.42
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-41-generic N/A
 linux-backports-modules-3.2.0-41-generic N/A
 linux-firmware 1.79.4
RfKill:

StagingDrivers: mei
Tags: precise staging
Uname: Linux 3.2.0-41-generic i686
UpgradeStatus: Upgraded to precise on 2012-08-24 (274 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
dmi.bios.date: 01/15/2009
dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd.
dmi.bios.version: 6.00 R1.11.2812.A1
dmi.board.name: D2812-A1
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: S26361-D2812-A1
dmi.chassis.type: 6
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.11.2812.A1:bd01/15/2009:svnFUJITSUSIEMENS:pnESPRIMOP7935:pvr:rvnFUJITSUSIEMENS:rnD2812-A1:rvrS26361-D2812-A1:cvnFUJITSUSIEMENS:ct6:cvr:
dmi.product.name: ESPRIMO P7935
dmi.sys.vendor: FUJITSU SIEMENS

[Dave Gilbert (ubuntu-treblig)]

On the basis that you say it's only this kernel that does it I've changed the package to the kernel package.
You say it doesn't respond to anything; how about:
   * Does it ping from another machine on your network (if you have one)
   * Does ctrl-alt-f1 go to a text console (ctrl-alt-f7 or f8 to get back)

[Juergen N (lauchpkuchen-sahnehaube)]

I tried CTRL-ALT-F1 but it did not work.

I did not try ping yet, since I have no other linux machine ready.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1184154

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

apport information

[Juergen N (lauchpkuchen-sahnehaube)]

Hi,

I ran the command. But of course with the older kernel which is OK. I can't run apport-collect with the troublesome kernel, since I don't get further as the login screen.

Regards,

/juergen

[Dave Gilbert (ubuntu-treblig)]

Critical: Renders the system temporarily unusable

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Please test the latest v3.2 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.45-precise/

[Juergen N (lauchpkuchen-sahnehaube)]

Hi,

I never installed an upstream kernel on my system, thus I need some hints.

I downloaded the package linux-image-3.2.45-030245-generic_3.2.45-030245.201305140735_i386.deb onto my system, but when I try to install it, the installer says, that I rather should install the meta-package for dependencies and so on.

The Muon packager of course by default does only install stable versions of the kernel.

How can I install it? Do I need this linux-generic package? Can you give the related links, please?

I hope, I will not break my running system -- I only have one box here for Kubuntu.

Regards and Thanks!

[Krzysztof Limburski (limbur)]

I have had a similar problem but my system frozes before the login window. I am using 64-bit system. The kernel version 3.2.45 help me to correct it. In my opinion kernel 3.2.44 is broken. On my second computer after kernel update I am able to login and work but system hangs up during shutdown.

Jurgen you should download:
linux-image-3.2.45-030245-generic_3.2.45-030245.201305140735_i386.deb
linux-headers-3.2.45-030245_3.2.45-030245.201305140735_all.deb
linux-headers-3.2.45-030245-generic_3.2.45-030245.201305140735_i386.deb

and install it using command:
sudo dpkg --install linux*deb

reboot

Best Regards

[Juergen N (lauchpkuchen-sahnehaube)]

Hi,

yesterday, I got the new upstream kernel (PL 45) by normal means unto my system (I did not have time to install it manually before).

The result is, that my system hangs even further. Now it hangs before the X environment is fully started. It seams that the X server is started partially, but no desktop shows up. I get some weird graphics display (one line of graphic -- a part of the desktop?? -- over the screen, the rest stays black) and the system hangs.

Now I have two kernel versions (3.2.44 and 3.2.45) on the system, that don't work!

Really weird, that nobody else has troubles.

What is going on?

Best Regards,

/juergen

[Juergen N (lauchpkuchen-sahnehaube)]

I off course meant, "the system now hangs even earlier"

[nako (vncprado)]

I had the same issue.
So I found:
http://askubuntu.com/questions/302129/xubuntu-12-04-hang-on-boot-of-kernel-3-2-0-44-generic
then I remove dahdi and something related to it.
Now I can login and typing uname -r:
3.2.0-45-generic

[Juergen N (lauchpkuchen-sahnehaube)]

@nako: I would say, this is not my bug, since I don't get swapon-messges (see the startup protocol, I added above).

Also I don't have *any* dahdi-modules installed.

[Juergen N (lauchpkuchen-sahnehaube)]

Hi there,

am I the only one affected?

But when I see, how much I had to do just to open the message, I guess many did not take the trouble.

I am a little frustrated, since the bug is now so old, two kernels are troublesome (till now) and still nobody is assigned.

Guess, I have to install Win7.

[Saija (julborre)]

Hi

I can attest that the kernel 3.2.0-44 AND 3.2.0-45 both of them hangs up the entire system, with them the system starts and show off the login screen, there when I move the mouse to enter my credentials the systems freeze, no mouse movement, no keyboard inputs, no CTRL+ALT+FN, nothing, nada.

The only option left to my is shut down the laptop pressing down the powen button for a while, then restart and the on the grub menu select previous linux versions and then select the 3.2.0-43 version.

My system it's a 12.04 Precise Pangolin.

[Andreas Profitlich (andreas.profitlich)]

you are not alone - the problem started with 3.2.0-43

the system gave me lots of kernel hung errors at boot time and stopped while booting at different stages but never allowed to login

I finally got back to 3.2.0-41 which is ok for me.

[Saija (julborre)]

I just installed the kernel 3.2.0-48 hoping this new version will fix the error, but this continues.

And I'm just wondering that there's no official answer

[Juergen N (lauchpkuchen-sahnehaube)]

Also my system hangs now with tree kernels!

Still nobody working on this.

Stupid names for versions do not make this better!

[Michael Reid (mareid)]

I am having a very similar problem to this. When I boot using kernel 3.2.0-48, X does not seem to start. The next thing I see after Grub is a black screen. If I press the power button on my computer while it is displaying the black screen, I hear the HDD clacking away as usual, as though the system is shutting down normally, then it powers off normally. Ctrl-Alt-F1 produces no effect.

If I boot kernel 3.2.0-45, the problem does not occur.

I am not sure if it is related, but input devices attached to my USB 3.0 ports recently stopped working in Grub, too.

[Andre Paquette (l-andre)]

I am also seeing this problem. I am using dahdi, so I assume it is related to that, but have not tried uninstalling it. On 3.2.0-44 and later I get soft lockups just after dahdi starts initializing. Am sticking with 3.2.0-43 until this is resolved.

[John Hopkinson (john-hopkinson)]

I am also have this same, or a very similar problem. Ever since 12.04 version 43 I have not been ale to get any of the newer version to work on my system. I am running on a Dell Optiplex 745 12.04 version 41.

If I attempt to use a newer version, after Boot the system goes to the next screen and the lights continue to run for a time while the system indicates disk access. After a while the lights stop, disk access stops and the system appears to freeze, nothing works. I have left the system for over 10 minutes to see if something is happening in the background, there is no indication of this. After that time my only option is to switch off the power, the power down button is not active.

I have no idea what is causing this problem, but it sounds very similar to those reported above.

Once I start the system in version 41, everything appears to be working normally.

[Saija (julborre)]

Enough is enough! I have had it with these annoying bugs on this annoying new Ubuntu!

I just formatted and installed Fedora on my work laptop, I'm planning on doing the same at home.

Thank you guys for your time and dedication but frankly I don't have the time now to mess with configurations, logs and support forums to make something works as expected specially something that a previous kernel version worked flawlessly, and the worst: no official answer, none, ninguna, zero, nada.

I'll always will try to make my best to help Ubuntu, but right now I'm moving elsewhere.

THANK YOU AND SEE YA ALL!

PS: I remember the good ol' days of Warthy Warthog and the new experience of having a good and usable and user friendly linux distro who doesn't need I became some sort of wizard to learn ancient incantations to make my old SIS620 integrated "graphic chip" work with X86(XFree, or X11, I don't remember..)

Gracias Totales!

[penalvch (penalvch)]

Juergen N, as per http://support.ts.fujitsu.com/Download/ShowFiles.asp an update is available for your BIOS (6.00.1.19). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

[Andre Paquette (l-andre)]

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: andre 1820 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 0xf8ff8000 irq 45'
   Mixer name : 'Analog Devices AD1988B'
   Components : 'HDA:11d4198b,104381f6,00100200'
   Controls : 49
   Simple ctrls : 26
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=5ff6e571-5a9f-4503-b785-11d535246217
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IwConfig:
 lo no wireless extensions.

 eth1 no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-43-generic root=UUID=8a71ba4a-d8d9-4fc8-9dc3-3df31bed8057 ro quiet splash
ProcVersionSignature: Ubuntu 3.2.0-43.68-generic 3.2.42
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory /home/andre not ours.
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-43-generic N/A
 linux-backports-modules-3.2.0-43-generic N/A
 linux-firmware 1.79.4
RfKill:

StagingDrivers: echo
Tags: precise staging
Uname: Linux 3.2.0-43-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 09/30/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1238
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5B-Deluxe
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.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

apport information

[Andre Paquette (l-andre)]

I am seeing (what I believe to be) the same problem with a P5B-Deluxe board, running the latest BIOS. (1238).

I've run a apport-collect of a successful boot with 3.2.0-43.
I will also try the upstream kernel.

[Andre Paquette (l-andre)]

Perhaps some useful info:

I updated to 3.2.45-030245 and it booted successfully, but DAHDI didn't come up because of a symbol mismatch.
I ran "sudo dpkg-reconfigure dahdi-dkms" and rebooted back into 3.2.45 and DAHDI came up fine. So the upstream kernel is working for me.

And so I went back to 3.2.0-44, which booted fine because of the symbol mismatch in DAHDI (which was reconfigured for 3.2.45). And re-ran dpkg-reconfigure on dahdi-dkms for that kernel, and now I can boot into 3.2.0-44 just fine.

It seems like the issue here is a dependency problem between dahdi and the kernel. The difference between 3.2.0-43 and 3.2.0-44 was small enough that it didn't fail to load because of a symbol mismatch but large enough that it caused some serious system issues that prevented booting.

Juergen, perhaps you should boot to 3.2.0-43 and add dahdi to the module blacklist. Then upgrade to the kernel of your choice and hopefully it will boot. Then reconfigure the dadhi package so it gets rebuilt for that kernel. Then remove dadhi from the module blacklist and reboot. And pray.

[Juergen N (lauchpkuchen-sahnehaube)]

Hi,

I am sorry, but I can not be of any further assistence with this bug, since I installed a new computer using Debian. One reason for the new computer and the choice of the OS was this bug. The old computer is retired (eventually I will install Win7 on it).

Best Regards,

/juergen

[penalvch (penalvch)]

Juergen N, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1184154/comments/62 regarding you no longer using Ubuntu. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Andre Paquette, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[John Hopkinson (john-hopkinson)]

Excuse me, but I still have this problem. The original reporter of this Bug may have changed OSes, but I have not and I still have the problem., the latest occurrence with version 49.

Reading this thread, I would believe that others do as well.

I would appreciate it if you would continue to attempt to resolve this problem.

[Andre Paquette (l-andre)]

They'll probably want you to raise a new bug report for it. If you do, please include me.

Btw, I'm convinced this isn't a kernel bug but rather a problem with rebuilding the modules when updating to a new kernel. See my notes above.

I was able to reproduce the problem but am trying to characterize it a little more before raising a new bug report myself. It could be a few days before I get to it...

[penalvch (penalvch)]

John Hopkinson, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.