On 01/13/2014 10:20 PM, Cristian RodrÌguez wrote:
El 13/01/14 18:59, Greg KH escribiÛ:
On Mon, Jan 13, 2014 at 04:20:05PM -0500, Mark Hounschell wrote:
I'll have to admit, I don't have a very good understanding of
systemd/udev. I am using systemd/udev version 208-15.1 on an
openSuSE-13.1 dist
El 14/01/14 09:52, Mark Hounschell escribió:
Well, the systemd/udev README file from 208-15.1:
yeah, one thing is what systemd upstream requires and a completely
different one is what openSUSE can/will support or allow.
It is not just systemd really, other applications or libraries may
Am 14.01.2014 15:03, schrieb Cristian Rodríguez:
El 14/01/14 09:52, Mark Hounschell escribió:
Well, the systemd/udev README file from 208-15.1:
yeah, one thing is what systemd upstream requires and a completely different
one is what openSUSE can/will support
or allow.
It is not just
On Tue, Jan 14, 2014 at 07:52:31AM -0500, Mark Hounschell wrote:
On 01/13/2014 10:20 PM, Cristian RodrÌguez wrote:
El 13/01/14 18:59, Greg KH escribiÛ:
On Mon, Jan 13, 2014 at 04:20:05PM -0500, Mark Hounschell wrote:
I'll have to admit, I don't have a very good understanding of
El 14/01/14 11:10, Reindl Harald escribió:
which application should this be?
please state a real-world example - the Kernel usually does not break userland
Fedora 18 as example was released with Kernel 3.6 and is now at EOL on 3.11.10
Fedora 17 as example was released with Kernel 3.3 and at
On Tue, Jan 14, 2014 at 10:17:36AM -0500, Mark Hounschell wrote:
On 01/13/2014 05:00 PM, Greg KH wrote:
On Mon, Jan 13, 2014 at 01:59:39PM -0800, Greg KH wrote:
That really sounds like a driver problem, especially given your trace
shows it is failing somewhere. The udevd PID is probably
On Mon, Jan 13, 2014 at 04:20:05PM -0500, Mark Hounschell wrote:
Basically, I don't think this problem is the driver. I think the problem
is systemd/udev related so I'm posting this here hoping the get some
input on what the problem is.
If the kernel crashes, then it's kernel's fault (usually).
On Mon, Jan 13, 2014 at 04:20:05PM -0500, Mark Hounschell wrote:
I'll have to admit, I don't have a very good understanding of
systemd/udev. I am using systemd/udev version 208-15.1 on an
openSuSE-13.1 dist and a 3.4.74 kernel.
3.4? That's an incompatible thing right there with openSUSE 13.1,
On Mon, Jan 13, 2014 at 01:59:39PM -0800, Greg KH wrote:
That really sounds like a driver problem, especially given your trace
shows it is failing somewhere. The udevd PID is probably because udev
loaded your driver.
Sorry, not loading it, but rather reading sysfs files that your driver
is
El 13/01/14 18:59, Greg KH escribió:
On Mon, Jan 13, 2014 at 04:20:05PM -0500, Mark Hounschell wrote:
I'll have to admit, I don't have a very good understanding of
systemd/udev. I am using systemd/udev version 208-15.1 on an
openSuSE-13.1 dist and a 3.4.74 kernel.
3.4? That's an incompatible
10 matches
Mail list logo
