Can anyone explain this error that I get on boot with Slackware 3.0,
kernel 1.3.100 complied ELF for Pentium?
Thanks in advance, Hal
Can anyone explain this error that I get on boot with Slackware 3.0,
kernel 1.3.100 complied ELF for Pentium?
Thanks in advance, Hal
Sure, read the file /usr/src/linux/Documentation/Changes which explainsQuote:>Can anyone explain this error that I get on boot with Slackware 3.0,
>kernel 1.3.100 complied ELF for Pentium?
--
Randy Young
Speaking strictly for myself!
Hi Hal,Quote:>Can anyone explain this error that I get on boot with Slackware 3.0,
>kernel 1.3.100 complied ELF for Pentium?
>Thanks in advance, Hal
sorry - this mail wont help you a lot..it just will say I am in the same
desaster. The broken flock()messsages bomb my bootup-sequence.
I was running a Linux-system with a Kernel of 1.2.13 which worked fine.
I needed to upgrade to use netatalk (Appletalk-application) and choosed
to install the 1.3.100 Kernel. After all I fetched the errormessages
you mentioned. According to the process-ids show during bootprocess
"lpd" "-bash" and "agetty" seem to be the affected parts.
Im not experienced in Linux...working with it just for a few weeks now, so
I will stand behind you and hope that any Linux-Guru comes around and tell
us a solution fpr this prob...I even dont know what effect these crashes
have on my system - did you recognize any problems?
Im using a 386/40 system / 8MB / ISA / Ethernet / Quantum 1080
Christian.
Yes absolutely *anyone* can. All they need do is scan the last fewQuote:>Can anyone explain this error that I get on boot with Slackware 3.0,
>kernel 1.3.100 complied ELF for Pentium?
--
. _\\__[oo from | Phones: +44 121 471 3789 (home)
. l___\\ /~~) /~~[ / [ | PGP-fp: D7 03 2A 4B D8 3A 05 37...
# ll l\\ ~~~~ ~ ~ ~ ~ | http://wcl-l.bham.ac.uk/~bam/
> >Can anyone explain this error that I get on boot with Slackware 3.0,
> >kernel 1.3.100 complied ELF for Pentium?
> >Thanks in advance, Hal
> Hi Hal,
> sorry - this mail wont help you a lot..it just will say I am in the same
> desaster. The broken flock()messsages bomb my bootup-sequence.
> I was running a Linux-system with a Kernel of 1.2.13 which worked fine.
--
Carlos PANTANO
www : http://eurus2.us.es/personal/pantano.html
Linux inside
--
************************************************************************
Terry R. McConnell Mathematics/215 Carnegie/Syracuse, N.Y. 13244-1150
************************************************************************
1. 1.3.95: fcntl_setlk() called by process 81 with broken flock() emulation
Those messages come from a change in fs/lock.c that just added a kprintf
statement. For all I can tell that code was executing silently in former
versions. This is hapening when agetty tries to lock the tty.
Francisco.
3. fcntl_setlk() called by process ?? with broken flock emulation
5. fcntl_setlk() called by process 73 with broken flock emulation
7. Linux-1.3.97 - kernel: fcntl_setlk() called by process 74 with broken flock() emulation
8. Printing
9. 1.3.95: fcntl_setlk() called by process 81 with broken flock() emulation
10. Linux-1.3.97 - kernel: fcntl_setlk() called by process 74 with broken flock() emulation
11. fcntl_setlk() called...w/ broken flock() emulation
12. fcntl_setlk() called... broken flock() emulation
13. fcntl_setlk() called with broken flock() emulation?