Re: [mythtv-users] Occasional hard freezes
On 11/1/05, Julian Edwards <[EMAIL PROTECTED]> wrote: Ryan Steffes wrote> Changing to acpi=off did not fix the problem. I'm a little concerned> with whether it's really off though, it seems to turn on local apic> before reading the kernel options: You will also need to clear the ECSD memory in the BIOS to make itreassign the IRQs. It's either labelled "reset ECSD" (or ESCD, mymemory is crap) or something like "clear NVRAM". If there's nothing like that then you may need to clear the whole BIOS settings with themobo jumper.What sound card are you using in the system? SBLive cards have knownproblems.___ I will try that, I've had it running well for a couple days now by not transfering data as much as I was doing (doing all my transcoding on the backend machine). I've been in the process of backing up all my dvds onto my drive, so it's really putting a crimp in my plans to only have one machine working on them at once. The NIC is looking very suspect at the moment, which is a pity since I specifically bought this board for the onboard gigabit nic and the onboard optical s/pdif out. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
Ryan Steffes wrote Changing to acpi=off did not fix the problem. I'm a little concerned with whether it's really off though, it seems to turn on local apic before reading the kernel options: You will also need to clear the ECSD memory in the BIOS to make it reassign the IRQs. It's either labelled "reset ECSD" (or ESCD, my memory is crap) or something like "clear NVRAM". If there's nothing like that then you may need to clear the whole BIOS settings with the mobo jumper. What sound card are you using in the system? SBLive cards have known problems. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
On 10/31/05, Ryan Steffes <[EMAIL PROTECTED]> wrote: I've tried seperating the drives onto different IDE channels, without success. I'm wondering if there's a problem with the onboard gigabit NIC itself. Does anyone have a system working properly with a MSI K7N2 Delta 2, with digital audio and gigabit nic working? ___mythtv-users mailing listmythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-usersI have drives on separate channels and still see sporadic issues. You could definately try a different NIC card, or even different NIC drivers (if available). ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
I've tried seperating the drives onto different IDE channels, without success. I'm wondering if there's a problem with the onboard gigabit NIC itself. Does anyone have a system working properly with a MSI K7N2 Delta 2, with digital audio and gigabit nic working? ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
On 10/29/05, Michael T. Dean <[EMAIL PROTECTED]> wrote: Jason Werpy wrote:>On 10/29/05, Ryan Steffes <[EMAIL PROTECTED]> wrote:On 10/28/05, Michael T. Dean < [EMAIL PROTECTED]> wrote:>>>vi /usr/src/linux-`uname -r`/Documentation/kernel- parameters.txt>>...>>I think you were trying for "acpi=noirq noapic nolapic". And, it >>>wouldn't hurt to throw in a "pci=noacpi" for good measure. Most of the>>>'net gets these parameters wrong, though, so I realize you saw someone>>>else recommend this... Changing to acpi=off did not fix the problem. I'm a little concerned with>>whether it's really off though, it seems to turn on local apic before>>reading the kernel options: Oct 29 08:56:54 mythtv kernel: Found and enabled local APIC!>>Oct 29 08:56:54 mythtv kernel: Initializing CPU#0>>Oct 29 08:56:54 mythtv kernel: Kernel command line: auto BOOT_IMAGE=MythTV >>ro root=341 acpi=off noapic nolapic resume=/dev/hdb3 splash=silent>>Oct 29 08:56:54 mythtv kernel: bootsplash: silent mode.Later, it does say:Oct 29 08:56:54 mythtv kernel: PCI: PCI BIOS revision 2.10 entry at>>0xfbe50, last bus=2>>Oct 29 08:56:54 mythtv kernel: PCI: Using configuration type 1>>Oct 29 08:56:54 mythtv kernel: mtrr: v2.0 (20020519)>>Oct 29 08:56:54 mythtv kernel: ACPI: Subsystem revision 20050211 >>Oct 29 08:56:54 mythtv kernel: ACPI: Interpreter disabled.>>Oct 29 08:56:54 mythtv kernel: Linux Plug and Play Support v0.97 (c) Adam>>Belay>>Oct 29 08:56:54 mythtv kernel: pnp: PnP ACPI: disabled >>Oct 29 08:56:54 mythtv kernel: PnPBIOS: Disabled>>Oct 29 08:56:54 mythtv kernel: PCI: Probing PCI hardware>>Oct 29 08:56:54 mythtv kernel: PCI: Probing PCI hardware (bus 00)>>Oct 29 08:56:54 mythtv kernel: PCI: Using IRQ router default [10de/01e0] >>at :00:00.0but it doesn't say anything about local apic again. How can I check that>>it's really disabled?>You might also need the nolapci kernel parameter to turn off local apci, its >separate from the main apci kernel parameters.>>Once again, I know you were just repeating something you've seen outthere on the 'net, but as described in kernel-parameters.txt (asreferenced above) there is no such parameter as "nolapci". As a matter of fact, there is no (relevant) such thing as APCI or apci. ACPI isAdvanced Configuration and Power Management and APIC is AdvancedProgrammable Interrupt Controller.Note, there's also no "nolacpi" parameter, and he's already using "nolapic". Mike___mythtv-users mailing listmythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-usersI think I got a typo in there somewhere. I meant nolacpi, or at least I meant the interrupt controler one, and not the power management thing. Oops. I hate these acronyms. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
On 10/29/05, Michael T. Dean <[EMAIL PROTECTED]> wrote: Ryan Steffes wrote:> Changing to acpi=off did not fix the problem. I'm a little concerned> with whether it's really off though, it seems to turn on local apic> before reading the kernel options: >> Oct 29 08:56:54 mythtv kernel: Found and enabled local APIC!> Oct 29 08:56:54 mythtv kernel: Initializing CPU#0> Oct 29 08:56:54 mythtv kernel: Kernel command line: auto> BOOT_IMAGE=MythTV ro root=341 acpi=off noapic nolapic resume=/dev/hdb3 > splash=silent> Oct 29 08:56:54 mythtv kernel: bootsplash: silent mode.>> Later, it does say:>> Oct 29 08:56:54 mythtv kernel: PCI: PCI BIOS revision 2.10 entry at> 0xfbe50, last bus=2 > Oct 29 08:56:54 mythtv kernel: PCI: Using configuration type 1> Oct 29 08:56:54 mythtv kernel: mtrr: v2.0 (20020519)> Oct 29 08:56:54 mythtv kernel: ACPI: Subsystem revision 20050211> Oct 29 08:56:54 mythtv kernel: ACPI: Interpreter disabled. > Oct 29 08:56:54 mythtv kernel: Linux Plug and Play Support v0.97 (c)> Adam Belay> Oct 29 08:56:54 mythtv kernel: pnp: PnP ACPI: disabled> Oct 29 08:56:54 mythtv kernel: PnPBIOS: Disabled> Oct 29 08:56:54 mythtv kernel: PCI: Probing PCI hardware > Oct 29 08:56:54 mythtv kernel: PCI: Probing PCI hardware (bus 00)> Oct 29 08:56:54 mythtv kernel: PCI: Using IRQ router default> [10de/01e0] at :00:00.0>> but it doesn't say anything about local apic again. How can I check > that it's really disabled?If you have a relatively nice BIOS, it will enable you to disable ACPI,LAPIC, and possibly APIC. Try that in addition to the kernel params.Mike___ mythtv-users mailing listmythtv-users@mythtv.orghttp://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users According to the BIOS, local apic is allegedly disabled. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
Ryan Steffes wrote: Changing to acpi=off did not fix the problem. I'm a little concerned with whether it's really off though, it seems to turn on local apic before reading the kernel options: Oct 29 08:56:54 mythtv kernel: Found and enabled local APIC! Oct 29 08:56:54 mythtv kernel: Initializing CPU#0 Oct 29 08:56:54 mythtv kernel: Kernel command line: auto BOOT_IMAGE=MythTV ro root=341 acpi=off noapic nolapic resume=/dev/hdb3 splash=silent Oct 29 08:56:54 mythtv kernel: bootsplash: silent mode. Later, it does say: Oct 29 08:56:54 mythtv kernel: PCI: PCI BIOS revision 2.10 entry at 0xfbe50, last bus=2 Oct 29 08:56:54 mythtv kernel: PCI: Using configuration type 1 Oct 29 08:56:54 mythtv kernel: mtrr: v2.0 (20020519) Oct 29 08:56:54 mythtv kernel: ACPI: Subsystem revision 20050211 Oct 29 08:56:54 mythtv kernel: ACPI: Interpreter disabled. Oct 29 08:56:54 mythtv kernel: Linux Plug and Play Support v0.97 (c) Adam Belay Oct 29 08:56:54 mythtv kernel: pnp: PnP ACPI: disabled Oct 29 08:56:54 mythtv kernel: PnPBIOS: Disabled Oct 29 08:56:54 mythtv kernel: PCI: Probing PCI hardware Oct 29 08:56:54 mythtv kernel: PCI: Probing PCI hardware (bus 00) Oct 29 08:56:54 mythtv kernel: PCI: Using IRQ router default [10de/01e0] at :00:00.0 but it doesn't say anything about local apic again. How can I check that it's really disabled? If you have a relatively nice BIOS, it will enable you to disable ACPI, LAPIC, and possibly APIC. Try that in addition to the kernel params. Mike ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
Jason Werpy wrote: On 10/29/05, Ryan Steffes <[EMAIL PROTECTED]> wrote: On 10/28/05, Michael T. Dean <[EMAIL PROTECTED]> wrote: vi /usr/src/linux-`uname -r`/Documentation/kernel- parameters.txt ... I think you were trying for "acpi=noirq noapic nolapic". And, it wouldn't hurt to throw in a "pci=noacpi" for good measure. Most of the 'net gets these parameters wrong, though, so I realize you saw someone else recommend this... Changing to acpi=off did not fix the problem. I'm a little concerned with whether it's really off though, it seems to turn on local apic before reading the kernel options: Oct 29 08:56:54 mythtv kernel: Found and enabled local APIC! Oct 29 08:56:54 mythtv kernel: Initializing CPU#0 Oct 29 08:56:54 mythtv kernel: Kernel command line: auto BOOT_IMAGE=MythTV ro root=341 acpi=off noapic nolapic resume=/dev/hdb3 splash=silent Oct 29 08:56:54 mythtv kernel: bootsplash: silent mode. Later, it does say: Oct 29 08:56:54 mythtv kernel: PCI: PCI BIOS revision 2.10 entry at 0xfbe50, last bus=2 Oct 29 08:56:54 mythtv kernel: PCI: Using configuration type 1 Oct 29 08:56:54 mythtv kernel: mtrr: v2.0 (20020519) Oct 29 08:56:54 mythtv kernel: ACPI: Subsystem revision 20050211 Oct 29 08:56:54 mythtv kernel: ACPI: Interpreter disabled. Oct 29 08:56:54 mythtv kernel: Linux Plug and Play Support v0.97 (c) Adam Belay Oct 29 08:56:54 mythtv kernel: pnp: PnP ACPI: disabled Oct 29 08:56:54 mythtv kernel: PnPBIOS: Disabled Oct 29 08:56:54 mythtv kernel: PCI: Probing PCI hardware Oct 29 08:56:54 mythtv kernel: PCI: Probing PCI hardware (bus 00) Oct 29 08:56:54 mythtv kernel: PCI: Using IRQ router default [10de/01e0] at :00:00.0 but it doesn't say anything about local apic again. How can I check that it's really disabled? You might also need the nolapci kernel parameter to turn off local apci, its separate from the main apci kernel parameters. Once again, I know you were just repeating something you've seen out there on the 'net, but as described in kernel-parameters.txt (as referenced above) there is no such parameter as "nolapci". As a matter of fact, there is no (relevant) such thing as APCI or apci. ACPI is Advanced Configuration and Power Management and APIC is Advanced Programmable Interrupt Controller. Note, there's also no "nolacpi" parameter, and he's already using "nolapic". Mike ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
On 10/29/05, Ryan Steffes <[EMAIL PROTECTED]> wrote:
On 10/28/05, Michael T. Dean <
[EMAIL PROTECTED]> wrote:
Ryan Steffes wrote:>On 10/28/05, Julian Edwards <[EMAIL PROTECTED]> wrote:>
>>>Ryan Steffes wrote:>I thought I had finally gotten this fixed with the kernel option
>>>nolapic, but it happened to me again. I am experiencing hard lock ups>>>that seem to be related to high data throughput, but aren't consistent>>>enough for me to track down. When it freezes, only hitting the reset
>>>or power button fixes it.>>I have an MSI K7N2 Delta 2 motherboard with an AMD Barton 2500+ in>>>it. It has a nforce northbridge. I am passing the kernel "acpi=no
>>>noapic nolapic". I'm running 2.6.11-6mdk. I have one PVR 150. I have>>>two hard drives, running LVM to make one video share. I'm running>>>ivtv 0.3.9>>What happens is a hard lock up. It generally happens when I'm
>>>exercising the ethernet hard.This exact same thing was happening to me too with my KT6 Delta.[snip]>Can anyone give any advice on where to go from here?
Sure. The problem is almost certainly to do with interrupt sharing. In>>my case it was a problem with the ACPI steering assigning too many>>devices the same IRQ. I ended up fixing it by disabling unnecessary
>>onboard hardware (eg I don't need 8 USB controllers or onboard sound),>>using acpi=off (is that different to your acpi=no ?) and re-positioning>>>According to proc/interrupts, there shouldn't be a sharing problem. However,
>I'm unsure if there is a difference between acpi=no and acpi=off. I'll try>"off" and see if I can pound away on the NIC and the hard drive and see what>happens.>vi /usr/src/linux-`uname -r`/Documentation/kernel-
parameters.txt/acpiacpi=
[HW,ACPI] Advanced Configuration and Power InterfaceFormat:
{ force | off | ht | strict }force
-- enable ACPI if default was offoff
-- disable ACPI if default was onnoirq
-- do not use ACPI for IRQ routinght
-- run only enough ACPI to enable Hyper Threadingstrict
-- Be less tolerant of platforms thatare notstrictly
ACPI specification compliant.I think you were trying for "acpi=noirq noapic nolapic". And, itwouldn't hurt to throw in a "pci=noacpi" for good measure. Most of the'net gets these parameters wrong, though, so I realize you saw someone
else recommend this...Note, also, that "acpi=off" would give you the same IRQ-related resultsas "acpi=noirq" (and disable the rest of ACPI, also).
Changing to acpi=off did not fix the problem. I'm a little concerned
with whether it's really off though, it seems to turn on local apic
before reading the kernel options:
Oct 29 08:56:54 mythtv kernel: Found and enabled local APIC!
Oct 29 08:56:54 mythtv kernel: Initializing CPU#0
Oct 29 08:56:54 mythtv kernel: Kernel command line: auto
BOOT_IMAGE=MythTV ro root=341 acpi=off noapic nolapic resume=/dev/hdb3
splash=silent
Oct 29 08:56:54 mythtv kernel: bootsplash: silent mode.
Later, it does say:
Oct 29 08:56:54 mythtv kernel: PCI: PCI BIOS revision 2.10 entry at 0xfbe50, last bus=2
Oct 29 08:56:54 mythtv kernel: PCI: Using configuration type 1
Oct 29 08:56:54 mythtv kernel: mtrr: v2.0 (20020519)
Oct 29 08:56:54 mythtv kernel: ACPI: Subsystem revision 20050211
Oct 29 08:56:54 mythtv kernel: ACPI: Interpreter disabled.
Oct 29 08:56:54 mythtv kernel: Linux Plug and Play Support v0.97 (c) Adam Belay
Oct 29 08:56:54 mythtv kernel: pnp: PnP ACPI: disabled
Oct 29 08:56:54 mythtv kernel: PnPBIOS: Disabled
Oct 29 08:56:54 mythtv kernel: PCI: Probing PCI hardware
Oct 29 08:56:54 mythtv kernel: PCI: Probing PCI hardware (bus 00)
Oct 29 08:56:54 mythtv kernel: PCI: Using IRQ router default [10de/01e0] at :00:00.0
but it doesn't say anything about local apic again. How can I check that it's really disabled?
___mythtv-users mailing listmythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
You might also need the nolapci kernel parameter to turn off local apci, its separate from the main apci kernel parameters.
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
On 10/28/05, Michael T. Dean <[EMAIL PROTECTED]> wrote:
Ryan Steffes wrote:>On 10/28/05, Julian Edwards <[EMAIL PROTECTED]> wrote:Ryan Steffes wrote:>I thought I had finally gotten this fixed with the kernel option
>>>nolapic, but it happened to me again. I am experiencing hard lock ups>>>that seem to be related to high data throughput, but aren't consistent>>>enough for me to track down. When it freezes, only hitting the reset
>>>or power button fixes it.>>I have an MSI K7N2 Delta 2 motherboard with an AMD Barton 2500+ in>>>it. It has a nforce northbridge. I am passing the kernel "acpi=no
>>>noapic nolapic". I'm running 2.6.11-6mdk. I have one PVR 150. I have>>>two hard drives, running LVM to make one video share. I'm running>>>ivtv 0.3.9>>What happens is a hard lock up. It generally happens when I'm
>>>exercising the ethernet hard.This exact same thing was happening to me too with my KT6 Delta.[snip]>Can anyone give any advice on where to go from here?
Sure. The problem is almost certainly to do with interrupt sharing. In>>my case it was a problem with the ACPI steering assigning too many>>devices the same IRQ. I ended up fixing it by disabling unnecessary
>>onboard hardware (eg I don't need 8 USB controllers or onboard sound),>>using acpi=off (is that different to your acpi=no ?) and re-positioning>>>According to proc/interrupts, there shouldn't be a sharing problem. However,
>I'm unsure if there is a difference between acpi=no and acpi=off. I'll try>"off" and see if I can pound away on the NIC and the hard drive and see what>happens.>vi /usr/src/linux-`uname -r`/Documentation/kernel-
parameters.txt/acpiacpi=
[HW,ACPI] Advanced Configuration and Power InterfaceFormat:
{ force | off | ht | strict }force
-- enable ACPI if default was offoff
-- disable ACPI if default was onnoirq
-- do not use ACPI for IRQ routinght
-- run only enough ACPI to enable Hyper Threadingstrict
-- Be less tolerant of platforms thatare notstrictly
ACPI specification compliant.I think you were trying for "acpi=noirq noapic nolapic". And, itwouldn't hurt to throw in a "pci=noacpi" for good measure. Most of the'net gets these parameters wrong, though, so I realize you saw someone
else recommend this...Note, also, that "acpi=off" would give you the same IRQ-related resultsas "acpi=noirq" (and disable the rest of ACPI, also).
Changing to acpi=off did not fix the problem. I'm a little concerned
with whether it's really off though, it seems to turn on local apic
before reading the kernel options:
Oct 29 08:56:54 mythtv kernel: Found and enabled local APIC!
Oct 29 08:56:54 mythtv kernel: Initializing CPU#0
Oct 29 08:56:54 mythtv kernel: Kernel command line: auto
BOOT_IMAGE=MythTV ro root=341 acpi=off noapic nolapic resume=/dev/hdb3
splash=silent
Oct 29 08:56:54 mythtv kernel: bootsplash: silent mode.
Later, it does say:
Oct 29 08:56:54 mythtv kernel: PCI: PCI BIOS revision 2.10 entry at 0xfbe50, last bus=2
Oct 29 08:56:54 mythtv kernel: PCI: Using configuration type 1
Oct 29 08:56:54 mythtv kernel: mtrr: v2.0 (20020519)
Oct 29 08:56:54 mythtv kernel: ACPI: Subsystem revision 20050211
Oct 29 08:56:54 mythtv kernel: ACPI: Interpreter disabled.
Oct 29 08:56:54 mythtv kernel: Linux Plug and Play Support v0.97 (c) Adam Belay
Oct 29 08:56:54 mythtv kernel: pnp: PnP ACPI: disabled
Oct 29 08:56:54 mythtv kernel: PnPBIOS: Disabled
Oct 29 08:56:54 mythtv kernel: PCI: Probing PCI hardware
Oct 29 08:56:54 mythtv kernel: PCI: Probing PCI hardware (bus 00)
Oct 29 08:56:54 mythtv kernel: PCI: Using IRQ router default [10de/01e0] at :00:00.0
but it doesn't say anything about local apic again. How can I check that it's really disabled?
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
Ryan Steffes wrote:
On 10/28/05, Julian Edwards <[EMAIL PROTECTED]> wrote:
Ryan Steffes wrote:
I thought I had finally gotten this fixed with the kernel option
nolapic, but it happened to me again. I am experiencing hard lock ups
that seem to be related to high data throughput, but aren't consistent
enough for me to track down. When it freezes, only hitting the reset
or power button fixes it.
I have an MSI K7N2 Delta 2 motherboard with an AMD Barton 2500+ in
it. It has a nforce northbridge. I am passing the kernel "acpi=no
noapic nolapic". I'm running 2.6.11-6mdk. I have one PVR 150. I have
two hard drives, running LVM to make one video share. I'm running
ivtv 0.3.9
What happens is a hard lock up. It generally happens when I'm
exercising the ethernet hard.
This exact same thing was happening to me too with my KT6 Delta.
[snip]
Can anyone give any advice on where to go from here?
Sure. The problem is almost certainly to do with interrupt sharing. In
my case it was a problem with the ACPI steering assigning too many
devices the same IRQ. I ended up fixing it by disabling unnecessary
onboard hardware (eg I don't need 8 USB controllers or onboard sound),
using acpi=off (is that different to your acpi=no ?) and re-positioning
According to proc/interrupts, there shouldn't be a sharing problem. However,
I'm unsure if there is a difference between acpi=no and acpi=off. I'll try
"off" and see if I can pound away on the NIC and the hard drive and see what
happens.
vi /usr/src/linux-`uname -r`/Documentation/kernel-parameters.txt
/acpi
acpi= [HW,ACPI] Advanced Configuration and Power Interface
Format: { force | off | ht | strict }
force -- enable ACPI if default was off
off -- disable ACPI if default was on
noirq -- do not use ACPI for IRQ routing
ht -- run only enough ACPI to enable Hyper Threading
strict -- Be less tolerant of platforms that
are not
strictly ACPI specification compliant.
I think you were trying for "acpi=noirq noapic nolapic". And, it
wouldn't hurt to throw in a "pci=noacpi" for good measure. Most of the
'net gets these parameters wrong, though, so I realize you saw someone
else recommend this...
Note, also, that "acpi=off" would give you the same IRQ-related results
as "acpi=noirq" (and disable the rest of ACPI, also).
Mike
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
On 10/28/05, Julian Edwards <[EMAIL PROTECTED]> wrote: Ryan Steffes wrote:> I thought I had finally gotten this fixed with the kernel option> nolapic, but it happened to me again. I am experiencing hard lock ups> that seem to be related to high data throughput, but aren't consistent > enough for me to track down. When it freezes, only hitting the reset> or power button fixes it.>> I have an MSI K7N2 Delta 2 motherboard with an AMD Barton 2500+ in> it. It has a nforce northbridge. I am passing the kernel "acpi=no > noapic nolapic". I'm running 2.6.11-6mdk. I have one PVR 150. I have> two hard drives, running LVM to make one video share. I'm running> ivtv 0.3.9>> What happens is a hard lock up. It generally happens when I'm > exercising the ethernet hard.This exact same thing was happening to me too with my KT6 Delta.[snip]> Can anyone give any advice on where to go from here?Sure. The problem is almost certainly to do with interrupt sharing. In my case it was a problem with the ACPI steering assigning too manydevices the same IRQ. I ended up fixing it by disabling unnecessaryonboard hardware (eg I don't need 8 USB controllers or onboard sound),using acpi=off (is that different to your acpi=no ?) and re-positioning According to proc/interrupts, there shouldn't be a sharing problem. However, I'm unsure if there is a difference between acpi=no and acpi=off. I'll try "off" and see if I can pound away on the NIC and the hard drive and see what happens. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
Ryan Steffes wrote: I thought I had finally gotten this fixed with the kernel option nolapic, but it happened to me again. I am experiencing hard lock ups that seem to be related to high data throughput, but aren't consistent enough for me to track down. When it freezes, only hitting the reset or power button fixes it. I have an MSI K7N2 Delta 2 motherboard with an AMD Barton 2500+ in it. It has a nforce northbridge. I am passing the kernel "acpi=no noapic nolapic". I'm running 2.6.11-6mdk. I have one PVR 150. I have two hard drives, running LVM to make one video share. I'm running ivtv 0.3.9 What happens is a hard lock up. It generally happens when I'm exercising the ethernet hard. This exact same thing was happening to me too with my KT6 Delta. [snip] Can anyone give any advice on where to go from here? Sure. The problem is almost certainly to do with interrupt sharing. In my case it was a problem with the ACPI steering assigning too many devices the same IRQ. I ended up fixing it by disabling unnecessary onboard hardware (eg I don't need 8 USB controllers or onboard sound), using acpi=off (is that different to your acpi=no ?) and re-positioning the cards in the PCI slots. I would check your motherboard's manual since some slots will share an interrupt whatever you do. You can also assign specific slots a specific IRQ in the BIOS. I've also heard that using SBLive cards can cause these sorts of issues - and that's exactly what I am using. If I remove it and turn on ACPI again it all works with no problems, but I need its SPDIF out. Ho hum. Good luck. J ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
--- Ryan Steffes <[EMAIL PROTECTED]> wrote: > These locks ups appear to be permanent, unless > temporary can last several > hours, over night and into the next morning. > > ___ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users Ummno. That'd be pretty different (and your patience is greater than mine). Sorry I couldn't be of help, though. Steve __ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
On 10/27/05, Steve Pugh <[EMAIL PROTECTED]> wrote: --- Ryan Steffes <[EMAIL PROTECTED]> wrote:> I thought I had finally gotten this fixed with the> kernel option nolapic,> but it happened to me again. I am experiencing hard > lock ups that seem to be> related to high data throughput, but aren't> consistent enough for me to> track down. When it freezes, only hitting the reset> or power button fixes> it. Hi Ryan,I'm wondering if your situation might be similar tomine but you've certainly checked more possibletroublespots than I did, I just got lucky with thetiming of my request ;-)I was experiencing what I thought were lockups when deleting recorded programs, either through theinterface or via MythWeb. Turns out it wasn't alockup (although the interface and/or Mythweb becamefrozen, and puTTY'ing in did not work). The freezewas temporary (lasting a few to several minutes) and related to deleting *large* files from my ext3filesystem. As far as I can tell, it's been remediedby switching to XFS for my program storage drive (onlyfive days of testing so far).Just a thought, not *entirely* your situation but close enough that I thought I'd post. If yourcurious, you can search for my threads from the pastweek and change.Best, Steve__Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com___mythtv-users mailing listmythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-usersI think you had a different issue. I am using reiserfs like the original poster (I like to be able to resize lvms down), and I see a delete pause of 1-2 seconds, no lockups or anything. However, I can induce a hard lockup on my box very easily. If I run a very data intensive process I _will_ get a hard lockup. I have moved commercial detection to my slave backend beacuse every 2-3 months I will get a hard lockup if I have a lot of commercial detection jobs running. Transcoding also causes issues. Of course I have an nforce2 chipset and I believe that it is the root of the problem. The only solace I can give you is that I have managed to configure my box to have really good uptime by keeping the large intensive jobs on the slave. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
I was experiencing what I thought were lockups whendeleting recorded programs, either through the interface or via MythWeb. Turns out it wasn't alockup (although the interface and/or Mythweb becamefrozen, and puTTY'ing in did not work). The freezewas temporary (lasting a few to several minutes) and related to deleting *large* files from my ext3filesystem. As far as I can tell, it's been remediedby switching to XFS for my program storage drive (onlyfive days of testing so far). These locks ups appear to be permanent, unless temporary can last several hours, over night and into the next morning. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Occasional hard freezes
--- Ryan Steffes <[EMAIL PROTECTED]> wrote: > I thought I had finally gotten this fixed with the > kernel option nolapic, > but it happened to me again. I am experiencing hard > lock ups that seem to be > related to high data throughput, but aren't > consistent enough for me to > track down. When it freezes, only hitting the reset > or power button fixes > it. Hi Ryan, I'm wondering if your situation might be similar to mine but you've certainly checked more possible troublespots than I did, I just got lucky with the timing of my request ;-) I was experiencing what I thought were lockups when deleting recorded programs, either through the interface or via MythWeb. Turns out it wasn't a lockup (although the interface and/or Mythweb became frozen, and puTTY'ing in did not work). The freeze was temporary (lasting a few to several minutes) and related to deleting *large* files from my ext3 filesystem. As far as I can tell, it's been remedied by switching to XFS for my program storage drive (only five days of testing so far). Just a thought, not *entirely* your situation but close enough that I thought I'd post. If your curious, you can search for my threads from the past week and change. Best, Steve __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] Occasional hard freezes
I thought I had finally gotten this fixed with the kernel option nolapic, but it happened to me again. I am experiencing hard lock ups that seem to be related to high data throughput, but aren't consistent enough for me to track down. When it freezes, only hitting the reset or power button fixes it. I have an MSI K7N2 Delta 2 motherboard with an AMD Barton 2500+ in it. It has a nforce northbridge. I am passing the kernel "acpi=no noapic nolapic". I'm running 2.6.11-6mdk. I have one PVR 150. I have two hard drives, running LVM to make one video share. I'm running ivtv 0.3.9 What happens is a hard lock up. It generally happens when I'm exercising the ethernet hard. Possibly related is that my nfs speed sucks, despite being gigabit on both sides. I'm not, however, pushing it insanely hard. An example would copying files to it while watching a movie. A recording might start and suddenly hard lock. It does not always require a recording to start however. There is no other computer on the network, and I have a D-Link gigabit router, but I still get frequent time outs. It's almost as though the hard drives are just completely swamped, but I can't find a reason why they should be. Sometimes even simple things like listing a directory can take quite a while. The file system is reiserfs, the first drive is a ST3200822A, the second is a ST3250823A. They aren't running particularly hot, and smartd isn't reporting bad errors. One of the disks had a few bad sectors that I had the tool replace with reserved sectors. Can anyone give any advice on where to go from here? ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
