Linux-Development-Sys Digest #620, Volume #6 Tue, 13 Apr 99 15:14:00 EDT
Contents:
Kernel problem (PANIC) (Koh)
Re: Programming tools for Linux/Unix: Editor, IDE, Frontend to GCC. (Donal K.
Fellows)
M-systems binary only drivers & GPL (Fabrice Bellard)
Re: Kernel problem (PANIC) (Daniel Robert Franklin)
PROC-fs, Need to make it CHARGEBEL ([EMAIL PROTECTED])
Re: CodeWarror for Linux (was: Re: Programming tools for ...) (Donal K. Fellows)
Re: a problem with scanf (Jack Klein)
Linux Debugger/Monitor (Coen Verkuyl)
Why is my process consuming system time? ([EMAIL PROTECTED])
CD wont't play after 2.0.36->2.2.5 (Michael Spalinski)
Re: Problems with 2.2.5 & sound & apm (Kent Ritchie)
Re: SIGPOLL on socket errors (Paul Vojta)
Re: M-systems binary only drivers & GPL (Markus Kohler)
Re: Win32 support in Linux (Harald Arnesen)
Re: New Kernel not booting (Rick O'Konis)
Best chip/method for new PCI card design ("Gregory Benjamin")
----------------------------------------------------------------------------
From: Koh <[EMAIL PROTECTED]>
Subject: Kernel problem (PANIC)
Date: Tue, 13 Apr 1999 12:35:15 +0800
Hai all,
My current kernel version is 2.0.32 and I try to install
kernel 2.0.36 into the machine. During installation everything
look fine.
I had done make def, make clean, and make zImage.
zImage has been copy to /boot/vmlinuz and configure
/etc/lilo.conf image=/boot/vmlinuz.
BUT during boot up, it STOP at mouting to root
directory. The message is "(something)..... PANIC ...."
and the system hang.
Anyone who knows a way to make this work, please, help me
Thanks in advance....
------------------------------
From: [EMAIL PROTECTED] (Donal K. Fellows)
Crossposted-To:
comp.os.linux.advocacy,comp.os.linux.development.apps,comp.os.linux.help,comp.unix.programmer
Subject: Re: Programming tools for Linux/Unix: Editor, IDE, Frontend to GCC.
Date: 13 Apr 1999 10:55:12 GMT
In article <[EMAIL PROTECTED]>,
Craig Graham <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Stephan Schulz) wrote:
>> My memory management subsystem catches most allocation/deallocation
>> errors with assertions, and I have a debug mode that allows me to
>> trace allocations and deallocations pretty well. I have had no major
>> problems here (although it is pretty unpleasant to step through the
>> code trying to find the two blocks you forgot to free...).
>
> I wrote a malloc/free wrapper that traces all allocations, and gives a
> dump of any lost blocks on program exit - with the module and line
> they were allocated at. It then lets you run through again and will
> breakpoint when the allocation you lost last time is made so you
> can easily trace any problems....
I know the assertion techniques well (and use them heavily :^) but I
tend to find that the nasty problems only occur very deep into a
program (there is an absolutely insane number of layers of memory
management in there - malloc() is just too slow...) and, because of
the use of reference counting to keep the memory churn down (this
makes an enormous difference,) I find that the problems that occur are
either a failure to decrement somewhere, or a decrement too much.
Murphy guarantees that things only ever go pear-shaped in code that is
actually correct (since the extra decrement is elsewhere) and no C
debugging tool on the planet tells you where you *didn't* run a piece
of code.
Since there is also a GUI and a compiler in the same process, things
are a little hairy! 100MB printf() traces are the only way.
Donal.
--
Donal K. Fellows http://www.cs.man.ac.uk/~fellowsd/ [EMAIL PROTECTED]
-- The small advantage of not having California being part of my country would
be overweighed by having California as a heavily-armed rabid weasel on our
borders. -- David Parsons <o r c @ p e l l . p o r t l a n d . o r . u s>
------------------------------
From: [EMAIL PROTECTED] (Fabrice Bellard)
Subject: M-systems binary only drivers & GPL
Date: 13 Apr 1999 11:50:21 GMT
I saw that several compagnies are using the M-Systems
(http://www.m-sys.com) disk-on-chip products with Linux. It emulates a
hard disk with flash memory.
This disk-on-chip is not like an IDE drive, so it needs a special
block driver. The driver is provided by M-Systems in binary form only.
Since this disk-on-chip is used for booting, the binary Linux driver
is statically linked with the Linux kernel (it is *not* a module).
My question is: is it legal ? Do Linus & the other copyright holders
of Linux allow that a binary only driver is statically linked with the
kernel ?
Whatever the answer is, a clear announcement must be made because many
compagnies are actually shipping products with this driver in the
Linux kernel.
Fabrice Bellard.
------------------------------
From: [EMAIL PROTECTED] (Daniel Robert Franklin)
Subject: Re: Kernel problem (PANIC)
Date: 13 Apr 99 05:00:47 GMT
Koh <[EMAIL PROTECTED]> writes:
>Hai all,
> My current kernel version is 2.0.32 and I try to install
>kernel 2.0.36 into the machine. During installation everything
>look fine.
> I had done make def, make clean, and make zImage.
>zImage has been copy to /boot/vmlinuz and configure
>/etc/lilo.conf image=/boot/vmlinuz.
> BUT during boot up, it STOP at mouting to root
>directory. The message is "(something)..... PANIC ...."
>and the system hang.
>Anyone who knows a way to make this work, please, help me
Most likely you didn't include EXT2FS support in the kernel.
Alternatively, you may have forgotten to compile in IDE hard drive
support, or SCSI (if you have a SCSI system). If you can get in to your
system, just recompile the kernel with those features.
On the other hand, if you can't even log in, you will need to create a
boot disk. For this situation, it really helps if you have another Linux
box on hand. I generally make a Linux boot disk (rather than make zImage,
stick a floppy in the disk drive and type make zdisk) when I compile my
kernel. Make sure it is rdev'd to your root partition (e.g. if your root
partition is /dev/hda3, do this: rdev /dev/fd0 /dev/hda3). Reboot, and you
should be "in", at which point you can try to correct things.
With LILO I like to keep an old known working image as a boot option -
with loadlin it is even easier - just keep a good kernel image somewhere
on your DOS partition (I would recommend having loadlin if you have a DOS
partition, even if you use LILO. It is a good backup system).
- Daniel
--
******************************************************************************
* Daniel Franklin - Postgraduate student in Electrical Engineering
* [EMAIL PROTECTED]
******************************************************************************
------------------------------
From: [EMAIL PROTECTED]
Subject: PROC-fs, Need to make it CHARGEBEL
Date: Tue, 13 Apr 1999 13:17:44 +0200
Hello,
I need statistics from the kernel about how many jiffies a process has
used when it's done.
I could scan /proc every second but thats overkill.
High level approach
Way one:
Find the place in the kernel were the process i terminated and then
write the number of jiffies i has used to the statistics DB.
Way Two(the way to go, i belive)
Copy the /proc/{pid}/stat when it's deleted.
I belive that it's in the linux/fs/proc/root.c:proc_unregister i whould
copy the stat, but how?
What pointer points to the stat BUFFER ie the string thats is writen in
stat file?
With this information i can start to charge my custumers of how much
they use the system per Cpu used.
THEN WE CAN REMOVE IBM FROM THE TOP OF MAINFRAMES
Regards Roger Strandberg SWEDEN
------------------------------
From: [EMAIL PROTECTED] (Donal K. Fellows)
Crossposted-To:
comp.os.linux.advocacy,comp.os.linux.development.apps,comp.os.linux.help,comp.unix.programmer
Subject: Re: CodeWarror for Linux (was: Re: Programming tools for ...)
Date: 13 Apr 1999 11:29:56 GMT
In article <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] says...
>> Another issue with Unix software is that graphical
>> apps make demands on the availability of X Windows running and
>> on bandwidth of a network connection that prohibit work in
>> many situations, so people typically refrain from doing something
>> that only pays off in eye candy rather than functionality if
>> it is going to be useful in fewer circumstances.
>
> Yeah right, like people develop over a LAN or WAN. Give me a break.
> Your child-like resistance is noted in your use of "eye candy" and
> dropped your case to ground zero.
Downstairs there is a big supercomputer cluster that provides a
national parallel compute resource. It sits in a secure room.
Developing software for that beastie *requires* doing it remotely.
Unless you expect everyone to have multi-M� computers on their
desks...
Donal.
--
Donal K. Fellows http://www.cs.man.ac.uk/~fellowsd/ [EMAIL PROTECTED]
-- The small advantage of not having California being part of my country would
be overweighed by having California as a heavily-armed rabid weasel on our
borders. -- David Parsons <o r c @ p e l l . p o r t l a n d . o r . u s>
------------------------------
From: [EMAIL PROTECTED] (Jack Klein)
Crossposted-To: comp.lang.c
Subject: Re: a problem with scanf
Date: Tue, 13 Apr 1999 05:48:50 GMT
On Mon, 12 Apr 1999 21:18:13 GMT, [EMAIL PROTECTED] (Jack Klein) wrote
in comp.lang.c:
> On Mon, 12 Apr 1999 21:30:40 +0200, Francesc Oller
> <[EMAIL PROTECTED]> wrote in comp.lang.c:
>
> > executing the following code in LINUX:
> >
> > ...
> > void main(void)
> > {
> > char c;
> > setvbuf(stdin,NULL,_IONBF,0);
> > tty_raw(0);
> > scanf("%c",&c);/*c=getchar();*/
> > tty_reset(0);
> > printf("c='%c'\n",c);
> > }
> >
> > where tty_raw puts the terminal in RAW mode and tty_reset
> > returns it to COOKED mode, makes me to have to press two chars
> > in order for scanf to get the first (i.e printf doesn't
> > execute until I press twice).
> >
> > However getchar works as expected (only one keyb press)
> > WHY?
> >
> > Francesc Oller
>
> <Jack>
>
> This question has nothing to do with the C language. In fact it stops
> being legal C when you typed "void main(void)" because the C language
> always has and still does require that main be defined with a return
> type of int.
>
> A bigger issue is that there are no functions named setvbuf(),
> tty_raw() or tty_reset() in the C language. Please keep your Linux
> specific questions in the Linux groups and out of comp.lang.c.
>
> But if you want to know why scanf() is evil and should be avoided in
> almost all situations, especially for live user input, see the
> comp.lang.c FAQ.
>
> FAQ for comp.lang.c
> http://www.eskimo.com/~scs/C-faq/top.html
>
> </Jack>
Sorry. Temporary insanity, but I'm better now. setvbuf() is
standard, but the tty functions are still not, and scanf() is still
evil.
Jack
------------------------------
From: [EMAIL PROTECTED] (Coen Verkuyl)
Subject: Linux Debugger/Monitor
Date: Tue, 13 Apr 1999 06:47:11 GMT
I'm looking for a debug tool for Linux (i386). I'm writing driver
software
for a ISA card with memory and registers mapped into the memory space
of the
PC. The debug tool must be able to access any physical memory address,
just
like the MS-DOS tool 'debug'.
Where can I find something like this?
Thanks for any help,
Coen
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Subject: Why is my process consuming system time?
Date: Tue, 13 Apr 1999 16:21:35 GMT
I recently got a biprocessor Pentium II system on which I installed
RedHat 5.2 and recompiled the kernel (2.0.36) for SMP. I noticed
with considerable surprise that my number crunching jobs (which
do pure calculation with very few system calls for I/O) consume
hardly any user time, but plenty of system time. The same programs
run at 99% user time on my laptop (single-processor Pentium, RedHat 5.1).
Is this something I should worry about or just a quirk of the time
counting system?
===============================================================================
Konrad Hinsen | E-Mail: [EMAIL PROTECTED]
Centre de Biophysique Moleculaire (CNRS) | Tel.: +33-2.38.25.55.69
Rue Charles Sadron | Fax: +33-2.38.63.15.17
45071 Orleans Cedex 2 | Deutsch/Esperanto/English/
France | Nederlands/Francais
===============================================================================
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: Michael Spalinski <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup
Subject: CD wont't play after 2.0.36->2.2.5
Date: 13 Apr 1999 12:46:45 -0400
After upgrading the kernel as in the subject, I can no longer play a CD
through the sound card (everything worked OK with 2.0.36). This happens on
a machine which has a SCSI CDROM drive, while on another machine here,
which has a non-SCSI drive (and the same sound card) everything is fine
(although 2.2.0 had the same problem there too).
The SCSI controler is Mylex BT958, and the Sound Card is SB16. I can mount
/dev/cdrom etc without problems (the correct module gets
inserted). Furthermore xplaycd (and other cd-players) recognizes that a CD
with the right number of tracks is there and "thinks" it is playing it: no
sound however is to be heard ...
Any ideas?
M.
------------------------------
From: [EMAIL PROTECTED] (Kent Ritchie)
Subject: Re: Problems with 2.2.5 & sound & apm
Date: 13 Apr 1999 13:28:21 GMT
Roope Anttinen ([EMAIL PROTECTED]) wrote:
: AFAIK dhcp is available in 2.0 series too.
Do you remember which package. The one I was trying to compile (and did
under 2.2.x) needed sock_packet configured in the kernel. Perhaps it was
introduced to 2.0.x after 34? Or perhaps it was a different DHCP client.
Do you remember where you found the DHCP client that worked with 2.0.x?
Thanks.
-Kent
------------------------------
From: [EMAIL PROTECTED] (Paul Vojta)
Subject: Re: SIGPOLL on socket errors
Date: 13 Apr 1999 10:58:27 -0700
In article <7eu60v$ll$[EMAIL PROTECTED]>, I wrote:
>An error condition on a socket is a pollable event.
...
Here is a little more information on what I am asking about:
On the following operating systems, the enclosed sample program reports
that a SIGPOLL signal is raised when the other half of a socket is closed:
SunOS 4.1.3
Linux 2.0.36 Intel
The following do not raise SIGPOLL in that case (constituting a bug, IMHO):
Linux 2.2.3 Intel
Linux 2.2.5 Sparc (32-bit)
Here is the sample program.
--Paul Vojta, [EMAIL PROTECTED]
=========
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <signal.h>
#include <errno.h>
#include <sys/file.h>
#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/in.h>
int sv[2];
int flag = 0;
int flag2 = 0;
static void
handler(int signo)
{
flag = 1;
}
static void
handler2(int signo)
{
flag2 = 1;
}
main(int argc, char **argv)
{
int w_flag = 0;
if (argc > 1) {
if (argc != 2 || *argv[1] != 'w') {
fputs("Usage: bug [w]\n", stderr);
exit(1);
}
w_flag = 1;
}
if (socketpair(AF_UNIX, SOCK_STREAM, IPPROTO_IP, sv)) {
perror("socketpair");
exit(1);
}
signal(SIGPOLL, handler);
signal(SIGURG, handler2);
if (fcntl(sv[1], F_SETOWN, getpid()) == -1) {
perror("F_SETOWN");
exit(1);
}
if (fcntl(sv[1], F_SETFL, fcntl(sv[1], F_GETFL, 0) | FASYNC) == -1) {
perror("F_SETFL");
exit(1);
}
if (w_flag)
write(sv[0], "x", 1);
else
close(sv[0]);
sleep(3); /* give the signal a chance to occur */
if (flag) puts("SIGPOLL received.");
if (flag2) puts("SIGURG received.");
return 0;
}
------------------------------
Subject: Re: M-systems binary only drivers & GPL
From: Markus Kohler <[EMAIL PROTECTED]>
Date: 13 Apr 1999 16:19:14 +0200
[EMAIL PROTECTED] (Fabrice Bellard) writes:
> I saw that several compagnies are using the M-Systems
> (http://www.m-sys.com) disk-on-chip products with Linux. It emulates a
> hard disk with flash memory.
>
> This disk-on-chip is not like an IDE drive, so it needs a special
> block driver. The driver is provided by M-Systems in binary form only.
>
> Since this disk-on-chip is used for booting, the binary Linux driver
> is statically linked with the Linux kernel (it is *not* a module).
>
> My question is: is it legal ? Do Linus & the other copyright holders
> of Linux allow that a binary only driver is statically linked with the
> kernel ?
My understanding is that it's illegal.
>
> Whatever the answer is, a clear announcement must be made because many
> compagnies are actually shipping products with this driver in the
> Linux kernel.
modules can be shipped without source code.
Markus
--
Markus Kohler mailto:[EMAIL PROTECTED]
------------------------------
From: Harald Arnesen <[EMAIL PROTECTED]>
Subject: Re: Win32 support in Linux
Date: 13 Apr 1999 11:44:42 +0200
[EMAIL PROTECTED] writes:
> My question is simple. Does Linux have win32 support? I had read in
> the 2.2.0 docs on linux.org that it would be, but when I installed it,
> I could not see anything indicating that it did. I don't want to
> win32alize my hd without first knowing that I can still access it from
> linux. Thanks.
Depends on what you mean. If you just want to access a FAT-32
partition, no problem. They can be mounted, just as partitions with
the native ext2 filesystem.
If you mean running 32-bit Windows applications, the answer is a
qualified no - but see www.winehq.org and www.vmware.com.
--
Harald Arnesen, Apall�kkveien 23 A, N-0956 Oslo, Norway
------------------------------
From: Rick O'Konis <[EMAIL PROTECTED]>
Subject: Re: New Kernel not booting
Date: Tue, 13 Apr 1999 09:43:51 -0500
The problem is with the "make config" process. I was clued in by a fellow
traveler in the Linux world. (Thank you Raymond, wherever you are!) If you
do a "make config" with an old .config file or a "make oldconfig" or a
"make menuconfig" then option CONFIG_VGA_CONSOLE is not set, resulting in
your kernel not being able to assign the console, thus hanging. You have to
run the old "make config" fresh and then the option appears.
Bill Anderson wrote:
> After installing a new drive (old one dying) last night, and recompiling
> the kernel to 2.2.1, it doesn't want to boot.
> When I get through lilo, it says "Ok, booting the kernel" and stays
> there.
> Before the old HD failed. 2.2.1 was working on this system, as does
> booting into 2.0.36.
>
> Any Ideas?
>
> Bill
------------------------------
From: "Gregory Benjamin" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware
Subject: Best chip/method for new PCI card design
Date: Thu, 8 Apr 1999 00:52:37 -0700
I'm in the early stages of designing a PCI card
for a laser film recorder (LFR) device. I have never
designed a PCI card or written a Linux driver, but
I have both designed hardware and written low-level
RTOS code for several processors over the years.
I want to produce a board design that works well on
the first try, or failing that, with minimal rework.
Volume will be low, so PCI interfaces in the form of
an IP core in an FPGA are probably out. The
computer system is dedicated to driving the LFR and
doing simple queue management. What I'm looking for
are recommendations on the most appropriate vendor/chip
for the PCI interface, the cleanest buffering/FIFOing
architecture that will assure me of no data loss, and
pointers on the most appropriate driver sources to use
as a starting point. I am also interested in inexpensive
(<$500) PCI development boards/tools to allow prototyping.
I have some familiarity with product offerings from
AMCC, Anchorchips, PLX, etc.
Here are some particulars:
# Laserlab LFR PCI design
o device is a high-resolution laser film recorder (LFR)
o LFR is controlled by a dedicated PC
o PC will run Linux (no support for other OSes planned)
o PC configuration
- ASUS P2B mainboard
- Intel CPU >= 366MHz.
- 128MB RAM
- Matrox G200 graphics adapter
- UDMA IDE disk(s) attached to mainboard
- 10/100 mbit/sec NIC
- LFR PCI card
o LFR charcteristics
- synchronous device -- data MUST be present when needed
- data processed as scan lines
- two scan line periods: 2.5 and 5.0 ms
- 5 Kilobytes per 2.5 ms scan line
( 400 scans/sec * 5KB/line = 2MB/sec)
- 10 Kilobytes per 5.0 ms scan line
( 200 scans/sec * 10KB/line = 2MB/sec)
- image takes up to 8 minutes, 40 seconds to produce
- image size 1040 Megabytes (maximum)
o LFR PCI card requirements
-- outbound data rate 2 megabytes/sec
-- inbound data rate < 100 kilobytes/sec
o Data flow
-- receive from NIC via tcp/ip
-- save to disk as sequence of files
-- read from disk to RAM
-- minimally process in RAM
-- output to LFR PCI card
All input appreciated!
o-----------------------------------------------------------------------o
| Gregory Benjamin Laserlab, Inc. o Laser photoplotting |
| [EMAIL PROTECTED] 6790 Top Gun Street o CNC machining |
| Suite 9 o Chemical milling |
| San Diego, CA 92121 o Printed Circuit Fabrication |
| www.laserlab.com Tel: 619-646-7660 o Precision photomasks |
| ftp.laserlab.com Fax: 619-646-7667 o AutoCAD to Gerber conversion|
o-----------------------------------------------------------------------o
------------------------------
** 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
******************************
