Instability after recent -Syu and huge /var/log files (over 3gb)

nitindb · 2009-08-05 22:35:34

After a recent -Syu I noticed the huge size of certain my /var/log files. These files may have grown before the recent upgrade, but I only noticed them recently because my drive the root partition had reached its limit. I read that deleting these log files should not cause any problems so I promptly deleted three of the larger log files. After this, I have noticed that my system has gotten quite unstable (e.g. the system seems to randomly log out a couple of times a day). Another strange thing I noticed was that certain saved searches in Thunderbird had disappeared or gotten corrupted. My nautilus bookmarks had also disappeared.

Any help with the above would be much appreciated. I just want as stable a system as possible in the Arch Linux world. I would have left a bug report, but I have no idea what could be causing the issues.

Last edited by nitindb (2009-08-05 22:42:49)

peart · 2009-08-05 22:39:25

Did you check what was flooding your logs before deleting them? This kind of info would be useful...

nitindb · 2009-08-05 22:52:32

I really should have checked the log files but the partition had filled up completely, so my priority at the time was just getting back to being able to use Arch. I did check a log file and it mentioned an I/O error, but I am not 100% sure what exactly it was. The log files have not inflated to that level again, however. What should be my next move?

.:B:. · 2009-08-05 22:58:03

Make your logs rotate and compress. Should buy you some time, but in the meantime you should really check your logs for problems. If /var/log fills quickly no doubt there will be a clue popping up soon. Very soon.

Removed log files don't have anything to do with system instability. Check dmesg and the likes for pointers on that. Most - if not all - files in /var/log are recreated if they don't exist anymore.

Allan · 2009-08-05 23:56:44

Do you use fam?

nitindb · 2009-08-06 09:18:45

I'd installed fam right from the outset and it has been added to the daemons list in rc.conf

nitindb · 2009-08-06 09:21:36

@B

I typed dmesg in terminal and it threw up some lines. Should I post the results or any idea what to look out for?

Last edited by nitindb (2009-08-06 09:21:49)

Allan · 2009-08-06 09:25:12

nitindb wrote:

I'd installed fam right from the outset and it has been added to the daemons list in rc.conf

Sometimes fam spits out lots of errors and requires a restart. A bit late now, but looking at what was in the log files would be helpful...

.:B:. · 2009-08-06 12:42:57

Post dmesg output and /var/log/messages.

nitindb · 2009-08-06 13:50:23

Here is the output for dmesg:-

Initializing CPU#1
Calibrating delay using timer specific routine.. 4191.08 BogoMIPS (lpj=6982528)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
[Firmware Warn]: MTRR: CPU 1: SYSCFG[MtrrFixDramModEn] not cleared by BIOS, clearing this bit
x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
CPU1: AMD Turion(tm) 64 X2 Mobile Technology TL-62 stepping 02
Brought up 2 CPUs
System has AMD C1E enabled
Switch to broadcast mode on CPU1
Total of 2 processors activated (8381.73 BogoMIPS).
CPU0 attaching sched-domain:
 domain 0: span 0-1 level MC
  groups: 0 1
CPU1 attaching sched-domain:
 domain 0: span 0-1 level MC
  groups: 1 0
Switch to broadcast mode on CPU0
net_namespace: 1056 bytes
Booting paravirtualized kernel on bare hardware
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: MCFG configuration 0: base f8000000 segment 0 buses 0 - 63
PCI: MCFG area at f8000000 reserved in E820
PCI: Using MMCONFIG for extended config space
PCI: Using configuration type 1 for base access
bio: create slab <bio-0> at 0
ACPI: EC: Look up EC in DSDT
ACPI: BIOS _OSI(Linux) query ignored
ACPI: Interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: No dock devices found.
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:05.0: PME# supported from D0 D3hot D3cold
pci 0000:00:05.0: PME# disabled
pci 0000:00:06.0: PME# supported from D0 D3hot D3cold
pci 0000:00:06.0: PME# disabled
pci 0000:00:12.0: reg 10 io port: [0x6eb0-0x6eb7]
pci 0000:00:12.0: reg 14 io port: [0x6eb8-0x6ebb]
pci 0000:00:12.0: reg 18 io port: [0x6ec0-0x6ec7]
pci 0000:00:12.0: reg 1c io port: [0x6ec8-0x6ecb]
pci 0000:00:12.0: reg 20 io port: [0x6ee0-0x6eef]
pci 0000:00:12.0: reg 24 32bit mmio: [0xfec01000-0xfec013ff]
pci 0000:00:12.0: set SATA to AHCI mode
pci 0000:00:13.0: reg 10 32bit mmio: [0xffb00000-0xffb00fff]
pci 0000:00:13.1: reg 10 32bit mmio: [0xffb01000-0xffb01fff]
pci 0000:00:13.2: reg 10 32bit mmio: [0xffb02000-0xffb02fff]
pci 0000:00:13.3: reg 10 32bit mmio: [0xffb03000-0xffb03fff]
pci 0000:00:13.4: reg 10 32bit mmio: [0xffb04000-0xffb04fff]
pci 0000:00:13.5: reg 10 32bit mmio: [0xffa80000-0xffa800ff]
pci 0000:00:13.5: supports D1 D2
pci 0000:00:13.5: PME# supported from D0 D1 D2 D3hot
pci 0000:00:13.5: PME# disabled
pci 0000:00:14.0: reg 10 io port: [0x10c0-0x10cf]
pci 0000:00:14.1: reg 10 io port: [0x1f0-0x1f7]
pci 0000:00:14.1: reg 14 io port: [0x3f4-0x3f7]
pci 0000:00:14.1: reg 18 io port: [0x00-0x07]
pci 0000:00:14.1: reg 1c io port: [0x00-0x03]
pci 0000:00:14.1: reg 20 io port: [0xbfa0-0xbfaf]
pci 0000:00:14.2: reg 10 64bit mmio: [0xfebfc000-0xfebfffff]
pci 0000:00:14.2: PME# supported from D0 D3hot D3cold
pci 0000:00:14.2: PME# disabled
pci 0000:01:05.0: reg 10 64bit mmio: [0xe0000000-0xefffffff]
pci 0000:01:05.0: reg 18 64bit mmio: [0xfe9f0000-0xfe9fffff]
pci 0000:01:05.0: reg 20 io port: [0xee00-0xeeff]
pci 0000:01:05.0: reg 24 32bit mmio: [0xfea00000-0xfeafffff]
pci 0000:01:05.0: supports D1 D2
pci 0000:01:05.2: reg 10 64bit mmio: [0xfe9ec000-0xfe9effff]
pci 0000:00:01.0: bridge io port: [0xe000-0xefff]
pci 0000:00:01.0: bridge 32bit mmio: [0xfe900000-0xfeafffff]
pci 0000:00:01.0: bridge 64bit mmio pref: [0xe0000000-0xefffffff]
pci 0000:0b:00.0: reg 10 64bit mmio: [0xfe8fc000-0xfe8fffff]
pci 0000:0b:00.0: reg 18 64bit mmio: [0xf0000000-0xf00fffff]
pci 0000:0b:00.0: supports D1 D2
pci 0000:0b:00.0: PME# supported from D3hot D3cold
pci 0000:0b:00.0: PME# disabled
pci 0000:00:05.0: bridge 32bit mmio: [0xfe800000-0xfe8fffff]
pci 0000:00:05.0: bridge 64bit mmio pref: [0xf0000000-0xf00fffff]
pci 0000:00:06.0: bridge io port: [0xd000-0xdfff]
pci 0000:00:06.0: bridge 32bit mmio: [0xfe600000-0xfe7fffff]
pci 0000:00:06.0: bridge 64bit mmio pref: [0xf0100000-0xf03fffff]
pci 0000:03:07.0: reg 10 io port: [0xce00-0xceff]
pci 0000:03:07.0: reg 14 32bit mmio: [0xfe5ff300-0xfe5ff3ff]
pci 0000:03:07.0: supports D1 D2
pci 0000:03:07.0: PME# supported from D1 D2 D3hot D3cold
pci 0000:03:07.0: PME# disabled
pci 0000:03:09.0: reg 10 32bit mmio: [0xfe5ff800-0xfe5fffff]
pci 0000:03:09.0: supports D1 D2
pci 0000:03:09.0: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:09.0: PME# disabled
pci 0000:03:09.1: reg 10 32bit mmio: [0xfe5ff400-0xfe5ff4ff]
pci 0000:03:09.1: supports D1 D2
pci 0000:03:09.1: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:09.1: PME# disabled
pci 0000:03:09.2: reg 10 32bit mmio: [0xfe5ff500-0xfe5ff5ff]
pci 0000:03:09.2: supports D1 D2
pci 0000:03:09.2: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:09.2: PME# disabled
pci 0000:03:09.3: reg 10 32bit mmio: [0xfe5ff600-0xfe5ff6ff]
pci 0000:03:09.3: supports D1 D2
pci 0000:03:09.3: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:09.3: PME# disabled
pci 0000:03:09.4: reg 10 32bit mmio: [0xfe5ff700-0xfe5ff7ff]
pci 0000:03:09.4: supports D1 D2
pci 0000:03:09.4: PME# supported from D0 D1 D2 D3hot D3cold
pci 0000:03:09.4: PME# disabled
pci 0000:00:14.4: transparent bridge
pci 0000:00:14.4: bridge io port: [0xc000-0xcfff]
pci 0000:00:14.4: bridge 32bit mmio: [0xfe500000-0xfe5fffff]
pci_bus 0000:00: on NUMA node 0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIE._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 9 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 9 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 9 10 11) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled.
PCI: Using ACPI for IRQ routing
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
Switched to high resolution mode on CPU 0
Switched to high resolution mode on CPU 1
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 13 devices
ACPI: ACPI bus type pnp unregistered
system 00:01: iomem range 0xff800000-0xff8fffff has been reserved
system 00:01: iomem range 0xffc00000-0xffcfffff has been reserved
system 00:06: ioport range 0xc80-0xcff could not be reserved
system 00:09: iomem range 0xfed00000-0xfed003ff has been reserved
system 00:0a: ioport range 0x900-0x97f has been reserved
system 00:0a: ioport range 0x980-0x9ff has been reserved
system 00:0a: ioport range 0xa00-0xa7f has been reserved
system 00:0a: ioport range 0xa80-0xaff has been reserved
system 00:0a: ioport range 0xcb0-0xcff could not be reserved
system 00:0a: ioport range 0xd00-0xd7f has been reserved
system 00:0a: ioport range 0xd80-0xdff has been reserved
system 00:0a: ioport range 0xe00-0xe7f has been reserved
system 00:0a: ioport range 0xe80-0xeaf has been reserved
system 00:0a: ioport range 0xc6c-0xc6c has been reserved
system 00:0a: ioport range 0x4d0-0x4d1 has been reserved
system 00:0a: ioport range 0x1000-0x1005 has been reserved
system 00:0a: ioport range 0x1008-0x100f has been reserved
system 00:0a: ioport range 0xc00-0xc01 has been reserved
system 00:0a: ioport range 0xc14-0xc14 has been reserved
system 00:0a: ioport range 0xc50-0xc51 has been reserved
system 00:0a: ioport range 0xc52-0xc52 has been reserved
system 00:0a: ioport range 0xc6f-0xc6f has been reserved
system 00:0a: ioport range 0xcd0-0xcd1 has been reserved
system 00:0a: ioport range 0xcd4-0xcd5 has been reserved
system 00:0a: ioport range 0xcd6-0xcd7 has been reserved
system 00:0a: ioport range 0x40b-0x40b has been reserved
system 00:0a: ioport range 0x4d6-0x4d6 has been reserved
system 00:0b: ioport range 0xf400-0xf4fe has been reserved
system 00:0b: ioport range 0x1006-0x1007 has been reserved
system 00:0b: ioport range 0x100a-0x1059 could not be reserved
system 00:0b: ioport range 0x1080-0x10bf has been reserved
system 00:0b: ioport range 0x10c0-0x10df could not be reserved
system 00:0b: ioport range 0x1010-0x102f has been reserved
system 00:0b: ioport range 0x809-0x809 has been reserved
system 00:0c: iomem range 0x0-0x9efff could not be reserved
system 00:0c: iomem range 0x9f000-0x9ffff could not be reserved
system 00:0c: iomem range 0xc0000-0xcffff could not be reserved
system 00:0c: iomem range 0xe0000-0xfffff could not be reserved
system 00:0c: iomem range 0x100000-0x77e637ff could not be reserved
system 00:0c: iomem range 0x77e63800-0x77efffff has been reserved
system 00:0c: iomem range 0x77f00000-0x77ffffff has been reserved
system 00:0c: iomem range 0x77f00000-0x7fefffff could not be reserved
system 00:0c: iomem range 0xffe00000-0xffffffff has been reserved
system 00:0c: iomem range 0xfec00000-0xfec0ffff could not be reserved
system 00:0c: iomem range 0xfee00000-0xfee0ffff has been reserved
system 00:0c: iomem range 0xfee10000-0xfee103ff has been reserved
system 00:0c: iomem range 0xf8000000-0xfbffffff has been reserved
pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
pci 0000:00:01.0:   IO window: 0xe000-0xefff
pci 0000:00:01.0:   MEM window: 0xfe900000-0xfeafffff
pci 0000:00:01.0:   PREFETCH window: 0x000000e0000000-0x000000efffffff
pci 0000:00:05.0: PCI bridge, secondary bus 0000:0b
pci 0000:00:05.0:   IO window: disabled
pci 0000:00:05.0:   MEM window: 0xfe800000-0xfe8fffff
pci 0000:00:05.0:   PREFETCH window: 0x000000f0000000-0x000000f00fffff
pci 0000:00:06.0: PCI bridge, secondary bus 0000:0c
pci 0000:00:06.0:   IO window: 0xd000-0xdfff
pci 0000:00:06.0:   MEM window: 0xfe600000-0xfe7fffff
pci 0000:00:06.0:   PREFETCH window: 0x000000f0100000-0x000000f03fffff
pci 0000:00:14.4: PCI bridge, secondary bus 0000:03
pci 0000:00:14.4:   IO window: 0xc000-0xcfff
pci 0000:00:14.4:   MEM window: 0xfe500000-0xfe5fffff
pci 0000:00:14.4:   PREFETCH window: disabled
pci 0000:00:05.0: setting latency timer to 64
pci 0000:00:06.0: setting latency timer to 64
pci_bus 0000:00: resource 0 io:  [0x00-0xffff]
pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff]
pci_bus 0000:01: resource 0 io:  [0xe000-0xefff]
pci_bus 0000:01: resource 1 mem: [0xfe900000-0xfeafffff]
pci_bus 0000:01: resource 2 pref mem [0xe0000000-0xefffffff]
pci_bus 0000:0b: resource 1 mem: [0xfe800000-0xfe8fffff]
pci_bus 0000:0b: resource 2 pref mem [0xf0000000-0xf00fffff]
pci_bus 0000:0c: resource 0 io:  [0xd000-0xdfff]
pci_bus 0000:0c: resource 1 mem: [0xfe600000-0xfe7fffff]
pci_bus 0000:0c: resource 2 pref mem [0xf0100000-0xf03fffff]
pci_bus 0000:03: resource 0 io:  [0xc000-0xcfff]
pci_bus 0000:03: resource 1 mem: [0xfe500000-0xfe5fffff]
pci_bus 0000:03: resource 3 io:  [0x00-0xffff]
pci_bus 0000:03: resource 4 mem: [0x000000-0xffffffff]
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
NET: Registered protocol family 1
Unpacking initramfs...
Freeing initrd memory: 733k freed
Simple Boot Flag at 0x79 set to 0x1
apm: BIOS not found.
Scanning for low memory corruption every 60 seconds
audit: initializing netlink socket (disabled)
type=2000 audit(1249569298.436:1): initialized
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
msgmni has been set to 1733
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci 0000:01:05.0: Boot video device
pcieport-driver 0000:00:05.0: irq 24 for MSI/MSI-X
pcieport-driver 0000:00:05.0: setting latency timer to 64
pcieport-driver 0000:00:06.0: irq 25 for MSI/MSI-X
pcieport-driver 0000:00:06.0: setting latency timer to 64
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
input: Macintosh mouse button emulation as /devices/virtual/input/input0
PNP: PS/2 Controller [PNP0303:KBC,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
cpuidle: using governor ladder
cpuidle: using governor menu
TCP cubic registered
NET: Registered protocol family 17
Using IPI No-Shortcut mode
registered taskstats version 1
Initalizing network drop monitor service
Freeing unused kernel memory: 392k freed
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
SCSI subsystem initialized
libata version 3.00 loaded.
ahci 0000:00:12.0: version 3.0
ahci 0000:00:12.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
ahci 0000:00:12.0: controller can't do 64bit DMA, forcing 32bit
ahci 0000:00:12.0: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
ahci 0000:00:12.0: flags: ncq sntf ilck pm led clo pmp pio slum part 
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m1024@0xfec01000 port 0xfec01100 irq 22
ata2: SATA max UDMA/133 abar m1024@0xfec01000 port 0xfec01180 irq 22
ata3: SATA max UDMA/133 abar m1024@0xfec01000 port 0xfec01200 irq 22
ata4: SATA max UDMA/133 abar m1024@0xfec01000 port 0xfec01280 irq 22
pata_atiixp 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16
scsi4 : pata_atiixp
scsi5 : pata_atiixp
ata5: PATA max UDMA/100 cmd 0x1f0 ctl 0x3f6 bmdma 0xbfa0 irq 14
ata6: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xbfa8 irq 15
ata5.00: ATAPI: TSSTcorp DVD+/-RW TS-L632H, D300, max UDMA/33
ata5.00: configured for UDMA/33
ata2: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
ata3: SATA link down (SStatus 0 SControl 300)
ata1: softreset failed (device not ready)
ata1: failed due to HW bug, retry pmp=0
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-7: SAMSUNG HM120JI, YF100-15, max UDMA7
ata1.00: 234441648 sectors, multi 8: LBA48 NCQ (depth 31/32)
ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
ata1.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG HM120JI  YF10 PQ: 0 ANSI: 5
scsi 4:0:0:0: CD-ROM            TSSTcorp DVD+-RW TS-L632H D300 PQ: 0 ANSI: 5
Driver 'sd' needs updating - please use bus_type methods
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors: (120 GB/111 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 < sda5 sda6 sda7 sda8 > sda3
sd 0:0:0:0: [sda] Attached SCSI disk
Driver 'sr' needs updating - please use bus_type methods
sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 4:0:0:0: Attached scsi CD-ROM sr0
EXT3-fs: mounted filesystem with writeback data mode.
kjournald starting.  Commit interval 5 seconds
rtc_cmos 00:04: RTC can wake from S4
rtc_cmos 00:04: rtc core: registered rtc_cmos as rtc0
rtc0: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
udev: starting version 141
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
lib80211_crypt: registered algorithm 'TKIP'
wl: module license 'Mixed/Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
wl 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
wl 0000:0b:00.0: setting latency timer to 64
eth0 (wl): not using net_device_ops yet
eth0: Broadcom BCM4328 802.11 Wireless Controller 5.10.91.9
sd 0:0:0:0: Attached scsi generic sg0 type 0
sr 4:0:0:0: Attached scsi generic sg1 type 5
ACPI: processor limited to max C-state 1
processor ACPI_CPU:00: registered as cooling_device0
ACPI: Processor [CPU0] (supports 8 throttling states)
processor ACPI_CPU:01: registered as cooling_device1
ACPI: Processor [CPU1] (supports 8 throttling states)
thermal LNXTHERM:01: registered as thermal_zone0
ACPI: Thermal Zone [THM] (36 C)
ACPI: AC Adapter [AC] (on-line)
input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2
ACPI: Lid Switch [LID]
input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
ACPI: Power Button [PBTN]
input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input4
ACPI: Sleep Button [SBTN]
input: PC Speaker as /devices/platform/pcspkr/input/input5
ACPI: Battery Slot [BAT0] (battery present)
dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
acpi device:31: registered as cooling_device2
input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A03:00/device:2d/device:2e/input/input6
ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
k8temp 0000:00:18.3: Temperature readouts might be wrong - check erratum #141
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
ACPI: WMI: Mapper loaded
Linux agpgart interface v0.103
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
ricoh-mmc: Ricoh MMC Controller disabling driver
ricoh-mmc: Copyright(c) Philip Langdale
ricoh-mmc: Ricoh MMC controller found at 0000:03:09.2 [1180:0843] (rev 12)
ricoh-mmc: Controller is now disabled.
8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
8139cp 0000:03:07.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd 0000:00:13.5: PCI INT D -> GSI 20 (level, low) -> IRQ 20
ehci_hcd 0000:00:13.5: EHCI Host Controller
ehci_hcd 0000:00:13.5: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:13.5: applying AMD SB600/SB700 USB freeze workaround
ehci_hcd 0000:00:13.5: debug port 1
ehci_hcd 0000:00:13.5: irq 20, io mem 0xffa80000
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ehci_hcd 0000:00:13.5: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 10 ports detected
ohci_hcd 0000:00:13.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ohci_hcd 0000:00:13.0: OHCI Host Controller
ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:13.0: irq 16, io mem 0xffb00000
ohci1394 0000:03:09.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
piix4_smbus 0000:00:14.0: SMBus Host Controller at 0x10c0, revision 0
ohci_hcd 0000:00:13.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
ohci_hcd 0000:00:13.1: OHCI Host Controller
ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:13.1: irq 17, io mem 0xffb01000
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[23]  MMIO=[fe5ff800-fe5fffff]  Max Packet=[2048]  IR/IT contexts=[4/4]
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ohci_hcd 0000:00:13.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ohci_hcd 0000:00:13.2: OHCI Host Controller
ohci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 4
ohci_hcd 0000:00:13.2: irq 18, io mem 0xffb02000
8139too Fast Ethernet driver 0.9.28
8139too 0000:03:07.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
eth1: RealTek RTL8139 at 0xf8ad2300, 00:15:c5:86:ec:da, IRQ 20
eth1:  Identified 8139 chip type 'RTL-8100B/8139D'
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
ohci_hcd 0000:00:13.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17
ohci_hcd 0000:00:13.3: OHCI Host Controller
ohci_hcd 0000:00:13.3: new USB bus registered, assigned bus number 5
ohci_hcd 0000:00:13.3: irq 17, io mem 0xffb03000
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pci 0000:03:09.1: SDHCI controller found [1180:0822] (rev 22)
sdhci-pci 0000:03:09.1: PCI INT B -> GSI 22 (level, low) -> IRQ 22
Registered led device: mmc0::
mmc0: SDHCI controller on PCI [0000:03:09.1] using DMA
usb usb5: configuration #1 chosen from 1 choice
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 2 ports detected
HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:14.2/input/input7
input: PS/2 Mouse as /devices/platform/i8042/serio2/input/input8
input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio2/input/input9
usb 2-1: new full speed USB device using ohci_hcd and address 2
input: HDA ATI SB Line In at Ext Rear Jack as /devices/pci0000:00/0000:00:14.2/input/input10
input: HDA ATI SB Mic at Ext Front Jack as /devices/pci0000:00/0000:00:14.2/input/input11
input: HDA ATI SB Mic at Ext Rear Jack as /devices/pci0000:00/0000:00:14.2/input/input12
input: HDA ATI SB Speaker at Ext Rear Jack as /devices/pci0000:00/0000:00:14.2/input/input13
input: HDA ATI SB Speaker at Ext Rear Jack as /devices/pci0000:00/0000:00:14.2/input/input14
input: HDA ATI SB Speaker at Ext Rear Jack as /devices/pci0000:00/0000:00:14.2/input/input15
input: HDA ATI SB Speaker at Ext Rear Jack as /devices/pci0000:00/0000:00:14.2/input/input16
input: HDA ATI SB HP Out at Ext Front Jack as /devices/pci0000:00/0000:00:14.2/input/input17
HDA Intel 0000:01:05.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
ohci_hcd 0000:00:13.4: PCI INT C -> GSI 18 (level, low) -> IRQ 18
ohci_hcd 0000:00:13.4: OHCI Host Controller
ohci_hcd 0000:00:13.4: new USB bus registered, assigned bus number 6
ohci_hcd 0000:00:13.4: irq 18, io mem 0xffb04000
usb usb6: configuration #1 chosen from 1 choice
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 2 ports detected
usb 2-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hiddev
usb 3-1: new low speed USB device using ohci_hcd and address 2
usb 3-1: configuration #1 chosen from 1 choice
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[424fc0003b1bbc70]
usbcore: registered new interface driver snd-usb-audio
input: Elan USB Phone as /devices/pci0000:00/0000:00:13.0/usb2/2-1/2-1:1.3/input/input18
generic-usb 0003:04F3:0A01.0001: input,hidraw0: USB HID v1.00 Device [Elan USB Phone] on usb-0000:00:13.0-1/input3
input: Kingsis Peripherals Evoluent VerticalMouse 2 as /devices/pci0000:00/0000:00:13.1/usb3/3-1/3-1:1.0/input/input19
generic-usb 0003:2222:3061.0002: input,hidraw1: USB HID v1.10 Mouse [Kingsis Peripherals Evoluent VerticalMouse 2] on usb-0000:00:13.1-1/input0
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
EXT3 FS on sda3, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda7, internal journal
EXT3-fs: mounted filesystem with writeback data mode.
Adding 1461872k swap on /dev/sda6.  Priority:-1 extents:1 across:1461872k 
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
pci 0000:01:05.0: PCI INT B -> GSI 19 (level, low) -> IRQ 19
eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
[drm] Initialized drm 1.1.0 20060810
[drm] Initialized radeon 1.30.0 20080528 for 0000:01:05.0 on minor 0
[drm] Setting GART location based on new memory map
[drm] Loading RS690/RS740 Microcode
[drm] Num pipes: 1
[drm] writeback test succeeded in 1 usecs
eth0: no IPv6 routers present
eth1: no IPv6 routers present
fuse init (API version 7.11)
Too big adjustment 32
Too big adjustment 32
process `skype' is using obsolete setsockopt SO_BSDCOMPAT
Too big adjustment 32
Too big adjustment 32
Too big adjustment 32
Too big adjustment 32
Too big adjustment 32
Too big adjustment 32
Too big adjustment 32
Too big adjustment 32
Too big adjustment 32
Too big adjustment 32
Too big adjustment 32
Too big adjustment 32
Too big adjustment 32
Too big adjustment 32
Too big adjustment 32
Clocksource tsc unstable (delta = 4398044019157 ns)
mmc0: new high speed SD card at address 1234
mmcblk0: mmc0:1234 SD02G 1.90 GiB 
 mmcblk0: p1
CE: hpet increasing min_delta_ns to 15000 nsec
mmc0: card 1234 removed

.:B:. · 2009-08-06 13:52:13

Looks more or less normal. You should monitor /var/log for log files that grow abnormally fast and check those.

nitindb · 2009-08-06 13:55:05

The output for /var/messages seems to be too large for this forum platform to handle and can't see any option for adding attachments?

.:B:. · 2009-08-06 14:45:54

Pastebin...

nitindb · 2009-08-06 18:24:01

Well here is my pastebin entry for the /var/messages contents:-

http://paste.pocoo.org/show/132897/

The 4th of August was when problems started occuring. Today, however, I have not yet noticed any issues apart from skype which occasionally won't shut down.

nitindb · 2009-08-07 10:22:10

I just had another random crash a few moments ago. I was on Firefox and had perhaps thunderbirdand tomboy open, when suddenly screen went blank and it took me back to the gdm login screen. Had to login again. I checked my /var/log/messages file and noticed the following error at the time when the crash happened:-

gnome-session[2363]: WARNING: Detected that screensaver has left the bus
gdm-binary[2168]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0

Does this shed any light?

Last edited by nitindb (2009-08-07 14:58:30)

fredo696 · 2009-08-20 10:24:16

hi all

just experienced the same problem today

found that the daemon/errors/everything log files were huge (3gb each) so my 15gb / partition was full.

couldn't open 'em so just deleted them & rebooted

now I have rebooted and their size is normal, no "error flood" noticed so far...

sand_man · 2009-08-20 23:06:01

fredo696 wrote:

hi all
just experienced the same problem today
found that the daemon/errors/everything log files were huge (3gb each) so my 15gb / partition was full.
couldn't open 'em so just deleted them & rebooted
now I have rebooted and their size is normal, no "error flood" noticed so far...

I was reading this thread and I was about the reply saying, this is going to happen again eventually lol.

Anyway, was there absolutely no way you could have read the logs? Maybe next time move them to another partition or external device so it no longer clogs your /var. If you want to want to fix the problem you really need to see whats in those logs.

nitindb · 2009-09-01 09:05:16

I've had this huge /var/log files issue come up again. This time, however, I did not delete the huge files, but instead tried to find out what error message was causing this to happen. Initially I tried opening the file using nano or gedit, but neither worked because the file was just too huge (1.8GB in size). After some googling I found the following command which allowed me to view the last 10000 lines of the log file and created a new text file displaying the results:-

sudo tail -n 10000 /var/log/everything.log.1 > huge_everything_log.txt

In the newly created huge_everything_log.txt file I found the following error message on Aug 23, that kept repeating itself and thus causing the log file to grow to 1.8GB in size:-

famd[2151]: fd 4 message length 1347375956 bytes exceeds max of 4136

So now that I've tracked the error message, hopefully someone might have an idea as to what is going on? For the time being I have deleted these log files (there are 3 them which were exactly 1.8GB in size). I read somewhere that i should restart /etc/rc.d/fam?

Allan · 2009-09-01 09:10:09

I have searched and searched for this issue and I can not find a patch to fix it...

The only workaround I can find is to restart the fam daemon once the problem hits.

theapodan · 2009-09-02 05:34:11

You could also replace fam with gamin, although that doesn't resolve the deeper problem with fam.

Last edited by theapodan (2009-09-02 05:35:08)

sand_man · 2009-09-02 07:12:12

I was gonna say, I haven't had this happen to me before. Then I realised I already use gamin.
I don't see the difference between the two. I suppose it's just a matter of, use what works for you. In this case, fam doesn't work.

shining · 2009-09-02 08:28:48

There was a discussion about fam vs gamin in arch-dev-public a few months ago.
Everyone was for removing fam and replacing it by gamin. But it did not happen yet.

http://mailman.archlinux.org/pipermail/ … 11934.html

Every normal file manager should use inotify by itself and not depend
on fam/gamin for that. What fam adds is the ability to monitor remote
file systems IIRC, gamin does not add anything (of course it adds the
basic functionality to file managers which don't have inotify
support).

are you in one of the following two cases :
1) using a filesystem with no inotify support
2) needing the ability to monitor remote file systems

otherwise, why are you using fam/gamin at all ?

if you are in one of the two cases, the message below might help in choosing between fam and gamin

Aha, here's a nice summary of the current fam/gamin status by JGC:
http://bugs.archlinux.org/task/14623#comment45188
> I think this would be the right time to switch to gamin:
> - fam is dead upstream, gamin isn't
> - fam needs a lot of patches to build, gamin builds out of the box
> - fam uses (patched) dnotify, a shitty API that has been replaced by inotify, which is used by gamin
> - fam uses a daemon, gamin works from the library linked to the application
> - fam needs a daemon on the NFS server, gamin does polling (just like fam without dnotify support), this is actually a disadvantage of gamin, if the fam way would work correctly

Edit : and I guess this current thread is another big point in favor of removing fam

Last edited by shining (2009-09-02 08:30:03)

broch · 2009-09-02 12:22:18

actually I don't have fam/gamin installed and this works but, you will have to compile few packages on your own (ABS). Not many though.

takedown · 2009-09-02 13:05:41

+1 for gamin 8)

Arch Linux

#1 2009-08-05 22:35:34

Instability after recent -Syu and huge /var/log files (over 3gb)

#2 2009-08-05 22:39:25

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#3 2009-08-05 22:52:32

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#4 2009-08-05 22:58:03

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#5 2009-08-05 23:56:44

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#6 2009-08-06 09:18:45

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#7 2009-08-06 09:21:36

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#8 2009-08-06 09:25:12

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#9 2009-08-06 12:42:57

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#10 2009-08-06 13:50:23

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#11 2009-08-06 13:52:13

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#12 2009-08-06 13:55:05

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#13 2009-08-06 14:45:54

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#14 2009-08-06 18:24:01

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#15 2009-08-07 10:22:10

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#16 2009-08-20 10:24:16

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#17 2009-08-20 23:06:01

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#18 2009-09-01 09:05:16

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#19 2009-09-01 09:10:09

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#20 2009-09-02 05:34:11

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#21 2009-09-02 07:12:12

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#22 2009-09-02 08:28:48

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#23 2009-09-02 12:22:18

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

#24 2009-09-02 13:05:41

Re: Instability after recent -Syu and huge /var/log files (over 3gb)

Board footer