Re: Fwd: Activating Suspend/Resume on FreeBSD 10.1

2015-02-17 Thread Kevin Oberman
On Tue, Feb 17, 2015 at 7:40 AM, John Baldwin j...@freebsd.org wrote:

 On Friday, January 30, 2015 12:37:10 pm Kevin Oberman wrote:
  My experience is the opposite.  With KMS I could run with VESA and
 without
  it I needed to pull VESA from my kernel.
 
  As of today I am running fine with KMS, i915, and vt(4) with a standard
  GENERIC 10-STABLE kernel. I was running KMS and vt(4) well before they
 were
  MFCed, so I don't remember when I stopped adding nooptions VESA, but I
  definitely used to need it to make suspect/resume work and don't any
 longer.
 
  In any case, trying  kernel without VESA is a good idea.

 FYI, VESA only applies to sc(4).  It is ignored for vt(4).  That is why it
 works with vt(4).

 --
 John Baldwin


I suspected that was the case, but did not recall for sure. Thanks for the
confirmation, though it does not help with the problem reported.
--
Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org


Re: Fwd: Activating Suspend/Resume on FreeBSD 10.1

2015-02-17 Thread John Baldwin
On Friday, January 30, 2015 12:37:10 pm Kevin Oberman wrote:
 My experience is the opposite.  With KMS I could run with VESA and without
 it I needed to pull VESA from my kernel.
 
 As of today I am running fine with KMS, i915, and vt(4) with a standard
 GENERIC 10-STABLE kernel. I was running KMS and vt(4) well before they were
 MFCed, so I don't remember when I stopped adding nooptions VESA, but I
 definitely used to need it to make suspect/resume work and don't any longer.
 
 In any case, trying  kernel without VESA is a good idea.

FYI, VESA only applies to sc(4).  It is ignored for vt(4).  That is why it 
works with vt(4).

-- 
John Baldwin
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org


Re: Fwd: Activating Suspend/Resume on FreeBSD 10.1

2015-01-30 Thread Kevin Oberman
On Thu, Jan 29, 2015 at 12:16 PM, Anthony Jenkins anthony.b.jenk...@att.net
 wrote:

 Ahhh... good ol' VESA driver:

 Jan 29 23:06:57 MyBSD kernel: Fatal trap 12: page fault while in
 kernel mode
 Jan 29 23:06:57 MyBSD kernel: cpuid = 0; apic id = 00
 Jan 29 23:06:57 MyBSD kernel: fault virtual address= 0x378
 Jan 29 23:06:57 MyBSD kernel: fault code= supervisor read
 data, page not present
 Jan 29 23:06:57 MyBSD kernel: instruction pointer=
 0x20:0x809149e1
 Jan 29 23:06:57 MyBSD kernel: stack pointer=
 0x28:0xfe011b3b9480
 Jan 29 23:06:57 MyBSD kernel: frame pointer=
 0x28:0xfe011b3b9500
 Jan 29 23:06:57 MyBSD kernel: code segment= base 0x0, limit
 0xf, type 0x1b
 Jan 29 23:06:57 MyBSD kernel: = DPL 0, pres 1, long 1, def32 0, gran 1
 Jan 29 23:06:57 MyBSD kernel: processor eflags= interrupt
 enabled, resume, IOPL = 0
 Jan 29 23:06:57 MyBSD kernel: current process= 996 (acpiconf)
 Jan 29 23:06:57 MyBSD kernel: trap number= 12
 Jan 29 23:06:57 MyBSD kernel: panic: page fault
 Jan 29 23:06:57 MyBSD kernel: cpuid = 0
 Jan 29 23:06:57 MyBSD kernel: KDB: stack backtrace:
 Jan 29 23:06:57 MyBSD kernel: #0 0x80963000 at
 kdb_backtrace+0x60
 Jan 29 23:06:57 MyBSD kernel: #1 0x80928125 at panic+0x155
 Jan 29 23:06:57 MyBSD kernel: #2 0x80d24f1f at trap_fatal+0x38f
 Jan 29 23:06:57 MyBSD kernel: #3 0x80d25238 at
 trap_pfault+0x308
 Jan 29 23:06:57 MyBSD kernel: #4 0x80d2489a at trap+0x47a
 Jan 29 23:06:57 MyBSD kernel: #5 0x80d0a782 at calltrap+0x8
 Jan 29 23:06:57 MyBSD kernel: #6 0x80d96ed5 at
 vesa_bios_save_restore+0x95
 Jan 29 23:06:57 MyBSD kernel: #7 0x80e02296 at vga_suspend+0xa6
 Jan 29 23:06:57 MyBSD kernel: #8 0x80e0258d at
 isavga_suspend+0x1d
 Jan 29 23:06:57 MyBSD kernel: #9 0x8095b204 at
 bus_generic_suspend+0x64
 Jan 29 23:06:57 MyBSD kernel: #10 0x8095b204 at
 bus_generic_suspend+0x64
 Jan 29 23:06:57 MyBSD kernel: #11 0x8095b204 at
 bus_generic_suspend+0x64
 Jan 29 23:06:57 MyBSD kernel: #12 0x8067e97d at
 pci_suspend+0x5d
 Jan 29 23:06:57 MyBSD kernel: #13 0x8095b204 at
 bus_generic_suspend+0x64
 Jan 29 23:06:57 MyBSD kernel: #14 0x8095b204 at
 bus_generic_suspend+0x64
 Jan 29 23:06:57 MyBSD kernel: #15 0x8035bc7f at
 acpi_suspend+0xf
 Jan 29 23:06:57 MyBSD kernel: #16 0x8095b204 at
 bus_generic_suspend+0x64
 Jan 29 23:06:57 MyBSD kernel: #17 0x8095b204 at
 bus_generic_suspend+0x64
 Jan 29 23:06:57 MyBSD kernel: Uptime: 1m7s


 A frequent recommendation I see is to remove VESA support from your
 kernel, apparently it has suspend/resume issues.  I don't think
 FreeBSD-10.1 uses the KMS graphics drivers by default, and I /thought/
 the recommendation was for KMS systems.  Shouldn't hurt to build a
 kernel without 'options VESA' and see what happens...

 Anthony


My experience is the opposite.  With KMS I could run with VESA and without
it I needed to pull VESA from my kernel.

As of today I am running fine with KMS, i915, and vt(4) with a standard
GENERIC 10-STABLE kernel. I was running KMS and vt(4) well before they were
MFCed, so I don't remember when I stopped adding nooptions VESA, but I
definitely used to need it to make suspect/resume work and don't any longer.

In any case, trying  kernel without VESA is a good idea.
--
Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org


Re: Fwd: Activating Suspend/Resume on FreeBSD 10.1

2015-01-29 Thread Anthony Jenkins
On 01/29/2015 08:42 AM, Mohammad Najafi wrote:
 Dear Members:

 ​acpiconf -s 3 results in kernel panic.​

 For more info, I have attached my FreeBSD kernel boot message

I don't see anything in the boot messages about a panic...

Some suggestions:

 - You can try to capture a kernel dump.  See
https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#kerneldebug-obtain
 - Try the hints in DebuggingSuspendResume on the FreeBSD wiki.  See
https://wiki.freebsd.org/SuspendResume and
https://wiki.freebsd.org/DebuggingSuspendResume
 - Try running FreeBSD-CURRENT.  You can boot it off a USB flash drive
and try suspend/resume.

Also read the FreeBSD ACPI stuff at
https://www.freebsd.org/doc/handbook/acpi-overview.html .

Anthony Jenkins

 Any help is highly welcome.

 Thanks in advance.
 M.Najafi


 ___
 freebsd-acpi@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
 To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org

___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org

Re: Fwd: Activating Suspend/Resume on FreeBSD 10.1

2015-01-29 Thread Adrian Chadd
Hi,

Please try a freebsd-head snapshot and see if that resolves your issue.

The fixes may not have been backported.

Thanks!

-a


On 29 January 2015 at 07:07, Anthony Jenkins anthony.b.jenk...@att.net wrote:
 On 01/29/2015 08:42 AM, Mohammad Najafi wrote:
 Dear Members:

 acpiconf -s 3 results in kernel panic.

 For more info, I have attached my FreeBSD kernel boot message

 I don't see anything in the boot messages about a panic...

 Some suggestions:

  - You can try to capture a kernel dump.  See
 https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#kerneldebug-obtain
  - Try the hints in DebuggingSuspendResume on the FreeBSD wiki.  See
 https://wiki.freebsd.org/SuspendResume and
 https://wiki.freebsd.org/DebuggingSuspendResume
  - Try running FreeBSD-CURRENT.  You can boot it off a USB flash drive
 and try suspend/resume.

 Also read the FreeBSD ACPI stuff at
 https://www.freebsd.org/doc/handbook/acpi-overview.html .

 Anthony Jenkins

 Any help is highly welcome.

 Thanks in advance.
 M.Najafi


 ___
 freebsd-acpi@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
 To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org

 ___
 freebsd-acpi@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
 To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org


Re: Fwd: Activating Suspend/Resume on FreeBSD 10.1

2015-01-29 Thread Mohammad Najafi
Hi,

I have tried FreeBSD 10.1 boot image and it almost works nicely. However,
my installed FreeBSD 10.1 does not suspend and gives kernel panic as you
can see in the attached kernel log (lines 265 to 313).

Thanks,
M.Najafi


On Thu, Jan 29, 2015 at 6:02 PM, Adrian Chadd adr...@freebsd.org wrote:

 Hi,

 Please try a freebsd-head snapshot and see if that resolves your issue.

 The fixes may not have been backported.

 Thanks!

 -a


 On 29 January 2015 at 07:07, Anthony Jenkins anthony.b.jenk...@att.net
 wrote:
  On 01/29/2015 08:42 AM, Mohammad Najafi wrote:
  Dear Members:
 
  acpiconf -s 3 results in kernel panic.
 
  For more info, I have attached my FreeBSD kernel boot message
 
  I don't see anything in the boot messages about a panic...
 
  Some suggestions:
 
   - You can try to capture a kernel dump.  See
 
 https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#kerneldebug-obtain
   - Try the hints in DebuggingSuspendResume on the FreeBSD wiki.  See
  https://wiki.freebsd.org/SuspendResume and
  https://wiki.freebsd.org/DebuggingSuspendResume
   - Try running FreeBSD-CURRENT.  You can boot it off a USB flash drive
  and try suspend/resume.
 
  Also read the FreeBSD ACPI stuff at
  https://www.freebsd.org/doc/handbook/acpi-overview.html .
 
  Anthony Jenkins
 
  Any help is highly welcome.
 
  Thanks in advance.
  M.Najafi
 
 
  ___
  freebsd-acpi@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
  To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
 
  ___
  freebsd-acpi@freebsd.org mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
  To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org



messages.suspend
Description: Binary data
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org

Re: Fwd: Activating Suspend/Resume on FreeBSD 10.1

2015-01-29 Thread Anthony Jenkins
Ahhh... good ol' VESA driver:

Jan 29 23:06:57 MyBSD kernel: Fatal trap 12: page fault while in
kernel mode
Jan 29 23:06:57 MyBSD kernel: cpuid = 0; apic id = 00
Jan 29 23:06:57 MyBSD kernel: fault virtual address= 0x378
Jan 29 23:06:57 MyBSD kernel: fault code= supervisor read
data, page not present
Jan 29 23:06:57 MyBSD kernel: instruction pointer=
0x20:0x809149e1
Jan 29 23:06:57 MyBSD kernel: stack pointer=
0x28:0xfe011b3b9480
Jan 29 23:06:57 MyBSD kernel: frame pointer=
0x28:0xfe011b3b9500
Jan 29 23:06:57 MyBSD kernel: code segment= base 0x0, limit
0xf, type 0x1b
Jan 29 23:06:57 MyBSD kernel: = DPL 0, pres 1, long 1, def32 0, gran 1
Jan 29 23:06:57 MyBSD kernel: processor eflags= interrupt
enabled, resume, IOPL = 0
Jan 29 23:06:57 MyBSD kernel: current process= 996 (acpiconf)
Jan 29 23:06:57 MyBSD kernel: trap number= 12
Jan 29 23:06:57 MyBSD kernel: panic: page fault
Jan 29 23:06:57 MyBSD kernel: cpuid = 0
Jan 29 23:06:57 MyBSD kernel: KDB: stack backtrace:
Jan 29 23:06:57 MyBSD kernel: #0 0x80963000 at
kdb_backtrace+0x60
Jan 29 23:06:57 MyBSD kernel: #1 0x80928125 at panic+0x155
Jan 29 23:06:57 MyBSD kernel: #2 0x80d24f1f at trap_fatal+0x38f
Jan 29 23:06:57 MyBSD kernel: #3 0x80d25238 at trap_pfault+0x308
Jan 29 23:06:57 MyBSD kernel: #4 0x80d2489a at trap+0x47a
Jan 29 23:06:57 MyBSD kernel: #5 0x80d0a782 at calltrap+0x8
Jan 29 23:06:57 MyBSD kernel: #6 0x80d96ed5 at
vesa_bios_save_restore+0x95
Jan 29 23:06:57 MyBSD kernel: #7 0x80e02296 at vga_suspend+0xa6
Jan 29 23:06:57 MyBSD kernel: #8 0x80e0258d at
isavga_suspend+0x1d
Jan 29 23:06:57 MyBSD kernel: #9 0x8095b204 at
bus_generic_suspend+0x64
Jan 29 23:06:57 MyBSD kernel: #10 0x8095b204 at
bus_generic_suspend+0x64
Jan 29 23:06:57 MyBSD kernel: #11 0x8095b204 at
bus_generic_suspend+0x64
Jan 29 23:06:57 MyBSD kernel: #12 0x8067e97d at pci_suspend+0x5d
Jan 29 23:06:57 MyBSD kernel: #13 0x8095b204 at
bus_generic_suspend+0x64
Jan 29 23:06:57 MyBSD kernel: #14 0x8095b204 at
bus_generic_suspend+0x64
Jan 29 23:06:57 MyBSD kernel: #15 0x8035bc7f at acpi_suspend+0xf
Jan 29 23:06:57 MyBSD kernel: #16 0x8095b204 at
bus_generic_suspend+0x64
Jan 29 23:06:57 MyBSD kernel: #17 0x8095b204 at
bus_generic_suspend+0x64
Jan 29 23:06:57 MyBSD kernel: Uptime: 1m7s


A frequent recommendation I see is to remove VESA support from your
kernel, apparently it has suspend/resume issues.  I don't think
FreeBSD-10.1 uses the KMS graphics drivers by default, and I /thought/
the recommendation was for KMS systems.  Shouldn't hurt to build a
kernel without 'options VESA' and see what happens...

Anthony

On 01/29/2015 02:43 PM, Mohammad Najafi wrote:
 Hi,

 I have tried FreeBSD 10.1 boot image and it almost works nicely.
 However, my installed FreeBSD 10.1 does not suspend and gives kernel
 panic as you can see in the attached kernel log (lines 265 to 313).

 Thanks,
 M.Najafi


 On Thu, Jan 29, 2015 at 6:02 PM, Adrian Chadd adr...@freebsd.org
 mailto:adr...@freebsd.org wrote:

 Hi,

 Please try a freebsd-head snapshot and see if that resolves your
 issue.

 The fixes may not have been backported.

 Thanks!

 -a


 On 29 January 2015 at 07:07, Anthony Jenkins
 anthony.b.jenk...@att.net mailto:anthony.b.jenk...@att.net wrote:
  On 01/29/2015 08:42 AM, Mohammad Najafi wrote:
  Dear Members:
 
  acpiconf -s 3 results in kernel panic.
 
  For more info, I have attached my FreeBSD kernel boot message
 
  I don't see anything in the boot messages about a panic...
 
  Some suggestions:
 
   - You can try to capture a kernel dump.  See
 
 
 https://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html#kerneldebug-obtain
   - Try the hints in DebuggingSuspendResume on the FreeBSD wiki.  See
  https://wiki.freebsd.org/SuspendResume and
  https://wiki.freebsd.org/DebuggingSuspendResume
   - Try running FreeBSD-CURRENT.  You can boot it off a USB flash
 drive
  and try suspend/resume.
 
  Also read the FreeBSD ACPI stuff at
  https://www.freebsd.org/doc/handbook/acpi-overview.html .
 
  Anthony Jenkins
 
  Any help is highly welcome.
 
  Thanks in advance.
  M.Najafi
 
 
  ___
  freebsd-acpi@freebsd.org mailto:freebsd-acpi@freebsd.org
 mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
  To unsubscribe, send any mail to
 freebsd-acpi-unsubscr...@freebsd.org