Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 14 May 2002 11:52:26 +0200 (CEST)
From:      Daniel Lang <dl@leo.org>
To:        FreeBSD-gnats-submit@FreeBSD.org
Subject:   kern/38070: 4.6-PRERELEASE panics on resume on Fujitsu Lifebook E-6xxx
Message-ID:  <20020514095226.8224D139F1@atrbg11.informatik.tu-muenchen.de>

next in thread | raw e-mail | index | archive | help

>Number:         38070
>Category:       kern
>Synopsis:       4.6-PRERELEASE panics on resume on Fujitsu Lifebook E-6xxx
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue May 14 03:00:03 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Daniel Lang <dl@leo.org>
>Release:        FreeBSD 4.6-PRERELEASE i386
>Organization:
LEO
>Environment:
System: FreeBSD spot.empire.trek.org 4.6-PRERELEASE FreeBSD 4.6-PRERELEASE #3: Thu May 2 15:03:24 CEST 2002 root@spot.empire.trek.org:/usr/obj/usr/src/sys/SPOT i386

related devices in kernel and probed:
[..]
apm0: <APM BIOS> on motherboard                                                    
apm: found APM BIOS v1.2, connected at v1.2                                        
[..]                                                                               
ichsmb0: <SMBus controller> port 0x1c00-0x1c1f irq 11 at device 31.3 on pci0       
[..]

>Description:

If I suspend the system with 'zzz' or if it suspends itself
it cannot be resumed. An attempt to resume it shows the following
behaviour:
  - Display keeps beeing switched off
  - Heavy disk activity for quite a while
  - System reboots (BIOS init etc)
  - FreeBSD boots, fscks
  - savecore finds crash dump on the dump-device

This explains the disk activity, which is due to writing the
crash dump.

I've analysed the crash dump with gdb, but its probably
useless since, a second trap is caught during processing of
the first. Here is the information anyway:

IdlePTD at phsyical address 0x00471000
initial pcb at physical address 0x003ac2e0
panicstr: page fault
panic messages:
---
Fatal trap 18: integer divide fault while in kernel mode
instruction pointer     = 0x58:0x49cd
stack pointer           = 0x10:0xc035f380
frame pointer           = 0x10:0x58
code segment            = base 0xc00f0000, limit 0xffff, type 0x1b
                        = DPL 0, pres 1, def32 0, gran 0
processor eflags        = interrupt enabled, IOPL = 0
current process         = Idle
interrupt mask          = 
trap number             = 18
panic: integer divide fault

syncing disks... 

Fatal trap 12: page fault while in kernel mode
[ info about this omitted ]

Stack-Trace:
(kgdb) bt
#0  dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487
#1  0xc018be57 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:316
#2  0xc018c27c in poweroff_wait (junk=0xc035642c, howto=-1070244017)
    at /usr/src/sys/kern/kern_shutdown.c:595
#3  0xc02f77ba in trap_fatal (frame=0xc035f188, eva=48)
    at /usr/src/sys/i386/i386/trap.c:966
#4  0xc02f748d in trap_pfault (frame=0xc035f188, usermode=0, eva=48)
    at /usr/src/sys/i386/i386/trap.c:859
#5  0xc02f7077 in trap (frame={tf_fs = -1070268400, tf_es = 16, tf_ds = 16, 
      tf_edi = -1069757696, tf_esi = 0, tf_ebp = -1070206512, 
      tf_isp = -1070206540, tf_ebx = -1070094084, tf_edx = 6867008, 
      tf_ecx = 2, tf_eax = 0, tf_trapno = 12, tf_err = 0, 
      tf_eip = -1071059460, tf_cs = 8, tf_eflags = 66050, tf_esp = 0, 
      tf_ss = 0}) at /usr/src/sys/i386/i386/trap.c:458
#6  0xc028edfc in acquire_lock (lk=0xc037a8fc)
    at /usr/src/sys/ufs/ffs/ffs_softdep.c:266
#7  0xc029341e in softdep_fsync_mountdev (vp=0xcd3a0b40)
    at /usr/src/sys/ufs/ffs/ffs_softdep.c:4024
#8  0xc029760e in ffs_fsync (ap=0xc035f244)
    at /usr/src/sys/ufs/ffs/ffs_vnops.c:134
#9  0xc02962cf in ffs_sync (mp=0xc1639200, waitfor=2, cred=0xc0e3a900, 
    p=0xc03ccb00) at vnode_if.h:558
#10 0xc01bb5d3 in sync (p=0xc03ccb00, uap=0x0)
    at /usr/src/sys/kern/vfs_syscalls.c:576
#11 0xc018bbf2 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:235
#12 0xc018c27c in poweroff_wait (junk=0xc035642c, howto=-1070244054)
    at /usr/src/sys/kern/kern_shutdown.c:595
#13 0xc02f77ba in trap_fatal (frame=0xc035f340, eva=0)
    at /usr/src/sys/i386/i386/trap.c:966
#14 0xc02f71c3 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 96, tf_edi = 0, 
      tf_esi = 0, tf_ebp = 88, tf_isp = -1070206100, tf_ebx = 1, tf_edx = 0, 
      tf_ecx = 2, tf_eax = 7, tf_trapno = 18, tf_err = 0, tf_eip = 18893, 
      tf_cs = 88, tf_eflags = 514, tf_esp = 5261840, tf_ss = -65520})
    at /usr/src/sys/i386/i386/trap.c:628
#15 0x49cd in ?? ()
cannot read proc at 0
(kgdb) 


What could be a hint to the problem, if I call 'apm'
I get (among useful information) an error message:
[..]
Failed to get the resume timer: APM error0xc
[..]

See also: Message-ID:  <20020513160556.GE621@atrbg11.informatik.tu-muenchen.de>
on <freebsd-mobile@freebsd.org>


>How-To-Repeat:
 - Install 4.6-PRERELEASE on a Fujitsu Lifebook E-6624
 - suspend the system
 - try to resume it

 Perfectly reproducable on my hardware.

>Fix:

 Don't suspend. :-/

>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?20020514095226.8224D139F1>