[Bug 750649] Re: [Lenovo W510/T410/T510] System is unable to suspend

2011-04-20 Thread Jason Joines
Resume from hibernate in Natty just stopped working on my Lenovo
ThinkPad T510.  It worked fine until running update's last night.
Updates today also gave errors when trying to update apport.

Kernel is 2.6.38-8.42.  I'm using the integrated intel graphics.

The problem is a kernel OOPS at boot.  These seem to be the relevant log
messages:

Apr 20 17:17:04 rooibos kernel: [  153.659483] BUG: unable to handle kernel 
NULL pointer dereference at 0008
Apr 20 17:17:04 rooibos kernel: [  153.659530] IP: [81171cba] 
link_path_walk+0x66a/0xc40
Apr 20 17:17:04 rooibos kernel: [  153.659565] PGD 225f60067 PUD 225f61067 PMD 
0 
Apr 20 17:17:04 rooibos kernel: [  153.659590] Oops:  [#1] SMP 
Apr 20 17:17:04 rooibos kernel: [  153.659607] last sysfs file: 
/sys/devices/virtual/tty/tty10/uevent
Apr 20 17:17:04 rooibos kernel: [  153.659634] CPU 0 
Apr 20 17:17:04 rooibos kernel: [  153.659644] Modules linked in: rfcomm sco 
bnep l2cap ip6table_filter ip6_tables nf_conntrack_ipv4 nf_defrag_ipv4 xt_state 
nf_conntrack iptable_filter ip_tables x_tables parport_pc ppdev dm_crypt 
snd_hda_codec_hdmi snd_hda_codec_conexant joydev snd_hda_intel snd_hda_codec 
snd_hwdep snd_pcm arc4 snd_seq_midi iwlagn thinkpad_acpi iwlcore tpm_tis nvram 
snd_rawmidi snd_seq_midi_event mac80211 lp parport snd_seq tpm cfg80211 
snd_timer btusb tpm_bios intel_ips snd_seq_device psmouse snd bluetooth 
soundcore snd_page_alloc serio_raw i915 sdhci_pci drm_kms_helper drm ahci 
libahci firewire_ohci firewire_core crc_itu_t e1000e sdhci i2c_algo_bit video
Apr 20 17:17:04 rooibos kernel: [  153.659966] 
Apr 20 17:17:04 rooibos kernel: [  153.659975] Pid: 1435, comm: kded4 Not 
tainted 2.6.38-8-generic #42-Ubuntu LENOVO 4313CTO/4313CTO
Apr 20 17:17:04 rooibos kernel: [  153.660017] RIP: 0010:[81171cba]  
[81171cba] link_path_walk+0x66a/0xc40
Apr 20 17:17:04 rooibos kernel: [  153.660054] RSP: 0018:8802314c7d68  
EFLAGS: 00010286
Apr 20 17:17:04 rooibos kernel: [  153.660076] RAX:  RBX: 
8802314c7e58 RCX: 
Apr 20 17:17:04 rooibos kernel: [  153.660105] RDX: 88022f6f8a80 RSI: 
 RDI: 88022f6f8a80
Apr 20 17:17:04 rooibos kernel: [  153.660136] RBP: 8802314c7e08 R08: 
0009 R09: 88022f6f8ac0
Apr 20 17:17:04 rooibos kernel: [  153.660166] R10: 002a R11: 
0202 R12: 88022f756600
Apr 20 17:17:04 rooibos kernel: [  153.660195] R13: 88022f5f7b60 R14: 
8802314c7db8 R15: 880230be2dc0
Apr 20 17:17:04 rooibos kernel: [  153.660225] FS:  7fafe0646780() 
GS:8800bb00() knlGS:
Apr 20 17:17:04 rooibos kernel: [  153.660259] CS:  0010 DS:  ES:  CR0: 
80050033
Apr 20 17:17:04 rooibos kernel: [  153.660283] CR2: 0008 CR3: 
000232519000 CR4: 06f0
Apr 20 17:17:04 rooibos kernel: [  153.660313] DR0:  DR1: 
 DR2: 
Apr 20 17:17:04 rooibos kernel: [  153.660343] DR3:  DR6: 
0ff0 DR7: 0400
Apr 20 17:17:04 rooibos kernel: [  153.660374] Process kded4 (pid: 1435, 
threadinfo 8802314c6000, task 880230be2dc0)
Apr 20 17:17:04 rooibos kernel: [  153.660407] Stack:
Apr 20 17:17:04 rooibos kernel: [  153.660417]  0001 
 ea00074b0988 8802fffe
Apr 20 17:17:04 rooibos kernel: [  153.660449]  8800bb00e380 
880230be2dc0 880230be2dc0 0040e060
Apr 20 17:17:04 rooibos kernel: [  153.662397]  0009c5372b66 
88023201201f 88022ea23d00 88022f6f8a80
Apr 20 17:17:04 rooibos kernel: [  153.664306] Call Trace:
Apr 20 17:17:04 rooibos kernel: [  153.666232]  [8117258b] 
do_path_lookup+0x5b/0x160
Apr 20 17:17:04 rooibos kernel: [  153.668167]  [811728f7] 
user_path_at+0x57/0xa0
Apr 20 17:17:04 rooibos kernel: [  153.670095]  [81134a78] ? 
unmap_region+0x158/0x170
Apr 20 17:17:04 rooibos kernel: [  153.671987]  [8113481e] ? 
remove_vma+0x6e/0x90
Apr 20 17:17:04 rooibos kernel: [  153.673859]  [8113627c] ? 
do_munmap+0x2ec/0x360
Apr 20 17:17:04 rooibos kernel: [  153.675739]  [811699d9] 
sys_readlinkat+0x39/0xb0
Apr 20 17:17:04 rooibos kernel: [  153.677565]  [81169a6b] 
sys_readlink+0x1b/0x20
Apr 20 17:17:04 rooibos kernel: [  153.679373]  [8100c002] 
system_call_fastpath+0x16/0x1b
Apr 20 17:17:04 rooibos kernel: [  153.681230] Code: 4c 8d 75 b0 48 8d 4d c8 48 
8d 75 a0 48 89 df 4c 89 f2 e8 ca f6 ff ff 85 c0 89 c1 75 c3 4c 8b 65 c8 4d 85 
e4 74 10 49 8b 44 24 10 48 83 78 08 00 0f 85 e7 02 00 00 8b 53 40 f6 c2 40 0f 
84 63 01 
Apr 20 17:17:04 rooibos kernel: [  153.685332] RIP  [81171cba] 
link_path_walk+0x66a/0xc40
Apr 20 17:17:04 rooibos kernel: [  153.687369]  RSP 8802314c7d68
Apr 20 17:17:04 rooibos kernel: [  153.689377] CR2: 0008
Apr 20 17:17:04 rooibos kernel: [  153.792219] ---[ end trace 74f449c61e96ecc7 

[Bug 750649] Re: [Lenovo W510/T410/T510] System is unable to suspend

2011-04-20 Thread Jason Joines
Resume from sleep/suspend to ram still works, it's only
hibernate/suspend to disk that fails.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750649

Title:
  [Lenovo W510/T410/T510] System is unable to suspend

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 750649] Re: [Lenovo W510/T410/T510] System is unable to suspend

2011-04-15 Thread Marc Legris
Issue seems to be resolved on the W510 with the latest natty packages,
with and without the nVidia driver.

** Changed in: linux (Ubuntu Natty)
   Status: Incomplete = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750649

Title:
  [Lenovo W510/T410/T510] System is unable to suspend

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 750649] Re: [Lenovo W510/T410/T510] System is unable to suspend

2011-04-11 Thread Chris Van Hoof
Marc -- Can you confirm you see the same behaviour with the nvidia
driver installed via jockey?

** Changed in: linux (Ubuntu Natty)
 Assignee: Chris Van Hoof (vanhoof) = Marc Legris (maaarc)

** Changed in: linux (Ubuntu Natty)
   Status: New = Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750649

Title:
  [Lenovo W510/T410/T510] System is unable to suspend

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 750649] Re: [Lenovo W510/T410/T510] System is unable to suspend

2011-04-10 Thread Johannes Postler
Maybe this is a duplicate of  #625364 ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750649

Title:
  [Lenovo W510/T410/T510] System is unable to suspend

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 750649] Re: [Lenovo W510/T410/T510] System is unable to suspend

2011-04-08 Thread Marc Legris
** Summary changed:

- [Lenovo W510/T410] System is unable to suspend
+ [Lenovo W510/T410/T510] System is unable to suspend

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750649

Title:
  [Lenovo W510/T410/T510] System is unable to suspend

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs