hello, when kudzu starts it gives
Checking for hardware changes/etc/rc.d/init.d/kudzu: line 23: 3937 Illegal instruction /sbin/kudzu $KUDZU_ARGS [FAILED] in "start" function there is
/sbin/kudzu $KUDZU_ARGS -z || /sbin/kudzu $KUDZU_ARGS
instead of typical
/usr/sbin/kudzu $KUDZU_ARGS -t 30
if [ "$RETVAL" -eq 5 ]; then echo -n $"Hardware configuration timed out." echo -n $"Run '/usr/sbin/kudzu' from the command line to re-detect." initlog -n kudzu -s $"Hardware configuration timed out." initlog -n kudzu -s $"Run '/usr/sbin/kudzu' from the command line to re-detect." fi
Any reason for that? Gianluca
On Thu, Dec 29, 2005 at 07:45:03AM +0100, Gianluca Cecchi wrote:
hello, when kudzu starts it gives
Checking for hardware changes/etc/rc.d/init.d/kudzu: line 23: 3937 Illegal instruction /sbin/kudzu $KUDZU_ARGS [FAILED]
What CPU are you running on ? Did you move disks between two different machines by any chance ?
Do you get the same thing when you run it by hand from the command line ? If so, running it under gdb (with the kudzu-debuginfo package installed) should give you a backtrace of where the problem occured.
Dave
It is strange to reproduce, as kudzu is a shell script. And right this boot time it gave no error. Analyzing commands, it seems that the offending command is kudzu -z || kudzu Tipically tou have sometimes the illegal option error, sometimes not, and it happens with the second kudzu in the command So I tried a two times sequence with: [root@fedora ~]# kudzu -z ||gdb kudzu GNU gdb Red Hat Linux (6.3.0.0-1.94rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run Starting program: /sbin/kudzu Reading symbols from shared object read from target memory...done. Loaded system supplied DSO at 0x3b4000
Program exited normally. (gdb) quit
[root@fedora ~]# kudzu -z ||gdb kudzu GNU gdb Red Hat Linux (6.3.0.0-1.94rh) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) run Starting program: /sbin/kudzu Reading symbols from shared object read from target memory...done. Loaded system supplied DSO at 0x745000
Program received signal SIGILL, Illegal instruction. 0x0805ee2f in run_vm86 () at lrmi.c:733 733 asm volatile ( (gdb) (gdb) quit The program is running. Exit anyway? (y or n) y
I don't know if other answers in last error could be more useful... HIH, Gianluca
2005/12/29, Gianluca Cecchi gianluca.cecchi@gmail.com:
hello, when kudzu starts it gives
Checking for hardware changes/etc/rc.d/init.d/kudzu: line 23: 3937 Illegal instruction /sbin/kudzu $KUDZU_ARGS [FAILED] in "start" function there is
/sbin/kudzu $KUDZU_ARGS -z || /sbin/kudzu $KUDZU_ARGS
instead of typical
/usr/sbin/kudzu $KUDZU_ARGS -t 30 if [ "$RETVAL" -eq 5 ]; then echo -n $"Hardware configuration timed out." echo -n $"Run '/usr/sbin/kudzu' from the command line to
re-detect." initlog -n kudzu -s $"Hardware configuration timed out." initlog -n kudzu -s $"Run '/usr/sbin/kudzu' from the command line to re-detect." fi
Any reason for that? Gianluca
devel@lists.stg.fedoraproject.org