10.0 on pci0
: cardbus0: CardBus bus on cbb0
: pccard0: 16-bit PCCard bus on cbb0
: pcib0: _PRS resource entry has unsupported type 0
: cbb: Unable to map IRQ...
: device_probe_and_attach: cbb0 attache returned 12
: [...]
:
: Disabeling ACPI makes it work again.
: However, I'm
On Sat, 15 Nov 2003, Nate Lawson wrote:
Please test this to be sure that it boots ok on your machine, especially
SMP boxes. Throttling should still work ok also.
Seems to work here:
hw.acpi.cpu.cx_supported: C1/1 C2/1 C3/85 C3/185
hw.acpi.cpu.cx_lowest: 0
hw.acpi.cpu.cx_history: 173839/0 0/0
On Sun, 16 Nov 2003, Lukas Ertl wrote:
On Sat, 15 Nov 2003, Nate Lawson wrote:
Please test this to be sure that it boots ok on your machine, especially
SMP boxes. Throttling should still work ok also.
Seems to work here:
hw.acpi.cpu.cx_supported: C1/1 C2/1 C3/85 C3/185
11:26:41 -0800 (PST)
njl 2003/11/15 11:26:06 PST
FreeBSD src repository
Modified files:
sys/dev/acpica acpi_cpu.c
share/man/man4 acpi.4
sys/conf files
sys/modules/acpi Makefile
Log:
Implement Cx CPU idle states and updated throttling
...
device_probe_and_attach: cbb0 attache returned 12
[...]
Disabeling ACPI makes it work again.
However, I'm then getting the 'watchdog time-out, reseting card' thing now, so no net
for
now.
tried the hw.pci._allow_usupported_io_range=1 option, but doesn't help.
Everything was fine before
: 16-bit PCCard bus on cbb0
: pcib0: _PRS resource entry has unsupported type 0
: cbb: Unable to map IRQ...
: device_probe_and_attach: cbb0 attache returned 12
: [...]
:
: Disabeling ACPI makes it work again.
: However, I'm then getting the 'watchdog time-out, reseting card' thing now, so no
net
On 2003-11-08 09:52 +0300, Konstantin Volevatch wrote:
Why acpi.ko module missed after latest CVS update?
Read UPDATING, or check the last few days worth of -current archives.
--
Munish Chopra
___
[EMAIL PROTECTED] mailing list
Hi,
wanted to let you know, that since yesterday ACPI on my
Dell Latitude D600 doesn't work anymore.
Does anybody have an idea what this breakage might have caused ?
About a week ago I got apm/acpi working with an unoff patch from this URL.
http://sandcat.nl/~stijn/freebsd/dell.php
I
On Fri, 7 Nov 2003, Andreas Klemm wrote:
wanted to let you know, that since yesterday ACPI on my
Dell Latitude D600 doesn't work anymore.
/usr/src/UPDATING
20031103:
The i386 APIC_IO kernel option has been replaced by
'device apic'. The ACPI module has also been temporarily
Hi Andreas,
I bet acpi isn't even running. As of a few days ago acpi is disabled
as a loadable module due to some changes in progress. Try adding
'device acpi' to your kernel.conf file and rebuild/reinstall the
kernel.
Ken
- Original Message -
From: Andreas Klemm [EMAIL PROTECTED
On Fri, Nov 07, 2003 at 11:28:19AM -0500, Ken Menzel wrote:
Hi Andreas,
I bet acpi isn't even running. As of a few days ago acpi is disabled
as a loadable module due to some changes in progress. Try adding
'device acpi' to your kernel.conf file and rebuild/reinstall the
kernel.
Ken
It's borked in 4.9 as well. I just had to downgrade a bunch of Servers
to 4.8 :(
Lanny
On Fri, 2003-11-07 at 11:07, Andreas Klemm wrote:
Hi,
wanted to let you know, that since yesterday ACPI on my
Dell Latitude D600 doesn't work anymore.
Does anybody have an idea what this breakage might
Why acpi.ko module missed after latest CVS update?
--
Konstantin M. Volevatch [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
is reproducable: every time i unplug my ac adapter, it
panic's. If i boot without the ac adapter plugged in, it panics. If i
boot with acpi disabled, it works fine.
my kernel config is GENERIC. I've rebuilt as of about 1pm EST today.
I'm attaching my dmesg from booting without acpi, and boot -v
Hi,
I'm using a Dell Inspiron 8000 running BIOS A22 (latest AFAIK) and FreeBSD
5.1-RELEASE. I've compiled a fixed DSDT following Stijn's instructions
which did fix a bunch of errors during/after bootup.
I'm trying to get some of the power saving states working but am having no
luck and can't
I'm using Motherboard based on VIA chipset and the S3 doesnt work correctly. On resume
if there are X the system doesn't restart and without X the system resmumes but hangs
few later.
I'm using FreeBSD 5.1-CURRENT: Wed Oct 29 15:35:15 CET 2003 i386
On Sat, 1 Nov 2003 22:02:56 +0200
Aragon
On 29/10/03 18:18 -0800, Nate Lawson wrote:
I looked at a few other ASL copies I have and you have an old version.
Have you done a BIOS update recently?
Yours: OEMID=DELL, OEM Table ID=CPi R, OEM Revision=0x27d0040b,
Others: OEMID=DELL, OEM Table ID=CPi R, OEM Revision=0x27d20b07,
had read this email a few hours earlier,
before I got frustrated and decided to give Debian a shot on this
laptop.
Linux would probably have had the same problem with your AML since we use
the same interpreter.
Happily running FreeBSD again,
Glad to hear it. Anyone else having ACPI trouble
getting BIF\n);
The second one did not trigger (I had actually been using ACPI_VPRINT
for a while to get info like that). I have a dump of my ASL here:
http://home.satanosphere.com/bsd/jeremy.asl.gz. As far as my dmesg goes,
I can get you one where it boots w/ ACPI disabled, but when it hangs
into DDB which - I presume - is not relevant to this problem.
Yes, that's true. What you probably want to do now is do tr pid for
the pids below to see what they're blocked on. Likely culprits are 24
(since it's on irq 7), 23 (acpi), 29, and 25. The most likely one is 24
because irq 7 is normally
* Nate Lawson [EMAIL PROTECTED] [2003-10-27 22:13]:
... What you probably want to do now is do tr pid for the
pids below to see what they're blocked on. Likely culprits are 24
(since it's on irq 7), 23 (acpi), 29, and 25. The most likely one
is 24 because irq 7 is normally edge triggered
On Mon, 27 Oct 2003, Thorsten Greiner wrote:
* Nate Lawson [EMAIL PROTECTED] [2003-10-27 22:13]:
... What you probably want to do now is do tr pid for the
pids below to see what they're blocked on. Likely culprits are 24
(since it's on irq 7), 23 (acpi), 29, and 25. The most likely one
* Nate Lawson [EMAIL PROTECTED] [2003-10-24 22:57]:
Type tr at the DDB prompt to get a trace of what is hanging.
At the time of the hang a 'ps' in DDB shows two screenful's of
processes. Doing a simple 'tr' just gives the backtrace of how I got
into DDB which - I presume - is not relevant to
On Wednesday 22 October 2003 22:22, Thorsten Greiner wrote:
Hi everybody,
I have a VIA EPIA-M 1 board which works mostly when I disable
ACPI in the bios. Unfortunately the parallel port is controlled by
some Super-IO chip and is not recognized during boot. The same holds
true for serial
I have a VIA EPIA-M 1 board which works mostly when I disable
ACPI in the bios. Unfortunately the parallel port is controlled by
some Super-IO chip and is not recognized during boot. The same holds
true for serial ports and the floppy controller.
When I enable ACPI in the bios
Hi everybody,
I have a VIA EPIA-M 1 board which works mostly when I disable
ACPI in the bios. Unfortunately the parallel port is controlled by
some Super-IO chip and is not recognized during boot. The same holds
true for serial ports and the floppy controller.
When I enable ACPI in the bios
ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.LNKU._CRS] (Node
0xc40e49c0), AE_AML_UNINITIALIZED_LOCAL
ACPI-0175: *** Error: Method execution failed [\\_SB_.PCI0.LPCB.LNKU._CRS] (Node
0xc40e49c0), AE_AML_UNINITIALIZED_LOCAL
This means your AML is lousy. Try some
Hi!
Is there way to make acpi work on fujitsu-siemens (amd 2500+)?
I have tried to search google, but no go. dmesg and sysctl outputs are below.
acpiconf -s 1 or 2 doesn't work. I guess because those errors.
Have someone made it work on fujitsu-siemens?
I would be grateful for any help you can
accessed during the second
suspend (ie. wiggling mouse). Yesterday after finally updating to a current
that boots my system after a couple of weeks without it I suspended the
system and resumed it to check some ACPI issues had been fixed, but that's
for another time. After resume I realized I
On Oct 17, 2003, at 10:25 AM, Nate Lawson wrote:
The problem is USB although ACPI magnifies it. USB devices can
generate
wake events. In my current testing of a new acpi_cpu driver, I've
found
that just having the USB bus enabled in the kernel (with no devices
attached) causes it to generate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 17 October 2003 01:25 pm, Nate Lawson wrote:
The problem is USB although ACPI magnifies it. USB devices can generate
wake events. In my current testing of a new acpi_cpu driver, I've found
that just having the USB bus enabled
). Yesterday after finally updating to a current
that boots my system after a couple of weeks without it I suspended the
system and resumed it to check some ACPI issues had been fixed, but that's
for another time. After resume I realized I needed my mouse, so I plugged it
in, dynamically loaded
/GeForce2
Additionally, I've been testing ACPI on this hardware. ACPI would be
highly desirable for this desktop dev. workstation.
ACPI support: Suspend is currently buggy:
- S1(POS): partially supported, tested to work in single user mode only.
- S3(STR): doesn't work most of the time
@ [dragonfruit] ~
Oct 5 23:40:58 dragonfruit kernel: ACPI-1287: *** Error: Method execution
failed [\_SB_.PCI0.LPCB.BAT1._BST] (Node 0xc47d
d980), AE_AML_REGION_LIMIT
Oct 5 23:40:58 dragonfruit kernel: ACPI-1287: *** Error: Method execution
failed [\_SB_.PCI0.LPCB.BAT1._BST] (Node 0xc47d
d980
On Sun, 5 Oct 2003, Matt Douhan wrote:
Oct 5 23:40:58 dragonfruit kernel: ACPI-1287: *** Error: Method execution
failed [\_SB_.PCI0.LPCB.BAT1._BST] (Node 0xc47d
d980), AE_AML_REGION_LIMIT
Oct 5 23:40:58 dragonfruit kernel: ACPI-1287: *** Error: Method execution
failed [\_SB_.PCI0.LPCB.BAT1
On 01/10/03 11:28 -0700, Nate Lawson wrote:
dmesg is not necessary. The only way to find what is hanging is to keep
working printfs deeper into the _BIF method. Start with
AcpiEvaluateObject in sys/contrib/dev/acpica/nsxfeval.c and sprinkle
printf A, B, C etc. throughout to find where it
On 30/09/03 15:04 -0700, Nate Lawson wrote:
Are you sure you tracked it down to INVARIANTS? Or was it DDB? Please
try with _just_ DDB and see if you can still reproduce the problem. If
so, then when it hangs, hit CTRL-ALT-ESC and type tr. This will tell
who is hung.
As far as debugging
On Wed, 1 Oct 2003, Jeremy Bingham wrote:
On 30/09/03 15:04 -0700, Nate Lawson wrote:
Are you sure you tracked it down to INVARIANTS? Or was it DDB? Please
try with _just_ DDB and see if you can still reproduce the problem. If
so, then when it hangs, hit CTRL-ALT-ESC and type tr. This
you one where it boots w/ ACPI disabled, but when it hangs, it
hangs before / is mounted at all, so I can't really get it. Should I
boot it again and just type the last lines out?
-j
--
/* You are not expected to understand this. */
Captain_Tenille
http
On Wed, 1 Oct 2003, Jeremy Bingham wrote:
On 01/10/03 09:33 -0700, Nate Lawson wrote:
As far as debugging prints, add the following printfs to
acpi_cmbat_get_bif():
printf(Before getting BIF\n);
as = AcpiEvaluateObject(h, _BIF, NULL, bif_buffer);
printf(After
Now I'm having an issue with ACPI. I used to hit the power button and
that would initiate a proper shutdown. Now it seems to do nothing,
but when I reboot the system goes into a suspended state before
completing the shutdown. The motherboard beeps three times, the
screen goes blank
Now I'm having an issue with ACPI. I used to hit the power button and
that would initiate a proper shutdown. Now it seems to do nothing,
but when I reboot the system goes into a suspended state before
completing the shutdown. The motherboard beeps three times, the
screen goes blank
On Wed, 1 Oct 2003, Nate Lawson wrote:
Now I'm having an issue with ACPI. I used to hit the power button and
that would initiate a proper shutdown. Now it seems to do nothing,
but when I reboot the system goes into a suspended state before
sysctl hw.acpi should show you what the power
On Mon, 29 Sep 2003, Nate Lawson wrote:
On Mon, 29 Sep 2003, Kevin Oberman wrote:
ACPI attaches the bus twice. See sys/dev/acpica/acpi.c:
Thanks. That explains why I get the message twice, but why do I get it
at all when the device is disabled in the device.hints file?
Dunno. That's
On 2003-09-29 13:33:06 (-0700), Nate Lawson [EMAIL PROTECTED] wrote:
On Mon, 29 Sep 2003, Kevin Oberman wrote:
From: John Baldwin [EMAIL PROTECTED]
On 29-Sep-2003 Kevin Oberman wrote:
I recently noticed that, when I boot with ACPI on my IBM T30, I get
errors trying to probe the BIOS
In my continuing quest to figure out what's wrong with ACPI in -CURRENT
on my laptop, I've tried going back to the old ata drivers (worked, but
made no difference), ended up blowing my computer up (weird fsck problem
crept in), went back to 5.1, moved up to -CURRENT again, and started
plugging
I'm not sure what's causing these ACPI problems in this recent -CURRENT,
but I've found where it's hanging. It's on this line:
as = AcpiEvaluateObject(h, _BIF, NULL, bif_buffer);
in acpi_cmbat.c in sys/dev/acpica/. The function AcpiEvaluateObject is
found in contrib/dev/acpica/nsxfeval.c, which
Please do not start new threads for the same problem as it makes it hard
to track down what your problem even was originally. I assume your
problem is hangs during boot, it appeared since 5.1R, and it goes away if
you enable options INVARIANTS. Is that right?
-Nate
On Tue, 23 Sep 2003, Jeremy Bingham wrote:
On 23/09/03 18:07 -0700, Nate Lawson wrote:
Enable options DDB. When it hangs, press CTRL-ALT-ESC and then tr to
get a traceback.
While ACPI influences this problem, I am uncertain it is the root cause.
-Nate
Way ahead of you there. I
On 30/09/03 14:48 -0700, Nate Lawson wrote:
Please do not start new threads for the same problem as it makes it hard
to track down what your problem even was originally. I assume your
problem is hangs during boot, it appeared since 5.1R, and it goes away if
you enable options INVARIANTS. Is
On Tue, 30 Sep 2003, Jeremy Bingham wrote:
On 30/09/03 14:48 -0700, Nate Lawson wrote:
Please do not start new threads for the same problem as it makes it hard
to track down what your problem even was originally. I assume your
problem is hangs during boot, it appeared since 5.1R, and it
I recently noticed that, when I boot with ACPI on my IBM T30, I get
errors trying to probe the BIOS disabled sio1. This does not happen
under apm and happens twice(?) when booting with ACPI and happens even
though I have the line 'hint.sio.1.disabled=1' in /boot/device.hints.
From my dmesg:
sio0
On 29-Sep-2003 Kevin Oberman wrote:
I recently noticed that, when I boot with ACPI on my IBM T30, I get
errors trying to probe the BIOS disabled sio1. This does not happen
under apm and happens twice(?) when booting with ACPI and happens even
though I have the line 'hint.sio.1.disabled=1
Date: Mon, 29 Sep 2003 16:04:25 -0400 (EDT)
From: John Baldwin [EMAIL PROTECTED]
On 29-Sep-2003 Kevin Oberman wrote:
I recently noticed that, when I boot with ACPI on my IBM T30, I get
errors trying to probe the BIOS disabled sio1. This does not happen
under apm and happens twice
On Mon, 29 Sep 2003, Kevin Oberman wrote:
Date: Mon, 29 Sep 2003 16:04:25 -0400 (EDT)
From: John Baldwin [EMAIL PROTECTED]
On 29-Sep-2003 Kevin Oberman wrote:
I recently noticed that, when I boot with ACPI on my IBM T30, I get
errors trying to probe the BIOS disabled sio1. This does
noticed that, when I boot with ACPI on my IBM T30, I get
errors trying to probe the BIOS disabled sio1. This does not happen
under apm and happens twice(?) when booting with ACPI and happens even
though I have the line 'hint.sio.1.disabled=1' in /boot/device.hints.
From my dmesg
On Mon, 29 Sep 2003, Kevin Oberman wrote:
Date: Mon, 29 Sep 2003 13:33:06 -0700 (PDT)
From: Nate Lawson [EMAIL PROTECTED]
ACPI attaches the bus twice. See sys/dev/acpica/acpi.c:
/*
* Scan all of the child devices we have created and let them probe/attach
On 25 Sep, Nate Lawson wrote:
I've got an IBM ThinkPad R40 that hangs when I do a shutdown -p. It
wedges after printing Powering system off using ACPI.
Attempting to use 'acpiconf -s to suspend produces similar hangs.
Your system is halting correctly but powering off is failing. A cursory
after the CPU is probed. I
uploaded the full trace to
http://people.freebsd.org/~truckman/r40-acpi-trace.bz2.
The system boots ok if I remove these two debug options.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
I've got an IBM ThinkPad R40 that hangs when I do a shutdown -p. It
wedges after printing Powering system off using ACPI.
Attempting to use 'acpiconf -s to suspend produces similar hangs.
Your system is halting correctly but powering off is failing. A cursory
glance at your ASL shows
it to go into debugging mode and get a stack trace. When I was
looking at where it was dying before with verbose logging turned on, it
seemed to be dying when it was trying to initialize the battery. I
looked at the ACPI stuff in the kernel, and I think I may have found
where it stops working
On 25/09/03 11:54 -0700, Nate Lawson wrote:
Interesting. Try turning on ACPI_LV_FUNCTIONS (see the email I just sent
to -current) as well as ACPI_DEBUG and let me know the last 3-4 prints
before it hangs. Not blaming anyone here, but could you also try without
ATAng? I am unable to use
On Thu, 25 Sep 2003, Jeremy Bingham wrote:
On 25/09/03 11:54 -0700, Nate Lawson wrote:
Interesting. Try turning on ACPI_LV_FUNCTIONS (see the email I just sent
to -current) as well as ACPI_DEBUG and let me know the last 3-4 prints
before it hangs. Not blaming anyone here, but could you
On 25/09/03 12:26 -0700, Nate Lawson wrote:
Will do. One question, though, before I get to recompiling -- is there
some specific option for ATAng in the kernel that I'm missing? The only
thing I see that looks similar is 'device ata'.
Unfortunately, no. You can cvsup to 2003/8/23 on just
Unfortunately, no. You can cvsup to 2003/8/23 on just the sys/dev/ata
directory and revert the change to sys/conf/files. That does the trick.
Currently ATAng causes a hang on resume from suspend whereas it has worked
for months before ATAng. I am running -current without ATAng with no
than normal.
That's because ACPI is a module and options defined in the kernel config
do not apply to the modules. I think someone was working on fixing this
annoyance.
To rebuild it, cd /sys/modules/acpi and do:
make ACPI_DEBUG=1
cp acpi.ko /boot/kernel.test (or wherever your test
I've got an IBM ThinkPad R40 that hangs when I do a shutdown -p. It s
wedges after printing Powering system off using ACPI. The display
stays on, and judging by the heat, it seems that the CPU is on as well.
It doesn't respond to the keyboard, so I haven't been able to get into
DDB. The only
it to go into debugging mode and get a stack trace. When I was
looking at where it was dying before with verbose logging turned on, it
seemed to be dying when it was trying to initialize the battery. I
looked at the ACPI stuff in the kernel, and I think I may have found
where it stops working. (It's where
On Mon, 22 Sep 2003, Andrew Thompson wrote:
Andrew Thompson wrote:
I fixed the other null derefernce in sc_bell() and the laptop is now
suspending with the serial console the same as without.
as it should, but the second suspend it only does acpi_SetSleepState()
- AcpiEnterSleepStatePrep()
There may be a problem with the ACPI drivers in -CURRENT. I cvsup'ed to
-CURRENT earlier today (9/23/03), rebuilt the world and kernel, and installed
everything without incident. When I rebooted my laptop after installing
the world, the kernel started hanging part way through the boot process.
I
When booting FreeBSD normally or in single-user mode, these are the last
messages displayed:
Timecounter TSC frequency 498470127 Hz quality 800
Timecounters tick every 10.000 msec
^^^ hangs after that
When booting FreeBSD with ACPI turned off or in Safe Mode, the computer
boots normally
On 23/09/03 18:07 -0700, Nate Lawson wrote:
Enable options DDB. When it hangs, press CTRL-ALT-ESC and then tr to
get a traceback.
While ACPI influences this problem, I am uncertain it is the root cause.
-Nate
Way ahead of you there. I compiled a kernel with DDB on, installed
On Tuesday 23 September 2003 10:01 pm, Jeremy Bingham wrote:
On 23/09/03 18:07 -0700, Nate Lawson wrote:
Enable options DDB. When it hangs, press CTRL-ALT-ESC and then
tr to
get a traceback.
While ACPI influences this problem, I am uncertain it is the root
cause.
-Nate
Way
Andrew Thompson wrote:
Nate Lawson wrote:
On Wed, 17 Sep 2003, Andrew Thompson wrote:
It has helped and the laptop is able to suspend with the serial cable
attached (further than before). It now panics on the first resume with
the following (gdb output at bottom).
You should do a quick grep
Nate Lawson wrote:
On Wed, 17 Sep 2003, Andrew Thompson wrote:
It has helped and the laptop is able to suspend with the serial cable
attached (further than before). It now panics on the first resume with
the following (gdb output at bottom).
I think the serial cable is masking the problem as
On Wed, 17 Sep 2003, Andrew Thompson wrote:
Nate Lawson wrote:
On Wed, 17 Sep 2003, Andrew Thompson wrote:
111 sc_cur_scr = sc-cur_scp-index;
For a temporary workaround, try changing line 111 to:
if (sc-cur_scp == NULL)
return (0);
This may not help things
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I reported this serveral times and no one seemed to be able to
reproduce the problem, and I couldn't figure out what wasn't being
shutoff. FInally I think that I figured it out. The display is the
thing that is not being shutoff. The reason I
On Wed, 17 Sep 2003, Anish Mistry wrote:
I reported this serveral times and no one seemed to be able to
reproduce the problem, and I couldn't figure out what wasn't being
shutoff. FInally I think that I figured it out. The display is the
thing that is not being shutoff. The reason I missed
cable. When I boot to the comconsole and try to suspend it panics
straight away with the following. The asl and dmesg can be found @
http://www.fud.org.nz/acpi/
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor read, page
Please compile your kernel with debug symbols (config -g KERNEL) and load
it into gdb to get the actual line of code that is getting that NULL
deref:
gdb kernel.debug
l *scsuspend+0x17
That should show the offending code segment.
-Nate
___
(To recap: I'm having ACPI problems on a DFI CD70-SC, with both 5.1-R and
5-CURRENT. Booting GENERIC doesn't show any problems, however, so there's
a good chance it's a misconfiguration issue.)
Thus spake Damian Gerow ([EMAIL PROTECTED]) [15/09/03 17:34]:
It's attached. There's no APM
Nate Lawson wrote:
Please compile your kernel with debug symbols (config -g KERNEL) and load
it into gdb to get the actual line of code that is getting that NULL
deref:
gdb kernel.debug
l *scsuspend+0x17
That should show the offending code segment.
Hopefully I have done this right :)
On Wed, 17 Sep 2003, Andrew Thompson wrote:
Nate Lawson wrote:
gdb kernel.debug
l *scsuspend+0x17
That should show the offending code segment.
(gdb) l *scsuspend+0x17
0xc03d7b17 is in scsuspend (/usr/src/sys/isa/syscons_isa.c:111).
106 int retry = 10;
107
strange that this would only be brought out with ACPI...?
Anyhow, it's working for me now. If anyone feels like further debugging,
I'm all game.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe
specified MAXMEM in, without any troubles.
It's also strange that this would only be brought out with ACPI...?
Anyhow, it's working for me now. If anyone feels like further debugging,
I'm all game.
It probably has something to do with the virtual/physical gymnastics ACPI
has to do to map its
Thus spake Nate Lawson ([EMAIL PROTECTED]) [16/09/03 16:24]:
I have no time to track this down but the output of acpidump -t may help
someone else who might be interested. You're looking for the pointers
that are stored in RSD PTR.
I'm still on 5.1-R, and there's no '-t' flag to acpidump.
on 5.1-R, and there's no '-t' flag to acpidump. However, I've
posted the dump on the web:
http://www.sentex.net/~damian/acpidump
so people can browse as they wish.
As expected, your ACPI tables are at the top of physmem: RSDT=0x1fff3000.
This is only 52k from 512MB. Something in how MAXMEM
Nate Lawson wrote:
On Wed, 17 Sep 2003, Andrew Thompson wrote:
(gdb) l *scsuspend+0x17
0xc03d7b17 is in scsuspend (/usr/src/sys/isa/syscons_isa.c:111).
106 int retry = 10;
107 static int dummy;
108 sc_softc_t *sc;
109
110 sc =
Thus spake Nate Lawson ([EMAIL PROTECTED]) [13/09/03 14:42]:
The post you reference shows the user with a kernel that has both APM and
ACPI installed, apparently. This is not valid.
Please report your kernel config. If GENERIC in 2003/9/6 booted fine with
ACPI and then your rebuilt kernel
(To recap: I'm having ACPI problems on a DFI CD70-SC, with both 5.1-R and
5-CURRENT. Booting GENERIC doesn't show any problems, however, so there's a
good chance it's a misconfiguration issue.)
Thus spake Damian Gerow ([EMAIL PROTECTED]) [15/09/03 17:34]:
It's attached. There's no APM
The post you reference shows the user with a kernel that has both APM and
ACPI installed, apparently. This is not valid.
Please report your kernel config. If GENERIC in 2003/9/6 booted fine with
ACPI and then your rebuilt kernel from 2003/9/7 fails, it is almost
certainly the devices you
Nate Lawson [EMAIL PROTECTED] writes:
Please report the dmesg from boot -v as that should help figure out why
pci_cfgregopen() fails.
Full log attached, both with and without ACPI.
Also, I think the following should be \_S3:
Name (\SS3, Package (0x04)
That shouldn't have any impact on my
On Tue, 9 Sep 2003, Dag-Erling [iso-8859-1] Smørgrav wrote:
Nate Lawson [EMAIL PROTECTED] writes:
Please report the dmesg from boot -v as that should help figure out why
pci_cfgregopen() fails.
Full log attached, both with and without ACPI.
Perhaps someone who knows our PCI code better
The Compaq Evo N610c that I'm having all these acpi problems with will
be at bsdcon, if anyone wants to take a look.
Doug
--
This .signature sanitized for your protection
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman
Doug,
We have already posted some info about the N610c here in the mailing
list. I've got a acpi code uploadable from the bootloader to bios
available:
http://www.guldan.cistron.nl/acpi_dsdt.dsl
This code can be compiled using iasl from the acpicatools port.
This produces a aml code
On Mon, 8 Sep 2003, Robert [unknown-8bit] Blacquière wrote:
Doug,
We have already posted some info about the N610c here in the mailing
list. I've got a acpi code uploadable from the bootloader to bios
available:
http://www.guldan.cistron.nl/acpi_dsdt.dsl
This code can be compiled
Could you post a diff -u of this against the original ASL so I can know
what issues it had?
Thanks,
Nate
On Mon, 8 Sep 2003, Robert [unknown-8bit] Blacquière wrote:
Doug,
We have already posted some info about the N610c here in the mailing
list. I've got a acpi code uploadable from
On Wed, 30 Jul 2003, Cagle, John (ISS-Houston) wrote:
I have a feeling that my acpi table didn't actually get overridden
though, due to the following from dmesg:
ACPI: DSDT was overridden.
-0424: *** Error: UtAllocate: Could not allocate size 6e49202a
ACPI-0428: *** Error: Could
Hi,
It's a lot ... 9666 lines... so i put it up on de site.
plus the acpi code from current running bios.
working patched version:
http://www.guldan.cistron.nl/acpi_dsdt.dsl
in bios version:
http://www.guldan.cistron.nl/acpi_dsdt_orig.dsl
and the diff -u
http
against *orig.
-Nate
On Mon, 8 Sep 2003, Robert [unknown-8bit] Blacquière wrote:
It's a lot ... 9666 lines... so i put it up on de site.
plus the acpi code from current running bios.
working patched version:
http://www.guldan.cistron.nl/acpi_dsdt.dsl
in bios version:
http
501 - 600 of 1744 matches
Mail list logo
