Am 25.06.2013 16:18, schrieb Dean Jenkins:
On 17/05/13 05:43, Alexander Holler wrote:
To reproduce it, call rfcomm connect /dev/rfcommN and after the
connection to the remote device happened, power down the remote device
and wait 20s (the timeout until a connection drop will be discovered).
I
On 17/05/13 05:43, Alexander Holler wrote:
Am 16.05.2013 23:53, schrieb Peter Hurley:
And the tty layer can't really _prevent_ the tty driver from mishandling
the port kref.
Especially since it seemed to have been worked before tty_ports got
introduced.
Well, at the time tty_port was introdu
Am 16.05.2013 23:53, schrieb Peter Hurley:
> And the tty layer can't really _prevent_ the tty driver from mishandling
> the port kref.
>
>> Especially since it seemed to have been worked before tty_ports got
>> introduced.
>
> Well, at the time tty_port was introduced to RFCOMM, there was nothin
On 05/16/2013 09:59 AM, Alexander Holler wrote:
Am 16.05.2013 15:47, schrieb Peter Hurley:
On 05/16/2013 02:45 AM, Alexander Holler wrote:
Hello,
after some pain because the "big step" (ecbbfd4) happened while the
support for my AMD CPU was broken and thus git bisect hit a series of
kernels wh
Am 16.05.2013 15:47, schrieb Peter Hurley:
On 05/16/2013 02:45 AM, Alexander Holler wrote:
Hello,
after some pain because the "big step" (ecbbfd4) happened while the
support for my AMD CPU was broken and thus git bisect hit a series of
kernels which didn't boot, I've finally found the cause for
On 05/16/2013 02:45 AM, Alexander Holler wrote:
Hello,
after some pain because the "big step" (ecbbfd4) happened while the support for
my AMD CPU was broken and thus git bisect hit a series of kernels which didn't boot, I've
finally found the cause for a memory corruption: tty_ldisc_release().
Am 16.05.2013 08:45, schrieb Alexander Holler:
tty_port is self-destructing, that means it destroys itself in
tty_port.c:tty_port_destructor() when the last reference is gone. E.g.
in case of rfcomm this happens with the call to tty->ops->close() in
tty_io.c:tty_release().
The problem here is t
Hello,
after some pain because the "big step" (ecbbfd4) happened while the
support for my AMD CPU was broken and thus git bisect hit a series of
kernels which didn't boot, I've finally found the cause for a memory
corruption: tty_ldisc_release().
What happens is the following:
tty_port is s
8 matches
Mail list logo
