Linux-Development-Sys Digest #663, Volume #6 Fri, 30 Apr 99 00:14:03 EDT
Contents:
Re: pc-speaker driver (Moritz Franosch)
Re: Help with compiling mico / What is Error 139 ("Royce")
Re: libpthread.so not thread safe? ("Michael Chen")
Re: hda:general protection: 0040 (David Andruczyk)
Re: RFS? Re: NFS vs DFS (John Hughes)
My zombie server (Vincent Stoessel)
un.h missing sun_len (Wlmet)
Re: Threads >> PThreads or LinuxThreads?? (Harald Schreiber)
Calibri Firewall/Router on Ebay. ("Jack Levin")
Re: pc-speaker driver (Kent Friis)
Re: Is Linux Y2K compliant? (Neil Schemenauer)
Re: how to access raw memory? (Tom Goodale)
Re: Powwerdown on shutdown for 2.2.6 laptop (Allin Cottrell)
Re: NFS vs DFS (Leslie Mikesell)
Re: RFS? Re: NFS vs DFS (Leslie Mikesell)
----------------------------------------------------------------------------
From: Moritz Franosch <[EMAIL PROTECTED]>
Subject: Re: pc-speaker driver
Date: 29 Apr 1999 21:37:33 +0200
> I would like to use the PC-speaker in lieu of
> a sound card, but the major option in this area,
> a module called pcsnd, does not want to compile
> on my system. (It's asking for linux/pcsnd.h,
> which neither 2.0.35 nor 2.2.6 kernels provide.)
A kernel patch is needed.
Download site is
http://www.imladris.demon.co.uk/pcsp/
This patch should generate '/usr/src/linux/include/linux/pcsnd.h'
among a lot of other things.
After some problems I got the patched kernel to compile, but the
program pcsel in the pcsnd-kit reported
/dev/pcsp: Operation not supported by device
The module loaded with a message, however, and there was no error
message in /var/log/messages or /var/log/warn.
If anyone knows solutions, please tell me.
Moritz
------------------------------
From: "Royce" <[EMAIL PROTECTED]>
Subject: Re: Help with compiling mico / What is Error 139
Date: Thu, 29 Apr 1999 16:49:44 +0100
I have just read the FAQ and so I installed linux on another PC and it died
at the same point??
If I do another make all after it dies it gets a bit further and dies again.
Any Ideas?
Royce
J.H.M. Dassen (Ray) wrote in message <7g9epp$kdg$[EMAIL PROTECTED]>...
>Royce <[EMAIL PROTECTED]> wrote:
>>/home/mico/./admin/mkdepend -I../include -O -fno-exceptions *.cc >>
>>.depend
>>make[1]: *** [.depend] Error 139 <---- What is this
>
>Error 139 corresponds to signal 11. This may be cause by hardware troubles;
>see the FAQ http://www.bitwizard.nl/sig11/ .
>
>HTH,
>Ray
>--
>J.H.M. Dassen | RUMOUR Believe all you hear. Your world
may
>[EMAIL PROTECTED] | not be a better one than the one the blocks
> | live in but it'll be a sight more vivid.
> | - The Hipcrime Vocab by Chad C.
Mulligan
------------------------------
From: "Michael Chen" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.help
Subject: Re: libpthread.so not thread safe?
Date: Thu, 29 Apr 1999 09:02:41 -0700
Marcus pointed out that libpthread.so has known problem with shared library, then
1. Do you know for fact that linking with libthread.a solves the problem?
2. Is there anyother library that has the similar problem, i.e. has weak link in libc?
Thank you
--Michael
Marcus Sundberg wrote in message <[EMAIL PROTECTED]>...
>Michael Chen wrote:
>>
>> I have a multi-threaded shared-library module compiled with gcc on Linux.
>> If I link it with the default -shared option, it is NOT thread safe. At run-time,
>> it often deadlock in calls to pthread_mutex_trylock(). xxgdb reveals that
>> the mutex is not properly zero out after pthread_mutex_init().
>>
>> Then I tried explicitly include "/usr/lib/libpthread.a" when I link the .so,
>> multi-threading seem to work fine.
>>
>> Is there something about libpthread.so that I don't know?
>
>This is a known bug in the dynamic linker of Linux.
>libc.so contains stub implementations of the pthread_mutex* functions
>and libpthread.so (and libpthread.a) contains the real functions.
>This way you do not bloat libc.so and get rid of the runtime overhead
>for non-threaded apps, while threaded apps who are linked to
>libpthread will use the real functions from there.
>
>Unfortunately when you link a shared library with libpthread.so this
>"overloading" doesn't work, unless every application is explicitly
>linked to libpthread too. If you run "ldd app" you'll see that
>libpthread.so is after libc.so in the list. I believe it _should_
>still work because the symbols in libc.so should be weak symbols,
>but for some reason it doesn't.
>
>A possible workaround is to dlopen() libpthread.so and explicitly
>use dlsym() to get the right functions. Note that this is non-portable
>because some OSes contains stuff like
>#define pthread_mutex_init _pthread_mutex_init
>in pthread.h
>
>My experience is that multithreaded shared libraries don't work
>well in many current UNIX variants.
>
>//Marcus
>--
>-------------------------------+------------------------------------
> Marcus Sundberg | http://www.stacken.kth.se/~mackan/
> Royal Institute of Technology | Phone: +46 707 295404
> Stockholm, Sweden | E-Mail: [EMAIL PROTECTED]
------------------------------
Date: Thu, 29 Apr 1999 12:28:10 -0400
From: David Andruczyk <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: hda:general protection: 0040
Roope Anttinen wrote:
>
> Hi,
>
> Do anyone have a clue what causes this when booting:
>
> Memory: sized by int13 088h
> Console: 16 point font, 400 scans
> Console: colour VGA+ 80x25, 1 virtual console (max 63)
> pcibios_init : BIOS32 Service Directory structure at 0x000f0280
> pcibios_init : BIOS32 Service Directory entry at 0xf0210
> pcibios_init : PCI BIOS revision 2.10 entry at 0xf0200
> Probing PCI hardware.
> Calibrating delay loop.. ok - 332.60 BogoMIPS
> Memory: 30952k/32768k available (656k kernel code, 384k reserved, 776k data)
> Swansea University Computer Society NET3.035 for Linux 2.0
> NET3: Unix domain sockets 0.13 for Linux NET3.035.
> Swansea University Computer Society TCP/IP for NET3.034
> IP Protocols: IGMP, ICMP, UDP, TCP
> VFS: Diskquotas version dquot_5.6.0 initialized
> Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
> Checking 'hlt' instruction... Ok.
> Intel Pentium with F0 0F bug - workaround enabled.
> alias mapping IDT readonly ... ... done
> Linux version 2.0.36 (root@atmlin03) (gcc driver version egcs-2.91.60 19981201
>(egcs-1.1.1 release) executing gcc version 2.7.2.3) #3 Wed Apr 28 18:16:53 EEST 1999
> Starting kswapd v 1.4.2.2
> Serial driver version 4.13p with no serial options enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> PS/2 auxiliary pointing device detected -- driver installed.
> APM BIOS version 1.2 Flags 0x07 (Driver version 1.2)
> Entry fdd6:0 cseg16 f000 dseg 40 cseg len ffff, dseg len ffff
> Connection version 1.1
> AC on line, battery status high, battery life 100%
> battery flag 0x01, battery life unknown
> Real Time Clock Driver v1.09
> hda: IBM-DDLA-21620, 1551MB w/96kB Cache, CHS=788/64/63
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> Partition check:
> hda:general protection: 0040
> CPU: 0
> EIP: 2040:[<0000015c>]
> EFLAGS: 00010246
> eax: 00002040 ebx: 0000001e ecx: 0000000a edx: 00000000
> esi: 001b784c edi: 00000000 ebp: 0000166d esp: 001b77b0
> ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: 0018
> Process swapper (pid: 0, process nr: 0, stackpage=001b5870)
> Stack: 00000040 00000000 00000123 00004f01 00000046 00000021 0018096a 00000010
> 00000246 00000018 0000002b 00000018 00000018 0000001e 001b784c 00000000
> 0000166d 001099b8 00109929 00109997 001b8024 0010aa79 00000100 0010968c
> Call Trace: [<0018096a>] [<001099b8>] [<00109929>] [<00109997>] [<0010aa79>]
>[<0010968c>] [<00109519>]
> Code: 1f f6 05 b0 00 00 00 02 1f c3 e8 4a 00 00 00 74 0d e8 4d 00
> Aiee, killing interrupt handler
> kfree of non-kmalloced memory: 001b78b8, next= 00000000, order=0
> kfree of non-kmalloced memory: 001b78a8, next= 00000000, order=0
> kfree of non-kmalloced memory: 001b7dbc, next= 00000000, order=0
> idle task may not sleep
> idle task may not sleep
> idle task may not sleep
> idle task may not sleep
> idle task may not sleep
>
> ..then booting continues normally and all seems functional. This machine is
> IBM ThinkPad 310E and this is dual booted between Win98 and Linux (SuSE-6.0)
>
> PC works just fine with SuSE's default kernel, but I wanted to compile my
> own mainly because APM isn't supported with the SuSE kernel (2.0.36). This
> self compiled kernel causes that.. eh "Aieee"
egcs can't be used to compile the kernel (yet)
Dave J. Andruczyk
Instructional Support Associate
Department of Technology
Buffalo State College
------------------------------
From: John Hughes <[EMAIL PROTECTED]>
Subject: Re: RFS? Re: NFS vs DFS
Date: 29 Apr 1999 18:15:03 +0200
[EMAIL PROTECTED] (Christopher Browne) writes:
> On 28 Apr 1999 17:49:58 +0200, John Hughes <[EMAIL PROTECTED]> wrote:
> >And not a word about RFS. How sad. I'll just go away and cry.
>
> It would be nice to see a precis on it so we may learn something about
> it, and whether or not it has merits that are of interest.
It was AT&T's entry in the great distributed filessystem war.
The nicest thing about it was that it was a distributed *Unix*
filesystem, so locking just worked, you could open remote devices, you
could open remote fifos...
It was killed by some bad implementations (they screwed up the byte
ordering in some of them), it may have been rather slow.
It was stateful.
--
John Hughes <[EMAIL PROTECTED]>,
Atlantic Technologies Inc. Tel: +33-1-4313-3131
66 rue du Moulin de la Pointe, Fax: +33-1-4313-3139
75013 PARIS.
------------------------------
From: Vincent Stoessel <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: My zombie server
Date: Thu, 29 Apr 1999 20:55:47 GMT
Anyone knows what could be the problem here?
Vincent Stoessel wrote:
>
> Ok, I'm stuck at my day job until I can go home and fix
> my apache/mysql/realaudio server om redHat 5.0 , 2.0.36 linux.
>
> While using a php script to do some updates to the local
> mysql serer, My server began dying: I am still logged into the
> machine via telnet but any command just gives me a segmentation fault.
> Fortunately this box syslogs to a remote server. Below is a block
> of info I'm getting from the machine.
> Did I just run out of memory or is it something more sinister.
> Thisngs I've done within the last 3 weeks
> 1.Hacked the kernal to set NR_OPEN to 1024 recompiled.
> 2. Hacked apache to accept up to 300 coonections in httpd.h
> 3. set mysql max connections to 600 and table cache to 200.
> I have 192 M of ram and I also run a RealAudio basic server off
> this box, it is limited to 40 streams.
>
> Apr 29 15:10:09 kernel: Unable to load interpreter
> Apr 29 15:10:25 kernel: Unable to handle kernel paging request at virtual address
>499fc000
> Apr 29 15:10:25 kernel: current->tss.cr3 = 0b4ab000,
> Apr 29 15:10:25 kernel: *pde = 06441067
> Apr 29 15:10:26 kernel: *pte = 00000000
> Apr 29 15:10:26 kernel: Oops: 0002
> Apr 29 15:10:26 kernel: CPU: 0
> Apr 29 15:10:26 kernel: EIP: 0010:[generic_file_read+995/1532]
> Apr 29 15:10:26 kernel: EFLAGS: 00010216
> Apr 29 15:10:26 kernel: eax: 05dd3000 ebx: 00001000 ecx: 00000002 edx:
>00000000
> Apr 29 15:10:26 kernel: esi: 05dd3ff8 edi: 499fc000 ebp: 00352edc esp:
>00ee1f54
> Apr 29 15:10:26 kernel: ds: 0018 es: 002b fs: 002b gs: 002b ss: 0018
> Apr 29 15:10:26 kernel: Process mysqld (pid: 23462, process nr: 354,
>stackpage=00ee1000)
> Apr 29 15:10:26 kernel: Stack: 00000018 03a2d2ec 00000000 00400000 0b68b600
>004f6000 0050e000
> 00001000
> Apr 29 15:10:26 kernel: 00000000 047df000 00000001 00000001 047df000
>004f6000 000f6000
> 00000000
> Apr 29 15:10:26 kernel: 00123560 0b68b600 03a2d2ec 499fb008 0030a000
>00ee2018 49905008
> 000000c5
> Apr 29 15:10:26 kernel: Call Trace: [sys_read+196/236] [system_call+85/124]
> Apr 29 15:10:26 kernel: Code: f3 a5 83 e3 03 89 d9 f3 a4 07 55 e8 6d 34 00 00 8b 5c
>24 1c
> Apr 29 15:10:26 kernel: Unable to handle kernel paging request at virtual address
>453ff000
> Apr 29 15:10:26 kernel: current->tss.cr3 = 0b4ab000,
> Apr 29 15:10:26 kernel: *pde = 07fe2067
> Apr 29 15:10:26 kernel: *pte = 00000000
> Apr 29 15:10:26 kernel: Oops: 0002
>
> Any insights, snide remarks, humor will be
> apreciated as I wait to leave.
> Thanks
> [EMAIL PROTECTED]
Looks like you could get more help at comp.os.linux.* ,
Vincent
------------------------------
From: [EMAIL PROTECTED] (Wlmet)
Subject: un.h missing sun_len
Date: 29 Apr 1999 21:42:57 GMT
What is the theory behind the sun_len field and why doesn't linux have such a
field in the sockaddr_un structure?
#ifndef _LINUX_UN_H
#define _LINUX_UN_H
#define UNIX_PATH_MAX 108
struct sockaddr_un {
unsigned short sun_family; /* AF_UNIX */
char sun_path[UNIX_PATH_MAX]; /* pathname */
};
struct cmsghdr {
unsigned int cmsg_len;
int cmsg_level;
int cmsg_type;
unsigned char cmsg_data[0];
};
#endif /* _LINUX_UN_H */
------------------------------
From: [EMAIL PROTECTED] (Harald Schreiber)
Subject: Re: Threads >> PThreads or LinuxThreads??
Date: 29 Apr 1999 22:13:38 GMT
Reply-To: [EMAIL PROTECTED]
In article <[EMAIL PROTECTED]>,
Martin Recktenwald <[EMAIL PROTECTED]> writes:
[...]
> prep.ai.mit.edu:/gnu/glibc/glibc-2.1-README:
>
> "glibc-2.1 has been (temporarily) removed, until some
> political issues are worked out."
>
glibc-2.1 has been removed from prep.ai.mit.edu by the GNU people
because the documentation of glibc-2.1 recommends compiling with
egcs and not with gcc. glibc-2.1 has been released several months
ago and the Linux distributions RedHat 6.0 and Caldera 2.2 are
alreday based on glibc-2.1
Harald
--
===================================================================
Harald Schreiber, Nizzaalle 26, D-52072 Aachen, Germany
Phone: +49-241-9108015, Email: [EMAIL PROTECTED]
===================================================================
------------------------------
From: "Jack Levin" <[EMAIL PROTECTED]>
Subject: Calibri Firewall/Router on Ebay.
Date: Thu, 29 Apr 1999 15:44:33 -0700
Crossposted-To:
comp.dcom.modems.cable,comp.dcom.xdsl,comp.os.linux.hardware,comp.os.linux.misc,comp.os.linux.networking,comp.os.linux.portable,comp.security.firewalls
Hi all... Check out Calibri-133 firewall being sold at Ebay. (hardware)
http://cgi.ebay.com/aw-cgi/eBayISAPI.dll?ViewItem&item=97714586
-Jack
------------------------------
From: Kent Friis <[EMAIL PROTECTED]>
Subject: Re: pc-speaker driver
Date: Thu, 29 Apr 1999 20:58:39 +0200
[EMAIL PROTECTED] wrote:
>
> which neither 2.0.35 nor 2.2.6 kernels provide.)
> This compels me to ask, why is there no PC speaker
> driver already in the kernel distribution?
> It seems like a fairly useful option and when
> used it would take up very few resources.
Why do you think it would take up very few resources?
Have you ever looked at a sound card? All those little
thingies are there for a reason - sound doesn't come
by itself, it is actually produced those thingies.
When you use the PC'speaker, you don't have anything
to make the sound (except for the speaker itself), and
thus you'll need to use the main CPU instead. Kind of
like a winmodem.
However if all you want from the pcspeaker is beeping
and tiny melodies, but no samples, etc. you don't need
a special driver. ascii 7 handles the beep, and both
duration and frequency can be changed by console ESC
codes or with xset.
Kent
------------------------------
From: [EMAIL PROTECTED] (Neil Schemenauer)
Subject: Re: Is Linux Y2K compliant?
Date: 29 Apr 1999 22:50:06 GMT
On 29 Apr 1999 10:59:41 PST, Don Baccus <[EMAIL PROTECTED]> wrote:
>Saving a couple of BCD digits per date seems silly in
>retrospect, but it wasn't so silly for companies with
>huge numbers of dated records in an era where a 50 MB
>"washtub" drive cost $40K or so (closer to $125K in
>today's money). Working with thousand dollar megabytes
>changes the economic constraints compared to working with
>thirty dollar gigabytes as we do today.
The root of the problem is people. The space argument doesn't really
wash. Check out
http://language.perl.com/news/y2k.html
for a good summary of how we got in this mess and how people are
now trying to cover their asses.
Neil
------------------------------
From: Tom Goodale <[EMAIL PROTECTED]>
Subject: Re: how to access raw memory?
Date: Mon, 26 Apr 1999 19:06:23 +0200
"Jacek Pop�awski" wrote:
>
> Konrad Mieredorff wrote:
> >Linux Device Drivers by Allessandro Rubini (O'Reilly)
>
> but what is it - a book?
> if it is avaiable online - please give me URL
> I live in Poland and have no big chance to buy book from west countries
> (it's no problem with transport, but with money)
It is a book, but there is also something similar (same author ? ) in
the LDP,
so downloadable.
Tom
------------------------------
From: Allin Cottrell <[EMAIL PROTECTED]>
Subject: Re: Powwerdown on shutdown for 2.2.6 laptop
Date: Thu, 29 Apr 1999 23:01:20 -0400
[EMAIL PROTECTED] wrote:
>
> I recently upgraded Sony pcg-f160 laptop running linux from 2.0.36 to 2.0.6.
> the Powerdown on shutdown used to work but now I can not seem to make
> function. Any clues?
No -- but a "same here" on the IBM ThinkPad, updating from 2.0.36 to
various 2.2.N kernels.
--
Allin Cottrell
Department of Economics
Wake Forest University, NC
------------------------------
From: [EMAIL PROTECTED] (Leslie Mikesell)
Subject: Re: NFS vs DFS
Date: 29 Apr 1999 22:19:19 -0500
In article <[EMAIL PROTECTED]>,
John Hughes <[EMAIL PROTECTED]> wrote:
>> In article <[EMAIL PROTECTED]>,
>> John Hughes <[EMAIL PROTECTED]> wrote:
>> >And not a word about RFS. How sad. I'll just go away and cry.
>>
>> It is a sad memory, if you recall how processes that had open files
>> or a working directory across a broken mount point were killed
>> with no chance to recover.
>
>A mere implementation detail. Not at all required by the protocol.
>
>(admittedly you'd get an error if you tried to read a file on a server
>that was down, but I see no reason you should get killed).
It was also a rather strange idea to let device nodes sort-of work
when ioctl()'s between machines of different CPU types (like 3B2/intel)
couldn't possibly be done. Having FIFOs that spanned machines
was kind of neat though.
Les Mikesell
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Leslie Mikesell)
Subject: Re: RFS? Re: NFS vs DFS
Date: 29 Apr 1999 22:27:15 -0500
In article <AOYV2.17245$[EMAIL PROTECTED]>,
Christopher Browne <[EMAIL PROTECTED]> wrote:
>>And not a word about RFS. How sad. I'll just go away and cry.
>
>Please don't.
>
>I'm not familiar with it, and I'm sure I'm not alone.
>
>It would be nice to see a precis on it so we may learn something about
>it, and whether or not it has merits that are of interest.
It was an attempt to preserve unix semantics to the extent possible
across machines. Device nodes actually refer to devices on the
remote host, FIFOs spanning machines, file locking that works, etc.
It actually worked very well except for the quirk that it killed
any processes that might be affected by a failure. It had to
maintain state and had no way to recover it after a disconnect.
The first version I used ran over AT&T's Starlan instead of IP and
had its own name resolution and domain concepts.
Les Mikesell
[EMAIL PROTECTED]
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.development.system) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Development-System Digest
******************************
