--- Begin Message ---
- To: "Jonathan Nieder" <jrnieder@gmail.com>
- Subject: Re: general protection fault in a ttyACM0 access
- From: "Albert van der Horst" <albert@spenarnc.xs4all.nl>
- Date: Wed, 19 Dec 2012 01:43:17 +0100
- Message-id: <2fd0f3946df93ca71672bff90165bd39.squirrel@webmail.xs4all.nl>
- In-reply-to: <[🔎] 20121206070343.GD3029@elie.Belkin>
- References: <20121018142105.3885.6395.reportbug@cherry.spenarnc.xs4all.nl> <20121124221239.GA23157@elie.Belkin> <63c5e744ee30be765788dcef7038c590.squirrel@webmail.xs4all.nl> <CAFzf2XwfZi_PZp0DGuzjP8DY6mDchN_JbH1sG7G3EvS2nb9h=A@mail.gmail.com> <652c859e24fc001bc1f2fc869bda6ff1.squirrel@webmail.xs4all.nl> <[🔎] 20121206070343.GD3029@elie.Belkin>
Jonathan Nieder schreef:
> Albert van der Horst wrote:
>> Jonathan Nieder schreef:
>
>>> Do you mind if I forward your message to the bug log? Do you
>>> have "dmesg" output from that experiment (since it should include a
>>> fuller trace)?
>>
>> You can do whatever is necessary wih the information I provided.
>
> Thanks much.
>
>> I don't have a dmesg, as the system has rebooted in between.
>> (For the moment, I have a similar problem with windows xt, but on
>> linux I have a workaround.)
>
> If you have time to sift through log files, it might be possible to
> find a log of the corresponding boot somewhere in /var/log/dmesg* or
> /var/log/syslog*.
I have been fooling around and with some effort reproduced the error.
This may be caused by a totally faulty program in a SBC but the driver
shouldn't crash.
Please find attached a file with a dmesg log. The configuration of my
system has not
changed.
>
> Good night,
> Jonathan
>
Groetjes Albert
--
Suffering is the prerogative of the strong, the weak -- perish.
Albert van der Horst
--- End Message ---