Hi all,
An interesting feature has came up with kernel 2.6.14 and hauppauge Nova-T (the older model) and the dxr3.
If the computer has been down and started again, modules load up, vdr starts and bang -> the computer seems locked up (even the numlock doesn't light).
This has happened multiple times already (and will happen if there's a power loss).
I've noticed that if the computer is left on for about 10 minutes, miraculously, everything start working again.
I've tried to start vdr with a plain 'vdr' command, and still, the computer will freeze (hauppauge drivers and dxr3's kernel modules were previously loaded though).
Not sure what causes this, but in case somebody stumbles into this, just wait for recovery :-)
BR, Jarmo
On Tue, Dec 13, 2005 at 12:52:49PM +0200, Jarmo Järvenpää wrote:
An interesting feature has came up with kernel 2.6.14 and hauppauge Nova-T (the older model) and the dxr3.
If the computer has been down and started again, modules load up, vdr starts and bang -> the computer seems locked up (even the numlock doesn't light).
This has happened multiple times already (and will happen if there's a power loss).
I've noticed that if the computer is left on for about 10 minutes, miraculously, everything start working again.
I had similar problems on my box. The computer would reboot if there was a lot of VGA activity right after power-on. It would be fine after a few minutes of warming up with video output suspended.
I fixed the problem by replacing the big capacitors on the motherboard. Most likely the on-board switching power supply of the motherboard (for the chipset or the CPU) was malfunctioning due to aging capacitors. One of the capacitors had some leaked electrolyte on the cap. I had hard time finding replacement capacitors, until a friend gave me ones from a motherboard that was damaged because of his home-made water cooler.
Of course, it could be software or the main power supply as well. Have you updated the software lately? Have you tried reverting it?
Marko
On Tue, 13 Dec 2005 12:52:49 +0200 Jarmo Järvenpää jjarven@softers.net wrote:
Hi all,
An interesting feature has came up with kernel 2.6.14 and hauppauge Nova-T (the older model) and the dxr3.
If the computer has been down and started again, modules load up, vdr starts and bang -> the computer seems locked up (even the numlock doesn't light).
This has happened multiple times already (and will happen if there's a power loss).
I've noticed that if the computer is left on for about 10 minutes, miraculously, everything start working again.
I've tried to start vdr with a plain 'vdr' command, and still, the computer will freeze (hauppauge drivers and dxr3's kernel modules were previously loaded though).
Not sure what causes this, but in case somebody stumbles into this, just wait for recovery :-)
BR, Jarmo
Could also be a problem with shared interrupts and an old dxr3 driver. What version are you using? Post the output of "cat /proc/interrupts".
-- Niko Mikkilä
Niko Mikkila wrote:
Could also be a problem with shared interrupts and an old dxr3 driver. What version are you using? Post the output of "cat /proc/interrupts".
Interrupts: CPU0 0: 1481133 XT-PIC timer 2: 0 XT-PIC cascade 3: 66813 XT-PIC em8300, saa7146 (1) 4: 1041 XT-PIC lirc_serial 6: 0 XT-PIC Intel 82801BA-ICH2 7: 58429 XT-PIC wlan0 8: 1 XT-PIC rtc 9: 252590 XT-PIC acpi, uhci_hcd:usb2, saa7146 (0) 10: 0 XT-PIC uhci_hcd:usb1 11: 2950 XT-PIC eth0 14: 31921 XT-PIC ide0 15: 22 XT-PIC ide1 NMI: 0 LOC: 0 ERR: 0 MIS: 0
Dxr3-driver: em8300-0.15.2
BR, Jarmo
On Wed, 2005-12-14 at 08:41 +0200, Jarmo Järvenpää wrote:
Niko Mikkila wrote:
Could also be a problem with shared interrupts and an old dxr3 driver. What version are you using? Post the output of "cat /proc/interrupts".
Interrupts:
[...]
3: 66813 XT-PIC em8300, saa7146 (1)
Even if using the newest em8300 driver, I would try to arrange it so that em8300 doesn't share interrupts with another device (or if it does, it does it with something less used than a DVB card). Shuffle cards in PCI slots, disable unneeded devices in BIOS, see if BIOS allows explicit IRQ assignments to PCI slots etc. Your IRQ 5 seems to have no devices on it...
-
Jarmo Järvenpää -
Marko Mäkelä -
Niko Mikkila -
Ville Skyttä