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 because udev
>> loaded your driver.
>
> Sorry, not loading it, but
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 usin
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. The back trace indicates an out
of kernel driver I have to maintain. Yet this also indicates "Pid: 361,
comm: systemd-udevd" caused the
On 04/17/2013 04:16 PM, Lennart Poettering wrote:
On Wed, 17.04.13 16:08, Mark Hounschell (ma...@compro.net) wrote:
That looks OK. Can you try the logger thing I suggested? That should
tell us if the transition works at all...
Sorry, I had a dentist Apt.
Uh, I put this as the first command
On 04/17/2013 01:32 PM, Lennart Poettering wrote:
On Wed, 17.04.13 13:21, Mark Hounschell (ma...@compro.net) wrote:
The only thing I see in /var/log/messages is:
2013-04-17T11:36:51.667308-04:00 utils-linux su: (to lcrs) root on
/dev/ttyS0
Bu that's run on ttyS0? Is that really script
On 04/17/2013 01:12 PM, Lennart Poettering wrote:
On Wed, 17.04.13 12:22, Mark Hounschell (ma...@compro.net) wrote:
On 04/17/2013 10:27 AM, Lennart Poettering wrote:
On Wed, 17.04.13 09:46, Mark Hounschell (ma...@compro.net) wrote:
I have been using systemd to boot into a very basic target
On 04/17/2013 10:27 AM, Lennart Poettering wrote:
On Wed, 17.04.13 09:46, Mark Hounschell (ma...@compro.net) wrote:
I have been using systemd to boot into a very basic target. That
target basically executes a script. In that script we execute an "su
-m -c command user". The last
On 04/17/2013 10:09 AM, Andrey Borzenkov wrote:
On Wed, Apr 17, 2013 at 5:46 PM, Mark Hounschell wrote:
I have been using systemd to boot into a very basic target. That target
basically executes a script. In that script we execute an "su -m -c command
user". The last version of syst
I have been using systemd to boot into a very basic target. That target
basically executes a script. In that script we execute an "su -m -c
command user". The last version of systemd I have where this worked is
version 37. I'm using opensuse dist and that was in version 12.2 from
about a year a
On 04/23/2012 08:33 AM, Mark Hounschell wrote:
On 04/22/2012 06:54 AM, Lennart Poettering wrote:
On Fri, 13.04.12 13:37, Mark Hounschell (ma...@compro.net) wrote:
On 04/12/2012 08:25 AM, Mark Hounschell wrote:
On 04/11/2012 05:12 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 22:44, Mark
On 04/22/2012 06:54 AM, Lennart Poettering wrote:
On Fri, 13.04.12 13:37, Mark Hounschell (ma...@compro.net) wrote:
On 04/12/2012 08:25 AM, Mark Hounschell wrote:
On 04/11/2012 05:12 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 22:44, Mark Hounschell wrote:
Same thing. About 20 seconds
On 04/13/2012 01:37 PM, Mark Hounschell wrote:
On 04/12/2012 08:25 AM, Mark Hounschell wrote:
On 04/11/2012 05:12 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 22:44, Mark Hounschell wrote:
Same thing. About 20 seconds after reaching the target, the device
entries
show up.
Does that block
On 04/12/2012 08:25 AM, Mark Hounschell wrote:
On 04/11/2012 05:12 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 22:44, Mark Hounschell wrote:
Same thing. About 20 seconds after reaching the target, the device
entries
show up.
Does that block or return immediately?
rmmod;
modprobe; time
On 04/11/2012 05:12 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 22:44, Mark Hounschell wrote:
Same thing. About 20 seconds after reaching the target, the device entries
show up.
Does that block or return immediately?
rmmod;
modprobe; time udevadm settle
Your driver creates the
On 04/11/2012 04:17 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 22:07, Mark Hounschell wrote:
On 04/11/2012 04:02 PM, Kay Sievers wrote:
Try:
systemctl enable udev-settle.service
I should enter this command then reboot?
Yeah, there is a chance, that the uevents will block this
On 04/11/2012 04:02 PM, Kay Sievers wrote:
On Wed, Apr 11, 2012 at 21:41, Mark Hounschell wrote:
On 04/10/2012 09:10 AM, Kay Sievers wrote:
On Tue, Apr 10, 2012 at 14:36, Mark Hounschellwrote:
I am having another issue with an out of kernel "GPL" device driver not
being ava
On 04/10/2012 09:10 AM, Kay Sievers wrote:
On Tue, Apr 10, 2012 at 14:36, Mark Hounschell wrote:
I am having another issue with an out of kernel "GPL" device driver not
being available "on time" so to say. When the kernel discovers this pci card
it loads it's kern
On 04/10/2012 05:07 PM, Lennart Poettering wrote:
On Mon, 09.04.12 09:59, Mark Hounschell (ma...@compro.net) wrote:
On 04/05/2012 05:23 PM, Colin Guthrie wrote:
'Twas brillig, and Mark Hounschell at 05/04/12 18:26 did gyre and gimble:
I'm not a systemd developer but I am trying to
On 04/10/2012 10:52 AM, Kay Sievers wrote:
On Tue, Apr 10, 2012 at 16:26, Mark Hounschell wrote:
On 04/10/2012 09:10 AM, Kay Sievers wrote:
We do not support any kernel device driver which does not create the
device nodes on its own from inside the kernel. Such drivers cause
problems and
On 04/10/2012 09:10 AM, Kay Sievers wrote:
On Tue, Apr 10, 2012 at 14:36, Mark Hounschell wrote:
I am having another issue with an out of kernel "GPL" device driver not
being available "on time" so to say. When the kernel discovers this pci card
it loads it's kern
On 04/09/2012 08:06 PM, Colin Guthrie wrote:
Yep, that works. Can the NAutoVTs be set differently on a per target basis?
Not as far as I know, but you should be able to do something similar via
a conflicts directive.
e.g. if you have NAutoVTs=6 by default you can just put:
Conflicts=autovt@tt
On 04/09/2012 10:30 AM, Colin Guthrie wrote:
'Twas brillig, and Mark Hounschell at 09/04/12 14:59 did gyre and gimble:
On 04/05/2012 05:23 PM, Colin Guthrie wrote:
'Twas brillig, and Mark Hounschell at 05/04/12 18:26 did gyre and gimble:
I'm not a systemd developer but I am t
On 04/05/2012 05:23 PM, Colin Guthrie wrote:
'Twas brillig, and Mark Hounschell at 05/04/12 18:26 did gyre and gimble:
I'm not a systemd developer but I am trying to use it in place of
sysvinit to create a dedicated "run-level" for our application. Is this
list an appropri
I'm not a systemd developer but I am trying to use it in place of
sysvinit to create a dedicated "run-level" for our application. Is this
list an appropriate place to inquire about problems I have?
Thanks in advance
Mark
___
systemd-devel mailing list
24 matches
Mail list logo
