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

2007-08-23 Thread Stefan Richter
Andrew Burgess wrote: > what's the best way to proceed? Debug old drivers or > switch to new ones? As I mentioned in the branch of the discussion which lost the Cc: LKML, this kind of bug looks like requiring a good look at the interaction of raw1394's and ohci1394's locking (and maybe

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

2007-08-23 Thread Andrew Burgess
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

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

2007-08-23 Thread Andrew Burgess
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

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

2007-08-23 Thread Stefan Richter
Andrew Burgess wrote: what's the best way to proceed? Debug old drivers or switch to new ones? As I mentioned in the branch of the discussion which lost the Cc: LKML, this kind of bug looks like requiring a good look at the interaction of raw1394's and ohci1394's locking (and maybe ieee1394's,