Re: Problem w/ ACPI in -CURRENT: Update
On 29/10/03 18:18 -0800, Nate Lawson wrote: I looked at a few other ASL copies I have and you have an old version. Have you done a BIOS update recently? Yours: OEMID=DELL, OEM Table ID=CPi R, OEM Revision=0x27d0040b, Others: OEMID=DELL, OEM Table ID=CPi R, OEM Revision=0x27d20b07, Others: OEMID=DELL, OEM Table ID=CPi R, OEM Revision=0x27d3050f, Update your BIOS and then do acpidump -t to verify your revision is the latest. -Nate Success! I updated my BIOS from A05 to A14, and -CURRENT works beautifully. I only wish that I had read this email a few hours earlier, before I got frustrated and decided to give Debian a shot on this laptop. Happily running FreeBSD again, -j -- /* You are not expected to understand this. */ Captain_Tenille http://www.satanosphere.com/ http://www.kuro5hin.org/ [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: Problem w/ ACPI in -CURRENT: Update
On Thu, 30 Oct 2003, Jeremy Bingham wrote: On 29/10/03 18:18 -0800, Nate Lawson wrote: I looked at a few other ASL copies I have and you have an old version. Have you done a BIOS update recently? Yours: OEMID=DELL, OEM Table ID=CPi R, OEM Revision=0x27d0040b, Others: OEMID=DELL, OEM Table ID=CPi R, OEM Revision=0x27d20b07, Others: OEMID=DELL, OEM Table ID=CPi R, OEM Revision=0x27d3050f, Update your BIOS and then do acpidump -t to verify your revision is the latest. -Nate Success! I updated my BIOS from A05 to A14, and -CURRENT works beautifully. I only wish that I had read this email a few hours earlier, before I got frustrated and decided to give Debian a shot on this laptop. Linux would probably have had the same problem with your AML since we use the same interpreter. Happily running FreeBSD again, Glad to hear it. Anyone else having ACPI trouble should please update to their latest BIOS revision before reporting a problem. Thanks, Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem w/ ACPI in -CURRENT: Update
On Wed, 1 Oct 2003, Jeremy Bingham wrote: On 30/09/03 15:04 -0700, Nate Lawson wrote: As far as debugging prints, add the following printfs to acpi_cmbat_get_bif(): printf(Before getting BIF\n); as = AcpiEvaluateObject(h, _BIF, NULL, bif_buffer); printf(After getting BIF\n); The second one did not trigger (I had actually been using ACPI_VPRINT for a while to get info like that). I have a dump of my ASL here: http://home.satanosphere.com/bsd/jeremy.asl.gz. As far as my dmesg goes, I can get you one where it boots w/ ACPI disabled, but when it hangs, it hangs before / is mounted at all, so I can't really get it. Should I boot it again and just type the last lines out? I looked at a few other ASL copies I have and you have an old version. Have you done a BIOS update recently? Yours: OEMID=DELL, OEM Table ID=CPi R, OEM Revision=0x27d0040b, Others: OEMID=DELL, OEM Table ID=CPi R, OEM Revision=0x27d20b07, Others: OEMID=DELL, OEM Table ID=CPi R, OEM Revision=0x27d3050f, Update your BIOS and then do acpidump -t to verify your revision is the latest. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem w/ ACPI in -CURRENT: Update
On 01/10/03 11:28 -0700, Nate Lawson wrote: dmesg is not necessary. The only way to find what is hanging is to keep working printfs deeper into the _BIF method. Start with AcpiEvaluateObject in sys/contrib/dev/acpica/nsxfeval.c and sprinkle printf A, B, C etc. throughout to find where it hangs. Alternatively, if you have a serial console and gdb, you can step through the method. -Nate I think I've tracked the offending line down, in sys/contrib/dev/acpia/sparse.c Status = WalkState-AscendingCallback (WalkState); The line shows up several times in the file, but that's the first occurance of it in the file. Interestingly, the function that line's in (or the while loop) does seem to be successfully run a few times before it fails. Is there anything else I should be looking for? I've looked around the source tree trying to figure out exactly what AscendingCallback is, but I'm not finding anything. -j -- /* You are not expected to understand this. */ Captain_Tenille http://www.satanosphere.com/ [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: Problem w/ ACPI in -CURRENT: Update
On 30/09/03 15:04 -0700, Nate Lawson wrote: Are you sure you tracked it down to INVARIANTS? Or was it DDB? Please try with _just_ DDB and see if you can still reproduce the problem. If so, then when it hangs, hit CTRL-ALT-ESC and type tr. This will tell who is hung. As far as debugging prints, add the following printfs to acpi_cmbat_get_bif(): printf(Before getting BIF\n); as = AcpiEvaluateObject(h, _BIF, NULL, bif_buffer); printf(After getting BIF\n); -Nate Tried compiling a kernel with just DDB, and I got no love. It still hung, and although I tried hitting CTRL-ALT-ESC and typing tr, it hung so hard that even that didn't work. -j -- /* You are not expected to understand this. */ Captain_Tenille http://www.satanosphere.com/ [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: Problem w/ ACPI in -CURRENT: Update
On Wed, 1 Oct 2003, Jeremy Bingham wrote: On 30/09/03 15:04 -0700, Nate Lawson wrote: Are you sure you tracked it down to INVARIANTS? Or was it DDB? Please try with _just_ DDB and see if you can still reproduce the problem. If so, then when it hangs, hit CTRL-ALT-ESC and type tr. This will tell who is hung. As far as debugging prints, add the following printfs to acpi_cmbat_get_bif(): printf(Before getting BIF\n); as = AcpiEvaluateObject(h, _BIF, NULL, bif_buffer); printf(After getting BIF\n); -Nate Tried compiling a kernel with just DDB, and I got no love. It still hung, and although I tried hitting CTRL-ALT-ESC and typing tr, it hung so hard that even that didn't work. Ok, that's good to know. How about the printfs? Did the second one trigger? I could use a URL to your ASL and full dmesg on boot: acpidump -t -d | gzip jeremy.asl.gz -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem w/ ACPI in -CURRENT: Update
On 01/10/03 09:33 -0700, Nate Lawson wrote: On Wed, 1 Oct 2003, Jeremy Bingham wrote: On 30/09/03 15:04 -0700, Nate Lawson wrote: Are you sure you tracked it down to INVARIANTS? Or was it DDB? Please try with _just_ DDB and see if you can still reproduce the problem. If so, then when it hangs, hit CTRL-ALT-ESC and type tr. This will tell who is hung. As far as debugging prints, add the following printfs to acpi_cmbat_get_bif(): printf(Before getting BIF\n); as = AcpiEvaluateObject(h, _BIF, NULL, bif_buffer); printf(After getting BIF\n); -Nate Tried compiling a kernel with just DDB, and I got no love. It still hung, and although I tried hitting CTRL-ALT-ESC and typing tr, it hung so hard that even that didn't work. Ok, that's good to know. How about the printfs? Did the second one trigger? I could use a URL to your ASL and full dmesg on boot: acpidump -t -d | gzip jeremy.asl.gz -Nate The second one did not trigger (I had actually been using ACPI_VPRINT for a while to get info like that). I have a dump of my ASL here: http://home.satanosphere.com/bsd/jeremy.asl.gz. As far as my dmesg goes, I can get you one where it boots w/ ACPI disabled, but when it hangs, it hangs before / is mounted at all, so I can't really get it. Should I boot it again and just type the last lines out? -j -- /* You are not expected to understand this. */ Captain_Tenille http://www.satanosphere.com/ [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: Problem w/ ACPI in -CURRENT: Update
On Wed, 1 Oct 2003, Jeremy Bingham wrote: On 01/10/03 09:33 -0700, Nate Lawson wrote: As far as debugging prints, add the following printfs to acpi_cmbat_get_bif(): printf(Before getting BIF\n); as = AcpiEvaluateObject(h, _BIF, NULL, bif_buffer); printf(After getting BIF\n); -Nate Ok, that's good to know. How about the printfs? Did the second one trigger? I could use a URL to your ASL and full dmesg on boot: The second one did not trigger (I had actually been using ACPI_VPRINT for a while to get info like that). I have a dump of my ASL here: http://home.satanosphere.com/bsd/jeremy.asl.gz. dmesg is not necessary. The only way to find what is hanging is to keep working printfs deeper into the _BIF method. Start with AcpiEvaluateObject in sys/contrib/dev/acpica/nsxfeval.c and sprinkle printf A, B, C etc. throughout to find where it hangs. Alternatively, if you have a serial console and gdb, you can step through the method. -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem w/ ACPI in -CURRENT: Update
Now I'm having an issue with ACPI. I used to hit the power button and that would initiate a proper shutdown. Now it seems to do nothing, but when I reboot the system goes into a suspended state before completing the shutdown. The motherboard beeps three times, the screen goes blank, and will complete the shutdown after I hit the any key. The strange thing is that in the past, a user initiated suspend while the system is running would never blank the screen, but this suspend-before-shutdown does... What do you need from me to help resolve this? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem w/ ACPI in -CURRENT: Update
In my continuing quest to figure out what's wrong with ACPI in -CURRENT on my laptop, I've tried going back to the old ata drivers (worked, but made no difference), ended up blowing my computer up (weird fsck problem crept in), went back to 5.1, moved up to -CURRENT again, and started plugging away at this problem again. I'm still not sure what's causing it, but I think I've found where it's hanging now: acpi_cmbat_get_bif() in acpi_cmbat.c. I'm putting more debugging statements into that file to see if I can narrow down exactly where it's hanging, but it looks like the problem is somewhere in there. Any ideas what I should be looking for? -j -- /* You are not expected to understand this. */ Captain_Tenille http://www.satanosphere.com/ [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: Problem w/ ACPI in -CURRENT: Update
I'm not sure what's causing these ACPI problems in this recent -CURRENT, but I've found where it's hanging. It's on this line: as = AcpiEvaluateObject(h, _BIF, NULL, bif_buffer); in acpi_cmbat.c in sys/dev/acpica/. The function AcpiEvaluateObject is found in contrib/dev/acpica/nsxfeval.c, which hasn't changed in a while. I tried adding a line to print out 'h', but I wasn't sure what to try to show it as. Prining it as an integer gave a weird negative value. What, exactly, should I be looking for here? -j -- /* You are not expected to understand this. */ Captain_Tenille http://www.satanosphere.com/ [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: Problem w/ ACPI in -CURRENT: Update
Please do not start new threads for the same problem as it makes it hard to track down what your problem even was originally. I assume your problem is hangs during boot, it appeared since 5.1R, and it goes away if you enable options INVARIANTS. Is that right? -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem w/ ACPI in -CURRENT: Update
On 30/09/03 14:48 -0700, Nate Lawson wrote: Please do not start new threads for the same problem as it makes it hard to track down what your problem even was originally. I assume your problem is hangs during boot, it appeared since 5.1R, and it goes away if you enable options INVARIANTS. Is that right? -Nate Yes, that is the case. It was only today that I managed to track down where the problem was cropping up, though. -j P.S. My apologies on the starting a new thread. -- /* You are not expected to understand this. */ Captain_Tenille http://www.satanosphere.com/ [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: Problem w/ ACPI in -CURRENT: Update
On Tue, 30 Sep 2003, Jeremy Bingham wrote: On 30/09/03 14:48 -0700, Nate Lawson wrote: Please do not start new threads for the same problem as it makes it hard to track down what your problem even was originally. I assume your problem is hangs during boot, it appeared since 5.1R, and it goes away if you enable options INVARIANTS. Is that right? -Nate Yes, that is the case. It was only today that I managed to track down where the problem was cropping up, though. Are you sure you tracked it down to INVARIANTS? Or was it DDB? Please try with _just_ DDB and see if you can still reproduce the problem. If so, then when it hangs, hit CTRL-ALT-ESC and type tr. This will tell who is hung. As far as debugging prints, add the following printfs to acpi_cmbat_get_bif(): printf(Before getting BIF\n); as = AcpiEvaluateObject(h, _BIF, NULL, bif_buffer); printf(After getting BIF\n); -Nate ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
