Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Wednesday, 14 November 2018 12:41:53 MST Stefan Ehmann wrote: > On 11/14/18 5:41 AM, Conrad Meyer wrote: > > Ok I'll go ahead and commit that too. > > Applied to 12.0-BETA, Ryzen 7 2700 values are now in the 30-55C range. > Looks reasonable. Much better here, too: dev.amdtemp.3.core0.sensor0: 38.1C dev.amdtemp.3.sensor_offset: -27 dev.amdtemp.2.core0.sensor0: 39.0C dev.amdtemp.2.sensor_offset: -27 dev.amdtemp.1.core0.sensor0: 37.5C dev.amdtemp.1.sensor_offset: -27 dev.amdtemp.0.core0.sensor0: 40.1C dev.amdtemp.0.sensor_offset: -27 Thanks! Rebecca ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On 11/14/18 5:41 AM, Conrad Meyer wrote: > You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL? > I.e., sometimes the CPU chooses to report on a range from 0-225C and > sometimes -49C-206C. I think someone else's 2990WX did the same > thing. I guess that patch never landed? 102°C - 49°C is the very > reasonable 53°C. > > Yeah, sigh, it never landed: https://reviews.freebsd.org/D16855 > > Ok I'll go ahead and commit that too. Applied to 12.0-BETA, Ryzen 7 2700 values are now in the 30-55C range. Looks reasonable. Thanks! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
Perfect! Sounds like we are on the right track, at least. Best, Conrad On Tue, Nov 13, 2018 at 8:55 PM Rebecca Cran wrote: > > On Tuesday, 13 November 2018 21:41:58 MST Conrad Meyer wrote: > > You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL? > > I.e., sometimes the CPU chooses to report on a range from 0-225C and > > sometimes -49C-206C. I think someone else's 2990WX did the same > > thing. I guess that patch never landed? 102°C - 49°C is the very > > reasonable 53°C. > > > > Yeah, sigh, it never landed: https://reviews.freebsd.org/D16855 > > Thanks, that's it: setting the sensor_offset sysctls to -76 results in FreeBSD > reporting 51.1C while the readout on the motherboard shows 51C :) > > I'll fetch and build r340426 tomorrow. > > -- > Rebecca > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tuesday, 13 November 2018 21:41:58 MST Conrad Meyer wrote: > You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL? > I.e., sometimes the CPU chooses to report on a range from 0-225C and > sometimes -49C-206C. I think someone else's 2990WX did the same > thing. I guess that patch never landed? 102°C - 49°C is the very > reasonable 53°C. > > Yeah, sigh, it never landed: https://reviews.freebsd.org/D16855 Thanks, that's it: setting the sensor_offset sysctls to -76 results in FreeBSD reporting 51.1C while the readout on the motherboard shows 51C :) I'll fetch and build r340426 tomorrow. -- Rebecca ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
Please try r340426 :-). On Tue, Nov 13, 2018 at 8:41 PM Conrad Meyer wrote: > > You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL? > I.e., sometimes the CPU chooses to report on a range from 0-225C and > sometimes -49C-206C. I think someone else's 2990WX did the same > thing. I guess that patch never landed? 102°C - 49°C is the very > reasonable 53°C. > > Yeah, sigh, it never landed: https://reviews.freebsd.org/D16855 > > Ok I'll go ahead and commit that too. > > Thanks, > Conrad > On Tue, Nov 13, 2018 at 8:38 PM Conrad Meyer wrote: > > > > On Tue, Nov 13, 2018 at 8:29 PM Rebecca Cran wrote: > > > > > > On Tuesday, 13 November 2018 21:17:59 MST Conrad Meyer wrote: > > > > > > > Maybe it should be -54 instead of +54? 183-(54*2) is the somewhat > > > > plausible 75?C (still pretty warm even for load). How good is your > > > > cooling solution? > > > > > > D'oh, of course it's -54 instead of +54 (For some reason I presumed a > > > positive > > > offset would be *subtracted*)! I have an all-in-one liquid thermaltake > > > cooler installed, and under Windows it reports reaching 67C when running > > > flat > > > out, which doesn't seem bad. > > > > Yeah, 67C seems totally great at load. > > > > > > (The references I can find with a quick search suggest TR 29xx should > > > > also be -27? rather than -54?C, but they may be mistaken. 183-54-27 > > > > is still 102?C ? extremely hot!) > > > > > > That's why I thought 54 was more likely! My 2990WX has 4 units for 32 > > > cores > > > instead of 2 units and 16 cores for other models, so I guessed that > > > perhaps I > > > should double the 27 value other people had said should be used. > > > > Hm, the Linux folks still use -27 for the 2990WX as well as all of the > > other threadripper models. I'm not sure what's right. I wish I had > > access to the Ryzen 2 register docs, but I don't. > > > > Best, > > Conrad ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
You know what, I wonder if you're running into the CUR_TEMP_RANGE_SEL? I.e., sometimes the CPU chooses to report on a range from 0-225C and sometimes -49C-206C. I think someone else's 2990WX did the same thing. I guess that patch never landed? 102°C - 49°C is the very reasonable 53°C. Yeah, sigh, it never landed: https://reviews.freebsd.org/D16855 Ok I'll go ahead and commit that too. Thanks, Conrad On Tue, Nov 13, 2018 at 8:38 PM Conrad Meyer wrote: > > On Tue, Nov 13, 2018 at 8:29 PM Rebecca Cran wrote: > > > > On Tuesday, 13 November 2018 21:17:59 MST Conrad Meyer wrote: > > > > > Maybe it should be -54 instead of +54? 183-(54*2) is the somewhat > > > plausible 75?C (still pretty warm even for load). How good is your > > > cooling solution? > > > > D'oh, of course it's -54 instead of +54 (For some reason I presumed a > > positive > > offset would be *subtracted*)! I have an all-in-one liquid thermaltake > > cooler installed, and under Windows it reports reaching 67C when running > > flat > > out, which doesn't seem bad. > > Yeah, 67C seems totally great at load. > > > > (The references I can find with a quick search suggest TR 29xx should > > > also be -27? rather than -54?C, but they may be mistaken. 183-54-27 > > > is still 102?C ? extremely hot!) > > > > That's why I thought 54 was more likely! My 2990WX has 4 units for 32 cores > > instead of 2 units and 16 cores for other models, so I guessed that perhaps > > I > > should double the 27 value other people had said should be used. > > Hm, the Linux folks still use -27 for the 2990WX as well as all of the > other threadripper models. I'm not sure what's right. I wish I had > access to the Ryzen 2 register docs, but I don't. > > Best, > Conrad ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tue, Nov 13, 2018 at 8:29 PM Rebecca Cran wrote: > > On Tuesday, 13 November 2018 21:17:59 MST Conrad Meyer wrote: > > > Maybe it should be -54 instead of +54? 183-(54*2) is the somewhat > > plausible 75?C (still pretty warm even for load). How good is your > > cooling solution? > > D'oh, of course it's -54 instead of +54 (For some reason I presumed a positive > offset would be *subtracted*)! I have an all-in-one liquid thermaltake > cooler installed, and under Windows it reports reaching 67C when running flat > out, which doesn't seem bad. Yeah, 67C seems totally great at load. > > (The references I can find with a quick search suggest TR 29xx should > > also be -27? rather than -54?C, but they may be mistaken. 183-54-27 > > is still 102?C ? extremely hot!) > > That's why I thought 54 was more likely! My 2990WX has 4 units for 32 cores > instead of 2 units and 16 cores for other models, so I guessed that perhaps I > should double the 27 value other people had said should be used. Hm, the Linux folks still use -27 for the 2990WX as well as all of the other threadripper models. I'm not sure what's right. I wish I had access to the Ryzen 2 register docs, but I don't. Best, Conrad ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tuesday, 13 November 2018 21:17:59 MST Conrad Meyer wrote: > Maybe it should be -54 instead of +54? 183-(54*2) is the somewhat > plausible 75?C (still pretty warm even for load). How good is your > cooling solution? D'oh, of course it's -54 instead of +54 (For some reason I presumed a positive offset would be *subtracted*)! I have an all-in-one liquid thermaltake cooler installed, and under Windows it reports reaching 67C when running flat out, which doesn't seem bad. > (The references I can find with a quick search suggest TR 29xx should > also be -27? rather than -54?C, but they may be mistaken. 183-54-27 > is still 102?C ? extremely hot!) That's why I thought 54 was more likely! My 2990WX has 4 units for 32 cores instead of 2 units and 16 cores for other models, so I guessed that perhaps I should double the 27 value other people had said should be used. -- Rebecca ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tue, Nov 13, 2018 at 8:05 PM Rebecca Cran wrote: > > On Tuesday, 13 November 2018 16:20:22 MST Stefan Ehmann wrote: > > > The 2700 has an offset of 0 though (2700X has 10). > > And I'm seeing a difference of more than 30 degrees. I guess something > > else must be happening here. > > I had thought 54 was the right offset for my 2990WX system, but now it's under > load building ports the temperature reported via dev.amdtemp is 183C! > Meanwhile the readout on the motherboard says "CPU Temp 53 C". Maybe it should be -54 instead of +54? 183-(54*2) is the somewhat plausible 75°C (still pretty warm even for load). How good is your cooling solution? (The references I can find with a quick search suggest TR 29xx should also be -27° rather than -54°C, but they may be mistaken. 183-54-27 is still 102°C — extremely hot!) Best, Conrad ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tue, Nov 13, 2018 at 7:16 PM Daniel Eischen wrote: > > On Tue, 13 Nov 2018, Conrad Meyer wrote: > > > On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote: > >> I've attached it. If it gets filtered by the mail list, I'll > >> make it http accessible. > > > > Thanks Daniel. > > > > It looks like your hostbridge zero device has a different device id > > than in my first generation Ryzen system. Would you please try the > > following patch and see if it attaches on your system? I don't > > actually have documentation for Ryzen 2, unfortunately, so I'm not > > totally sure if the SMN is accessed in the same way for the new > > hostbridge device id. The change below should at least attempt > > attaching to hostb0 on your system. > > That seems to have done the trick, thanks! Output > attached. Thanks for the quick test! I've committed Johannes' substantially similar patch as r340425. Cheers, Conrad ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tuesday, 13 November 2018 16:20:22 MST Stefan Ehmann wrote: > The 2700 has an offset of 0 though (2700X has 10). > And I'm seeing a difference of more than 30 degrees. I guess something > else must be happening here. I had thought 54 was the right offset for my 2990WX system, but now it's under load building ports the temperature reported via dev.amdtemp is 183C! Meanwhile the readout on the motherboard says "CPU Temp 53 C". -- Rebecca ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tue, 13 Nov 2018, Conrad Meyer wrote: On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote: I've attached it. If it gets filtered by the mail list, I'll make it http accessible. Thanks Daniel. It looks like your hostbridge zero device has a different device id than in my first generation Ryzen system. Would you please try the following patch and see if it attaches on your system? I don't actually have documentation for Ryzen 2, unfortunately, so I'm not totally sure if the SMN is accessed in the same way for the new hostbridge device id. The change below should at least attempt attaching to hostb0 on your system. That seems to have done the trick, thanks! Output attached. -- DEnet.inet6.ip6.use_tempaddr: 0 net.inet6.ip6.temppltime: 86400 net.inet6.ip6.tempvltime: 604800 net.inet6.ip6.prefer_tempaddr: 0 hw.usb.template: -1 kstat.zfs.misc.arcstats.arc_tempreserve: 0 kstat.zfs.misc.zcompstats.attempts: 18438 dev.amdtemp.0.core0.sensor0: 28.1C dev.amdtemp.0.sensor_offset: 0 dev.amdtemp.0.%parent: hostb0 dev.amdtemp.0.%pnpinfo: dev.amdtemp.0.%location: dev.amdtemp.0.%driver: amdtemp dev.amdtemp.0.%desc: AMD CPU On-Die Thermal Sensors dev.amdtemp.%parent: dev.cpu.7.temperature: 28.1C dev.cpu.6.temperature: 28.1C dev.cpu.5.temperature: 28.1C dev.cpu.4.temperature: 28.1C dev.cpu.3.temperature: 28.1C dev.cpu.2.temperature: 28.1C dev.cpu.1.temperature: 28.1C dev.cpu.0.temperature: 28.1C ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
Of course, Johannes has already thought of this! See
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228480 and
https://reviews.freebsd.org/D15567 .
On Tue, Nov 13, 2018 at 6:41 PM Conrad Meyer wrote:
>
> On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote:
> > I've attached it. If it gets filtered by the mail list, I'll
> > make it http accessible.
>
> Thanks Daniel.
>
> It looks like your hostbridge zero device has a different device id
> than in my first generation Ryzen system. Would you please try the
> following patch and see if it attaches on your system? I don't
> actually have documentation for Ryzen 2, unfortunately, so I'm not
> totally sure if the SMN is accessed in the same way for the new
> hostbridge device id. The change below should at least attempt
> attaching to hostb0 on your system.
>
> diff --git a/sys/dev/amdsmn/amdsmn.c b/sys/dev/amdsmn/amdsmn.c
> index 17792dd922cd..6fe36b4cc4da 100644
> --- a/sys/dev/amdsmn/amdsmn.c
> +++ b/sys/dev/amdsmn/amdsmn.c
> @@ -60,7 +60,8 @@ struct amdsmn_softc {
> static struct pciid {
> uint32_tdevice_id;
> } amdsmn_ids[] = {
> - { 0x14501022 },
> + { 0x14501022 }, /* Ryzen */
> + { 0x15d01022 }, /* Ryzen 2 */
> };
>
> /*
> diff --git a/sys/dev/amdtemp/amdtemp.c b/sys/dev/amdtemp/amdtemp.c
> index 2463212c25f5..765e660a8461 100644
> --- a/sys/dev/amdtemp/amdtemp.c
> +++ b/sys/dev/amdtemp/amdtemp.c
> @@ -102,6 +102,7 @@ static struct amdtemp_product {
> { VENDORID_AMD, DEVICEID_AMD_MISC16_M30H },
> { VENDORID_AMD, DEVICEID_AMD_MISC17 },
> { VENDORID_AMD, DEVICEID_AMD_HOSTB17H },
> + { VENDORID_AMD, 0x15d0 },
> };
>
> /*
>
>
> Thanks,
> Conrad
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tue, Nov 13, 2018 at 6:26 PM Daniel Eischen wrote:
> I've attached it. If it gets filtered by the mail list, I'll
> make it http accessible.
Thanks Daniel.
It looks like your hostbridge zero device has a different device id
than in my first generation Ryzen system. Would you please try the
following patch and see if it attaches on your system? I don't
actually have documentation for Ryzen 2, unfortunately, so I'm not
totally sure if the SMN is accessed in the same way for the new
hostbridge device id. The change below should at least attempt
attaching to hostb0 on your system.
diff --git a/sys/dev/amdsmn/amdsmn.c b/sys/dev/amdsmn/amdsmn.c
index 17792dd922cd..6fe36b4cc4da 100644
--- a/sys/dev/amdsmn/amdsmn.c
+++ b/sys/dev/amdsmn/amdsmn.c
@@ -60,7 +60,8 @@ struct amdsmn_softc {
static struct pciid {
uint32_tdevice_id;
} amdsmn_ids[] = {
- { 0x14501022 },
+ { 0x14501022 }, /* Ryzen */
+ { 0x15d01022 }, /* Ryzen 2 */
};
/*
diff --git a/sys/dev/amdtemp/amdtemp.c b/sys/dev/amdtemp/amdtemp.c
index 2463212c25f5..765e660a8461 100644
--- a/sys/dev/amdtemp/amdtemp.c
+++ b/sys/dev/amdtemp/amdtemp.c
@@ -102,6 +102,7 @@ static struct amdtemp_product {
{ VENDORID_AMD, DEVICEID_AMD_MISC16_M30H },
{ VENDORID_AMD, DEVICEID_AMD_MISC17 },
{ VENDORID_AMD, DEVICEID_AMD_HOSTB17H },
+ { VENDORID_AMD, 0x15d0 },
};
/*
Thanks,
Conrad
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tue, 13 Nov 2018, Conrad Meyer wrote: Hi Daniel, On Tue, Nov 13, 2018 at 10:01 AM Daniel Eischen wrote: Greetings, I'm trying to track down a couple of things. amdtemp doesn't report any temperature sensors, and acpi seems to have some errors. Not sure if they are related. Maybe not. If they do not attach, it suggests that maybe the Ryzen 2 has a different hostbridge PCI devid. ... The amdtemp module loads fine (including the dependent amdsmn), but doesn't report any temperature related sysctls. Can you run 'devinfo -v' and send or paste the output? Thank you. I've attached it. If it gets filtered by the mail list, I'll make it http accessible. -- DEnexus0 cryptosoft0 vtvga0 apic0 ram0 acpi0 cpu0 pnpinfo _HID=none _UID=0 at handle=\_PR_.P000 acpi_perf0 hwpstate0 acpi_throttle0 cpufreq0 cpu1 pnpinfo _HID=none _UID=0 at handle=\_PR_.P001 acpi_perf1 hwpstate1 acpi_throttle1 cpu2 pnpinfo _HID=none _UID=0 at handle=\_PR_.P002 acpi_perf2 hwpstate2 acpi_throttle2 cpu3 pnpinfo _HID=none _UID=0 at handle=\_PR_.P003 acpi_perf3 hwpstate3 acpi_throttle3 cpu4 pnpinfo _HID=none _UID=0 at handle=\_PR_.P004 acpi_perf4 hwpstate4 acpi_throttle4 cpu5 pnpinfo _HID=none _UID=0 at handle=\_PR_.P005 acpi_perf5 hwpstate5 acpi_throttle5 cpu6 pnpinfo _HID=none _UID=0 at handle=\_PR_.P006 acpi_perf6 hwpstate6 acpi_throttle6 cpu7 pnpinfo _HID=none _UID=0 at handle=\_PR_.P007 acpi_perf7 hwpstate7 acpi_throttle7 unknown pnpinfo _HID=none _UID=0 at handle=\_PR_.P008 unknown pnpinfo _HID=none _UID=0 at handle=\_PR_.P009 unknown pnpinfo _HID=none _UID=0 at handle=\_PR_.P00A unknown pnpinfo _HID=none _UID=0 at handle=\_PR_.P00B unknown pnpinfo _HID=none _UID=0 at handle=\_PR_.P00C unknown pnpinfo _HID=none _UID=0 at handle=\_PR_.P00D unknown pnpinfo _HID=none _UID=0 at handle=\_PR_.P00E unknown pnpinfo _HID=none _UID=0 at handle=\_PR_.P00F pcib0 pnpinfo _HID=PNP0A08 _UID=0 at handle=\_SB_.PCI0 pci0 hostb0 pnpinfo vendor=0x1022 device=0x15d0 subvendor=0x1043 subdevice=0x876b class=0x06 at slot=0 function=0 dbsf=pci0:0:0:0 handle=\_SB_.PCI0.D004 unknown pnpinfo vendor=0x1022 device=0x15d1 subvendor=0x1022 subdevice=0x15d1 class=0x080600 at slot=0 function=2 dbsf=pci0:0:0:2 handle=\_SB_.PCI0.IOMA hostb1 pnpinfo vendor=0x1022 device=0x1452 subvendor=0x subdevice=0x class=0x06 at slot=1 function=0 dbsf=pci0:0:1:0 pcib1 pnpinfo vendor=0x1022 device=0x15d3 subvendor=0x1043 subdevice=0x876b class=0x060400 at slot=1 function=2 dbsf=pci0:0:1:2 handle=\_SB_.PCI0.GPP1 pci1 xhci0 pnpinfo vendor=0x1022 device=0x43d0 subvendor=0x1b21 subdevice=0x1142 class=0x0c0330 at slot=0 function=0 dbsf=pci0:1:0:0 handle=\_SB_.PCI0.GPP1.PTXH usbus0 uhub2 ahci0 pnpinfo vendor=0x1022 device=0x43c8 subvendor=0x1b21 subdevice=0x1062 class=0x010601 at slot=0 function=1 dbsf=pci0:1:0:1 handle=\_SB_.PCI0.GPP1.PT01 ahcich0 at channel=0 ahcich1 at channel=1 ahcich2 at channel=2 ahcich3 at channel=3 ahcich4 at channel=4 ahcich5 at channel=5 ahcich6 at channel=6 ahcich7 at channel=7 pcib2 pnpinfo vendor=0x1022 device=0x43c6 subvendor=0x1b21 subdevice=0x0201 class=0x060400 at slot=0 function=2 dbsf=pci0:1:0:2 handle=\_SB_.PCI0.GPP1.PT02 pci2 pcib3 pnpinfo vendor=0x1022 device=0x43c7 subvendor=0x1b21 subdevice=0x3306 class=0x060400 at slot=0 function=0 dbsf=pci0:2:0:0 handle=\_SB_.PCI0.GPP1.PT02.PT20 pci3 pcib4 pnpinfo vendor=0x1022 device=0x43c7 subvendor=0x1b21 subdevice=0x3306 class=0x060400 at slot=4 function=0 dbsf=pci0:2:4:0 handle=\_SB_.PCI0.GPP1.PT02.PT24 pci4 xhci1 pnpinfo vendor=0x1b21 device=0x1242 subvendor=0x1043 subdevice=0x8675 class=0x0c0330 at slot=0 function=0 dbsf=pci0:4:0:0 handle=\_SB_.PCI0.GPP1.PT02.PT24.AS42 usbus1 uhub0 ukbd0 pnpinfo vendor=0x046d product=0xc31c devclass=0x00 devsubclass=0x00 devproto=0x00 sernum="" release=0x6400 mode=host intclass=0x03 intsubclass=0x01 intprotocol=0x01 at bus=1 hubaddr=1 port=3 devaddr=2 interface=0 ugen=ugen1.2 uhid0 pnpinfo vendor=0x046d product=0xc31c devclass=0x00 devsubclass=0x00 devproto=0x00 sernum="" release=0x6400 mode=host intclass=0x03 intsubclass=0x00 intprotocol=0x00 at bus=1 hubaddr=1 port=3 devaddr=2 interface=1 ugen=ugen1.2 ums0 pnpinfo vendor=0x046d product=0xc014 devclass=0x00 devsubclass=0x00 devproto=0x00 sernum="" release=0x0340 mode=host intclass=0x03 intsubclass=0x
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tue, Nov 13, 2018 at 5:15 PM Rozhuk Ivan wrote: > > On Tue, 13 Nov 2018 19:41:47 -0500 > Daniel Eischen wrote: > > > >> I'm trying to track down a couple of things. amdtemp doesn't > > >> report any temperature sensors, and acpi seems to have some > > >> errors. Not sure if they are related. > > > > > > It s a bit legacy ) > > > Try mine: http://www.netlab.linkpc.net/download/tmp/amdtemp.c > > > does not use amdsmn. > > > > Thanks, I think?! I tried it and it panic'd as soon as it was > > kldload'd. I don't have the trace back handy, but it was in a mtx > > lock after a pci_write. I'm running 13-current, so it could be > > something different between that and -stable or whatever you're > > testing it on. > > > I do not test it on 13. > Make sure that you have not amdtemp and amdsmn built in kernel and that they > not loaded. Your amdtemp_rtc_temp_sysctl has a lock recursion bug and any INVARIANTS kernel will panic running it. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tue, 13 Nov 2018 19:41:47 -0500 Daniel Eischen wrote: > >> I'm trying to track down a couple of things. amdtemp doesn't > >> report any temperature sensors, and acpi seems to have some > >> errors. Not sure if they are related. > > > > It s a bit legacy ) > > Try mine: http://www.netlab.linkpc.net/download/tmp/amdtemp.c > > does not use amdsmn. > > Thanks, I think?! I tried it and it panic'd as soon as it was > kldload'd. I don't have the trace back handy, but it was in a mtx > lock after a pci_write. I'm running 13-current, so it could be > something different between that and -stable or whatever you're > testing it on. I do not test it on 13. Make sure that you have not amdtemp and amdsmn built in kernel and that they not loaded. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
Hi Daniel, On Tue, Nov 13, 2018 at 10:01 AM Daniel Eischen wrote: > > Greetings, > > I'm trying to track down a couple of things. amdtemp doesn't > report any temperature sensors, and acpi seems to have some > errors. Not sure if they are related. Maybe not. If they do not attach, it suggests that maybe the Ryzen 2 has a different hostbridge PCI devid. > ... > The amdtemp module loads fine (including the dependent amdsmn), but > doesn't report any temperature related sysctls. Can you run 'devinfo -v' and send or paste the output? Thank you. All the best, Conrad ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
> On Nov 13, 2018, at 2:06 PM, Rozhuk Ivan wrote: > > On Tue, 13 Nov 2018 12:59:59 -0500 (EST) > Daniel Eischen wrote: > >> I'm trying to track down a couple of things. amdtemp doesn't >> report any temperature sensors, and acpi seems to have some >> errors. Not sure if they are related. > > It s a bit legacy ) > Try mine: http://www.netlab.linkpc.net/download/tmp/amdtemp.c > does not use amdsmn. Thanks, I think?! I tried it and it panic'd as soon as it was kldload'd. I don't have the trace back handy, but it was in a mtx lock after a pci_write. I'm running 13-current, so it could be something different between that and -stable or whatever you're testing it on. -- DE ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On 11/13/18 10:14 PM, Conrad Meyer wrote: > On Tue, Nov 13, 2018 at 1:04 PM Stefan Ehmann wrote: >> After kldload amdtemp I see the following sysctls: >> dev.cpu.0.temperature: 77.1C >> dev.amdtemp.0.core0.sensor0: 77.1C >> >> The temperature I see in BIOS is much lower (maybe around 40.0C). Don't >> know if just the offset is wrong or the numbers are completely bogus. >> >> Numbers from sysutils/xmbmon look saner but not sure if they are correct. > > You can adjust dev.amdtemp.N.sensor_offset as needed. By default, the > amdtemp sysctl gives you the unadjusted value. On different Ryzen > models the raw value is wrong by different amounts. E.g. on my 1950X, > I have sensor_offset set to "-27" to show correct temperature > readings. > > See this link for a table of offset values for various Ryzen models: > https://www.guru3d.com/articles-pages/amd-ryzen-7-2700-review,7.html Thanks for the link. The 2700 has an offset of 0 though (2700X has 10). And I'm seeing a difference of more than 30 degrees. I guess something else must be happening here. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On 11/13/18 10:40 PM, Daniel Eischen wrote: > >> On Nov 13, 2018, at 4:02 PM, Stefan Ehmann wrote: >> >>> On 11/13/18 8:59 PM, Daniel Eischen wrote: On Tue, 13 Nov 2018, Greg V wrote: On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen wrote: > Greetings, > > I'm trying to track down a couple of things. amdtemp doesn't > report any temperature sensors, and acpi seems to have some > errors. Not sure if they are related. > > These are the ACPI-related warnings and errors during boot. > >Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has > valid Length but zero Address: 0x/0x1 > (20181031/tbfadt-796) I see this one on my R7 1700 / X370 system, seems harmless. >> >> I also see this warning on the X470-pro with Ryzen 7 2700 on 12.0-BETA. >> But I don't get the Firmware errors below. > > What BIOS version are you using? I'm running 13-current built from just a > few days ago. Never had any temp sysctls since initial install (beginning of > October). Latest Version (4024), but I think I've tried it before with an older version. Didn't notice any differences though. But I guess amdtemp is more dependent on the CPU than on the main board. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tue, 13 Nov 2018 13:14:46 -0800 Conrad Meyer wrote: > You can adjust dev.amdtemp.N.sensor_offset as needed. By default, the > amdtemp sysctl gives you the unadjusted value. On different Ryzen > models the raw value is wrong by different amounts. E.g. on my 1950X, > I have sensor_offset set to "-27" to show correct temperature > readings. > Looks like new AGESA/BIOS change something, my fork of amdtemp now show (read) same value as on onboard led in "CurTmpTjSel" ... dev.amdtemp.0.rtc.CurTmpTjSel: 47.7C dev.amdtemp.0.rtc.CurTmp: 96.7C ... 49C diff, this was some sort of offset for older AMD CPU, used to calc CurTmpTjSel then it set to 3. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
> On Nov 13, 2018, at 4:02 PM, Stefan Ehmann wrote:
>
>> On 11/13/18 8:59 PM, Daniel Eischen wrote:
>>> On Tue, 13 Nov 2018, Greg V wrote:
>>>
>>>
>>>
>>> On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen
>>> wrote:
Greetings,
I'm trying to track down a couple of things. amdtemp doesn't
report any temperature sensors, and acpi seems to have some
errors. Not sure if they are related.
These are the ACPI-related warnings and errors during boot.
Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has
valid Length but zero Address: 0x/0x1
(20181031/tbfadt-796)
>>>
>>> I see this one on my R7 1700 / X370 system, seems harmless.
>
> I also see this warning on the X470-pro with Ryzen 7 2700 on 12.0-BETA.
> But I don't get the Firmware errors below.
What BIOS version are you using? I'm running 13-current built from just a few
days ago. Never had any temp sysctls since initial install (beginning of
October).
acpi0: on motherboard
Firmware Error (ACPI): Failure creating [\134_SB.SMIC],
AE_ALREADY_EXISTS (20181031/dswload2-477)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
(20181031/psobject-372)
Firmware Error (ACPI): Failure creating [\134_SB.SMIB],
AE_ALREADY_EXISTS (20181031/dsfield-803)
>>>
>>> Looks like people see these on Linux:
>>>
>>> https://forum.manjaro.org/t/unstable-behaviour-not-always-completely-booting/55823/5
>>>
>>>
>>> Are you on the latest firmware ("BIOS") revision for your board?
>>
>> Yes, it's an ASUS Prime X-470 PRO, and I'm running with the latest
>> BIOS from 2018 September 21, version 4024.
>>
>> https://www.asus.com/us/Motherboards/PRIME-X470-PRO/HelpDesk_BIOS/
>>
>
> After kldload amdtemp I see the following sysctls:
> dev.cpu.0.temperature: 77.1C
> dev.amdtemp.0.core0.sensor0: 77.1C
>
> The temperature I see in BIOS is much lower (maybe around 40.0C). Don't
> know if just the offset is wrong or the numbers are completely bogus.
>
> Numbers from sysutils/xmbmon look saner but not sure if they are correct.
Yeah, I don't have any sensors detected, but my BIOS reports around 39C, right
around the same as yours. There are both motherboard and CPU temps in BIOS,
reporting just a couple of degrees difference.
Overall, this system is very stable, haven't had any crashes or hangs.
--
DE
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tue, Nov 13, 2018 at 1:04 PM Stefan Ehmann wrote: > After kldload amdtemp I see the following sysctls: > dev.cpu.0.temperature: 77.1C > dev.amdtemp.0.core0.sensor0: 77.1C > > The temperature I see in BIOS is much lower (maybe around 40.0C). Don't > know if just the offset is wrong or the numbers are completely bogus. > > Numbers from sysutils/xmbmon look saner but not sure if they are correct. You can adjust dev.amdtemp.N.sensor_offset as needed. By default, the amdtemp sysctl gives you the unadjusted value. On different Ryzen models the raw value is wrong by different amounts. E.g. on my 1950X, I have sensor_offset set to "-27" to show correct temperature readings. See this link for a table of offset values for various Ryzen models: https://www.guru3d.com/articles-pages/amd-ryzen-7-2700-review,7.html Take care, Conrad ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On 11/13/18 8:59 PM, Daniel Eischen wrote:
> On Tue, 13 Nov 2018, Greg V wrote:
>
>>
>>
>> On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen
>> wrote:
>>> Greetings,
>>>
>>> I'm trying to track down a couple of things. amdtemp doesn't
>>> report any temperature sensors, and acpi seems to have some
>>> errors. Not sure if they are related.
>>>
>>> These are the ACPI-related warnings and errors during boot.
>>>
>>> Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has
>>> valid Length but zero Address: 0x/0x1
>>> (20181031/tbfadt-796)
>>
>> I see this one on my R7 1700 / X370 system, seems harmless.
I also see this warning on the X470-pro with Ryzen 7 2700 on 12.0-BETA.
But I don't get the Firmware errors below.
>>> acpi0: on motherboard
>>> Firmware Error (ACPI): Failure creating [\134_SB.SMIC],
>>> AE_ALREADY_EXISTS (20181031/dswload2-477)
>>> ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
>>> (20181031/psobject-372)
>>> Firmware Error (ACPI): Failure creating [\134_SB.SMIB],
>>> AE_ALREADY_EXISTS (20181031/dsfield-803)
>>
>> Looks like people see these on Linux:
>>
>> https://forum.manjaro.org/t/unstable-behaviour-not-always-completely-booting/55823/5
>>
>>
>> Are you on the latest firmware ("BIOS") revision for your board?
>
> Yes, it's an ASUS Prime X-470 PRO, and I'm running with the latest
> BIOS from 2018 September 21, version 4024.
>
> https://www.asus.com/us/Motherboards/PRIME-X470-PRO/HelpDesk_BIOS/
>
After kldload amdtemp I see the following sysctls:
dev.cpu.0.temperature: 77.1C
dev.amdtemp.0.core0.sensor0: 77.1C
The temperature I see in BIOS is much lower (maybe around 40.0C). Don't
know if just the offset is wrong or the numbers are completely bogus.
Numbers from sysutils/xmbmon look saner but not sure if they are correct.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tue, 13 Nov 2018, Greg V wrote:
On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen wrote:
Greetings,
I'm trying to track down a couple of things. amdtemp doesn't
report any temperature sensors, and acpi seems to have some
errors. Not sure if they are related.
These are the ACPI-related warnings and errors during boot.
Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid
Length but zero Address: 0x/0x1 (20181031/tbfadt-796)
I see this one on my R7 1700 / X370 system, seems harmless.
acpi0: on motherboard
Firmware Error (ACPI): Failure creating [\134_SB.SMIC],
AE_ALREADY_EXISTS (20181031/dswload2-477)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
(20181031/psobject-372)
Firmware Error (ACPI): Failure creating [\134_SB.SMIB],
AE_ALREADY_EXISTS (20181031/dsfield-803)
Looks like people see these on Linux:
https://forum.manjaro.org/t/unstable-behaviour-not-always-completely-booting/55823/5
Are you on the latest firmware ("BIOS") revision for your board?
Yes, it's an ASUS Prime X-470 PRO, and I'm running with the latest
BIOS from 2018 September 21, version 4024.
https://www.asus.com/us/Motherboards/PRIME-X470-PRO/HelpDesk_BIOS/
--
DE
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tue, Nov 13, 2018 at 8:59 PM, Daniel Eischen
wrote:
Greetings,
I'm trying to track down a couple of things. amdtemp doesn't
report any temperature sensors, and acpi seems to have some
errors. Not sure if they are related.
These are the ACPI-related warnings and errors during boot.
Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has
valid Length but zero Address: 0x/0x1
(20181031/tbfadt-796)
I see this one on my R7 1700 / X370 system, seems harmless.
acpi0: on motherboard
Firmware Error (ACPI): Failure creating [\134_SB.SMIC],
AE_ALREADY_EXISTS (20181031/dswload2-477)
ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog
(20181031/psobject-372)
Firmware Error (ACPI): Failure creating [\134_SB.SMIB],
AE_ALREADY_EXISTS (20181031/dsfield-803)
Looks like people see these on Linux:
https://forum.manjaro.org/t/unstable-behaviour-not-always-completely-booting/55823/5
Are you on the latest firmware ("BIOS") revision for your board?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
On Tue, 13 Nov 2018 12:59:59 -0500 (EST) Daniel Eischen wrote: > I'm trying to track down a couple of things. amdtemp doesn't > report any temperature sensors, and acpi seems to have some > errors. Not sure if they are related. It s a bit legacy ) Try mine: http://www.netlab.linkpc.net/download/tmp/amdtemp.c does not use amdsmn. On newer BIOS it swap CurTmpTjSel and CurTmp, and CurTmp show >90C. I dont know why, @cem may know. dev.amdtemp.0.htc.PslApicLoEn: 1 dev.amdtemp.0.htc.PslApicHiEn: 1 dev.amdtemp.0.htc.HtcActSts: 1 dev.amdtemp.0.htc.HtcAct: 1 dev.amdtemp.0.htc.HtcPstateLimit: 7 dev.amdtemp.0.htc.HtcSlewSel: 1 dev.amdtemp.0.htc.HtcLock: 1 dev.amdtemp.0.htc.HtcEn: 1 dev.amdtemp.0.htc.HtcHystLmt: 7.6C dev.amdtemp.0.htc.HtcTmpLmt: 115.6C dev.amdtemp.0.tts.core1.sensor1_offset: 0 dev.amdtemp.0.tts.core1.sensor0_offset: 0 dev.amdtemp.0.tts.core1.sensor1: -0.9C dev.amdtemp.0.tts.core1.sensor0: -0.9C dev.amdtemp.0.tts.core0.sensor1_offset: 0 dev.amdtemp.0.tts.core0.sensor0_offset: 0 dev.amdtemp.0.tts.core0.sensor1: -0.9C dev.amdtemp.0.tts.core0.sensor0: -0.9C dev.amdtemp.0.tts.thermtrip: 0 dev.amdtemp.0.tts.sense: 1 dev.amdtemp.0.tts.enable: 0 dev.amdtemp.0.tts.DiodeOffset: 13 dev.amdtemp.0.tts.TjOffset: 0 dev.amdtemp.0.rtc.sensor_offset: 0 dev.amdtemp.0.rtc.PerStepTimeUp: 15 dev.amdtemp.0.rtc.PerStepTimeDn: 15 dev.amdtemp.0.rtc.TmpMaxDiffUp: 3 dev.amdtemp.0.rtc.TmpSlewDnEn: 1 dev.amdtemp.0.rtc.CurTmpTjSel: 1.6C dev.amdtemp.0.rtc.CurTmp: 50.6C dev.amdtemp.0.%parent: hostb10 dev.amdtemp.0.%pnpinfo: dev.amdtemp.0.%location: dev.amdtemp.0.%driver: amdtemp dev.amdtemp.0.%desc: AMD CPU On-Die Thermal Sensors dev.amdtemp.%parent: ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
No amdtemp sysctls, acpi errors, AMD Ryzen 5 2400G
Greetings, I'm trying to track down a couple of things. amdtemp doesn't report any temperature sensors, and acpi seems to have some errors. Not sure if they are related. These are the ACPI-related warnings and errors during boot. Firmware Warning (ACPI): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x/0x1 (20181031/tbfadt-796) acpi0: on motherboard Firmware Error (ACPI): Failure creating [\134_SB.SMIC], AE_ALREADY_EXISTS (20181031/dswload2-477) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181031/psobject-372) Firmware Error (ACPI): Failure creating [\134_SB.SMIB], AE_ALREADY_EXISTS (20181031/dsfield-803) The amdtemp module loads fine (including the dependent amdsmn), but doesn't report any temperature related sysctls. $ sysctl -a | grep temp cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed cd0: Attempt to query device size failed: NOT READY, Medium not present- tray closed net.inet6.ip6.use_tempaddr: 0 net.inet6.ip6.temppltime: 86400 net.inet6.ip6.tempvltime: 604800 net.inet6.ip6.prefer_tempaddr: 0 hw.usb.template: -1 kstat.zfs.misc.arcstats.arc_tempreserve: 0 kstat.zfs.misc.zcompstats.attempts: 135280 Here's the relevent CPU line from dmesg. CPU: AMD Ryzen 5 2400G with Radeon Vega Graphics (3593.34-MHz K8-class CPU) Origin="AuthenticAMD" Id=0x810f10 Family=0x17 Model=0x11 Stepping=0 Features=0x178bfbff Features2=0x7ed8320b AMD Features=0x2e500800 AMD Features2=0x35c233ff Structured Extended Features=0x209c01a9 XSAVE Features=0xf AMD Extended Feature Extensions ID EBX=0x1007 SVM: (disabled in BIOS) NP,NRIP,VClean,AFlush,DAssist,NAsids=32768 TSC: P-state invariant, performance statistics The full dmesg, /usr/sbin/acpidump -dt, and apcica-tools acpudumps (with and without -s) are here: https://people.freebsd.org/~deischen/2400g/dmesg.txt https://people.freebsd.org/~deischen/2400g/acpidump.txt https://people.freebsd.org/~deischen/2400g/acpica.acpidump.txt Thanks -- DE ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection
Am 15.08.2018 um 10:43 schrieb Vladimir Zakharov: Hello! On Tue, Aug 14, 2018, Pete Wright wrote: On 8/14/18 6:13 PM, Kyle Evans wrote: On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: i also attempted to boot using UEFI but the system hangs very early in the boot process. i have reverted to legacy mode for now so that i can work, but am keen to test out any patches or do any other debugging that is needed. Hi Pete, Where in the process does it hang with UEFI? I can't help much with any of your other problems, but I am curious about this one. =) sure thing - the last several lines are: random: fast provider: "Intel Secure Key RNG" kbd1 at kbdmux0 netmap: loaded module nexus0 at this point it hangs. let me know if you want me to try booting with verbose output to dmesg or something. I've updated from r337734 and got the same here with HP Probook 430 G2. Setting efi.rt.disabled=1 in /boot/loader.conf fixed the problem for me. # uname -a FreeBSD vzakharov 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 #24 r337829: Wed Aug 15 06:33:54 MSK 2018 root@vzakharov:/home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 I can confirm efi.rt.disabled=1 in /boot/loader.conf fixes my problem too, which I posted in reply to Kyle's r337773 hint (non-bootable (UEFI, geli, ZFS) kernel on haswell [Was: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection]) Machine here is DH87MC+i3-4330 (LynxPoint/Series8+haswell) -harry ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
non-bootable (UEFI, geli, ZFS) kernel on haswell [Was: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection]
Am 15.08.2018 um 06:01 schrieb Kyle Evans: On Tue, Aug 14, 2018 at 10:56 PM, Pete Wright wrote: On 8/14/18 8:45 PM, Kyle Evans wrote: On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright wrote: On 8/14/18 6:13 PM, Kyle Evans wrote: On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: i also attempted to boot using UEFI but the system hangs very early in the boot process. i have reverted to legacy mode for now so that i can work, but am keen to test out any patches or do any other debugging that is needed. Hi Pete, Where in the process does it hang with UEFI? I can't help much with any of your other problems, but I am curious about this one. =) sure thing - the last several lines are: random: fast provider: "Intel Secure Key RNG" kbd1 at kbdmux0 netmap: loaded module nexus0 at this point it hangs. let me know if you want me to try booting with verbose output to dmesg or something. Are you running GENERIC, or custom config? Any modules loaded? this is a GENERIC kernel using ZFS as well as GELI full disk encryption. Good to know, thanks! Hello, me too here, kind of... Machine resets after nexus0 – took my SLR with 1s exposure time to make sure there's no more GOP output available :-( Haven't tried efi.rt.disabled=1 yet, since I had to spend some time to get the old kernel in place. non-booting kernel inquestion is custom r337804. Like Pete, I'm booting from a ZFS pool utilizing GOP, load_geli, zfs, aesni, nut my machine dosen't hang after "nexus0" but hard resets. The modules loaded don't influence the problem, even with only "kernel" (which is MINIMAL_config + very view devices/filesystems added) loaded, the machine resets after "nexus0". Will try efi.rt.disabled=1 tomorrow. Anyone intending to update a haswell/UEFI machine (Intel DH87MC in my case, with INVPCID microcode updated BIOS) could run into simialr situation I guess, so please make sure to be prepared... My first suspicion were side effects of r337715. But this is just a wild guess, haven't bisected anything yet. Thanks, -harry ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection
On Tue, 14 Aug 2018 20:41:03 -0700 Pete Wright wrote: > On 8/14/18 6:13 PM, Kyle Evans wrote: > > On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: > >> i also attempted to boot using UEFI but the system hangs very early in the > >> boot process. i have reverted to legacy mode for now so that i can work, > >> but am keen to test out any patches or do any other debugging that is > >> needed. > > Hi Pete, > > > > Where in the process does it hang with UEFI? I can't help much with > > any of your other problems, but I am curious about this one. =) > sure thing - the last several lines are: > > random: fast provider: "Intel Secure Key RNG" > kbd1 at kbdmux0 > netmap: loaded module > nexus0 Similar situation same here on a Lenovo ThinkPad E540, except that the netmpa message occurs prior to "random: fast provider: "Intel Secure Key RNG" > > at this point it hangs. let me know if you want me to try booting with > verbose output to dmesg or something. > > > cheers, > -pete > > Other UEFI booting systems (oldish Asrock Z77-Pro4/Pro4-M) throw some infos shortly after booting the kernel which look like the stuff I can see from the UEFI loader very early - but it is to fast to catch with the naked eye. The boxes reboot and spinning booting this way. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection
Hello! On Tue, Aug 14, 2018, Pete Wright wrote: > > On 8/14/18 6:13 PM, Kyle Evans wrote: > > On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: > > > i also attempted to boot using UEFI but the system hangs very early in the > > > boot process. i have reverted to legacy mode for now so that i can work, > > > but am keen to test out any patches or do any other debugging that is > > > needed. > > Hi Pete, > > > > Where in the process does it hang with UEFI? I can't help much with > > any of your other problems, but I am curious about this one. =) > sure thing - the last several lines are: > > random: fast provider: "Intel Secure Key RNG" > kbd1 at kbdmux0 > netmap: loaded module > nexus0 > > at this point it hangs. let me know if you want me to try booting with > verbose output to dmesg or something. I've updated from r337734 and got the same here with HP Probook 430 G2. Setting efi.rt.disabled=1 in /boot/loader.conf fixed the problem for me. # uname -a FreeBSD vzakharov 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 #24 r337829: Wed Aug 15 06:33:54 MSK 2018 root@vzakharov:/home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 -- Regards, | "In theory there is no difference between theory Vladimir Zakharov | and practice. In practice there is."- Yogi Berra ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection
On Tue, 14 Aug 2018 20:41:03 -0700 Pete Wright wrote: > On 8/14/18 6:13 PM, Kyle Evans wrote: > > On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: > >> i also attempted to boot using UEFI but the system hangs very early in the > >> boot process. i have reverted to legacy mode for now so that i can work, > >> but am keen to test out any patches or do any other debugging that is > >> needed. > > Hi Pete, > > > > Where in the process does it hang with UEFI? I can't help much with > > any of your other problems, but I am curious about this one. =) > sure thing - the last several lines are: > > random: fast provider: "Intel Secure Key RNG" > kbd1 at kbdmux0 > netmap: loaded module > nexus0 Similar situation same here on a Lenovo ThinkPad E540, except that the netmpa message occurs prior to "random: fast provider: "Intel Secure Key RNG" > > at this point it hangs. let me know if you want me to try booting with > verbose output to dmesg or something. > > > cheers, > -pete > > Other UEFI booting systems (oldish Asrock Z77-Pro4/Pro4-M) throw some infos shortly after booting the kernel which look like the stuff I can see from the UEFI loader very early - but it is to fast to catch with the naked eye. The boxes reboot and spinning booting this way. Addon: this is with CURRENT r337832 Last known working version for me is: r337718 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection
On 8/14/18 9:06 PM, Pete Wright wrote: On 8/14/18 9:01 PM, Kyle Evans wrote: I'm curious if you've been bitten somehow by recently enabling EFIRT in GENERIC. Can you try setting efi.rt.disabled=1 at loader prompt and see where that gets you? i did attempt to set that in loader.conf - and it progressed farther but kernel panic'd when trying to bring up my iwn wireless interface. Interesting... out of side curiosity, what does this panic look like? Can you also try running a kernel >= r337773 with kib's patch from [1] applied to make sure this the EFI part of this isn't already solved? sure i can give that a spin. i'm building an older version in an attempt to bisect this issue (i have a skylake system running a checkout from monday without issues, so testing that now). if i am still running into problems i'll boot with efi.rt.disabled=1 and will post the gdb panic string here. Excellent. so i have reverted back to this git hash: 90f37b39e4a https://github.com/freebsd/freebsd/commit/90f37b39e4ad481d3e5a059123f7d68ac153f0c5 and i can confirm that i am able to boot with EFI enabled, do not experience any issues bringing up my iwn interface and HDMI is recognized according to xrandr. so that solves my immediate problem! :) interestingly enough i still see the ACPI errors I reported earlier, but perhaps that is a red herring. i'll go back to the tip of master and apply kib's patch and see how it goes. ok great (thank's ccache for making buildkernel fast :) ) so after applying the patch from kib i have the same behavior as i'm seeing on git hash 90f37b39e4a. i.e. boots fine with UEFI enabled, iwn interface comes up, HDMI output is detected by xrandr and interesting ACPI warning messages. i'll dogfood this patch tomorrow when i get into the office and validate connecting my HDMI display works as expected and will report any other issues i bump into. thanks for your help Kyle! I didn't think to test kib's patch as i was assuming my issue was related to the ACPI errors, but this seems to get me back to where i need to be to work tomorrow so i'm good to go :) -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection
On 8/14/18 9:01 PM, Kyle Evans wrote: I'm curious if you've been bitten somehow by recently enabling EFIRT in GENERIC. Can you try setting efi.rt.disabled=1 at loader prompt and see where that gets you? i did attempt to set that in loader.conf - and it progressed farther but kernel panic'd when trying to bring up my iwn wireless interface. Interesting... out of side curiosity, what does this panic look like? Can you also try running a kernel >= r337773 with kib's patch from [1] applied to make sure this the EFI part of this isn't already solved? sure i can give that a spin. i'm building an older version in an attempt to bisect this issue (i have a skylake system running a checkout from monday without issues, so testing that now). if i am still running into problems i'll boot with efi.rt.disabled=1 and will post the gdb panic string here. Excellent. so i have reverted back to this git hash: 90f37b39e4a https://github.com/freebsd/freebsd/commit/90f37b39e4ad481d3e5a059123f7d68ac153f0c5 and i can confirm that i am able to boot with EFI enabled, do not experience any issues bringing up my iwn interface and HDMI is recognized according to xrandr. so that solves my immediate problem! :) interestingly enough i still see the ACPI errors I reported earlier, but perhaps that is a red herring. i'll go back to the tip of master and apply kib's patch and see how it goes. -p -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection
On Tue, Aug 14, 2018 at 10:56 PM, Pete Wright wrote: > > On 8/14/18 8:45 PM, Kyle Evans wrote: >> >> On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright wrote: >>> >>> On 8/14/18 6:13 PM, Kyle Evans wrote: On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: > > i also attempted to boot using UEFI but the system hangs very early in > the > boot process. i have reverted to legacy mode for now so that i can > work, > but am keen to test out any patches or do any other debugging that is > needed. Hi Pete, Where in the process does it hang with UEFI? I can't help much with any of your other problems, but I am curious about this one. =) >>> >>> sure thing - the last several lines are: >>> >>> random: fast provider: "Intel Secure Key RNG" >>> kbd1 at kbdmux0 >>> netmap: loaded module >>> nexus0 >>> >>> at this point it hangs. let me know if you want me to try booting with >>> verbose output to dmesg or something. >>> >> Are you running GENERIC, or custom config? Any modules loaded? > > > > this is a GENERIC kernel using ZFS as well as GELI full disk encryption. > Good to know, thanks! > >> >> I'm curious if you've been bitten somehow by recently enabling EFIRT >> in GENERIC. Can you try setting efi.rt.disabled=1 at loader prompt and >> see where that gets you? > > > i did attempt to set that in loader.conf - and it progressed farther but > kernel panic'd when trying to bring up my iwn wireless interface. > Interesting... out of side curiosity, what does this panic look like? Can you also try running a kernel >= r337773 with kib's patch from [1] applied to make sure this the EFI part of this isn't already solved? > > i'm building an older version in an attempt to bisect this issue (i have a > skylake system running a checkout from monday without issues, so testing > that now). if i am still running into problems i'll boot with > efi.rt.disabled=1 and will post the gdb panic string here. > Excellent. > -pete > Thanks, Kyle Evans [1] https://lists.freebsd.org/pipermail/freebsd-current/2018-August/070660.html ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection
On 8/14/18 8:45 PM, Kyle Evans wrote: On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright wrote: On 8/14/18 6:13 PM, Kyle Evans wrote: On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: i also attempted to boot using UEFI but the system hangs very early in the boot process. i have reverted to legacy mode for now so that i can work, but am keen to test out any patches or do any other debugging that is needed. Hi Pete, Where in the process does it hang with UEFI? I can't help much with any of your other problems, but I am curious about this one. =) sure thing - the last several lines are: random: fast provider: "Intel Secure Key RNG" kbd1 at kbdmux0 netmap: loaded module nexus0 at this point it hangs. let me know if you want me to try booting with verbose output to dmesg or something. Are you running GENERIC, or custom config? Any modules loaded? this is a GENERIC kernel using ZFS as well as GELI full disk encryption. I'm curious if you've been bitten somehow by recently enabling EFIRT in GENERIC. Can you try setting efi.rt.disabled=1 at loader prompt and see where that gets you? i did attempt to set that in loader.conf - and it progressed farther but kernel panic'd when trying to bring up my iwn wireless interface. i'm building an older version in an attempt to bisect this issue (i have a skylake system running a checkout from monday without issues, so testing that now). if i am still running into problems i'll boot with efi.rt.disabled=1 and will post the gdb panic string here. -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection
On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright wrote: > > On 8/14/18 6:13 PM, Kyle Evans wrote: >> >> On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: >>> >>> i also attempted to boot using UEFI but the system hangs very early in >>> the >>> boot process. i have reverted to legacy mode for now so that i can work, >>> but am keen to test out any patches or do any other debugging that is >>> needed. >> >> Hi Pete, >> >> Where in the process does it hang with UEFI? I can't help much with >> any of your other problems, but I am curious about this one. =) > > sure thing - the last several lines are: > > random: fast provider: "Intel Secure Key RNG" > kbd1 at kbdmux0 > netmap: loaded module > nexus0 > > at this point it hangs. let me know if you want me to try booting with > verbose output to dmesg or something. > Are you running GENERIC, or custom config? Any modules loaded? I'm curious if you've been bitten somehow by recently enabling EFIRT in GENERIC. Can you try setting efi.rt.disabled=1 at loader prompt and see where that gets you? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection
On 8/14/18 6:13 PM, Kyle Evans wrote: On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: i also attempted to boot using UEFI but the system hangs very early in the boot process. i have reverted to legacy mode for now so that i can work, but am keen to test out any patches or do any other debugging that is needed. Hi Pete, Where in the process does it hang with UEFI? I can't help much with any of your other problems, but I am curious about this one. =) sure thing - the last several lines are: random: fast provider: "Intel Secure Key RNG" kbd1 at kbdmux0 netmap: loaded module nexus0 at this point it hangs. let me know if you want me to try booting with verbose output to dmesg or something. cheers, -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection
On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: > i also attempted to boot using UEFI but the system hangs very early in the > boot process. i have reverted to legacy mode for now so that i can work, > but am keen to test out any patches or do any other debugging that is > needed. Hi Pete, Where in the process does it hang with UEFI? I can't help much with any of your other problems, but I am curious about this one. =) Thanks, Kyle Evans ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
CURRENT from today throws lots of ACPI errors, lost HDMI detection
howdy, running code from today and having lots of issues. when i boot the system (a kabylake laptop) using legacy mode in the BIOS i see lots of these errors are thrown in dmesg: acpi0: on motherboard Firmware Error (ACPI): Failure creating [\134_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20180810/dswload2-468) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-372) ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-689) Firmware Error (ACPI): Failure creating [\134_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20180810/dswload2-468) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-372) ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-689) Firmware Error (ACPI): Failure creating [\134_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20180810/dswload2-468) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-372) ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-689) Firmware Error (ACPI): Failure creating [\134_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20180810/dswload2-468) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-372) ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-689) Firmware Error (ACPI): Failure creating [\134_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20180810/dswload2-468) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-372) ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-689) there are lots more, i can post a pastebin link if needed. i also attempted to boot using UEFI but the system hangs very early in the boot process. i have reverted to legacy mode for now so that i can work, but am keen to test out any patches or do any other debugging that is needed. thx! -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New ACPI Errors
On 02/13/2018 17:34, Claude Buisson wrote: > On 02/13/2018 22:49, Pete Wright wrote: >> Hello, >> I have started seeing a lot of these messages spam my system log: >> >> ACPI Error: No pointer back to namespace node in package >> 0xf8000f79a080 (20180209/dsargs-472) >> ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, >> AE_AML_INTERNAL (20180209/psparse-677) >> ACPI Error: Method parse/execution failed \134_SB.AC._PSR, >> AE_AML_INTERNAL (20180209/psparse-677) >> >> I noticed this starting from a CURRENT build i installed two weeks >> ago, and still see it from a world/kernel i built last night. two >> questions: >> 1) has anyone else noticed this? >> 2) is this something to worry about? >> >> i can help debug the issue but am not sure where to start poking. >> >> thanks! >> -pete >> > Here I have > > ACPI Error: No pointer back to namespace node in package > 0xf8000171f700 (20180209/dsargs-472) > ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName > unavailable] (20180209/dswexec-606) > ACPI Error: Method parse/execution failed > \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677) > > with svn 329142 on a Lenovo ThinkCentre M83 > ACPI APIC Table: > > Claude Buisson This problem should be fixed now (r80). Sorry for the delay. Jung-uk Kim signature.asc Description: OpenPGP digital signature
Re: New ACPI Errors
On 02/16/2018 13:54, Pete Wright wrote: On 02/15/2018 13:37, Jung-uk Kim wrote: On 02/13/2018 17:34, Claude Buisson wrote: On 02/13/2018 22:49, Pete Wright wrote: Hello, I have started seeing a lot of these messages spam my system log: ACPI Error: No pointer back to namespace node in package 0xf8000f79a080 (20180209/dsargs-472) ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) ACPI Error: Method parse/execution failed \134_SB.AC._PSR, AE_AML_INTERNAL (20180209/psparse-677) I noticed this starting from a CURRENT build i installed two weeks ago, and still see it from a world/kernel i built last night. two questions: 1) has anyone else noticed this? 2) is this something to worry about? i can help debug the issue but am not sure where to start poking. thanks! -pete Here I have ACPI Error: No pointer back to namespace node in package 0xf8000171f700 (20180209/dsargs-472) ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] (20180209/dswexec-606) ACPI Error: Method parse/execution failed \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677) with svn 329142 on a Lenovo ThinkCentre M83 ACPI APIC Table: Claude Buisson I believe you can silence the errors with the attached patch. Please try it and let me know. hrm still getting errors: Feb 16 13:49:45 runner kernel: ACPI Error: No pointer back to namespace node in package 0xf80003c8c080 (20180209/dsargs-472) Feb 16 13:49:45 runner kernel: ACPI Error: Method parse/execution failed \_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) Feb 16 13:49:45 runner kernel: ACPI Error: Method parse/execution failed \_SB.AC._PSR, AE_AML_INTERNAL (20180209/psparse-677) here's my diff: diff --git a/sys/contrib/dev/acpica/include/platform/acfreebsd.h b/sys/contrib/dev/acpica/include/platform/acfreebsd.h index 905dffb7a40..df89399a369 100644 --- a/sys/contrib/dev/acpica/include/platform/acfreebsd.h +++ b/sys/contrib/dev/acpica/include/platform/acfreebsd.h @@ -166,6 +166,7 @@ #define ACPI_UINTPTR_T uintptr_t +#define ACPI_IGNORE_PACKAGE_RESOLUTION_ERRORS #define ACPI_USE_DO_WHILE_0 #define ACPI_USE_LOCAL_CACHE #define ACPI_USE_NATIVE_DIVIDE hi there - i was wondering if anyone has taken a look at this issue. I am still seeing these ACPI errors on recent CURRENT systems: ACPI Error: No pointer back to namespace node in package 0xf803e71fff00 (20180313/dsargs-472) ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, AE_AML_INTERNAL (20180313/psparse-677) ACPI Error: Method parse/execution failed \134_SB.AC._PSR, AE_AML_INTERNAL (20180313/psparse-677) I have two amd64 (skylake and kabylake) systems that are exhibiting this behavior and am more than happy to test patches or other things. cheers! -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New ACPI Errors
On 02/15/2018 13:37, Jung-uk Kim wrote: On 02/13/2018 17:34, Claude Buisson wrote: On 02/13/2018 22:49, Pete Wright wrote: Hello, I have started seeing a lot of these messages spam my system log: ACPI Error: No pointer back to namespace node in package 0xf8000f79a080 (20180209/dsargs-472) ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) ACPI Error: Method parse/execution failed \134_SB.AC._PSR, AE_AML_INTERNAL (20180209/psparse-677) I noticed this starting from a CURRENT build i installed two weeks ago, and still see it from a world/kernel i built last night. two questions: 1) has anyone else noticed this? 2) is this something to worry about? i can help debug the issue but am not sure where to start poking. thanks! -pete Here I have ACPI Error: No pointer back to namespace node in package 0xf8000171f700 (20180209/dsargs-472) ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] (20180209/dswexec-606) ACPI Error: Method parse/execution failed \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677) with svn 329142 on a Lenovo ThinkCentre M83 ACPI APIC Table: Claude Buisson I believe you can silence the errors with the attached patch. Please try it and let me know. hrm still getting errors: Feb 16 13:49:45 runner kernel: ACPI Error: No pointer back to namespace node in package 0xf80003c8c080 (20180209/dsargs-472) Feb 16 13:49:45 runner kernel: ACPI Error: Method parse/execution failed \_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) Feb 16 13:49:45 runner kernel: ACPI Error: Method parse/execution failed \_SB.AC._PSR, AE_AML_INTERNAL (20180209/psparse-677) here's my diff: diff --git a/sys/contrib/dev/acpica/include/platform/acfreebsd.h b/sys/contrib/dev/acpica/include/platform/acfreebsd.h index 905dffb7a40..df89399a369 100644 --- a/sys/contrib/dev/acpica/include/platform/acfreebsd.h +++ b/sys/contrib/dev/acpica/include/platform/acfreebsd.h @@ -166,6 +166,7 @@ #define ACPI_UINTPTR_T uintptr_t +#define ACPI_IGNORE_PACKAGE_RESOLUTION_ERRORS #define ACPI_USE_DO_WHILE_0 #define ACPI_USE_LOCAL_CACHE #define ACPI_USE_NATIVE_DIVIDE -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New ACPI Errors
On 02/13/2018 17:34, Claude Buisson wrote: > On 02/13/2018 22:49, Pete Wright wrote: >> Hello, >> I have started seeing a lot of these messages spam my system log: >> >> ACPI Error: No pointer back to namespace node in package >> 0xf8000f79a080 (20180209/dsargs-472) >> ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, >> AE_AML_INTERNAL (20180209/psparse-677) >> ACPI Error: Method parse/execution failed \134_SB.AC._PSR, >> AE_AML_INTERNAL (20180209/psparse-677) >> >> I noticed this starting from a CURRENT build i installed two weeks >> ago, and still see it from a world/kernel i built last night. two >> questions: >> 1) has anyone else noticed this? >> 2) is this something to worry about? >> >> i can help debug the issue but am not sure where to start poking. >> >> thanks! >> -pete >> > Here I have > > ACPI Error: No pointer back to namespace node in package > 0xf8000171f700 (20180209/dsargs-472) > ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName > unavailable] (20180209/dswexec-606) > ACPI Error: Method parse/execution failed > \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677) > > with svn 329142 on a Lenovo ThinkCentre M83 > ACPI APIC Table: > > Claude Buisson I believe you can silence the errors with the attached patch. Please try it and let me know. Jung-uk Kim Index: sys/contrib/dev/acpica/include/platform/acfreebsd.h === --- sys/contrib/dev/acpica/include/platform/acfreebsd.h (revision 329340) +++ sys/contrib/dev/acpica/include/platform/acfreebsd.h (working copy) @@ -166,6 +166,7 @@ #define ACPI_UINTPTR_T uintptr_t +#define ACPI_IGNORE_PACKAGE_RESOLUTION_ERRORS #define ACPI_USE_DO_WHILE_0 #define ACPI_USE_LOCAL_CACHE #define ACPI_USE_NATIVE_DIVIDE signature.asc Description: OpenPGP digital signature
Re: New ACPI Errors
On 02/13/2018 22:49, Pete Wright wrote: Hello, I have started seeing a lot of these messages spam my system log: ACPI Error: No pointer back to namespace node in package 0xf8000f79a080 (20180209/dsargs-472) ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) ACPI Error: Method parse/execution failed \134_SB.AC._PSR, AE_AML_INTERNAL (20180209/psparse-677) I noticed this starting from a CURRENT build i installed two weeks ago, and still see it from a world/kernel i built last night. two questions: 1) has anyone else noticed this? 2) is this something to worry about? i can help debug the issue but am not sure where to start poking. thanks! -pete Here I have ACPI Error: No pointer back to namespace node in package 0xf8000171f700 (20180209/dsargs-472) ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] (20180209/dswexec-606) ACPI Error: Method parse/execution failed \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677) with svn 329142 on a Lenovo ThinkCentre M83 ACPI APIC Table: Claude Buisson ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
New ACPI Errors
Hello, I have started seeing a lot of these messages spam my system log: ACPI Error: No pointer back to namespace node in package 0xf8000f79a080 (20180209/dsargs-472) ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, AE_AML_INTERNAL (20180209/psparse-677) ACPI Error: Method parse/execution failed \134_SB.AC._PSR, AE_AML_INTERNAL (20180209/psparse-677) I noticed this starting from a CURRENT build i installed two weeks ago, and still see it from a world/kernel i built last night. two questions: 1) has anyone else noticed this? 2) is this something to worry about? i can help debug the issue but am not sure where to start poking. thanks! -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ACPI errors when booting laptop
Have you checked for BIOS updates? The BIOS on recent Skylake laptops have been a running disaster. At least the Dell XPS laptops had ACPI errors be fixed by an update. -M On Sat, Jul 30, 2016 at 10:43 PM, Ben Woods wrote: > Hi everyone, > > I get the following ACPI errors in my dmesg when booting my NEC Lavie HZ750 > laptop with FreeBSD 12-current. I have noticed things not functioning > correct (except suspend/resume not working), but then again I don't really > know much about ACPI or what I should expect to see. Any ideas what the > problem is? > > Full dmesg is also attached. > > acpi0: on motherboard > acpi_ec_ecdt_probe: can't get handle > ACPI Error: No handler for Region [EC__] (0xf8000548fc80) > [EmbeddedControl] (20160527/evregion-180) > ACPI Error: Region EmbeddedControl (ID=3) has no handler > (20160527/exfldio-320) > ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC._REG] (Node > 0xf80005494980), AE_NOT_EXIST (20160527/psparse-559) > acpi0: Power Button (fixed) > ACPI Error: No handler for Region [EC__] (0xf8000548fc80) > [EmbeddedControl] (20160527/evregion-180) > ACPI Error: Region EmbeddedControl (ID=3) has no handler > (20160527/exfldio-320) > ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] > (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) > ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node > 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) > ACPI Error: No handler for Region [EC__] (0xf8000548fc80) > [EmbeddedControl] (20160527/evregion-180) > ACPI Error: Region EmbeddedControl (ID=3) has no handler > (20160527/exfldio-320) > ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] > (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) > ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node > 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) > ACPI Error: No handler for Region [EC__] (0xf8000548fc80) > [EmbeddedControl] (20160527/evregion-180) > ACPI Error: Region EmbeddedControl (ID=3) has no handler > (20160527/exfldio-320) > ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] > (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) > ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node > 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) > ACPI Error: No handler for Region [EC__] (0xf8000548fc80) > [EmbeddedControl] (20160527/evregion-180) > ACPI Error: Region EmbeddedControl (ID=3) has no handler > (20160527/exfldio-320) > ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] > (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) > ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node > 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) > ACPI Error: No handler for Region [EC__] (0xf8000548fc80) > [EmbeddedControl] (20160527/evregion-180) > ACPI Error: Region EmbeddedControl (ID=3) has no handler > (20160527/exfldio-320) > ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] > (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) > ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node > 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) > ACPI Error: No handler for Region [EC__] (0xf8000548fc80) > [EmbeddedControl] (20160527/evregion-180) > ACPI Error: Region EmbeddedControl (ID=3) has no handler > (20160527/exfldio-320) > ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] > (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) > ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node > 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) > ACPI Error: No handler for Region [EC__] (0xf8000548fc80) > [EmbeddedControl] (20160527/evregion-180) > ACPI Error: Region EmbeddedControl (ID=3) has no handler > (20160527/exfldio-320) > ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] > (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) > ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node > 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) > ACPI Error: No handler for Region [EC__] (0xf8000548fc80) > [EmbeddedControl] (20160527/evregion-180) > ACPI Error: Region EmbeddedControl (ID=3) has no handler > (20160527/exfldio-320) > ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] > (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) > ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node > 0xf8000549a640), AE_N
ACPI errors when booting laptop
Hi everyone, I get the following ACPI errors in my dmesg when booting my NEC Lavie HZ750 laptop with FreeBSD 12-current. I have noticed things not functioning correct (except suspend/resume not working), but then again I don't really know much about ACPI or what I should expect to see. Any ideas what the problem is? Full dmesg is also attached. acpi0: on motherboard acpi_ec_ecdt_probe: can't get handle ACPI Error: No handler for Region [EC__] (0xf8000548fc80) [EmbeddedControl] (20160527/evregion-180) ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160527/exfldio-320) ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC._REG] (Node 0xf80005494980), AE_NOT_EXIST (20160527/psparse-559) acpi0: Power Button (fixed) ACPI Error: No handler for Region [EC__] (0xf8000548fc80) [EmbeddedControl] (20160527/evregion-180) ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160527/exfldio-320) ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) ACPI Error: No handler for Region [EC__] (0xf8000548fc80) [EmbeddedControl] (20160527/evregion-180) ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160527/exfldio-320) ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) ACPI Error: No handler for Region [EC__] (0xf8000548fc80) [EmbeddedControl] (20160527/evregion-180) ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160527/exfldio-320) ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) ACPI Error: No handler for Region [EC__] (0xf8000548fc80) [EmbeddedControl] (20160527/evregion-180) ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160527/exfldio-320) ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) ACPI Error: No handler for Region [EC__] (0xf8000548fc80) [EmbeddedControl] (20160527/evregion-180) ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160527/exfldio-320) ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) ACPI Error: No handler for Region [EC__] (0xf8000548fc80) [EmbeddedControl] (20160527/evregion-180) ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160527/exfldio-320) ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) ACPI Error: No handler for Region [EC__] (0xf8000548fc80) [EmbeddedControl] (20160527/evregion-180) ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160527/exfldio-320) ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) ACPI Error: No handler for Region [EC__] (0xf8000548fc80) [EmbeddedControl] (20160527/evregion-180) ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160527/exfldio-320) ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) ACPI Error: No handler for Region [EC__] (0xf8000548fc80) [EmbeddedControl] (20160527/evregion-180) ACPI Error: Region EmbeddedControl (ID=3) has no handler (20160527/exfldio-320) ACPI Error: Method parse/execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/psparse-559) ACPI Error: Method execution failed [\134_SB.PCI0.LPCB.EC.BAT1._STA] (Node 0xf8000549a640), AE_NOT_EXIST (20160527/uteval-111) ACPI Error: No handler for Region [EC__] (0xf8000548fc80) [EmbeddedControl] (20160527/evregion-180) ACPI Error: Region EmbeddedControl (ID=3) has
Re: new MB = ACPI Errors?
* Steve Ames <[EMAIL PROTECTED]> [030908 20:26]: > > Hey. I installed a new motherboard today and now I get a lot of ACPI > errors (with a kernel from today and one from a few days back). This > anything to worry about? Not really, just annoying. A fair number (all that I've seen!) of motherboard ship with ACPI tables that are buggy. Namely, they are bug-for-bug compatible with Microsoft's much more lenient ACPI interpreter. The stricter one built into FreeBSD chokes on a lot of things. The short answer is, unless you have hardware that's actually not functioning properly, you can usually ignore those messages. You can also just turn off ACPI and they'll go away. (But you're likely to replace them with a bunch of "PNP0501 Could not assign resources" type messages, it's a toss-up.) If you are so inclined, it's often very easy to fix these things. Install the devel/acpicatools port, then use the ASL compiler and decompiler like so: acpidump -o foo.dsdt -d > foo.asl iasl foo.asl You will likely get a lot of errors at that point. Not knowing anything about ACPI I was able to figure out the really easy ones in a few hours. In particular, watch for things like this: foo.asl 1577: Method (_STA, 0, NotSerialized) Warning 2019 - ^ Not all control paths return a value (_STA) These are harmless but easy to fix. Stick Return(0) inside the blocks that are missing them. The line numbers should give you a good idea. foo.asl 857: Field (PSRG, DWordAcc, NoLock, Preserve) Error1047 - ^ Access width is greater than region size These are a bit tricker. It means a field was defined inside of an ACPI region that is bigger than the region itself. The offending lines are: OperationRegion (PSRG, SystemMemory, 0x0410, 0x01) Field (PSRG, DWordAcc, NoLock, Preserve) The 0x01 at the end of the first line means this region is 1 byte big; the DWordAcc in the second line means there's a field that's 4 bytes big in that region. Not good :) In my case simply making the region bigger: OperationRegion (PSRG, SystemMemory, 0x0410, 0x04) Field (PSRG, DWordAcc, NoLock, Preserve) Solved the compile problems. Any more complex ACPI problems you can probably post here and get some assistance from the numerous people who fixed their own ACPI tables. There's also numerous examples on the web of fixed ASL code that may solve similar problems to your own -- hit google and look for the error messages. After that, just copy the .aml file that iasl outputs into /boot and put this in loader.conf: acpi_dsdt_load="YES"# DSDT Overriding acpi_dsdt_type="acpi_dsdt" # Don't change this acpi_dsdt_name="/boot/foo.aml" --Mike pgp0.pgp Description: PGP signature
new MB = ACPI Errors?
Hey. I installed a new motherboard today and now I get a lot of ACPI errors (with a kernel from today and one from a few days back). This anything to worry about? -Steve Preloaded elf module "/boot/kernel/acpi.ko" at 0xc046a248. acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 acpi_cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKM._SRS] (Node 0xc3c145a0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKM._SRS] (Node 0xc3c145a0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKM._SRS] (Node 0xc3c145a0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKM._SRS] (Node 0xc3c145a0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKM._SRS] (Node 0xc3c145a0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKM._SRS] (Node 0xc3c145a0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKM._SRS] (Node 0xc3c145a0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKM._SRS] (Node 0xc3c145a0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKM._SRS] (Node 0xc3c145a0), AE_AML_BUFFER_LIMIT pci0: on pcib0 pcib1: at device 8.0 on pci0 ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKB._SRS] (Node 0xc3c14ea0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKB._SRS] (Node 0xc3c14ea0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKB._SRS] (Node 0xc3c14ea0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKB._SRS] (Node 0xc3c14ea0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKB._SRS] (Node 0xc3c14ea0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKB._SRS] (Node 0xc3c14ea0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKB._SRS] (Node 0xc3c14ea0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKB._SRS] (Node 0xc3c14ea0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKB._SRS] (Node 0xc3c14ea0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKM._SRS] (Node 0xc3c145a0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.LNKM._SRS] (Node 0xc3c145a0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Error: Method execution failed [\\_SB_.SRS_] (Node 0xc14210c0), AE_AML_BUFFER_LIMIT ACPI-1287: *** Erro
Re: ACPI errors on my desktop PC (floppy not found)
It would help if you would tell me when you last had a working kernel. The output of acpidump -t -d -o martin.dsdt > martin.asl would also help. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI errors on my desktop PC (floppy not found)
Martin wrote: Hi, I have more problems to report with the ACPI support and will submit a PR, if you want. I don't know when this got broken. Here some pieces of my dmesg: --- FreeBSD 5.1-CURRENT #0: Thu Sep 4 22:38:56 CEST 2003 [...] acpi0: on motherboard Take a look at PR kern/48494, there is a patch for the AML there for the ABIT BP6 board. I belive other ABIT boards have the similar Store(Local0, Local0) problem. That fixed the floppy problem for me. - Pawel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI errors on my desktop PC (floppy not found)
Am Do, 2003-09-04 um 23.56 schrieb David O'Brien: > Athlon-based? No. CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff It's an old Abit mainboard, but everything always worked here. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI errors on my desktop PC (floppy not found)
On Thu, Sep 04, 2003 at 11:30:49PM +0200, Martin wrote: > I have more problems to report with the ACPI support and will submit a > PR, if you want. I don't know when this got broken. ... > As you can see I recompiled today to confirm that the problem > still exists. This is only about floppy. Everything else is ok. Athlon-based? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ACPI errors on my desktop PC (floppy not found)
Hi, I have more problems to report with the ACPI support and will submit a PR, if you want. I don't know when this got broken. Here some pieces of my dmesg: --- FreeBSD 5.1-CURRENT #0: Thu Sep 4 22:38:56 CEST 2003 [...] acpi0: on motherboard pcibios: BIOS version 2.10 Using $PIR table, 8 entries at 0xc00fdef0 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.ISA_.FDC0._CRS] (Node 0xc29ca6e0), AE_AML_UNINITIALIZED_LOCAL ACPI-0175: *** Error: Method execution failed [\\_SB_.PCI0.ISA_.FDC0._CRS] (Node 0xc29ca6e0), AE_AML_UNINITIALIZED_LOCAL can't fetch resources for \\_SB_.PCI0.ISA_.FDC0 - AE_AML_UNINITIALIZED_LOCAL [...] fdc0: cannot reserve I/O port range (1 ports) orm0: at iomem 0xd1000-0xd27ff,0xc-0xcefff on isa0 fdc0: cannot reserve I/O port range (6 ports) --- As you can see I recompiled today to confirm that the problem still exists. This is only about floppy. Everything else is ok. Martin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI errors on boot
On Wed, Jun 18, 2003 at 09:11:23AM +0200, Maikel Verheijen wrote: > I have recently installed FreeBSD 5.1 on my Dell C800 laptop, and I get > quite a lot (well: 48 :) of these errors on boot: > > ACPI-0293: *** Warning: Buffer created with zero length in AML > -0166: *** Error: UtAllocate: Attempt to allocate zero bytes > > Are those harmfull? Is there something I can do with it? Otherwise my laptop > is working perfectly... :) ^ I have serious doubts on that. I'm pretty sure your battery status won't be showed correctly. Fix is in the archives of this and/or acpi-jp@ list. Mark -- Mark SantcroosRIPE Network Coordination Centre http://www.ripe.net/home/mark/New Projects Group/TTM ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ACPI errors on boot
Hi list! I have recently installed FreeBSD 5.1 on my Dell C800 laptop, and I get quite a lot (well: 48 :) of these errors on boot: ACPI-0293: *** Warning: Buffer created with zero length in AML -0166: *** Error: UtAllocate: Attempt to allocate zero bytes Are those harmfull? Is there something I can do with it? Otherwise my laptop is working perfectly... :) Thank you, Maikel Verheijen. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI errors and panic
>It seems like the fix right now is to disable it. >Put this line: >hint.acpi.0.disabled="1" >in /boot/device.hints Thankyou, this has given me a nice clean bootup now and I can reboot without it panicing. I'm still curious to learn what all that stuff ment though! --- Matt ([EMAIL PROTECTED]) http://www.xtaz.co.uk/ --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI errors and panic
At 06:04 PM 3/16/2003, Matt wrote: Hi, I have just recently installed -CURRENT on my desktop as I've been using it succesfully on a server for months now. However this desktop has much more advanced hardware. Whilst it does work perfectly and I have device support for everything I get a lot of ACPI errors on bootup and also a panic when I try to reboot it, though luckily after it's synced the disks. I have saved the dmesg output to http://tao.xtaz.co.uk/dmesg.txt I was wondering if somebody could tell me what all those errors (and the random gibberish at the top) is about. I also assume that the panic happens right as the o/s tries to reset the system. I've tried turning off acpi in the bios but freebsd still see's it all and it has no affect. Is there anything I can do regarding sysctl.conf etc to prevent all this? Or alternatively if there is a problem do you know how to go abotu fixing it rather than just trynig to disable it? Matt, It seems like the fix right now is to disable it. Put this line: hint.acpi.0.disabled="1" in /boot/device.hints dave racette To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI errors and panic
Hi, I have just recently installed -CURRENT on my desktop as I've been using it succesfully on a server for months now. However this desktop has much more advanced hardware. Whilst it does work perfectly and I have device support for everything I get a lot of ACPI errors on bootup and also a panic when I try to reboot it, though luckily after it's synced the disks. I have saved the dmesg output to http://tao.xtaz.co.uk/dmesg.txt I was wondering if somebody could tell me what all those errors (and the random gibberish at the top) is about. I also assume that the panic happens right as the o/s tries to reset the system. I've tried turning off acpi in the bios but freebsd still see's it all and it has no affect. Is there anything I can do regarding sysctl.conf etc to prevent all this? Or alternatively if there is a problem do you know how to go abotu fixing it rather than just trynig to disable it? Regards, Matt. --- Matt ([EMAIL PROTECTED]) http://www.xtaz.co.uk/ --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI errors
>From dmesg.boot: acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0% ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed, AE_ERROR Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04ff0a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 996556073 Hz CPU: Mobile AMD Athlon(tm) 4 Processor (996.56-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x661 Stepping = 1 Features=0x383f9ff AMD Features=0xc044 real memory = 335544320 (320 MB) Regards, Hugo D. Valentim [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Rather verbose ACPI errors.
"David O'Brien" wrote: > Ever since the last ACPI import, I get all this output (non-verbose) > boot. What's the change on them going away soon? > > acpi0: on motherboard > ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 > ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND > ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND > ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND > ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND > ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND > ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND In this case, the tyan thunder K7 bios has got a hosed acpi dsdt table. There are referecens to a field "Z00Q" in a structure, but it isn't defined anywhere. It is regarding the ACPI code to enable the second serial port (pin header on motherboard). It will go away if/when tyan fix the bios. They broke this in a recent "upgrade". Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Rather verbose ACPI errors.
Ever since the last ACPI import, I get all this output (non-verbose) boot. What's the change on them going away soon? acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND acpi0: power button is handled as a fixed feature programming model. acpi0: sleep button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND ..snip.. psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00Q] in namespace, AE_NOT_FOUND ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI Errors on hp omnibook xe4100
On Thu, 2 Jan 2003, Adrian Neumaier wrote: > on of the problems this here: > > ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR > ACPI-1287: *** Error: Method execution failed, AE_ERROR > ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR > ACPI-1287: *** Error: Method execution failed, AE_ERROR > ACPI-1287: *** Error: Method execution failed, AE_ERROR > ACPI-1287: *** Error: Method execution failed, AE_ERROR > > this error occurs every time i boot and often during the work with the > laptop. Does booting with set hw.acpi.ec.event_driven=1 help? -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI Errors on hp omnibook xe4100
Hi, i have a hp omnibook xe4100 and the acpi stuff has some problems i dont know how to solve them. on of the problems this here: ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed, AE_ERROR ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed, AE_ERROR ACPI-1287: *** Error: Method execution failed, AE_ERROR ACPI-1287: *** Error: Method execution failed, AE_ERROR this error occurs every time i boot and often during the work with the laptop. the other problem is that i dont get any information about my battery status. apm and sysctl -a hw.acpi are always stating that the ac is online, even when its not plugged in. I included the output of dmesg, sysctl -a hw.acpi and apm. My Kernel is build without APM Support. In hoping for any help regards Adrian Neumaier hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.disable_on_poweroff: 1 hw.acpi.cpu.max_speed: 16 hw.acpi.cpu.current_speed: 16 hw.acpi.cpu.performance_speed: 16 hw.acpi.cpu.economy_speed: 8 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3312 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3632 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3682 hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.acline: 1 hw.acpi.battery.life: 100 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-RC-20021213-JPSNAP #0: Tue Dec 31 02:03:06 CET 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/LAPTOP Preloaded elf kernel "/boot/kernel/kernel" at 0xc05bb000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc05bb0a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1202735180 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1202.74-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b4 Stepping = 4 Features=0x383f9ff real memory = 637534208 (608 MB) avail memory = 613117952 (584 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 6 entries at 0xc00fdf60 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_lid0: on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xec00-0xefff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pcib1: could not get PCI interrupt routing table for \\_SB_.PCI0.AGPB - AE_NOT_FOUND pci1: on pcib1 pci1: at device 0.0 (no driver attached) cbb0: irq 11 at device 10.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0x1000-0x100f at device 17.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x1020-0x103f irq 9 at device 17.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub0: port error, restarting port 1 uhub0: port error, giving up port 1 ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.10, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. uhub0: port error, restarting port 2 uhub0: port error, giving up port 2 pci0: at device 17.4 (no driver attached) pcm0: port 0x1010-0x1013,0x1014-0x1017,0x1400-0x14ff irq 10 at device 17.5 on pci0 pci0: at device 17.6 (no driver attached) vr0: port 0x1c00-0x1cff mem 0xe800-0xe8ff irq 11 at device 18.0 on pci0 ../../../vm/uma_core.c:1330: could sleep with "vr0" locked from ../../../pci/if_vr.c:666 vr0: Ethernet address: 00:c0:9f:17:27:66 miibus0: on vr0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ../../../vm/uma_core.c:1330: could sleep with "vr0" locked from ../../../pci/if_vr.c:292 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: on ppbus0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0
Re: Call for testers: acpica-unix-20021122 (was Re: ACPI errors and then panic - fixed!)
> On Thu, 28 Nov 2002 13:38:13 +0900 (JST), Mitsuru IWASAKI ><[EMAIL PROTECTED]> said: Mitsuru> The patches against today's CURRENT at: Mitsuru> http://people.freebsd.org/~iwasaki/acpi/acpica-20021118-20021122-test20021128.diff Mitsuru> Please try this if you have problems about ACPI interpreter or GPE Mitsuru> initialization. Hi Iwasaki-San, Apologies for the delayed response as I was offline. I installed the above patch, but with no considerable change. I am still having problems with ACPI on my IBM A31p TP. Right now, I am using the world and kernel from 7th December. Is there a patch against the latest cvs ? These are the errors I get acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31 Using $PIR table, 14 entries at 0xc00fdeb0 ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST and this error I get when I try to suspend the TP. acpi0: AcpiGetSleepTypeData failed - AE_NOT_FOUND But then, the TP shuts down properly with ACPI if I poweroff with the button. Anything else I am missing ? TIA Regards Sid -- You can't carve your way to success without cutting remarks. Sid Carter - http://khader.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI errors
In message <[EMAIL PROTECTED]>, Hongbo Li wrot e: >I installed FBSD-current on my laptop(IBM Thinkpad >A21m). These were some error messages about ACPI in >dmesg: > >system power profile changed to 'economy' >ACPI-0432: *** Error: Handler for >[EmbeddedControl] returned AE_ERROR >ACPI-1287: *** Error: Method execution failed, >AE_ERROR >ACPI-0432: *** Error: Handler for >[EmbeddedControl] returned AE_ERROR >ACPI-1287: *** Error: Method execution failed, >AE_ERROR Try specifying hw.acpi.ec.event_driven="1" in device.hints . To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI errors
I installed FBSD-current on my laptop(IBM Thinkpad A21m). These were some error messages about ACPI in dmesg: system power profile changed to 'economy' ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed, AE_ERROR ACPI-0432: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1287: *** Error: Method execution failed, AE_ERROR __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [acpi-jp 2013] RE: ACPI errors w/ latest ACPI code on GA BX2000 based system
Thanks, Bob.
> I think this code is the problem:
>
> Scope(\_TZ_) {
> ThermalZone(THRM) {
> Name(_AL0, Package(0x1) {
> FAN_,
> })
>
>
> The name "FAN_" is not defined elsewhere in the namespace.
I guess that BIOS writer forgot to delete _AL0 definition :)
Instead, you can delete these lines and override DSDT, I think.
Name(_AL0, Package(0x1) {
FAN_,
})
Thanks
To my memo:
DefinitionBlock (
"acpi_dsdt.aml",//Output filename
"DSDT", //Signature
0x1,//DSDT Revision
"COMPAQ", //OEMID
"AWRDACPI", //TABLE ID
0x1000 //OEM Revision
)
>
> Bob
>
>
> -Original Message-
> From: Thomas Seck [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, November 30, 2002 4:34 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: [acpi-jp 2009] Re: ACPI errors w/ latest ACPI code on GA BX2000
> based system
>
> * Mitsuru IWASAKI ([EMAIL PROTECTED]):
>
> Iwasaki-san,
> list members,
>
> > > > ACPI-0438: *** Error: Looking up [FAN_] in namespace, AE_NOT_FOUND
> > > > ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND
> >
> > I think that this was caused by the following spec changes.
> > From CHANGES.txt:
> >
> > 22 October 2002. Summary of changes for version 20021022.
> >
> > 1) ACPI CA Core Subsystem:
> >
> > Implemented a restriction on the Scope operator that the
> > target must already exist in the namespace at the time the
> > operator is encountered (during table load or method
> > execution). In other words, forward references are not
> > allowed and Scope() cannot create a new object. This changes
> > the previous behavior where the interpreter would create the
> > name if not found. This new behavior correctly enables the
> > search-to-root algorithm during namespace lookup of the target
> > name. Because of this upsearch, this fixes the known Compaq
> > _SB_.OKEC problem and makes both the AML interpreter and iASL
> > compiler compatible with other ACPI implementations.
> >
> >
> > Could you send your acpidump output to this acpi-jp ML?
>
> Of course. And thank you very much for working on this. Please see the
> attached file.
>
> --Thomas
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: [acpi-jp 2009] Re: ACPI errors w/ latest ACPI code on GA BX2000 based system
I think this code is the problem:
Scope(\_TZ_) {
ThermalZone(THRM) {
Name(_AL0, Package(0x1) {
FAN_,
})
The name "FAN_" is not defined elsewhere in the namespace.
Bob
-Original Message-
From: Thomas Seck [mailto:[EMAIL PROTECTED]]
Sent: Saturday, November 30, 2002 4:34 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [acpi-jp 2009] Re: ACPI errors w/ latest ACPI code on GA BX2000
based system
* Mitsuru IWASAKI ([EMAIL PROTECTED]):
Iwasaki-san,
list members,
> > > ACPI-0438: *** Error: Looking up [FAN_] in namespace, AE_NOT_FOUND
> > > ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND
>
> I think that this was caused by the following spec changes.
> From CHANGES.txt:
>
> 22 October 2002. Summary of changes for version 20021022.
>
> 1) ACPI CA Core Subsystem:
>
> Implemented a restriction on the Scope operator that the
> target must already exist in the namespace at the time the
> operator is encountered (during table load or method
> execution). In other words, forward references are not
> allowed and Scope() cannot create a new object. This changes
> the previous behavior where the interpreter would create the
> name if not found. This new behavior correctly enables the
> search-to-root algorithm during namespace lookup of the target
> name. Because of this upsearch, this fixes the known Compaq
> _SB_.OKEC problem and makes both the AML interpreter and iASL
> compiler compatible with other ACPI implementations.
>
>
> Could you send your acpidump output to this acpi-jp ML?
Of course. And thank you very much for working on this. Please see the
attached file.
--Thomas
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: [acpi-jp 2004] ACPI errors w/ latest ACPI code on GA BX2000 based system
* Mitsuru IWASAKI ([EMAIL PROTECTED]):
Iwasaki-san,
list members,
> > > ACPI-0438: *** Error: Looking up [FAN_] in namespace, AE_NOT_FOUND
> > > ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND
>
> I think that this was caused by the following spec changes.
> From CHANGES.txt:
>
> 22 October 2002. Summary of changes for version 20021022.
>
> 1) ACPI CA Core Subsystem:
>
> Implemented a restriction on the Scope operator that the
> target must already exist in the namespace at the time the
> operator is encountered (during table load or method
> execution). In other words, forward references are not
> allowed and Scope() cannot create a new object. This changes
> the previous behavior where the interpreter would create the
> name if not found. This new behavior correctly enables the
> search-to-root algorithm during namespace lookup of the target
> name. Because of this upsearch, this fixes the known Compaq
> _SB_.OKEC problem and makes both the AML interpreter and iASL
> compiler compatible with other ACPI implementations.
>
>
> Could you send your acpidump output to this acpi-jp ML?
Of course. And thank you very much for working on this. Please see the
attached file.
--Thomas
/*
RSD PTR: Checksum=226, OEMID=COMPAQ, RsdtAddress=0x0fff3000
*/
/*
RSDT: Length=40, Revision=1, Checksum=17,
OEMID=COMPAQ, OEM Table ID=AWRDACPI, OEM Revision=0x42302e31,
Creator ID=AWRD, Creator Revision=0x0
*/
/*
Entries={ 0x0fff3040 }
*/
/*
DSDT=0xfff30c0
INT_MODEL=PIC
SCI_INT=9
SMI_CMD=0xb2, ACPI_ENABLE=0xa1, ACPI_DISABLE=0xa0, S4BIOS_REQ=0xa4
PM1a_EVT_BLK=0x4000-0x4003
PM1a_CNT_BLK=0x4004-0x4005
PM2_TMR_BLK=0x4008-0x400b
PM2_GPE0_BLK=0x400c-0x400f
P_LVL2_LAT=90ms, P_LVL3_LAT=900ms
FLUSH_SIZE=0, FLUSH_STRIDE=0
DUTY_OFFSET=1, DUTY_WIDTH=0
DAY_ALRM=13, MON_ALRM=0, CENTURY=0
Flags={WBINVD,PROC_C1,SLP_BUTTON}
*/
/*
DSDT: Length=10553, Revision=1, Checksum=88,
OEMID=COMPAQ, OEM Table ID=AWRDACPI, OEM Revision=0x1000,
Creator ID=MSFT, Creator Revision=0x10c
*/
DefinitionBlock (
"acpi_dsdt.aml",//Output filename
"DSDT", //Signature
0x1,//DSDT Revision
"COMPAQ", //OEMID
"AWRDACPI", //TABLE ID
0x1000 //OEM Revision
)
{
Scope(\_PR_) {
Processor(\_PR_.CPU0, 1, 0x4010, 0x6) {
}
}
Name(\_S0_, Package(0x2) {
0x5,
0x5,
})
OperationRegion(CMOS, SystemIO, 0x70, 0x2)
Field(CMOS, ByteAcc, NoLock, Preserve) {
INX_, 8,
DTA_, 8
}
Store(0x8, Local0)
Store(0x54, INX_)
Store(DTA_, Local1)
And(Local1, Local0, Local1)
If(LEqual(Local1, 0x8)) {
Name(\_S3_, Package(0x2) {
0x1,
0x1,
})
}
Else {
Name(\_S1_, Package(0x2) {
0x4,
0x4,
})
}
Name(\_S4_, Package(0x2) {
Zero,
Zero,
})
Name(\_S5_, Package(0x2) {
Zero,
Zero,
})
OperationRegion(\DEBG, SystemIO, 0x80, 0x1)
Field(\DEBG, ByteAcc, NoLock, Preserve) {
DBG1, 8
}
OperationRegion(\MUS1, SystemIO, 0x64, 0x1)
Field(\MUS1, ByteAcc, NoLock, Preserve) {
MUSE, 8
}
OperationRegion(EXTM, SystemMemory, 0x000ff830, 0x10)
Field(EXTM, WordAcc, NoLock, Preserve) {
ROM1, 16,
RMS1, 16,
ROM2, 16,
RMS2, 16,
ROM3, 16,
RMS3, 16,
AMEM, 32
}
OperationRegion(VGAM, SystemMemory, 0x000c0002, 0x1)
Field(VGAM, ByteAcc, NoLock, Preserve) {
VGA1, 8
}
OperationRegion(\TRAP, SystemIO, 0x402f, 0x1)
Field(\TRAP, ByteAcc, NoLock, Preserve) {
, 1,
TR13, 1
}
OperationRegion(PMES, SystemIO, 0x4015, 0x1)
Field(PMES, ByteAcc, NoLock, Preserve) {
, 1,
PME_, 1
}
OperationRegion(\GBLE, SystemIO, 0x4021, 0x1)
Field(\GBLE, ByteAcc, NoLock, Preserve) {
ESMI, 8
}
Name(CMDB, Buffer(0x8) { })
CreateByteField(CMDB, 0x0, BYT0)
CreateByteField(CMDB, 0x1, BYT1)
CreateByteField(CMDB, 0x2, BYT2)
CreateByteField(CMDB, 0x3, BYT3)
CreateByteField(CMDB, 0x4, BYT4)
CreateByteField(CMDB, 0x5, BYT5)
CreateByteField(CMDB, 0x6, BYT6)
CreateByteField(CMDB, 0x7, BYT7)
Name(IDEB, Buffer(0x38) { })
CreateField(IDEB, 0x0, 0x38, CMD0)
CreateField(IDEB, 0x38, 0x38, CMD1)
CreateField(IDEB, 0x70, 0x38, CMD2)
CreateField(IDEB, 0xa8, 0x38, CMD3)
CreateField(IDEB, 0xe0, 0x38, CMD4)
CreateField(IDEB, 0x0118, 0x38, CMD5)
CreateField(IDEB, 0x0150, 0x38, CMD6)
CreateField(IDEB, 0x0188, 0x38, CMD7)
OperationRegion(APMP, SystemIO, 0xb2, 0x2)
Field(APMP, ByteAcc, NoLock, Preserve) {
APMC, 8,
APMD, 8
}
OperationRegion(ELCR, SystemIO, 0x04d0, 0x2)
Field(ELCR, ByteAcc, NoLock, Preserve) {
ELC1, 8,
ELC2, 8
}
OperationRegion(GPOB, SystemIO, 0x4034, 0x4)
Field(GPOB, ByteAcc, NoLock, Preserve) {
GP00, 1,
GP01, 1,
GP02, 1,
GP03, 1,
GP04, 1,
GP05, 1,
GP06, 1,
GP07,
Re: [acpi-jp 2004] ACPI errors w/ latest ACPI code on GA BX2000based system
Hi, > A freshly built system with Now 28 sources now throws the ACPI errors > seen in the dmesg output. The former ACPI snapshot did not complain in > any way on this system. [snip] > > ACPI-0438: *** Error: Looking up [FAN_] in namespace, AE_NOT_FOUND > > ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND I think that this was caused by the following spec changes. >From CHANGES.txt: 22 October 2002. Summary of changes for version 20021022. 1) ACPI CA Core Subsystem: Implemented a restriction on the Scope operator that the target must already exist in the namespace at the time the operator is encountered (during table load or method execution). In other words, forward references are not allowed and Scope() cannot create a new object. This changes the previous behavior where the interpreter would create the name if not found. This new behavior correctly enables the search-to-root algorithm during namespace lookup of the target name. Because of this upsearch, this fixes the known Compaq _SB_.OKEC problem and makes both the AML interpreter and iASL compiler compatible with other ACPI implementations. Could you send your acpidump output to this acpi-jp ML? Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI errors w/ latest ACPI code on GA BX2000 based system
A freshly built system with Now 28 sources now throws the ACPI errors seen in the dmesg output. The former ACPI snapshot did not complain in any way on this system. The board in question is a Gigabyte BX2000 with F7 BIOS. --Thomas dmesg: > Copyright (c) 1992-2002 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.0-CURRENT #0: Fri Nov 29 00:53:39 CET 2002 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0614000. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06140a8. > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 549940129 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (549.94-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x673 Stepping = 3 > >Features=0x387f9ff > real memory = 268369920 (255 MB) > avail memory = 254169088 (242 MB) > Initializing GEOMetry subsystem > Pentium Pro MTRR support enabled > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 > Using $PIR table, 8 entries at 0xc00fdd70 > ACPI-0438: *** Error: Looking up [FAN_] in namespace, AE_NOT_FOUND > ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND > acpi0: power button is handled as a fixed feature programming model. > Timecounter "ACPI-safe" frequency 3579545 Hz > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 > acpi_cpu0: on acpi0 > acpi_tz0: on acpi0 > ACPI-0438: *** Error: Looking up [FAN_] in namespace, AE_NOT_FOUND > ACPI-1287: *** Error: Method execution failed, AE_NOT_FOUND > acpi_button0: on acpi0 > pcib0: port 0x5000-0x500f,0x4000-0x4041,0xcf8-0xcff on acpi0 > pci0: on pcib0 > agp0: mem 0xd800-0xdbff at >device 0.0 on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at device 0.0 (no driver attached) > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0xf000-0xf00f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > uhci0: port 0xe000-0xe01f irq 10 at device >7.2 on pci0 > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > pci0: at device 7.3 (no driver attached) > rl0: port 0xe400-0xe4ff mem 0xe000-0xe0ff irq 5 >at device 10.0 on pci0 > rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode > rl0: Ethernet address: 00:48:54:3d:60:ce > miibus0: on rl0 > rlphy0: on miibus0 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > pci0: at device 11.0 (no driver attached) > fdc0: port 0x3f7,0x3f2-0x3f5 >irq 6 drq 2 on acpi0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > sio0 port 0x3f8-0x3ff irq 4 on acpi0 > sio0: type 16550A > sio1 port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/16 bytes threshold > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model MouseMan+, device ID 0 > orm0: at iomem 0xc8000-0xc9fff,0xc-0xc7fff on isa0 > pmtimer0 on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 > Timecounters tick every 10.000 msec > ad0: DMA limited to UDMA33, non-ATA66 cable or device > ad0: 19541MB [39703/16/63] at ata0-master UDMA33 > acd0: CDROM at ata0-slave UDMA33 > acd1: CD-RW at ata1-slave UDMA33 > Mounting root from ufs:/dev/ad0s2a To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Call for testers: acpica-unix-20021122 (was Re: ACPI errors and then panic - fixed!)
* De: Mitsuru IWASAKI <[EMAIL PROTECTED]> [ Data: 2002-11-27 ] [ Subjecte: Call for testers: acpica-unix-20021122 (was Re: ACPI errors and then panic - fixed!) ] > The patches against today's CURRENT at: > http://people.freebsd.org/~iwasaki/acpi/acpica-20021118-20021122-test20021128.diff > > Please try this if you have problems about ACPI interpreter or GPE > initialization. Iwasaki-san! This works for me, thanks very much for helping keep us all up to date, and making it possible to get the issues resolved. Here's a dmesg from my laptop, now that ACPI works. %%% dmesg-YAY Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #48: Wed Nov 27 23:30:47 CST 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/LUNA Preloaded elf kernel "/boot/kernel/kernel" at 0xc0547000. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 474889174 Hz CPU: AMD-K6(tm) 3D processor (474.89-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x8800 real memory = 67043328 (63 MB) avail memory = 59457536 (56 MB) Security policy loaded: TrustedBSD MAC/None (trustedbsd_mac_none) Initializing GEOMetry subsystem K6-family MTRR support enabled (2 registers) acpi0: on motherboard ACPI-0628: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 6 entries at 0xc00fdf60 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <32-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_lid0: on acpi0 acpi_cmbat0: on acpi0 acpi_acad0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 initial configuration \\_SB_.PCI0.ISA_.LNK1 irq 11: [ 3 4 5 6 7 9 10 11 14 15] low,level,sharable 0.4.0 \\_SB_.PCI0.ISA_.LNK2 irq 11: [ 3 4 5 6 7 9 10 11 14 15] low,level,sharable 0.4.1 \\_SB_.PCI0.ISA_.LNK5 irq 9: [ 3 4 5 6 7 9 10 11 14 15] low,level,sharable 0.19.0 \\_SB_.PCI0.ISA_.LNK3 irq 5: [ 3 4 5 6 7 9 10 11 14 15] low,level,sharable 0.8.0 \\_SB_.PCI0.ISA_.LNK4 irq 10: [ 3 4 5 6 7 10 11 14 15] low,level,sharable 0.16.0 before setting priority for links before fixup boot-disabled links - after fixup boot-disabled links -- arbitrated configuration - \\_SB_.PCI0.ISA_.LNK1 irq 11: [ 3 4 5 6 7 9 10 11 14 15] low,level,sharable 0.4.0 \\_SB_.PCI0.ISA_.LNK2 irq 11: [ 3 4 5 6 7 9 10 11 14 15] low,level,sharable 0.4.1 \\_SB_.PCI0.ISA_.LNK5 irq 9: [ 3 4 5 6 7 9 10 11 14 15] low,level,sharable 0.19.0 \\_SB_.PCI0.ISA_.LNK3 irq 5: [ 3 4 5 6 7 9 10 11 14 15] low,level,sharable 0.8.0 \\_SB_.PCI0.ISA_.LNK4 irq 10: [ 3 4 5 6 7 10 11 14 15] low,level,sharable 0.16.0 pci0: on pcib0 agp0: mem 0xe000-0xe3ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 initial configuration \\_SB_.PCI0.ISA_.LNK1 irq 11: [ 3 4 5 6 7 9 10 11 14 15] low,level,sharable 1.0.0 before setting priority for links before fixup boot-disabled links - after fixup boot-disabled links -- arbitrated configuration - \\_SB_.PCI0.ISA_.LNK1 irq 11: [ 3 4 5 6 7 9 10 11 14 15] low,level,sharable 1.0.0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) cbb0: mem 0x8800-0x88000fff irq 11 at device 4.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: mem 0x88001000-0x88001fff irq 11 at device 4.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 isab0: at device 7.0 on pci0 isa0: on isab0 pcm0: mem 0xfedf-0xfedf,0xfeddf000-0xfedd irq 5 at device 8.0 on pci0 atapci0: port 0xfcf0-0xfcff at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at device 16.0 (no driver attached) pci0: at device 17.0 (no driver attached) ohci0: mem 0xfedde000-0xfeddefff irq 9 at device 19.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered speaker0 port 0x61 on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 acpi_ec0: port 0x66,0x62 on acpi0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 npx0: on motherboard npx0: INT 16 interface orm0: at iomem 0xc-0xcb7ff on isa0 ppc0: parallel port not found. sc0: at
Call for testers: acpica-unix-20021122 (was Re: ACPI errors andthen panic - fixed!)
Hi all, > > Our web person is out today, so things will be posted Monday at the > > earliest. > > > > I'll email Iwasaki-san the latest release, so y'all can get going if you > > want. > > Thank you! > I've just confirmed that the deleted object problem had been solved in > the latest release (Andy sent it to me). > I'll make diffs for FreeBSD soon. The patches against today's CURRENT at: http://people.freebsd.org/~iwasaki/acpi/acpica-20021118-20021122-test20021128.diff Please try this if you have problems about ACPI interpreter or GPE initialization. Please note that tarball for acpica-unix-20021122 and CHANGES.txt on Intel Web site is not available yet (will be availalbe next week), refer the Release notes from sourceforge.net instead. http://sourceforge.net/project/shownotes.php?group_id=36832&release_id=124563 Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [acpi-jp 2000] RE: ACPI errors and then panic - fixed!
Hi, > Our web person is out today, so things will be posted Monday at the > earliest. > > I'll email Iwasaki-san the latest release, so y'all can get going if you > want. Thank you! I've just confirmed that the deleted object problem had been solved in the latest release (Andy sent it to me). I'll make diffs for FreeBSD soon. John, there is new OS layer function for PCI. Could you help? Thanks /* * Interim function needed for PCI IRQ routing */ void AcpiOsDerivePciId( ACPI_HANDLE rhandle, ACPI_HANDLE chandle, ACPI_PCI_ID **PciId); To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: [acpi-jp 1988] Re: ACPI errors and then panic - fixed!
Our web person is out today, so things will be posted Monday at the
earliest.
I'll email Iwasaki-san the latest release, so y'all can get going if you
want.
Regards -- Andy
> -Original Message-
> From: Moore, Robert
> Sent: Wednesday, November 27, 2002 8:28 AM
> To: 'Mitsuru IWASAKI'; Grover, Andrew; Moore, Robert
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: [acpi-jp 1988] Re: ACPI errors and then panic - fixed!
>
>
>
> The deleted object problem has been fixed in the 20021122
> release which should be available soon, if not already. (I
> was able to reproduce the problem with your dsdt on previous
> releases, and I verified it fixed with the 11/22 release.)
>
> I did not see any mutex issues -- as we found out on Linux,
> the OSL implementation of wait_semaphore is often the culprit.
>
> Bob
>
>
> -Original Message-
> From: Mitsuru IWASAKI [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 27, 2002 12:37 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [acpi-jp 1988] Re: ACPI errors and then panic - fixed!
>
> Hi, Intel folks.
> It seems that there is a bug in cached object utilization.
> This causes strange behavior;
> first evaluation of \_SB_.PCI0.LPC_.EC__.BAT0._BST is OK, but
> second (or later) evaluation returns AE_TYPE.
>
> > acpi_cmbat0: error fetching current battery status -- AE_TYPE
>
> The raw DSDT is at:
> http://www.root.org/~nate/acpi/ibm.dsdt
>
> I guess that InternalObject was returned to cache in
> AcpiUtReleaseToCache() but the same object is still in use
> somewhere (for ResultObj ?).
>
> I could reproduce this problem with acpica debugger. Trace
> output attached. I'll track this down later.
>
> Thanks
>
>
> % acpicadb ibm.dsdt
> Loading Acpi table from file ibm.dsdt
> utmisc-0802 [11] UtAcquireMutex: Mutex
> [ACPI_MTX_Namespace] already acquired by this thread [C25]
> utmisc-0802 [11] UtAcquireMutex: Mutex
> [ACPI_MTX_Namespace] already acquired by this thread [C25]
> Parsing
> Methods:..
> ..
> ..
> ..
> ..
>
> Table [DSDT] - 1208 Objects with 61 Devices 354 Methods 18
> Regions Acpi table [DSDT] successfully installed and loaded
> - f _BST
> \_SB_.PCI0.LPC_.EC__.BAT0._BST (0x80ba0a8) - Method
> \_SB_.PCI0.LPC_.EC__.BAT1._BST (0x80ba6a8) - Method
> - debug _SB_.PCI0.LPC_.EC__.BAT0._BST
> Executing \_SB_.PCI0.LPC_.EC__.BAT0._BST
> 0 #007F XOr (DerefOf (Index (BT0I, 0x00)))
>
> %
> ArgObj:0x80b9ea8 Name BT0I Package 0x80e1ba8
> ArgObj:0x80f9fa8 Integer
> ArgObj:0x80fe028 Integer
> 0 #0037 [EvalSubTree] (Package (0x0D)
> {
> 0x00,
> 0x,
> 0x,
> 0x01,
> 0x2A30,
> 0x00,
> 0x00,
> 0x01,
> 0x01,
> "",
> "",
> "",
> ""
> })
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
RE: [acpi-jp 1988] Re: ACPI errors and then panic - fixed!
The deleted object problem has been fixed in the 20021122 release which
should be available soon, if not already. (I was able to reproduce the
problem with your dsdt on previous releases, and I verified it fixed with
the 11/22 release.)
I did not see any mutex issues -- as we found out on Linux, the OSL
implementation of wait_semaphore is often the culprit.
Bob
-Original Message-
From: Mitsuru IWASAKI [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 27, 2002 12:37 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [acpi-jp 1988] Re: ACPI errors and then panic - fixed!
Hi, Intel folks.
It seems that there is a bug in cached object utilization.
This causes strange behavior;
first evaluation of \_SB_.PCI0.LPC_.EC__.BAT0._BST is OK, but
second (or later) evaluation returns AE_TYPE.
> acpi_cmbat0: error fetching current battery status -- AE_TYPE
The raw DSDT is at:
http://www.root.org/~nate/acpi/ibm.dsdt
I guess that InternalObject was returned to cache in AcpiUtReleaseToCache()
but the same object is still in use somewhere (for ResultObj ?).
I could reproduce this problem with acpica debugger. Trace output attached.
I'll track this down later.
Thanks
% acpicadb ibm.dsdt
Loading Acpi table from file ibm.dsdt
utmisc-0802 [11] UtAcquireMutex: Mutex [ACPI_MTX_Namespace]
already acquired by this thread [C25]
utmisc-0802 [11] UtAcquireMutex: Mutex [ACPI_MTX_Namespace]
already acquired by this thread [C25]
Parsing
Methods:
..
Table [DSDT] - 1208 Objects with 61 Devices 354 Methods 18 Regions
Acpi table [DSDT] successfully installed and loaded
- f _BST
\_SB_.PCI0.LPC_.EC__.BAT0._BST (0x80ba0a8) - Method
\_SB_.PCI0.LPC_.EC__.BAT1._BST (0x80ba6a8) - Method
- debug _SB_.PCI0.LPC_.EC__.BAT0._BST
Executing \_SB_.PCI0.LPC_.EC__.BAT0._BST
0 #007F XOr (DerefOf (Index (BT0I, 0x00)))
%
ArgObj:0x80b9ea8 Name BT0I Package 0x80e1ba8
ArgObj:0x80f9fa8 Integer
ArgObj:0x80fe028 Integer
0 #0037 [EvalSubTree] (Package (0x0D)
{
0x00,
0x,
0x,
0x01,
0x2A30,
0x00,
0x00,
0x01,
0x01,
"",
"",
"",
""
})
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ACPI errors - IBM Thinkpad A31p
> On Tue, 26 Nov 2002 14:33:09 +0900 (JST), Mitsuru IWASAKI ><[EMAIL PROTECTED]> said: Mitsuru> Hi, Mitsuru> Are you trying this with acpica-unix-20021118 patch which was Mitsuru> announced recently? Mitsuru> http://people.freebsd.org/~iwasaki/acpi/acpica-20021002-20021118-test20021121.diff Hi, Tried the above patch, but the kernel itself won't compile. I just did a fresh cvsup and patched. It fails at the cardbus compile. >> ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST >> ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST >> ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST >> ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST >> ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST >> ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST >> ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST >> ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST >> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 >> acpi_cpu0: on acpi0 >> acpi_tz0: on acpi0 >> acpi_lid0: on acpi0 >> acpi_button0: on acpi0 Regards Sid -- Cleanliness is next to impossible. Sid Carter - http://khader.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [acpi-jp 1988] Re: ACPI errors and then panic - fixed!
Hi, Intel folks.
It seems that there is a bug in cached object utilization.
This causes strange behavior;
first evaluation of \_SB_.PCI0.LPC_.EC__.BAT0._BST is OK, but
second (or later) evaluation returns AE_TYPE.
> acpi_cmbat0: error fetching current battery status -- AE_TYPE
The raw DSDT is at:
http://www.root.org/~nate/acpi/ibm.dsdt
I guess that InternalObject was returned to cache in AcpiUtReleaseToCache()
but the same object is still in use somewhere (for ResultObj ?).
I could reproduce this problem with acpica debugger. Trace output attached.
I'll track this down later.
Thanks
% acpicadb ibm.dsdt
Loading Acpi table from file ibm.dsdt
utmisc-0802 [11] UtAcquireMutex: Mutex [ACPI_MTX_Namespace] already acquired
by this thread [C25]
utmisc-0802 [11] UtAcquireMutex: Mutex [ACPI_MTX_Namespace] already acquired
by this thread [C25]
Parsing
Methods:..
Table [DSDT] - 1208 Objects with 61 Devices 354 Methods 18 Regions
Acpi table [DSDT] successfully installed and loaded
- f _BST
\_SB_.PCI0.LPC_.EC__.BAT0._BST (0x80ba0a8) - Method
\_SB_.PCI0.LPC_.EC__.BAT1._BST (0x80ba6a8) - Method
- debug _SB_.PCI0.LPC_.EC__.BAT0._BST
Executing \_SB_.PCI0.LPC_.EC__.BAT0._BST
0 #007F XOr (DerefOf (Index (BT0I, 0x00)))
%
ArgObj:0x80b9ea8 Name BT0I Package 0x80e1ba8
ArgObj:0x80f9fa8 Integer
ArgObj:0x80fe028 Integer
0 #0037 [EvalSubTree] (Package (0x0D)
{
0x00,
0x,
0x,
0x01,
0x2A30,
0x00,
0x00,
0x01,
0x01,
"",
"",
"",
""
})
%
ArgObj:0x80fe0a8 Integer 000D
ResultObj: 0x80e1ba8 Package 0x80e1ba8
ResultObj: 0x80fe828 [Index] Integer
0 #007F XOr (DerefOf (-Return Value- ()))
%
ArgObj:0x80abf28
ArgObj:0x80fe828 [Index] Integer
ResultObj: 0x80fe0a8 Integer
0 #007F XOr (-Return Value- (), 0x01, Local0)
%
ArgObj:0x80b02a8
ArgObj:0x80fe0a8 Integer
ArgObj:0x80fe828 Integer 0001
ArgObj:0x80fe028 [Local0] 0x0 Uninitialized
ResultObj: 0x80f9fa8 Integer 0001
D #00A4 Return (E #0035 GBST (0x00, HB0S, Local0, BT0P))
% into
ArgObj:0x80fe028 Integer
ArgObj:0x80b7828 Name HB0S RegionField 0x80df5a8
ArgObj:0x80fe828 [Local0] 0x80f9fa8 Integer 0001
ArgObj:0x80b9f28 Name BT0P Package 0x80e1c28
0 #5B80 OperationRegion (ECOR (Path \_SB_.PCI0.LPC_.EC__.ECOR), EmbeddedControl,
0x00, 0x0100)
%
ArgObj:0x80fe928 Integer
ArgObj:0x80fe9a8 Integer 0100
DEBUG[read (EC, 8, 0x38)](default: 0x0 / 0) >>
0 #0037 [EvalSubTree] (Package (0x04) {})
%
ArgObj:0x80fe828 Integer 0004
ResultObj: 0x80e1c28 Package 0x80e1c28
0 #5B23 Acquire (BATM, 0x)
%
ArgObj:0x80b9aa8 Name BATM Mutex 0x80e18a8
ArgObj:0x80fe828 Integer
ResultObj: 0x80fe928 Integer
8 #00A0 If (And (Arg1, 0x20)) {}
%
ArgObj:0x80fe928 [Arg1] 0x80fe8a8 Integer
ArgObj:0x80fe828 Integer 0020
ArgObj:0x80fe9a8 Integer
ResultObj: 0x80fe928 Integer
8 #00A0 If (Predicate = [False], Skipping IF block
%
00015 #00A0 If (And (Arg1, 0x40)) {}
%
ArgObj:0x80fe928 [Arg1] 0x80fe8a8 Integer
ArgObj:0x80fe9a8 Integer 0040
ArgObj:0x80fe828 Integer
ResultObj: 0x80fe928 Integer
00015 #00A0 If (Predicate = [False], Skipping IF block
%
00022 #0070 Store (0x00, Local0)
%
ArgObj:0x80fe928 Integer
ArgObj:0x80fe828 [Local0] 0x0 Uninitialized
ResultObj: 0x80fe928 Integer
00020 #00A1 Else
{
Predicate = [False], ELSE block was executed
%
00013 #00A1 Else
{
Predicate = [False], ELSE block was executed
%
00026 #00A0 If (And (Arg1, 0x0F)) {}
%
ArgObj:0x80fe828 [Arg1] 0x80fe8a8 Integer
ArgObj:0x80fe9a8 Integer 000F
ArgObj:0x80feaa8 Integer
ResultObj: 0x80fe828 Integer 0
Re: [acpi-jp 1940] Re: ACPI errors and then panic - fixed!
On Thu, 21 Nov 2002, Mitsuru IWASAKI wrote: > > On Sat, 5 Oct 2002, Mitsuru IWASAKI wrote: > > > From: Nate Lawson <[EMAIL PROTECTED]> > > > Subject: ACPI errors and then panic > > > Date: Fri, 4 Oct 2002 17:14:31 -0700 (PDT) > > > Message-ID: <[EMAIL PROTECTED]> > > > > > > > My laptop appears to work ok without ACPI but of course I don't get > > > > suspend, resume, etc. I have never been able to get ACPI to work with it, > > > > including with a -current as of 2 hours ago. If ACPI is enabled, I get a > > > > spew of: > > > > > > > > ACPI-0412 *** Error: NsSearchAndEnter: Bad character in ACPI name > > > > > > > > and then a panic from acpi_attach. > > > > I sent a reply including the requested traces on Oct 25. Do you need any > > more information? > > Please try with new ACPI CA patches at: > http://people.freebsd.org/~iwasaki/acpi/acpica-20021002-20021118-test20021121.diff > Some memory leak releated bugs were fixed, so your problem might be > solved by this hopefully. I did try the patch and am happy to report that my laptop boots with acpi enabled. Thank you! Please commit it before 5.0R. However, acpi doesn't seem to be working for me. Calls to check the battery status fail. Here is my dmesg and sysctl: hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 1 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3252 hw.acpi.thermal.tz0.active: -1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3637 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3692 hw.acpi.thermal.tz0._ACx: -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.battery.life: 98 hw.acpi.battery.time: -1 hw.acpi.battery.state: 4 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 hw.acpi.acline: 1 --- Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #11: Tue Nov 26 10:44:02 PST 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/LAPTOP Preloaded elf kernel "/boot/kernel/kernel" at 0xc0562000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc05620a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 999153113 Hz CPU: Pentium III/Pentium III Xeon/Celeron (999.15-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383f9ff real memory = 401997824 (383 MB) avail memory = 384696320 (366 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31 Using $PIR table, 14 entries at 0xc00fdeb0 ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_lid0: on acpi0 ACPI-1287: *** Error: Method execution failed, AE_NOT_EXIST acpi_button0: on acpi0 ACPI-1287: *** Error: Me
Re: ACPI errors - IBM Thinkpad A31p
Hi, Are you trying this with acpica-unix-20021118 patch which was announced recently? http://people.freebsd.org/~iwasaki/acpi/acpica-20021002-20021118-test20021121.diff Also [EMAIL PROTECTED] is better place for ACPI CA related problem reports. Thanks From: Sid Carter <[EMAIL PROTECTED]> Subject: ACPI errors - IBM Thinkpad A31p Date: 26 Nov 2002 10:35:41 +0530 Message-ID: <[EMAIL PROTECTED]> > Hi Folks, > > I see this error while booting into BSD and I presume this might be the > problem that acpi on my TP does not work. > > The errors are something like this. > > > acpi0: on motherboard > Using $PIR table, 14 entries at 0xc00fdeb0 > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > acpi0: power button is handled as a fixed feature programming model. > Timecounter "ACPI-fast" frequency 3579545 Hz > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > acpi_cpu0: on acpi0 > acpi_tz0: on acpi0 > acpi_lid0: on acpi0 > acpi_button0: on acpi0 > > > Dmesg on the box > > > FreeBSD 5.0-CURRENT #0: Fri Nov 22 17:37:35 IST 2002 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0618000. > Preloaded elf module "/boot/kernel/snd_ich.ko" at 0xc06180a8. > Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc0618154. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0618200. > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 1198990668 Hz > CPU: Pentium 4 (1198.99-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 > Features=0x3febf9ff AT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM> > real memory = 267780096 (255 MB) > avail memory = 253579264 (241 MB) > Initializing GEOMetry subsystem > Pentium Pro MTRR support enabled > npx0: on motherboard > npx0: INT 16 interface > > > uname -a > > FreeBSD tango 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Nov 22 17:37:35 IST 2002 >root@tango:/usr/obj/usr/src/sys/GENERIC i386 > > Any fix for this ? I am unable to use ACPI in FBSD. > > TIA > Regards > Sid > -- > When I was in school, I cheated on my metaphysics exam: I looked into > the soul of the boy sitting next to me. > -- Woody Allen > > Sid Carter - http://khader.net/ > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI errors - IBM Thinkpad A31p
Hi Folks, I see this error while booting into BSD and I presume this might be the problem that acpi on my TP does not work. The errors are something like this. acpi0: on motherboard Using $PIR table, 14 entries at 0xc00fdeb0 ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 Dmesg on the box FreeBSD 5.0-CURRENT #0: Fri Nov 22 17:37:35 IST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0618000. Preloaded elf module "/boot/kernel/snd_ich.ko" at 0xc06180a8. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc0618154. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0618200. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1198990668 Hz CPU: Pentium 4 (1198.99-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febf9ff real memory = 267780096 (255 MB) avail memory = 253579264 (241 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface uname -a FreeBSD tango 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Nov 22 17:37:35 IST 2002 root@tango:/usr/obj/usr/src/sys/GENERIC i386 Any fix for this ? I am unable to use ACPI in FBSD. TIA Regards Sid -- When I was in school, I cheated on my metaphysics exam: I looked into the soul of the boy sitting next to me. -- Woody Allen Sid Carter - http://khader.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI Errors - IBM Thinkpad A31p
Hi Folks, I see this error while booting into BSD and I presume this might be the problem that acpi on my TP does not work. The errors are something like this. acpi0: on motherboard Using $PIR table, 14 entries at 0xc00fdeb0 ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST ACPI-1354: *** Error: Method execution failed, AE_NOT_EXIST acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 Dmesg on the box FreeBSD 5.0-CURRENT #0: Fri Nov 22 17:37:35 IST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0618000. Preloaded elf module "/boot/kernel/snd_ich.ko" at 0xc06180a8. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc0618154. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc0618200. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1198990668 Hz CPU: Pentium 4 (1198.99-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febf9ff real memory = 267780096 (255 MB) avail memory = 253579264 (241 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface uname -a FreeBSD tango 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Nov 22 17:37:35 IST 2002 root@tango:/usr/obj/usr/src/sys/GENERIC i386 Any fix for this ? I am unable to use ACPI in FBSD. TIA Regards Sid -- The church is near but the road is icy; the bar is far away but I will walk carefully. -- Russian Proverb Sid Carter - http://khader.net To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [acpi-jp 1940] Re: ACPI errors and then panic
Hi, > On Sat, 5 Oct 2002, Mitsuru IWASAKI wrote: > > From: Nate Lawson <[EMAIL PROTECTED]> > > Subject: ACPI errors and then panic > > Date: Fri, 4 Oct 2002 17:14:31 -0700 (PDT) > > Message-ID: <[EMAIL PROTECTED]> > > > > > My laptop appears to work ok without ACPI but of course I don't get > > > suspend, resume, etc. I have never been able to get ACPI to work with it, > > > including with a -current as of 2 hours ago. If ACPI is enabled, I get a > > > spew of: > > > > > > ACPI-0412 *** Error: NsSearchAndEnter: Bad character in ACPI name > > > > > > and then a panic from acpi_attach. > > I sent a reply including the requested traces on Oct 25. Do you need any > more information? Please try with new ACPI CA patches at: http://people.freebsd.org/~iwasaki/acpi/acpica-20021002-20021118-test20021121.diff Some memory leak releated bugs were fixed, so your problem might be solved by this hopefully. > One interesting thing is that the oem sysctl node seems bogus: >hint.acpi.0.oem=IBM ?? > where the ?'s are invalid characters like the happy face. I saw similar problem long time ago. My problem was acpi.ko is too old and badly matched with kernel. Please make sure that your acpi.ko is fresh as well as kernel when you try. > > BTW, what's model name? Some ThinkPad's are blacklisted such as > > IBM 600E. And may I add your ACPI data to our repo. (in Japan) ? > > IBM T23. Feel free to use the dsdt and/or asl however you wish. OK, I'll add them to our CVS repo. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI errors and then panic
On Sat, 5 Oct 2002, Mitsuru IWASAKI wrote: > From: Nate Lawson <[EMAIL PROTECTED]> > Subject: ACPI errors and then panic > Date: Fri, 4 Oct 2002 17:14:31 -0700 (PDT) > Message-ID: <[EMAIL PROTECTED]> > > > My laptop appears to work ok without ACPI but of course I don't get > > suspend, resume, etc. I have never been able to get ACPI to work with it, > > including with a -current as of 2 hours ago. If ACPI is enabled, I get a > > spew of: > > > > ACPI-0412 *** Error: NsSearchAndEnter: Bad character in ACPI name > > > > and then a panic from acpi_attach. I sent a reply including the requested traces on Oct 25. Do you need any more information? Thanks, -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI errors and then panic
Thank you for the reply. On Sat, 5 Oct 2002, Mitsuru IWASAKI wrote: > Hi, > # ACPI CA related problem should be sent to [EMAIL PROTECTED] > # so that Intel folks can be aware of the problem. Ok, I didn't know that. > From: Nate Lawson <[EMAIL PROTECTED]> > Subject: ACPI errors and then panic > Date: Fri, 4 Oct 2002 17:14:31 -0700 (PDT) > Message-ID: <[EMAIL PROTECTED]> > > > My laptop appears to work ok without ACPI but of course I don't get > > suspend, resume, etc. I have never been able to get ACPI to work with it, > > including with a -current as of 2 hours ago. If ACPI is enabled, I get a > > spew of: > > > > ACPI-0412 *** Error: NsSearchAndEnter: Bad character in ACPI name > > > > and then a panic from acpi_attach. > > First several lines of DDB backtrace would be very helpful > to track the problem down. > Also having following lines in your loader.conf would be > helpful to determine which object causes the ACPI CA Eroor. > > debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_BUS" > debug.acpi.level="ACPI_LV_WARN ACPI_LV_ERROR ACPI_LV_OBJECTS" I have placed a ddb session with tracebacks for two panics at: http://www.root.org/~nate/acpi/ddb1 http://www.root.org/~nate/acpi/ddb2 I set your debug options in device.hints. One interesting thing is that the oem sysctl node seems bogus: hint.acpi.0.oem=IBM ?? where the ?'s are invalid characters like the happy face. > BTW, what's model name? Some ThinkPad's are blacklisted such as > IBM 600E. And may I add your ACPI data to our repo. (in Japan) ? IBM T23. Feel free to use the dsdt and/or asl however you wish. > > Here are the appropriate files... > > http://www.root.org/~nate/acpi/ibm.asl > > http://www.root.org/~nate/acpi/ibm.dsdt > > http://www.root.org/~nate/acpi/ibm.dmesg (from a working boot) (Note that I renamed the .aml file to asl as shown above) -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI errors and then panic
Hi, # ACPI CA related problem should be sent to [EMAIL PROTECTED] # so that Intel folks can be aware of the problem. From: Nate Lawson <[EMAIL PROTECTED]> Subject: ACPI errors and then panic Date: Fri, 4 Oct 2002 17:14:31 -0700 (PDT) Message-ID: <[EMAIL PROTECTED]> > My laptop appears to work ok without ACPI but of course I don't get > suspend, resume, etc. I have never been able to get ACPI to work with it, > including with a -current as of 2 hours ago. If ACPI is enabled, I get a > spew of: > > ACPI-0412 *** Error: NsSearchAndEnter: Bad character in ACPI name > > and then a panic from acpi_attach. First several lines of DDB backtrace would be very helpful to track the problem down. Also having following lines in your loader.conf would be helpful to determine which object causes the ACPI CA Eroor. debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_BUS" debug.acpi.level="ACPI_LV_WARN ACPI_LV_ERROR ACPI_LV_OBJECTS" BTW, what's model name? Some ThinkPad's are blacklisted such as IBM 600E. And may I add your ACPI data to our repo. (in Japan) ? > Here are the appropriate files... > http://www.root.org/~nate/acpi/ibm.aml > http://www.root.org/~nate/acpi/ibm.dsdt > http://www.root.org/~nate/acpi/ibm.dmesg (from a working boot) > > Let me know if you need more info. > > -Nate > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI errors and then panic
My laptop appears to work ok without ACPI but of course I don't get suspend, resume, etc. I have never been able to get ACPI to work with it, including with a -current as of 2 hours ago. If ACPI is enabled, I get a spew of: ACPI-0412 *** Error: NsSearchAndEnter: Bad character in ACPI name and then a panic from acpi_attach. Here are the appropriate files... http://www.root.org/~nate/acpi/ibm.aml http://www.root.org/~nate/acpi/ibm.dsdt http://www.root.org/~nate/acpi/ibm.dmesg (from a working boot) Let me know if you need more info. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: acpica-unix-20020829 patches (was Re: Lots of ACPI errors when booting yesterdays CURRENT
On Thu, Sep 05, 2002 at 03:06:30PM +0900, Mitsuru IWASAKI wrote: > Please try the latest version acpica-unix-20020829, patches for > FreeBSD at: > http://people.freebsd.org/~iwasaki/acpi/acpica-20020815-20020829-test20020905.diff Hi Mitsuru, I applied your patches today and besides the "Revision"s mismatch it applied cleanly. Running it now without new problems or new features. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
acpica-unix-20020829 patches (was Re: Lots of ACPI errors whenbooting yesterdays CURRENT
Hi, > Below is a trimmed dmesg from booting yesterdays CURRENT on my > SuperMicro P3TDE6 machine (RCC/ServerWorks HE-SLt chipset). > I heven't found anything wrong with the OS, it is just that the boot > seems to be a bit on the chatty side :-) > Is this caused by a bad BIOS setting or is there something strange with > this board/BIOS or the acpi support in CURRENT? > I also noticed support for four acpi_cpu:s is, this as intended, the > board only have room for two? Please try the latest version acpica-unix-20020829, patches for FreeBSD at: http://people.freebsd.org/~iwasaki/acpi/acpica-20020815-20020829-test20020905.diff Hopefully some of the problems will be solved. From CHANGES.txt If the target of a Scope() operator already exists, it must be an object type that actually opens a scope -- such as a Device, Method, Scope, etc. This is a fatal runtime error. Similar error check has been added to the iASL compiler also. Tightened up the namespace load to disallow multiple names in the same scope. This previously was allowed if both objects were of the same type. (i.e., a lookup was the same as entering a new name). Thanks > Copyright (c) 1992-2002 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.0-CURRENT #0: Tue Sep 3 17:41:10 CEST 2002 > [EMAIL PROTECTED]:/usr/obj/ext/FreeBSD/CURRENT/sys/EUKLIDES > Preloaded elf kernel "/boot/kernel/kernel" at 0xc04c7000. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04c70a8. > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 1266068553 Hz > CPU: Pentium III/Pentium III Xeon/Celeron (1266.07-MHz 686-class CPU) >Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 > > >Features=0x383fbff > real memory = 536805376 (524224K bytes) > avail memory = 515674112 (503588K bytes) > Pentium Pro MTRR support enabled > Using $PIR table, 10 entries at 0xc00f52e0 > ACPI-0536: *** Error: Field name [INDX] already exists in current scope > ACPI-0536: *** Error: Field name [DATA] already exists in current scope > ACPI-0536: *** Error: Field name [INDX] already exists in current scope > ACPI-0536: *** Error: Field name [DATA] already exists in current scope > ACPI-0536: *** Error: Field name [C000] already exists in current scope > ACPI-0536: *** Error: Field name [C010] already exists in current scope > ACPI-0536: *** Error: Field name [C020] already exists in current scope > ACPI-0685: *** Warning: NsLookup: INDX, type 1, checking for type 11 > ACPI-0685: *** Warning: NsLookup: DATA, type 2, checking for type 11 > ACPI-0685: *** Warning: NsLookup: INDX, type 1, checking for type 11 > ACPI-0685: *** Warning: NsLookup: DATA, type 2, checking for type 11 > ACPI-0685: *** Warning: NsLookup: C000, type 8, checking for type 13 > ACPI-0685: *** Warning: NsLookup: C010, type 8, checking for type 13 > ACPI-0685: *** Warning: NsLookup: C020, type 8, checking for type 13 > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND > ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND > ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND > ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND > ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND > ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND > ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND > ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND > acpi0: power button is handled as a fixed feature programming model. > Timecounter "ACPI-safe" frequency 3579545 Hz > ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND > --- 15 identical lines removed > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 > acpi_cpu0: on acpi0 > acpi_cpu1: on acpi0 > acpi_cpu2: on acpi0 > acpi_cpu3: on acpi0 > acpi_button0: on acpi0 > pcib1: on acpi0 > pci0: on pcib1 > pcib3: at device 0.1 on pci0 > pci1: on pcib3 > pci1: at device 0.0 (no driver attached) > nge0: port 0xde00-0xdeff mem > 0xfeadb000-0xfeadbfff irq 11 at device 1.0 on pci0 > nge0: Ethernet address: 00:40:33:af:35:33 > miibus0: on nge0 > nsgphy0: on miibus0 > nsgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > pci0: at device 2.0 (no driver attached) > pcm0: port 0xdf00-0xdf3f irq 11 at device 3.0 on pci0 > ahc_pci0: port 0xd000-0xd0ff mem > 0xfeadc000-0xfeadcfff irq 5 at device 5.0 on pci0 > aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs > ahc_pci1: port 0xd800-0xd8ff mem > 0xfeadf000-0xfead irq 10 at device 5.1 on pci0 > aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs > fxp0: port 0xd400-0xd43f mem > 0xfe90-0xfe9f,0xfeadd000-0xfeaddfff irq 9 a
Lots of ACPI errors when booting yesterdays CURRENT
Below is a trimmed dmesg from booting yesterdays CURRENT on my SuperMicro P3TDE6 machine (RCC/ServerWorks HE-SLt chipset). I heven't found anything wrong with the OS, it is just that the boot seems to be a bit on the chatty side :-) Is this caused by a bad BIOS setting or is there something strange with this board/BIOS or the acpi support in CURRENT? I also noticed support for four acpi_cpu:s is, this as intended, the board only have room for two? /Martin Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Tue Sep 3 17:41:10 CEST 2002 [EMAIL PROTECTED]:/usr/obj/ext/FreeBSD/CURRENT/sys/EUKLIDES Preloaded elf kernel "/boot/kernel/kernel" at 0xc04c7000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04c70a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 1266068553 Hz CPU: Pentium III/Pentium III Xeon/Celeron (1266.07-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383fbff real memory = 536805376 (524224K bytes) avail memory = 515674112 (503588K bytes) Pentium Pro MTRR support enabled Using $PIR table, 10 entries at 0xc00f52e0 ACPI-0536: *** Error: Field name [INDX] already exists in current scope ACPI-0536: *** Error: Field name [DATA] already exists in current scope ACPI-0536: *** Error: Field name [INDX] already exists in current scope ACPI-0536: *** Error: Field name [DATA] already exists in current scope ACPI-0536: *** Error: Field name [C000] already exists in current scope ACPI-0536: *** Error: Field name [C010] already exists in current scope ACPI-0536: *** Error: Field name [C020] already exists in current scope ACPI-0685: *** Warning: NsLookup: INDX, type 1, checking for type 11 ACPI-0685: *** Warning: NsLookup: DATA, type 2, checking for type 11 ACPI-0685: *** Warning: NsLookup: INDX, type 1, checking for type 11 ACPI-0685: *** Warning: NsLookup: DATA, type 2, checking for type 11 ACPI-0685: *** Warning: NsLookup: C000, type 8, checking for type 13 ACPI-0685: *** Warning: NsLookup: C010, type 8, checking for type 13 ACPI-0685: *** Warning: NsLookup: C020, type 8, checking for type 13 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND --- 15 identical lines removed acpi_timer0: <32-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_cpu2: on acpi0 acpi_cpu3: on acpi0 acpi_button0: on acpi0 pcib1: on acpi0 pci0: on pcib1 pcib3: at device 0.1 on pci0 pci1: on pcib3 pci1: at device 0.0 (no driver attached) nge0: port 0xde00-0xdeff mem 0xfeadb000-0xfeadbfff irq 11 at device 1.0 on pci0 nge0: Ethernet address: 00:40:33:af:35:33 miibus0: on nge0 nsgphy0: on miibus0 nsgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto pci0: at device 2.0 (no driver attached) pcm0: port 0xdf00-0xdf3f irq 11 at device 3.0 on pci0 ahc_pci0: port 0xd000-0xd0ff mem 0xfeadc000-0xfeadcfff irq 5 at device 5.0 on pci0 aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs ahc_pci1: port 0xd800-0xd8ff mem 0xfeadf000-0xfead irq 10 at device 5.1 on pci0 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs fxp0: port 0xd400-0xd43f mem 0xfe90-0xfe9f,0xfeadd000-0xfeaddfff irq 9 at device 6.0 on pci0 fxp0: Ethernet address 00:30:48:23:0e:af inphy0: on miibus1 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto isab0: port 0x580-0x58f at device 15.0 on pci0 isa0: on isab0 pci0: at device 15.1 (no driver attached) pci0: at device 15.2 (no driver attached) pcib4: on acpi0 pcib4: duplicate bus number 0 - not probing bus atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND --- 13 identical lines removed fdc0: cmd 3 failed at out byte 1 of 3 ACPI-1354: *** Error: Method execution failed, AE_NOT_FOUND --- 170 identical lines removed fdc0: cmd 3 failed at out byte 1 of 3 ACPI-1354: *** Error: Method execution failed, AE_N
Re: ACPI errors
Mitsuru IWASAKI wrote: > [move to -current because STABLE don't have acpica support yet] > > Hi, > > > System: TOS 5005-S504 > > Error with any kernel build: > > Using $PIR table, 0 entries at 0xc00f0190 > > ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation: AE_BAD_SIGNAT URE > > ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_SIGNATU RE > > ACPI: Table load failed: AE_BAD_SIGNATURE > > It seems that this problem happens after sys/i386/i386/pmap.c rev > 1.352 changes. Could you replace pmap.c with 1.351 ? > > Peter, do you have any ideas with this ? If backing out rev 1.352 solves the problem, feel free to go ahead and either back it out or add #if 0 around the changes. But I think the fix is to change this: /* We have a 1MB direct mapped region at KERNBASE */ if (pa < 0x0010 && pa + size <= 0x0010) - return (void *)(pa + KERNBASE); + return (void *)(pa + offset + KERNBASE); I've committed this as 1.356. If it doesn't solve it, then go ahead and back out both 1.352 and 1.356. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: ACPI errors
-Original Message-
From: Mitsuru IWASAKI [mailto:[EMAIL PROTECTED]]
Sent: Sun 8/4/2002 8:59 AM
To: Robert D Hughes
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: ACPI errors
[move to -current because STABLE don't have acpica support yet]
I reposted it over there, so let's move the conversation there.
Hi,
> System: TOS 5005-S504
> Error with any kernel build:
> Using $PIR table, 0 entries at 0xc00f0190
> ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation:
AE_BAD_SIGNATURE
> ACPI-0213: *** Error: AcpiLoadTables: Could not load tables:
AE_BAD_SIGNATURE
> ACPI: Table load failed: AE_BAD_SIGNATURE
It seems that this problem happens after sys/i386/i386/pmap.c rev
1.352 changes. Could you replace pmap.c with 1.351 ?
How would I pull a specific version from cvs?
Peter, do you have any ideas with this ?
> Same thing happens if I do an unset acpi_load or if I try boot -s, or both.
I think your kernel config file includes 'device acpica'.
Nope. It's auto-loading as a module, as per NOTES.
Thanks,
Rob
èR{.nÇ+·¬zwfj)m¢f£¢·hkyàRàÂ+aº{.nÇ+·ç±×.®·§¶)í
æèw* ¶¦zË
ACPI Errors
Reposted because I screwed up the first time and sent it to the wrong list System: TOS 5005-S504 Error with any kernel build: Using $PIR table, 0 entries at 0xc00f0190 ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation: AE_BAD_SIGNATURE ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_SIGNATURE ACPI: Table load failed: AE_BAD_SIGNATURE Shortly after that, I get a hard lock at at either the load of the fxp driver, or when probing the pci bus. Same thing happens if I do an unset acpi_load or if I try boot -s, or both. Ideas? ¡Iì¹» ®&Þ±éݨ¥¶Ý¢jçH:+éì¹» ®&Þ~·nÇ\ººÞا¶¡Ü¨~Ø^ë,j
Re: ACPI errors
It seems Mitsuru IWASAKI wrote: > [move to -current because STABLE don't have acpica support yet] > > Hi, > > > System: TOS 5005-S504 > > Error with any kernel build: > > Using $PIR table, 0 entries at 0xc00f0190 > > ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation: AE_BAD_SIGNATURE > > ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_SIGNATURE > > ACPI: Table load failed: AE_BAD_SIGNATURE Yups that fails here on all systems I have as well... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI errors
[move to -current because STABLE don't have acpica support yet] Hi, > System: TOS 5005-S504 > Error with any kernel build: > Using $PIR table, 0 entries at 0xc00f0190 > ACPI-0171: *** Error: AcpiLoadTables: RSDP Failed validation: AE_BAD_SIGNATURE > ACPI-0213: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_SIGNATURE > ACPI: Table load failed: AE_BAD_SIGNATURE It seems that this problem happens after sys/i386/i386/pmap.c rev 1.352 changes. Could you replace pmap.c with 1.351 ? Peter, do you have any ideas with this ? > Same thing happens if I do an unset acpi_load or if I try boot -s, or both. I think your kernel config file includes 'device acpica'. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI errors on laptop running latest -current
When I boot up my gateway solo 2550, I get the following errors ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR ACPI-0428: *** Error: Handler for [EmbeddedControl] returned AE_ERROR ACPI-1305: *** Error: Method execution failed, AE_ERROR I've attached my dmesg. I also think there is a problem with acpi detecting the battery properly. IF anyone has any ideas I'd appreciate it. hw.acpi.acline: 0 hw.acpi.battery.life: 0 hw.acpi.battery.time: -1 hw.acpi.battery.state: 0 hw.acpi.battery.units: 1 hw.acpi.battery.info_expire: 5 -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. [EMAIL PROTECTED] FreeBSD Committer Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Wed Jun 12 22:44:45 CDT 2002 root@:/usr/obj/usr/src/sys/DWCJR Preloaded elf kernel "/boot/kernel/kernel" at 0xc03e9000. Preloaded elf module "/boot/kernel/usb.ko" at 0xc03e90a8. Preloaded elf module "/boot/kernel/random.ko" at 0xc03e9150. Preloaded elf module "/boot/kernel/sysvmsg.ko" at 0xc03e91fc. Preloaded elf module "/boot/kernel/sysvsem.ko" at 0xc03e92a8. Preloaded elf module "/boot/kernel/snp.ko" at 0xc03e9354. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc03e93fc. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 647189041 Hz CPU: Pentium III/Pentium III Xeon/Celeron (647.19-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383f9ff real memory = 167706624 (163776K bytes) avail memory = 158613504 (154896K bytes) Pentium Pro MTRR support enabled Using $PIR table, 15 entries at 0xc00fded0 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_pcib0: port 0xcf8-0xcff on acpi0 pci0: on acpi_pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1000-0x100f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: irq 5 at device 7.2 on pci0 uhci0: Could not map ports device_probe_and_attach: uhci0 attach returned 6 pci0: at device 7.3 (no driver attached) pccbb0: irq 10 at device 10.0 on pci0 cardbus0: on pccbb0 pccard0: <16-bit PCCard bus> on pccbb0 pccbb1: irq 10 at device 10.1 on pci0 cardbus1: on pccbb1 pccard1: <16-bit PCCard bus> on pccbb1 pci0: at device 14.0 (no driver attached) pci0: at device 16.0 (no driver attached) acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_button0: on acpi0 acpi_ec0: port 0x66,0x62 on acpi0 ppc0 port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 orm0: at iomem 0xc-0xcbfff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 pmtimer0 on isa0 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled Timecounters tick every 10.000 msec acpi_cpu: CPU throttling enabled, 8 steps from 100% to 12.5% cardbus1: Expecting link target, got 0x22 cardbus1: Resource not specified in CIS: id=10, size=100 cardbus1: Resource not specified in CIS: id=14, size=200 rl0: port 0x1100-0x11ff mem 0x84002000-0x840021ff irq 10 at device 0.0 on cardbus1 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:50:22:00:23:f5 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ad0: 9590MB [19485/16/63] at ata0-master UDMA33 acd0: DVD-ROM at ata1-master PIO4 Mounting root from ufs:/dev/ad0s2a WARNING: / was not properl
