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
On Tue, 23 Sep 2003, Jeremy Bingham wrote: On 23/09/03 18:07 -0700, Nate Lawson wrote: Enable options DDB. When it hangs, press CTRL-ALT-ESC and then tr to get a traceback. While ACPI influences this problem, I am uncertain it is the root cause. -Nate Way ahead of you there. I compiled a kernel with DDB on, installed it, and everything worked fine. No hangs or anything. When I recompiled the kernel with the debugging options off, the same hang happened again. Bizarre, to say the least. Again, booting with ACPI turned off worked fine. I'm making another debug kernel, and I'll try running that for a while. When you say debugging options, do you mean you added things other than options DDB (i.e. INVARIANTS or others)? -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]
Re: Problem w/ ACPI in -CURRENT
So, after running this laptop with debugging stuff and INVARIANTS on all day and having it work fine, I decided to try taking the INVARIANTS options out of the kernel. Lo and behold, it now hangs again when I try to boot. I can't even get it to respond when I hit Ctrl-Alt-Esc and try to get it to go into debugging mode and get a stack trace. When I was looking at where it was dying before with verbose logging turned on, it seemed to be dying when it was trying to initialize the battery. I looked at the ACPI stuff in the kernel, and I think I may have found where it stops working. (It's where the kernel tries to initialize the battery - somewhere in sys/dev/acpia/acpi_cmbat.c.) Interesting. Try turning on ACPI_LV_FUNCTIONS (see the email I just sent to -current) as well as ACPI_DEBUG and let me know the last 3-4 prints before it hangs. Not blaming anyone here, but could you also try without ATAng? I am unable to use ATAng on my laptop. -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
On 25/09/03 11:54 -0700, Nate Lawson wrote: Interesting. Try turning on ACPI_LV_FUNCTIONS (see the email I just sent to -current) as well as ACPI_DEBUG and let me know the last 3-4 prints before it hangs. Not blaming anyone here, but could you also try without ATAng? I am unable to use ATAng on my laptop. -Nate Will do. One question, though, before I get to recompiling -- is there some specific option for ATAng in the kernel that I'm missing? The only thing I see that looks similar is 'device ata'. -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
On Thu, 25 Sep 2003, Jeremy Bingham wrote: On 25/09/03 11:54 -0700, Nate Lawson wrote: Interesting. Try turning on ACPI_LV_FUNCTIONS (see the email I just sent to -current) as well as ACPI_DEBUG and let me know the last 3-4 prints before it hangs. Not blaming anyone here, but could you also try without ATAng? I am unable to use ATAng on my laptop. -Nate Will do. One question, though, before I get to recompiling -- is there some specific option for ATAng in the kernel that I'm missing? The only thing I see that looks similar is 'device ata'. Unfortunately, no. You can cvsup to 2003/8/23 on just the sys/dev/ata directory and revert the change to sys/conf/files. That does the trick. Currently ATAng causes a hang on resume from suspend whereas it has worked for months before ATAng. I am running -current without ATAng with no problems. -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
On 25/09/03 12:26 -0700, Nate Lawson wrote: Will do. One question, though, before I get to recompiling -- is there some specific option for ATAng in the kernel that I'm missing? The only thing I see that looks similar is 'device ata'. Unfortunately, no. You can cvsup to 2003/8/23 on just the sys/dev/ata directory and revert the change to sys/conf/files. That does the trick. Currently ATAng causes a hang on resume from suspend whereas it has worked for months before ATAng. I am running -current without ATAng with no problems. -Nate Interesting. That's a problem I haven't come across yet, oddly enough, and I've been bouncing back and forth between 5.1-RELEASE and -CURRENT a bunch. Recovery from suspend seems to working as far as I recall, at least on console (X, in its majesty, freaks out). I'll try it w/out ATAng, though. -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
Unfortunately, no. You can cvsup to 2003/8/23 on just the sys/dev/ata directory and revert the change to sys/conf/files. That does the trick. Currently ATAng causes a hang on resume from suspend whereas it has worked for months before ATAng. I am running -current without ATAng with no problems. -Nate Herm. I checked out a copy of the sys tree from 8/23, copied the files from sys/dev/ata over (after deleting the current ones), made the changes in sys/conf/files, and tried making a new kernel, but it won't do it. I get errors like: ../../../dev/ata/ata-all.c: In function `ataioctl': ../../../dev/ata/ata-all.c:409: error: `ATAPICMD' undeclared (first use in this function) ../../../dev/ata/ata-all.c:409: error: (Each undeclared identifier is reported only once ../../../dev/ata/ata-all.c:409: error: for each function it appears in.) ../../../dev/ata/ata-all.c:421: error: union has no member named `atapi' ../../../dev/ata/ata-all.c:424: error: union has no member named `atapi' ../../../dev/ata/ata-all.c:424: error: `ATAPI_CMD_WRITE' undeclared (first use in this function) ../../../dev/ata/ata-all.c:425: error: union has no member named `atapi' ../../../dev/ata/ata-all.c:425: error: union has no member named `atapi' ... etc. etc. etc. What am I missing? Incidentally, compiling a kernel w/ ACPI_DEBUG and putting those lines in /boot/loader.conf that you mentioned in that other email did nothing -- booting with verbose logging gave the same amount of logging, and booting normally didn't give any more messages than normal. -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
On Thu, 25 Sep 2003, Jeremy Bingham wrote: Unfortunately, no. You can cvsup to 2003/8/23 on just the sys/dev/ata directory and revert the change to sys/conf/files. That does the trick. Currently ATAng causes a hang on resume from suspend whereas it has worked for months before ATAng. I am running -current without ATAng with no problems. -Nate Herm. I checked out a copy of the sys tree from 8/23, copied the files from sys/dev/ata over (after deleting the current ones), made the changes in sys/conf/files, and tried making a new kernel, but it won't do it. I get errors like: ../../../dev/ata/ata-all.c: In function `ataioctl': ../../../dev/ata/ata-all.c:409: error: `ATAPICMD' undeclared (first use in this function) ... etc. etc. etc. What am I missing? /sys/sys/ata.h needs to be reverted. You should look at the original commit message to have a full understanding of what needs to be reverted. Incidentally, compiling a kernel w/ ACPI_DEBUG and putting those lines in /boot/loader.conf that you mentioned in that other email did nothing -- booting with verbose logging gave the same amount of logging, and booting normally didn't give any more messages than normal. That's because ACPI is a module and options defined in the kernel config do not apply to the modules. I think someone was working on fixing this annoyance. To rebuild it, cd /sys/modules/acpi and do: make ACPI_DEBUG=1 cp acpi.ko /boot/kernel.test (or wherever your test kernel is) reboot An easier way is to just include acpi in the kernel build. Add this to your kernel config and rebuild: device acpica options ACPI_DEBUG -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
So, after running this laptop with debugging stuff and INVARIANTS on all day and having it work fine, I decided to try taking the INVARIANTS options out of the kernel. Lo and behold, it now hangs again when I try to boot. I can't even get it to respond when I hit Ctrl-Alt-Esc and try to get it to go into debugging mode and get a stack trace. When I was looking at where it was dying before with verbose logging turned on, it seemed to be dying when it was trying to initialize the battery. I looked at the ACPI stuff in the kernel, and I think I may have found where it stops working. (It's where the kernel tries to initialize the battery - somewhere in sys/dev/acpia/acpi_cmbat.c.) What should I do? I can't even seem to get the kernel to core dump right for some reason, so should I insert some code to spit out messages in the kernel where I think it might be hanging, or am I totally going down the wrong path here? -j -- /* You are not expected to understand this. */ Captain_Tenille http://www.satanosphere.com/ [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Problem w/ ACPI in -CURRENT
There may be a problem with the ACPI drivers in -CURRENT. I cvsup'ed to -CURRENT earlier today (9/23/03), rebuilt the world and kernel, and installed everything without incident. When I rebooted my laptop after installing the world, the kernel started hanging part way through the boot process. I played around with it some, and found some things out about what was going on. When booting FreeBSD with verbose logging on, these are the last messages displayed. acpi_acad0: acline inititialization start acpi_acad0: On Line acpi_acad0: acline inititialization done, tried 1 times acpi_cmbat0: battery initialization start ^^^ hangs after that When booting FreeBSD normally or in single-user mode, these are the last messages displayed: Timecounter TSC frequency 498470127 Hz quality 800 Timecounters tick every 10.000 msec ^^^ hangs after that When booting FreeBSD with ACPI turned off or in Safe Mode, the computer boots normally. Rebooting with either of those options, however, leads the kernel to complain about some processes not dying. I'm not sure if that's relevant to this problem, however. When booting with the old kernel from 5.1-RELEASE, it booted OK, but complained some (as one might expect). Right now, since the laptop boots with ACPI turned off and the verbose logging seems to die when it's doing something with the battery, it looks to me like the problem is there. Right now, I'm building a new kernel with debugging support turned on, so hopefully by tonight I might know more. Has any one else come across this problem, or is it more likely something on my end? -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
When booting FreeBSD normally or in single-user mode, these are the last messages displayed: Timecounter TSC frequency 498470127 Hz quality 800 Timecounters tick every 10.000 msec ^^^ hangs after that When booting FreeBSD with ACPI turned off or in Safe Mode, the computer boots normally. Enable options DDB. When it hangs, press CTRL-ALT-ESC and then tr to get a traceback. While ACPI influences this problem, I am uncertain it is the root cause. -Nate ___ [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
On 23/09/03 18:07 -0700, Nate Lawson wrote: Enable options DDB. When it hangs, press CTRL-ALT-ESC and then tr to get a traceback. While ACPI influences this problem, I am uncertain it is the root cause. -Nate Way ahead of you there. I compiled a kernel with DDB on, installed it, and everything worked fine. No hangs or anything. When I recompiled the kernel with the debugging options off, the same hang happened again. Bizarre, to say the least. Again, booting with ACPI turned off worked fine. I'm making another debug kernel, and I'll try running that for a while. -j -- /* You are not expected to understand this. */ Captain_Tenille http://www.satanosphere.com/ [EMAIL PROTECTED] ___ [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
On Tuesday 23 September 2003 10:01 pm, Jeremy Bingham wrote: On 23/09/03 18:07 -0700, Nate Lawson wrote: Enable options DDB. When it hangs, press CTRL-ALT-ESC and then tr to get a traceback. While ACPI influences this problem, I am uncertain it is the root cause. -Nate Way ahead of you there. I compiled a kernel with DDB on, installed it, and everything worked fine. No hangs or anything. When I recompiled the kernel with the debugging options off, the same hang happened again. Bizarre, to say the least. Again, booting with ACPI turned off worked fine. I'm making another debug kernel, and I'll try running that for a while. I've been having the same issue for a couple of weeks now, and am not sure if it is ACPI related or ATAng. I'll post my traceback, tomorrow when I finish rebuilding. -- Anish Mistry pgp0.pgp Description: signature
