Mailing List Archive: MythTV: Users

HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't)

Index | Next | Previous | View Threaded

krt at krt

Jul 9, 2012, 2:22 PM

Post #1 of 18 (1104 views)
Permalink

HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't)

Hi,

I recently re-installed Mythbuntu 12.04 64bit on a machine that was running
Mythbuntu 11.10 32-bit PAE (without this issue)

Everything seems to be working - it records, plays back, does everything OK
- except that sometimes the box reboots itself?!

There doesn't seem to be any particular trigger that I can work out - last
night it crashed while recording as soon as I stopped watching something.
It also looks like it crashed overnight while recording, but not playing
anything. Of course it's also been up for sometimes two days without a hitch.

I'm not really sure what to do here. I am using the Mythbuntu installed
nVidia blob driver, and I have tried changing this to the driver with
updates rather than the non-updated driver. This hasn't made any difference
to stability - I mention it only because previously I used the nVidia driver
installed manually (rather than the Ubuntu package).

Typically I would believe this was caused by bad RAM or suchlike - but that
seems a stretch given the 32bit OS never exhibited any stability problems at
all.

So - I really don't know what to do! The WAF is plummeting (if the
Tour-de-france highlights weren't repeated a few hours after the
crash-mid-schedule I would have really been in the dog house.)

Please, I would like some help getting to the bottom of this.

Could it be the drivers for the two SAA7146 DVB cards?
Maybe the RAM has coincidentally come loose? (I will check this today.)

Any sage advice much appreciated.

thanks,
-kt

PS> Here's some of the dmesg

root [at] mediabo:/var/log# cat dmesg
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.2.0-26-generic (buildd [at] bats) (gcc version
4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #41-Ubuntu SMP Thu Jun 14 17:49:24
UTC 2012 (Ubuntu 3.2.0-26.41-generic 3.2.19)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic
root=UUID=ca427392-c930-4000-aadf-2de2fa630313 ro quiet splash vt.handoff=7
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009e800 (usable)
[ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 0000000070000000 (usable)
[ 0.000000] BIOS-e820: 0000000070000000 - 0000000080000000 (reserved)
[ 0.000000] BIOS-e820: 0000000080000000 - 00000000afef0000 (usable)
[ 0.000000] BIOS-e820: 00000000afef0000 - 00000000afef3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000afef3000 - 00000000aff00000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000e2000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 0000000240000000 (usable)
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] DMI 2.4 present.
[ 0.000000] DMI: Gigabyte Technology Co., Ltd.
GA-E7AUM-DS2H/GA-E7AUM-DS2H, BIOS F3a 02/04/2009
[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000
(usable) ==> (reserved)
[ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
[ 0.000000] No AGP bridge found

... snip 8><

[ 0.441964] pci_bus 0000:02: resource 2 [mem 0xc0000000-0xdfffffff 64bit
pref]
[ 0.442003] NET: Registered protocol family 2
[ 0.442201] IP route cache hash table entries: 262144 (order: 9, 2097152
bytes)
[ 0.443458] TCP established hash table entries: 524288 (order: 11,
8388608 bytes)
[ 0.448034] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 0.448303] TCP: Hash tables configured (established 524288 bind 65536)
[ 0.448305] TCP reno registered
[ 0.448320] UDP hash table entries: 4096 (order: 5, 131072 bytes)
[ 0.448367] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
[ 0.448502] NET: Registered protocol family 1
[ 0.448715] ACPI: PCI Interrupt Link [AUBA] enabled at IRQ 23
[ 0.448731] pci 0000:00:04.0: PCI INT A -> Link[AUBA] -> GSI 23 (level,
low) -> IRQ 23
[ 0.448753] pci 0000:00:04.0: PCI INT A disabled
[ 0.448855] ACPI: PCI Interrupt Link [AUB2] enabled at IRQ 22
[ 0.448862] pci 0000:00:04.1: PCI INT B -> Link[AUB2] -> GSI 22 (level,
low) -> IRQ 22
[ 0.448882] pci 0000:00:04.1: PCI INT B disabled
[ 0.448980] ACPI: PCI Interrupt Link [AU1B] enabled at IRQ 21
[ 0.448986] pci 0000:00:06.0: PCI INT A -> Link[AU1B] -> GSI 21 (level,
low) -> IRQ 21
[ 0.449002] pci 0000:00:06.0: PCI INT A disabled
[ 0.449104] ACPI: PCI Interrupt Link [AU2B] enabled at IRQ 20
[ 0.449110] pci 0000:00:06.1: PCI INT B -> Link[AU2B] -> GSI 20 (level,
low) -> IRQ 20
[ 0.449128] pci 0000:00:06.1: PCI INT B disabled
[ 0.449168] pci 0000:02:00.0: Boot video device
[ 0.449171] PCI: CLS 32 bytes, default 64
[ 0.449173] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 0.449175] Placing 64MB software IO TLB between ffff8800abee6000 -
ffff8800afee6000
[ 0.449177] software IO TLB at phys 0xabee6000 - 0xafee6000
[ 0.449543] audit: initializing netlink socket (disabled)
[ 0.449551] type=2000 audit(1341821523.444:1): initialized
[ 0.490113] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.538202] VFS: Disk quotas dquot_6.5.2
[ 0.538258] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.538733] fuse init (API version 7.17)
[ 0.538815] msgmni has been set to 14929
[ 0.539369] Block layer SCSI generic (bsg) driver version 0.4 loaded
(major 253)
[ 0.539422] io scheduler noop registered
[ 0.539424] io scheduler deadline registered
[ 0.539452] io scheduler cfq registered (default)
[ 0.539571] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.539590] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 0.539637] intel_idle: MWAIT substates: 0x22220
[ 0.539639] intel_idle: does not run on family 6 model 23
[ 0.539724] input: Power Button as
/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
[ 0.539728] ACPI: Power Button [PWRB]
[ 0.539790] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[ 0.539792] ACPI: Power Button [PWRF]
[ 0.539890] Marking TSC unstable due to TSC halts in idle
[ 0.539907] ACPI: acpi_idle registered with cpuidle
[ 0.542580] ERST: Table is not found!
[ 0.542582] GHES: HEST is not enabled!
[ 0.542646] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 0.562999] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.618976] Freeing initrd memory: 13852k freed
[ 0.784545] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[ 0.820238] Linux agpgart interface v0.103
[ 0.821555] brd: module loaded
[ 0.822228] loop: module loaded
[ 0.822328] ahci 0000:00:0b.0: version 3.0
[ 0.822437] ACPI: PCI Interrupt Link [APSI] enabled at IRQ 23
[ 0.822441] ahci 0000:00:0b.0: PCI INT A -> Link[APSI] -> GSI 23 (level,
low) -> IRQ 23
[ 0.822499] ahci 0000:00:0b.0: irq 40 for MSI/MSI-X
[ 0.822504] ahci 0000:00:0b.0: controller can't do PMP, turning off CAP_PMP
[ 0.822547] ahci 0000:00:0b.0: AHCI 0001.0200 32 slots 6 ports 3 Gbps
0x3f impl SATA mode
[ 0.822550] ahci 0000:00:0b.0: flags: 64bit ncq sntf led pio slum part boh
[ 0.822553] ahci 0000:00:0b.0: setting latency timer to 64
[ 0.823260] scsi0 : ahci
[ 0.823366] scsi1 : ahci
[ 0.823462] scsi2 : ahci
[ 0.823555] scsi3 : ahci
[ 0.823649] scsi4 : ahci
[ 0.823746] scsi5 : ahci
[ 0.823849] ata1: SATA max UDMA/133 abar m8192 [at] 0xe418400 port 0xe4184100
irq 40
[ 0.823851] ata2: SATA max UDMA/133 abar m8192 [at] 0xe418400 port 0xe4184180
irq 40
[ 0.823853] ata3: SATA max UDMA/133 abar m8192 [at] 0xe418400 port 0xe4184200
irq 40
[ 0.823855] ata4: SATA max UDMA/133 abar m8192 [at] 0xe418400 port 0xe4184280
irq 40
[ 0.823857] ata5: SATA max UDMA/133 abar m8192 [at] 0xe418400 port 0xe4184300
irq 40
[ 0.823859] ata6: SATA max UDMA/133 abar m8192 [at] 0xe418400 port 0xe4184380
irq 40
[ 0.824211] Fixed MDIO Bus: probed
[ 0.824228] tun: Universal TUN/TAP device driver, 1.6
[ 0.824229] tun: (C) 1999-2004 Max Krasnyansky <maxk [at] qualcomm>
[ 0.824269] PPP generic driver version 2.4.2
[ 0.824358] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.824371] ehci_hcd 0000:00:04.1: PCI INT B -> Link[AUB2] -> GSI 22
(level, low) -> IRQ 22
[ 0.824381] ehci_hcd 0000:00:04.1: setting latency timer to 64
[ 0.824383] ehci_hcd 0000:00:04.1: EHCI Host Controller
[ 0.824426] ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus
number 1
[ 0.824452] ehci_hcd 0000:00:04.1: debug port 1
[ 0.824459] ehci_hcd 0000:00:04.1: cache line size of 32 is not supported
[ 0.824475] ehci_hcd 0000:00:04.1: irq 22, io mem 0xe4186000
[ 0.836016] ehci_hcd 0000:00:04.1: USB 2.0 started, EHCI 1.00
[ 0.836156] hub 1-0:1.0: USB hub found
[ 0.836163] hub 1-0:1.0: 6 ports detected
[ 0.836221] ehci_hcd 0000:00:06.1: PCI INT B -> Link[AU2B] -> GSI 20
(level, low) -> IRQ 20
[ 0.836230] ehci_hcd 0000:00:06.1: setting latency timer to 64
[ 0.836232] ehci_hcd 0000:00:06.1: EHCI Host Controller
[ 0.836270] ehci_hcd 0000:00:06.1: new USB bus registered, assigned bus
number 2
[ 0.836284] ehci_hcd 0000:00:06.1: debug port 1
[ 0.836291] ehci_hcd 0000:00:06.1: cache line size of 32 is not supported
[ 0.836303] ehci_hcd 0000:00:06.1: irq 20, io mem 0xe418b000
[ 0.848017] ehci_hcd 0000:00:06.1: USB 2.0 started, EHCI 1.00
[ 0.848136] hub 2-0:1.0: USB hub found
[ 0.848141] hub 2-0:1.0: 6 ports detected
[ 0.848203] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.848216] ohci_hcd 0000:00:04.0: PCI INT A -> Link[AUBA] -> GSI 23
(level, low) -> IRQ 23
[ 0.848225] ohci_hcd 0000:00:04.0: setting latency timer to 64
[ 0.848227] ohci_hcd 0000:00:04.0: OHCI Host Controller
[ 0.848266] ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus
number 3
[ 0.848283] ohci_hcd 0000:00:04.0: irq 23, io mem 0xe418c000
[ 0.906094] hub 3-0:1.0: USB hub found
[ 0.906099] hub 3-0:1.0: 6 ports detected
[ 0.906153] ohci_hcd 0000:00:06.0: PCI INT A -> Link[AU1B] -> GSI 21
(level, low) -> IRQ 21
[ 0.906162] ohci_hcd 0000:00:06.0: setting latency timer to 64
[ 0.906164] ohci_hcd 0000:00:06.0: OHCI Host Controller
[ 0.906207] ohci_hcd 0000:00:06.0: new USB bus registered, assigned bus
number 4
[ 0.906227] ohci_hcd 0000:00:06.0: irq 21, io mem 0xe418a000
[ 0.962094] hub 4-0:1.0: USB hub found
[ 0.962098] hub 4-0:1.0: 6 ports detected
[ 0.962150] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.962193] usbcore: registered new interface driver libusual
[ 0.962223] i8042: PNP: No PS/2 controller found. Probing ports directly.
[ 0.994929] i8042: Failed to disable AUX port, but continuing anyway...
Is this a SiS?
[ 0.994931] i8042: If AUX port is really absent please use the
'i8042.noaux' option
[ 1.140021] ata2: SATA link down (SStatus 0 SControl 300)
[ 1.140039] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.140903] ata1.00: ATA-8: WDC WD20EARX-008FB0, 51.0AB51, max UDMA/133
[ 1.140906] ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 1.141797] ata1.00: configured for UDMA/133
[ 1.141963] scsi 0:0:0:0: Direct-Access ATA WDC WD20EARX-008
51.0 PQ: 0 ANSI: 5
[ 1.142154] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1.142153] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00
TB/1.81 TiB)
[ 1.142155] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 1.142200] sd 0:0:0:0: [sda] Write Protect is off
[ 1.142203] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.142225] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[ 1.144020] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 1.144033] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.144043] ata5: SATA link down (SStatus 0 SControl 300)
[ 1.144053] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1.144835] ata4.00: ATA-8: WDC WD20EARX-008FB0, 51.0AB51, max UDMA/133
[ 1.144839] ata4.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 1.145636] ata4.00: configured for UDMA/133
[ 1.148026] ata3.00: ATAPI: HL-DT-ST BDDVDRW GGC-H20L, 1.03, max UDMA/133
[ 1.148034] usb 1-3: new high-speed USB device number 2 using ehci_hcd
[ 1.153443] ata3.00: configured for UDMA/133
[ 1.172667] ata6.00: ATA-8: ST31500341AS, CC1H, max UDMA/133
[ 1.172670] ata6.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 1.182799] sda: sda1 sda2 < sda5 >
[ 1.183128] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.214562] ata6.00: configured for UDMA/133
[ 1.244113] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.244222] mousedev: PS/2 mouse device common for all mice
[ 1.244358] rtc_cmos 00:05: RTC can wake from S4
[ 1.244544] rtc_cmos 00:05: rtc core: registered rtc_cmos as rtc0
[ 1.244592] rtc0: alarms up to one year, y3k, 242 bytes nvram, hpet irqs
[ 1.244651] device-mapper: uevent: version 1.0.3
[ 1.244713] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised:
dm-devel [at] redhat
[ 1.244809] cpuidle: using governor ladder
[ 1.244952] cpuidle: using governor menu
[ 1.244954] EFI Variables Facility v0.08 2004-May-17
[ 1.245139] TCP cubic registered
[ 1.245228] NET: Registered protocol family 10
[ 1.245594] NET: Registered protocol family 17
[ 1.245597] Registering the dns_resolver key type
[ 1.245756] PM: Hibernation image not present or could not be loaded.
[ 1.245773] registered taskstats version 1
[ 1.272098] scsi 2:0:0:0: CD-ROM HL-DT-ST BDDVDRW GGC-H20L
1.03 PQ: 0 ANSI: 5
[ 1.275214] Magic number: 4:695:219
[ 1.275388] rtc_cmos 00:05: setting system clock to 2012-07-09 08:12:05
UTC (1341821525)
[ 1.277803] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 1.277805] EDD information not available.
[ 1.291209] Initializing USB Mass Storage driver...
[ 1.291396] scsi6 : usb-storage 1-3:1.0
[ 1.291451] usbcore: registered new interface driver usb-storage
[ 1.291452] USB Mass Storage support registered.
[ 1.377756] sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2
cdda tray
[ 1.377760] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 1.377914] sr 2:0:0:0: Attached scsi CD-ROM sr0
[ 1.378012] sr 2:0:0:0: Attached scsi generic sg1 type 5
[ 1.378201] scsi 3:0:0:0: Direct-Access ATA WDC WD20EARX-008
51.0 PQ: 0 ANSI: 5
[ 1.378310] sd 3:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00
TB/1.81 TiB)
[ 1.378312] sd 3:0:0:0: [sdb] 4096-byte physical blocks
[ 1.378341] sd 3:0:0:0: Attached scsi generic sg2 type 0
[ 1.378371] sd 3:0:0:0: [sdb] Write Protect is off
[ 1.378374] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[ 1.378428] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[ 1.378597] scsi 5:0:0:0: Direct-Access ATA ST31500341AS CC1H PQ:
0 ANSI: 5
[ 1.378704] sd 5:0:0:0: [sdc] 2930277168 512-byte logical blocks: (1.50
TB/1.36 TiB)
[ 1.378742] sd 5:0:0:0: [sdc] Write Protect is off
[ 1.378745] sd 5:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 1.378755] sd 5:0:0:0: Attached scsi generic sg3 type 0
[ 1.378762] sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled,
doesn't support DPO or FUA
[ 1.394811] sdc: sdc1
[ 1.395029] sd 5:0:0:0: [sdc] Attached SCSI disk
[ 1.572042] usb 2-3: new high-speed USB device number 3 using ehci_hcd
[ 1.705793] scsi7 : usb-storage 2-3:1.0
[ 1.809385] sdb: sdb1
[ 1.809751] sd 3:0:0:0: [sdb] Attached SCSI disk
[ 1.811103] Freeing unused kernel memory: 920k freed
[ 1.811304] Write protecting the kernel read-only data: 12288k
[ 1.815792] Freeing unused kernel memory: 1616k freed
[ 1.819424] Freeing unused kernel memory: 1200k freed
[ 1.834108] udevd[113]: starting version 175
[ 1.861749] forcedeth: Reverse Engineered nForce ethernet driver. Version
0.64.
[ 1.861934] ACPI: PCI Interrupt Link [APCH] enabled at IRQ 22
[ 1.861941] forcedeth 0000:00:0a.0: PCI INT A -> Link[APCH] -> GSI 22
(level, low) -> IRQ 22
[ 1.861946] forcedeth 0000:00:0a.0: setting latency timer to 64
[ 1.910035] ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
[ 1.910052] firewire_ohci 0000:01:0e.0: PCI INT A -> Link[APC3] -> GSI 18
(level, low) -> IRQ 18
[ 1.911619] Floppy drive(s): fd0 is 1.44M
[ 1.925260] forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x732 @ 3, addr
00:1f:d0:ad:f0:38
[ 1.925264] forcedeth 0000:00:0a.0: highdma csum pwrctl gbit lnktim msi
desc-v3
[ 1.929243] FDC 0 is a post-1991 82077
[ 1.968142] firewire_ohci: Added fw-ohci device 0000:01:0e.0, OHCI v1.10,
4 IR + 8 IT contexts, quirks 0x2
[ 1.996055] CE: hpet increased min_delta_ns to 11520 nsec
[ 2.012038] usb 4-2: new full-speed USB device number 2 using ohci_hcd
[ 2.059203] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[ 2.059206] EXT4-fs (sda1): write access will be enabled during recovery
[ 2.229088] hub 4-2:1.0: USB hub found
[ 2.232040] hub 4-2:1.0: 3 ports detected
[ 2.289775] scsi 6:0:0:0: Direct-Access Seagate Desktop 0130
PQ: 0 ANSI: 4
[ 2.290309] sd 6:0:0:0: Attached scsi generic sg4 type 0
[ 2.290912] sd 6:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00
TB/1.81 TiB)
[ 2.291642] sd 6:0:0:0: [sdd] Write Protect is off
[ 2.291645] sd 6:0:0:0: [sdd] Mode Sense: 2f 08 00 00
[ 2.292643] sd 6:0:0:0: [sdd] No Caching mode page present
[ 2.292645] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[ 2.295640] sd 6:0:0:0: [sdd] No Caching mode page present
[ 2.295642] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[ 2.311130] EXT4-fs (sda1): orphan cleanup on readonly fs
[ 2.311138] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 24903688
[ 2.311163] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 24903685
[ 2.311170] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 24903684
[ 2.311176] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 24903683
[ 2.311183] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced
inode 24903682
[ 2.311188] EXT4-fs (sda1): 5 orphan inodes deleted
[ 2.311189] EXT4-fs (sda1): recovery complete
[ 2.321666] sdd: sdd1
[ 2.325656] sd 6:0:0:0: [sdd] No Caching mode page present
[ 2.325659] sd 6:0:0:0: [sdd] Assuming drive cache: write through
[ 2.325662] sd 6:0:0:0: [sdd] Attached SCSI disk
[ 2.472133] firewire_core: created device fw0: GUID 00ab1b3e00001fd0, S400
[ 2.552050] usb 3-4: new low-speed USB device number 2 using ohci_hcd
[ 2.586726] EXT4-fs (sda1): mounted filesystem with ordered data mode.
Opts: (null)
[ 2.706630] scsi 7:0:0:0: Direct-Access Seagate Desktop 0130
PQ: 0 ANSI: 4
[ 2.707482] sd 7:0:0:0: Attached scsi generic sg5 type 0
[ 2.708110] sd 7:0:0:0: [sde] 3907029168 512-byte logical blocks: (2.00
TB/1.81 TiB)
[ 2.709480] sd 7:0:0:0: [sde] Write Protect is off
[ 2.709483] sd 7:0:0:0: [sde] Mode Sense: 2f 08 00 00
[ 2.710479] sd 7:0:0:0: [sde] No Caching mode page present
[ 2.710482] sd 7:0:0:0: [sde] Assuming drive cache: write through
[ 2.713480] sd 7:0:0:0: [sde] No Caching mode page present
[ 2.713483] sd 7:0:0:0: [sde] Assuming drive cache: write through
[ 2.742005] sde: sde1
[ 2.745474] sd 7:0:0:0: [sde] No Caching mode page present
[ 2.745477] sd 7:0:0:0: [sde] Assuming drive cache: write through
[ 2.745480] sd 7:0:0:0: [sde] Attached SCSI disk
[ 2.830055] usb 4-2.2: new full-speed USB device number 3 using ohci_hcd
[ 3.042041] usb 4-2.3: new full-speed USB device number 4 using ohci_hcd
[ 13.416937] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 13.463121] udevd[447]: starting version 175
[ 13.499010] i2c i2c-0: nForce2 SMBus adapter at 0x1c00
[ 13.499015] ACPI: resource nForce2_smbus [io 0x1c80-0x1cbf] conflicts
with ACPI region SM00 [io 0x1c80-0x1c85]
[ 13.499017] ACPI: If an ACPI driver is available for this device, you
should use it instead of the native driver
[ 13.500181] lp: driver loaded but no devices found
[ 13.510499] saa7146: register extension 'budget_ci dvb'
[ 13.510712] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
[ 13.510729] budget_ci dvb 0000:01:05.0: PCI INT A -> Link[APC1] -> GSI 16
(level, low) -> IRQ 16
[ 13.510793] saa7146: found saa7146 @ mem ffffc90000c7e000 (revision 1,
irq 16) (0x13c2,0x1011)
[ 13.510795] saa7146 (0): dma buffer size 192512
[ 13.510797] DVB: registering new adapter (TT-Budget/WinTV-NOVA-T PCI)
[ 13.514685] IR NEC protocol handler initialized
[ 13.522024] IR RC5(x) protocol handler initialized
[ 13.529318] IR RC6 protocol handler initialized
[ 13.530530] Linux video capture interface: v2.00
[ 13.534493] type=1400 audit(1341821537.754:2): apparmor="STATUS"
operation="profile_load" name="/sbin/dhclient" pid=523 comm="apparmor_parser"
[ 13.534813] type=1400 audit(1341821537.754:3): apparmor="STATUS"
operation="profile_load"
name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=523
comm="apparmor_parser"
[ 13.534999] type=1400 audit(1341821537.754:4): apparmor="STATUS"
operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script"
pid=523 comm="apparmor_parser"
[ 13.535826] saa7146: register extension 'budget_av'
[ 13.537107] IR JVC protocol handler initialized
[ 13.538190] type=1400 audit(1341821537.758:5): apparmor="STATUS"
operation="profile_load" name="/usr/sbin/ntpd" pid=552 comm="apparmor_parser"
[ 13.543191] IR Sony protocol handler initialized
[ 13.543879] nvidia: module license 'NVIDIA' taints kernel.
[ 13.543885] Disabling lock debugging due to kernel taint
[ 13.545034] adapter has MAC addr = 00:d0:5c:22:15:f5
[ 13.558551] IR MCE Keyboard/mouse protocol handler initialized
[ 13.568574] lirc_dev: IR Remote Control driver registered, major 250
[ 13.568744] IR LIRC bridge handler initialized
[ 13.580580] Adding 7862268k swap on /dev/sda5. Priority:-1 extents:1
across:7862268k
[ 13.608140] Registered IR keymap rc-hauppauge
[ 13.608249] input: Budget-CI dvb ir receiver saa7146 (0) as
/devices/pci0000:00/0000:00:09.0/0000:01:05.0/rc/rc0/input2
[ 13.608927] rc0: Budget-CI dvb ir receiver saa7146 (0) as
/devices/pci0000:00/0000:00:09.0/0000:01:05.0/rc/rc0
[ 13.611360] ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 21
[ 13.611368] snd_hda_intel 0000:00:08.0: PCI INT A -> Link[AAZA] -> GSI 21
(level, low) -> IRQ 21
[ 13.611370] hda_intel: Disabling MSI
[ 13.611405] snd_hda_intel 0000:00:08.0: setting latency timer to 64
[ 13.616765] wmi: Mapper loaded
[ 13.616890] DVB: registering adapter 0 frontend 0 (Philips TDA10045H
DVB-T)...
[ 13.617340] ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
[ 13.617359] budget_av 0000:01:06.0: PCI INT A -> Link[APC2] -> GSI 17
(level, low) -> IRQ 17
[ 13.617411] saa7146: found saa7146 @ mem ffffc900037e4000 (revision 1,
irq 17) (0x1894,0x003a)
[ 13.617414] saa7146 (1): dma buffer size 192512
[ 13.617416] DVB: registering new adapter (Satelco EasyWatch DVB-T)
[ 13.620332] input: iMON Panel, Knob and Mouse(15c2:ffdc) as
/devices/pci0000:00/0000:00:04.0/usb3/3-4/3-4:1.0/input/input3
[ 13.626553] [Firmware Bug]: ACPI(IGPU) defines _DOD but not _DOS
[ 13.626741] input: Video Bus as
/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:09/LNXVIDEO:00/input/input4
[ 13.626867] ACPI: Video Device [IGPU] (multi-head: yes rom: no post: no)
[ 13.627275] input: Logitech Logitech BT Mini-Receiver as
/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.2/4-2.2:1.0/input/input5
[ 13.627376] generic-usb 0003:046D:C71E.0001: input,hidraw0: USB HID v1.11
Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.2/input0
[ 13.630098] usbcore: registered new interface driver usbhid
[ 13.630100] usbhid: USB HID core driver
[ 13.640052] imon 3-4:1.0: 0xffdc iMON LCD, MCE IR (id 0x9f)
[ 13.653484] adapter failed MAC signature check
[ 13.653486] encoded MAC from EEPROM was
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff
[ 13.664025] Registered IR keymap rc-imon-mce
[ 13.664114] input: iMON Remote (15c2:ffdc) as
/devices/pci0000:00/0000:00:04.0/usb3/3-4/3-4:1.0/rc/rc1/input6
[ 13.664228] rc1: iMON Remote (15c2:ffdc) as
/devices/pci0000:00/0000:00:04.0/usb3/3-4/3-4:1.0/rc/rc1
[ 13.680130] imon 3-4:1.0: iMON device (15c2:ffdc, intf0) on usb<3:2>
initialized
[ 13.680152] usbcore: registered new interface driver imon
[ 13.795984] input: Logitech Logitech BT Mini-Receiver as
/devices/pci0000:00/0000:00:06.0/usb4/4-2/4-2.3/4-2.3:1.0/input/input7
[ 13.796530] logitech 0003:046D:C71F.0002: input,hiddev0,hidraw1: USB HID
v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:06.0-2.3/input0
[ 13.924501] budget_av: KNC1-1: MAC addr = 00:09:d6:6d:4a:8a
[ 14.028267] DVB: registering adapter 1 frontend 0 (Philips TDA10046H
DVB-T)...
[ 14.028526] budget_av: ci interface initialised
[ 14.102016] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ 14.242717] hda_codec: ALC889A: BIOS auto-probing.
[ 14.373375] SGI XFS with ACLs, security attributes, realtime, large
block/inode numbers, no debug enabled
[ 14.375007] SGI XFS Quota Management subsystem
[ 14.375549] XFS (sdb1): Mounting Filesystem
[ 14.860940] XFS (sdb1): Starting recovery (logdev: internal)
[ 14.935732] XFS (sdb1): Ending recovery (logdev: internal)
[ 15.113113] kjournald starting. Commit interval 5 seconds
[ 15.113341] EXT3-fs (sdc1): warning: maximal mount count reached, running
e2fsck is recommended
[ 15.113809] EXT3-fs (sdc1): using internal journal
[ 15.113811] EXT3-fs (sdc1): recovery complete
[ 15.114186] EXT3-fs (sdc1): mounted filesystem with ordered data mode
[ 15.132153] XFS (sdd1): Mounting Filesystem
[ 15.444562] XFS (sdd1): Starting recovery (logdev: internal)
[ 15.573546] XFS (sdd1): Ending recovery (logdev: internal)
[ 15.592864] XFS (sde1): Mounting Filesystem
[ 15.640141] input: HDA NVidia Line as
/devices/pci0000:00/0000:00:08.0/sound/card0/input8
[ 15.640252] input: HDA NVidia Front Mic as
/devices/pci0000:00/0000:00:08.0/sound/card0/input9
[ 15.640329] input: HDA NVidia Rear Mic as
/devices/pci0000:00/0000:00:08.0/sound/card0/input10
[ 15.640416] input: HDA NVidia Front Headphone as
/devices/pci0000:00/0000:00:08.0/sound/card0/input11
[ 15.640491] input: HDA NVidia Line-Out Side as
/devices/pci0000:00/0000:00:08.0/sound/card0/input12
[ 15.640565] input: HDA NVidia Line-Out CLFE as
/devices/pci0000:00/0000:00:08.0/sound/card0/input13
[ 15.640637] input: HDA NVidia Line-Out Surround as
/devices/pci0000:00/0000:00:08.0/sound/card0/input14
[ 15.640709] input: HDA NVidia Line-Out Front as
/devices/pci0000:00/0000:00:08.0/sound/card0/input15
[ 15.641135] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 15.641325] ACPI: PCI Interrupt Link [APMU] enabled at IRQ 20
[ 15.641333] nvidia 0000:00:03.5: PCI INT B -> Link[APMU] -> GSI 20
(level, low) -> IRQ 20
[ 15.641477] ACPI: PCI Interrupt Link [AIGP] enabled at IRQ 23
[ 15.641480] nvidia 0000:02:00.0: PCI INT A -> Link[AIGP] -> GSI 23
(level, low) -> IRQ 23
[ 15.641486] nvidia 0000:02:00.0: setting latency timer to 64
[ 15.641491] vgaarb: device changed decodes:
PCI:0000:02:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[ 15.642080] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 295.49 Mon
Apr 30 23:46:33 PDT 2012
[ 15.832122] XFS (sde1): Starting recovery (logdev: internal)
[ 15.908380] XFS (sde1): Ending recovery (logdev: internal)
[ 15.928906] init: failsafe main process (1069) killed by TERM signal
[ 15.993711] type=1400 audit(1341821540.214:6): apparmor="STATUS"
operation="profile_load"
name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=1153
comm="apparmor_parser"
[ 15.993766] type=1400 audit(1341821540.214:7): apparmor="STATUS"
operation="profile_load" name="/usr/sbin/mysqld" pid=1155 comm="apparmor_parser"
[ 15.994097] type=1400 audit(1341821540.214:8): apparmor="STATUS"
operation="profile_replace" name="/sbin/dhclient" pid=1154
comm="apparmor_parser"
[ 15.994421] type=1400 audit(1341821540.214:9): apparmor="STATUS"
operation="profile_replace"
name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1154
comm="apparmor_parser"
[ 15.994602] type=1400 audit(1341821540.214:10): apparmor="STATUS"
operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script"
pid=1154 comm="apparmor_parser"
[ 15.995678] type=1400 audit(1341821540.214:11): apparmor="STATUS"
operation="profile_replace" name="/usr/sbin/ntpd" pid=1156
comm="apparmor_parser"
[ 16.013974] forcedeth 0000:00:0a.0: irq 41 for MSI/MSI-X
[ 16.077986] lirc_imon: module is from the staging directory, the quality
is unknown, you have been warned.
[ 16.078276] lirc_imon: Driver for SoundGraph iMON MultiMedia IR/Display, v0.8
[ 16.078340] usbcore: registered new interface driver lirc_imon
[ 16.093043] imon 3-4:1.0: Looks like you're trying to use an IR protocol
this device does not support
[ 16.093047] imon 3-4:1.0: Unsupported IR protocol specified, overriding
to iMON IR protocol

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

thomas at mashos

Jul 9, 2012, 2:53 PM

Post #2 of 18 (1019 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

On Mon, Jul 9, 2012 at 2:22 PM, Kingsley Turner <krt [at] krt> wrote:
> Hi,
>
> I recently re-installed Mythbuntu 12.04 64bit on a machine that was running
> Mythbuntu 11.10 32-bit PAE (without this issue)
<snip>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users

Are you sure the machine is crashing and not just X? Did you tell it
to automatically install updates, and maybe it's rebooting because of
that?

Thanks,

Thomas Mashos
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

krt at krt

Jul 9, 2012, 3:23 PM

Post #3 of 18 (1015 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

On 10/07/12 07:53, Thomas Mashos wrote:
> On Mon, Jul 9, 2012 at 2:22 PM, Kingsley Turner <krt [at] krt> wrote:
>> Hi,
>>
>> I recently re-installed Mythbuntu 12.04 64bit on a machine that was running
>> Mythbuntu 11.10 32-bit PAE (without this issue)
> <snip>
> Are you sure the machine is crashing and not just X? Did you tell it to
> automatically install updates, and maybe it's rebooting because of that?

Yeah, I'm 100% sure it's not just X - I saw the BIOS boot screen come up,
and the uptime is back to a few hours (or so) when I don't.

Auto-install updates is turned off (according to
/etc/apt/apt.conf.d/50unattended-upgrades)

thanks,
-kt

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

jyavenard at gmail

Jul 9, 2012, 5:52 PM

Post #4 of 18 (1011 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

without a kernel backtrace of what's likely to be a kernel panic, it
will be pretty hard to know why it's rebooting

This used to happen on one of my box with a 9400M nvidia chipset.

Do you have another linux box running ?
Set netconsole on the machine that crash and listen to it on the remote machine.

Something like this:
http://www.cyberciti.biz/tips/linux-netconsole-log-management-tutorial.html

Now the bad news is that if it's actually a kernel crash, probably
none of us here will be able to do anything about it ...
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

yiannividalis at hotmail

Jul 9, 2012, 10:26 PM

Post #5 of 18 (1006 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

> Date: Tue, 10 Jul 2012 08:23:48 +1000
> From: krt [at] krt
> To: mythtv-users [at] mythtv
> Subject: Re: [mythtv-users] HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't)
>
> On 10/07/12 07:53, Thomas Mashos wrote:
> > On Mon, Jul 9, 2012 at 2:22 PM, Kingsley Turner <krt [at] krt> wrote:
> >> Hi,
> >>
> >> I recently re-installed Mythbuntu 12.04 64bit on a machine that was running
> >> Mythbuntu 11.10 32-bit PAE (without this issue)
> > <snip>
> > Are you sure the machine is crashing and not just X? Did you tell it to
> > automatically install updates, and maybe it's rebooting because of that?
>
> Yeah, I'm 100% sure it's not just X - I saw the BIOS boot screen come up,
> and the uptime is back to a few hours (or so) when I don't.
>
> Auto-install updates is turned off (according to
> /etc/apt/apt.conf.d/50unattended-upgrades)
>
> thanks,
> -kt
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://www.mythtv.org/mailman/listinfo/mythtv-users

----------------------------------------

I don't know if it applies to your case, but I used to have reboots (on opensuse 11.4) on Athlon II, x86_64 while I was using EIT on a DVB-S mantis card. I disabled it since I don't use it (I added a disecq switch and the card is not usable since) and I didn't have a single reboot since.

Yianni.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

peper03 at yahoo

Jul 10, 2012, 1:18 PM

Post #6 of 18 (993 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

On 09/07/12 23:22, Kingsley Turner wrote:
> Hi,
>
> I recently re-installed Mythbuntu 12.04 64bit on a machine that was
> running Mythbuntu 11.10 32-bit PAE (without this issue)
>
> Everything seems to be working - it records, plays back, does
> everything OK - except that sometimes the box reboots itself?!
>
> There doesn't seem to be any particular trigger that I can work out -
> last night it crashed while recording as soon as I stopped watching
> something. It also looks like it crashed overnight while recording,
> but not playing anything. Of course it's also been up for sometimes
> two days without a hitch.
>
> I'm not really sure what to do here. I am using the Mythbuntu
> installed nVidia blob driver, and I have tried changing this to the
> driver with updates rather than the non-updated driver. This hasn't
> made any difference to stability - I mention it only because
> previously I used the nVidia driver installed manually (rather than
> the Ubuntu package).
>
> Typically I would believe this was caused by bad RAM or suchlike - but
> that seems a stretch given the 32bit OS never exhibited any stability
> problems at all.

I doubt this is your problem but have you tried wiggling the power
cables in the case to see if there's a bad connection? I just finished
building my system, case and all, and had a similar problem to you. The
box would just suddenly reset for no apparent reason. I eventually
tracked it down to a very slightly loose connection on the power cable
to the motherboard. Pin 14 (the green wire) is normally shorted by the
motherboard to ground to tell the power supply to turn on and provide
full power. Because the connection on this wire was a bit loose, it
would stop being shorted to ground and the power supply would turn off.
Invariably it turned back on again immediately (no idea why) making it
look more like a reset than power down. After I squeezed the connector
a bit, the problem went away.

As I say, if you haven't touched the hardware, only the software,
there's no reason why you should suddenly have this problem but if all
else fails, it may be worth checking.

Richard.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

krt at krt

Jul 10, 2012, 2:48 PM

Post #7 of 18 (987 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

krt at krt

Jul 10, 2012, 9:35 PM

Post #8 of 18 (983 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

On 11/07/12 06:18, Richard wrote:
> On 09/07/12 23:22, Kingsley Turner wrote:
>>
>> I recently re-installed Mythbuntu 12.04 64bit on a machine that was
>> running Mythbuntu 11.10 32-bit PAE (without this issue)
>>
>> Everything seems to be working - it records, plays back, does everything
>> OK - except that sometimes the box reboots itself?!
>>
> I doubt this is your problem but have you tried wiggling the power cables
> in the case to see if there's a bad connection? I just finished building
> my system, case and all, and had a similar problem to you. The box would
> just suddenly reset for no apparent reason. I eventually tracked it down
> to a very slightly loose connection on the power cable to the
> motherboard. Pin 14 (the green wire) is normally shorted by the
> motherboard to ground to tell the power supply to turn on and provide full
> power. Because the connection on this wire was a bit loose, it would stop
> being shorted to ground and the power supply would turn off. Invariably
> it turned back on again immediately (no idea why) making it look more like
> a reset than power down. After I squeezed the connector a bit, the
> problem went away.
>
> As I say, if you haven't touched the hardware, only the software, there's
> no reason why you should suddenly have this problem but if all else fails,
> it may be worth checking.
>

I did replace 2 hard disks when I re-installed. So maybe something became
loose.
I've just checked the plug connections, pulled, clean && re-seated the RAM,
vacuumed the dust off all the filters & fans...

Fingers crossed that was it.

thanks for the help,
-kt

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

krt at krt

Aug 4, 2012, 11:44 PM

Post #9 of 18 (884 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

pat at flying-gecko

Aug 8, 2012, 11:44 AM

Post #10 of 18 (860 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

On Sun, Aug 05, 2012 at 04:44:54PM +1000, Kingsley Turner wrote:
> Hello again,
>
> I think I've determined the culprit - sort of.
>
> It wasn't the power supply... $200 wasted.
>
> I used to run xscreensaver with the opengl photo-panning applette.
> I was sitting around cogitating, watching the screensaver pan over a
> photo, and the box rebooted.
> I checked the schedule - it wasn't recording at the time.
>
> So I disabled xscreensaver - and thereby "fixed" the reboots.
>
> It's now been up for nearly 48 hours, which hasn't happened for
> weeks - it got to the stage where it would last 2-3 hours at most.
>
> So of xscreensaver is causing the box to reboot (As JWZ says, there
> is nothing in xscreensaver that should cause a problem with X, (let
> alone a reboot)) - this means it's probably the nVidia blob right?
>
> I'm using a motherboard with an on-board nvidia 9400 GPU. The
> drivers are the Ubuntu module shipped ones "+updates".
>
> Maybe I should change to the latest manual nVidia drivers ?
>
> What do you think ?

I doubt the nVidia blob is the issue (might be, check the nVidia forums
for the issue), unless you just updated it and then the problem started.

CLEAN YOUR CPU HEATSINK - Make sure CPU fan(s)/airflow are good.

I had a box doing something similar. I replaced the power supply, and was
pulling my hair out trying to figure out why it was randomly rebooting.
I installed the sensors package to monitor CPU temps and found it was
overheating (getting to the ACPI BIOS critical temp).

My symptoms: seemingly random shutdowns/reboots with a decreasing time
between them. Didn't seem to matter if I was watching a show or the
backend was idle. I later found it would reboot during a CPU intensive
application (transcoding for instance) every time.

I also noticed the "upgrade" from Ubuntu 11 to 12 revived my automatic
shutdown command for myth backend so the backend would shutdown after
the timeout - I had disabled that (at least I thought I had) before the
upgrade. After cleaning the CPU heatsink and disabling the auto backend
idle shutdown the box has been rock solid.

--
,-----------------------------------------------------------------------------.
> Patrick Ouellette | I have been all things unholy. If God can work <
> pat(at)flying-gecko.net | through me, he can work through anyone. <
> Amateur Radio: NE4PO | -- Francis of Assisi <
`-----------------------------------------------------------------------------'
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

bhaskins at chartermi

Aug 8, 2012, 5:24 PM

Post #11 of 18 (855 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

On 08/08/2012 02:44 PM, Patrick Ouellette wrote:
> On Sun, Aug 05, 2012 at 04:44:54PM +1000, Kingsley Turner wrote:
>> Hello again,
>>
>> I think I've determined the culprit - sort of.
>>
>> It wasn't the power supply... $200 wasted.
>>
>> I used to run xscreensaver with the opengl photo-panning applette.
>> I was sitting around cogitating, watching the screensaver pan over a
>> photo, and the box rebooted.
>> I checked the schedule - it wasn't recording at the time.
>>
>> So I disabled xscreensaver - and thereby "fixed" the reboots.
>>
>> It's now been up for nearly 48 hours, which hasn't happened for
>> weeks - it got to the stage where it would last 2-3 hours at most.
>>
>> So of xscreensaver is causing the box to reboot (As JWZ says, there
>> is nothing in xscreensaver that should cause a problem with X, (let
>> alone a reboot)) - this means it's probably the nVidia blob right?
>>
>> I'm using a motherboard with an on-board nvidia 9400 GPU. The
>> drivers are the Ubuntu module shipped ones "+updates".
>>
>> Maybe I should change to the latest manual nVidia drivers ?
>>
>> What do you think ?
> I doubt the nVidia blob is the issue (might be, check the nVidia forums
> for the issue), unless you just updated it and then the problem started.
>
> CLEAN YOUR CPU HEATSINK - Make sure CPU fan(s)/airflow are good.
>
> I had a box doing something similar. I replaced the power supply, and was
> pulling my hair out trying to figure out why it was randomly rebooting.
> I installed the sensors package to monitor CPU temps and found it was
> overheating (getting to the ACPI BIOS critical temp).
>
> My symptoms: seemingly random shutdowns/reboots with a decreasing time
> between them.
I have seen this several times and the problem was that the small
capacitors surrounding the CPU were dying.

If the tops of the aluminum cans are even starting to pop up
( they should be slightly depressed ) or if there is any sign of
leakage they are on their way out.

If you have a choice, such as when buying a new motherboard,
always go for the solid caps.
> Didn't seem to matter if I was watching a show or the
> backend was idle. I later found it would reboot during a CPU intensive
> application (transcoding for instance) every time.
>
> I also noticed the "upgrade" from Ubuntu 11 to 12 revived my automatic
> shutdown command for myth backend so the backend would shutdown after
> the timeout - I had disabled that (at least I thought I had) before the
> upgrade. After cleaning the CPU heatsink and disabling the auto backend
> idle shutdown the box has been rock solid.
>
>

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

krt at krt

Sep 24, 2012, 2:48 PM

Post #12 of 18 (694 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

On 10/07/12 07:22, Kingsley Turner wrote:
> Hi,
>
> I recently re-installed Mythbuntu 12.04 64bit on a machine that was
> running Mythbuntu 11.10 32-bit PAE (without this issue)
>
> Everything seems to be working - it records, plays back, does everything
> OK - except that sometimes the box reboots itself?!
>
> There doesn't seem to be any particular trigger that I can work out - last
> night it crashed while recording as soon as I stopped watching something.
> It also looks like it crashed overnight while recording, but not playing
> anything. Of course it's also been up for sometimes two days without a
> hitch.
>
> I'm not really sure what to do here. I am using the Mythbuntu installed
> nVidia blob driver, and I have tried changing this to the driver with
> updates rather than the non-updated driver. This hasn't made any
> difference to stability - I mention it only because previously I used the
> nVidia driver installed manually (rather than the Ubuntu package).
>
> Typically I would believe this was caused by bad RAM or suchlike - but
> that seems a stretch given the 32bit OS never exhibited any stability
> problems at all.
>
> So - I really don't know what to do! The WAF is plummeting (if the
> Tour-de-france highlights weren't repeated a few hours after the
> crash-mid-schedule I would have really been in the dog house.)

Just a follow-up on this -

I found an identical motherboard, and some RAM to re-test this.
I had already replaced the PSU, to no effect (except to the wallet).

With the new motherboard, and the new or existing RAM - exactly the same

So I removed the nvidia blob supplied with Ubuntu, and installed from the
nVidia supplied driver.
This did lead to a change: instead of simply rebooting, now it gets GUI
lockups. Killing X etc. has no effect, but the backend seems to be running
OK. I could ssh in and reboot it.

Just now it hard-locked everything during some TV playback, with a repeating
audio loop (about 1 second long, very weird).
Running an xscreensaver GL based hack seems to cause the problem within an
hour or so, or otherwise longer. This time I had "chmod -x" xscreensaver
before reboot, so that was out of the equation too.

That leaves only the CPU and two DVB cards that have not been swapped out.

I was under the impression CPU's didn't break?
I re-did the thermal paste when I swapped the motherboard; but I also
checked the thermals before, and it was all fine (about 45C IIRC).

Any further advice?

Ditch the DVB cards for a while and test ?

cheers,
-kt

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

david at more

Sep 25, 2012, 12:54 AM

Post #13 of 18 (688 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

On 24 Sep 2012 22:49, "Kingsley Turner" <krt [at] krt> wrote:
> Any further advice?

I can't give advice, but I can say that I've had pretty much all those
symptoms over the past 6 months on my Zotac Atom/Ion FE. I'd had the freeze
with repeated audio loop occasionally for years and suspected ALSA.
Eventually I upgraded from 10.10 to 11.04 so I could upgrade from 0.24 to
0.25. Then I moved from diskless to a new 12.04 install on an SSD. All
32-bit. My BE is still on 10.04.

Somewhere along that route, stability hit a horrific low. Frequent reboots
and freezes of many different kinds. The kids practically stopped watching
TV, so it had its benefits. But after some extended troubleshooting, I
finally saw a RAM test that failed. While replacing the RAM, a tiny 8mm
long sliver of metal (a shaving from the case?) appeared that had been
lodged on the motherboard under the RAM sockets. Anyway, this exercise
solved the random reboots and some of the freezes.

The remaining FE freezes were fixed by correcting a pm-utils bug (see my
recent thread on that). My FE now seems to be very stable...

Other stuff I've hit along the way:

1. The original nvidia drivers in 12.04 can cause xorg to crash. I now use
the x-swat PPA version.

2. I read reports of random reboots with the 3.2 kernel which were fixed in
3.4. I tried installing a 3.4 kernel, but it made no different for me so I
reverted.

3. As well as the pm-utils issue I mentioned, I've previously had other
problems that only happen after suspend/resume, but not after a reboot.

FWIW, the only significant problems I've experienced that haven't had clues
in the logs have been hardware or nvidia driver issues.

David

david at more

Sep 25, 2012, 1:30 AM

Post #14 of 18 (682 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

On 24 September 2012 22:48, Kingsley Turner <krt [at] krt> wrote:
> Any further advice?

One last thing I tried whilst troubleshooting my problems; disabling
ACPI in the kernel boot options. Not necessarily a solution in its own
right, but it did help me figure out that one of my issues only
happened after resume.

David
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

jksjdevelop at gmail

Sep 25, 2012, 1:11 PM

Post #15 of 18 (680 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

On 25/09/12 08:54, David Edwards wrote:
> I can't give advice, but I can say that I've had pretty much all those
> symptoms over the past 6 months on my Zotac Atom/Ion FE. I'd had the
> freeze with repeated audio loop occasionally for years and suspected
> ALSA. Eventually I upgraded from 10.10 to 11.04 so I could upgrade
Just to confirm this, I too have a first gen Nvidia ion atom comb and I
have suffered the same symptoms as David.
System stability was hopeless on recent Ubuntu kernels.
Ubuntu 11.10 with Nvidia 295.20 was stable.
Then useless until 12.04.1 kernel 3.2.0-29 with nvidia 295.49 .
The issues were video hang, last audio block looping.
Kernel 3.2.0-30 is not stable, I have not tried 31.
It makes no difference whether 32 or 64 bit kernels are used.
I am sticking with 3.2.0-29 nvidia 295.49.
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://www.mythtv.org/mailman/listinfo/mythtv-users

krt at krt

Feb 5, 2013, 4:18 PM

Post #16 of 18 (325 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

joe at thefrys

Feb 5, 2013, 7:18 PM

Post #17 of 18 (320 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

> I recently re-installed Mythbuntu 12.04 64bit on a machine that was
>> running Mythbuntu 11.10 32-bit PAE (without this issue)
>>
>> Everything seems to be working - it records, plays back, does everything
>> OK - except that sometimes the box reboots itself?!
>>
>> There doesn't seem to be any particular trigger that I can work out -
>> last night it crashed while recording as soon as I stopped watching
>> something. It also looks like it crashed overnight while recording, but not
>> playing anything. Of course it's also been up for sometimes two days
>> without a hitch.
>>
>
>
> So ... more than six months later, I can finally revel the culprit was ...
> THE C-P-U !!! <shocked gasp from the crowd />
>
> I bought a new DVB card, and had thus replaced *everything* in the box
> except the CPU. The lock-ups & reboots persisted.
>
> Still not wanting to believe it to be true, I only bought a $40 2nd-hand
> core2-duo, replacing my core2-quad.
>
> Lots of problems went away.
> Crashes (although it's only been 12 hours, so maybe I'm being too
> optimistic).
> Transcoding didn't work properly either - it missed cut points etc.
> Running a high-end open-gl screensaver (it shows my photo album while
> idle) used to lock it up
>
> I still need to do some more testing, but *fingers crossed*, it's all
> fixed with the CPU.
>
> Are CPU's repairable ?
>
> I wonder if it's still under warranty ? Don't think I have the receipt.
>

Nope, not repairable.

While you may have a bad CPU, it could be something else altogether. You
might not have had good thermal conductivity with the heatsink, may not
have had a good seat in the socket, may have outdated firmware.
Additionally, you might be able to get away with under-clocking, disabling
a core, increasing voltages, etc. Finally, I have seen similar issues
caused by a power supply, or the motherboard's power circuits/.

While the two chips you compared are similar in many ways... they may be
very different in terms of the demands they place on other components in
the system... in order to have any assurance that it's the CPU, you would
need to do an apples to apples comparison and replace it with an identical
CPU.

krt at krt

Feb 10, 2013, 6:26 PM

Post #18 of 18 (290 views)
Permalink

Re: HELP! 64bit Mythbuntu spontaneously reboots (32bit didn't) [In reply to]

On 06/02/13 14:18, Joseph Fry wrote:
>
>
> Everything seems to be working - it records, plays back, does
> everything OK - except that sometimes the box reboots itself?!
>
> There doesn't seem to be any particular trigger that I can work
> out - last night it crashed while recording as soon as I stopped
> watching something. It also looks like it crashed overnight while
> recording, but not playing anything. Of course it's also been up
> for sometimes two days without a hitch.
>
>
>
> So ... more than six months later, I can finally revel the culprit was
> ... THE C-P-U !!! <shocked gasp from the crowd />
>
>
>
> Nope, not repairable.
>
> While you may have a bad CPU, it could be something else altogether. You
> might not have had good thermal conductivity with the heatsink, may not
> have had a good seat in the socket, may have outdated firmware.
> Additionally, you might be able to get away with under-clocking,
> disabling a core, increasing voltages, etc. Finally, I have seen similar
> issues caused by a power supply, or the motherboard's power circuits/.
>
> While the two chips you compared are similar in many ways... they may be
> very different in terms of the demands they place on other components in
> the system... in order to have any assurance that it's the CPU, you would
> need to do an apples to apples comparison and replace it with an identical
> CPU.
>

For the most part: true!

But I also replaced the motherboard (I had an identical spare) which
involved re-seating the CPU, and re-thermal-pasting
Also I recorded the thermals, it was all nominal.

The big problem is I was tired of dicking-around with it, and wanted it to
Just Work (TM). Now it does :D

You don't realise how much you depend on MythTV working.
Ok so the kids wont go hungry if it doesn't perform, but it makes life just
that little bit nicer.

thanks for the suggestions,
-kt

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads