* S3,S4 on Acer TM632XC
@ 2003-04-26 9:47 Mizu
0 siblings, 0 replies; only message in thread
From: Mizu @ 2003-04-26 9:47 UTC (permalink / raw)
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f
[-- Attachment #1: Type: text/plain, Size: 7313 bytes --]
Hi.
I was testing $SUBJ with kernel 2.5.68 (acpi ver=3D20030328)
With this kernel options: acpi_sleep=3Ds3_bios pci=3Dnoacpi
echo -n 3 >/proc/acpi/sleep
this is a debug message:
Enabling SEP on CPU 0
Back to C!
Debug: sleeping function called from illegal context
at mm/slab.c:1664
Call Trace:
[...] __might_sleep+..
kmalloc
acpi_os_allocate
acpi_ut_callocate
acpi_evalute
acpi_leave_sleep_state
acpi_system_suspend
acpi_suspend
acpi_system_write_sleep
vfs_write
sys_write
syscall_call
.................F R E E Z Y....................
Without s3_bios, there is no backlight of LCD.
++
And later, i saw this kernel messages. (Automatic sleeping function
after x=
y minutes
?)=20
kern.log:
Debug: sleeping function called from illegal context at
mm/page_alloc.c:541
Apr 25 10:24:08 mizu kernel: Call Trace:
Apr 25 10:24:08 mizu kernel: [<c011f637>] __might_sleep+0x5f/0x74
Apr 25 10:24:08 mizu kernel: [<c014aff8>] __alloc_pages+0x2c6/0x2cb
Apr 25 10:24:08 mizu kernel: [<c011ac2e>] pte_alloc_one+0x2d/0x98
Apr 25 10:24:08 mizu kernel: [<c015667b>] pte_alloc_map+0x89/0x210
Apr 25 10:24:08 mizu kernel: [<c015845c>] remap_page_range+0x113/0x30b
Apr 25 10:24:08 mizu kernel: [<c014adbc>] __alloc_pages+0x8a/0x2cb
Apr 25 10:24:08 mizu kernel: [<d0b762c0>] +0x0/0xa20 [nvidia]
Apr 25 10:24:08 mizu kernel: [<d0b762c0>] +0x0/0xa20 [nvidia]
Apr 25 10:24:08 mizu kernel: [<d0a0f41c>] KernMapAGPPages+0x37/0x71
[nvidia]
Apr 25 10:24:08 mizu kernel: [<d0b762c0>] +0x0/0xa20 [nvidia]
Apr 25 10:24:08 mizu kernel: [<d0b76300>] +0x40/0xa20 [nvidia]
Apr 25 10:24:08 mizu kernel: [<d0b762c0>] +0x0/0xa20 [nvidia]
Apr 25 10:24:08 mizu kernel: [<d0a0cffe>] nv_kern_mmap+0x1a4/0x2bf
[nvidia]
Apr 25 10:24:08 mizu kernel: [<c015bdfa>] do_mmap_pgoff+0x263/0x6a0
Apr 25 10:24:08 mizu kernel: [<c015beaa>] do_mmap_pgoff+0x313/0x6a0
Apr 25 10:24:08 mizu kernel: [<c0112e1f>] old_mmap+0xf7/0x14f
Apr 25 10:24:08 mizu kernel: [<c010c58b>] math_state_restore+0x29/0x41
Apr 25 10:24:08 mizu kernel: [<c010afaf>] syscall_call+0x7/0xb
Apr 25 10:24:08 mizu kernel:=20
Apr 25 10:25:30 mizu kernel: spurious 8259A interrupt: IRQ7.
Apr 25 10:50:05 mizu kernel: Debug: sleeping function called from
illegal context at mm/page_alloc.c:541
Apr 25 10:50:05 mizu kernel: Call Trace:
Apr 25 10:50:05 mizu kernel: [<c011f637>] __might_sleep+0x5f/0x74
Apr 25 10:50:05 mizu kernel: [<c014aff8>] __alloc_pages+0x2c6/0x2cb
Apr 25 10:50:05 mizu kernel: [<c011ac2e>] pte_alloc_one+0x2d/0x98
Apr 25 10:50:05 mizu kernel: [<c015667b>] pte_alloc_map+0x89/0x210
Apr 25 10:50:05 mizu kernel: [<c015845c>] remap_page_range+0x113/0x30b
Apr 25 10:50:05 mizu kernel: [<c014adbc>] __alloc_pages+0x8a/0x2cb
Apr 25 10:50:05 mizu kernel: [<d0b762c0>] +0x0/0xa20 [nvidia]
Apr 25 10:50:05 mizu kernel: [<d0b762c0>] +0x0/0xa20 [nvidia]
Apr 25 10:50:05 mizu kernel: [<d0a0f41c>] KernMapAGPPages+0x37/0x71
[nvidia] And later, i saw this kernel messages. (Automatic sleeping
function after x=
y minutes
?)=20
kern.log:
Debug: sleeping function called from illegal context at
mm/page_alloc.c:541
Apr 25 10:24:08 mizu kernel: Call Trace:
Apr 25 10:24:08 mizu kernel: [<c011f637>] __might_sleep+0x5f/0x74
Apr 25 10:24:08 mizu kernel: [<c014aff8>] __alloc_pages+0x2c6/0x2cb
Apr 25 10:24:08 mizu kernel: [<c011ac2e>] pte_alloc_one+0x2d/0x98
Apr 25 10:24:08 mizu kernel: [<c015667b>] pte_alloc_map+0x89/0x210
Apr 25 10:24:08 mizu kernel: [<c015845c>] remap_page_range+0x113/0x30b
Apr 25 10:24:08 mizu kernel: [<c014adbc>] __alloc_pages+0x8a/0x2cb
Apr 25 10:24:08 mizu kernel: [<d0b762c0>] +0x0/0xa20 [nvidia]
Apr 25 10:24:08 mizu kernel: [<d0b762c0>] +0x0/0xa20 [nvidia]
Apr 25 10:24:08 mizu kernel: [<d0a0f41c>] KernMapAGPPages+0x37/0x71
[nvidia]
Apr 25 10:24:08 mizu kernel: [<d0b762c0>] +0x0/0xa20 [nvidia]
Apr 25 10:24:08 mizu kernel: [<d0b76300>] +0x40/0xa20 [nvidia]
Apr 25 10:24:08 mizu kernel: [<d0b762c0>] +0x0/0xa20 [nvidia]
Apr 25 10:24:08 mizu kernel: [<d0a0cffe>] nv_kern_mmap+0x1a4/0x2bf
[nvidia]
Apr 25 10:24:08 mizu kernel: [<c015bdfa>] do_mmap_pgoff+0x263/0x6a0
Apr 25 10:24:08 mizu kernel: [<c015beaa>] do_mmap_pgoff+0x313/0x6a0
Apr 25 10:24:08 mizu kernel: [<c0112e1f>] old_mmap+0xf7/0x14f
Apr 25 10:24:08 mizu kernel: [<c010c58b>] math_state_restore+0x29/0x41
Apr 25 10:24:08 mizu kernel: [<c010afaf>] syscall_call+0x7/0xb
Apr 25 10:24:08 mizu kernel:=20
Apr 25 10:25:30 mizu kernel: spurious 8259A interrupt: IRQ7.
Apr 25 10:50:05 mizu kernel: Debug: sleeping function called from
illegal context at mm/page_alloc.c:541
Apr 25 10:50:05 mizu kernel: Call Trace:
Apr 25 10:50:05 mizu kernel: [<c011f637>] __might_sleep+0x5f/0x74
Apr 25 10:50:05 mizu kernel: [<c014aff8>] __alloc_pages+0x2c6/0x2cb
Apr 25 10:50:05 mizu kernel: [<c011ac2e>] pte_alloc_one+0x2d/0x98
Apr 25 10:50:05 mizu kernel: [<c015667b>] pte_alloc_map+0x89/0x210
Apr 25 10:50:05 mizu kernel: [<c015845c>] remap_page_range+0x113/0x30b
Apr 25 10:50:05 mizu kernel: [<c014adbc>] __alloc_pages+0x8a/0x2cb
Apr 25 10:50:05 mizu kernel: [<d0b762c0>] +0x0/0xa20 [nvidia]
Apr 25 10:50:05 mizu kernel: [<d0b762c0>] +0x0/0xa20 [nvidia]
Apr 25 10:50:05 mizu kernel: [<d0a0f41c>] KernMapAGPPages+0x37/0x71
[nvidia]
Apr 25 10:50:05 mizu kernel: [<d0b762c0>] +0x0/0xa20 [nvidia]
Apr 25 10:50:05 mizu kernel: [<d0b76300>] +0x40/0xa20 [nvidia]
Apr 25 10:50:05 mizu kernel: [<d0b762c0>] +0x0/0xa20 [nvidia]
Apr 25 10:50:05 mizu kernel: [<d0a0cffe>] nv_kern_mmap+0x1a4/0x2bf
[nvidia]
Apr 25 10:50:05 mizu kernel: [<c015bdfa>] do_mmap_pgoff+0x263/0x6a0
Apr 25 10:50:05 mizu kernel: [<c015beaa>] do_mmap_pgoff+0x313/0x6a0
Apr 25 10:50:05 mizu kernel: [<c0112e1f>] old_mmap+0xf7/0x14f
Apr 25 10:50:05 mizu kernel: [<c010c58b>] math_state_restore+0x29/0x41
Apr 25 10:50:05 mizu kernel: [<c010afaf>] syscall_call+0x7/0xb
Apr 25 10:50:05 mizu kernel:=20
=2E
++
Sometimes S4 works good (with same Trace messages ;( ), but sometimes
when =
i try to S4, there was something like ide-disk BUG. I dont have
that message, becouse there was only console message + FREEZY !
I've ALI chipset:
ALI15X3: IDE controller at PCI slot 00:10.0
ALI15X3: chipset revision 196
ALI15X3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x2480-0x2487, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x2488-0x248f, BIOS settings: hdc:pio, hdd:pio
++
On the pci, there is this device:
00:11.0 Bridge: ALi Corporation M7101 PMU
Subsystem: Acer Incorporated [ALI]: Unknown device 102b
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr-=
Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=3Dmedium
>TAbort- =
<TAbort- <MAbort- >SERR- <PERR-
I read in kernel src: pci/devices.h:
DEVICE(1025,7101,"M7101 PCI PMU Power Management Controller")
=2E...
Do i need this device to correct Power Management ?
---END OF QUESTIONS.. ;)
Thx=20
mizu
--
--
_______M_i_z_u________
--> Linux Friendly <--
[-> E-mail:michal-VaXaUECoPuY@public.gmane.org
[-> ICQ:97165392
[-> WWW: http://www.mizu.sk
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-04-26 9:47 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-04-26 9:47 S3,S4 on Acer TM632XC Mizu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox