Re: ACPI errors

From: Doug White (dwhite_at_gumbysoft.com)
Date: 01/31/05

  • Next message: Doug White: "Re: [current tinderbox] failure on sparc64/sparc64"
    Date: Mon, 31 Jan 2005 12:04:02 -0800 (PST)
    To: Filippo Forti <filippo.forti@fastwebnet.it>
    
    

    On Sun, 30 Jan 2005, Filippo Forti wrote:

    > Hi,
    > I've started getting this error randomly since about 15 days ago.
    > I've cvsupped yesterday but the error still comes up sometimes.
    > The system is a Dell Inspiron 5100.

    This would be worthy to post to freebsd-acpi@freebsd.org. Do you
    regularly run with WITNESS on purpose?

    >
    >
    > Sleeping on "acsem" with the following non-sleepable
    > locks held:
    > exclusive sleep mutex acpica subsystem lock r = 0 (0xc235c9c0) locked @
    > /usr/src/sys/modules/acpi/acpi/../../../dev/acpica/Osd/O
    > sdSynch.c:360
    > KDB: stack backtrace:
    > kdb_backtrace(c09dbe14,e32beb84,1,1,1) at kdb_backtrace+0x2f
    > witness_warn(5,c235cb40,c08cb115,c0baf5ca,c065b845) at
    > witness_warn+0x1bb
    > msleep(c235cb40,c235cb40,100,c0baf5ca,0) at msleep+0x58
    > AcpiOsWaitSemaphore(c235cb40,1,ffff,8,15) at AcpiOsWaitSemaphore+0x1fb
    > AcpiUtAcquireMutex(7,1,0,0,0) at AcpiUtAcquireMutex+0x8f
    > AcpiDisableGpe(0,1c,1,c227a7d1,c239f180) at AcpiDisableGpe+0x23
    > EcGpeHandler(c239f180,1,0,8,102f) at EcGpeHandler+0x3f
    > AcpiEvGpeDispatch(c2380f50,1c,c227a7dd,27fa10,4) at
    > AcpiEvGpeDispatch+0xc4
    > AcpiEvGpeDetect(c230bc20,0,c230bc20,e32bed14,c064f39e) at
    > AcpiEvGpeDetect+0x12f
    > AcpiEvSciXruptHandler(c230bc20,0,c08c8452,256,c0990c60) at
    > AcpiEvSciXruptHandler+0x2a
    > ithread_loop(c2279880,e32bed48,c08c8251,30e,c2279880) at
    > ithread_loop+0x157
    > fork_exit(c064f247,c2279880,e32bed48) at fork_exit+0xc7
    > fork_trampoline() at fork_trampoline+0x8
    > --- trap 0x1, eip = 0, esp = 0xe32bed7c, ebp = 0 ---
    >
    > I'm running with a modified DSDT (downloaded from acpi.sf.net) which I used on
    > linux and FreeBSD since the beginning.
    > Is this normal/not dangerous?
    >
    > Thanks in advance
    >
    > Regards
    > Filippo
    > _______________________________________________
    > freebsd-current@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-current
    > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    >

    -- 
    Doug White                    |  FreeBSD: The Power to Serve
    dwhite@gumbysoft.com          |  www.FreeBSD.org
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    

  • Next message: Doug White: "Re: [current tinderbox] failure on sparc64/sparc64"

    Relevant Pages

    • Re: Panic on suspend
      ... Filippo Forti wrote: ... > FreeBSD is -CURRENT from Monday. ... > I'm using a modified DSDT which used to work before I updated on Monday. ... > dmesg from after reboot is attacched. ...
      (freebsd-current)
    • Re: Panic on suspend
      ... On Tuesday 01 March 2005 03:30 pm, Filippo Forti wrote: ... > laptop. ... FreeBSD is -CURRENT from Monday. ... > I'm using a modified DSDT which used to work before I updated on Monday. ...
      (freebsd-current)