on 11/12/2011 23:12 Lev Serebryakov said the following:
Hello, Andriy.
You wrote 11 декабря 2011 г., 23:12:34:
Is it true? Is it possible to have FreeBSD/amd64 without ACPI?
It seems, that device mptable in kernel config helps.
Why is it not in GENERIC kernel?
Just a guess, maybe
FWIW, it should be easy to ship a config file for that soekris, which
just does:
include GENERIC
device mptable
It may be worthwhile at least considering this (along with a couple of
comments explaining why the default kernel doesn't work on the soekris
board) for 9.0.
Question: can you load
detect some
devices without any errors or panics.
This box has one big difference from billions other Intel-based
boxes on market: it has very special BIOS without ACPI at all. Someone
says, that it could be reason why FreeBSD/amd64 could not be boot on
this box.
Is it true? Is it possible to have
run on it without
problems.
But FreeBSD/amd64 can not. It stops after kernel detect some
devices without any errors or panics.
This box has one big difference from billions other Intel-based
boxes on market: it has very special BIOS without ACPI at all. Someone
says, that it could be reason
On Saturday, October 08, 2011 5:29:12 am Henri Hennebert wrote:
Hello,
On my configuration, If I boot 9.0-BETA3 (r225759) without ACPI, the
kernel encounter a page fault before the end of the boot.
A photo of the screen can be found at:
http://verbier.restart.be/xfer/dsc00042.jpg
Hello,
On my configuration, If I boot 9.0-BETA3 (r225759) without ACPI, the
kernel encounter a page fault before the end of the boot.
A photo of the screen can be found at:
http://verbier.restart.be/xfer/dsc00042.jpg
Henri
___
freebsd-current
Hello,
I'm running 9.0-CURRENT on a MacbookPro 5,5. Following a recent update,
I found that the acpi battery functionality had stopped working. I
suspect, given the nature of it, that other people may have seen this
problem as well.
I did some work, and traced the problem to its source
Would you mind filing a PR?
This kind of thing is important and best not to get lost. :)
Adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
On 09/19/11 23:46, Adrian Chadd wrote:
Would you mind filing a PR?
This kind of thing is important and best not to get lost. :)
Done. Identifier is kern/160838.
signature.asc
Description: OpenPGP digital signature
I tried running a -current (r219926) release in VirtualBox and got a panic.
acpi0: could not allocate interrupt
ACPI Exception: AE_ALREADY_EXISTS, Unable to install System Control Interrupt
handler (20110316/evevent-137)
acpi: Could not enable ACPI: AE_ALREADY_EXISTS
device_attach: acpi0 attach
On 26/03/2011, at 17:47, Daniel O'Connor wrote:
I tried running a -current (r219926) release in VirtualBox and got a panic.
I found that modifying the VM with..
VBoxManage modifyvm Installer\ test --hpet on --ioapic on
Makes it boot.
acpi0: could not allocate interrupt
ACPI Exception
On Tuesday, November 09, 2010 5:58:13 pm C. P. Ghost wrote:
On Mon, Nov 8, 2010 at 11:14 PM, John Baldwin j...@freebsd.org wrote:
This patch changes the Forth code for the Beastie menu to only display the
menu option to enable or disable ACPI if the loader detects ACPI. This
avoids
What are the chances the detection fails and one still needs to disable ACPI
and can't because it's not showing as a option ?
Thanks,
David Rhodus
On Nov 8, 2010, at 5:14 PM, John Baldwin j...@freebsd.org wrote:
This patch changes the Forth code for the Beastie menu to only display the
menu
If the loader can't detect acpi, the kernel can't either.
Scott
On Nov 10, 2010, at 9:01 AM, David Rhodus wrote:
What are the chances the detection fails and one still needs to disable ACPI
and can't because it's not showing as a option ?
Thanks,
David Rhodus
On Nov 8, 2010, at 5:14
or disable ACPI if the loader detects ACPI. This
avoids
displaying a menu item prompting to enable ACPI if the BIOS doesn't
actually
include ACPI. Any objections?
Wouldn't that be a POLA violation? Some admins may be used to the
current menu, and would be scratching head
On Tue, Nov 09, 2010 at 03:45:52PM +0200, Andriy Gapon wrote:
on 09/11/2010 07:26 Lars Engels said the following:
Maybe we should also import PCBSD's patches to the beastie menu?
In PCBSD's beastie menu you can toggle some settings like safe mode,
and ACPI, so the kernel is not loaded
. That way you have a multi-selection,
e.g. select safe mode but enable acpi.
Maybe we could also add a menu entry to boot without any modules, so
loaders.conf gets overridden?
That sounds cool. Like e.g. selecting verbose single-user boot completely from
the menu.
Good idea.
--
Andriy Gapon
on 09/11/2010 07:26 Lars Engels said the following:
Maybe we should also import PCBSD's patches to the beastie menu?
In PCBSD's beastie menu you can toggle some settings like safe mode,
and ACPI, so the kernel is not loaded as soon as select an option.
See
http://trac.pcbsd.org/browser
On Mon, Nov 8, 2010 at 11:14 PM, John Baldwin j...@freebsd.org wrote:
This patch changes the Forth code for the Beastie menu to only display the
menu option to enable or disable ACPI if the loader detects ACPI. This avoids
displaying a menu item prompting to enable ACPI if the BIOS doesn't
On Tue, Nov 9, 2010 at 2:58 PM, C. P. Ghost cpgh...@cordula.ws wrote:
On Mon, Nov 8, 2010 at 11:14 PM, John Baldwin j...@freebsd.org wrote:
This patch changes the Forth code for the Beastie menu to only display the
menu option to enable or disable ACPI if the loader detects ACPI. This
avoids
code for the Beastie menu to only display the
menu option to enable or disable ACPI if the loader detects ACPI. This
avoids
displaying a menu item prompting to enable ACPI if the BIOS doesn't
actually
include ACPI. Any objections?
Wouldn't that be a POLA violation? Some admins may
, John Baldwin j...@freebsd.org wrote:
This patch changes the Forth code for the Beastie menu to only display the
menu option to enable or disable ACPI if the loader detects ACPI. This
avoids
displaying a menu item prompting to enable ACPI if the BIOS doesn't
actually
include ACPI. Any
John Baldwin wrote:
This patch changes the Forth code for the Beastie menu to only display the
menu option to enable or disable ACPI if the loader detects ACPI. This avoids
displaying a menu item prompting to enable ACPI if the BIOS doesn't actually
include ACPI. Any objections?
I have
On Mon, Nov 08, 2010 at 05:14:53PM -0500, John Baldwin wrote:
This patch changes the Forth code for the Beastie menu to only display the
menu option to enable or disable ACPI if the loader detects ACPI. This avoids
displaying a menu item prompting to enable ACPI if the BIOS doesn't actually
This patch changes the Forth code for the Beastie menu to only display the
menu option to enable or disable ACPI if the loader detects ACPI. This avoids
displaying a menu item prompting to enable ACPI if the BIOS doesn't actually
include ACPI. Any objections?
--- //depot/projects/smpng/sys/boot
Hello list,
here is a digital camera pic of a panic that happened while booting
yesterdays Source tree
http://www.puffybsd.com/IMG_4136.JPG
here is a dmesg from a older current
http://www.puffybsd.com/amddmesg.txt
--
Sam Fourman Jr.
Fourman Networks
http://www.fourmannetworks.com
Uh, that looks like geom to me, not acpi...
-Garrett
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
here is a dmesg from a older current
http://www.puffybsd.com/amddmesg.txt
Uh, that looks like geom to me, not acpi...
-Garrett
I saw the ACPI warning on top so I blamed ACPI...
maybe I was wrong, this stuff is not my strong suit
--
Sam Fourman Jr.
Fourman Networks
http
while booting
yesterdays Source tree
http://www.puffybsd.com/IMG_4136.JPG
here is a dmesg from a older current
http://www.puffybsd.com/amddmesg.txt
Uh, that looks like geom to me, not acpi...
I saw the ACPI warning on top so I blamed ACPI...
maybe I was wrong, this stuff is not my strong
I saw the ACPI warning on top so I blamed ACPI...
maybe I was wrong, this stuff is not my strong suit
It's ok :) (one thing to note is that the ACPI warning is present
in both cases)... It would be interesting to note what modules you
load (in particular the geom ones), and what GEOM
Dear Andriy,
sorry for the delay.
On 10/22/10 11:29, Andriy Gapon wrote:
on 22/10/2010 12:09 vol...@vwsoft.com said the following:
On 10/22/10 10:53, Andriy Gapon wrote:
[ping]
Sorry, Andriy!
I haven't found the time to hack yesterday. The Intel website doesn't provide
the 20091221
-verbose.txt
Hmm, it looks like you have ACPI and APIC disabled... either in kernel config or
in BIOS?
If yes, can you try to not do it?
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
/~vwe/misc/Vaio_p11z/dmesg-verbose.txt
Hmm, it looks like you have ACPI and APIC disabled... either in kernel config or
in BIOS?
If yes, can you try to not do it?
Andriy,
the Vaio P11Z does not boot at all with ACPI enabled so it's disabled in
loader.conf. The panic messages are various if I
on 25/10/2010 14:23 vol...@vwsoft.com said the following:
the Vaio P11Z does not boot at all with ACPI enabled so it's disabled in
loader.conf. The panic messages are various if I try.
I would be interested to look at that problem (or those problems) too.
And now I think that see what
is an Intel Atom Z520 (single core). System doesn't boot at all w/
acpi
enabled.
The following patch made me to boot up again.
Index: i386/i386/mp_machdep.c
===
--- i386/i386/mp_machdep.c(revision 213936)
+++ i386/i386
). System doesn't boot at all w/ acpi
enabled.
The following patch made me to boot up again.
Index: i386/i386/mp_machdep.c
===
--- i386/i386/mp_machdep.c(revision 213936)
+++ i386/i386/mp_machdep.c(working copy)
@@ -286,7 +286,7
on 22/10/2010 12:09 vol...@vwsoft.com said the following:
On 10/22/10 10:53, Andriy Gapon wrote:
[ping]
Sorry, Andriy!
I haven't found the time to hack yesterday. The Intel website doesn't provide
the 20091221 tarball anymore (but a more recent one) and I need to lay my
hands
on the
Hi Andriy list!
Since rev 213323 my Sony Vaio P11Z was unable to boot up. It broke with
a divide by zero in topo_probe_0x4 at line 289 as cpu_logical is 0.
The cpu is an Intel Atom Z520 (single core). System doesn't boot at all
w/ acpi enabled.
The following patch made me to boot up again
/
acpi
enabled.
The following patch made me to boot up again.
Index: i386/i386/mp_machdep.c
===
--- i386/i386/mp_machdep.c(revision 213936)
+++ i386/i386/mp_machdep.c(working copy)
@@ -286,7 +286,7
-- Forwarded Message --
Subject: Re: MacBookPro 5,1
Date: Sunday 17 October 2010, 15:47:56
From: Hans Petter Selasky hsela...@c2i.net
To: freebsd-a...@freebsd.org
CC: linux-a...@vger.kernel.org
Hi,
CC'ing the Linux guys, hence I belive you are using the same ACPI code like
to power down the system
: # very soon.
: notify 10 {
: match system ACPI;
: match subsystem Thermal;
: match notify 0xcc;
: action logger -p kern.emerg 'WARNING: system temperature too high,
: shutting down soon!';
: };
:
: I'm
initially ruled out
the heat problem due to this entry in devd.conf:
# Notify all users before beginning emergency shutdown when we get
# a _CRT or _HOT thermal event and we're going to power down the system
# very soon.
notify 10 {
match system ACPI;
match subsystem
10 {
match system ACPI;
match subsystem Thermal;
match notify 0xcc;
action logger -p kern.emerg 'WARNING: system temperature too
high, shutting down soon!';
};
I'm not getting any of those notices in the logs, so I was looking
On 6/16/2010 5:05 AM, John Baldwin wrote:
You can reduce the polling interval by changing
hw.acpi.thermal.polling_rate (it is in seconds it seems) to a lower value.
Thanks, I'll give that a try, although with the cleaning I gave it
yesterday I'm hoping to avoid heat problems for a while. :)
Has anyone looked into pr i386/54781? It sounds very similar, and it
doesn't happen only on intel laptops. It also happens on my athlon laptop.
--
Russell A. Jackson ([EMAIL PROTECTED])
The irony is, if you're willing to kill a perpetrator, you probably won't have
to. -- Massad Ayoob
On 02-Dec-2003 Brooks Davis wrote:
On Tue, Dec 02, 2003 at 05:50:27PM -0500, John Baldwin wrote:
On 25-Nov-2003 Brooks Davis wrote:
Since the interrupt changes, my dual Xeons based on the SE7500WV2 board
don't work with ACPI. Specificly, the onboard nics (em0 and em1)
appear
Hi Nate,
On Tuesday 02 December 2003 23:34, Nate Lawson wrote:
Try other states (acpiconf -s 1, 2, 4). If one works, use it. If not,
try disabling acpi and using apm(4) to suspend and resume.
Normally that would be grand, but now that I've not compiled acpi into the
kernel, I have no /dev
On Wed, 3 Dec 2003, Melvyn Sopacua wrote:
On Tuesday 02 December 2003 23:34, Nate Lawson wrote:
Try other states (acpiconf -s 1, 2, 4). If one works, use it. If not,
try disabling acpi and using apm(4) to suspend and resume.
Normally that would be grand, but now that I've not compiled
On Wednesday 03 December 2003 21:57, Nate Lawson wrote:
On Wed, 3 Dec 2003, Melvyn Sopacua wrote:
On Tuesday 02 December 2003 23:34, Nate Lawson wrote:
Try other states (acpiconf -s 1, 2, 4). If one works, use it. If not,
try disabling acpi and using apm(4) to suspend and resume
Brooks Davis wrote:
Since acpi0 failed to probe, ACPI isn't used to route interrupts. However,
the apic code expects ACPI to do that since it enumerated CPUs and I/O
APICs. You are just going to have to disable ACPI for now.
acpi0: INTEL SWV20on motherboard
ACPI-1287: *** Error
with floppy support and acpi?
(There are no newer bios updates for the board around AFAIK)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Tuesday 02 December 2003 00:47, Daniel O'Connor wrote:
On Tuesday 02 December 2003 08:46, Ryan wrote:
Are you able to suspend to disk? So far I haven't been able to suspend to
disk on my Inspiron 8200. I'm using the fixed DSDT table from the URL
you posted as well.
The fixed DSDT only
Hello,
I have a Sony VAIO PCG-GRX626P, and I'm using a two days old FreeBSD
current, and pretty much everything works, except that when I move
into sleep mode 3 (acpiconf -s 3) I cannot bring my lap back. :-(
The fan starts again, but nothing else happens, after a while I just
power off the
originally installed 5.1R, the machine had
an older, non-ACPI BIOS.)
I've attached the verbose boot messages from 5.1R, in case that's
worth anything. Such a shame -- it gets within a hair's breadth of
running init, but it just can't quite make it all the way there.
Would you try this patch
dmesg, please, including error.
-Nate
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Try other states (acpiconf -s 1, 2, 4). If one works, use it. If not,
try disabling acpi and using apm(4) to suspend and resume.
Suspend/resume is far down my list of things to troubleshoot and most of
the problems are very hw-specific.
-Nate
On 23-Nov-2003 John Polstra wrote:
I have an old dual PII/400 system that I'm trying to set up as a
-current scratchbox. The motherboard is a Tyan S1836DLUAN with the
Intel 440BX chipset. I upgraded the BIOS to the latest from Tyan's
web site. It is supposed to support ACPI. I'm using
On 25-Nov-2003 Brooks Davis wrote:
Since the interrupt changes, my dual Xeons based on the SE7500WV2 board
don't work with ACPI. Specificly, the onboard nics (em0 and em1)
appear to not be recieving interupts. Instead, they continiously get
watchdog timeouts. In a stock current
On Tue, Dec 02, 2003 at 05:50:27PM -0500, John Baldwin wrote:
On 25-Nov-2003 Brooks Davis wrote:
Since the interrupt changes, my dual Xeons based on the SE7500WV2 board
don't work with ACPI. Specificly, the onboard nics (em0 and em1)
appear to not be recieving interupts. Instead
On Tuesday 02 December 2003 21:50, Melvyn Sopacua wrote:
I used to suspend to disk in 4.x after creating the S2D partition with
the floppy image from Dell, however I don't any more..
I kept the Dell partition intact. Or does it need special formatting?
If it's a newish laptop then that
memory = 251052032 (239 MB)
Pentium Pro MTRR support enabled
acpi0: AMIINT SiS735XX on motherboard
pcibios: BIOS version 2.10
Using $PIR table, 8 entries at 0xc00f7950
acpi0: Power Button (fixed)
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port
Your ASL indicates that it returns different values for present (based on
PS2F) and current resources (based on KBDI). Please send me the URL to
the full ASL so I can see what sets those two variables.
-Nate
___
[EMAIL PROTECTED] mailing list
On Mon, Dec 01, 2003 at 09:48:40AM -0800, Nate Lawson wrote:
Your ASL indicates that it returns different values for present (based on
PS2F) and current resources (based on KBDI). Please send me the URL to
the full ASL so I can see what sets those two variables.
http://zxy.spb.ru/acpi.dump
Hi,
I've done some testing with acpi:
S1 level - does not blank the display.
S2 level - unsupported by the BIOS
S3/S4 level - reboot the machine, with at best a print_cpu debug statement[1]
s5 level - works as expected
[1] I've pressed 'pause' and copied it for anybody that wants the register
those two variables.
http://zxy.spb.ru/acpi.dump
Do you need additional information?
Try this workaround, recompile your asl, set dsdt_load in loader.conf.
See acpi(4) if you need info on this process. I think your BIOS needs a
workaround. I wonder if the MS interpreter ignores _STA for some
can see what sets those two variables.
http://zxy.spb.ru/acpi.dump
Do you need additional information?
Try this workaround, recompile your asl, set dsdt_load in loader.conf.
See acpi(4) if you need info on this process. I think your BIOS needs a
workaround. I wonder if the MS
Hi
If you just looking for working acpi with your inspiron 8000 then try this patches at
http://sandcat.nl/~stijn/freebsd/dell.php. It works for me with -current.
regards
Thomas Vogt
Hi,
I've done some testing with acpi:
S1 level - does not blank the display.
S2 level - unsupported
=-
Thomas said:
Hi
If you just looking for working acpi with your inspiron 8000 then try this
patches at
http://sandcat.nl/~stijn/freebsd/dell.php. It works for me with -current.
regards
Thomas Vogt
Hi,
I've done some testing with acpi:
S1 level - does not blank the display.
S2 level
On Monday 01 December 2003 22:56, Thomas wrote:
If you just looking for working acpi with your inspiron 8000 then try this
patches at http://sandcat.nl/~stijn/freebsd/dell.php. It works for me with
-current.
Thanx. It mentions the ports version of acpidump and iasl, which are already
in my
On Tuesday 02 December 2003 08:46, Ryan wrote:
Are you able to suspend to disk? So far I haven't been able to suspend to
disk on my Inspiron 8200. I'm using the fixed DSDT table from the URL
you posted as well.
I used to suspend to disk in 4.x after creating the S2D partition with the
floppy
If acpi enabled PS/2 mouse failed to work and irq12 cold't attach
to psmintr.
Is this problem reporting PS/2 mouse resource before atkbdc?
psmcpnp0 irq 12 on acpi0
atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0
atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
atkbd: the current
Nate Lawson writes:
No way! Good (non-386) equipment is never to old. :)
Please add debug.acpi.disable=cpu to loader.conf or type that in at the
loader prompt. If it boots ok, we'll have to debug the acpi_cpu_startup
path.
Speaking of which, I have a Good (see above...) motherboard
On 29-Nov-2003 George Hartzell wrote:
Speaking of which, I have a Good (see above...) motherboard looking
for a worthy home.
There's an alias [EMAIL PROTECTED] just for such offers. :-)
John
___
[EMAIL PROTECTED] mailing list
On Fri, 28 Nov 2003 21:03:24 +0900
Makoto Matsushita [EMAIL PROTECTED] wrote:
is enabled, etc. Moreover, it seems that long standing random/slower/
faster clock-time bug is resolved!
Wow! I want new one:-).
Please note that this is about FreeBSD as VMware's *guest* OS, not
as
Since the interrupt changes, my dual Xeons based on the SE7500WV2 board
don't work with ACPI. Specificly, the onboard nics (em0 and em1)
appear to not be recieving interupts. Instead, they continiously get
watchdog timeouts. In a stock current, this is an instant panic. With
a minor fix
acpi0: INTEL SWV20on motherboard
ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.EC0_._REG] (Node
0xc29b4660), AE_NOT_EXIST
acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST
device_probe_and_attach: acpi0 attach returned 6
This is the source of the problems
an older, non-ACPI BIOS.)
I've attached the verbose boot messages from 5.1R, in case that's
worth anything. Such a shame -- it gets within a hair's breadth of
running init, but it just can't quite make it all the way there.
John
SMAP type=01 base= len=0009fc00
SMAP type=02
On Tue, Nov 25, 2003 at 12:12:16PM -0800, Nate Lawson wrote:
acpi0: INTEL SWV20on motherboard
ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.SBRG.EC0_._REG]
(Node 0xc29b4660), AE_NOT_EXIST
acpi0: Could not initialise SystemIO handler: AE_NOT_EXIST
23 13:32:22 PST 2003
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/VASHON
Preloaded elf kernel /boot/kernel/kernel at 0xc07bc000.
ACPI APIC Table: TYANCP TYANTBLE
Calibrating clock(s) ... i8254 clock: 1193039 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter i8254
On Mon, 24 Nov 2003, John Polstra wrote:
On 24-Nov-2003 Nate Lawson wrote:
Please add debug.acpi.disable=cpu to loader.conf or type that in at the
loader prompt. If it boots ok, we'll have to debug the acpi_cpu_startup
path.
Thanks. It still hangs even with debug.acpi.disable=cpu. I
. It appears your ACPI timer is bad. The reason why I suggest this
is that it seems like interrupts are being lost.
-Nate
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL
to disable ACPI in
/boot/loader.conf.
If you can break to the debugger after it has hung, a tr would be nice.
The fact that it didn't occur to me to try that says a lot about how
long I've been away from -current. :-( I've attached traces from
two different boots. They seem to vary somewhat. I
On 24-Nov-2003 Nate Lawson wrote:
It's a long shot, but what about setting kern.timecounter.hardware to
i8254. It appears your ACPI timer is bad. The reason why I suggest this
is that it seems like interrupts are being lost.
I put kern.timecounter.hardware=i8254 into /boot/loader.conf
In message [EMAIL PROTECTED], John Polstra writes:
On 24-Nov-2003 Nate Lawson wrote:
It's a long shot, but what about setting kern.timecounter.hardware to
i8254. It appears your ACPI timer is bad. The reason why I suggest this
is that it seems like interrupts are being lost.
I put
On Mon, 24 Nov 2003, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], John Polstra writes:
On 24-Nov-2003 Nate Lawson wrote:
It's a long shot, but what about setting kern.timecounter.hardware to
i8254. It appears your ACPI timer is bad. The reason why I suggest
.
Remember, though, in order to boot it I had to disable ACPI in
/boot/loader.conf.
Yes, I see. You could use an older kernel like the 5.1R cd.
If you can break to the debugger after it has hung, a tr would be nice.
The fact that it didn't occur to me to try that says a lot about how
long
shows that machdep.acpi_root is 0.
Remember, though, in order to boot it I had to disable ACPI in
/boot/loader.conf.
Yes, I see. You could use an older kernel like the 5.1R cd.
I'll try that, and send you the dump if I can get one.
Both of these show that acpi_task_thread is calling a task
,c0462229,c12a0c00,cdb64c34) at
AcpiUtAcquireFromCache+0x53
Both of these show that acpi_task_thread is calling a task and then
AcpiOsSignalSemaphore is hanging. I'm wondering if your system can't
handle the acpi interrupt being moved to irq 20. Please try this
(untested) patch that should
) at AcpiUtReleaseMutex+0x8c
AcpiUtAcquireFromCache(2,cdb64bf4,c0462229,c12a0c00,cdb64c34) at
AcpiUtAcquireFromCache+0x53
Both of these show that acpi_task_thread is calling a task and then
AcpiOsSignalSemaphore is hanging. I'm wondering if your system can't
handle the acpi interrupt being moved
On 25-Nov-2003 Nate Lawson wrote:
Someone more familiar with ithread_loop should probably answer this. One
workaround might be to enable ACPI_NO_SEMAPHORES on your box.
I built and booted a kernel with ACPI_NO_SEMAPHORES, but it still
hangs at the same point in the boot. The stack trace is
Good people,
I have managed to crowbar ACPI support into working on ThinkPad 560Z
with the attached patch. The problem seems to be that TP returns
everything and a kitchen sink in the list of available IRQs, but expects
OS to use one you have set up using
I have an old dual PII/400 system that I'm trying to set up as a
-current scratchbox. The motherboard is a Tyan S1836DLUAN with the
Intel 440BX chipset. I upgraded the BIOS to the latest from Tyan's
web site. It is supposed to support ACPI. I'm using -current from
around noon Pacific time
No way! Good (non-386) equipment is never to old. :)
Please add debug.acpi.disable=cpu to loader.conf or type that in at the
loader prompt. If it boots ok, we'll have to debug the acpi_cpu_startup
path.
-Nate
___
[EMAIL PROTECTED] mailing list
I'm having difficulty getting battery and thermal status. If I compile the
kernel with APM support I get battery statistics but if I try to put
APM/ACPI in the kernel ACPI reports that another PM system is enabled and
doesn't load the /dev/acpi device. If I take APM out and compile in ACPI I
On Sat, 22 Nov 2003, Ryan Sommers wrote:
I'm having difficulty getting battery and thermal status. If I compile the
kernel with APM support I get battery statistics but if I try to put
APM/ACPI in the kernel ACPI reports that another PM system is enabled and
doesn't load the /dev/acpi device
John Baldwin writes:
Ok, your BIOS is buggy, but I think I can work around it.
http://www.FreeBSD.org/~jhb/patches/acpi_irq.patch
Thanks, now it's working much better!
New dmesg and vmstat-i at http://tomppa.iki.fi/~tomppa/FreeBSD/
Tomppa
/
You probably shouldn't be using intpm with acpi by the way.
--
John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/
Power Users Use the Power to Serve! - http://www.FreeBSD.org/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org
Tomi Vainio writes:
My old MSI-6120 SMP system has been unusable quite a while with ACPI.
I've got these so far:
- Couldn't get vector from ISR
- vmstat -i shows high interrupt rates and system is very slow
- kernel trap 12 panic
Latest problem is something like
My old MSI-6120 SMP system has been unusable quite a while with ACPI.
I've got these so far:
- Couldn't get vector from ISR
- vmstat -i shows high interrupt rates and system is very slow
- kernel trap 12 panic
Latest problem is something like this:
pfs_vncache_unload(): 2 entries remaining
On 15-Nov-2003 Dylan Wylie wrote:
List,
Running -CURRENT now gives the following problem on a Compaq Pressario 1600-
XL144 laptop:
[...]
cbb0: TI1211 PCI-CardBus Bridge at device 10.0 on pci0
cardbus0: CardBus bus on cbb0
pccard0: 16-bit PCCard bus on cbb0
pcib0: _PRS resource entry
401 - 500 of 1744 matches
Mail list logo
