Re: ACPI thermal panics ThinkPad 600X
As Kevin Oberman wrote: > > Can you suspend from within graphics mode? > Have you tried using APMD to put the display into text mode when > suspending? Tried it, but didn't get that to work. I. e., it seems apmd never calls /etc/rc.suspend (i can't see any syslog entry from that logger call either). -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI thermal panics ThinkPad 600X
> Date: Mon, 17 Feb 2003 23:22:28 +0100 (MET) > From: [EMAIL PROTECTED] (Joerg Wunsch) > Sender: [EMAIL PROTECTED] > > "Matthew N. Dodd" <[EMAIL PROTECTED]> wrote: > > > My only outstanding issue is that I can't suspend if an application > > is holding /dev/dsp or /dev/audio open. > > Can you suspend from within graphics mode? I can't seem to do that, > neither with APM nor with ACPI. In some case, i've seen four > horizontal lines upon wakeup, in other cases, the graphics display > gets restored correctly, but the machine still locks up (probably in > APM BIOS, not even the lock key LEDs react, but Fn works). > > Suspending from within text mode always works. The graphics mode > problem is particularly annoying if the system enters auto-suspend > on a low battery condition... Have you tried using APMD to put the display into text mode when suspending? This si not my favorite way to do things, but it should work a lot better than nothing. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI thermal panics ThinkPad 600X
Terry Lambert <[EMAIL PROTECTED]> wrote: > A more useful reference, I think, is: > > http://sourceforge.net/mailarchive/message.php?msg_id=3597172 > > If you add similar code to FreeBSD to detect and patch the BIOS > table, this fixes the problem in FreeBSD, as well (though adding > the code is somewhat tricky: YMMV, knowledge of both FreeBSD and > Linux required; sorry, I do not have a patch against -current). Yah, I think the correct/updated version is at: http://www.poupinou.org/acpi/ibm_ecdt.html However, I think I'll pray and wait for an IBM BIOS fix. I'm not yet that desperate. ;-( In the meantime, I'll muddle through with apm. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI thermal panics ThinkPad 600X
Darryl Okahata wrote: > Tom Rhodes <[EMAIL PROTECTED]> wrote: > > > ACPI gives me hell on my IBM Thinkpad A31, also. Yet since it > > does not crash anything I just leave it be waiting for the day > > when the ACPI hackers have time to fix it :) > > It may not necessarily be a FreeBSD problem (or, not only). While > there may be issues with FreeBSD's ACPI, there are definitely issues > with the A31 BIOS: > > http://sourceforge.net/mailarchive/message.php?msg_id=3597168 A more useful reference, I think, is: http://sourceforge.net/mailarchive/message.php?msg_id=3597172 If you add similar code to FreeBSD to detect and patch the BIOS table, this fixes the problem in FreeBSD, as well (though adding the code is somewhat tricky: YMMV, knowledge of both FreeBSD and Linux required; sorry, I do not have a patch against -current). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI thermal panics ThinkPad 600X
Tom Rhodes <[EMAIL PROTECTED]> wrote: > ACPI gives me hell on my IBM Thinkpad A31, also. Yet since it > does not crash anything I just leave it be waiting for the day > when the ACPI hackers have time to fix it :) It may not necessarily be a FreeBSD problem (or, not only). While there may be issues with FreeBSD's ACPI, there are definitely issues with the A31 BIOS: http://sourceforge.net/mailarchive/message.php?msg_id=3597168 -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI thermal panics ThinkPad 600X
"Matthew N. Dodd" <[EMAIL PROTECTED]> wrote: > My only outstanding issue is that I can't suspend if an application > is holding /dev/dsp or /dev/audio open. Can you suspend from within graphics mode? I can't seem to do that, neither with APM nor with ACPI. In some case, i've seen four horizontal lines upon wakeup, in other cases, the graphics display gets restored correctly, but the machine still locks up (probably in APM BIOS, not even the lock key LEDs react, but Fn works). Suspending from within text mode always works. The graphics mode problem is particularly annoying if the system enters auto-suspend on a low battery condition... -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI thermal panics ThinkPad 600X
Ruslan Ermilov wrote: > > --cWoXeonUoKmBZSoM > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Sun, Feb 16, 2003 at 10:24:57AM -0800, David O'Brien wrote: > > On Sun, Feb 16, 2003 at 07:55:49PM +0200, Ruslan Ermilov wrote: > > > > Don't cross post current and developers. > > > >=20 > > > > The developers charter says it's for internal management i.e. how we > > > > manage the project and not for discussing code issues. It's badly nam= > ed, > > > > we should have called it something like "members" or "admin". > > > >=20 > > > I must disagree. This message equally applies -current as well > > > as -developers; > >=20 > > It doesn't matter what you think -- this is our written down rules. > > Please obey them. If you want to target both lists, sent the message out > > twice -- once to each list. > >=20 > OK, I stand corrected. I should have written to src-committers@. No, src-committers wouldn't have helped you. That's src developers only, not public. Do not cross-post src-committers with -current either. If you really want to have a public discussion, post to -current, and then a second "hey, look over on -current" to src-developers@. Or do a bcc: src-developers or something. But not a To:/CC: cross post. 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 thermal panics ThinkPad 600X
[developers@ removed from CC list] On Sun, Feb 16, 2003 at 07:55:49PM +0200, Ruslan Ermilov wrote: > On Sun, Feb 16, 2003 at 11:50:46AM +, Paul Richards wrote: > > Don't cross post current and developers. > > > > The developers charter says it's for internal management i.e. how we > > manage the project and not for discussing code issues. It's badly named, > > we should have called it something like "members" or "admin". > > > I must disagree. This message equally applies -current as well > as -developers; I was interested in hearing from both -current > users and ACPI developers, and developers are not guaranteed to > be subscribed to the -current mailing list, are they? I think anybody using -current is expected to be subscribed to -current. I think it follows that if you develop for -current that you at least be on -current (the commit bit is optional, the mailinglist subscription is not :-) Something like that. No written-down rules AFAICT, but just plain common sense. -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI thermal panics ThinkPad 600X
On Sun, Feb 16, 2003 at 10:24:57AM -0800, David O'Brien wrote: > On Sun, Feb 16, 2003 at 07:55:49PM +0200, Ruslan Ermilov wrote: > > > Don't cross post current and developers. > > > > > > The developers charter says it's for internal management i.e. how we > > > manage the project and not for discussing code issues. It's badly named, > > > we should have called it something like "members" or "admin". > > > > > I must disagree. This message equally applies -current as well > > as -developers; > > It doesn't matter what you think -- this is our written down rules. > Please obey them. If you want to target both lists, sent the message out > twice -- once to each list. > OK, I stand corrected. I should have written to src-committers@. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg52493/pgp0.pgp Description: PGP signature
Re: ACPI thermal panics ThinkPad 600X
On Sun, Feb 16, 2003 at 07:55:49PM +0200, Ruslan Ermilov wrote: > > Don't cross post current and developers. > > > > The developers charter says it's for internal management i.e. how we > > manage the project and not for discussing code issues. It's badly named, > > we should have called it something like "members" or "admin". > > > I must disagree. This message equally applies -current as well > as -developers; It doesn't matter what you think -- this is our written down rules. Please obey them. If you want to target both lists, sent the message out twice -- once to each list. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI thermal panics ThinkPad 600X
On Sun, Feb 16, 2003 at 11:50:46AM +, Paul Richards wrote: > Don't cross post current and developers. > > The developers charter says it's for internal management i.e. how we > manage the project and not for discussing code issues. It's badly named, > we should have called it something like "members" or "admin". > I must disagree. This message equally applies -current as well as -developers; I was interested in hearing from both -current users and ACPI developers, and developers are not guaranteed to be subscribed to the -current mailing list, are they? > On Sat, 2003-02-15 at 02:49, Ruslan Ermilov wrote: > > ACPI thermal panics my ThinkPad 600X, is anyone > > interested in a crash dump analysis? > > > > > > Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg52478/pgp0.pgp Description: PGP signature
Re: ACPI thermal panics ThinkPad 600X
On Sun, Feb 16, 2003 at 05:45:42PM +0100, Wiktor Niesiobedzki wrote: > On Sat, Feb 15, 2003 at 11:16:12PM +0200, Ruslan Ermilov wrote: > > Me being dumb. Forgot to comment out the apm "disabled" hint > > in /boot/device.hints. Still, scary things happen after > > resuming from zzz(8). "ata1: resetting devices..." forever. > > > Did you happen to have: > options AUTO_EOI_1 > in your kernel configuration? > No. It says something about the temperature exceeding the system limit and barfs. I thought I'd better live with APM for the time being rather than with ACPI without thermal -- I noticed that the cooler isn't so active without it. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg52477/pgp0.pgp Description: PGP signature
Re: ACPI thermal panics ThinkPad 600X
On Sat, Feb 15, 2003 at 11:16:12PM +0200, Ruslan Ermilov wrote: > Me being dumb. Forgot to comment out the apm "disabled" hint > in /boot/device.hints. Still, scary things happen after > resuming from zzz(8). "ata1: resetting devices..." forever. > Did you happen to have: options AUTO_EOI_1 in your kernel configuration? Cheers, Wiktor Niesiobedzki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI thermal panics ThinkPad 600X
Don't cross post current and developers. The developers charter says it's for internal management i.e. how we manage the project and not for discussing code issues. It's badly named, we should have called it something like "members" or "admin". On Sat, 2003-02-15 at 02:49, Ruslan Ermilov wrote: > ACPI thermal panics my ThinkPad 600X, is anyone > interested in a crash dump analysis? > > > Cheers, -- Paul Richards <[EMAIL PROTECTED]> FreeBSD Services Ltd To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI thermal panics ThinkPad 600X
On Sat, Feb 15, 2003 at 06:41:29PM +0200, Ruslan Ermilov wrote: > On Sat, Feb 15, 2003 at 09:48:32AM -0500, Matthew N. Dodd wrote: > > On Sat, 15 Feb 2003, Dag-Erling Smorgrav wrote: > > > Unfortunately I can't afford a new laptop, so I'm stuck with my 600E. > > > > APM works fine on the 600E. The latest BIOS updates and new model main > > batteries seem to solve most of the battery complaints. > > > > My only outstanding issue is that I can't suspend if an application is > > holding /dev/dsp or /dev/audio open. > > > Hmm, is this on -CURRENT or -STABLE? I can't get apm(4) > working on 600X with -CURRENT; the module loading has some > problems and even if I compile apm statically, no /dev/apm* > entries are created. > Me being dumb. Forgot to comment out the apm "disabled" hint in /boot/device.hints. Still, scary things happen after resuming from zzz(8). "ata1: resetting devices..." forever. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg52406/pgp0.pgp Description: PGP signature
Re: ACPI thermal panics ThinkPad 600X
On Sat, Feb 15, 2003 at 09:48:32AM -0500, Matthew N. Dodd wrote: > On Sat, 15 Feb 2003, Dag-Erling Smorgrav wrote: > > Unfortunately I can't afford a new laptop, so I'm stuck with my 600E. > > APM works fine on the 600E. The latest BIOS updates and new model main > batteries seem to solve most of the battery complaints. > > My only outstanding issue is that I can't suspend if an application is > holding /dev/dsp or /dev/audio open. > Hmm, is this on -CURRENT or -STABLE? I can't get apm(4) working on 600X with -CURRENT; the module loading has some problems and even if I compile apm statically, no /dev/apm* entries are created. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg52394/pgp0.pgp Description: PGP signature
Re: ACPI thermal panics ThinkPad 600X
On Sat, 15 Feb 2003, Dag-Erling Smorgrav wrote: > Unfortunately I can't afford a new laptop, so I'm stuck with my 600E. APM works fine on the 600E. The latest BIOS updates and new model main batteries seem to solve most of the battery complaints. My only outstanding issue is that I can't suspend if an application is holding /dev/dsp or /dev/audio open. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI thermal panics ThinkPad 600X
Tom Rhodes <[EMAIL PROTECTED]> writes: > Ruslan Ermilov <[EMAIL PROTECTED]> wrote: > > ACPI thermal panics my ThinkPad 600X, [...] > ACPI gives me hell on my IBM Thinkpad A31, also. [...] This is just the last in a long series of Thinkpad f***ups. I concluded long ago that ThinkPads are nothing but trouble: buggy BIOSes; broken charge controllers that will ruin a brand new battery in weeks; keyboard / trackpoint assemblies with a one-year MTBF; broken APM and / or ACPI; docking stations that render the machine unusable until you reset and reconfigure the BIOS, etc. Unfortunately I can't afford a new laptop, so I'm stuck with my 600E. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI thermal panics ThinkPad 600X
On Sat, 15 Feb 2003 04:49:39 +0200 Ruslan Ermilov <[EMAIL PROTECTED]> wrote: > ACPI thermal panics my ThinkPad 600X, is anyone > interested in a crash dump analysis? > > ACPI gives me hell on my IBM Thinkpad A31, also. Yet since it does not crash anything I just leave it be waiting for the day when the ACPI hackers have time to fix it :) -- Tom Rhodes To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ACPI thermal panics ThinkPad 600X
ACPI thermal panics my ThinkPad 600X, is anyone interested in a crash dump analysis? Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg52371/pgp0.pgp Description: PGP signature
