Date: Tue, 30 Apr 2002 01:24:36 -0700 (PDT) From: Jonas Nagel <fireball@zerouptime.ch> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/37589: Kernel panics upon resume from zzz on my IBM ThinkPad 390X Message-ID: <200204300824.g3U8Oar48044@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 37589 >Category: kern >Synopsis: Kernel panics upon resume from zzz on my IBM ThinkPad 390X >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Apr 30 01:30:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Jonas Nagel >Release: FreeBSD 4.5-STABLE >Organization: - >Environment: FreeBSD hirt 4.5-STABLE FreeBSD 4.5-STABLE #1: Wed Apr 17 23:18:45 CEST 2002 root@hirt:/usr/obj/usr/src/sys/HIRT i386 >Description: When I first installed 4.5-R and occasionally updated via cvsup to -S apm suspend worked fine. I updated cvsup made world like two or one week before the date stated in the uname output and of course also recompiled the kernel. But I haven't updated for a while already then...like 5 weeks ago or something. Ever since I was unable to resume normally from sleep mode; when I unfold the notebook or pull the power lever to resume from suspend, it comes back up first, but when it tries to reinitialize the network (I guess), the kernel panics. Console Log snippet follows; as you can see first, I enter suspend and then resume: Apr 30 09:24:07 hirt /kernel: xe0: promiscuous mode disabled Apr 30 09:24:08 hirt /kernel: xe0: detached Apr 30 09:24:08 hirt /kernel: pccard: card disabled, slot 1 Apr 30 09:24:08 hirt /kernel: resumed from suspended mode (slept 00:00:18) Apr 30 09:27:05 hirt /kernel: pccard: card inserted, slot 1 Apr 30 09:27:05 hirt /kernel: Apr 30 09:27:05 hirt /kernel: Apr 30 09:27:05 hirt /kernel: Fatal trap 12: page fault while in kernel mode Apr 30 09:27:05 hirt /kernel: fault virtual address = 0x4 Apr 30 09:27:05 hirt /kernel: fault code = supervisor read, page not present Apr 30 09:27:05 hirt /kernel: instruction pointer = 0x8:0xc0164602 Apr 30 09:27:05 hirt /kernel: stack pointer = 0x10:0xc8fcbd40 Apr 30 09:27:05 hirt /kernel: frame pointer = 0x10:0xc8fcbd48 Apr 30 09:27:05 hirt /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Apr 30 09:27:05 hirt /kernel: = DPL 0, pres 1, def32 1, gran 1 Apr 30 09:27:05 hirt /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Apr 30 09:27:05 hirt /kernel: current process = 288 (dhclient) Apr 30 09:27:05 hirt /kernel: interrupt mask = Apr 30 09:27:05 hirt /kernel: trap number = 12 Apr 30 09:27:05 hirt /kernel: panic: page fault Apr 30 09:27:05 hirt /kernel: Apr 30 09:27:05 hirt /kernel: syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Apr 30 09:27:05 hirt /kernel: giving up on 1 buffers Apr 30 09:27:05 hirt /kernel: Uptime: 47m4s Apr 30 09:27:05 hirt /kernel: Automatic reboot in 15 seconds - press a key on the console to abort But I have to add a compliment here, FreeBSD crashes really fast, all within a second. >How-To-Repeat: Buy[1] an old IBM ThinkPad 390X (hopefully newer or even older models do it too) and install FreeBSD-STABLE on it. Fold it shut to invoke apm suspend or execute apm -z or zzz, then resume it unfolding it or pulling the power lever shortly. [1] Alternatively you can steal or borrow one or simply contact me :P >Fix: My best idea would be to rollback apmd, apm or kernel changes thereof to april 1st (I think then it worked yet for me) or if you can spot the bug directly, of course, go ahead, fix it. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200204300824.g3U8Oar48044>