Re: Linux 2.6.9-rc3
From: Gene Heskett (gene.heskett_at_verizon.net)
Date: 09/30/04
- Previous message: Bartlomiej Zolnierkiewicz: "Re: PATCH: (Test) it8212 driver for 2.6.9rc3"
- In reply to: Marcel Holtmann: "Re: Linux 2.6.9-rc3"
- Next in thread: John Cherry: "Re: Linux 2.6.9-rc3 (compile stats)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: linux-kernel@vger.kernel.org Date: Thu, 30 Sep 2004 16:41:29 -0400
On Thursday 30 September 2004 01:24, Marcel Holtmann wrote:
>Hi Gene,
>
>> >> Ok, this 2.6.9 cycle is getting too long, but here's a -rc3 and
>> >> hopefully we're getting there now.
>> >
>> > CC [M] drivers/isdn/capi/capi.o
>> >/build1/tduffy/linux-2.6.9-rc3/drivers/isdn/capi/capi.c: In
>> > function `handle_minor_send':
>> >/build1/tduffy/linux-2.6.9-rc3/drivers/isdn/capi/capi.c:538:
>> >warning: cast from pointer to integer of different size
>> >/build1/tduffy/linux-2.6.9-rc3/drivers/isdn/capi/capi.c: In
>> > function `capi_recv_message':
>> >/build1/tduffy/linux-2.6.9-rc3/drivers/isdn/capi/capi.c:649:
>> >error: `tty' undeclared (first use in this function)
>> >/build1/tduffy/linux-2.6.9-rc3/drivers/isdn/capi/capi.c:649:
>> >error: (Each undeclared identifier is reported only once
>> >/build1/tduffy/linux-2.6.9-rc3/drivers/isdn/capi/capi.c:649:
>> >error: for each function it appears in.)
>> >make[4]: *** [drivers/isdn/capi/capi.o] Error 1
>> >make[3]: *** [drivers/isdn/capi] Error 2
>> >make[2]: *** [drivers/isdn] Error 2
>> >make[1]: *** [drivers] Error 2
>> >make: *** [_all] Error 2
>> >-
>>
>> Please start from the 2.6.8.tar.gz tarball, Tom. This looks like
>> you may started from the 2.6.8.1.tar.gz.
>
>no. It is a problem of the TTY locking fixes from Alan.
>
>Regards
>
>Marcel
>
Odd, here I'm using both seriel ports, ah, wait a min.
Could a fubar'd amdump run have occured if there was traffic on the
seriel port the ups is attached to, like a quick message that there
had been a power failure, shutdown was eminent, but it came back in
about 2 seconds? There was nothing in the logs. Humm, lemme fire up
the bulldog and see if that screws things up.
That didn't seem to, and everything I looked at looked nominal,
including its own log.
The other seriel port is being used for my X10 stuff, but that would
also be logged and there is nothing there either.
How does this TTY locking thing manifest itself?
-- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Bartlomiej Zolnierkiewicz: "Re: PATCH: (Test) it8212 driver for 2.6.9rc3"
- In reply to: Marcel Holtmann: "Re: Linux 2.6.9-rc3"
- Next in thread: John Cherry: "Re: Linux 2.6.9-rc3 (compile stats)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
