No way! You're totally awesome, that was the right track...
On 26.06.2015 07:14, Martin Pitt wrote:
> This sounds like a script or program that runs for suspend tries to
> apply an "atomically update file contents" approach (write data into a
> file.new, then mv file.new file) to a /dev node, whi
On 26.06.2015 07:43, Greg KH wrote:
>> It's one byte long and this one byte is exactly the data that my
>> userspace program tried to send. But obviously my user space program
>> could not have created that node (no permission to write in /dev,
>> obviously, and my program has no suid or anything,
On Thu, 25 Jun 2015 22:07:27 +0200
"Johannes Bauer" wrote:
>
> Oh, okay, this would be insanely weird then if it were a kernel bug.
> Do you think LKML is the right place to post this to then?
>
No, I think the suspend-to-RAM scripts should be checked or asked on
the mailing list of the upstr
On Thu, Jun 25, 2015 at 09:15:18PM +0200, Johannes Bauer wrote:
> Hi list,
>
> I'm seeing a very odd issue with udev and I'm not really sure which
> component could/would be responsible -- udev is pretty much my only hope.
>
> Here's the situation: I have a USB/serial converter attached to my
> c
Hello Johannes,
Johannes Bauer [2015-06-25 21:15 +0200]:
> I'm seeing a very odd issue with udev and I'm not really sure which
> component could/would be responsible -- udev is pretty much my only hope.
Unlikely, I'm afraid.
> Now the odd thing: When I put my computer into suspend-to-RAM, I'm
>
On Thu, Jun 25, 2015 at 4:15 PM, Johannes Bauer wrote:
> Hi list,
>
> I'm seeing a very odd issue with udev and I'm not really sure which
> component could/would be responsible -- udev is pretty much my only hope.
>
Probably GregKH can assist you with this problem, udev is not at fault
because it
On 25.06.2015 21:28, Robert Milasan wrote:
> Don't think udev is creating those char devices in such a new version.
> I think is handled by the kernel.
>
> I've seen such a bug once, but it was related to /dev/null, some script
> or app was remove /dev/null and creating a normal file, don't know
On Thu, 25 Jun 2015 21:15:18 +0200
"Johannes Bauer" wrote:
> Hi list,
>
> I'm seeing a very odd issue with udev and I'm not really sure which
> component could/would be responsible -- udev is pretty much my only
> hope.
>
> Here's the situation: I have a USB/serial converter attached to my
> co
Hi list,
I'm seeing a very odd issue with udev and I'm not really sure which
component could/would be responsible -- udev is pretty much my only hope.
Here's the situation: I have a USB/serial converter attached to my
computer. It's detected as /dev/ttyUSB0. A program is started as my
local user
