Re: 2.2.17-RAID: Eating memory

[Francois Romieu]

John Plate <[EMAIL PROTECTED]> écrit :
[do_try_to_free_pages]

Known issue on < 2.2.19pre kernels (do a search for "do_try_to_free_pages"
on the ML archive). It doesn't require RAID btw. Upgrade to 2.2.19prexx, it
performs better.

-- 
Ueimor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [patch] pae-2.4.3-A4

[Studierende der Universitaet des Saarlandes]

> plus i took to opportunity to reduce the allocation size of PAE-pgds. 
> Their size is only 32 bytes, and we allocated a full page. Now the code 
> kmalloc()s a 32 byte cacheline for the pgd. (there is a hardware 
> constraint on alignment: this cacheline must be at least 16-byte aligned, 
> which is true for the current kmalloc() code.)

No, it isn't ;-)

Just enable slab debugging (it's a kernel option in alan's ac kernels),
and then the kmalloc result is not aligned anymore.

--
Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

IRQ timeout when switching slot on ide cdrom changer

[Marc x]

Hi,

I have this problem on kernel 2.4.2, various ac
patches, including latest ac24.

When requesting a slot change, most of the time I get
a 
>hdc: irq timeout: status=0xd0 { Busy } 
>hdc: ATAPI reset complete 

and the drive switches me back to the first slot. 
I have tried w/ an w/o DMA , no succes.

The same drive worked fine under various 2.2.x
kernels.

Marc.


___
Do You Yahoo!? -- Pour dialoguer en direct avec vos amis, 
Yahoo! Messenger : http://fr.messenger.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Can't compile 2.4.2-ac25

[Chung Won-young]

Try this:

--- es1370.orig Mon Mar 26 18:15:06 2001
+++ es1370.cMon Mar 26 17:47:54 2001
@@ -170,6 +170,8 @@
 struct gameport {
 int io;
 int size;
 +   void (*trigger)(struct gameport *);
 +   unsigned char (*read)(struct gameport *);
  };

extern inline void gameport_register_port(struct gameport 
*gameport)


- ÆóÀÎ -

ICQ : 36602496
E - Mail : [EMAIL PROTECTED], [EMAIL PROTECTED]
Homepage : http://kernel.pe.kr, http://pain.kernel.pe.kr

On Mon, 26 Mar 2001, Chung Won-young wrote:

>
> Hello,
> I receive the following error with make zImage:
>
> es1370.c: In function `es1370_probe':
> es1370.c:2667: structure has no member named `trigger'
> es1370.c:2667: structure has no member named `read'
> make[3]: *** [es1370.o] Error 1
> make[3]: Leaving directory `/usr/src/linux-2.4.2/drivers/sound'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.4.2/drivers/sound'
> make[1]: *** [_subdir_sound] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4.2/drivers'
> make: *** [_dir_drivers] Error 2
>
>
>
> maybe 'Update es1370, es1371,esssolo' has some problem.
>
>
> - ÆóÀÎ -
>
> ICQ : 36602496
> E - Mail : [EMAIL PROTECTED], [EMAIL PROTECTED]
> Homepage : http://kernel.pe.kr, http://pain.kernel.pe.kr
>
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.2ac25

[Dieter Nützel]

I got the following compilation error with aic7xxx (sorry, $LANGUAGE=german 
:-)

make[5]: Entering directory 
`/usr/src/linux-2.4.2-ac25/drivers/scsi/aic7xxx/aicasm'
if [ -e "/usr/include/db3/db_185.h" ]; then \
echo "#include " > aicdb.h;   \
elif [ -e "/usr/include/db_185.h" ]; then   \
echo "#include " > aicdb.h;   \
elif [ -e "/usr/include/db/db_185.h" ]; then\
echo "#include " > aicdb.h;\
elif [ -e "/usr/include/db2/db_185.h" ]; then   \
echo "#include " > aicdb.h;   \
elif [ -e "/usr/include/db1/db_185.h" ]; then   \
echo "#include " > aicdb.h;   \
else\
echo "*** Install db development libraries";\
fi
gcc -I/usr/include -ldb aicasm_gram.c aicasm_scan.c aicasm.c aicasm_symbol.c 
-o
aicasm
aicasm/aicasm_gram.y:45: ../queue.h: Datei oder Verzeichnis nicht gefunden
aicasm/aicasm_gram.y:50: aicasm.h: Datei oder Verzeichnis nicht gefunden
aicasm/aicasm_gram.y:51: aicasm_symbol.h: Datei oder Verzeichnis nicht 
gefunden
aicasm/aicasm_gram.y:52: aicasm_insformat.h: Datei oder Verzeichnis nicht 
gefunden
aicasm/aicasm_scan.l:44: ../queue.h: Datei oder Verzeichnis nicht gefunden
aicasm/aicasm_scan.l:49: aicasm.h: Datei oder Verzeichnis nicht gefunden
aicasm/aicasm_scan.l:50: aicasm_symbol.h: Datei oder Verzeichnis nicht 
gefunden
aicasm/aicasm_scan.l:51: y.tab.h: Datei oder Verzeichnis nicht gefunden
make[5]: *** [aicasm] Error 1
make[5]: Leaving directory 
`/usr/src/linux-2.4.2-ac25/drivers/scsi/aic7xxx/aicasm'
make[4]: *** [aicasm/aicasm] Error 2
make[4]: Leaving directory `/usr/src/linux-2.4.2-ac25/drivers/scsi/aic7xxx'
make[3]: *** [first_rule] Error 2
make[3]: Leaving directory `/usr/src/linux-2.4.2-ac25/drivers/scsi/aic7xxx'
make[2]: *** [_subdir_aic7xxx] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.2-ac25/drivers/scsi'
make[1]: *** [_subdir_scsi] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.2-ac25/drivers'
make: *** [_dir_drivers] Error 2

-- 
Dieter Nützel
Graduate Student, Computer Science

University of Hamburg
Department of Computer Science
Cognitive Systems Group
Vogt-Kölln-Straße 30
D-22527 Hamburg, Germany

email: [EMAIL PROTECTED]
@home: [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux should better cope with power failure

[David Balazic]

Gerhard Mack wrote:
> 
> This sounds very nice.. can such a thing be done with the reset switch as
> well?

Don't think so.
I'm not sure , but I think that the reset button is directly connected
to the reset pin of most chips and can not be overrided.
Off course this is the first candidate for a "reboot properly" button,
but there is no hardware support. That is why I used the power button,
which is ( more or less ) under software control.


> Gerhard
> 
> On Fri, 23 Mar 2001, David Balazic wrote:
> 
> > I had a similar experience:
> > X crashed , hosing the console , so I could not initiate
> > a proper shutdown.
> >
> > Here I must note that the response you got on linux-kernel is
> > shameful.
> >
> > What I did was to write a kernel/apmd patch , that performed a
> > proper shutdown when I press the power button ( which luckily
> > works as long as the kernel works ).
> >
> > Ask me for details, if interested.
> > The patch was for 2.2.x IIRC, so I would have to rewrite it almost
> > from scratch.
> >
> >
> > Otto Wyss ([EMAIL PROTECTED]) wrote :
> >
> > > Lately I had an USB failure, leaving me without any access to my system
> > > since I only use an USB-keyboard/-mouse. All I could do in that
> > > situation was switching power off and on after a few minutes of
> > > inactivity. From the impression I got during the following startup, I
> > > assume Linux (2.4.2, EXT2-filesystem) is not very suited to any power
> > > failiure or manually switching it off. Not even if there wasn't any
> > > activity going on.
> > >
> > > Shouldn't a good system allways try to be on the save side? Shouldn't
> > > Linux try to be more fail save? There is currently much work done in
> > > getting high performance during high activity but it seems there is no
> > > work done at all in getting a save system during low/no activity. I
> > > think this is a major drawback and should be addressed as fast as
> > > possible. Bringing a system to save state should allway have a high priority.
> > >
> > > How could this be accomplished:
> > > 1. Flush any dirty cache pages as soon as possible. There may not be any
> > > dirty cache after a certain amount of idle time.
> > > 2. Keep open files in a state where it doesn't matter if they where
> > > improperly closed (if possible).
> > > 3. Swap may not contain anything which can't be discarded. Otherwise
> > > swap has to be treated as ordinary disk space.
> > >
> > > These actions are not filesystem dependant. It might be that certain
> > > filesystem cope better with power failiure than others but still it's
> > > much better not to have errors instead to fix them.
> > >
> > > Don't we tell children never go close to any abyss or doesn't have
> > > alpinist a saying "never go to the limits"? So why is this simple rule
> > > always broken with computers?
> > >
> > > O. Wyss
> >
> > --
> > David Balazic
> > --
> > "Be excellent to each other." - Bill & Ted
> > - - - - - - - - - - - - - - - - - - - - - -
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to [EMAIL PROTECTED]
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> >
> 
> --
> Gerhard Mack
> 
> [EMAIL PROTECTED]
> 
> <>< As a computer I find your faith in technology amusing.


-- 
David Balazic
--
"Be excellent to each other." - Bill & Ted
- - - - - - - - - - - - - - - - - - - - - -
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Prevent OOM from killing init

[Horst von Brand]

Jonathan Morton <[EMAIL PROTECTED]> said:
> I'm currently investigating the old non-overcommit patch, which (apart from
> needing manual applying to recent kernels) appears to be rather broken in a
> trivial way.  It prevents allocation if total reserved memory is greater
> than the total unallocated memory.  Let me say that again, a different way
> - it prevents memory usage from exceeding 50%...

Think fork(2).
-- 
Horst von Brand [EMAIL PROTECTED]
Casilla 9G, Vin~a del Mar, Chile   +56 32 672616
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Q: How do I get from the latest stable kernel version to the latest prepatch version ?

[Hen, Shmulik]

Hi,

According to http://www.kernel.org, the latest stable kernel version is
2.4.2. The latest prepatch version is 2.4.3-pre3.

In order to get a full 2.4.3-pre8 kernel do I have to:

A. download linux-2.4.2.tar.gz and all the patch-2.4.3-preX.gz and apply
them in succession or,
B. download linux-2.4.3.tar.gz (exists ?) and then apply the all patches or,
C. download linux-2.4.3-pre7.tar.gz (exists ?) and apply only
patch-2.4.3-pre8.gz ?


Thanks,

Shmulik Hen
Software Engineer
Linux Advanced Networking Services
Network Communications Group, Israel (NCGj)
Intel Corporation Ltd.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.4.2 NINI_PARTITION

[Andrzej Krzysztofowicz]

"[EMAIL PROTECTED] wrote:"

> msdos.c MINI_PARTITION underclared (first use in this function)
> msdos.c MINI_NR_SUBPARTITIONS' undeclared (first use in this function)
> check msdos.c msdos.h
> can not find MINI_PARTITION/MINI_NR_SUBPARTITIONS

Do you mean MINIX_PARTITION ?
^ !!!

1. It is already fixed in 2.4.3-pre1 
2. Just don't compile Minix partition support if you don't need it and
   everything will be OK.

Andrzej
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

CML1 cleanup patch, take 2

[Eric S. Raymond]

OK, since peoples' territorial instincts have started to lather up,
I guess I'm going to have to do this the hard way...

This file is a patch expressed in two ways.  First, procedurally, as a
way to duplicate its effects on any kernel source tree.  Secondly, as
an explicit patch against 2.4.3-pre8.  It replaces my previous patch
against 2.4.3-pre6.

This patch is the first result of a consistency audit of the configuration 
system.  I have been building analysis tools to check the correctness of
my CML2 rules file, and the processs of testing them turned up some problems.

The purpose of this patch is threefold:

(1) Clean up two errors in the CML1 corpus that could lead to subtle bugs.
This is a BUG FIX in CML1.

(2) Fix up 20 cris-architecture configuration symbols lacking a CONFIG_
prefix, so they obey CML1/CML2 conventions and can be detected by
`make dep', also static-analysis tools and consistency checkers.
This is a BUG FIX in CML1.

(3) Fix up 10 configuration symbols of the form CONFIG_[0-9]*; specific 
changes are those suggested 8 Jan 2001 by PPC port maintainer Tom Rini.
This change has been APPROVED by an authorized maintainer.

This leaves ten symbols in a form that breaks CML2.  I'll go after
the other individual maintainers about those.  Sigh

No actual object code will be changed by this patch; it merely does
one-to-one substitutions on some configuration symbols.

Let me repeat that.  This patch changes *no* object code.  None.
However, merging it before the 2.5 fork will save me (and probably
Alan) some nasty large headaches later on...

For the procedural form, you will require the following Python 2.0 script:

 SCRIPT BEGINS HERE ---
#!/usr/bin/env python
#
# symbolreplace -- replace symbols in the current Linux source tree

import sys, os, re, getopt

renamings = {}  # Dictionary of translations
dobackup = 1
verbose = 0

#
# This is the only bit of knowledge in this script that knows anything
# about the lexical rules of the symbols we're looking for.  It's used as a
# guard expression on either side of each old symbol name -- matches
# must begin either with this guard or with a beginning-of-line, and end
# either with this guard or an end-of-line.  The purpose is to prevent false
# matches on FOO in FOOBAR and BARFOO.
#
guard = "[^A-Za-z0-9_]"

def backup(file):
"Create a backup for the given file."
# Compute where the RCS directory for this file should live.
# Create it if necessary.
rcs_dir = os.path.join(os.path.dirname(file), "RCS")
if not os.path.exists(rcs_dir):
os.mkdir(rcs_dir)

# If there is no RCS master corresponding to the file, create one,
rcs_file = os.path.join(rcs_dir, os.path.basename(file) + ",v")
if not os.path.exists(rcs_file):
os.system("ci -u -t- " + file + " >/dev/null 2>&1")

# Check out a working copy if needed.
if not os.access(file, os.W_OK):
os.system("co -l " + file + " >/dev/null 2>&1")

def treevisit(root, visitor):
"Apply the visitor function to every file under the given root path."
def treewalker(hook, dirname, files):
for file in files:
here = os.path.join(dirname, file)
if os.path.isfile(here) and here.find("RCS") == -1:
hook(here)
os.path.walk(root, treewalker, visitor)

def replacer(file):
if verbose:
print file

# Suck the entire file into core as a list of lines.
ifp = open(file, "r")
contents = ifp.read()
ifp.close()

# Now perform the substitution on each line.
substitutions = 0
for pattern in renamings.keys():
new_contents = pattern.sub(r"\1"+renamings[pattern]+r"\2", contents)
if new_contents != contents:
substitutions = substitutions + 1
contents = new_contents

# Spew the results.
if substitutions:
if dobackup:
backup(file)
ofp = open(file, "w")
ofp.write(contents)
ofp.close()

def read_translations(fp):
"Read translation requests from the given file object, ignoring comments."
while 1:
line = fp.readline()
if not line:
break
elif line[0] == '#' or line[0] == '\n':
continue
else:
(old, new) = line.split()
regexp = re.compile("(^|" + guard +")" + old + "(" + guard + "|$)")
renamings[regexp] = new

# Main sequence

if __name__ == '__main__': 
# Main sequence

# Process options
(options, arguments) = getopt.getopt(sys.argv[1:], "d:nv")
topdir = "."
for (switch, val) in options:
if (switch == '-d'):
topdir = val
elif (switch == '-n'):
dobackup = 0
elif (switch == '-v'):
verbose = 1

read_translations(sys.stdin)
treevisit(topdir, replacer)

# That's all, folks!
 SCRIPT ENDS HERE 

Re: question on /dev/tap0

[David Woodhouse]

[EMAIL PROTECTED] said:
>  Intended behaviour. This is because of the access checks done in the
> netlink code. Misleading, yes. 

I fixed the netlink code so it allowed this to work at one point. Search 
l-k archives for it.

--
dwmw2


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Prevent OOM from killing init

[Jonathan Morton]

>> I'm currently investigating the old non-overcommit patch, which (apart from
>> needing manual applying to recent kernels) appears to be rather broken in a
>> trivial way.  It prevents allocation if total reserved memory is greater
>> than the total unallocated memory.  Let me say that again, a different way
>> - it prevents memory usage from exceeding 50%...
>
>Think fork(2).

fork() is allowed to return a failure value, and it already does so if
there isn't enough memory (at least with the limited tests I've come up
with).  Guess again.

I have, however, found a bug in the non-overcommit patch - it seems to be
capable of double-freeing (and then some) - starting 4 Java VMs and then
closing them causes VMReserved to go negative on my system.

--
from: Jonathan "Chromatix" Morton
mail: [EMAIL PROTECTED]  (not for attachments)
big-mail: [EMAIL PROTECTED]
uni-mail: [EMAIL PROTECTED]

The key to knowledge is not to rely on people to teach you it.

Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/

-BEGIN GEEK CODE BLOCK-
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
-END GEEK CODE BLOCK-


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

ac25 - hang mounting swap

[J . A . Magallon]

On 03.26 Alan Cox wrote:
> 
> 2.4.2-ac25

It just hangs when init scripts try to activate swap. I will look at
what is init trying to mount and decode the info that Sysrq-P gives,
but if this suggests somebody anything already known...
Sysrq-p gives different info as time goes, so perhaps it is not stuck
but caught in an infinite loop trying to mount the only swap partition
I have.

All previous av worked fine.

-- 
J.A. Magallon  #  Let the source
mailto:[EMAIL PROTECTED]  #  be with you, Luke... 

Linux werewolf 2.4.2-ac24 #1 SMP Sat Mar 24 12:40:29 CET 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] kernel/exit.c - 2.4.2 - small optimalisation (very small) to do_exit()

[Heusden, Folkert van]

Hi,

This very small patches re-orders 2 if-statements so that in the
most common case 1 less if-statement is executed, in the worst
case the same number of if-statements is executed (doesn't matter
though: it's would be the fault-situation anyway).

diff -ur --minimal linux-vanilla/kernel/exit.c linux-2.4.2/kernel/exit.c
--- linux-vanilla/kernel/exit.c Mon Mar 26 09:28:13 2001
+++ linux-2.4.2/kernel/exit.c   Mon Mar 26 10:50:30 2001
@@ -425,10 +425,12 @@
 
if (in_interrupt())
panic("Aiee, killing interrupt handler!");
-   if (!tsk->pid)
-   panic("Attempted to kill the idle task!");
-   if (tsk->pid == 1)
-   panic("Attempted to kill init!");
+   if (tsk->pid <= 1) {
+   if (tsk->pid)
+   panic("Attempted to kill init!");
+   else
+   panic("Attempted to kill the idle task!");
+   }
tsk->flags |= PF_EXITING;
del_timer_sync(&tsk->real_timer);


Greetings,

Folkert van Heusden ([EMAIL PROTECTED])
[ www.vanheusden.com ]

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Announce: modutils 2.4.4 is available

[Keith Owens]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

Another small collection of bug fixes.  No new facilities.

ftp://ftp..kernel.org/pub/linux/utils/kernel/modutils/v2.4

modutils-2.4.4.tar.gz   Source tarball, includes RPM spec file
modutils-2.4.4-1.src.rpmAs above, in SRPM format
modutils-2.4.4-1.i386.rpm   Compiled with egcs-2.91.66, glibc 2.1.2
modutils-2.4.4-1.sparc64.rpmCombined sparc 32/64.
modutils-2.4.4-1.ia64.rpm   Compiled with gcc 2.96-ia64-000717 snap 001117,
libc-2.2.1.
patch-modutils-2.4.4.gz Patch from modutils 2.4.3 to 2.4.4.

Related kernel patches.

patch-2.4.2-persistent.gz   Adds persistent data and generic string
support to kernel 2.4.2.  Optional.

Changelog extract

* Do not generate filenames when reading nested config files.
* depmod ignored user prune commands, reported by Kristofer T. Karas.
* Change error message for short ELF header.
* Missing commas in alias list.  Urs Thuermann.
* Print an error message when genksyms detects a bad kernel version.
  Mark McLoughlin
* modinfo default changed to filename, description, author, parameters.
  Mark McLoughlin

I will not be supporting modutils, ksymoops or kdb for the next 4
weeks; time for a holiday, probably without net access.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.3 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999

iD8DBQE6vxOdi4UHNye0ZOoRAvw+AKCK7IKCyxMEW8CqjXS4HLnKIQn2zgCguVIs
8Eu5DSDyqb4LfumqQ9ATTFQ=
=vg9V
-END PGP SIGNATURE-

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

BUG in reiserfs with 2.4.2-ac20 + linux-aic7xxx Rev 6.1.7

[Jean Charles Delepine]

Hello,

[dmesg, /proc/cpuinfo, /proc/interrupt, mount, ... at end of mail]
 
Mar 25 06:53:10 gip2 kernel: scsi1: PCI error Interrupt at seqaddr = 0x8
Mar 25 06:53:10 gip2 kernel: scsi1: Data Parity Error Detected during address or write 
data phase
Mar 25 06:53:55 gip2 kernel: scsi1: PCI error Interrupt at seqaddr = 0x8
Mar 25 06:53:55 gip2 kernel: scsi1: Data Parity Error Detected during
address or write data phase

I have many of them. Before I upgrade to linux-aic7xxx Rev 6.1.7. I 
experienced some freeze with the stock 2.4.2 and with 2.2 with many
scsi : aborting command due to timeout.

This one is new and not on the scsi1 interface :

Mar 25 06:56:50 gip2 kernel: journal_begin called without kernel lock held
Mar 25 06:56:50 gip2 kernel: kernel BUG at journal.c:423!

Thru ksymoops :

kernel BUG at journal.c:423!
invalid operand: 
CPU:0
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010286
eax: 001d   ebx:    ecx: c0227880   edx: 0282
esi: c19ad000   edi: c56f1f00   ebp: 0018   esp: c56f1e80
ds: 0018   es: 0018   ss: 0018
Process sort (pid: 30642, stackpage=c56f1000)
Stack: e086d384 01a7 e0865432 e086e3a1 c56f1f00 de13f9a0   
   3abd7a92 0003 c013675f dcbec5c0 1000 dcbec5c0 e086566a c56f1f00 
   c19ad000 0018  e0852ff8 c56f1f00 c19ad000 0018  
Call Trace: [] [] [] [] [] 
[] [] 
   [] [] [] [] [] [] 
Code: 0f 0b 83 c4 08 c3 8d 76 00 31 c0 c3 90 31 c0 c3 90 56 53 31 

>>EIP; e0862f7b <[reiserfs]reiserfs_check_lock_depth+33/3c>   <=
Trace; e086d384 <[reiserfs].rodata.start+4ce4/6b7a>
Trace; e0865432 <[reiserfs]do_journal_begin_r+2a/230>
Trace; e086e3a1 <[reiserfs].rodata.start+5d01/6b7a>
Trace; c013675f 
Trace; e086566a <[reiserfs]journal_begin+16/1c>
Trace; e0852ff8 <[reiserfs]reiserfs_truncate_file+98/194>
Trace; c0125469 
Trace; e0853fc0 <[reiserfs]reiserfs_vfs_truncate_file+c/10>
Trace; c0123724 
Trace; c01284b9 
Trace; c0132a0b 
Trace; c0108f3b 
Trace; c010002b 
Code;  e0862f7b <[reiserfs]reiserfs_check_lock_depth+33/3c>
 <_EIP>:
Code;  e0862f7b <[reiserfs]reiserfs_check_lock_depth+33/3c>   <=
   0:   0f 0b ud2a  <=
Code;  e0862f7d <[reiserfs]reiserfs_check_lock_depth+35/3c>
   2:   83 c4 08  add$0x8,%esp
Code;  e0862f80 <[reiserfs]reiserfs_check_lock_depth+38/3c>
   5:   c3ret
Code;  e0862f81 <[reiserfs]reiserfs_check_lock_depth+39/3c>
   6:   8d 76 00  lea0x0(%esi),%esi
Code;  e0862f84 <[reiserfs]push_journal_writer+0/4>
   9:   31 c0 xor%eax,%eax
Code;  e0862f86 <[reiserfs]push_journal_writer+2/4>
   b:   c3ret
Code;  e0862f87 <[reiserfs]push_journal_writer+3/4>
   c:   90nop
Code;  e0862f88 <[reiserfs]pop_journal_writer+0/4>
   d:   31 c0 xor%eax,%eax
Code;  e0862f8a <[reiserfs]pop_journal_writer+2/4>
   f:   c3ret
Code;  e0862f8b <[reiserfs]pop_journal_writer+3/4>
  10:   90nop
Code;  e0862f8c <[reiserfs]dump_journal_writers+0/30>
  11:   56push   %esi
Code;  e0862f8d <[reiserfs]dump_journal_writers+1/30>
  12:   53push   %ebx
Code;  e0862f8e <[reiserfs]dump_journal_writers+2/30>
  13:   31 00 xor%eax,(%eax)

Linux gip2 2.4.2-ac20-p1 #4 SMP Thu Mar 22 13:28:35 CET 2001 i686 unknown
Kernel modules 2.4.2
Gnu C  2.95.2
Gnu Make   3.79.1
Binutils   2.9.5.0.37
Linux C Library2.1.3
Dynamic linker ldd: version 1.9.11
Procps 2.0.6
Mount  2.10q
Net-tools  2.05
Console-tools  0.2.3
Sh-utils   2.0
Modules Loaded reiserfs 3c59x
reiserfsprogs  3.x.0d

$ mount
/dev/sdh3 on / type ext2 (rw,errors=remount-ro,errors=remount-ro)
proc on /proc type proc (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sdh2 on /boot type ext2 (rw)
/dev/sdh5 on /usr type ext2 (rw)
/dev/sdc1 on /var type reiserfs (rw)
/dev/sdc2 on /var/log type reiserfs (rw)
/dev/sda1 on /var/spool/cyrus type reiserfs (rw)
/dev/sdb1 on /www type ext2 (rw,noatime)
/dev/sdd1 on /var/spool/squid/1 type reiserfs (rw,noatime)
/dev/sde1 on /var/spool/squid/2 type reiserfs (rw,noatime)
/dev/sdf1 on /var/spool/squid/3 type reiserfs (rw,noatime)
/dev/sdg1 on /var/spool/squid/4 type reiserfs (rw,noatime)

sda to sdg are on a gdth interface.
sdh (was sda before 2.4.2-ac or the new linux-aic) is on an adaptec.

processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 7
model name  : Pentium III (Katmai)
stepping: 3
cpu MHz : 501.138
cache size  : 512 KB
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level :

Re: Linux should better cope with power failure

[David Balazic]

Otto Wyss wrote:
> 
> > I had a similar experience:
> > X crashed , hosing the console , so I could not initiate
> > a proper shutdown.
> >
> > Here I must note that the response you got on linux-kernel is
> > shameful.
> >
> Thanks, but I expected it a little bit. All around Linux is centered
> around getting the highest performance out of it and very low (to low
> IMHO) is done to have a save system. The attitude "It doesn't matter
> making mistakes, they get fix anyhow" annoys me most, especially if it
> were easy to prevent them.
> 
> > What I did was to write a kernel/apmd patch , that performed a
> > proper shutdown when I press the power button ( which luckily
> > works as long as the kernel works ).
> >
> Not with a AT power supply but certainly nice to have. See that it gets
> included into the kernel.

It was just a line or two bugfix, not a real patch. I will dig it up
and send a patch for 2.4 
When I have the time :-)


-- 
David Balazic
--
"Be excellent to each other." - Bill & Ted
- - - - - - - - - - - - - - - - - - - - - -
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Can't compile 2.4.2-ac25

[Chung Won-young]

sorry...

Try this:

--- es1370.orig Mon Mar 26 18:15:06 2001
+++ es1370.cMon Mar 26 17:47:54 2001
@@ -170,6 +170,8 @@
 struct gameport {
int io;
int size;
+   void (*trigger)(struct gameport *);
+   unsigned char (*read)(struct gameport *);
 };

 extern inline void gameport_register_port(struct gameport *gameport)


- ÆóÀÎ -

ICQ : 36602496
E - Mail : [EMAIL PROTECTED], [EMAIL PROTECTED]
Homepage : http://kernel.pe.kr, http://pain.kernel.pe.kr

On Mon, 26 Mar 2001, Andrzej Krzysztofowicz wrote:

> "Chung Won-young wrote:"
> > Try this:
> >
> > --- es1370.orig Mon Mar 26 18:15:06 2001
> > +++ es1370.cMon Mar 26 17:47:54 2001
> > @@ -170,6 +170,8 @@
> >  struct gameport {
> >  int io;
> >  int size;
> >  +   void (*trigger)(struct gameport *);
> >  +   unsigned char (*read)(struct gameport *);
> >   };
> >
> > extern inline void gameport_register_port(struct gameport 
>*gameport)
>
>
> Looks strange...
> gpm's copy & paste + joe ?
> :)
>
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux should better cope with power failure

[David Balazic]

David ( Ford ) , I think you are misunderstanding a bit here.
The problem here is not that a fsck is needed after an unclean umount,
but that users are forced to corrupt ( by unclean umount due to reset or
poweroff ) their perfectly good file system on a "perfectly" working
system, when their keyboard goes wacko ( happens more often than you might
think, just remember those "log in over net and run 'shutdown -r'" advice's )

David Ford wrote:
> 
> Otto Wyss wrote:
> 
> > > I had a similar experience:
> > > X crashed , hosing the console , so I could not initiate
> > > a proper shutdown.
> > >
> > > Here I must note that the response you got on linux-kernel is
> > > shameful.
> > >
> > Thanks, but I expected it a little bit. All around Linux is centered
> > around getting the highest performance out of it and very low (to low
> > IMHO) is done to have a save system. The attitude "It doesn't matter
> > making mistakes, they get fix anyhow" annoys me most, especially if it
> > were easy to prevent them.
> 
> No, the correct answer is if you want a reliable recovery then run your disks
> in non write buffered mode.  I.e. turn on sync in fstab.
> 
> It's all about RTFM and knowing the difference between buffered actions and
> nonbuffered.
> 
> Everything you need to have a safely clean and proper crash recovery system
> already is within your power, you just need to read the man pages and fix
> your fstab instead of blaming linux-kernel for bad attitudes.
> 
> Yes, it's very easy to prevent e2fsck runs.  Run synchronous or journaled
> file systems.
> 
> > > > Don't we tell children never go close to any abyss or doesn't have
> > > > alpinist a saying "never go to the limits"? So why is this simple rule
> > > > always broken with computers?
> > > >
> > Is there a similar expression which could be hammered into any
> > developers mind, i.e. "Don't make errors, others already do them for you".
> 
> There is also a very common expression...RTFM.
> 
> Please understand what you are doing before you do it, particularly before
> you bad mouth others for having a bad attitude.  Don't blame race car makers
> for destructive engine failure when you expect it to act like a family car.
> 
> -d
> 
> --
>   There is a natural aristocracy among men. The grounds of this are virtue and 
>talents. Thomas Jefferson
>   The good thing about standards is that there are so many to choose from. Andrew S. 
>Tanenbaum


-- 
David Balazic
--
"Be excellent to each other." - Bill & Ted
- - - - - - - - - - - - - - - - - - - - - -
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

a 2.4.2 kernel oops...

[Pierfrancesco Caci]

*** please Cc to [EMAIL PROTECTED] when replying ***

Hi, I sent a similar report a couple of weeks ago but got no
response. Can Someone Who Knows (TM) please have a look at it and tell
me what's wrong with this Olivetti Netstrada? It works with 2.2.18 but
all the 2.4.x kernels didn't work so far. I tried also changing
compile options, eliminating all that is not strictly necessary to
boot, but got the same error.

here is it:

Linux version 2.4.2 (root@paperino) (gcc version 2.95.3 20010219 (prerelease)) #1 Fri 
Mar 16 15:23:30 CET 2001
BIOS-provided physical RAM map:
 BIOS-e801: 0009f000 @  (usable)
 BIOS-e801: 41505000 @ 0010 (usable)
Warning only 896MB will be used.
Use a HIGHMEM enabled kernel.
On node 0 totalpages: 229376
zone(0): 4096 pages.
zone(1): 225280 pages.
zone(2): 0 pages.
Kernel command line: BOOT_IMAGE=test ro root=802 BOOT_FILE=/vmlinuz.test 
console=ttyS0,9600
Initializing CPU#0
Detected 200.012 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 398.95 BogoMIPS
Memory: 899624k/917504k available (1320k kernel code, 17492k reserved, 450k data, 84k 
init, 0k highmem)
Dentry-cache hash table entries: 131072 (order: 8, 1048576 bytes)
Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes)
Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
VFS: Diskquotas version dquot_6.4.0 initialized
CPU: Before vendor init, caps: fbff  , vendor = 0
CPU: L1 I cache: 8K, L1 D cache: 8K
CPU: L2 cache: 512K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: After vendor init, caps: fbff   
CPU: After generic, caps: fbff   
CPU: Common caps: fbff   
CPU: Intel Pentium Pro stepping 09
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
general protection fault: 
CPU:0
EIP:0010:[]
EFLAGS: 00010246
eax:    ebx:    ecx: 0072   edx: c013cff4
esi: f7fbf000   edi:    ebp: f7fbf000   esp: c1efff2c
ds: 0018   es: 0018   ss: 0018
Process swapper (pid: 1, stackpage=c1eff000)
Stack:  c1ef70c0 c0123d59  c1ef70c0 0001 c1ef70c0 0246 
   0007 c02b5538 0001 c0123e3f c1ef70c0 0007 c1ef6200 c1ef6200 
    c013da82 c1ef70c0 0007 c1ef6200 c01e5543 c1ef6200 0001 
Call Trace: [] [] [] [] [] 
[] [] 
   [] 

Code: f3 ab 8d 93 90 00 00 00 c7 83 90 00 00 00 00 00 00 00 8d 83 
Kernel panic: Attempted to kill init!




CPU:0
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax:    ebx:    ecx: 0072   edx: c013cff4
esi: f7fbf000   edi:    ebp: f7fbf000   esp: c1efff2c
ds: 0018   es: 0018   ss: 0018
Process swapper (pid: 1, stackpage=c1eff000)
Stack:  c1ef70c0 c0123d59  c1ef70c0 0001 c1ef70c0 0246 
   0007 c02b5538 0001 c0123e3f c1ef70c0 0007 c1ef6200 c1ef6200 
    c013da82 c1ef70c0 0007 c1ef6200 c01e5543 c1ef6200 0001 
Call Trace: [] [] [] [] [] 
[] [] 
   [] 
Code: f3 ab 8d 93 90 00 00 00 c7 83 90 00 00 00 00 00 00 00 8d 83 

>>EIP; c013d013<=
Trace; c0123d59 
Trace; c0123e3f 
Trace; c013da82 
Trace; c01e5543 
Trace; c012feac 
Trace; c0130432 
Trace; c0107007 
Trace; c0107424 
Code;  c013d013 
 <_EIP>:
Code;  c013d013<=
   0:   f3 ab repz stos %eax,%es:(%edi)   <=
Code;  c013d015 
   2:   8d 93 90 00 00 00 lea0x90(%ebx),%edx
Code;  c013d01b 
   8:   c7 83 90 00 00 00 00  movl   $0x0,0x90(%ebx)
Code;  c013d022 
   f:   00 00 00 
Code;  c013d025 
  12:   8d 83 00 00 00 00 lea0x0(%ebx),%eax

Kernel panic: Attempted to kill init!

970 warnings issued.  Results may not be reliable.
(this is because I ran it on a different machine, the system.map was
the one from the crashing kernel, though)

Also, I just realized that this stupid bios tells the kernel to have a
lot of memory, while it only has 128 M (see the line just at the
beginning of the boot output).

here's what's inside this machine:


root@mirror:~ # lspci -v
00:03.0 Ethernet controller: Digital Equipment Corporation DECchip 21041 [Tulip Pass 
3] (rev 11)
Flags: bus master, medium devsel, latency 96, IRQ 11
I/O ports at ec00
Memory at df00 (32-bit, non-prefetchable)
Expansion ROM at de00 [disabled]

00:05.0 Non-VGA unclassified device: Intel Corporation 82375EB (rev 15)
Flags: bus master, medium devsel, latency 248

00:14.0 RAM memory: Intel Corporation 450KX/GX [Orion] - 82453KX/GX Memory controller 
(rev 05)
Flags: fast devsel

00:19.0 Host bridge: Intel Corporation 450KX/GX [Orion] - 82454KX/GX PCI bridge (rev 
06)
Flags: bus

ASSISTANCE

[mani elisabeth]

FROM : MRS ELIZABETH NKEIRU-MANI

RE : MONEY TRANSFER.

Dear Sir, 

I know my message will come to you as a surprise.
Don’t worry I was totally convinced to write you in
reference of the transfer of US$23 M to your account
for onward investment (hotel industries) in your
country. I am Mrs ELIZABETH NKEIRU MANI the second
wife of the former chief of defence-staff late General
HANIS MANI MANI of Guinea Bissau. My late husband was
killed just last year December following his role as a
rebel leader against the past government of Guinea
Bissau as of 1998. Following this political crisis, we
were forced to leave our country to Abidjan the
capital city of Cote d’Ivoire for our life sake. It is
here in Abidjan he deposited this said money in a
private security company as a family valuables. We got
to know about this information and as well able to
recover all the relevant documents regards to this
deposits through his foreign adviser here in Abidjan.
If you are thus and truly disposed to assist us in
transferring of this fund kindly write me through my
e-mail address. More information about the lifting of
this funds legally follows immediately after your and
positive reply. 

NB: Please kindly contact my son JAMES with interest
on phone number (225) 07-60-29-61.

Thank “you for your maximum co-operation.

MRS ELIZABETH NKEIRU MANI For the family.






__
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail. 
http://personal.mail.yahoo.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Announce] kdb v1.8 updates are available

[Keith Owens]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Content-Type: text/plain; charset=us-ascii

http://oss.sgi.com/projects/kdb/download/ix86/ contains patches for kdb
v1.8 against 2.4.3-pre8 and 2.4.2-ac25.

This update is just to sync with the current kernels.  No new
facilities.

I will not be supporting modutils, ksymoops or kdb for the next 4
weeks; time for a holiday, probably without net access.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.3 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999

iD8DBQE6vxRfi4UHNye0ZOoRAttRAKChrzaPXo2mWN+bQeDMmptWGUxyXACgimYy
NW8ez9vlskwwRcqeqHGoRTg=
=AMeq
-END PGP SIGNATURE-

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

intercept key press

[Kumar, Bharath]

Hi !

  I am Bharath . I am using Red Hat 2.2 
  I am looking for reasons rather than solution to my question.
  Is it possible to intercept the key press so that you can execute 
  your own routine than a default routine for key press . 
  For Eg : It is possible for you send what ever you type on keybord 
  to log file then display it on console .
  If the answer is Yes please do tell me how to go about it . 
  Any suggestions on this matter will be duly appreciated . I have not
subscribed
  to the list hence ,I kindly request to send your valuable suggestions by
CC ing to
  this mail-ID : [EMAIL PROTECTED] 

With regards
Bharath



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: ASSISTANCE

[Mark Mitchell]

Wonder if the spam program's running on Linux...?


mani elisabeth wrote:
> 
> FROM : MRS ELIZABETH NKEIRU-MANI
> 
> RE : MONEY TRANSFER.
> 
> Dear Sir,
> 
> I know my message will come to you as a surprise.
> Don’t worry I was totally convinced to write you in
> reference of the transfer of US$23 M to your account
> for onward investment (hotel industries) in your
> country. I am Mrs ELIZABETH NKEIRU MANI the second
> wife of the former chief of defence-staff late General
> HANIS MANI MANI of Guinea Bissau. My late husband was
> killed just last year December following his role as a
> rebel leader against the past government of Guinea
> Bissau as of 1998. Following this political crisis, we
> were forced to leave our country to Abidjan the
> capital city of Cote d’Ivoire for our life sake. It is
> here in Abidjan he deposited this said money in a
> private security company as a family valuables. We got
> to know about this information and as well able to
> recover all the relevant documents regards to this
> deposits through his foreign adviser here in Abidjan.
> If you are thus and truly disposed to assist us in
> transferring of this fund kindly write me through my
> e-mail address. More information about the lifting of
> this funds legally follows immediately after your and
> positive reply.
> 
> NB: Please kindly contact my son JAMES with interest
> on phone number (225) 07-60-29-61.
> 
> Thank “you for your maximum co-operation.
> 
> MRS ELIZABETH NKEIRU MANI For the family.
> 
> __
> Do You Yahoo!?
> Get email at your own domain with Yahoo! Mail.
> http://personal.mail.yahoo.com/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Pls see

[Sujit Kumar]

> Can anybody help me with the exact utility of the fn 
> 
> rdtsc( )  ??
> 
> 
> Thx 
> 
> Regards
> Sujit Kumar
> 
> DCM Technologies
> 125, Udyog Vihar, Phase - I
> Gurgaon.
> Phone: 91-6398001-08
> 
> Remember it was Amateurs who built the Ark and Professionals who built the
> Titanic .
> 
> 
> 
> ___
> Redhat-devel-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-devel-list
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: ASSISTANCE

[Juha Saarinen]

This is a variant on the Nigerian Scam... avoid at all cost.

:: -Original Message-
:: From: [EMAIL PROTECTED]
:: [mailto:[EMAIL PROTECTED]]On Behalf Of mani elisabeth
:: Sent: Monday, March 26, 2001 10:24 PM
:: To: [EMAIL PROTECTED]
:: Subject: ASSISTANCE
:: 
:: 
:: FROM : MRS ELIZABETH NKEIRU-MANI



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

slow latencies on IDE disk drives( controller? )

[Uncle George]

I am processing sound data on /dev/dsp. Generally the ~61k devive buffer
is enough to keep the device satiated && gives the program time to fill
up the device buffer when there is 16k of buffer space that needs to be
filled.

But on occasion the /dev/dsp device "slurrs" ( sounds like what happens
when the speed of a tape recorder slows down due to a finger placed down
on the capstain ) unexpectedly. This was eventually traced to the usage
of an IDE disk drive. using the scsi drive does not cause the problem to
manifest itself( at least my ears say so ). but using "dd if=/dev/hda4
of=/dev/null ) does immediately cause the slurring to happen.


I think I can create a simple pgm to demo this problem, but the DATA
file that gets feed into /dev/dsp is a little large for e-mail.


/gat

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[BUG] vmalloc_area_pages() in 2.4.2-ac25

[Tachino Nobuhiro]

  vmalloc_area_pages() in 2.4.2-ac25 seems to be broken. It calls
spin_lock(&init_mm.page_table_lock) twice and causes system hang.



inline int vmalloc_area_pages (unsigned long address, unsigned long size,
   int gfp_mask, pgprot_t prot)
{
pgd_t * dir;
unsigned long end = address + size;
int ret;

dir = pgd_offset_k(address);
flush_cache_all();
spin_lock(&init_mm.page_table_lock);
do {
pmd_t *pmd;

spin_lock(&init_mm.page_table_lock);/* pmd_alloc requires this */
pmd = pmd_alloc(&init_mm, dir, address);
spin_unlock(&init_mm.page_table_lock);
ret = -ENOMEM;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2.4.3pre8 - fail to compile af_ipx.c, omission from drivers/net/Makefile

[Eran Mann]

Apparently net_init.o is missing from export-objs in 
drivers/net/Makefile in kernel 2.4.3.pre8, which causes network modules
to fail to load.

Additionally, trying to compile IPX in 2.4.3pre8 results in the
following errors:
make[2]: Entering directory `/mdk/src/linux-2.4.3/net/ipx'
gcc -D__KERNEL__ -I/mdk/src/linux-2.4.3/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i686 -DMODULE -DMODVERSIONS -include
/mdk/src/linux-2.4.3/include/linux/modversions.h   -DEXPORT_SYMTAB -c
af_ipx.c
af_ipx.c: In function `ipxrtr_route_packet':
af_ipx.c:1545: warning: passing arg 4 of `sock_alloc_send_skb_R05cfeed4'
makes integer from pointer without a cast
af_ipx.c:1545: too few arguments to function
`sock_alloc_send_skb_R05cfeed4'
af_ipx.c: At top level:
af_ipx.c:2534: unknown field `sendpage' specified in initializer
af_ipx.c:2534: `sock_no_sendpage' undeclared here (not in a function)
af_ipx.c:2534: warning: excess elements in struct initializer
af_ipx.c:2534: warning: (near initialization for `ipx_dgram_ops')
make[2]: *** [af_ipx.o] Error 1
make[2]: Leaving directory `/mdk/src/linux-2.4.3/net/ipx'
make[1]: *** [_modsubdir_ipx] Error 2
make[1]: Leaving directory `/mdk/src/linux-2.4.3/net'
make: *** [_mod_net] Error 2

These patches fix the above problems:
===
--- linux-2.4.3pre8.orig/drivers/net/Makefile   Mon Mar 26 13:16:17 2001
+++ linux/drivers/net/Makefile  Mon Mar 26 12:03:26 2001
@@ -16,7 +16,7 @@
 # This list comes from 'grep -l EXPORT_SYMBOL *.[hc]'.
 
 export-objs := 8390.o arlan.o aironet4500_core.o aironet4500_card.o
ppp_async.o \
-   ppp_generic.o slhc.o pppox.o auto_irq.o
+   ppp_generic.o slhc.o pppox.o auto_irq.o net_init.o
 
 ifeq ($(CONFIG_TULIP),y)
   obj-y += tulip/tulip.o
=
--- linux-2.4.3pre8.orig/net/ipx/af_ipx.c   Mon Mar 26 13:17:08 2001
+++ linux/net/ipx/af_ipx.c  Mon Mar 26 13:14:52 2001
@@ -1542,7 +1542,7 @@
ipx_offset = intrfc->if_ipx_offset;
size = sizeof(struct ipxhdr) + len + ipx_offset;
 
-   skb = sock_alloc_send_skb(sk, size, noblock, &err);
+   skb = sock_alloc_send_skb(sk, size, 0, noblock, &err);
if (!skb)
goto out_put;
 
@@ -2531,7 +2531,6 @@
sendmsg:ipx_sendmsg,
recvmsg:ipx_recvmsg,
mmap:   sock_no_mmap,
-   sendpage:   sock_no_sendpage,
 };
 
 #include 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] OOM handling

[Ingo Oeser]

On Sun, Mar 25, 2001 at 09:13:20PM -0500, Matthew Chappee wrote:
> The point being, my database shouldn't be selected for
> termination.  Nobody ever got fired for kill -9'ing netscape,
> but Oracle is a different story.  I urge you, consider the
> patch.

No, you got fired for not setting ulimits. Your boss is right
then!

ulimit -d 65536
ulimit -v 81920

and my netscape is very happy most of the time.

And my system is not disturbed.

64MB RAM + 256MB swap.

In a school I had the same setup on a 256MB server (256MB swap)
serving apps (StarOffice and Netscape) to  ~16 X clients.

I never had OOM there.

I think this is the amount of memory an oracle server at least
have to have, right?

What are your ulimits? What are your amounts of RAM+SWAP?

Regards

Ingo Oeser
-- 
10.+11.03.2001 - 3. Chemnitzer LinuxTag 
  been there and had much fun   
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] OOM handling

[Jasper Spaans]

On Mon, Mar 26, 2001 at 01:33:05PM +0200, Ingo Oeser wrote:
> > The point being, my database shouldn't be selected for
> > termination.  Nobody ever got fired for kill -9'ing netscape,
> > but Oracle is a different story.  I urge you, consider the
> > patch.
> 
> No, you got fired for not setting ulimits. Your boss is right
> then!
> 
> ulimit -d 65536
> ulimit -v 81920

Ehm, right.

Running netscape (or any other memory hog which doesn't belong on a server)
on a production server seems reason enough for a little talk with your boss.

On the other hand, if no other apps are running on your box, and Oracle gets
killed due to OOM, you probably have underestimated your hardware needs, or
Oracle has gone haywire, which is a good reason for killing it.

Thus, nothing seems wrong with the current kill algorithm to me...

Just my two cents,
-- 
  Q_.   Jasper Spaans <[EMAIL PROTECTED]>
 `~\http://jsp.ds9a.nl/
Mr /\   Tel/Fax: +31-20-8749842
Zap Move all .sig for great justice!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [kbuild-devel] Re: CML1 cleanup patch

[John Cowan]

esr scripsit:

> I could have done this, allowing tokens to be recognized as numeric only
> if all chars are digits.  I didn't, for two reasons: (1) Lexical analysis
> is, as it turns out, a hotspot in the CML2 compiler code -- the last thing
> it needs is more overhead, and (2) interpreting symbols with leading digits
> as nonnumeric tokens is just *wrong*.  Ugh.  Violates the Principle of Least
> Surprise big-time.

In fact this has come up before: in Usenet software, which has to differentiate
between an article and a sub-newsgroup.  An article has to have an all-numeric
name, and It Would Have Been Nice if all newsgroup names began with non-digits,
but then there was comp.bugs.4bsd.

-- 
John Cowan   [EMAIL PROTECTED]
One art/there is/no less/no more/All things/to do/with sparks/galore
--Douglas Hofstadter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [BUG] vmalloc_area_pages() in 2.4.2-ac25

[Andrew Morton]

Tachino Nobuhiro wrote:
> 
>   vmalloc_area_pages() in 2.4.2-ac25 seems to be broken. It calls
> spin_lock(&init_mm.page_table_lock) twice and causes system hang.
> 

Yes, it would.  Delete the innermost lock and unlock.


--- linux-2.4.2-ac25/mm/vmalloc.c   Mon Mar 26 21:38:38 2001
+++ ac/mm/vmalloc.c Mon Mar 26 21:52:05 2001
@@ -152,9 +152,7 @@
do {
pmd_t *pmd;

-   spin_lock(&init_mm.page_table_lock);/* pmd_alloc requires this */
pmd = pmd_alloc(&init_mm, dir, address);
-   spin_unlock(&init_mm.page_table_lock);
ret = -ENOMEM;
if (!pmd)
break;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Q: How do I get from the latest stable kernel version to the late st prepatch version ?

[Leonid Mamtchenkov]

Hello Hen, Shmulik,

Once you wrote about "Q: How do I get from the latest stable kernel version to the 
late st prepatch version ?":
HS> According to http://www.kernel.org, the latest stable kernel version is
HS> 2.4.2. The latest prepatch version is 2.4.3-pre3.
HS> 
HS> In order to get a full 2.4.3-pre8 kernel do I have to:
HS> 
HS> A. download linux-2.4.2.tar.gz and all the patch-2.4.3-preX.gz and apply
HS> them in succession or,
HS> B. download linux-2.4.3.tar.gz (exists ?) and then apply the all patches or,
HS> C. download linux-2.4.3-pre7.tar.gz (exists ?) and apply only
HS> patch-2.4.3-pre8.gz ?

Download 2.4.2 and then apply 2.4.3-preX (latest) on it... that's it.
You might want to visit http://kernelnewbies.org .  They have some good docs
there.

-- 
 Best regards,
 Leonid Mamtchenkov
 System Administrator

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] static zero initializers removal

[Andrey Panin]

Hi all,

this patch (against 2.4.2-ac25) removes many static zero initializers from
various parts of kernel.

Best regards.

-- 
Andrey Panin| Embedded systems software engineer
[EMAIL PROTECTED]| PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc
 patch-zeroinit.bz2
 PGP signature

Re: [BUG] vmalloc_area_pages() in 2.4.2-ac25

[Andrew Morton]

Andrew Morton wrote:
> 
> Tachino Nobuhiro wrote:
> >
> >   vmalloc_area_pages() in 2.4.2-ac25 seems to be broken. It calls
> > spin_lock(&init_mm.page_table_lock) twice and causes system hang.
> >
> 
> Yes, it would.  Delete the innermost lock and unlock.
> 

And the other one.

--- linux-2.4.2-ac25/mm/vmalloc.c   Mon Mar 26 21:38:38 2001
+++ ac/mm/vmalloc.c Mon Mar 26 22:49:29 2001
@@ -126,9 +126,7 @@
do {
pte_t * pte;
 
-   spin_lock(&init_mm.page_table_lock);/* pte_alloc requires this */
pte = pte_alloc(&init_mm, pmd, address);
-   spin_unlock(&init_mm.page_table_lock);
if (!pte)
return -ENOMEM;
if (alloc_area_pte(pte, address, end - address, gfp_mask, prot))
@@ -152,9 +150,7 @@
do {
pmd_t *pmd;

-   spin_lock(&init_mm.page_table_lock);/* pmd_alloc requires this */
pmd = pmd_alloc(&init_mm, dir, address);
-   spin_unlock(&init_mm.page_table_lock);
ret = -ENOMEM;
if (!pmd)
break;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: CML1 cleanup patch, take 2

[Bjorn Wesen]

On Mon, 26 Mar 2001, Eric S. Raymond wrote:
> (2) Fix up 20 cris-architecture configuration symbols lacking a CONFIG_
> prefix, so they obey CML1/CML2 conventions and can be detected by
> `make dep', also static-analysis tools and consistency checkers.
> This is a BUG FIX in CML1.

No need for you to fret on this; it's partly fixed in the version in
Alan's tree and the rest will be cleaned up in our next update.

-Bjorn

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: CML1 cleanup patch, take 2

[Eric S. Raymond]

Bjorn Wesen <[EMAIL PROTECTED]>:
> On Mon, 26 Mar 2001, Eric S. Raymond wrote:
> > (2) Fix up 20 cris-architecture configuration symbols lacking a CONFIG_
> > prefix, so they obey CML1/CML2 conventions and can be detected by
> > `make dep', also static-analysis tools and consistency checkers.
> > This is a BUG FIX in CML1.
> 
> No need for you to fret on this; it's partly fixed in the version in
> Alan's tree and the rest will be cleaned up in our next update.

Good!  That will simplify my life a lot.  Assuming Linus takes that ac patch.

Greg Banks may have suggested a tolerable solution to the other problem.
I'm working on it now.
-- 
http://www.tuxedo.org/~esr/">Eric S. Raymond

There's a truism that the road to Hell is often paved with good intentions.
The corollary is that evil is best known not by its motives but by its
*methods*.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

kernel 243p8 problems

[Mario Mikocevic]

Hi,

1st :

# depmod -a 2.4.3-pre8
depmod: *** Unresolved symbols in /lib/modules/2.4.3-pre8/kernel/drivers/net/dummy.o
depmod: *** Unresolved symbols in /lib/modules/2.4.3-pre8/kernel/drivers/net/eepro100.o

the rest :

it's Compaq PL 6500 with 4 penguins and 2 gig RAM
Compaq SMART2 hardware RAID and DLT are also bundled ! :)

Well, there is a problem with cpqarray driver. If I boot without noapic
it hangs right after

cpqarray: Device e11 has been found at 5 0
Compaq SMART2 Driver (v 2.4.2)
Found 1 controller(s)
cpqarray: Finding drives on ida0 (Smart Array 3200)
cpqarray ida/c0d0: blksz=512 nr_blks=17764320
cpqarray ida/c0d1: blksz=512 nr_blks=17764320
Partition check:
 ida/c0d0

but if I put noapic I get only _one_ CPU usable ->

]# cat /proc/interrupts 
   CPU0   CPU1   CPU2   CPU3   
  0: 926630  0  0  0  XT-PIC  timer
  1: 11  0  0  0  XT-PIC  keyboard
  2:  0  0  0  0  XT-PIC  cascade
  8:  1  0  0  0  XT-PIC  rtc
  9: 34  0  0  0  XT-PIC  sym53c8xx
 10: 30  0  0  0  XT-PIC  sym53c8xx
 11:   2522  0  0  0  XT-PIC  ida0
 14:  3  0  0  0  XT-PIC  ide0
 15:   7547  0  0  0  XT-PIC  eth1
NMI:  0  0  0  0 
LOC: 926548 926547 926546 926545 
ERR:  0


any patches to take/patch/slap !?

ps
any other required info available on request

-- 
Mario Mikočević (Mozgy)
My favourite FUBAR ...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2.4.3-pre8 problem with 8139too - failure to load

[Frank Jacobberger]

Something has changed regarding the 8139too driver in pre8.

I worked on it all morning long trying to resolve why the sucker
failed to load. There are new configuration options that need to
be addressed. As you recall there were zippo options in the pre7.

There are now:

RealTek RTL-8139 PCI Fast Ethernet Adapter support  [M]  
  Use PIO instead of MMIO   
  [*]
  Support for automatic channel equalization (EXPERIMENTAL)   [ ]
  Support for older RTL-8129/8130 boards[*]

Doing any combination of the above netted no positive result here.

I have run every kernel patch since 2.4.0 blah and
have never seen this driver fail to load or perform to some degree.

Trying to do insmod 8139too.o from the :
/lib/modules/2.4.3-pre8/kernel/drivers/net directory show these
unresolved symbols:

8139too.o: unresolved symbol alloc_etherdev
8139too.o: unresolved symbol unregister_netdev
8139too.o: unresolved symbol register_netdev

Maybe Jeff can shed more light on these changes

Thanks,

Frank

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: kernel 243p8 problems

[Jeff Garzik]

Mario Mikocevic wrote:
> 
> Hi,
> 
> 1st :
> 
> # depmod -a 2.4.3-pre8
> depmod: *** Unresolved symbols in /lib/modules/2.4.3-pre8/kernel/drivers/net/dummy.o
> depmod: *** Unresolved symbols in 
>/lib/modules/2.4.3-pre8/kernel/drivers/net/eepro100.o

What are the unresolved symbols?

-- 
Jeff Garzik   | May you have warm words on a cold evening,
Building 1024 | a full moon on a dark night,
MandrakeSoft  | and a smooth road all the way to your door.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] gcc-3.0 warnings

[Tim Wright]

On Fri, Mar 23, 2001 at 05:16:26PM -0800, Stephen Satchell wrote:
[...]
> Really?  I have a "cleanup" function that can be called during failure 
> cases (and success cases -- but you didn't mention that) so that the cost 
> is very low and I don't have to code ANY labels.
> 
> But then again, I'm a double-pipe abuser, in that I tend to code "atomic" 
> sequences as
> 
> if ((a) || (b) || (c) || (d) || (e) || (f) || (g) || ... ) { something 
> failed}  else {it all worked!}
> 
> and make sure that the failure value is non-zero for each a, b, c, d, and 
> so forth.
> 

Sorry, my example was too simplistic. Replace simple allocations with e.g.
allocate();
grab lock;
set flag;
allocate();

or something similar. Yes it's possible to code a state variable to remember
where you got to, or to e.g. add an extra boolean variable to indicate that
you grabbed the lock, but I'd argue that this obfuscates the code as well as
making it less efficient. It's no good looking to see if the lock has been
grabbed - if you failed at the first stage, it may still be locked by a
different CPU.

Tim

-- 
Tim Wright - [EMAIL PROTECTED] or [EMAIL PROTECTED] or [EMAIL PROTECTED]
IBM Linux Technology Center, Beaverton, Oregon
Interested in Linux scalability ? Look at http://lse.sourceforge.net/
"Nobody ever said I was charming, they said "Rimmer, you're a git!"" RD VI
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: Q: How do I get from the latest stable kernel version to the latest prepatch version ?

[Hen, Shmulik]

Thanks.
It just struck me odd that the latest is 2.4.2 while the prepatches were
2.4.3 so I figured there must be something I missed in between (my logic
told me that a 2.4.3 patch would be against a 2.4.3 something ;-).

BTW, I haven't seen any announcements from Linus in this mailing list
regarding new versions, just the updates on the web site and Alan's release
notes saying he's merging with 2.4.3xx. Are those announcements being posted
somewhere else now ?

-Original Message-
From: Leonid Mamtchenkov [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 26, 2001 2:33 PM
To: Hen, Shmulik
Cc: 'LKML'
Subject: Re: Q: How do I get from the latest stable kernel version to
the late st prepatch version ?


Hello Hen, Shmulik,

Once you wrote about "Q: How do I get from the latest stable kernel version
to the late st prepatch version ?":
HS> According to http://www.kernel.org, the latest stable kernel version is
HS> 2.4.2. The latest prepatch version is 2.4.3-pre3.
HS> 
HS> In order to get a full 2.4.3-pre8 kernel do I have to:
HS> 
HS> A. download linux-2.4.2.tar.gz and all the patch-2.4.3-preX.gz and apply
HS> them in succession or,
HS> B. download linux-2.4.3.tar.gz (exists ?) and then apply the all patches
or,
HS> C. download linux-2.4.3-pre7.tar.gz (exists ?) and apply only
HS> patch-2.4.3-pre8.gz ?

Download 2.4.2 and then apply 2.4.3-preX (latest) on it... that's it.
You might want to visit http://kernelnewbies.org .  They have some good docs
there.

-- 
 Best regards,
 Leonid Mamtchenkov
 System Administrator


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[PATCH] Fix net driver load problems

[Jeff Garzik]

Frank Jacobberger wrote:
> 
> Something has changed regarding the 8139too driver in pre8.
> 
> I worked on it all morning long trying to resolve why the sucker
> failed to load. There are new configuration options that need to
> be addressed. As you recall there were zippo options in the pre7.
> 
> There are now:
> 
> RealTek RTL-8139 PCI Fast Ethernet Adapter support  [M]
>   Use PIO instead of MMIO
>   [*]

Note by selecting this, you must made your driver slower.  Did you read
the help for the option?

>   Support for automatic channel equalization (EXPERIMENTAL)   [ ]
>   Support for older RTL-8129/8130 boards[*]

By selecting this you made your driver bigger, probably for no reason..

> Doing any combination of the above netted no positive result here.
> 
> I have run every kernel patch since 2.4.0 blah and
> have never seen this driver fail to load or perform to some degree.
> 
> Trying to do insmod 8139too.o from the :
> /lib/modules/2.4.3-pre8/kernel/drivers/net directory show these
> unresolved symbols:
> 
> 8139too.o: unresolved symbol alloc_etherdev
> 8139too.o: unresolved symbol unregister_netdev
> 8139too.o: unresolved symbol register_netdev
> 
> Maybe Jeff can shed more light on these changes

After staring hard at my source, I ran another diff and found that
net_init is not listed in export-objs.  Oh well, it's better to compile
stuff into your kernel anyway ;-) ;-)

Attached is a patch which fixes things.

Jeff


-- 
Jeff Garzik   | May you have warm words on a cold evening,
Building 1024 | a full moon on a dark night,
MandrakeSoft  | and a smooth road all the way to your door.

Index: drivers/net/Makefile
===
RCS file: /cvsroot/gkernel/linux_2_4/drivers/net/Makefile,v
retrieving revision 1.1.1.32
retrieving revision 1.1.1.32.2.1
diff -u -r1.1.1.32 -r1.1.1.32.2.1
--- drivers/net/Makefile2001/03/26 04:48:45 1.1.1.32
+++ drivers/net/Makefile2001/03/26 05:29:41 1.1.1.32.2.1
@@ -15,8 +15,9 @@
 # All of the (potential) objects that export symbols.
 # This list comes from 'grep -l EXPORT_SYMBOL *.[hc]'.
 
-export-objs := 8390.o arlan.o aironet4500_core.o aironet4500_card.o 
ppp_async.o \
-   ppp_generic.o slhc.o pppox.o auto_irq.o
+export-objs := 8390.o arlan.o aironet4500_core.o aironet4500_card.o \
+   ppp_async.o ppp_generic.o slhc.o pppox.o auto_irq.o \
+   net_init.o
 
 ifeq ($(CONFIG_TULIP),y)
   obj-y += tulip/tulip.o

Re: Q: How do I get from the latest stable kernel version to the latest prepatch version ?

[Jeff Garzik]

"Hen, Shmulik" wrote:
> 
> Hi,
> 
> According to http://www.kernel.org, the latest stable kernel version is
> 2.4.2. The latest prepatch version is 2.4.3-pre3.
> 
> In order to get a full 2.4.3-pre8 kernel do I have to:
> 
> A. download linux-2.4.2.tar.gz and all the patch-2.4.3-preX.gz and apply
> them in succession or,
> B. download linux-2.4.3.tar.gz (exists ?) and then apply the all patches or,
> C. download linux-2.4.3-pre7.tar.gz (exists ?) and apply only
> patch-2.4.3-pre8.gz ?

Apply only the latest patch, currently 2.4.3-pre8.

-- 
Jeff Garzik   | May you have warm words on a cold evening,
Building 1024 | a full moon on a dark night,
MandrakeSoft  | and a smooth road all the way to your door.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: CML1 cleanup patch

[Alan Cox]

> I hope you will reconsider after you've seen the reasons I posted in a later
> message, Alan.  You're one of the people I'm tring to save a lot of hassle
> for later on.  In fact, you are likely to be the largest beneficiary of
> this change.

Near term - no. I have much larger problems to worry about than config
destabilization

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Should mount --bind not follow symlinks?

[Anthony]

Jamie Lokier wrote:
> The automounter could indeed chase those symlinks.
> 
> Also, if the automounter creates a symlink in /opt anyway, and the link
> subsequently works (as you said), then it shouldn't be returning "No
> such file or directory" the first time.
> 
> In other words the latter behaviour looks like a bug in the automounter,
> and the former is a feature which could be added but isn't needed for
> your application.

Okay!  Well, the following I think fixes everything for me, as a 
small tweak to autofs-4.0.0pre9.

Thanks

Anthony


*** modules/mount_bind.c.Orig   Sun Mar 25 15:43:27 2001
--- modules/mount_bind.cMon Mar 26 22:57:10 2001
***
*** 19,24 
--- 19,25 
  #include 
  #include 
  #include 
+ #include 
  #include 
  #include 
  #include 
***
*** 71,76 
--- 72,84 
char *fullpath;
int err;
int i;
+ 
+   char real[PATH_MAX];
+   if (!realpath(what, real)) {
+ syslog(LOG_NOTICE, MODPREFIX "realpath %s failed: %m", what);
+ return 1;
+   }
+   what = real;
  
fullpath = alloca(strlen(root)+name_len+2);
if ( !fullpath ) {
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: CML1 cleanup patch, take 2

[Jeff Garzik]

esr wrote:
> OK, since peoples' territorial instincts have started to lather up,
> I guess I'm going to have to do this the hard way...

"Split up your patch" still apparently hasn't filtered into your head. 
Since that is more difficult than posting a single patch, I would say
you are doing it the slack way, and the way that makes it more difficult
for Linus and Alan to approve one part of your patch, and disapprove of
another part.


> This file is a patch expressed in two ways.  First, procedurally, as a
> way to duplicate its effects on any kernel source tree.  Secondly, as
> an explicit patch against 2.4.3-pre8.  It replaces my previous patch
> against 2.4.3-pre6.
> 
> This patch is the first result of a consistency audit of the configuration 
> system.  I have been building analysis tools to check the correctness of
> my CML2 rules file, and the processs of testing them turned up some problems.
> 
> The purpose of this patch is threefold:
> 
> (1) Clean up two errors in the CML1 corpus that could lead to subtle bugs.
> This is a BUG FIX in CML1.

separate patch?


> (2) Fix up 20 cris-architecture configuration symbols lacking a CONFIG_
> prefix, so they obey CML1/CML2 conventions and can be detected by
> `make dep', also static-analysis tools and consistency checkers.
> This is a BUG FIX in CML1.

separate patch?

What did the cris guys say, when you showed them this patch?

I agree this change is a bug fix, but get the cris' guys input first.

This should be in a separate patch, too.


> (3) Fix up 10 configuration symbols of the form CONFIG_[0-9]*; specific 
> changes are those suggested 8 Jan 2001 by PPC port maintainer Tom Rini.
> This change has been APPROVED by an authorized maintainer.

Maybe I am not caught up with the times...  I thought Cort Dougan was
the overall PowerPC maintainer.  That's what MAINTAINERS says.

Anyway, this is up to the PowerPC guys, but I disagree with this change
nonetheless.  MandrakeSoft has a PPC port, and as I mentioned earlier,
some utilities in the build process etc. look at CONFIG_xxx.

PPC guys:  this is a gratuitous renaming change that is not required. 
If you have been following the "CML1 cleanup patch" thread, you see that
Eric is blindly dictating policy when he says that CONFIG_[0-9] needs to
be cleaned up.


> This leaves ten symbols in a form that breaks CML2.  I'll go after
> the other individual maintainers about those.  Sigh
> 
> No actual object code will be changed by this patch; it merely does
> one-to-one substitutions on some configuration symbols.
> 
> Let me repeat that.  This patch changes *no* object code.  None.
> However, merging it before the 2.5 fork will save me (and probably
> Alan) some nasty large headaches later on...

Object code changes are not the only thing we are concerned with in a
stable series.
Let me repeat myself for the cheap seats:   Changing the 2.4.x
CONFIG_xxx namespace changes the source code API provided to other
kernel code.  It affects software not in the Linux kernel tree.

Your changes (1) and (2) sound ok.  Your change (3) is gratuitous, based
on policy change discussed with no one, and does not belong in stable
series 2.4.x.

Linus, Alan, Cort, please consider rejecting Eric's patch while it
contains (3).

Thanks,

Jeff


-- 
Jeff Garzik   | May you have warm words on a cold evening,
Building 1024 | a full moon on a dark night,
MandrakeSoft  | and a smooth road all the way to your door.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: ac25 - hang mounting swap

[Alan Cox]

> It just hangs when init scripts try to activate swap. I will look at
> what is init trying to mount and decode the info that Sysrq-P gives,
> but if this suggests somebody anything already known...

PAE or non PAE

> Sysrq-p gives different info as time goes, so perhaps it is not stuck
> but caught in an infinite loop trying to mount the only swap partition
> I have.

See what it is looping through if you can
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Use semaphore for producer/consumer case...

[Stelian Pop]

On Fri, Mar 23, 2001 at 07:34:07PM +0100, Manfred Spraul wrote:
> >  consumer()
> 
> > /* Let's wait for 10 items */
> > atomic_set(&sem->count, -10);
> 
> That doesn't work, at least the i386 semaphore implementation doesn't
> support semaphore counts < 0.

Does that mean that kernel semaphore can not be used for something
else than mutual exclusion ?

Stelian.
-- 
Stelian Pop <[EMAIL PROTECTED]>
|- Ingénieur Informatique Libre --|
| Alcôve - http://www.alcove.com - Tel: +33 1 49 22 68 00 |
|--- Alcôve, l'informatique est libre |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Use semaphore for producer/consumer case...

[Stelian Pop]

On Fri, Mar 23, 2001 at 03:52:54PM -0800, Nigel Gamble wrote:

> For the producer/consumer case, you want to initialize the semaphore to
> 0, not 1 which DECLARE_MUTEX(sem) does.  So I would use
> 
> __DECLARE_SEMAPHORE_GENERIC(sem, 0)

You're right that the DECLARE_MUTEX does not (entirely) do the job, 
but I set manually the value of sem->count:
> > atomic_set(&sem->count, -10);

> Then consumer could be:
>   /* Wait for 10 items to be produced */
>   for (i = 0; i < 10; i++)
>   down(&sem);

IMHO, this will not work, because the producer could be issuing
more than one 'up(&sem)' at the time...

Stelian.
-- 
Stelian Pop <[EMAIL PROTECTED]>
|- Ingénieur Informatique Libre --|
| Alcôve - http://www.alcove.com - Tel: +33 1 49 22 68 00 |
|--- Alcôve, l'informatique est libre |
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux Worm (fwd)

[Richard B. Johnson]

On Fri, 23 Mar 2001, Gerhard Mack wrote:

> On Fri, 23 Mar 2001, Bob Lorenzini wrote:
> 
> > I'm annoyed when persons post virus alerts to unrelated lists but this
> > is a serious threat. If your offended flame away.
> 
> This should be a wake up call... distributions need to stop using product
> with consistently bad security records. 
> 
>   Gerhard
> 

The immediate affect of specifically targeting Linux is to cause
"security administrators" to deny network access to all Linux
machines.

I have just received notice that my machines will no longer be
provided access to "The Internet".

"Effective on or before 16:00:00 local time, the only personal
computers that will be allowed Internet access are those administered
by a Microsoft Certified Network Administrator. This means that
no Unix or Linux machines will be provided access beyond the local
area network. If you require Internet access, the company will
provide a PC which runs a secure operating system such as Microsoft
Windows, or Windows/NT. Insecure operating systems like Linux must
be removed from company owned computers before the end of this week."


Cheers,
Dick Johnson

Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).

"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

'spurious APIC interrupt' - Dell PowerEdge 1400

[Stephen Frost]

Running into a problem with one of our Dell PowerEdge 1400 servers.
We see these messages very rarely, but after they show up the machine
goes into a really odd state:

Mar 26 09:37:27 maul kernel: spurious APIC interrupt on CPU#1, should never happen.
Mar 26 09:37:27 maul kernel: unexpected IRQ vector 216 on CPU#1!

Basically things seem to only kinda work.  My guess is that possibly one of
the CPUs has been shut down or similar and so half the processes are getting
kind of 'stuck'.

Any thoughts?  dmesg follows, more information availible upon request,
thanks!


Stephen

---
===# dmesg
Linux version 2.2.18-raid-mosix (bma@black) (gcc version 2.95.2 2220 (Debian 
GNU/Linux)) #2 SMP Tue Jan 2 12:40:13 EST 2001
Intel MultiProcessor Specification v1.4
Virtual Wire compatibility mode.
OEM ID: DELL Product ID: POWEREDGE CE APIC at: 0xFEE0
Processor #1 Pentium(tm) Pro APIC version 17
Processor #0 Pentium(tm) Pro APIC version 17
I/O APIC #2 Version 17 at 0xFEC0.
I/O APIC #3 Version 17 at 0xFEC01000.
Processors: 2
mapped APIC to e000 (fee0)
mapped IOAPIC to d000 (fec0)
mapped IOAPIC to c000 (fec01000)
Detected 794719 kHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 1585.97 BogoMIPS
Memory: 1034844k/1048512k available (1512k kernel code, 424k reserved, 11676k data, 
56k init)
Dentry hash table entries: 131072 (order 8, 1024k)
Buffer cache hash table entries: 524288 (order 9, 2048k)
Page cache hash table entries: 262144 (order 8, 1024k)
256K L2 cache (8 way)
CPU: L2 Cache: 256K
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.35a (19990819) Richard Gooch ([EMAIL PROTECTED])
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
256K L2 cache (8 way)
CPU: L2 Cache: 256K
per-CPU timeslice cutoff: 50.03 usecs.
CPU1: Intel Pentium III (Coppermine) stepping 06
calibrating APIC timer ... 
. CPU clock speed is 794.6271 MHz.
. system bus clock speed is 132.4377 MHz.
Booting processor 0 eip 2000
Calibrating delay loop... 1585.97 BogoMIPS
Intel machine check reporting enabled on CPU#0.
256K L2 cache (8 way)
CPU: L2 Cache: 256K
OK.
CPU0: Intel Pentium III (Coppermine) stepping 06
Total of 2 processors activated (3171.94 BogoMIPS).
enabling symmetric IO mode... ...done.
ENABLING IO-APIC IRQs
...changing IO-APIC physical APIC ID to 2
...changing IO-APIC physical APIC ID to 3
init IO_APIC IRQs
 IO-APIC (apicid-pin) 2-0, 2-2, 2-5, 2-11, 2-13WARNING: ASSIGN_IRQ_VECTOR wrapped back 
to 52
, 3-13 not connected.
...trying to set up timer as ExtINT... .. (found pin 0) ... works.
number of MP IRQ sources: 39.
number of IO-APIC #2 registers: 16.
number of IO-APIC #3 registers: 16.
testing the IO APIC...

IO APIC #2..
 register #00: 0200
...: physical APIC id: 02
 register #01: 000F0011
... : max redirection entries: 000F
... : IO APIC version: 0011
 register #02: 
... : arbitration: 00
 IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:   
 00 001 01  000   0   00751
 01 000 00  000   0   01159
 02 000 00  100   0   00000
 03 000 00  000   0   01161
 04 000 00  000   0   01169
 05 000 00  100   0   00000
 06 000 00  000   0   01171
 07 000 00  000   0   01179
 08 000 00  000   0   01181
 09 000 00  000   0   01189
 0a 0FF 0F  110   1   01191
 0b 000 00  100   0   00000
 0c 000 00  000   0   01199
 0d 000 00  100   0   00000
 0e 000 00  000   0   011A1
 0f 000 00  000   0   011A9

IO APIC #3..
 register #00: 0300
...: physical APIC id: 03
 register #01: 000F0011
... : max redirection entries: 000F
... : IO APIC version: 0011
 register #02: 0E00
... : arbitration: 0E
 IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:   
 00 0FF 0F  110   1   011B1
 01 0FF 0F  110   1   011B9
 02 0FF 0F  110   1   011C1
 03 0FF 0F  110   1   011C9
 04 0FF 0F  110   1   011D1
 05 0FF 0F  110   1   011D9
 06 0FF 0F  110   1   011E1
 07 0FF 0F  110   1   011E9
 08 0FF 0F  110   1   011F1
 09 0FF 0F  110   1   011F9
 0a 0FF 0F  110   1   01152
 0b 0FF 0F  110   1   0115A
 0c 0FF 0F  110   1   01162
 0d 000 00  100   0   0

Re: CML1 cleanup patch, take 2

[Tom Rini]

On Mon, Mar 26, 2001 at 09:50:53AM -0500, Jeff Garzik wrote:
> esr wrote:

> > (3) Fix up 10 configuration symbols of the form CONFIG_[0-9]*; specific 
> > changes are those suggested 8 Jan 2001 by PPC port maintainer Tom Rini.
> > This change has been APPROVED by an authorized maintainer.
> 
> Maybe I am not caught up with the times...  I thought Cort Dougan was
> the overall PowerPC maintainer.  That's what MAINTAINERS says.

Yes.  Cort is indeed the overall, head PPC guy.  Paul M does a lot too. :)
However, all of these name changes have gone past not only those two, but
a large portion of the PPC kernel community as well.  Everyone likes 'em,
or at least agrees they aren't bad changes.

> Anyway, this is up to the PowerPC guys, but I disagree with this change
> nonetheless.  MandrakeSoft has a PPC port, and as I mentioned earlier,
> some utilities in the build process etc. look at CONFIG_xxx.

Yes, they do.  Which is partily why I was actually going to wait until
2.5 for many of these to come in.

> PPC guys:  this is a gratuitous renaming change that is not required. 
> If you have been following the "CML1 cleanup patch" thread, you see that
> Eric is blindly dictating policy when he says that CONFIG_[0-9] needs to
> be cleaned up.

The counter point to this is what does "CONFIG_6xx" or 8xx mean?  It's as bad
as CONFIG_Mxxx imho :)

> > This leaves ten symbols in a form that breaks CML2.  I'll go after
> > the other individual maintainers about those.  Sigh
> > 
> > No actual object code will be changed by this patch; it merely does
> > one-to-one substitutions on some configuration symbols.
> > 
> > Let me repeat that.  This patch changes *no* object code.  None.
> > However, merging it before the 2.5 fork will save me (and probably
> > Alan) some nasty large headaches later on...
> 
> Object code changes are not the only thing we are concerned with in a
> stable series.
> Let me repeat myself for the cheap seats:   Changing the 2.4.x
> CONFIG_xxx namespace changes the source code API provided to other
> kernel code.  It affects software not in the Linux kernel tree.

Yes.  Symbol changes should be a 2.5 thing anyways.

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux Worm (fwd)

[Gregory Maxwell]

On Mon, Mar 26, 2001 at 10:07:22AM -0500, Richard B. Johnson wrote:
[snip]
> I have just received notice that my machines will no longer be
> provided access to "The Internet".
> 
> "Effective on or before 16:00:00 local time, the only personal
> computers that will be allowed Internet access are those administered
> by a Microsoft Certified Network Administrator. This means that
> no Unix or Linux machines will be provided access beyond the local
> area network. If you require Internet access, the company will
> provide a PC which runs a secure operating system such as Microsoft
> Windows, or Windows/NT. Insecure operating systems like Linux must
> be removed from company owned computers before the end of this week."

You've demonstrated over and over again that you work for a constantly
stupid company. 

Please find someplace else to work, your issues have become more depressing
then amusing. :)

It's sad that people like the one who sent out messages like that can stay
employed. In the last year there have been several Windows love-bug type
worms each causing damaged estimated in the billions. One or two Linux worms
that go after a long fixed problem with no published accounts of significant
damage and you get that sort of email..

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: CML1 cleanup patch

[Rik van Riel]

On Mon, 26 Mar 2001, Jeff Garzik wrote:

> Well, bummer.  I can't seem to find Eric's message archived anywhere.
> 
> FWIW I am opposed to any large-scale cleanup of the configuration
> language and/or identifiers in -any- 2.4.x series kernel.

Seconded, this is a 2.5 issue...  (IMHO, at least)

Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...

http://www.surriel.com/
http://www.conectiva.com/   http://distro.conectiva.com.br/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

/proc/sys/vm/freepages read-only?!?

[David L. Parsley]

Hi,

I'm trying to do some vm tuning for diskless (and therefore swapless)
devices.  (I'm working on a distro that tftp's packages and runs
entirely in RAM)

Even on an X terminal with 64MB RAM, badly behaved apps can use lots of
ram in the Xserver, and what I'm seeing is a hang.  The box is usually
still pingable, just unresponsive.  I'm using cramfs pretty heavily, and
I think what's occuring is that the terminal gets too low on freepages,
and since pages used by X can't be swapped out, the box starts thrashing
the vm and is unable to get pages to uncompress into.

My first thought was echo (bigger numbers) > /proc/sys/vm/freepages -
but lo! - it's not writable anymore.  I found comments in page_alloc.c
indicating it had to be read-only, but it seems it's only a safety
precaution.  Something along the lines of values too small being 'bad
bad'.


help?
David
-- 
David L. Parsley
Network Administrator
Roanoke College
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] Prevent OOM from killing init

[Rik van Riel]

On Mon, 26 Mar 2001, Jonathan Morton wrote:

> I have, however, found a bug in the non-overcommit patch - it seems to
> be capable of double-freeing (and then some) - starting 4 Java VMs and
> then closing them causes VMReserved to go negative on my system.

*grin*

It's nice to see the non-overcommit code being tested and
fixed like this. If there turns out to be a demand for this
patch, I guess we'll even want to integrate this into the
kernel ... possibly even the 2.4 kernel, if the code changes
are small/managable enough.

regards,

Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...

http://www.surriel.com/
http://www.conectiva.com/   http://distro.conectiva.com.br/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [kbuild-devel] Re: CML1 cleanup patch

[Rik van Riel]

On Mon, 26 Mar 2001, John Cowan wrote:

> esr scripsit:
> 
> > it needs is more overhead, and (2) interpreting symbols with leading digits
> > as nonnumeric tokens is just *wrong*.  Ugh.  Violates the Principle of Least
> > Surprise big-time.
> 
> In fact this has come up before: in Usenet software, which has to
> differentiate between an article and a sub-newsgroup.  An article has
> to have an all-numeric name, and It Would Have Been Nice if all
> newsgroup names began with non-digits, but then there was
> comp.bugs.4bsd.

What's wrong with using the _file type_ for these things ?

Conversely, why can't CML2 use the CONFIG_ prefix to
determine if a symbol is a configuration option, like
we're doing now?

Please do point out if I'm missing something, but I
really fail to see what the fuss is about.

regards,

Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...

http://www.surriel.com/
http://www.conectiva.com/   http://distro.conectiva.com.br/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

ext2 corruption in 2.4.2, scsi only system

[Dale E Martin]

Hello.  I've got a dual PPro machine running 2.4.2, and Debian (stable + a
little bit of "testing".)  This machine is heavily loaded about 3/4 of the
time, doing a daily regression test on a project we're working on.
Bascially, the machine runs g++ about 18 hours a day on machine generated
code.

With 2.2.17 the machine would have process hangs after a couple of days -
this was repeatable.  (specifically g++ would start hanging, even compiling
"hello world".) 

I had had good luck with 2.4.x on other boxes, so I put it on this machine
as well.  Several times now I've seen ext2 corruption with no other
noteworthy logs.  


The last time we saw this after no other kernel messages:
Mar 23 18:40:02 woodlawn kernel: EXT2-fs error (device sd(8,6)):
ext2_free_blocks: Freeing blocks in system zones - Block = 62, count = 1
Mar 23 19:18:33 woodlawn kernel: EXT2-fs error (device sd(8,6)):
ext2_new_block: Allocating block in system zone - block = 62
Mar 24 18:40:04 woodlawn kernel: EXT2-fs error (device sd(8,6)):
ext2_free_blocks: Freeing blocks in system zones - Block = 62, count = 1
Mar 24 19:07:22 woodlawn kernel: EXT2-fs error (device sd(8,6)):
ext2_new_block: Allocating block in system zone - block = 62
Mar 25 16:45:01 woodlawn kernel: EXT2-fs error (device sd(8,1)):
ext2_free_blocks: bit already cleared for block 460146
Mar 25 16:45:01 woodlawn kernel: Remounting filesystem read-only
Mar 25 18:40:03 woodlawn kernel: EXT2-fs error (device sd(8,6)):
ext2_free_blocks: Freeing blocks in system zones - Block = 62, count = 1

On the boot prior, we saw this:
Mar  8 11:34:08 woodlawn kernel: EXT2-fs error (device sd(8,6)):ext2_free_blocks: 
Freeing blocks in system zones - Block = 720946, count = 1
Mar  8 13:10:53 woodlawn kernel: EXT2-fs error (device sd(8,6)):ext2_new_block:
 Allocating block in system zone - block = 720946
Mar  8 13:13:49 woodlawn kernel: EXT2-fs error (device sd(8,6)): ext2_free_block
s: Freeing blocks in system zones - Block = 720946, count = 1
Mar  8 15:32:52 woodlawn kernel: EXT2-fs error (device sd(8,6)): ext2_new_block:
 Allocating block in system zone - block = 720946
Mar  8 15:35:20 woodlawn kernel: EXT2-fs error (device sd(8,6)): ext2_free_block
s: Freeing blocks in system zones - Block = 720946, count = 1
Mar  9 06:26:07 woodlawn kernel: init_special_inode: bogus imode (52171)
Mar  9 06:26:07 woodlawn kernel: init_special_inode: bogus imode (30564)
Mar  9 06:26:07 woodlawn kernel: init_special_inode: bogus imode (51522)
Mar  9 06:26:07 woodlawn kernel: init_special_inode: bogus imode (71400)
Mar  9 06:26:07 woodlawn kernel: init_special_inode: bogus imode (70072)
Mar  9 06:26:07 woodlawn kernel: init_special_inode: bogus imode (72163)
Mar  9 06:26:07 woodlawn kernel: init_special_inode: bogus imode (57522)
Mar  9 06:26:07 woodlawn kernel: init_special_inode: bogus imode (30062)
Mar  9 06:26:07 woodlawn kernel: init_special_inode: bogus imode (31137)
Mar  9 06:26:07 woodlawn kernel: init_special_inode: bogus imode (30532)
Mar  9 06:26:07 woodlawn kernel: init_special_inode: bogus imode (0)
Mar  9 06:26:07 woodlawn kernel: init_special_inode: bogus imode (0)
Mar  9 06:26:07 woodlawn kernel: init_special_inode: bogus imode (71563)

At that point, there were some large and not easily removed files that
appeared on the filesystem in question.

The machine is a dual PPro, it has a Buslogic BT958 with a single 9G
scsi/wide drive in it.  There aren't any logs related to physical disk
problems.  If the machine starts doing this again, I'll take a look in
/proc/scsi/Buslogic and see if it's showing any errors in there.

Thanks for any help, and please let me know if I need to supply any other
info.  I guess the only other thing I can think of is the kernel is
compiled with gcc 2.95.2, which I realize is considered "slightly risky" or
so

Thanks,
Dale
-- 
Dale E. Martin, Clifton Labs, Inc.
Senior Computer Engineer
[EMAIL PROTECTED]
http://www.cliftonlabs.com
pgp key available
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux Worm (fwd)

[David Weinehall]

On Mon, Mar 26, 2001 at 10:07:22AM -0500, Richard B. Johnson wrote:
> On Fri, 23 Mar 2001, Gerhard Mack wrote:
> 
> > On Fri, 23 Mar 2001, Bob Lorenzini wrote:
> > 
> > > I'm annoyed when persons post virus alerts to unrelated lists but this
> > > is a serious threat. If your offended flame away.
> > 
> > This should be a wake up call... distributions need to stop using product
> > with consistently bad security records. 
> > 
> > Gerhard
> > 
> 
> The immediate affect of specifically targeting Linux is to cause
> "security administrators" to deny network access to all Linux
> machines.
> 
> I have just received notice that my machines will no longer be
> provided access to "The Internet".
> 
> "Effective on or before 16:00:00 local time, the only personal
> computers that will be allowed Internet access are those administered
> by a Microsoft Certified Network Administrator. This means that
> no Unix or Linux machines will be provided access beyond the local
> area network. If you require Internet access, the company will
> provide a PC which runs a secure operating system such as Microsoft
> Windows, or Windows/NT. Insecure operating systems like Linux must
> be removed from company owned computers before the end of this week."

O. I especially like the "secure operating systems such as Microsoft
Windows" part. I'm impressed with their clear perception.


/David
  _ _
 // David Weinehall <[EMAIL PROTECTED]> /> Northern lights wander  \\
//  Project MCA Linux hacker//  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Compiling problem kernel 2.4.2

[Theodoor Scholte]

Hello,

I have a problem with compiling kernel-2.4.2. When I want to make a bzImage 
on a RedHat Linux 5.2 box,
then I get this error-message:

gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -02
-fomit-frame-pointer -fno-strict-aliasing -pipe -march=i486  -c -o init/main.o
init/main.c
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -02
fomit-frame-pointer -fno-strict-aliasing -pipe  -march=i486
-DUTS_MACHINE='"i386"' -c -o init/version.o init/version.c
cpp: /usr/src/linux/include/linux/compile.h: Input/output error
init/version.c:20: `UTS_VERSION' undeclared here (not in a function)
init/version.c:20: initializer element for `system_utsname.version' is not
constant
init/version.c:25: parse error before `LINUX_COMPILE_BY'
make: *** [init/version.o] Error 1

I have installed these software revisions:
GNU C  egcs-2.91.66
GNU make  3.78.1
binutils  2.9.5.0.22-6
util-linux  2.10f
modutils  2.4.2
e2fsprogs  1.19

What is the solution for this problem? On a Slackware 7.1-box with the same 
software-revisions I have no problems with compiling kernel 2.4.2.

Thanks in advance,

Theodoor Scholte

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux Worm (fwd)

[Bob_Tracy]

Gregory Maxwell wrote:
> On Mon, Mar 26, 2001 at 10:07:22AM -0500, Richard B. Johnson wrote:
> [snip]
> > I have just received notice that my machines will no longer be
> > provided access to "The Internet".
> 
> It's sad that people like the one who sent out messages like that can stay
> employed.

So let's quit covering for 'em.  Let's have the name(s) behind that
idiotic policy letter, because I would not knowingly allow any company
I work for to hire such people.

ProblemRemedy
-----
hangnail   amputate
headache   amputate
(etc.)

Sheesh...

--Bob Tracy
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Compiling problem kernel 2.4.2

[Tobias Ringstrom]

On Mon, 26 Mar 2001, Theodoor Scholte wrote:

> Hello,
>
> I have a problem with compiling kernel-2.4.2. When I want to make a bzImage
> on a RedHat Linux 5.2 box,
> then I get this error-message:

> [...]

> cpp: /usr/src/linux/include/linux/compile.h: Input/output error

Disk full?  Bad disk?

/Tobias

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

offtopic Re: Linux Worm (fwd)

[John Jasen]

On Mon, 26 Mar 2001, Bob_Tracy wrote:

> So let's quit covering for 'em.  Let's have the name(s) behind that
> idiotic policy letter, because I would not knowingly allow any company
> I work for to hire such people.

In this case, the person(s) making the policy seem to be short on clue,
and long on agenda.

However, I can understand and agree with, from a security perspective, a
company deciding to ditch OSes that they have little to no idea about how
to handle.

I've been in the position to suggest that very action to companies, as
their $VENDOR-OS box sits in the corner and decays quietly, because
everyone either ignores it while its working, or kicks it into
'submission' when something goes wrong ...

Yeah, the _solution_ is to have IT people with lots of clue, but, well ...
*cough* ...

--
-- John E. Jasen ([EMAIL PROTECTED])
-- In theory, theory and practise are the same. In practise, they aren't.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] [RESEND] update chipsfb driver

[James Simmons]

I have seen a more complete driver but I haven't tested it since I don't
have this video card. It is at http://www.visuelle-maschinen.de/ctfb/

MS: (n) 1. A debilitating and surprisingly widespread affliction that
renders the sufferer barely able to perform the simplest task. 2. A disease.

James Simmons  [[EMAIL PROTECTED]]   /|
fbdev/console/gfx developer \ o.O|
http://www.linux-fbdev.org   =(_)=
http://linuxgfx.sourceforge.netU
http://linuxconsole.sourceforge.net

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: BUG in reiserfs with 2.4.2-ac20 + linux-aic7xxx Rev 6.1.7

[Chris Mason]

> 
> Mar 25 06:56:50 gip2 kernel: journal_begin called without kernel lock held
> Mar 25 06:56:50 gip2 kernel: kernel BUG at journal.c:423!
> 
Ok, this BUG is there to catch people trying to use the reiserfs journal
without the BKL held.  Older ac series kernel had a bug where vmtruncate
would trigger this when called from generic_file_write (which your stack
trace shows you hit).

But, ac20 should have the fix.  Looks like only the expanding truncate case
ended up under the BKL in vmtruncate.  This untested diff is stolen from the
expanding truncate fix in ac25:

--- linux/mm/memory.c.1 Mon Mar 26 11:05:25 2001
+++ linux/mm/memory.c   Mon Mar 26 11:06:31 2001
@@ -969,7 +969,12 @@
spin_unlock(&mapping->i_shared_lock);
truncate_inode_pages(mapping, offset);
if (inode->i_op && inode->i_op->truncate)
+   {
+   /* This doesnt scale but it is meant to be a 2.4 invariant */
+   lock_kernel();
inode->i_op->truncate(inode);
+   unlock_kernel();
+   }
return 0;
 
 do_expand:

-chris

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

64-bit block sizes on 32-bit systems

[LA Walsh]

I vaguely remember a discussion about this a few months back.
If I remember, the reasoning was it would unnecessarily slow
down smaller systems that would never have block devices in
the 4-28T range attached.  

However, isn't it possible there will continue to be a series
of P-IV,V,VI,VII ...etc, addons that will be used for sometime
to come.  I've even heard it suggested that we might see
2 or more CPU's on a single chip as a way to increase cpu
capacity w/o driving up clock speed.  Given the cheapness of
.25T drives now, seeing the possibility of 4T drives doesn't seem
that remote (maybe 5 years?).  

Side question: does the 32-bit block size limit also apply to 
RAID disks or does it use a different block-nr type?

So...is it the plan, or has it been though about -- 'abstracting'
block numbes as a typedef 'block_nr', then at compile time
having it be selectable as to whether or not this was to
be a 32-bit or 64 bit quantity -- that way older systems would
lose no efficiency.  Drivers that couldn't be or hadn't been
ported to use 'block_nr' could default to being disabled if
64-bit blocks were selected, etc.

So has this idea been tossed about and or previously thrashed?

-l

-- 
L A Walsh| Trust Technology, Core Linux, SGI
[EMAIL PROTECTED]  | Voice: (650) 933-5338
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] OOM handling

[Michael Peddemors]

Uh... and aside from init, mission critical stuff... crond should never
get killed, it runs mission critical cleanup tasks..
If crond dies, might as well make the machine die in a lot of cases.. I
hate to miss my nightly database exports...

Getting to look more and more like we need some way to configure certain
tasks at the admin level to never die..


-- 
"Catch the Magic of Linux..."

Michael Peddemors - Senior Consultant
LinuxAdministration - Internet Services
NetworkServices - Programming - Security
WizardInternet Services http://www.wizard.ca
Linux Support Specialist - http://www.linuxmagic.com

(604)589-0037 Beautiful British Columbia, Canada

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Compiling problem kernel 2.4.2

[Theodoor Scholte]

> > Hello,
> >
> > I have a problem with compiling kernel-2.4.2. When I want to make a bzImage
> > on a RedHat Linux 5.2 box,
> > then I get this error-message:
>
> > [...]
>
> >> cpp: /usr/src/linux/include/linux/compile.h: Input/output error
>
>Disk full?  Bad disk?

No, that is not the problem. The disk is is in a very good health and the 
disk is certainly not full. I compile the kernel over an nfs-mapping. The 
mapping is good.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: via-rhine driver: wicked 2005 problem

[wing tung Leung]

On Mon, Mar 26, 2001 at 09:08:46AM +0200, Manfred Spraul wrote:
> > [Kernel 2.4.2,
> 
> the -ac kernels contain a patch that automatically resets the nic if it
> dies. I've attached my old patch, it applies to 2.4.2.
 
Your patch works fine for resetting the NIC. There are some a one or two
log messages coming up, but the transfer continues after a small delay.

It doesn't solve the (less urgent) problem of not being able the use the
NIC after a warm boot in M$ Windows. As I said, pulling the power cord from
the ATX power supply and reinserting it, makes it go away.

> > I tried the diagnostic utilities from Donald Becker at Scyld.com,
> > but I don't  know what I should be looking for. The text output
> > seems ok to me. 
> >
> Could you post the output?
> And a few more lines from your kernel log.

It's rather much to post the the mailing list, I think, so I've put it online
at [http://win-www.uia.ac.be/u/s965817/via-rhine.report/]. If you prefer
otherwise, just tell me. I can always send a tarball of the logs.

Some explanation of the logs:

report: script for creating the device status dumps
hang/:  about the "timed out" problem receiving much data
242/:  using the default module from 2.4.2 release
 before/:   device status before the lock, while NIC works well
 after/:device status after the lock, during timeout messages
242patch/: using the patched version
 before/:   device status before the timeout or wicked messages
 after/:device status afterwards (NIC keeps working fine)
windoze:/   about the warm-boot-after-windoze problem
winboot/:  device info booting after warm boot (problem case)
coldboot/: device info booting after total cold boot (no problem)


Thanks a lot for the patch.

Tung

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.2ac25

[Ivan Kokshaysky]

On Mon, Mar 26, 2001 at 07:34:26AM +0100, Alan Cox wrote:
> Alpha has probably been broken by the pre8 merge.

Yep, but not too much. This "unbreaks" it.

Ivan.

--- 2.4.2-ac25/include/asm-alpha/pgalloc.h  Mon Mar 26 17:59:22 2001
+++ linux/include/asm-alpha/pgalloc.h   Mon Mar 26 19:58:19 2001
@@ -303,7 +303,7 @@ static inline void pmd_free_slow(pmd_t *
free_page((unsigned long)pmd);
 }
 
-static inline pte_t *pte_alloc_one(void)
+static inline pte_t *pte_alloc_one(unsigned long address)
 {
pte_t *pte = (pte_t *)__get_free_page(GFP_KERNEL);
if (pte)
@@ -311,7 +311,7 @@ static inline pte_t *pte_alloc_one(void)
return pte;
 }
 
-static inline pte_t *pte_alloc_one_fast(void)
+static inline pte_t *pte_alloc_one_fast(unsigned long address)
 {
unsigned long *ret;
 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: via-rhine driver: wicked 2005 problem

[Jeff Garzik]

wing tung Leung wrote:
> It doesn't solve the (less urgent) problem of not being able the use the
> NIC after a warm boot in M$ Windows. As I said, pulling the power cord from
> the ATX power supply and reinserting it, makes it go away.

Would it be possible for you to re-run your tests against kernel
2.4.3-pre8?  (ftp://ftp.us.kernel.org/pub/linux/kernel/testing/)

This is the "official" latest version of the via-rhine driver, and it
includes Manfred's patch, as well as a pci_enable_device movement might
solve your problem.

If the problem is still not solved, could you download via-diag.c and
libmii.c from ftp://www.scyld.com/pub/diag/   Compile instructions are
at the bottom of via-diag.c.  I'm interested in seeing two via-diag
register snapshots, one from a cold boot (where it is working), and one
from a warm boot.

  ./via-diag -maaavvveef > via-diag-cold.txt
and
  ./via-diag -maaavvveef > via-diag-warm.txt
then
   diff -u v*cold.txt v*warm.txt | send mail...

And to see if the PCI configuration registers change between warm boot
and cold boot, run lspci from pciutils:

  lspci -vvvxxx > lspci-cold.txt
and
  lspci -vvvxxx > lspci-warm.txt
then
  diff -u l*cold.txt l*warm.txt | send mail...

-- 
Jeff Garzik   | May you have warm words on a cold evening,
Building 1024 | a full moon on a dark night,
MandrakeSoft  | and a smooth road all the way to your door.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux Worm (fwd)

[Henning P. Schmiedehausen]

[EMAIL PROTECTED] (Richard B. Johnson) writes:

>I have just received notice that my machines will no longer be
>provided access to "The Internet".

>"Effective on or before 16:00:00 local time, the only personal
>computers that will be allowed Internet access are those administered
>by a Microsoft Certified Network Administrator. This means that
>no Unix or Linux machines will be provided access beyond the local
>area network. If you require Internet access, the company will
>provide a PC which runs a secure operating system such as Microsoft
>Windows, or Windows/NT. Insecure operating systems like Linux must
>be removed from company owned computers before the end of this week."

This is a troll, right? I mean, you wouldn't work for a company that
publishes such internal memos (and allows its employees to post in
into a public mailing list), would you?

If you're working for a company that considers one OS "more secure"
than another, your "security administrator" should really get a clue.

I mean, they all suck. Really, all of them. That's why they're OSes. ;-)

Regards
Henning

-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen   -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED]

Am Schwabachgrund 22  Fon.: 09131 / 50654-0   [EMAIL PROTECTED]
D-91054 Buckenhof Fax.: 09131 / 50654-20   
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.2.19 aic7xxx breaks pcmcia

[David Hinds]

On Mon, Mar 26, 2001 at 05:14:13PM +1000, Keith Owens wrote:
> 2.2.19 Documentation/Changes says pcmcia-cs 3.0.14.  I am using 3.1.21
> and it breaks if you compile the kernel with scsi support then try to
> compile pcmcia.  clients/apa1480_stub.c in 3.1.21 has
>   #include <../drivers/scsi/aic7xxx.h>
> but in 2.2.19 that file is drivers/scsi/aic7xxx/aic7xxx.h.  You need at
> least pcmcia-cs 3.1.25 for kernel 2.2.19 with scsi support.

Correct.  It is not just the header file that is at issue, though; the
whole build procedure for the aic7xxx driver changed.

> In the kernel and associated utilities I want to remove lines like
>   #include <../drivers/scsi/aic7xxx.h>
> and replace them with
>   #include "aic7xxx.h"
> with the Makefile specifying -I $(TOPDIR)/drivers/scsi (2.2.18) or -I
> $(TOPDIR)/drivers/scsi/aic7xxx (2.2.19).  Hard coding long path names
> for #include is bad, especially when they contain '..'.  It stops
> kernel developers moving code around and makes it difficult to do some
> of the things I plan for the 2.5 Makefile rewrite.  David, how easy
> would it be to change pcmcia to this style of include?

It would not be too hard to do what you suggest, but would make for
very long CPPFLAGS.  Which is inconvenient if you like to actually see
what's going on when you do a build.  I think more of the include
files at issue should probably be in the kernel include tree, and not
hidden in the driver tree.  That would make the issue moot.

What are the things you're planning that will cause trouble?  I would
also think it would be less of an issue with 2.5 if there is some hope
that in-kernel PCMCIA is going to be the standard.

-- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux Worm (fwd)

[Bob Lorenzini]

On Mon, 26 Mar 2001, Richard B. Johnson wrote:

> 
> "Effective on or before 16:00:00 local time, the only personal
> computers that will be allowed Internet access are those administered
> by a Microsoft Certified Network Administrator. This means that
> no Unix or Linux machines will be provided access beyond the local
> area network. If you require Internet access, the company will
> provide a PC which runs a secure operating system such as Microsoft
> Windows, or Windows/NT. Insecure operating systems like Linux must
> be removed from company owned computers before the end of this week."

You might point out that only linux machines running a older version of
bind are at risk. Over one million credit card numbers were stolen from
microsoft servers in the last year. I suspect none of your linux machines
are even running bind. 

Bob

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

RE: Q: How do I get from the latest stable kernel version to the latest prepatch version ?

[J . A . Magallon]

On 03.26 "Hen, Shmulik" wrote:
> Thanks.
> It just struck me odd that the latest is 2.4.2 while the prepatches were
> 2.4.3 so I figured there must be something I missed in between (my logic
> told me that a 2.4.3 patch would be against a 2.4.3 something ;-).
> 

It all depends on the name of the patch. Usually, the '-preXX' patches
are 'previews' of the thing, so a 2.4.3-pre8 is 'preview 8 of what could
be 2.4.3', so as 2.4.3 still does not exist, the patch applies on 2.4.2.

On the other way, the Alan Cox series  is named 2.4.2-acXX, because they
add features to test to 2.4.2 that anybody knows if will end on an 'official'
kernel. Perhaps if a bugfix-feature that appears in 2.4.2-acX is ok, it
can end up in the official preview 2.4.3-preY for the next kernel.
 
-- 
J.A. Magallon  #  Let the source
mailto:[EMAIL PROTECTED]  #  be with you, Luke... 

Linux werewolf 2.4.2-ac24 #1 SMP Sat Mar 24 12:40:29 CET 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [PATCH] static zero initializers removal

[Jeff Garzik]

I'll take a look at merging the drivers/net part of this patch, except
for where it touches drivers/net/wan.

Andrey -- for maintainers at least, it might be nice to split these up
via subsystem -- one patch for drivers/isdn, one patch for drivers/char,
etc.

-- 
Jeff Garzik   | May you have warm words on a cold evening,
Building 1024 | a full moon on a dark night,
MandrakeSoft  | and a smooth road all the way to your door.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Use semaphore for producer/consumer case...

[Manfred Spraul]

From: "Stelian Pop" <[EMAIL PROTECTED]>
> >
> > That doesn't work, at least the i386 semaphore implementation
doesn't
> > support semaphore counts < 0.
>
> Does that mean that kernel semaphore can not be used for something
> else than mutual exclusion ?
>
It's a bit better: counts >= 0 are supported, i.e. you can call up()
before down(), and that's used in several places.

The for loop that Nigel proposed should solve your problem. Multiple
up's are handled correctly.

--
Manfred

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Lovely crash with 2.4.2-ac24.

[Zephaniah E\. Hull]

This had hit me a few times with ac18 (I'm not sure it was the same
crash though) and just hit me again with ac24.

Alan cced due to it being in the ac kernels, Andre because the trace
seems to point to the IDE code.

Thanks.

Zephaniah E. Hull.

-- 
 PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801
Keys available at http://whitestar.soark.net/~warp/public_keys.
   CCs of replies from mailing lists are encouraged.

 Mercury: gpm isn't a very good web browser.  fix it.


ksymoops 2.3.7 on i586 2.4.2-ac24.  Options used
 -V (default)
 -k /proc/ksyms (default)
 -l /proc/modules (default)
 -o /lib/modules/2.4.2-ac24-c2/ (specified)
 -m /boot/2.4.2-ac24-c2/System.map (specified)

kernel BUG at printk.c:461!
invalid operand: 
CPU:0
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010282
eax: 001c   ebx: c1224120 ecx: c025373c   edx: 0282
esi: c1291000   edi: c129116e ebp:    esp: c026be60
ds: 0018   es: 0018   ss: 0018
Process swapper (pid: 0, stackpage=c026b000)
Stack:  00204e00 01cd c017d8a0 c129107f c0171b9f c1291000 c1291568 c1291168
 c026bfa4  7f2ce700 c018bc35  0018b5a8 c129156d
c129116e 01f6 c02ce700  c02ce700 c119afc8 0008 004c4000
Call Trace: [] [] [] [] []
[] [] [] [] [] []
[] [] [] [] [] []
[] [] [] []
Code: 0f 0b 83 c4 08 b9 3c 37 25 c0 ff 0d 3c 37 25 c0 0f 88 68 64

>>EIP; c0114fee<=
Trace; c017d8a0 
Trace; c0171b9f 
Trace; c018bc35 
Trace; c018d0bc 
Trace; c019038d 
Trace; c0188009 
Trace; c0188062 
Trace; c016ff35 
Trace; c01197e4 
Trace; c011ab26 
Trace; c011870f 
Trace; c0118647 
Trace; c0118550 
Trace; c010a152 
Trace; c0107120 
Trace; c0108df0 
Trace; c0107120 
Trace; c0107143 
Trace; c01071a7 
Trace; c0106000 
Trace; c0100191 
Code;  c0114fee 
 <_EIP>:
Code;  c0114fee<=
   0:   0f 0b ud2a  <=
Code;  c0114ff0 
   2:   83 c4 08  add$0x8,%esp
Code;  c0114ff3 
   5:   b9 3c 37 25 c0mov$0xc025373c,%ecx
Code;  c0114ff8 
   a:   ff 0d 3c 37 25 c0 decl   0xc025373c
Code;  c0114ffe 
  10:   0f 88 68 64 00 00 js 647e <_EIP+0x647e> c011b46c 


 <0>Kernel panic: Aiee, killing interrupt handler!

 PGP signature

Re: ac25 - hang mounting swap

[J . A . Magallon]

On 03.26 Alan Cox wrote:
> 
> See what it is looping through if you can
>

Well, my mail took a hundred years to get to the list, and in the meanwhile
I read the posts on the bugs in vmalloc.c. That solved my boot, now I'm
running ac25.

-- 
J.A. Magallon  #  Let the source
mailto:[EMAIL PROTECTED]  #  be with you, Luke... 

Linux werewolf 2.4.2-ac25 #5 SMP Mon Mar 26 17:46:56 CEST 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

paride error, aparantly with VFS

[idalton]

I appear to have found a problem reading from paride hard disks under
2.4.2

Reading from the raw block devices seems to be fine.

# dd if=/dev/pd/disc0/disc of=/dev/null
works.

However, accessing partitions on the device through VFS by mounting them
hangs the machine.

With vfat and msdos partitions: 
# mount -t (vfat|msdos) /dev/pd/disc0/part1 /mnt
and then
# cat /mnt/* > /dev/null
or
# dd if=/mnt/drvspace.000 of=/dev/null

I eventually see the following error message, and all logins are
unresponsive. I can reboot with SysRq.

do_pd_read_drq: status = 0x10050 = SEEK READY TMO

Doing a similar test with an ext2 fs on the drive:

do_pd_read_drq: status = 0x10052 = SEEK READY TMO

Changing parallel port mode in the BIOS does not make any difference.

The paride controller is a Shuttle EPAT plus. The parallel port is an
Intel 82371AB (I think)

-- Ferret
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Adaptec Array1000

[Roberto Fichera]

Hi all,

Does anyone know how to configure this controller (chipset AAA-133U2 aka 
AIC-78xx)
with one RAID5 hardware volume ? The kernel 2.2.16 see all the disks 
(4x18Gb) but
don't see the unique volume.

Thanks in advance.

Roberto Fichera.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

bug report: paride with devfs

[idalton]

I found this one out while trying to back up an old win95 system ;)



[1.] One line summary of the problem:

paride and/or devfs bork up and OOPS

[2.] Full description of the problem/report:

When releasing and re-loading the 'pd' module, swapping drives on the
parport box hardware, the devfs entry under /dev/pd/ doesn't get
updated, OOPS happens when creating or removing nodes by hand.

[3.] Keywords (i.e., modules, networking, kernel):

parport paride devfs modules

[4.] Kernel version (from /proc/version):

Linux version 2.4.2cc (root@bicycle) (gcc version 2.95.3 20010125 (prerelease)) #1 Thu 
Mar 15 13:10:32 PST 2001

[5.] Output of Oops.. message (if applicable) with symbolic information
 resolved (see Documentation/oops-tracing.txt)

ksymoops 2.3.7 on i586 2.4.2cc.  Options used
 -V (default)
 -k /proc/ksyms (default)
 -l /proc/modules (default)
 -o /lib/modules/2.4.2cc/ (default)
 -m /boot/System.map-2.4.2cc (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

Warning (compare_maps): ksyms_base symbol __VERSIONED_SYMBOL(cuecat_process_scancode) 
not found in System.map.  Ignoring ksyms_base entry
Warning (compare_maps): snd symbol pm_register not found in 
/usr/lib/alsa-modules/2.4.2cc/0.5/snd.o.  Ignoring 
/usr/lib/alsa-modules/2.4.2cc/0.5/snd.o entry
Warning (compare_maps): snd symbol pm_send not found in 
/usr/lib/alsa-modules/2.4.2cc/0.5/snd.o.  Ignoring 
/usr/lib/alsa-modules/2.4.2cc/0.5/snd.o entry
Warning (compare_maps): snd symbol pm_unregister not found in 
/usr/lib/alsa-modules/2.4.2cc/0.5/snd.o.  Ignoring 
/usr/lib/alsa-modules/2.4.2cc/0.5/snd.o entry

Mar 25 18:42:02 bicycle kernel: paride: version 1.05 installed
Mar 25 18:42:02 bicycle kernel: paride: epat registered as protocol 0
Mar 25 18:42:05 bicycle kernel: pd: pd version 1.05, major 45, cluster 64, nice 0
Mar 25 18:42:05 bicycle kernel: pda: Sharing parport0 at 0x378
Mar 25 18:42:05 bicycle kernel: pda: epat 1.01, Shuttle EPAT chip c6 at 0x378, mode 5 
(EPP-32), delay 1
Mar 25 18:42:05 bicycle kernel: pda: Conner Periphe, master, 237744 blocks [116M], 
(762/8/39), fixed media
Mar 25 18:42:05 bicycle kernel:  pda: p1
Mar 25 18:42:05 bicycle kernel: devfs: devfs_auto_unregister(): only one slave allowed
Mar 25 18:42:05 bicycle kernel:   master: "disc"  old slave: "disc1"  new slave: 
"disc3"
Mar 25 18:42:05 bicycle kernel: Forcing Oops
Mar 25 18:42:05 bicycle kernel: kernel BUG at base.c:1887!
Mar 25 18:42:05 bicycle kernel: invalid operand: 
Mar 25 18:42:05 bicycle kernel: CPU:0
Mar 25 18:42:05 bicycle kernel: EIP:0010:[devfs_auto_unregister+98/116]
Mar 25 18:42:05 bicycle kernel: EFLAGS: 00010282
Mar 25 18:42:05 bicycle kernel: eax: 001b   ebx: c6541d40   ecx: c7442000   edx: 
c022e888
Mar 25 18:42:05 bicycle kernel: esi: c6541bc0   edi: c88a84c0   ebp: c6541c40   esp: 
c276dd90
Mar 25 18:42:05 bicycle kernel: ds: 0018   es: 0018   ss: 0018
Mar 25 18:42:05 bicycle kernel: Process modprobe (pid: 4615, stackpage=c276d000)
Mar 25 18:42:05 bicycle kernel: Stack: c0201f4f c02026c0 075f  2d00 
c014a40e c6541d40 c6541bc0
Mar 25 18:42:05 bicycle kernel:c023229c 2d00 c88a84c0 c88a84c0  
 c6541bc0 63736964
Mar 25 18:42:05 bicycle kernel:0033 c027c584 c0113e8f 702f2e2e 69642f64 
00306373 c7af66c0 c012f371
Mar 25 18:42:05 bicycle kernel: Call Trace: [devfs_register_disc+378/412] [] 
[]
Mar 25 18:42:05 bicycle kernel:[] [devfs_register_partitions+26/184] 
[]
[] [check_partition+274/288] [] [] []
Mar 25 18:42:05 bicycle kernel:[] [] [] 
[] [] [] [] []
[] [] [] [] []
Mar 25 18:42:05 bicycle kernel:[] [] [] 
[] [] [] [sys_init_module+1269/1424] []
Mar 25 18:42:05 bicycle kernel:[] [system_call+51/64]
Mar 25 18:42:05 bicycle kernel: Code: 0f 0b 83 c4 0c 90 8d 74 26 00 89 73 24 5b 5e c3 
89 f6 8b 44
Using defaults from ksymoops -t elf32-i386 -a i386

Trace; c88a84c0 <[pd]pd_gendisk+0/30>
Trace; c88a84c0 <[pd]pd_gendisk+0/30>
Trace; c88a8d68 <[pd]pd_buf+4c/203>
Trace; c88a1214 <[paride]pi_unclaim+18/1c>
Trace; c88a1243 <[paride]pi_disconnect+13/18>
Trace; c88a8d20 <[pd]pd_buf+4/203>
Trace; c88a8d20 <[pd]pd_buf+4/203>
Trace; c88a6e51 <[pd]pd_init_dev_parms+79/80>
Trace; c88a8d20 <[pd]pd_buf+4/203>
Trace; c88a8106 <[pd].rodata.start+2c6/4d3>
Trace; c88a84c0 <[pd]pd_gendisk+0/30>
Trace; c88a74da <[pd]pd_detect+14e/184>
Trace; c88a84c0 <[pd]pd_gendisk+0/30>
Trace; c88a84f0 <[pd]pd_fops+0/13>
Trace; c88a64f3 <[pd]pd_init+127/150>
Trace; c88a80a0 <[pd].rodata.start+260/4d3>
Trace; c88a7e40 <[pd].rodata.start+0/4d3>
Trace; c88a7e40 <[pd].rodata.start+0/4d3>
Tra

Re: ext2 corruption in 2.4.2, scsi only system

[Dale E Martin]

> Dale,
> Alan Cox has reported the following:
> 
> > 2.4.2-ac19
> > ...
> > o   Hopefully fix the buslogic corruptions  (me)
> 
> Alan's ac tree also contains a consolidated set of
> patches from Eric Youngdale for the SCSI midlevel.
> Alan's latest is ac25 and may be worth trying (ac24
> has been working fine for me).

After scanning the mailing list archives, I was under the impression that
this Buslogic issue was an AC series problem.  Is there a known problem
with Buslogic controllers in 2.4.2?  

Thanks for the info.

  Dale
-- 
Dale E. Martin, Clifton Labs, Inc.
Senior Computer Engineer
[EMAIL PROTECTED]
http://www.cliftonlabs.com
pgp key available
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 64-bit block sizes on 32-bit systems

[Matthew Wilcox]

On Mon, Mar 26, 2001 at 08:39:21AM -0800, LA Walsh wrote:
> I vaguely remember a discussion about this a few months back.
> If I remember, the reasoning was it would unnecessarily slow
> down smaller systems that would never have block devices in
> the 4-28T range attached.  

4k page size * 2GB = 8TB.

i consider it much more likely on such systems that the page size will
be increased to maybe 16 or 64k which would give us 32TB or 128TB.
you keep on trying to increase the size of types without looking at
what gcc outputs in the way of code that manipulates 64-bit types.
seriously, why don't you just try it?  see what the performance is.
see what the code size is.  then come back with some numbers.  and i mean
numbers, not `it doesn't feel any slower'.

personally, i'm going to see what the situation looks like in 5 years time
and try to solve the problem then.  there're enough real problems with the
VFS today that i don't feel inclined to fix tomorrow's potential problems.

-- 
Revolutions do not require corporate support.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: ext2 corruption in 2.4.2, scsi only system

[Alan Cox]

> After scanning the mailing list archives, I was under the impression that
> this Buslogic issue was an AC series problem.  Is there a known problem
> with Buslogic controllers in 2.4.2?  

It seems there is. The changes in -ac and in 2.4.3pre limit the max blocks
per request which seems to make it happier

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: ext2 corruption in 2.4.2, scsi only system

[Douglas Gilbert]

Dale E Martin wrote:
> [snip]
> I had had good luck with 2.4.x on other boxes, so I put it 
> on this machine as well.  Several times now I've seen ext2 
> corruption with no other noteworthy logs.
> .
> The machine is a dual PPro, it has a Buslogic BT958 with a 
> single 9G scsi/wide drive in it.
> 

Dale,
Alan Cox has reported the following:

> 2.4.2-ac19
> ...
> o   Hopefully fix the buslogic corruptions  (me)

Alan's ac tree also contains a consolidated set of
patches from Eric Youngdale for the SCSI midlevel.
Alan's latest is ac25 and may be worth trying (ac24
has been working fine for me).

Doug Gilbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 64-bit block sizes on 32-bit systems

[LA Walsh]

Matthew Wilcox wrote:
> 
> On Mon, Mar 26, 2001 at 08:39:21AM -0800, LA Walsh wrote:
> > I vaguely remember a discussion about this a few months back.
> > If I remember, the reasoning was it would unnecessarily slow
> > down smaller systems that would never have block devices in
> > the 4-28T range attached.
> 
> 4k page size * 2GB = 8TB.
---
Drat...was being more optimistic -- you're right
the block_nr can be negative.  Somehow thought page size could
be 8Kliving in future land.  That just makes the limitations
even closer at hand...:-(

> you keep on trying to increase the size of types without looking at
> what gcc outputs in the way of code that manipulates 64-bit types.
---
Maybe someone will backport some of the features of the
IA-64 code generator into 'gcc'.  I've been told that in some 
cases it's a 2.5x performance difference.  If 'gcc' is generating
bad code, then maybe the 'gcc' people will increase the quality
of their code -- I'm sure they are just as eagerly working on
gcc improvements as we are kernel improvements.  When I worked
on the PL/M compiler project at Intel, I know our code-optimization
guy would spend endless cycles trying to get better optimization
out of the code.  He got great joy out of doing so. -- and
that was almost 20 years ago -- and code generation has come
a *long* way since then.

> seriously, why don't you just try it?  see what the performance is.
> see what the code size is.  then come back with some numbers.  and i mean
> numbers, not `it doesn't feel any slower'.
---
As for 'trying' it -- would anyone care if we virtualized
the block_nr into a typedef?  That seems like it would provide
for cleaner (type-checked) code at no performance penalty and
more easily allow such comparisons.

Well this is my point: if I have disks > 8T, wouldn't
it be at *all* beneficial to be able to *choose* some slight
performance impact and access those large disks vs. having not
choice?  Having it as a configurable would allow a given 
installation to make that choice rather than them having no
choice.  BTW, are block_nr's on RAID arrays subject to this
limitation?
> 
> personally, i'm going to see what the situation looks like in 5 years time
> and try to solve the problem then.
---
It's not the same, but SGI has had customers for over
3 years using >2T *files*.  The point I'm looking at is if
the P-X series gets developed enough, and someone is using a
4-16P system, a corp user might be approaching that limit
today or tomorrow.  Joe User, might not for 5 years, but that's
what the configurability is about.  Keep linux usable for both
ends of the scale -- "I love scalability"

-l

-- 
L A Walsh| Trust Technology, Core Linux, SGI
[EMAIL PROTECTED]  | Voice: (650) 933-5338
-- 
L A Walsh| Trust Technology, Core Linux, SGI
[EMAIL PROTECTED]  | Voice: (650) 933-5338
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Lovely crash with 2.4.2-ac24.

[Andre Hedrick]

Zephaniah,

Does this happen in a non-ac kernel?
I have not updated code since around 2.4.0, but other have.
You point ot a few times w/ ac18, but is there one before that which does
not cause this to happen?

The question is to gain isolation of the changes.

On Mon, 26 Mar 2001, Zephaniah E. Hull wrote:

> This had hit me a few times with ac18 (I'm not sure it was the same
> crash though) and just hit me again with ac24.
> 
> Alan cced due to it being in the ac kernels, Andre because the trace
> seems to point to the IDE code.
> 
> Thanks.
> 
> Zephaniah E. Hull.
> 
> -- 
>  PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801
> Keys available at http://whitestar.soark.net/~warp/public_keys.
>CCs of replies from mailing lists are encouraged.
> 
>  Mercury: gpm isn't a very good web browser.  fix it.
> 

Andre Hedrick
Linux ATA Development
ASL Kernel Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: slow latencies on IDE disk drives( controller? )

[Andre Hedrick]

Hello GAT,

Can you be more specific?  I need a kernel and hardware info and generally
more info than what is given.  Is this a PIO/DMA process is it a laptop or
unsupported hardware?

On Mon, 26 Mar 2001, Uncle George wrote:

> I am processing sound data on /dev/dsp. Generally the ~61k devive buffer
> is enough to keep the device satiated && gives the program time to fill
> up the device buffer when there is 16k of buffer space that needs to be
> filled.
> 
> But on occasion the /dev/dsp device "slurrs" ( sounds like what happens
> when the speed of a tape recorder slows down due to a finger placed down
> on the capstain ) unexpectedly. This was eventually traced to the usage
> of an IDE disk drive. using the scsi drive does not cause the problem to

How did you derive this path to the ATA driver?
What is the drive, and how fast (or how slow) is it?

> manifest itself( at least my ears say so ). but using "dd if=/dev/hda4
> of=/dev/null ) does immediately cause the slurring to happen.
> 
> 
> I think I can create a simple pgm to demo this problem, but the DATA
> file that gets feed into /dev/dsp is a little large for e-mail.

The content of the barf is not important, but the process you are doing to
create this issue is.

Andre Hedrick
Linux ATA Development

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: NCR53c8xx driver and multiple controllers...(not new prob)

[Gérard Roudier]

On Sun, 25 Mar 2001, LA Walsh wrote:

> Here is the 'alternate' output when the ncr53c8xx driver is
> compiled in:
> 
> SCSI subsystem driver Revision: 1.00
> scsi-ncr53c7,8xx : at PCI bus 0, device 8, function 0
> scsi-ncr53c7,8xx : warning : revision of 35 is greater than 2.
> scsi-ncr53c7,8xx : NCR53c810 at memory 0xfa101000, io 0x2000, irq 58
> scsi0 : burst length 16
> scsi0 : NCR code relocated to 0x37d6c610 (virt 0xf7d6c610)
> scsi0 : test 1 started
> scsi0 : NCR53c{7,8}xx (rel 17)
> request_module[block-major-8]: Root fs not mounted
> VFS: Cannot open root device "807" or 08:07
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 08:07
> -

The 53c7,8xx driver is a different driver that hasn't been updated for the
support of the 53C896. I figure out that you already have been replied
upon this point.

For your machine configuration you want to use either the NCR53C8XX driver
or the SYM53C8XX driver. The SYM53C8XX driver has a better support for the
896 as it handles phase mismatch from SCRIPTS. The both drivers share the
same kernel config options for simplicity (in fact the SYM53C8XX driver
just steals the NCR53C8XX config options).

Go to the SCSI low-level configuration form under make menuconfig for
example and configure the SYM53C8XX driver as 'Y' and the NCR53C8XX driver
as 'N'. Btw, also configure 'N' the 53c7,8xx driver to avoid conflicts.

You may also have a look at the help entries for these drivers and at the 
file linux/drivers/scsi/README.ncr53c8xx (also applies to SYM53C8XX).

A driver named SYM-2 that replaces both the NCR53C8XX and the SYM53C8XX
drivers also exists. This driver is multi-platform and for now has been 
added support for Linux, FreeBSD and NetBSD. It is intended to replace the
NCR53C8XX and the SYM53C8XX. It is not included in Linux for now since we
only have _stable_ kernels at the moment and the NCR+SYM driver pair is
the current _stable_ support for SYMBIOS 53C8XX controllers. 
If you want to try SYM-2: ftp://ftp.tux.org/roudier/README-drivers-linux

  Gérard.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [kbuild-devel] Re: CML1 cleanup patch

[Eric S. Raymond]

Rik van Riel <[EMAIL PROTECTED]>:
> What's wrong with using the _file type_ for these things ?

I don't understand that.
 
> Conversely, why can't CML2 use the CONFIG_ prefix to
> determine if a symbol is a configuration option, like
> we're doing now?

I do understand this.  Greg Banks pointed it out last night, and I'm
testing a CML2 version that implements it now.
-- 
http://www.tuxedo.org/~esr/">Eric S. Raymond

The two pillars of `political correctness' are, 
  a) willful ignorance, and
  b) a steadfast refusal to face the truth
-- George MacDonald Fraser
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Adaptec Array1000

[Justin T. Gibbs]

>Hi all,
>
>Does anyone know how to configure this controller (chipset AAA-133U2
>aka AIC-78xx) with one RAID5 hardware volume ? The kernel 2.2.16 see
>all the disks (4x18Gb) but don't see the unique volume.

These boards are not currently supported in RAID mode.  Your
best bet is Linux MD.

--
Justin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 2.4.2 fs/inode.c

[Chris Mason]

On Thursday, March 22, 2001 01:42:15 PM -0500 Jan Harkes
<[EMAIL PROTECTED]> wrote:

> 
> I found some code that seems wrong and didn't even match it's comment.
> Patch is against 2.4.2, but should go cleanly against 2.4.3-pre6 as well.
> 

Ok, this looks correct, makes reiserfs faster, and survived under load.  The
idea was to only call dirty_inode if sync_one might decide the inode needs
flushing to disk.  So, the check in __mark_inode_dirty should look the same
as the check in sync_one.

> --- linux/fs/inode.c.orig Thu Mar 22 13:20:55 2001
> +++ linux/fs/inode.c  Thu Mar 22 13:21:32 2001
> @@ -133,7 +133,7 @@
>  
>if (sb) {
>/* Don't do this for I_DIRTY_PAGES - that doesn't actually dirty the
>inode itself */ 
> - if (flags & (I_DIRTY | I_DIRTY_SYNC)) {
> + if (flags & (I_DIRTY_SYNC | I_DIRTY_DATASYNC)) {
>if (sb->s_op && sb->s_op->dirty_inode)
>sb->s_op->dirty_inode(inode);
>}
> -

-chris

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: 64-bit block sizes on 32-bit systems

[Manfred Spraul]

>> I vaguely remember a discussion about this a few months back.
>> If I remember, the reasoning was it would unnecessarily slow
>> down smaller systems that would never have block devices in
>> the 4-28T range attached.
>
>4k page size * 2GB = 8TB.

Try it.
If your drive (array) is larger than 512byte*4G (4TB) linux will eat
your data.

drivers/block/ll_rw_blk.c, in submit_bh()
>bh->b_rsector = bh->b_blocknr * (bh->b_size >> 9);

But it shouldn't cause data corruptions:
It was discussed a few months ago, and iirc LVM refuses to create too
large volumes.

--
Manfred


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: paride error, aparantly with VFS

[Tim Waugh]

On Sun, Mar 25, 2001 at 09:37:38PM -0800, [EMAIL PROTECTED] wrote:

> do_pd_read_drq: status = 0x10050 = SEEK READY TMO

Please try a recent -ac kernel and let me know if the problem persists
or goes away.

Tim.
*/

 PGP signature

2.2.19 toshiba module fix

[Greg KH]

The following patch enables the toshiba module to compile correctly on
2.2.19.

thanks,

greg k-h

-- 
greg@(kroah|wirex).com
http://immunix.org/~greg


diff -Naur -X /home/greg/linux/dontdiff linux-2.2.19/drivers/char/toshiba.c 
linux-2.2.19-greg/drivers/char/toshiba.c
--- linux-2.2.19/drivers/char/toshiba.c Sun Mar 25 09:45:19 2001
+++ linux-2.2.19-greg/drivers/char/toshiba.cMon Mar 26 09:19:08 2001
@@ -78,7 +78,7 @@
 #include
 #endif
 
-#include"toshiba.h"
+#include
 
 #define TOSH_MINOR_DEV 181
 

Re: 64-bit block sizes on 32-bit systems

[Matthew Wilcox]

On Mon, Mar 26, 2001 at 08:01:21PM +0200, Manfred Spraul wrote:
> drivers/block/ll_rw_blk.c, in submit_bh()
> >bh->b_rsector = bh->b_blocknr * (bh->b_size >> 9);
> 
> But it shouldn't cause data corruptions:
> It was discussed a few months ago, and iirc LVM refuses to create too
> large volumes.

Ah yes, I'd forgotten the block layer still works in terms of 512-byte blocks.

-- 
Revolutions do not require corporate support.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Adaptec Array1000

[Roberto Fichera]

At 10.51 26/03/01 -0700, Justin T. Gibbs wrote:

> >Hi all,
> >
> >Does anyone know how to configure this controller (chipset AAA-133U2
> >aka AIC-78xx) with one RAID5 hardware volume ? The kernel 2.2.16 see
> >all the disks (4x18Gb) but don't see the unique volume.
>
>These boards are not currently supported in RAID mode.  Your
>best bet is Linux MD.

Ok! As I was thinking, I must configure it with Linux MD.

Thanks.


Roberto Fichera.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/