| Summary: | sys-fs/e4rat: e4rat-preload looks to break rc_hotplug | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
| Component: | Current packages | Assignee: | Markos Chandras (RETIRED) <hwoarang> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | openrc |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
/var/lib/e4rat/startup.log
/var/log/rc.log |
||
|
Description
Pacho Ramos
2011-12-11 13:13:54 UTC
Will CC openrc people as maybe they will know what is going wrong here or, at least, how to debug the problem Created attachment 295463 [details]
/var/lib/e4rat/startup.log
We're going to need a lot more of the openrc boot log. Do you have rc_parallel on? Is e4rat loading any kernel modules? Created attachment 295481 [details]
/var/log/rc.log
(In reply to comment #3) > We're going to need a lot more of the openrc boot log. I have attached /var/log/rc.log for now > Do you have rc_parallel on? Yes, will try to disable it > Is e4rat loading any kernel modules? Doesn't seem to be loading any module :/ Is udev actually being loaded? I don't see it in your logs. (In reply to comment #5) [...] > > Do you have rc_parallel on? > > Yes, will try to disable it It's the same :( (In reply to comment #6) > Is udev actually being loaded? I don't see it in your logs. It looks to be running: # ps axu | grep udev root 167 0.0 0.0 12764 880 ? S<s 19:05 0:00 /sbin/udevd --daemon root 435 0.0 0.0 12884 904 ? S< 19:05 0:00 /sbin/udevd --daemon root 436 0.0 0.0 12884 832 ? S< 19:05 0:00 /sbin/udevd --daemon root 2827 0.0 0.0 10488 836 pts/0 S+ 19:06 0:00 grep --colour=auto udev Today it works ok again :-O Maybe the problem was caused by me only "rebooting" yesterday and now, after a "poweroff", it behaves ok again even with e4rat (looks strange to me but now it works for some reason and yesterday not) (In reply to comment #8) > Today it works ok again :-O > > Maybe the problem was caused by me only "rebooting" yesterday and now, after a > "poweroff", it behaves ok again even with e4rat (looks strange to me but now it > works for some reason and yesterday not) Yeah, I have just seen it tends to fail when "rebooting" but always work when I poweroff and, then, poweron my laptop :/ My bluetooth device is an external USB one that is always connected to the laptop Since bluetooth script has now completely changed as was demonstrated its old way of using rc_hotplug was undesired, I guess this is obsolete now |
