* Anton Blanchard [EMAIL PROTECTED] [001004 21:31]:
I just had my box completely lock up under 2.4.0-test9. I had insmodded
the dbri.o audio driver, which for some reason was refusing to work, at
all. So I rmmodded it, and at that point, the screen flickered once and
wham, complete
Andre Hedrick wrote:
On Mon, 9 Oct 2000, Andre Tomt wrote:
The fastest ATA drives out that are not public yet are in 39-42mB/s.
Also SCSI can not sustain rates much better than maybe 60mB/s.
Andre, how are you benchmarking drives ?
In context you wrote, I've got rather curious results
[EMAIL PROTECTED] wrote:
8. Fix Exists But Isnt Merged
* 2.4.0-test8 has a BUG at ll_rw_blk:711. (Johnny Accot, Steffen
Luitz) (Al Viro has a patch)
Said patch has already been merged in the test9-pre and -final series
and the bug can be considered fixed.
-Udo.
-
To
Hi there!
FIRST: I did NOT load the pwc-driver from nemosoft! (I hope anybody
is satisfied now ;-)
I got the following kernel oops when plugging the webcam. There
wis NO driver installed! Just plugging in.
I attach the output form messages send through ksymoops, the USB relevant
part of my
Hi!
The following BUG related oopses caused my machine to die (well, X didnt
survive...) while just compiling a little program. I dont know if these
issues are fixed yet within one of the floating patches, so here goes the
report (dmesg stripped a little).
Richard.
--
Richard Guenther [EMAIL
On Mon, 9 Oct 2000 [EMAIL PROTECTED] wrote:
* Writing to tapes 2.4G causes tar to fail with EIO (using
2.4.0-test7-pre5; it works under 2.4.0-test1-ac18 --- Tigran
Aivazian)
this has now been working since test8 and certainly in test9. Why it
failed on test7-pre5? Probably
On Mon, Oct 09, 2000 at 03:54:21AM +0200, Andi Kleen wrote:
On Mon, Oct 09, 2000 at 02:45:54AM +0100, Kenn Humborg wrote:
On Mon, Oct 09, 2000 at 02:21:09AM +0100, Kenn Humborg wrote:
On Mon, Oct 09, 2000 at 02:20:27AM +0200, Andi Kleen wrote:
2.4 TCP code relies on current being valid
On Mon, 9 Oct 2000, blizbor wrote:
Andre, how are you benchmarking drives ?
Direct access below the driver without any file-system getting in the way.
No reorder of requests because of linear seeks.
These are kernel level tests because timers get set upon the execution of
the command block
Andre Hedrick wrote:
snip
They may be a way to test and create drive profiles that are stored and
reloaded to the kernel that will add the missing supercharge on Andrea's
elevator. Basically creating a physical LBA sector profile.
Trust that this will be painful to create because this is
On Mon, 9 Oct 2000, Andre Hedrick wrote:
snip
You are doing Ultra-66 speeds my friend.
The fastest ATA drives out that are not public yet are in 39-42mB/s.
Also SCSI can not sustain rates much better than maybe 60mB/s.
Actually, my other IBM UDMA33 drive did 20mB/s on a 600mB IDE to SCSI
Ive been seeing poor read results from tiotest in recent 2.2 kernels
since 2.2.16.
The performance is fine with 1 thread but slows right down with 8.
I include the tiotest results here but I see similar results with iozone
-t.
Kernel 2.2.15
[robert@testmac25 robert]$ tiotest -f 30 -t 8 -r 0
But you are right, here is a bug nobody reported before. I will take care of
it.
Hmm,
your just a bit off here, I believe Gerhard has posted this bug
a number of times, further more I have submitted a fix for this
bug, but has still not been accepted. Neither has there been any feedback
on
Hi,
The m68k port which has a interrupt stack solves the problem by
loading current into a global register variable on all kernel entries.
Not all m68k cpus have an interrupt stack and it can be turned off, so we
don't use it.
bye, Roman
-
To unsubscribe from this list: send the line
On Mon, 9 Oct 2000, Andre Tomt wrote:
Using a newer ATA66 IBM 7200rpm drive, on a VIA chipset, I can sustain
24-25mB/s in both UDMA33 and ATA66 mode. This is a Athlon Asus
This okay, the drive has a physical data IO limit for sustained, not
burst. Thus getting 24-25mB/s in both UDMA33/ATA66
On Fri, 6 Oct 2000, Rik van Riel wrote:
[...]
They are niced because the user thinks them a bit less
important.
Please don't, this assumption is quite wrong. I use nice just to be
'nice' to other users. I can run my *important* CPU hog simulation
nice +10 in order to let other people get
On Mon, 9 Oct 2000, Keith Owens wrote:
On Sun, 8 Oct 2000 23:50:43 +0200 (MEST),
Jaroslav Kysela [EMAIL PROTECTED] wrote:
this patch contains following fixes and enhancements to export ISA
PnP IDs outside the kernel module:
* module.h - added MODULE_GENERIC_TABLE
* isapnp.h - added
On Mon, 9 Oct 2000 12:29:19 +0200 (MEST),
Jaroslav Kysela [EMAIL PROTECTED] wrote:
On Mon, 9 Oct 2000, Keith Owens wrote:
Modutils and the kernel are compiled from different headers, none of
this #include linux/xxx.h business in modutils. So you must never
assume that the structures in
On Mon, 9 Oct 2000, Keith Owens wrote:
On Mon, 9 Oct 2000 12:29:19 +0200 (MEST),
Jaroslav Kysela [EMAIL PROTECTED] wrote:
On Mon, 9 Oct 2000, Keith Owens wrote:
Modutils and the kernel are compiled from different headers, none of
this #include linux/xxx.h business in modutils. So you
On Mon, 9 Oct 2000, Andre Hedrick wrote:
huge snip
Recall that I told you that there is a physical limit of getting stuff off
the drives. The platter density is to low and the rpm's are to slow to
get there yet. Remember it took second genration ATA66 drives to fill
the ATA33 bandwidth.
I'm still looking for a 2.2.17 driver for my Tekram DC390U3W dual channel
scsi card. I found drivers for 2.2.16 and below on the lsi and tekram
ftp-sites, but applying them causes rejects, and manually fixing the
driver makes sg going into an infinite loop during boot. My C knowledge is
very
On Mon, Oct 09, 2000 at 02:08:55AM -0700, Miles Lane wrote:
Andre Hedrick wrote:
snip
They may be a way to test and create drive profiles that are stored and
reloaded to the kernel that will add the missing supercharge on Andrea's
elevator. Basically creating a physical LBA sector
Browsing patch-2.2.17.gz I found this:
linux/arch/i386/kernel/setup.c:
Isn't here an "else" or "break" missing? Otherwise
``x86_cap_flags[16] = "pat"'' is always the case, and extended
AMD features are always present.
@@ -1029,17 +1130,22 @@
case X86_VENDOR_AMD:
On Mon, 9 Oct 2000, Marco Colombo wrote:
On Fri, 6 Oct 2000, Rik van Riel wrote:
[...]
They are niced because the user thinks them a bit less
important.
Please don't, this assumption is quite wrong. I use nice just to be
'nice' to other users. I can run my *important* CPU hog
On Mon, 9 Oct 2000 12:55:28 +0200 (MEST),
Jaroslav Kysela [EMAIL PROTECTED] wrote:
I fully understand your point, but I don't want to have a special
case for ISA PnP. What about this change:
#define MODULE_GENERIC_TABLE(gtype,name)\
const struct gtype##_id * __module_##gtype##_table =
On Mon, 9 Oct 2000, blizbor wrote:
On Mon, 9 Oct 2000, Andre Tomt wrote:
The fastest ATA drives out that are not public yet are in 39-42mB/s.
Also SCSI can not sustain rates much better than maybe 60mB/s.
Andre, how are you benchmarking drives ?
In context you wrote, I've got rather
The kernel provided with the redhat 7.0 cannot be compiled with ip =
masquerading on icmp masquerading on (using gcc and kgcc, I got the =
same error).
I could not found any information about that.
Anyone can help ?
Can you put the report in Red Hat bugzilla rather than the main kernel
Hi,
I recently changed the kernel from 2.2.15 to 2.2.17 and added new promise 100
card. During 3 days 2 production servers crashed 4 times and had several
lockups when there was zillion messages like
VM: do_try_to_free_memmory failed for XXX
we then changed the kernel to 2.2.18pre3 + ide + raid
all attempts to access the scanner, including running the xsane program,
or even probing for attached scanners with "scanimage -L" cause the box
to run extremely slowly. CTL-C the program accessing the scanner and the
system responsiveness returns to normal.
What scsi controller card are you
make xconfig
make dep
make clean
[make bzImage]
you need the kernel image here
make modules
make modules_install
edit /etc/lilo.conf and add lilo header.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read
Alan Cox wrote:
all attempts to access the scanner, including running the xsane program,
or even probing for attached scanners with "scanimage -L" cause the box
to run extremely slowly. CTL-C the program accessing the scanner and the
system responsiveness returns to normal.
What scsi
On Mon, Oct 09, 2000 at 09:47:43AM +0200, valery brasseur wrote:
I have a Oops in the kernel which say's "tcp_v4_hash: bug, socket state
is 1"
can someone explain me what's wrong ?
Hard to say when you don't send the decoded (=run through ksymoops
with correct System.map) oops.
-Andi
-
To
linux-2.4.0-test9
gcc-2.97 CVS
configured for Athlon
binutils-2.9.5.0.22-6
Do I need an updated binutils maybe?
as --version
GNU assembler 2.9.5
[...]
gcc -D__KERNEL__ -I/usr/src/linux-2.4.0-test9/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2
You need to set your /proc/sys/net/core/{w,r}mem* values large enough
for the window scale to have any reason to have a non-zero value.
Later,
David S. Miller
[EMAIL PROTECTED]
OK. That worked. Thanks! It is worth noting that the 2.4.0-test9-pre9
kernel doesn't care about the {r,w}mem_max
On Mon, Oct 09, 2000 at 12:19:26AM -0400, [EMAIL PROTECTED] wrote:
Linux 2.4 Status/TODO Page
* 2.4.0-test2 breaks the behaviour of the ether=0,0,eth1 boot
parameter (dwguest)
This has been fixed.
-
To unsubscribe from this list: send the line "unsubscribe
on 10/8/00 4:23 PM, [EMAIL PROTECTED] at [EMAIL PROTECTED] wrote:
I am looking for a solution for the following problem.
We have installed some new promise 100 cards and ibm ata 100 disks
on some of the servers, assembled the 2.2.17 + ide + raid kernel.
Since then we had several crashes on
Hi there,
there has been a patch, which limits the amount of RAM used by
ramfs.
I didn't find this in the archives (neither public ones nor
private). And no, I do NOT think I just dreamed about it ;-)
TIA Regards
Ingo Oeser
--
Feel the power of the penguin - run [EMAIL PROTECTED]
esc:x
-
On 6 Oct 00 at 19:25, Petr Vandrovec wrote:
Hi,
month ago I informed here that VMware causes oops on exit.
After some time, and tons of tweaking I was able to recreate
it without vmmon... 2.4.0-test9, no special patches, no
vmware modules loaded...
Machine is dual PIII/450, 256MB
Andi Kleen wrote:
On Mon, Oct 09, 2000 at 02:51:28PM +0200, valery brasseur wrote:
Andi Kleen wrote:
On Mon, Oct 09, 2000 at 09:47:43AM +0200, valery brasseur wrote:
I have a Oops in the kernel which say's "tcp_v4_hash: bug, socket state
is 1"
can someone explain me what's
On Mon, Oct 09 2000, Alan Cox wrote:
At this point, I would prefer that we just leave the ordering alone - I
don' tknow of any actual problems with it, and I don't think it's worth
re-organizing things to make it the exact same thing it used to be..
SCSI has real ordering requirements
On Mon, Oct 09, 2000 at 01:05:10PM +0200, Andre Tomt wrote:
The sym53c8xx driver handles this card nicely in u160scsi mode using
kernel 2.4testX, but I don't want that kernel on this machine. 2.2.17 does
not detect the card, and looking at the source, the chip, nor the speeds
are not
* RTL 8139 cards sometimes stop responding. Both drivers don't
handle this quite good enough yet. (reported by Rogier Wolff,
tentatively reported as fixed by David Ford.)
2.4.0-test9 Spontaneous reboots under network load with this
driver. Sorry, no more
Anyone tried this combination?
I had one small compile problem in the driver (which was a return code,
something about HASH, I forget now, but it's only defined for i386)
After that, mkfs and attempted to mount didn't work. the driver couldn't
find a valid fs on the drive.
I have successfully
On Mon, Oct 09, 2000 at 12:12:02PM +0200, Marco Colombo wrote:
On Fri, 6 Oct 2000, Rik van Riel wrote:
[...]
They are niced because the user thinks them a bit less
important.
Please don't, this assumption is quite wrong. I use nice just to be
'nice' to other users. I can run my
Graham Leggett wrote:
all attempts to access the scanner, including running the xsane program,
or even probing for attached scanners with "scanimage -L" cause the box
to run extremely slowly. CTL-C the program accessing the scanner and the
system responsiveness returns to normal.
hello,
i haven't been on lkml since vger died, but just subscribed and looked
at the archives and was unable to find anything on this...
i'm running 2.4.0-test9 and 2.2.18-pre15. for both of these kernels, if
i enable usb and smp, i get a lot of usb device timeout errors. if i
recompile, just
Andre Hedrick wrote:
Something like this?
Close but now there is no select.
--- /opt/kernel/linux-2.4.0-test9/drivers/scsi/ide-scsi.c Sat Sep 23
I'm having some serious problems with parallel port ZIP with latest
2.4.0-test9 kernel
Oct 9 16:57:23 dual kernel: Detected scsi
You have to do Buslogic and AHA17xx before AHA15xx or you get a wrong driver
and in the 17xx case data corruption risks
You must do scsi before i2o_scsi or AMI Megaraids break
My point exactly. The ordering of driver in drivers/scsi is done now,
but I don't see a clean way of
oh, btw, i also tried an asus p2b-ds mobo with the intel bx chipset with
the same results.
pete
On Mon, 09 Oct 2000, Pete Toscano wrote:
hello,
i haven't been on lkml since vger died, but just subscribed and looked
at the archives and was unable to find anything on this...
i'm running
On Sat, Oct 07, 2000 at 12:42:16PM -0400, Brian Gerst wrote:
"Forever shall I be." wrote:
I got this OOPS while unloading the ns558 module.. I don't think it did
this in 2.4.0-test8, but I don't recall ever unloading it in test8..
I've attached the ksymoops output..
--
Zinx
On Mon, Oct 09, 2000 at 02:08:55AM -0700, Miles Lane wrote:
like Partition Magic? It sure would be nice to have a native
version of Partition Magic or an Open Source work-alike.
Is anyone aware of a project to implement such an Open Source
alternative?
ftp://ftp.gnu.org/gnu/parted
--
i2o_block.c: you don't need EXPORT_NO_SYMBOLS (yes, I know it was there
before)
I put it there intentionally. It exports no symbols. I dont want the module
stuff therefore exporting everything in that file.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Mon, Oct 09 2000, Alan Cox wrote:
You have to do Buslogic and AHA17xx before AHA15xx or you get a wrong driver
and in the 17xx case data corruption risks
You must do scsi before i2o_scsi or AMI Megaraids break
My point exactly. The ordering of driver in drivers/scsi is done
Miles writes:
Is this the kind of information required to build an application
like Partition Magic? It sure would be nice to have a native
version of Partition Magic or an Open Source work-alike.
Is anyone aware of a project to implement such an Open Source
alternative?
The GNU parted
On Mon, 9 Oct 2000, Alan Cox wrote:
SCSI has real ordering requirements for drivers.
You have to do Buslogic and AHA17xx before AHA15xx or you get a wrong driver
and in the 17xx case data corruption risks
Hmm.. The current order is the same as in 2.2.x, and puts aha17xx _after_
On Mon, 9 Oct 2000, Torben Mathiasen wrote:
My point exactly. The ordering of driver in drivers/scsi is done now,
but I don't see a clean way of doing I2O without moving upperlayers
into a seperate dir.
Why?
People would tend to use the i2o ones as modules anyway, so they _have_ to
work
On Mon, 9 Oct 2000, Alan Cox wrote:
Link scsi as a whole before i2o ?
Yup.
Also, we should really finalise the host order thing in scsi/Makefile. If
it's true that aha17xx must come before aha1542, it's wrong as it stands
now. Any other gotchas that were caught in 2.2.x?
On Mon, Oct 09, 2000 at 12:36:46PM -0400, Pete Toscano wrote:
any more information i can provide to help?
Yes:
What kind of timeout errors are you seeing? Kernel debug logs would be
helpful.
What devices are you trying to use?
What is your .config file?
What is your BIOS setting for MPS (if
On Mon, 9 Oct 2000, Torben Mathiasen wrote:
Link scsi as a whole before i2o ?
Yes, that can be done pretty easy, but Then I2O will link
core - hosts - upper - I2O and I'm not sure this is okay.
Think modules. Remember how it has always worked.
The above is pretty much how all
Could we change the behaviour in 2.2 like we did it in 2.3 and make it
more compatible with other UN*Xes? The attached (untested) patch
should implement the 2.4 behaviour.
Maybe, but not for 2.2.18
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Mon, Oct 09 2000, Linus Torvalds wrote:
On Mon, 9 Oct 2000, Alan Cox wrote:
Link scsi as a whole before i2o ?
Yup.
Also, we should really finalise the host order thing in scsi/Makefile. If
it's true that aha17xx must come before aha1542, it's wrong as it stands
now. Any
I've seen the problem on both of my computers with Creative Riva TNT2. On
this card the palette turns darker. On other cards the palette turns to
rubbish or corrupted in another fashionable ways. It's a bug in those
cards - switching to video mode and back to text mode doesn't preserve the
greg,
machine's at home and in a bit of a wedged state, so i can't get this
info to you right away, but i will if you think it'll help debug the
issue. from what you say, the people on the linux-usb-devel list
already have patches for these things, so i'm wondering if it'll be
useful.
anyway,
On Sun, 8 Oct 2000, Linus Torvalds wrote:
On Wed, 4 Oct 2000, Rik van Riel wrote:
The potential for this bug has been around since 2.3.51, when
different balance_ratios for different zones became possible.
You must NOT depend on some global "freepages" thing.
Don't do this patch. Fix
In article [EMAIL PROTECTED],
Kenn Humborg [EMAIL PROTECTED] wrote:
I'd just like to confirm that it's illegal to call current()
from interrupt-handling code.
It's not categorically forbidden.
It does indeed happen, think about things like cross-CPU interrupts for
TLB invalidations etc.
At
Sigh... Do a search on Brook's Law, will you?
You lose because the project isn't late yet ;-)
Brooks' law has certain assumptions in it that are not applicable to a low
communication cost, highly parallel environments
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Alan Cox wrote:
4. Boot Time Failures
* IBM Thinkpad 390 won't boot since 2.3.11 (See Decklin Foster for
more info)
Add Palmax PD1100 hangs during boot since 2.4.0-test9
My Asus P55TP4 (i430FX)/AMD K5 PC also crashes after "Booting the
kernel..."
and before printing
On Mon, 9 Oct 2000, Marco Colombo wrote:
On Fri, 6 Oct 2000, Rik van Riel wrote:
[...]
They are niced because the user thinks them a bit less
important.
Please don't, this assumption is quite wrong. I use nice just to
be 'nice' to other users. I can run my *important* CPU hog
For what it's worth, the system was called "Jackdaw" and was written by
Mike Challis. It was in extensive use on the University's MVT/MVS/MVSXA
mainframe for many years as the database for holding user information. The
document Alain's got is probably Computer Laboratory Technical Report no.
Also, we should really finalise the host order thing in scsi/Makefile. If
it's true that aha17xx must come before aha1542, it's wrong as it stands
now. Any other gotchas that were caught in 2.2.x?
Those are the only ones I know
Buslogic cards and AHA174x cards both emulate an aha1542 but
You have to do Buslogic and AHA17xx before AHA15xx or you get a wrong driver
and in the 17xx case data corruption risks
Hmm.. The current order is the same as in 2.2.x, and puts aha17xx _after_
the other ones. Or did that change in the later 2.2.x series?
I will double check that
On Mon, Oct 09 2000, Linus Torvalds wrote:
On Mon, 9 Oct 2000, Torben Mathiasen wrote:
My point exactly. The ordering of driver in drivers/scsi is done now,
but I don't see a clean way of doing I2O without moving upperlayers
into a seperate dir.
Why?
I was referring to Alan's
Kurt Garloff wrote:
I could not agree more. Normally, you'd better kill a foreground task
(running nice 0) than selecting one of those background jobs for some
reasons:
* The foreground job can be restarted by the interactive user
(Most likely, it will be only netscape anyway)
* The
Yes, that can be done pretty easy, but Then I2O will link
core - hosts - upper - I2O and I'm not sure this is okay.
Thats fine. I2O scsi is the last scsi driver anyway, the rest of i2o registers
devices on different majors with no ordering issues
-
To unsubscribe from this list: send the
On Mon, 9 Oct 2000, Andrea Arcangeli wrote:
On Fri, Oct 06, 2000 at 04:19:55PM -0400, Byron Stanoszek wrote:
In the OOM killer, shouldn't there be a check for PID 1 just to enforce that
Init can't be killed in 2.2.x latest, the same bugfix should be forward
ported to 2.4.x.
I believe we
I'm having real trouble mounting a dvd (udf filesystem) in my Pioneer
104S drive. It usually failes with:
mount: wrong fs type, bad option, bad superblock on /dev/dvd,
or too many mounted file systems
but it succeeds sometimes. For a while I've been inserting the dvd,
waiting until the
On Mon, Oct 09 2000, Alan Cox wrote:
Yes, that can be done pretty easy, but Then I2O will link
core - hosts - upper - I2O and I'm not sure this is okay.
Thats fine. I2O scsi is the last scsi driver anyway, the rest of i2o registers
devices on different majors with no ordering issues
On Wed, 04 Oct 2000, Brian Gerst wrote:
Mikulas Patocka wrote:
Hi.
arch/i386/kernel/entry.S
xchgl %eax, ORIG_EAX(%esp) # orig_eax (get the error code. )
movl %esp,%edx
xchgl %ecx, ES(%esp)# get the address and save es.
pushl %eax
Excellent. But Alan, you wrote earlier that i2o needed to be the last host
adapter and _before_ the upper layers. This is what made me start this
patch.
Sorry. Then I was unclear and I sent you off doing un-needed work.
Apologies
-
To unsubscribe from this list: send the line "unsubscribe
On Mon, Oct 09, 2000 at 08:37:55PM +0200, Mikael Pettersson wrote:
We could also do the following:
1. Move the error_code block from divide_error to page_fault;
this removes one jump from the page_fault path.
It is not clear that it is worth it. You want to align error_code and
On Mon, 9 Oct 2000, Ingo Molnar wrote:
If you have a better algorithm, feel free to send patches.
yes. Please remove the above part.
OK, done.
Rik
--
"What you're running that piece of shit Gnome?!?!"
-- Miguel de Icaza, UKUUG 2000
http://www.conectiva.com/
On Mon, Oct 09, 2000 at 08:42:26PM +0200, Ingo Molnar wrote:
ignoring the kill would just preserve those bugs artificially.
If the oom killer kills a thing like init by mistake or init has a memleak
you'll notice both problems regardless of having a magic for init in a _very_
slow path so I
Rik van Riel wrote:
On Mon, 9 Oct 2000, Marco Colombo wrote:
On Fri, 6 Oct 2000, Rik van Riel wrote:
[...]
They are niced because the user thinks them a bit less
important.
Please don't, this assumption is quite wrong. I use nice just to
be 'nice' to other users. I can run my
On Mon, 9 Oct 2000, Andrea Arcangeli wrote:
On Mon, Oct 09, 2000 at 08:42:26PM +0200, Ingo Molnar wrote:
ignoring the kill would just preserve those bugs artificially.
If the oom killer kills a thing like init by mistake
That only happens in the "random" OOM killer 2.2 has ...
So you
2.4.0-test9
modules.dep reports that pppox needs pppoe and pppoe needs pppox.
modprobe pppo(e|x) segfaults (out of memory???).
---
Meelis Roos ([EMAIL PROTECTED])
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read
Meelis Roos writes:
2.4.0-test9
modules.dep reports that pppox needs pppoe and pppoe needs pppox.
modprobe pppo(e|x) segfaults (out of memory???).
A fix has been submitted. If you need a quick fix, do not compile as
a module, or remove line 158 of pppox.c.
Michal Ostrowski
[EMAIL
Rik van Riel wrote:
On Mon, 9 Oct 2000, Marco Colombo wrote:
On Fri, 6 Oct 2000, Rik van Riel wrote:
[...]
They are niced because the user thinks them a bit less
important.
Please don't, this assumption is quite wrong. I use nice just to
be 'nice' to other users. I can run my
Hiya,
Subject says it all... If I select 'Winchip 2' or 'Winchip 2A/Winchip 3' for
'Processor Family' and try to boot the kernel on an iopener with a Winchip 2A,
the show stops right after the 'decompressing the kernel...' line is
displayed. Nothing happens. It just freezes...
Cheers//Frank
Here's an idea, farfetched as it may be.
Page the entire process out to disk into a user defined area, SIGHALT it and use
printk or a kthread/userproc to notify the user that something was kicked out of
the sandbox for playing bad. The user can add more swap if desired, then use a
userland tool
8139too Fast Ethernet driver 0.9.10 loaded
eth0: RealTek RTL8139 Fast Ethernet at 0xc8859000, 00:c0:df:04:7f:9b, IRQ 11
eth0: Identified 8139 chip type 'RTL-8139B'
I routinely (several times an hour) get messages like this:
eth0: Abnormal interrupt, status 0002
2.4.0-test9, x86, UP
AMD
On Mon, 9 Oct 2000, Rick Haines wrote:
I'm having real trouble mounting a dvd (udf filesystem) in my Pioneer
104S drive. It usually failes with:
mount: wrong fs type, bad option, bad superblock on /dev/dvd,
or too many mounted file systems
I suspect that it is a UDF issue and not
Then spam the console loudly with printk, but don't destroy the whole machine.
Init should only get killed if it REALLY is taking a lot of memory. On a 4 or 8meg
machine tho, the probability of init getting killed is simply too high for
comfort. I have never ever seen init start consuming
[EMAIL PROTECTED] (BERNARD Sebastien) wrote..
Near the test3-4 kernel, I was not able to reach www.linuxtoday.com.
After some debug, I find that is because my linux box is emitting syn
packet with some really strange options (description of packet follows).
Can anyone tell me if this
On Mon, 9 Oct 2000, Rik van Riel wrote:
On Mon, 9 Oct 2000, Marco Colombo wrote:
On Fri, 6 Oct 2000, Rik van Riel wrote:
[...]
They are niced because the user thinks them a bit less
important.
Please don't, this assumption is quite wrong. I use nice just to
be 'nice' to
On Mon, Oct 09, 2000 at 04:07:32PM -0300, Rik van Riel wrote:
No. It's only needed if your OOM algorithm is so crappy that
it might end up killing init by mistake.
The algorithm you posted on the list in this thread will kill init if on 4Mbyte
machine without swap init is large 3 Mbytes and
On Mon, 9 Oct 2000, Andrea Arcangeli wrote:
No. It's only needed if your OOM algorithm is so crappy that
it might end up killing init by mistake.
The algorithm you posted on the list in this thread will kill init if
on 4Mbyte machine without swap init is large 3 Mbytes and you execute
On Mon, Oct 09, 2000 at 12:30:20PM -0700, David Ford wrote:
Init should only get killed if it REALLY is taking a lot of memory. On a 4 or 8meg
Init should never get killed. Killing init can be compared to destroy the TCP
stack. Some app can keep to run right for some minute until they run
Ditto here -
Running 8139too drivers on 2.4.0-test9:
8139too Fast Ethernet driver 0.9.10 loaded
eth0: RealTek RTL8139 Fast Ethernet at 0xd1834000, 00:e0:7d:7b:5a:16,
IRQ 10
eth0: Identified 8139 chip type 'RTL-8139A'
eth1: RealTek RTL8139 Fast Ethernet at 0xd1836000, 00:e0:7d:7b:5a:1d,
IRQ 10
Ted,
Here are some corrections to the published list.
I'm working on new additions now.
~Randy
6. In Progress
* USB: hotplug (PNP) and module autoloader support
+ Move to "1. Should Be Fixed". We want more testing of it, of course.
9. To Do
* USB: OHCI root-hub-timer does
Andre,
Where's the patch for the CD RW/DVD fix you did over the weekend. I
need to grab it and see if I can get this drive working on speed=8 on
2.4.0.
Jeff
Andre Hedrick wrote:
On Mon, 9 Oct 2000, Rick Haines wrote:
I'm having real trouble mounting a dvd (udf filesystem) in my
Rik,
what do you think about the attached patch? It increases the effective
priority of a (kernel-) killed process, and initiates a reschedule, so
that it gets selected ASAP. (except if there are RT processes around.)
This should make OOM decisions 'visible' much more quickly.
Ingo
301 - 400 of 528 matches
Mail list logo
