Created attachment 46393 [details] syslog containing kernel messages during s/r, including the oops The oops happens after resume once in about 4-5 s/r cycles. System is a notebook with Radeon X1300 on Debian testing with some packages upgraded to unstable. Kernel is latest 2.6.38 from debian. Radeon driver is 6.14.1 libdrm: 2.4.24-2 When resuming the X display appears for a short time, then the kernel switches back to the console and prints the oops. In less than a seconds some more oopses appear usually in code related to the cdrom, moving the original radeon oops out from the screen. Fortunately by then the oops got written to the syslog and that is attached. Here is the oops (also present in the attached syslog): BUG: unable to handle kernel NULL pointer dereference at 00000001 IP: [<c10b6e0d>] kmem_cache_alloc_trace+0x55/0x92 *pde = 00000000 Oops: 0000 [#1] SMP last sysfs file: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:3.0/tty/ttyACM0/uevent Pid: 1955, comm: Xorg Tainted: G W O 2.6.38-2-686 #1 Acer TravelMate 6460/Coniston EIP: 0060:[<c10b6e0d>] EFLAGS: 00213002 CPU: 0 EIP is at kmem_cache_alloc_trace+0x55/0x92 EAX: f5406a18 EBX: 00000001 ECX: 00000054 EDX: 00000000 ESI: f5002100 EDI: f82c250b EBP: 000080d0 ESP: f70f3e08 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 Process Xorg (pid: 1955, ti=f70f2000 task=f720e080 task.ti=f70f2000) Stack: 00203246 00000054 00001000 eec92400 00002000 00002000 f82c250b 00001000 f51a5a80 f501e000 f84fc25a 00203286 002763ae 00000000 f70f3e98 f51a5a80 00002000 00000000 f84fc32c 00000004 00000000 00000000 f70f3e68 f82cf274 Call Trace: [<f82c250b>] ? drm_gem_object_alloc+0xc/0x51 [drm] [<f84fc25a>] ? radeon_gem_object_create+0x27/0xb1 [radeon] [<f84fc32c>] ? radeon_gem_create_ioctl+0x48/0x7c [radeon] [<f82c0fa4>] ? drm_ioctl+0x224/0x2d5 [drm] [<f84fc2e4>] ? radeon_gem_create_ioctl+0x0/0x7c [radeon] [<c10bdd4b>] ? do_sync_read+0x9e/0xd3 [<f82c0d80>] ? drm_ioctl+0x0/0x2d5 [drm] [<c10c901c>] ? do_vfs_ioctl+0x478/0x4c3 [<c11105bc>] ? fsnotify_perm+0x4f/0x5a [<c10bd9bb>] ? fsnotify_access+0x48/0x4f [<c10be758>] ? vfs_read+0x99/0xd6 [<c10c90ab>] ? sys_ioctl+0x44/0x64 [<c1002f1f>] ? sysenter_do_call+0x12/0x28 Code: 04 24 fa 90 8d 74 26 00 8b 06 64 03 05 f4 df 44 c1 8b 18 85 db 75 11 50 89 f9 89 ea 89 f0 e8 6e f9 ff ff 5f 89 c3 eb 08 8b 56 10 <8b> 14 13 89 10 8b 04 24 50 9d 8d 74 26 00 85 db 74 0e 66 85 ed EIP: [<c10b6e0d>] kmem_cache_alloc_trace+0x55/0x92 SS:ESP 0068:f70f3e08 CR2: 0000000000000001 ---[ end trace 5f481312f8713c89 ]---
Created attachment 46394 [details] xorg log from the session when the oops appeared
Upgraded to 2.6.39 and the issue seems to be gone. There are times when resume fails, but in a completely different way without having a kernel oops printed or logged. If I get around to find out some more information about it I will open a new bug.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.