On Tue, Feb 17, 2015 at 7:40 AM, John Baldwin 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, a
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
On Thu, Jan 29, 2015 at 12:16 PM, Anthony Jenkins 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
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= supe
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 wrote:
> Hi,
>
> Please
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 wrote:
> On 01/29/2015 08:42 AM, Mohammad Najafi wrote:
>> Dear Members:
>>
>> "acpiconf -s 3" results in kernel panic.
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. S
