Firewire lockup on 2.6.22.3 in SMP but not UP, old drivers

I can pull video via firewire from a set top box using
test_mpeg2 for hours (97GB is my current record) if using a
UP kernel. The machine locks hard after about 500MB using an
SMP kernel. No messages, no altsysreq keys. It seems to
lock faster if I make the machine busy (disk and cpu). One
time it locked up running firewire_tester and once when I
switched cables between cable tv set top boxes (I think
while test_mpeg2 was running)

kernel 2.6.22.3 x86_64. I enabled all the mutex debug stuff
that I could find and turned on the NMI softlock detection
stuff. Nada. I tried the driver debug stuff but that seems
more for development (tracing).

I did not try a serial console to catch any messages that
cannot make it through syslog.

The hardware is ASUS A8V Deluxe:

00:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)

Google shows this to be common although there are two other
chip versions out there.

The PC is about two years old, runs alot of stuff (server,
compiles, etc) and runs fine SMP until I touch firewire.

I have ordered a PCI firewire card to eliminate that part of
the hardware. Its also a VIA chipset.

If that doesn't help, does that make it seem like a driver
issue? (The UP vs SMP seems an odd symptom for hardware) If
so, what's the best way to proceed? Debug old drivers or
switch to new ones? I have decades of C experience but know
nothing of 1394.

I want to use firewire with mythtv. Libs used by myth:

athlon:aab > ldd /usr/bin/myth*|grep 1394|sort|uniq
libavc1394.so.0 => /usr/lib64/libavc1394.so.0 (0x0000003141200000)
libraw1394.so.8 => /usr/lib64/libraw1394.so.8 (0x000000313f600000)
librom1394.so.0 => /usr/lib64/librom1394.so.0 (0x0000003140600000)

How close are these libraries to working with a set top box
with the new drivers?

Any quick hacks come to mind? Wrap the existing drivers in
the big kernel lock just to see if that gets things to work?
(that probably makes it obvious that I'm a kernel newbie :-)

I'll cc lkml for any general debug hints.

Thanks for any help
Andrew
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: Assuming someone else called the IRQ
    ... Maybe it is just some debug that can be safely ignored and removed from ... If two or more devices share an IRQ this is normal that when IRQ ... happens all of these drivers' IRQ routine is called. ... Try to grep kernel source for this string and ask the maintainer for the ...
    (Linux-Kernel)
  • Re: ACPI Error under 2.6.26-rc*
    ... and attach the rsdp for all of the three cases (good, ACPI Error, ... could you please attach the dmesg output of a 2.6.25.10 kernel which has ... # IPVS transport protocol load balancing support ... # Device Drivers ...
    (Linux-Kernel)
  • 2.6.25 Regression: DriveStatusError
    ... I tried all -git Kernels since begining of cycle and starting when they finaly ... Root is on a raid1 using a IDE Samsung SP1614N as hda and a SATA Samsung ... Kernel driver in use: VIA_IDE ... # AX.25 network device drivers ...
    (Linux-Kernel)
  • Re: [GIT PATCH] ACPI patches for 2.6.25-rc0 (#2)
    ... ACPI: add newline to printk ... SMP ... Kernel panic - not syncing: ... # Infrared-port device drivers ...
    (Linux-Kernel)
  • Re: Why is /sys/class/power_supply/CMB1/energy_now not exported?
    ... [fixing bad linux kernel mailing list email address - sorry, ... # IPVS transport protocol load balancing support ... # Core Netfilter Configuration ... # AX.25 network device drivers ...
    (Linux-Kernel)