log fills harddisk

[Member luker]

Hi forum,

there’s an error in my antiX-box that I don’t know yet how to track down.
Prerequisite:
Watch TV in VLC or MythTV throuhg my DVB-S card, which is a Pinnacle PCTV Sat.
Symptom:
TV runs fine as long as user doen’t try to do anything. But log files grow to such sizes that the harddisk gets filled up. The whole system becomes slower. Starting X doesn’t work after next boot.

What I have found:
The files

/var/log/messages
/var/log/syslog
/var/log/kern.log

each grow over a dozen GB. They all show large amounts of this error line

Oct 13 18:12:13 hostname kernel: [  494.255061] bt878(0): irq PPERR risc_pc=7b769208
Oct 13 18:12:13 hostname kernel: [  494.255073] bt878(0): irq PPERR risc_pc=7b769008
Oct 13 18:12:13 hostname kernel: [  494.255092] bt878(0): irq PPERR risc_pc=7b769010
Oct 13 18:12:13 hostname kernel: [  494.255109] bt878(0): irq PPERR risc_pc=7b769010
Oct 13 18:12:13 hostname kernel: [  494.255127] bt878(0): irq PPERR risc_pc=7b769010
Oct 13 18:12:13 hostname kernel: [  494.255147] bt878(0): irq PPERR risc_pc=7b769010

The last number in each line runs from 008 to 208 in steps of 2 and then wraps around.

The error line contains a bt878, so the connection to the PCTV Sat is given.

What is an irq PPERR risc pc=<hexnumber>?
How do I get rid of it?

[Anonymous]

Helpful

Up

0

::

don’t know yet how to track down

I would websearch, using the following query:

solved error bt878 irq PPERR risc_pc

or

error bt878 irq PPERR risc_pc

or

kernel error bt878 irq PPERR risc_pc

[Member Xecure]

Helpful

Up

0

::

Solving the problem will be difficult. Search in the net “bt878″(0): “irq PPERR risc_pc=” and there are many posts with your problem from 2006 to today.

If nothing stops working and you just don’t want the error to stop being reported, try adding this to your boot options entry:
pci=noaer
If I am not mistaken, this stops reporting PCIE errors.
Adding Boot parameters to Grub on installed system: https://antixlinuxfan.miraheze.org/wiki/Boot_Parameters#Making_boot_parameters_permanent_for_grub

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Moderator christophe]

Helpful

Up

0

::

I ran into this problem before:

What I have found:
The files

/var/log/messages
/var/log/syslog
/var/log/kern.log

each grow over a dozen GB.

It happened to me running pcsxr. How I solved it is more of a “work-around” solution, but it works.
I set up a cron job to zero-out those 3 offending log files every 10 minutes. In case you are interested, this is how to set it up:

1. In a terminal, run:
sudo crontab -u root -e
This edits root’s crontab. This opens your default cli text editor.

2. Add the following lines to the end of this file:

*/10 * * * * clear > /var/log/kern.log
*/10 * * * * clear > /var/log/messages
*/10 * * * * clear > /var/log/syslog

These lines set it to wipe out those pesky logs every ten minutes. I don’t ever even notice it.

(This is easy to reverse, by erasing the commands from the root crontab, if you ever need to do so.)

I have them set up now. It just works for me. 🙂

HTH

• This reply was modified 2 years, 6 months ago by christophe.

Attachments:

1. 

   screenshot1.jpg
   

confirmed antiX frugaler, since 2019

[Author]

Posts