Logout Freeze [kernel tried to execute NX-protected page - exploit attempt? (uid: 0)]

Hello,

I've got the same bug when the non-free nvidia driver are used. Actually, after some logout/reboots/shutdown (without the driver installed) I've got no problem. I suppose this is the driver for nvidia 64bits but I'm not sure.

I am using the x64 non-free nvidia driver as well, but in accordance with the bug here (http://ubuntuforums.org/showthread.php?t=1593705) i am forced to use the driver or be stuck with an 800x600 screen on an 18.1" laptop screen...
It is amazing how the only unstable parts of linux systems are the proprietary ones.

Hello
can someone reproduce the bug and attach here, using below button 'Add attacment or patch' the files:
/var/log/kern.log
/var/log/kern.log.1
Thanks
Fabio

That's simply not possible because the computer locks up and you are forced to kill the computer. However, after installing updates from update manager manually (which should be automatic...) on Thursday, I have not experienced the issue. I'll keep you updated on whether or not it happens again. (And there was an NVidia update so I hope it fixed it)

Oh and sorry I forgot to mention I also removed quiet and splash from my grub boot settings. I'm not sure which fixed the problem - If you would like me to add them back in and try testing like that for a while I would be happy to.

Ok, thanks for the reply
I set the status for auto expiration in 60 days if there's no activities in this report.
If you still experiencing again problems with update manager please open a bug report typing in terminal
ubuntu-bug update-manager
Thanks again
Fabio

Il giorno sab, 23/04/2011 alle 16.21 +0000, Daniel Centore ha scritto:
> Oh and sorry I forgot to mention I also removed quiet and splash from my
> grub boot settings. I'm not sure which fixed the problem - If you would
> like me to add them back in and try testing like that for a while I
> would be happy to.
>
Hello
Yes it can be usefull to evaluate if the freeze is due to plymouth.
Times ago i've experienced a bug in wich i've to press a key to complete
the shutdown.

Greetings
Fabio

I have two machines which are both still experiencing a hard freeze on logout/shutdown on the released version of 11.04. Initially I thought it was fglrx related, but I have swapped one machine to an nvidia card and am still experiencing the issue. I 've attached the current xorg.conf from the nvidia machine. Switching to nouveau still doesn't cure the problem.

The hang still appears when shutting down using a terminal command.

/var/log/kern.log from machine which is hanging on logout/shutdown

The log starts out with the ati card installed (hangs), then switches to an nvidia card (still hangs...). There might even be a boot
with the onboard graphics buried in there (nvidia, still hangs :)

can you try disabling plymouth (removing splash and quiet from the boot args)? I need this as a production machine right now and really don't wanna mess with my (working) configuration.

Removing quiet and splash has no effect on the hang.

From kern.log:

Apr 29 09:54:50 PB1 kernel: [ 35.202322] ioremap error for 0xbffa0000-0xbffa1000, requested 0x10, got 0x0
Apr 29 09:54:50 PB1 kernel: [ 35.210258] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro,commit=0
Apr 29 09:54:50 PB1 kernel: [ 35.302810] usb 2-2: usbfs: interface 0 claimed by usblp while 'usb' sets config #1
Apr 29 09:54:54 PB1 kernel: [ 38.684926] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro,commit=0
Apr 29 09:54:58 PB1 kernel: [ 42.576009] eth0: no IPv6 routers present
Apr 29 09:55:07 PB1 kernel: [ 51.673415] hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.
Apr 29 09:55:42 PB1 kernel: [ 86.976253] kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
Apr 29 09:55:42 PB1 kernel: [ 86.976255] BUG: unable to handle kernel paging request at c00cc663
Apr 29 09:55:42 PB1 kernel: [ 86.976257] IP: [<c00cc663>] 0xc00cc663
Apr 29 09:55:42 PB1 kernel: [ 86.976267] *pdpt = 000000000187d001 *pde = 0000000001958067 *pte = 80000000000cc163
Apr 29 09:55:42 PB1 kernel: [ 86.976270] Oops: 0011 [#1] SMP
Apr 29 09:55:42 PB1 kernel: [ 86.976272] last sysfs file: /sys/devices/virtual/sound/timer/uevent
Apr 29 09:55:42 PB1 kernel: [ 86.976275] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat snd_hrtimer rfcomm binfmt_misc sco bnep l2cap dm_crypt ppdev parport_pc snd_hda_codec_hdmi nvidia(P) snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm ipt_REJECT snd_seq_midi ipt_LOG xt_multiport snd_rawmidi snd_seq_midi_event snd_seq xt_limit xt_tcpudp ipt_addrtype btusb xt_state snd_timer bluetooth ip6table_filter snd_seq_device ip6_tables nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_ftp nf_conntrack iptable_filter psmouse ip_tables x_tables joydev serio_raw snd usblp i2c_nforce2 soundcore snd_page_alloc hwmon_vid coretemp lp parport usbhid hid uvesafb usb_storage uas ahci libahci forcedeth pata_amd
Apr 29 09:55:42 PB1 kernel: [ 86.976306]
Apr 29 09:55:42 PB1 kernel: [ 86.976308] Pid: 1182, comm: Xorg Tainted: P 2.6.38-8-generic-pae #42-Ubuntu Packard Bell imedia S1710/MCP73T-AD
Apr 29 09:55:42 PB1 kernel: [ 86.976312] EIP: 0060:[<c00cc663>] EFLAGS: 00213246 CPU: 0
Apr 29 09:55:42 PB1 kernel: [ 86.976317] EIP is at 0xc00cc663
Apr 29 09:55:42 PB1 kernel: [ 86.976318] EAX: 00004f07 EBX: 00000000 ECX: 00000000 EDX: 00000000
Apr 29 09:55:42 PB1 kernel: [ 86.976320] ESI: f1938000 EDI: f1938754 EBP: e4047bc4 ESP: e4047bb8
Apr 29 09:55:42 PB1 kernel: [ 86.976321] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068

The BUG output in kern.log has disappeared now, but the problem (freeze on logout /shutdown) still remains.
There are various people reporting this elsewhere, all marked as duplicates of #762203.

I have both an nvidia and an fglrx desktop machine displaying the bug.

I have the same issue here after upgrading to 11.04. A workmate of mine installed a fresh copy on identical hardware and does experience the issue, issue could be upgrade related. It's diffidently related to VT switching. If I switch terminals, the issue occurs (ctrl-alt-f1). HP EliteBook 8540p

While in 10.10 I ran I followed the walk-through on the page below titled "Script To Fix The Ubuntu Plymouth For Proprietary Nvidia And ATI Graphics Drivers". Did other users reporting this issue also run this?

http://www.webupd8.org/2010/10/script-to-fix-ubuntu-plymouth-for.html

I never ran this script. And I also have the issue when switching terminals (I thought it was a different bug).

I ran the script located URL below and now I have the non-graphical VT (Virtual Terminal), text only, but the VT switching issues are gone, I can logout, shutdown, switch VTs....

http://www.kyleabaker.com/downloads/ubuntu/scripts/plymouth-resolution-fix-revert-back.sh.zip

Yes, the revert script fixes the logout/shutdown freeze for me on the fglrx machine.

 http://www.kyleabaker.com/downloads/ubuntu/scripts/plymouth-resolution-fix-revert-back.sh.zip

I had forgotten that I had tinkered with the plymouth settings in 10.10 to get rid of an ugly bootsplash - self inflicted bug :)

I'll try in tomorrow on the nvidia machine that is showing similar symptoms.

I'll cross post to #762203.

The key is to run "sudo apt-get purge v86d" - Daniel try this command

If I install that package (v86d) and execute /sbin/v86d, the console will lock up immediately when switching VTs. v86d is not included by default on a fresh stock Ubuntu install.

It's also a good idea to set the Plymouth theme back to default, if you changed it....

sudo update-alternatives --config default.plymouth

mia

I do not have v86d installed. Also, I disabled plymouth (as described above) and updated many packages. Around the same time, the freezes stopped for me. I do not want to re-enable plymouth because I need a production machine for the time being. Some of the others who still have this problem might like to try this though.

Removing v86d also fixes the freeze for me on the nvidia machine so, for me at any rate, that seems to have been the root cause.

Daniel Centore, thank you for reporting this and helping make Ubuntu better. Natty reached EOL on October 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/767927/comments/24