[Pkg-lirc-maint] Bug#373871: [lirc] Debian bug #373871 - Are you still seeing this?

[Mario L]

One more thing, there is a minor difference in the dmesg output between the
two.  On machines that do not work, there is an extra poll called

[26290.389273] lirc_dev (lirc_serial[1]): open called
> [26290.389297] lirc_serial: Interrupt 4, port 03f8 obtained
> [26290.389309] lirc_dev (lirc_serial[1]): open result = 0
> [26290.389315] lirc_dev (lirc_serial[1]): ioctl called (0x80046900)
> [26290.389319] lirc_dev (lirc_serial[1]): ioctl result = 0
> [26290.389324] lirc_dev (lirc_serial[1]): ioctl called (0x40046911)
> [26290.389328] lirc_dev (lirc_serial[1]): ioctl called (0x40046912)
> [26290.389333] lirc_dev (lirc_serial[1]): ioctl result = 0
> [26290.389337] lirc_dev (lirc_serial[1]): ioctl called (0x80046907)
> [26290.389342] lirc_dev (lirc_serial[1]): ioctl result = -515
> [26290.389351] lirc_dev (lirc_serial[1]): poll called
> [26290.389355] lirc_dev (lirc_serial[1]): poll result = 0
> [26290.389376] lirc_dev (lirc_serial[1]): write called
> [26290.451157] lirc_dev (lirc_serial[1]): poll called
> [26290.451163] lirc_dev (lirc_serial[1]): poll result = 0
> [26290.451205] lirc_dev (lirc_serial[1]): poll called
> [26290.451208] lirc_dev (lirc_serial[1]): poll result = 0
> [26290.451855] lirc_dev (lirc_serial[1]): close called
> [26290.451874] lirc_serial: freed IRQ 4
>


On 8/2/06, Mario L <superm1 at gmail.com> wrote:
>
> By no Hitch, I mean I didn't have to do anything special other then
> install dapper, update to latest security updates, and install the lirc
> packages that I built.
>
> I am attaching a text file with several logs as well as indicating the
> method that I used to enable debug mode (after the app was compiled for
> debug)
>
> Regards,
>
> Mario
>
> On 7/30/06, Amaya <amaya at debian.org> wrote:
>
> > Mario L wrote:
> > > Still having the troubles - but I Have a minor update to complicate
> > > things.
> >
> > :(
> >
> > > I attempted this on a roomate's laptop that has a serial port.
> > > Installed again from a fresh updated dapper.  Grabbed the same lirc
> > > debs that I built on my other x86 machine, threw them on there and
> > > grabbed the same conf files.  The thing works no hitch.
> >
> > Sorry, what do you mean by "The thing works no hitch"?
> >
> > > I dont know what to make of this now considering the fact.  I
> > > recompiled lirc in debug mode and verified that the same things are
> > > being sent out of each computer with a diff of the output log.  Its
> > > verbose the same (other then times being sent :))
> >
> > Having that log might help me submit a more complete report for
> > upstream, do you still have it?
> >
> > > I'm really thinking this must be related to some sort of timing issue,
> > > perhaps this laptop of my roomate's doesn't support some kind of
> > > higher speed clocking that my desktop and myth machine both do.
> >
> > No idea.
> >
> > --
> >   ·''`.          Policy is your friend. Trust the Policy.
> > : :' :     Love the Policy. Obey the Policy. -- Lars Wirzenius
> > `. `'           Proudly running unstable Debian GNU/Linux
> >    `-     www.amayita.com   www.malapecora.com  www.chicasduras.com
> >
>
>
>
> --
> Mario Limonciello
> superm1 at gmail.com
>
>


-- 
Mario Limonciello
superm1 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/pkg-lirc-maint/attachments/20060802/d1fb0c6c/attachment-0001.html