Resurrecting an old thread.
To rehash the issue: The motherboard in my mythbackend died. I replaced
it with an ASUS K8V-X SE and AMD Athlon 64 3000+. It also had a PVR-250
and a PVR-500 in it. The formerly rock solid machine started having
random reboots with no warning. I traced it down to the PVR-500. When
capturing from the PVR-500, the box would suddenly reboot. Nothing in
the logs or on the console.
So I finally got some time and money to throw at this issue. I ebay'd a
ASRock K8Upgrade-NF3 motherboard. I swapped it out for the ASUS board.
The machine is rock solid again. The ASUS board uses a VIA K8T800
northbridge and a VIA VT8237R southbridge. The ASRock board use a single
NVIDIA nForce3 250 chip. I mention the chipsets as I suspect that the
VIA chipset were the culprit. I have no evidence, just my gut. The ASUS
board ran fine when the PVR-500 wasn't in use. The two just didn't play
well together.
Just an FYI,
Ken
Steve Firth wrote:
It's sounding like Mark Paulus' theory is the best contender: Dodgy caps
on the PVR-500 or motherboard.
Given that the PSU itself is known to be OK, and you've swapped a lot of
stuff already....a change of thought...
I can't see any way for a PCI card to generate a genuine spurious reset
to the motherboard. Though someone may correct me.
I can only imagine that a reboot could happen if the supplies are
marginally decoupled either on the motherboard where the PCI connector
"exits"
or on the card itself, or a combination of the two, pulling down one of
the supplies for enough time to do an unintentional power on-reset.
Improving the decoupling on either board may help as the (lack of) total
decoupling would be the problem. I'm suspecting that the source is the
PCI card but the effect is on the motherboard only.
Depending how brave you are......in reverse order of ease!
I'm not sure if you are able to add SMD caps yourself? If you are, don't
worry about the value just use the largest value you can find in the
same package type , and solder it over the top, in parallel of the old
ones. SI theory has changed recently on this point, it used to be the
biggest value cap, but the increased inductance tends to swamp the
capacitive gains.
Slightly less fiddly would be to take flying leads from the PSU directly
to the PCI card, reducing the Vdd drop along the motherboard. Even just
a fat ground lead could help.
Alternatively, if you aren't able to do any decoupling/soldering
experiments! You could try to reduce any possible undesired impedance by
cleaning up the contacts on the PCI card, making them as shiny-clean as
possible. This is likely to be resistive not inductive and so will
impact overall Vdd droop not instantaneous droop, but it may give you
some margin.
Can you use a PCI slot closer to where the ATX supply enters the
motherboard? This would improve the net impedance.
Can you try a PCI extender board or several stacked? The idea here is
to increase the inductance, to provide more Vdd isolation from the
motherboard supplies, on the assumption that the PCI card
integrity/margin is OK, but it couples back noise to the motherboard.
Sorry again if this is information overload
spf
----- Original message -----
Sent: 2009/06/09 17:03:19
Subject: Re:Re: [ivtv-users] Random Reboots w/PVR-500
I orginally thought power supply and upgraded to a newer, more
powerful(700W) one. It didn't help.
I've moved around/removed as much as I could; i.e. drives, cards, etc.,
with no change. I've tried multiple video cards and moving the PVR cards
around, same results.
The old MB/CPU combo was a 32bit AMD setup. Something completely died
and I couldn't get it to post, so I installed the current combo which
were laying around from upgrading another system.
With the card installed, but not in use, the system will run fine for
days. Myth will record from PVR-250 without a problem. Start one capture
from the PVR-500 and in 1 to ~20 minutes, the system reboots.
When it reboots, it comes back up just fine.
Steve Firth wrote:
>
>
> Thoughts......
>
> Is the psu upto the job of the new motherboard/CPU. Is there a
possibility
> of a thermal or other environmental issue with the processor? e.g. is
> heatsink correctly
> connected? Can you beg/borrow/steal a chunkier PSU to try a swap?
>
> Clean all connectors. Could you have damaged a connector when installing
> new motherboard etc ?
> or pushed the solder away from the back of the PCB? A dry joint is
> possible especially on the larger connectors : Do any of the
> solder joints on the PSU connectors particularly look "dull"? Or, just
> resolder them anyway if you're OK with a soldering
> iron (I've seen this often on TV HT side)
>
> After restart and being presented with BIOS does it then continue with
> the boot to Myth
> or just hangs? i.e. are we suspecting spurious resets?
>
> Can you swap back the old processor? and do a 2 way uP/Motherboard swap
> with all 4 combinations?
> (new/new, old/new, old/old, new/old)
>
> Can you remove the Disk drives one by one? or any other peripherals?
>
> I'm rabbiting now : In summary: can you change/remove as much as
> possible and see if there is any change in behaviour?
>
>
>
> spf
>
> ----- Original message -----
> Sent: 2009/06/09 16:00:17
> Subject: Re:[ivtv-users] Random Reboots w/PVR-500
>
> I am running MythTV via atrpms packages on a CentOS 5.3 install. I have
> a PVR-250, a PVR-500 and a HD HomeRun. I am getting random reboots when
> capturing from the PVR-500. There are no problems when capturing from
> the PVR-250. It is not a MythTV issue as it occurs when I just cat from
> the appropriate /dev/videoX device file. There are no messages on the
> console or in /var/log/messages. All of a sudden the machine reboots and
> I'm looking at the BIOS startup screen. The problem has persisted
> through kernel updates. It started not long after I installed a new
> motherboard and processor due to the old one dying. So, I'm thinking
> chip issue or something like that.
>
> Any ideas will be greatly appreciated.
>
> Ken
>
>
>
>
>
> Processor: AMD Athlon(tm) 64 Processor 3000+
> Motherboard: ASUS K8V-X SE
> Distro: CentOS 5.3
> Kernel: 2.6.18-128.1.10.el5 (stock)
> ivtv-0.10.6-132.el5
> ivtv-firmware-20080701-18
> ivtv-kmdl-2.6.18-128.1.10.el5-0.10.6-132.el5
> perl-Video-ivtv-0.13-8.0.el5
>
> ivtv: ==================== START INIT IVTV ====================
> ivtv: version 0.10.6 (tagged release) loading
> ivtv: Linux version: 2.6.18-128.1.10.el5 SMP mod_unload 686 REGPARM
> 4KSTACKS gcc-4.1
> ivtv: In case of problems please include the debug info between
> ivtv: the START INIT IVTV and END INIT IVTV lines, along with
> ivtv: any module options, when mailing the ivtv-users mailinglist.
> ivtv0: Autodetected Hauppauge card (cx23416 based)
> ACPI: PCI Interrupt 0000:00:0c.0[A] -> GSI 17 (level, low) -> IRQ 185
> input: PC Speaker as /class/input/input0
> via-rhine.c:v1.10-LK1.4.1 July-24-2006 Written by Donald Becker
> sd 0:0:0:0: Attached scsi generic sg0 type 0
> sd 1:0:0:0: Attached scsi generic sg1 type 0
> ivtv0: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> ivtv0: Encoder revision: 0x02060039
> tveeprom 1-0050: Hauppauge model 32031, rev B110, serial# 6790025
> tveeprom 1-0050: tuner model is Philips FI1236 MK2 (idx 10, type 2)
> tveeprom 1-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 1-0050: audio processor is MSP3435 (idx 10)
> tveeprom 1-0050: decoder processor is SAA7115 (idx 19)
> tveeprom 1-0050: has no radio, has IR remote
> ivtv0: Autodetected Hauppauge WinTV PVR-250
> tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0)
> saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c driver #0)
> msp3400 1-0040: MSP3435G-B6 found @ 0x80 (ivtv i2c driver #0)
> msp3400 1-0040: MSP3435G-B6 supports radio, mode is autodetect and
> autoselect
> ivtv0: Registered device video0 for encoder MPEG (16 MB)
> ivtv0: Registered device video32 for encoder YUV (2 MB)
> ivtv0: Registered device vbi0 for encoder VBI (8 MB)
> ivtv0: Registered device video24 for encoder PCM audio (1 MB)
> tuner 1-0061: type set to 2 (Philips NTSC (FI1236,FM1236 and
compatibles))
> ivtv0: Initialized Hauppauge WinTV PVR-250, card #0
> ivtv: ====================== NEXT CARD ======================
> ivtv1: Autodetected Hauppauge card (cx23416 based)
> ACPI: PCI Interrupt 0000:02:08.0[A] -> GSI 19 (level, low) -> IRQ 193
> ivtv1: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> ivtv1: Encoder revision: 0x02060039
> tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #1)
> tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner)
> tuner 2-0060: TEA5767 detected.
> tuner 2-0060: chip found @ 0xc0 (ivtv i2c driver #1)
> tuner 2-0060: type set to 62 (Philips TEA5767HN FM Radio)
> tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #1)
> tveeprom 2-0050: Hauppauge model 23552, rev D492, serial# 7855863
> tveeprom 2-0050: tuner model is Philips FQ1236A MK4 (idx 92, type 57)
> tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 2-0050: second tuner model is Philips TEA5768HL FM Radio (idx
> 101, type 62)
> tveeprom 2-0050: audio processor is CX25843 (idx 37)
> tveeprom 2-0050: decoder processor is CX25843 (idx 30)
> tveeprom 2-0050: has radio, has no IR remote
> ivtv1: Autodetected WinTV PVR 500 (unit #1)
> cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1)
> cx25840 2-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #1)
> ivtv1: Registered device video1 for encoder MPEG (16 MB)
> ivtv1: Registered device video33 for encoder YUV (2 MB)
> ivtv1: Registered device vbi1 for encoder VBI (8 MB)
> ivtv1: Registered device video25 for encoder PCM audio (1 MB)
> ivtv1: Registered device radio1 for encoder radio
> tuner 2-0061: type set to 57 (Philips FQ1236A MK4)
> ivtv1: Initialized WinTV PVR 500 (unit #1), card #1
> PCI: Enabling device 0000:00:11.5 (0000 -> 0001)
> ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 201
> PCI: Setting latency timer of device 0000:00:11.5 to 64
> ivtv: ====================== NEXT CARD ======================
> ivtv2: Autodetected Hauppauge card (cx23416 based)
> ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 16 (level, low) -> IRQ 209
> codec_read: codec 0 is not valid [0xfe0000]
> codec_read: codec 0 is not valid [0xfe0000]
> codec_read: codec 0 is not valid [0xfe0000]
> codec_read: codec 0 is not valid [0xfe0000]
> ivtv2: loaded v4l-cx2341x-enc.fw firmware (376836 bytes)
> ivtv2: Encoder revision: 0x02060039
> tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #2)
> tda9887 3-0043: tda988[5/6/7] found @ 0x43 (tuner)
> tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #2)
> cx25840 3-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #2)
> cx25840 3-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
> wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #2)
> tveeprom 3-0050: Hauppauge model 23552, rev D492, serial# 7855863
> tveeprom 3-0050: tuner model is Philips FQ1236A MK4 (idx 92, type 57)
> tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08)
> tveeprom 3-0050: second tuner model is Philips TEA5768HL FM Radio (idx
> 101, type 62)
> tveeprom 3-0050: audio processor is CX25843 (idx 37)
> tveeprom 3-0050: decoder processor is CX25843 (idx 30)
> tveeprom 3-0050: has radio, has no IR remote
> ivtv2: Correcting tveeprom data: no radio present on second unit
> ivtv2: Autodetected WinTV PVR 500 (unit #2)
> ivtv2: Registered device video2 for encoder MPEG (16 MB)
> ivtv2: Registered device video34 for encoder YUV (2 MB)
> ivtv2: Registered device vbi2 for encoder VBI (8 MB)
> ivtv2: Registered device video26 for encoder PCM audio (1 MB)
> tuner 3-0061: type set to 57 (Philips FQ1236A MK4)
> ivtv2: Initialized WinTV PVR 500 (unit #2), card #2
> ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 23 (level, low) -> IRQ 217
> eth0: VIA Rhine II at 0xfaa00000, 00:15:f2:41:46:a9, IRQ 217.
> eth0: MII PHY found at address 1, status 0x7849 advertising 01e1 Link
0000.
> r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
> ACPI: PCI Interrupt 0000:00:0d.0[A] -> GSI 18 (level, low) -> IRQ 225
> r8169 0000:00:0d.0: no PCI Express capability
> eth1: RTL8169sb/8110sb at 0xf89de000, 00:19:e0:73:18:31, XID 10000000
> IRQ 225
> ivtv: ==================== END INIT IVTV ====================
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
