Re: FIXED POST: Two problems after upgrade to Debian 1.3
On 3 Jun, Martin Bialasinski wrote: On 3 Jun, Curtis L. Daugaard wrote: 1) Irqtune was working for me under v.1.2, but though my configured hardware is the same I now get an error message. Here is the message at boot time: irqtune: setting system IRQ priority to 3/14 irqtune: insmod failed on '/usr/lib/hwtools/irqtune_mod.o' snip irqtune is compiled to work with any kernelversion (great work). I had the same errors, so I tracked it down with the developers. The result was that modutils 2.1.23 had a bug. After upgrading to 2.1.34-5 everthing worked fine. What actually happend was that insmod dumped core when trying to load irqtune_mod.o leaving it half configured. Just update modutils and everthing will work as expected. Thanks for your post. Unfortunately upon checking I find that I already have modutils 2.1.34-5 installed. Best regards, Curt C.L. Daugaard [EMAIL PROTECTED] __ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Two problems after upgrade to Debian 1.3
Can someone enlighten me on two problems? I can't seem to solve them with the available documentation 1) Irqtune was working for me under v.1.2, but though my configured hardware is the same I now get an error message. Here is the message at boot time: " irqtune: setting system IRQ priority to 3/14 irqtune: insmod failed on '/usr/lib/hwtools/irqtune_mod.o' " Should I ignore the second message and assume the priority has been set? (Netscape does crash now and then.) 2) On boot up when syslogd starts it hangs for about 8 to 10 seconds. Not a problem I guess, but it didn'tused to do it. My thanks to anyone who can help. Curt C.L. Daugaard [EMAIL PROTECTED] ___ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Two problems after upgrade to Debian 1.3
I don't have to check the headers to see that you're using Netscape 4 because I'm using Pine and HTML email doesn't look good here. There is something in the 'preferences' to disable it. I seem to remember that it defaults to HTML allowed when first installed. If they are serious about the new 'communicator' name, they should default to plain text composition so it would communicate with elm, pine, etc. To answer part of your question: Netscape does crash now and then, especially beta versions. I notice that some of the crashes occur when I go to a site that has lots of Java. Other crashes occur because Netscape just feels like crashing at random. I wouldn't judge irqtune on the basis of Netscape behaviour. On Mon, 2 Jun 1997, Curtis L. Daugaard wrote: HTML Can someone enlighten me on two problems?nbsp; I can'tnbsp; seem to solve them with the available documentation P1) Irqtune was working for me under v.1.2, but though my configured hardware is the same I now get an error message.nbsp; Here is the message at boot time: Pnbsp; irqtune: setting system IRQ priority to 3/14 BRnbsp;nbsp; irqtune: insmod failed on '/usr/lib/hwtools/irqtune_mod.o'nbsp; PShould I ignore the second message and assume the priority has been set?nbsp; (Netscape does crash now and then.) P2) On boot up when syslogd starts it hangs for about 8 to 10 seconds.nbsp; Not a problem I guess, but it didn'tused to do it. PMy thanks to anyone who can help. PCurt PC.L. Daugaard BR[EMAIL PROTECTED] BR___ BR UL BR/UL /HTML -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . +--+ + Paul Wade Greenbush Technologies Corporation + + mailto:[EMAIL PROTECTED] http://www.greenbush.com/ + +--+ + http://www.greenbush.com/cds.html Special Linux CD offer + +--+ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Two problems after upgrade to Debian 1.3
In article [EMAIL PROTECTED] you wrote: Can someone enlighten me on two problems?nbsp; I can'tnbsp; seem to solve them with the available documentation P1) Irqtune was working for me under v.1.2, but though my configured hardware is the same I now get an error message.nbsp; Here is the message at boot time: Pnbsp; irqtune: setting system IRQ priority to 3/14 BRnbsp;nbsp; irqtune: insmod failed on '/usr/lib/hwtools/irqtune_mod.o'nbsp; I get the same thing here, but it hasn't caused any problems, AFAIK it may be that the kernel it was compiled under is different from the one that you are using. PShould I ignore the second message and assume the priority has been set?nbsp; (Netscape does crash now and then.) I don't think it will be set, but this should affect netscape AFAIK. P2) On boot up when syslogd starts it hangs for about 8 to 10 seconds.nbsp; Not a problem I guess, but it didn'tused to do it. There was a change in the code so that it waits for 10 seconds to avoid a race condition - nothing to worry about, besides which Debian is so stable that you hardly ever have to reboot :) Adrian -- email: [EMAIL PROTECTED] | Artificial intelligence - the http://www.poboxes.com/adrian.bridgett | art of making computers act PGP key available on public key servers | like those in the movies -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
FIXED POST: Two problems after upgrade to Debian 1.3
My apologies to the debian-user list for my faulty original post. I had just installed Netscape 4.0 and forgot to disable HTML in its mail package (which is enabled by default). Let me try again. Can someone enlighten me on the following, which I can't seem to solve with the available documentation? 1) Irqtune was working for me under v.1.2, but though my configured hardware is the same I now get an error message. Here is the message at boot time: irqtune: setting system IRQ priority to 3/14 irqtune: insmod failed on '/usr/lib/hwtools/irqtune_mod.o' Should I ignore the second message and assume the priority has been set? (Netscape does crash now and then, one of the symptoms irqtune is said to address.) 2) The second problem concerning syslogd hanging has been solved in a posted response to my original defective post. Thanks again. Curt C.L. Daugaard [EMAIL PROTECTED] ___ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: FIXED POST: Two problems after upgrade to Debian 1.3
On 3 Jun, Curtis L. Daugaard wrote: 1) Irqtune was working for me under v.1.2, but though my configured hardware is the same I now get an error message. Here is the message at boot time: irqtune: setting system IRQ priority to 3/14 irqtune: insmod failed on '/usr/lib/hwtools/irqtune_mod.o' Should I ignore the second message and assume the priority has been set? (Netscape does crash now and then, one of the symptoms irqtune is said to address.) irqtune is compiled to work with any kernelversion (great work). I had the same errors, so I tracked it down with the developers. The result was that modutils 2.1.23 had a bug. After upgrading to 2.1.34-5 everthing worked fine. What actually happend was that insmod dumped core when trying to load irqtune_mod.o leaving it half configured. Just update modutils and everthing will work as expected. Ciao, Martin -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
upgrade to debian 1.3
During the upgrade i saw the following message: --- Setting up libg++27-dev (2.7.2.1-9) ... Update-menus: Dpkg is locking dpkg status area: forking to background and wait for /var/lib/dpkg/lock to become unlocked. Setting up lynx (2.7-2) ... Configuration file `/etc/lynx.cfg' == File on system created by you or by a script. == File also in package provided by package maintainer. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version Z : background this process to examine the situation The default action is to keep your current version. *** lynx.cfg (Y/I/N/O/Z) [default=N] ? unable to lock dpkg status database(/var/lib/dpkg/lock) This means your system is messed up badly. Aborting. -- Somebody can shed some light on this ? Regards, Danny -- Danny ter Haar | Cistron Internet Services | Unix Internet [EMAIL PROTECTED] SP6| finger [EMAIL PROTECTED] for PGP-key |specialists --0.68 seconds which for an android is an eternity-+31-172-419445--- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: upgrade to debian 1.3
On Apr 29, Danny ter Haar wrote During the upgrade i saw the following message: Update-menus: Dpkg is locking dpkg status area: forking to background and wait for /var/lib/dpkg/lock to become unlocked. Setting up lynx (2.7-2) ... Configuration file `/etc/lynx.cfg' [...] The default action is to keep your current version. *** lynx.cfg (Y/I/N/O/Z) [default=N] ? unable to lock dpkg status database(/var/lib/dpkg/lock) This means your system is messed up badly. Aborting. Somebody can shed some light on this ? Just a guess (Joost, please comment): update-menus is expensive to run, so it was modified not to run for each individual package install, but for each dpkg install session. This was done by some form of waiting until dpkg's lock was removed, and then locking it for update-menus. Your example shows that this does (unfortunately) not indicate that the dpkg run is complete, and that this interferes with normal dpkg operation. Maybe this is a solution: let update-menus use a lock file of its own to prevent concurrent runs, and have the single active run wait until dpkg's lock file is gone before doing the expensive operations? Greetings, Ray -- ART A friend of mine in Tulsa, Okla., when I was about eleven years old. I'd be interested to hear from him. There are so many pseudos around taking his name in vain. - The Hipcrime Vocab by Chad C. Mulligan -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: upgrade to debian 1.3
On Apr 29, Danny ter Haar wrote
During the upgrade i saw the following message:
Update-menus: Dpkg is locking dpkg status area: forking to background
and wait for /var/lib/dpkg/lock to become unlocked.
Setting up lynx (2.7-2) ...
Configuration file `/etc/lynx.cfg'
[...]
The default action is to keep your current version.
*** lynx.cfg (Y/I/N/O/Z) [default=N] ? unable to lock dpkg status
database(/var/lib/dpkg/lock)
This means your system is messed up badly. Aborting.
Somebody can shed some light on this ?
Just a guess (Joost, please comment): update-menus is expensive to run
Yes, but that's not the main reason.
This was done by some form of waiting until dpkg's
lock was removed, and then locking it for update-menus. Your example shows
that this does (unfortunately) not indicate that the dpkg run is complete,
and that this interferes with normal dpkg operation.
To be more precise, I try to lock the dpkg file, and then
_immediately_ afterwards, unlock it:
fd=open(DPKG_LOCKFILE, O_RDWR|O_CREAT|O_TRUNC, 0660);
fl.l_type= F_WRLCK;
fl.l_whence= SEEK_SET;
fl.l_start= 0;
fl.l_len= 1;
if (fcntl(fd,F_SETLK,fl) == -1) {
if (errno == EWOULDBLOCK || errno == EAGAIN)
return 1;
cerrunable to lock dpkg status database(DPKG_LOCKFILE)endl
This means your system is messed up badly. Aborting.;
exit(1);
}
fl.l_type= F_UNLCK;
fl.l_whence= SEEK_SET;
fl.l_start= 0;
fl.l_len= 1;
if (fcntl(fd,F_SETLK,fl) == -1){
Note also that the error message is from update-menus
(yes, I just chaged update-menus to put it's name before that error
message). The code comes directly from dpkg, btw, but I chaged the
error message. At the line of the unable to ..., dpkg has (dpkg/lib/lock.c):
if (fcntl(dblockfd,F_SETLK,fl) == -1) {
if (errno == EWOULDBLOCK || errno == EAGAIN)
ohshit(status database area is locked - another dpkg/dselect is running)
;
ohshite(unable to lock dpkg status database);
Maybe this is a solution: let update-menus use a lock file of its own to
prevent concurrent runs, and have the single active run wait until dpkg's
lock file is gone before doing the expensive operations?
update-menus acutally does have it's own lock file (/var/run/update-menus.pid).
The main reason why update-menus checks for a running dpkg is that
it has to know what packages are installed (to create the menu's
files). While dpkg is still running, it doesn't update the
/var/lib/dpkg/info/status file, and thus update-menus would see the
old status file (the one from before dpkg was started).
I'm not sure there was actually an error in the above lynx install
session (appart from the possibly wrong error message) Apparently, the
manpage for fcntl has:
F_SETLK The lock is set (when l_type is F_RDLCK or
F_WRLCK) or cleared (when it is F_UNLCK). If the
lock is held by someone else, this call returns
-1 and sets errno to EACCES or EAGAIN.
So, probably I should also test for EACCES. (why doesn't dpkg does this?)
Anybody know more about this?
--
joost witteveen, [EMAIL PROTECTED]
#!/bin/perl -sp0777iX+d*lMLa^*lN%0]dsXx++lMlN/dsM0j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$kSK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: upgrade to debian 1.3
In message [EMAIL PROTECTED] you wrote: ... I'm not sure there was actually an error in the above lynx install session (appart from the possibly wrong error message) ... If the lock is held by someone else, this call returns -1 and sets errno to EACCES or EAGAIN. So, probably I should also test for EACCES. (why doesn't dpkg does this?) Perhaps dpkg mmaps the file, so it always gets EAGAIN. Anyway, I had this error while dpkg was installing hdimage for dosemu. Everything got installed fine, so the error message is in error. :) You probably should log messages via syslog so that they don't mess with output from foreground jobs. AFA I can see open() should block until dpkg run is complete -- the only test I can think of is to poll with non-blocking open() and see if it makes any difference. Dimitri -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: upgrade to debian 1.3
In message [EMAIL PROTECTED] you wrote:
...
I'm not sure there was actually an error in the above lynx install
session (appart from the possibly wrong error message)
... If the
lock is held by someone else, this call returns
-1 and sets errno to EACCES or EAGAIN.
So, probably I should also test for EACCES. (why doesn't dpkg does this?)
Perhaps dpkg mmaps the file, so it always gets EAGAIN.
No, it doesn't (read the code I showed, and you'll see that
errno excactly is not EAGAIN, that's what I test for).
Anyway, I had this error while dpkg was installing hdimage for dosemu.
Everything got installed fine, so the error message is in error. :)
update-menus wasn't run, that's all (very slight error).
You probably should log messages via syslog so that they don't mess
with output from foreground jobs.
Fortunatly I didn't, as otherwise people never would see when it happens.
I am glad I now at least know that the fcntl() call also can give
something else than EWOULDBLOCK or EAGAIN (that's what these
messages prove), I'll just go and check what the other thing
is (probably it's EACCES).
AFA I can see open() should block
until dpkg run is complete
The fd=open(DPKG_LOCKFILE, O_RDWR|O_CREAT|O_TRUNC, 0660);
call above doesn't block. (otherwise, none of the messages above
would appear!).
-- the only test I can think of is to poll
with non-blocking open() and see if it makes any difference.
So this is not needed.
--
joost witteveen, [EMAIL PROTECTED]
#!/bin/perl -sp0777iX+d*lMLa^*lN%0]dsXx++lMlN/dsM0j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$kSK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
