Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 5 Apr 2002 21:17:09 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 5 Apr 2002 21:16:59 -0500 Received: from 12-234-33-29.client.attbi.com ([12.234.33.29]:14404 "HELO top.worldcontrol.com") by vger.kernel.org with SMTP id ; Fri, 5 Apr 2002 21:16:47 -0500 From: brian@worldcontrol.com Date: Fri, 5 Apr 2002 18:13:55 -0800 To: Alan Cox Cc: linux-kernel@vger.kernel.org Subject: Re: Linux 2.4.19pre5-ac3 w/swsusp oops Message-ID: <20020406021355.GA7553@top.worldcontrol.com> Mail-Followup-To: Brian Litzinger , Alan Cox , linux-kernel@vger.kernel.org In-Reply-To: <200204051945.g35JjnX23183@devserv.devel.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-No-Archive: yes X-Noarchive: yes Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 05, 2002 at 02:45:49PM -0500, Alan Cox wrote: > Ok its fun time. This adds the software suspend code. Its not perfect yet and > a lot of drivers need power management support to work nicely with it. This > is one of the things we have to handle for future ACPI work so its good to > give people a platform for checking their PM code. I had to type it in my hand from a digital photograph. The actually picture of the oops is available at http://www.litzinger.com/opps-swsusp.jpg (its large 464576 bytes) ksymoops 2.4.0 on i686 2.4.19-pre5-ac3. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.19-pre5-ac3/ (default) -m /boot/System.map-2.4.19-pre5-ac3 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Warning (compare_maps): ksyms_base symbol vmalloc_to_page_R__ver_vmalloc_to_page not found in System.map. Ignoring ksyms_base entry Warning (compare_maps): mismatch on symbol usb_devfs_handle , usbcore says d8833fb4, /lib/modules/2.4.19-pre5-ac3/kernel/drivers/usb/usbcore.o says d8833a74. Ignoring /lib/modules/2.4.19-pre5-ac3/kernel/drivers/usb/usbcore.o entry c013897b *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010293 eax: ffffffff ebx: d5e32540 ecx: 00000000 edx: c14c4334 esi: 00000000 edi: 00001000 ebp: 00000001 esp: d7f77e14 ds: 0018 es: 0018 ss: 0018 Process bdflush (pid: 5, stackpage=d7f77000) Stack: d5e32540 c0138a10 d5e23540 c14c4334 00000000 6e6d6c6b 7271706f 76757573 7a797877 c14c4334 00000306 d7f77ea4 00001000 c0138bf6 c14c4334 00001000 00000001 c14c4334 d7772000 c013a1b7 c14c4334 00000306 00001000 c14c4334 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 2b 90 c8 00 00 00 69 d2 c5 4e ec c4 c1 fa 02 c1 e2 0c 03 90 >>EIP; c013897b <===== Trace; c0138a01 Trace; c0138bf6 Trace; c013a1b7 Trace; c0130269 Trace; c01167f6 <__call_console_drivers+46/60> Trace; c0130357 Trace; c0122ebe Trace; c0116ae4 Trace; c012382f Trace; c0116ae4 Trace; c0122cae Trace; c0123a0b Trace; c0123eb2 Trace; c011a989 <__run_task_queue+49/60> Trace; c013a995 Trace; c0105000 <_stext+0/0> Trace; c0105000 <_stext+0/0> Trace; c0106f66 Trace; c013a910 Code; c013897b 00000000 <_EIP>: Code; c013897b <===== 0: 2b 90 c8 00 00 00 sub 0xc8(%eax),%edx <===== Code; c0138981 6: 69 d2 c5 4e ec c4 imul $0xc4ec4ec5,%edx,%edx Code; c0138987 c: c1 fa 02 sar $0x2,%edx Code; c013898a f: c1 e2 0c shl $0xc,%edx Code; c013898d 12: 03 90 00 00 00 00 add 0x0(%eax),%edx 3 warnings issued. Results may not be reliable. Anything else you'd like to know? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/