I can also confirm that newest snapshot works now.
On Thu, Jun 26, 2014 at 7:45 AM, Nils R m...@hxgn.net wrote:
Works now with the latest snapshot (dsdt.c rev. 1.211), thanks!
I know on my laptop no acpi meant doesn't work. My saving grace is I
always keep a kernel from the previous snapshot I tried as obsd. So if
bsd doesn't work, I just boot from that. Do you have an older snapshot
kernel you can tell tech support to boot into?
On Thu, Jun 26, 2014 at 7:36 PM, Scott
Unfortunately, not. It was a fresh install from a CD image to a hard
drive which I then shipped to the ISP for installation, which replaced a
failing drive in my machine co-located there.
In any event, bypassing acpi in ukc got the machine up again, and I was
able to upgrade to the latest
On 2014-06-26, Scott Vanderbilt li...@datagenic.com wrote:
Having done a little man page reading on boot-time configuration, I
learned about the existence of ukc. I'm wondering whether something like
ukc disable acpi0
might circumvent the kernel panic and allow the boot to successfully
On 2014-06-26, Scott Vanderbilt li...@datagenic.com wrote:
Having done a little man page reading on boot-time configuration, I
learned about the existence of ukc. I'm wondering whether something like
ukc disable acpi0
might circumvent the kernel panic and allow the boot to
On 6/27/2014 12:10 PM, Stuart Henderson wrote:
On 2014-06-26, Scott Vanderbilt li...@datagenic.com wrote:
Having done a little man page reading on boot-time configuration, I
learned about the existence of ukc. I'm wondering whether something like
ukc disable acpi0
might circumvent the
On Fri, Jun 27, 2014 at 01:15:59PM -0600, Theo de Raadt wrote:
On 2014-06-26, Scott Vanderbilt li...@datagenic.com wrote:
Having done a little man page reading on boot-time configuration, I
learned about the existence of ukc. I'm wondering whether something like
ukc disable acpi0
On Fri, Jun 27, 2014 at 12:37:33PM -0700, Scott Vanderbilt wrote:
On 6/27/2014 12:10 PM, Stuart Henderson wrote:
On 2014-06-26, Scott Vanderbilt li...@datagenic.com wrote:
Having done a little man page reading on boot-time configuration, I
learned about the existence of ukc. I'm wondering
On 6/27/14, Theo de Raadt dera...@cvs.openbsd.org wrote:
On 2014-06-26, Scott Vanderbilt li...@datagenic.com wrote:
Having done a little man page reading on boot-time configuration, I
learned about the existence of ukc. I'm wondering whether something
like
ukc disable acpi0
might
Works now with the latest snapshot (dsdt.c rev. 1.211), thanks!
I have this exact same kernel panic. Unfortunately, it's occurring on a
host at a remote co-lo. Does anyone know a way that I can get the
on-site tech to suppress the assertion by way of some boot-time
configuration? Then at least I can get this machine up and running so I
can immediately
Having done a little man page reading on boot-time configuration, I
learned about the existence of ukc. I'm wondering whether something like
ukc disable acpi0
might circumvent the kernel panic and allow the boot to successfully
complete. I'm hoping that since this is a server, ACPI is
Scott Vanderbilt [li...@datagenic.com] wrote:
Having done a little man page reading on boot-time configuration, I learned
about the existence of ukc. I'm wondering whether something like
ukc disable acpi0
That or disable acpi
might circumvent the kernel panic and allow the boot to
My system panic's from the KASSERT() call at line 2269 after dsdt.c was
updated to 1.210.
All I have is the basic panic message and the dmesg from the last known
working snapshot kernel. I tried to get more information but my USB
keyboard does not work in the kernel debugger, and my on-board
Am 25.06.2014 17:05 schrieb Jason Crawford ja...@purebsd.net:
My system panic's from the KASSERT() call at line 2269 after dsdt.c was
updated to 1.210.
All I have is the basic panic message and the dmesg from the last known
working snapshot kernel. I tried to get more information but my
15 matches
Mail list logo
