[Fwd: Re: amd64 suspend/resume broken on current]

From: Alexander Motin <mav_at_FreeBSD.org>
Date: Sat, 09 May 2009 16:55:40 +0300
-------- Original Message --------
Subject: Re: amd64 suspend/resume broken on current
Date: Fri, 8 May 2009 21:52:45 +0200
From: Guy Brand <gb_at_unistra.fr>
Organization: Direction Informatique, Université de Strasbourg, France
To: Alexander Motin <mav_at_mavhome.dp.ua>
References: <gtslv6$ufq$1_at_FreeBSD.cs.nctu.edu.tw> 
<4A021118.2030106_at_mavhome.dp.ua> <20090508111024.GK4922_at_unistra.fr> 
<4A041DC2.90106_at_mavhome.dp.ua> <20090508144551.GA1599_at_unistra.fr> 
<4A047925.6060301_at_mavhome.dp.ua>

Guy Brand wrote:
 > Alexander Motin wrote:
> > Done. No firewire issue of course, but a kernel panic on resume. Bad
> > karma since yesterday :-)
> 
> Where is this panic happens now?

Just after resuming:

   Fatal trap 12: page fault while in kernel mode
   ...
   current process = 1415 (acpiconf)

The backtrace says:

   intr_execute_handlers() at intr_execute_handlers+0x21
   lapic_handle_intr() at lapic_handle_intr+0x37
   Xapic_isr1() at Xapic_isr1+0xa4

   acpi_sleep_machdep() at acpi_sleep_machdep+0x3b2
   acpi_EnterSleepState() at acpi_EnterSleepState+0x3fe
   acpi_AckSleepState() at acpi_AckSleepState+0x163
   devfs_ioctl() at devfs_ioctl_f+0x77
   kern_ioctl() at kern_ioctl+0xb0
   ioctl() at ioctl+0xfd
   syscall() at syscal+0x246
   Xfast_syscall() at Xfast_syscall+0xd0


-- 
   bug


-- 
Alexander Motin
Received on Sat May 09 2009 - 12:55:49 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:47 UTC