Hanging on boot: Triggering udev events

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
Post Reply
chaplean
Ronin
Ronin
Posts: 2
Joined: 26 May 2019, 19:30
Distribution: XFCE-4.0

Hanging on boot: Triggering udev events

Post#1 by chaplean » 26 May 2019, 20:06

Good day dear Porteusers :)

The boot process hangs on Oracle VirtualBox with the following message:

Code: Select all

Triggering udev events: /sbin/udevadm trigger --action=add
Live CD (ISO) boots without problems.
After installation, the problem appeared after several days of use.

On the real machine after installation the same situation, several weeks of notmal boot and then the same message.
No hardware change, there are 5 machines with exactly the same hardware, 2 of them are still okay, 3 of them started to show this message.
The combination of Ctrl + C makes the boot proceed.

Totally messed, can you please tell me where is the problem may be?

nanZor
Samurai
Samurai
Posts: 185
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.0 RC1 XFCE
Location: Los Angeles

Hanging on boot: Triggering udev events

Post#2 by nanZor » 27 May 2019, 10:31

If they are Intel boxes with Atom cpu's, this is pretty common. Use of cheatcode intel_idle.max_cstate=1 seems to help alleviate the problem. Still, every once in a blue moon.....

Thanks for the CTRL-C tip - I'll have to try that when mine gets cranky every 25th boot or so...
That's a UNIX book - cool. -Garth

chaplean
Ronin
Ronin
Posts: 2
Joined: 26 May 2019, 19:30
Distribution: XFCE-4.0

Hanging on boot: Triggering udev events

Post#3 by chaplean » 28 May 2019, 16:40

No, the configuration is the following: Intel(R) Celeron(R) CPU J1900 @ 1.99GHz

Digging deeper and trying to understand the difference between live and installed system I tried to remove:

Code: Select all

rm-rf /mnt/sda1/porteus/changes/etc/*
(previously backed the "etc" folder up). The boot was okay!

Then restored it to try to delete file by file inside to figure out which one is preventing the normal boot.

Code: Select all

/etc/profile.d/porteus.sh
was the reason.

Removed it and it got replaced with new one, but the system boots without hangs now.
Maybe it was corrupted?

nanZor
Samurai
Samurai
Posts: 185
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.0 RC1 XFCE
Location: Los Angeles

Hanging on boot: Triggering udev events

Post#4 by nanZor » 28 May 2019, 20:08

WOW! I just took a look at my own porteus.sh file:

The export DISTRO=porteus is in there like 50 times!

Code: Select all

export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export DISTRO=porteus
export BOOTDEV=/mnt/sda1
export BASEDIR=/mnt/sda1
export PORTDIR=/mnt/sda1/porteus
export MODDIR=/mnt/sda1/porteus/modules
export PORTCFG=/mnt/sda1/porteus/porteus-v4.0-x86_64.cfg

And at the end, the PORTCFG points to porteus-v4.0-x86_64.cfg, which we know doesn't work for the changes= code. (but does for some others)

In order for my changes= to work, it is applied to the /boot/syslinux/porteus.cfg file instead after each desired line with APPEND. Not sure if this causes confusion for that issue.

I'll delete my porteus.sh, reboot, and see what happens....

Update: after deleting my own /etc/profile.d/porteus.sh file, I have a nice clean result:

Code: Select all

export DISTRO=porteus
export BOOTDEV=/mnt/sda1
export BASEDIR=/mnt/sda1
export PORTDIR=/mnt/sda1/porteus
export MODDIR=/mnt/sda1/porteus/modules
export PORTCFG=/mnt/sda1/porteus/porteus-v4.0-x86_64.cfg
Nice find! I wonder what caused my original porteus.sh file to have all that duplicated DISTRO exports?
That's a UNIX book - cool. -Garth

nanZor
Samurai
Samurai
Posts: 185
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.0 RC1 XFCE
Location: Los Angeles

Hanging on boot: Triggering udev events

Post#5 by nanZor » 28 May 2019, 21:31

UPDATE:

Fixing the porteus.sh by deleting it, and having it be regenerated hasn't stopped my random problems at this point either. BUT only on my low end Intel boxes. It never has this problem on the AMD cpu's.

I've been chasing down intel_idle.max_cstate=1 solutions, and even blacklisting i2c components such as:

initcall_blacklist=i2c_dw_init_master

as I see i2c problems pop up often in my dmesg.

My other intel sticks are starting to act up, just like the mini-pc's, with hardware like this:
x86_64 Intel(R) Atom(TM) x5-Z8330 CPU @ 1.44GHz GenuineIntel

Not sure that it matters, but have been trying various positions of cheatcodes before specific Porteus codes like changes= in my boot line, etc.

I know it's not a solution, but I'm just getting sick of dealing with all the Intel specific issues.
That's a UNIX book - cool. -Garth

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 2361
Joined: 20 Mar 2012, 03:42
Distribution: 5.0rc1-64bit all-DE+more
Location: australia
Contact:

Hanging on boot: Triggering udev events

Post#6 by ncmprhnsbl » 28 May 2019, 22:05

porteus.sh is generated at each boot by initrd.. this section: (see at /mnt/live/linuxrc)

Code: Select all

uep=/union/etc/profile.d
uepp=$uep/porteus.sh
[ ! -d $uep ] && mkdir -p $uep
[ ! `grep -o "DISTRO=" $uepp >/dev/null 2>&1` ] && echo "export DISTRO=porteus" >> $uepp
if [ -e $uepp ]; then
	sed -i '/BOOTDEV/d' $uepp
	sed -i '/BASEDIR/d' $uepp
	sed -i '/PORTDIR/d' $uepp
	sed -i '/MODDIR/d' $uepp
	sed -i '/CHGERR/d' $uepp
	sed -i '/PORTCFG/d' $uepp
fi
echo "export BOOTDEV=$CFGDEV" >> $uepp
echo "export BASEDIR=${PTH%/*}" >> $uepp
echo "export PORTDIR=$PTH" >> $uepp
echo "export MODDIR=$MODDIR" >> $uepp
echo "export PORTCFG=$PORTCFG" >> $uepp
if [ $CHGERR ]; then echo "export CHGERR=$CHGERR" >> $uepp; fi
chmod +x $uepp
not immediately obvious to me why DISTRO=porteus is being apparently appended(or prepended)or just repeated..
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

nanZor
Samurai
Samurai
Posts: 185
Joined: 09 Apr 2019, 03:27
Distribution: Porteus 5.0 RC1 XFCE
Location: Los Angeles

Hanging on boot: Triggering udev events

Post#7 by nanZor » 28 May 2019, 23:31

I'll have to dig deeper, but I seem to see DISTRO=porteus being appended multiple times when I switch between say Graphics, Always Fresh, Copy2Ram etc. But not always. :)

Then again, I'm crashing my Intel stuff, but I'll put that in another thread so we don't dilute this one.

I'm thinking of deleting the porteus.sh either upon boot or shutdown before I get more solid facts...
That's a UNIX book - cool. -Garth

Post Reply