[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#391007: marked as done (linux-image-2.6-686: ieee1394 problems width dvgrab)

Your message dated Thu, 4 Dec 2008 23:33:42 +0100
with message-id <20081204223342.GA7785@galadriel.inutil.org>
and subject line Re: linux-image-2.6-686: ieee1394 problems width dvgrab
has caused the Debian Bug report #391007,
regarding linux-image-2.6-686: ieee1394 problems width dvgrab
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
391007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391007
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6-686
Version: 2.6.17+2
Severity: important


<mylife>
When I went back from holidays, around mid-August, I grabbed
my videos from my Panasonic NV-GS17 mini-DV camera with
dvgrab with no problem at all, on my Dell Latitude D800
with a Pentium M 1.70 Ghz, 2Mb cache and 1 Gb of RAM.
</mylife>

Now whenever I use dvgrab even for live capture, I've got hundreds 
of lines identical to the following one in the kernel logs : 

--- CUT ---
ohci1394: gw-host0: Waking dma ctx=1 ... processing is probably too slow
--- CUT ---

The resulting files show fine in mplayer or videolan but are accelerated,
making audio almost inaudible and people run instead of walk.

Since August I ran several system upgrades, and I don't remember
the kernel version which worked at that time.

Following some instructions I found on the web I used hdparm to 
enable DMA, 32 bit I/O, Multiple sectors, and Interrupt unmask on my 
hard disk, and also set dma, interrupt_unmask and 32 bits I/O on the 
internal DVD burner. Still no luck.

Any idea of what could be wrong ?

TIA

Jerome Alet

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=fr_FR@euro, LC_CTYPE=fr_FR@euro (charmap=ISO-8859-15)

Versions of packages linux-image-2.6-686 depends on:
ii  linux-image-2.6.17-2-686      2.6.17-9   Linux 2.6.17 image on PPro/Celeron

linux-image-2.6-686 recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Thu, Dec 04, 2008 at 11:12:58PM +0100, Moritz Muehlenhoff wrote:
> On Wed, Oct 04, 2006 at 11:11:35AM +0200, Jerome.ALET@unice.fr wrote:
> > Package: linux-image-2.6-686
> > Version: 2.6.17+2
> > Severity: important
> > 
> > 
> > <mylife>
> > When I went back from holidays, around mid-August, I grabbed
> > my videos from my Panasonic NV-GS17 mini-DV camera with
> > dvgrab with no problem at all, on my Dell Latitude D800
> > with a Pentium M 1.70 Ghz, 2Mb cache and 1 Gb of RAM.
> > </mylife>
> > 
> > Now whenever I use dvgrab even for live capture, I've got hundreds 
> > of lines identical to the following one in the kernel logs : 
> > 
> > --- CUT ---
> > ohci1394: gw-host0: Waking dma ctx=1 ... processing is probably too slow
> > --- CUT ---
> > 
> > The resulting files show fine in mplayer or videolan but are accelerated,
> > making audio almost inaudible and people run instead of walk.
> > 
> > Since August I ran several system upgrades, and I don't remember
> > the kernel version which worked at that time.
> 
> Does this error still occur with more recent kernel versions?

Submitter's address bounces. Closing the bug.

Cheers,
        Moritz

--- End Message ---
Reply to: