Looks fixed to me.
** Changed in: acpid (Ubuntu)
Status: Triaged => Fix Released
--
Log output far too verbose
https://bugs.launchpad.net/bugs/31512
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubun
Please can someone confirm if this has been fixed in Intrepid testing?
In theory this patch should have been merged from Debian, however it is
not specifically mentioned in the package changelog.
--
Log output far too verbose
https://bugs.launchpad.net/bugs/31512
You received this bug notificatio
To disable acpid logging, edit /etc/default/acpid and add "-l /dev/null" to the
end of the OPTIONS string. On my system, the line looks like this with the
change:
OPTIONS="-s /var/run/acpid.socket -l /dev/null"
I am running hardy amd64. Once in a while, /var/log/apcid gets so large
that it qui
** Changed in: acpid (Debian)
Status: New => Fix Released
--
Log output far too verbose
https://bugs.launchpad.net/bugs/31512
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
What does that mean, "add -l /dev/null" to the command line"? What is
the full command to disable acpid logging? I'm getting an event in the
log every second, but I can't figure out how to disable it.
sudo acpid -l /dev/nulljust returns: acpid: can't open
/proc/acpi/event: Device or resource
** Changed in: acpid (Debian)
Status: Unknown => New
--
Log output far too verbose
https://bugs.launchpad.net/bugs/31512
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
This bug is quite old (and the comments shifted to offtopic).
acpid 1.0.6 uses syslog logging now (Hardy has 1.0.4) and there's a similar bug
report in Debian, which I'll link.
** Changed in: acpid (Ubuntu)
Importance: Low => Medium
Status: New => Triaged
** Bug watch added: Debian Bug
William,
It should work without the hdparm -B 254 workaround. If it doesn't then
you have some other program running that is also accessing the disk
(suggestions have been thunderbird amongst other things). This is one
of those annoying bugs where you have to squash all of them before the
proble
Toshiba Satellite Pro 4600 notebook produces the following, when running
on AC power (and the battery is 100% charged, and has been full for
hours):
.
[Fri Nov 23 23:54:30 2007] received event "battery BAT1 0080 0001"
[Fri Nov 23 23:54:30 2007] notifying client 4319[107:115]
[Fri Nov 2
btrace howto :
http://ubuntuforums.org/showpost.php?p=3722850&postcount=374
--
Log output far too verbose
https://bugs.launchpad.net/bugs/31512
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
regarding my previous post about btrace :
https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/31512/comments/10
You need to first do this :
sudo mount -t debugfs none_debug /sys/kernel/debug
--
Log output far too verbose
https://bugs.launchpad.net/bugs/31512
You received this bug notification b
Maybe btrace will show you whether acpid logging is indeed too verbose.
sudo aptitude install blktrace
sudo btrace /dev/sda
When I ran btrace myself I got this : "/sys/kernel/debug does not appear to be
a debug filesystem"
That's probably because I have encrypted my disk during the installation
Further correction -- lm-profiler is not reliable for this, as it causes
log writes itself. :-/ It does seem that acpid may be the main
culprit.
--
Log output far too verbose
https://bugs.launchpad.net/bugs/31512
You received this bug notification because you are a member of Ubuntu
Bugs, which
This is not what is causing #59695 (recently duped to #17216) for me. I
have no problem with excessive log writes from acpid, although there may
be some other log that is causing the problem. I verified this tailing
acpid while running lm-profiler.
-b
--
Log output far too verbose
https://bugs
Partial correction -- It has started logging more often, after
unplugging and plugging in the battery, but seems to log mostly around
once every 1-2 minutes. However, that doesn't fully account for the
writes I get from reiserfs/0 (or 1) every 30 seconds (I.e., I'm still
saying that acpid is not t
What did lm-profiler claim was touching the hard disk? That's probably
the easiest way to work out what's causing the disk to unpark in each
case, as it seems that various programs can cause the effect of bug
59695. There should probably be some kind of review of installed
services to see what do
I can confirm the excessive logging on a Samsung X20 running Feisty.
On battery power a battery event gets logged to /var/log/acpid every 30-40s.
Disabling the logging with -l /dev/null in /etc/default/acpid gets rid of that.
Please note that for every battery event also /etc/acpi/power.sh is exe
Yes, I see these in the log, but only if I plug/unplug the AC adapter.
There are no regularly scheduled battery events in the log, no matter
whether I run the laptop on mains or battery.
--
Log output far too verbose
https://bugs.launchpad.net/bugs/31512
You received this bug notification because
Are you seeing battery events at all in that log? Seems strange that
they wouldn't appear.
You are right that it could be any process that's causing the writes,
though specifically it has to be something that writes regularly with
intervals greater than the hard disk park time. If several proces
I cannot confirm this on an Asus G1S-A1 laptop (Gutsy, x86-64).
/var/log/acpid accumulates less than 3k per week on this model, despite
intensive use.
However, I do see bug 59695 regardless.
I think that we have to be careful with pinpointing a single source for
the hard drive problems. If it is
This is causing bug 59695 (the infamous laptop-killing bug), or rather,
is the actual cause of the drive problem.
On my laptop, ACPID gets a battery event roughly every 15 seconds, each
of these produces a write to the log file.
Laptop hard drives seem to be set up for bursty I/O (a reasonably
as
21 matches
Mail list logo
