-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
I just wanted to let everyone know that we have changed the
cryptographic key for the Linux Kernel Archives. The reason is that
the original key was generated with an expiration date, and
unfortunately it appears that too much software
On Mon, 9 Oct 2000, Kurt Garloff wrote:
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
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 or init has a memleak
you'll notice both problems regardless of having a magic for init
On Tue, Oct 10, 2000 at 12:14:11AM -0700, James Simmons wrote:
This patch fixes a minor config error for drivers/usb/Config.in. When you
select USB Human Interface Device (HID) support I assume you should be
able to select a USB mouse and/or USB keyboard. With the current Config.in
you
Also I need to adjust the rules for "ignore byte93" because the the
various methods that are being supported.
On Tue, 10 Oct 2000, Vojtech Pavlik wrote:
Try the "ignore byte93" option in the IDE menu. The IBM doesn't try to
do UDMA66 because the ZIP drive kills its 80-wire cable detection
On Tue, Oct 10, 2000 at 12:43:33AM -0700, Andre Hedrick wrote:
Also I need to adjust the rules for "ignore byte93" because the the
various methods that are being supported.
Yes, it would be nice if we had some better guesses on whether to think
the 80-wire cable is present. It would also be
On Tue, 10 Oct 2000, Vojtech Pavlik wrote:
On Tue, Oct 10, 2000 at 12:43:33AM -0700, Andre Hedrick wrote:
Also I need to adjust the rules for "ignore byte93" because the the
various methods that are being supported.
Yes, it would be nice if we had some better guesses on whether to
tvaudio: TV audio decoder + audio/video mux driver
tvaudio: known chips:
tda9840,tda9873h,tda9850,tda9855,tea6300,tea6420,tda8425,pic16c54
(PV951)
bttv: driver version 0.7.44 loaded
bttv: using 2 buffers with 2080k (4160k total) for capture
bttv: Bt8xx card found (0).
bttv0: Bt848 (rev 18) at
On Tue, Oct 10, 2000 at 01:10:06AM -0700, Andre Hedrick wrote:
These are two different issues.
One is host side detection and the other is drive side
detection/acknowledgement.
ide0=ata66 overrides the host-rules
ivb-byte93 overrides the mixed drive side rules.
The only think that is
Alan Cox wrote:
- Fix the megaraid (revert if need be)
is this the source of repeated "Blocked mailbox..!!" messages which
cause lock-ups on three Dell PowerEdge 2450s we have with AMI MegaRaid
Enterprise 1500 controllers in them?
Rob
--
Robert Brooks,Systems Manager,
Working our way up, Pete noticed that _sparc_free_io() wasn't aligning
plen properly... problem solved.
While we were there, we noticed a few more problems in the file (misuse
of a #define, and poor renaming of copied code).
At this point, the dbri driver is properly loadable and
Linus Torvalds wrote:
You can also still do the stack pointer plaything by just using
indirection: and when you context switch you switch the pointer around at
the base of the per-cpu interrupt stack.
Indirection, à la "current = *(stack ~8191)" might not be a bad idea
in general. As Ralf
important here (and it could just be a simple configuration error.)
Still, unless I'm mistaken, isn't an 8259A a UART, which should be related
to the serial port? Seems odd it would show up on IRQ 7...
8259A is the interrupt controller on a PC. (A pair of them actually). They
raise IRQ 7 if
Albert D. Cahalan wrote:
X, and any other big friendly processes, could participate in
memory balancing operations. X could be made to clean out a
font cache when the kernel signals that memory is low. When
the situation becomes serious, X could just mmap /dev/zero over
top of the background
Alan Cox wrote:
- Fix the megaraid (revert if need be)
is this the source of repeated "Blocked mailbox..!!" messages which
cause lock-ups on three Dell PowerEdge 2450s we have with AMI MegaRaid
Enterprise 1500 controllers in them?
The current 2.2.18pre does this with certain specific
Linus Torvalds wrote:
You can also still do the stack pointer plaything by just using
indirection: and when you context switch you switch the pointer around =
at
the base of the per-cpu interrupt stack.
Indirection, =E0 la "current =3D *(stack ~8191)" might not be a bad ide=
a
in
Andreas Dilger wrote:
Having a SIGDANGER handler is good for 2 reasons:
1) Lets processes know when memory is short so they can free needless cache.
2) Mark process with a SIGDANGER handler as "more important" than those
without. Most people won't care about this, but init, and X, and
--On 09 October 2000, 17:40 -0300 Rik van Riel [EMAIL PROTECTED]
wrote:
On Mon, 9 Oct 2000, James Sutherland wrote:
On Mon, 9 Oct 2000, Ingo Molnar wrote:
On Mon, 9 Oct 2000, Rik van Riel wrote:
so dns helper is killed first, then netscape. (my idea might not
make sense though.)
Date:Tue, 10 Oct 2000 10:54:11 +0100 (BST)
From: Alan Cox [EMAIL PROTECTED]
Having the stacks aligned also isnt good for the caches. If you are
bored some time instrument the cache lines that wake_up() touches
on a wake. Its very common to see most of them being on the
On Tue, Oct 10, 2000 at 11:17:31AM +0200, Markus Pfeiffer wrote:
Vojtech Pavlik wrote:
On Tue, Oct 10, 2000 at 12:43:33AM -0700, Andre Hedrick wrote:
Btw, reading the ATA/ATAPI-6 specs I think UDMA66 should work on a
setup where would be just one drive and a really short, 40-wire cable
On Tue, Oct 10, 2000 at 04:27:04AM -0500, Jordan wrote:
I have tried moving the Kenwood CDROM and the Zip between channels and
this works well. I would get rid of the zip if it was a viable option
but need it to do transfers, and the IBM has a real UDMA 66 cable and
upto ATA 100 capability
On Tue, Oct 10, 2000 at 11:52:33AM +0200, Matthias Andree wrote:
On Mon, 02 Oct 2000, Alan Cox announced:
2.2.18pre15
I'd like to know if there are any issues with the current dc390-2.0e or
2.0e3 drivers that prevent its inclusion/that prevent Kurt from
submitting it for inclusion. As per
On Thu, Oct 05, 2000 at 06:01:32AM -0500, Gnea wrote:
So here's the scoop:
I'm putting together this system for my sister to dual-boot Linux
(debian) and Windows 98. Originally, I had an IBM 1.7gig ata33 hard
drive in there, and everything worked fine. Then she decided she
wanted to have
I already pointed this out :-). Its not only write caching (dev null doesnt
write at all)
I think its read caching (read ahead)
Cheers
Markus
"Mike A. Harris" wrote:
On Mon, 9 Oct 2000, blizbor wrote:
On Mon, 9 Oct 2000, Andre Tomt wrote:
The fastest ATA drives out that are not public
hi all,
given struct netdevice for any pci network device, is there any way to get
corresponding
"struct pci_dev".
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Tue, Oct 10, 2000 at 04:44:40PM +0530, [EMAIL PROTECTED] wrote:
hi all,
given struct netdevice for any pci network device, is there any way to get
corresponding
"struct pci_dev".
No.
--
Vojtech Pavlik
SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Andries Brouwer wrote:
On Mon, Oct 09, 2000 at 04:37:38PM +, Zdenek Kabelac wrote:
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 removable disk sda at scsi0,
channel
Oct 9 16:57:24 dual kernel:
I am currently booted into a 2.4.0-test10-pre1 kernel with two
modifications, the VIA 3.6 drivers you have provided and the Patch from
Andre that you sent. My IBM is the primary master with the zip as its
slave and the Kenwood is the secondary master with the Plextor as its
slave. Here is my
Hi!
Ok, that means Andre's patch works. Congrats, Andre! Now, could you send
me 'hdparm -i /dev/hdb' for the ZIP? It seems to be in SWDMA0 mode,
which is interesting, because I thought it can't do that. You probably
have some newer model.
Do all your drives work correctly now?
Thanks for your
echo "0" /proc/sys/net/ipv4/tcp_ecn
Yes, Cisco does know about the bug in their product.
Later,
David S. Miller
[EMAIL PROTECTED]
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
hi all,
given struct netdevice for any pci network device, is there any way to
get
corresponding
"struct pci_dev".
No.
Not directly, but pci_dev knows about netdevice, so you can scan the
pci_dev's
to find a match with the required netdevice. (Or do a similar match search
on base_addr)
Based of my measurement on i386 smp configuration,
If a system has plenty of runnable tasks, schedule() produces
noticable amount of cache misses at runqueue-head traversing and the
goodness calculations.
David S. Miller writes:
Some of us actually have instrumented it :-) I added a coloring
"Phillips, Mike" wrote:
hi all,
given struct netdevice for any pci network device, is there any way to
get
corresponding
"struct pci_dev".
No.
Not directly, but pci_dev knows about netdevice, so you can scan the
pci_dev's
to find a match with the required netdevice
Or really?
On Mon, 9 Oct 2000, Daniel Lange wrote:
Periodically, I get the following error with the 2.4.0test9 kernel:
spurious 8259A interrupt: IRQ7.
[SNIPPED...]
This will sometimes happen with the 8259A and really should not even
be logged. There is a default handler for all interrupts. If this
[EMAIL PROTECTED] wrote:
3. Security
* Fix module remove race bug (still to be done: TTY, ldisc, I2C,
video_device - Al Viro) (Rogier Wolff will handle ATM)
Patch for tty and ldisc is in your inbox...
...
8. Fix Exists But Isnt Merged
...
* Many network device
Hi There!
1.: SCSI lock-up when scanning with SNAPSCAN1236
2.:
I have an AGFA SNAP-scan 1236S and used it with the kernel
2.2.16 and with the new beta-test-kernel 2.4.0-test9.
The SCSI-Controller is a aha152x and is working fine with
the 2.2.16 kernel except that there is an error message from
On Mon, 9 Oct 2000, Linus Torvalds wrote:
On Mon, 9 Oct 2000, Rik van Riel wrote:
I'd prefer just X having a higher "mm nice level" or something.
Which it has, because:
1) CAP_RAW_IO
2) p-euid == 0
Oh, I agree, but we might want to generalize this a bit so that root could
Andi Kleen wrote:
On Fri, Oct 06, 2000 at 10:00:36PM +1100, Andrew Morton wrote:
The little-low-latency patch for test9 is at
http://www.uow.edu.au/~andrewm/linux/2.4.0-test9-low-latency.patch
Notes:
- It now passes Benno's tests with 50% headroom (thanks to
Ingo's
Hi Andrew,
Take a look at the olympic driver (drivers/net/tokenring/olympic.c)
function olympic_proc_info. This is called from a read into the proc
filesystem. When we get the read we want to print out details on
all the olympic devices in the system so we have to scan the
pci tree and find a
"Jeff V. Merkey" wrote:
"Jeff V. Merkey" wrote:
"David S. Miller" wrote:
Date:Tue, 10 Oct 2000 00:44:58 +0200
From: "Andi Kleen" [EMAIL PROTECTED]
On Mon, Oct 09, 2000 at 11:41:13PM +0100, Alan Cox wrote:
I dont actually know a CPU that doesnt have
Oops.. sorry for the typo. The server in question is running linux-2.2.16
tarball from ftp.kernel.org instead of 2.2.17 .
Thanks!
- Forwarded message from [EMAIL PROTECTED] -
Date: Tue, 10 Oct 2000 21:28:14 +0800 (SGT)
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Subject:
I have problem with Matrox G400 framebuffer. After turn
on computer, kernel freez durning boot with snow on my monitor.
When I start it with options video=matrox:disbled, and run XFree86
4.0.1 with official drivers from Matrox web page, and reboot my
computer again - everything works fine.
From
On Tue, Oct 10, 2000 at 04:38:02AM +0100, Philipp Rumpf wrote:
Init should never die. If we get to do_exit in init we'll panic which is
the right thing to do (reboot on critical systems).
If the page fault can fail with OOM on init, init will get a SIGSEGV while
running a signal handler
Hi Linus, hi Alan,
I'd like to get some driver included into the mainstream kernels.
The driver is a new high-level SCSI driver, which was derived from the
standard st driver. It drives the OnStream tape drives SC-30/50 (SCSI) and
DI-30 (IDE, via ide-scsi) and USB-30 (USB, via usb-storage). The
I tried the patch, but the result is the same... Uncompressing Linux...,
now booting the kernel..., NOTHING
These Winchips need all the help they can get, so if you know something
else I might try...
Ok, I've narrowed it down to the changes to mtrr.c in test8
Looks like the Cyrix III
Hi,
First some explanation. Most cryption algorithms initialize
the cryption process with some init values, called IV (by me :-).
This means that two identical clear messages will give
different encrypted messages, if different IVs are used.
The loop device supports different IVs;
the IVs are
On Tue, Oct 10, 2000 at 09:06:49AM +0200, Helge Hafting wrote:
If you want init to live - prove that it don't eat too much memory.
I don't see why the machine should be stable only if init is small.
My kernel won't be stable only if init is small since it doesn't cost
anything to handle
Linus Torvalds wrote:
Basically, the only thing _I_ think X can do is to really say "oh, please
don't count my memory, because everything I do I do for my clients, not
for myself".
THAT is my argument. Basically there is nothing we can reliably account.
So we might as well fall back on
(There is a second generation drive, ADR-x0, which has a much more advanced
firmware and does fully comply with SCSI-2 spec, BTW.)
'fully'? Not.
This latter drive has had problems too, but it seems to me that the arrival of
the ADR-50 should preclude the need to support the ADR-30.
-
To
Hi...
I _hate_ to do this, but I couldn't find (except for a reference to
"others who have segfaults using glibc") no reference to this problem.
Insmod of i2c, videodev and bttv succeed without problems or any message
in /var/log/debug, messages or syslog.
Also, though I'm surely no expert,
On Tue, 10 Oct 2000, Philipp Rumpf wrote:
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 a task that grows over 1M.
This sounds suspiciously like the description of a DEAD system ;)
But
[OOM killer war]
Hi there,
before you argue endlessly about the "Right OOM Killer (TM)", I
did a small patch to allow replacing the OOM killer at runtime.
You can even use modules, if you are careful (see khttpd on how
to do this without refcouting).
So now you can stop arguing about the one
Doesn't work for all devices. Also since base_addr is truncated to
16-bits when passed to ifconfig, this gets even nastier for userspace.
You do the best you can with what's available :)
...and noone but the driver can trust this information to be pointing to
an up-to-date struct
On Tue, 10 Oct 2000, Philipp Rumpf wrote:
On Tue, Oct 10, 2000 at 12:06:07PM -0300, Rik van Riel wrote:
On Tue, 10 Oct 2000, Philipp Rumpf wrote:
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
On Tue, 10 Oct 2000, Ingo Oeser wrote:
before you argue endlessly about the "Right OOM Killer (TM)", I
did a small patch to allow replacing the OOM killer at runtime.
So now you can stop arguing about the one and only OOM killer,
implement it, provide it as module and get back to the
On Tue, Oct 10, 2000 at 07:21:05AM -0500, Jordan wrote:
Everything is working great! I can access my hard drive quickly, both
CD drives are working and I can read and write to my zip as a
partitioned drive or as a block device for Tar archives. Thanks for all
of the help.
Great. Thanks
On Tue, Oct 10, 2000 at 12:30:51PM -0300, Rik van Riel wrote:
Not killing init when we "should" definately prevents
embedded systems from auto-rebooting when they should
do so.
(OTOH, I don't think embedded systems will run into
this OOM issue too much)
but when they do, they're hard to
On Tue, Oct 10, 2000 at 12:32:50PM -0300, Rik van Riel wrote:
So now you can stop arguing about the one and only OOM killer,
implement it, provide it as module and get back to the important
stuff ;-)
This is definately a cool toy for people who have doubts
that my OOM killer will do the
Kurt Garloff wrote:
Actually, 2.0e3 did include one rather important fix which solved the
trouble: Some devices get upset, when the driver tries to negotiate sync
(or wide) connections, but the device actually does not support it.
So, the driver now waits for the first INQUIRY result and
Hi,
While trying 2.4.0-test10-pre1 on my Sun4m SparcSystem600, i'm getting an
error during 'make dep' ;((
I don't know anything about assembly, so there I can't help, but here's
the output:
galaxy:/usr/src/kernel-source-2.4-0-test10-pre1# make dep
make -C arch/sparc/kernel check_asm
make[1]:
Hi,
I want to setup RAID.
I am working on kernel version 2.2.12.
I am using RAID patches available.
I create a RAID configuring file called
/etc/raidtab
#mkraid /dev/md0/*md0 is the device I am
selecting*/
After this when I check /proc/mdstat , I find
On Tue, Oct 10, 2000 at 12:20:07PM -0400, Mark Hahn wrote:
Btw, reading the ATA/ATAPI-6 specs I think UDMA66 should work on a
setup where would be just one drive and a really short, 40-wire cable
without problems as well. I've even seen systems shipped like that.
uh, what part of the
In article [EMAIL PROTECTED],
Jamie Lokier [EMAIL PROTECTED] wrote:
Linus Torvalds wrote:
You can also still do the stack pointer plaything by just using
indirection: and when you context switch you switch the pointer around at
the base of the per-cpu interrupt stack.
Indirection, à la
On Tue, 10 Oct 2000, Jamie Lokier wrote:
The assembler doesn't use nops for alignment -- it inserts longer
instructions that are effectively nops, either 1 or two. For larger
stretches, the assembler inserts a jmp itself for alignment.
Note that some of them are not very good no-ops. At
On Mon, 9 Oct 2000, Byron Stanoszek wrote:
it also might be good to have options to kill anything connected to a pty
first, and to not kill anything attatched to the console. obviously these
leave ways for admins to shoot themselves in the foot, but they could be
useful.
I _had_
On Tue, 10 Oct 2000, Rogier Wolff wrote:
So if Netscape can "pump" 40 extra megabytes of memory out of X, this
can be exploited.
Now we're back to the point that a heuristic can never be right all
the time..
I agree. In fact, we never left that.
Nothing is perfect.
In fact, a
Linus Torvalds wrote:
The assembler doesn't use nops for alignment -- it inserts longer
instructions that are effectively nops, either 1 or two. For larger
stretches, the assembler inserts a jmp itself for alignment.
Note that some of them are not very good no-ops. At least at some
On Thu, 28 Sep 2000, Ivan Passos wrote:
In order to get the configuration of a board, I have to send, from
userspace, an ioctl to the driver and wait for the board to complete its
action. The way this is implemented is as follows:
- In the ioctl, the driver sends a command to the board and
I cannot verify this signature with gpg or pgp. gpg says
gpg: invalid radix64 character 00 skipped
gpg: Signature made Tue Oct 10 08:26:46 2000 MEST using DSA key ID 2BCBC621
gpg: BAD signature from "H. Peter Anvin (hpa) [EMAIL PROTECTED]"
Walter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dave,
This patch fixed the problems, for now. The system now boots OK, and seems to
run OK (have not hit it very hard yet since it currently runs without a
heatsink). Tnanks...
Cheers//Frank
--
W ___
## o o\/ Frank de Lange \
}# \| /
Either you forgot to attach the patch for it was bigger than 40K.
On Tue, 10 Oct 2000, Frank de Lange wrote:
Dave,
This patch fixed the problems, for now. The system now boots OK, and seems to
run OK (have not hit it very hard yet since it currently runs without a
heatsink). Tnanks...
James,
The patch I referred to can be found in Dave's message... I gave him some
feedback on the problems with Winchips...
Cheers//Frank
--
W ___
## o o\/ Frank de Lange \
}# \| / \
##---# _/ Hacker for Hire \
In article [EMAIL PROTECTED],
Ivan Passos [EMAIL PROTECTED] wrote:
"You could use a semaphore for this. Initialize it to 0, then call
down() from the ioctl, and up() from the interrupt handler. If the
up() happens before the down(), the down() won't go to sleep."
Initializing it to 0 means:
http://www.osopinion.com/Opinions/MontyManley/MontyManley15.html
good article, several unfortunate truths within.
-Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco Network Administrator/Engineer
[EMAIL PROTECTED]
bttv0: model: BT848A( *** UNKNOWN *** ) [autodetected]
How about fixing this first? The card list knows about a few
cards where it better should'nt load the msp3400 driver...
i2c-dev.o: Registered 'bt848 #0' as minor 0
msp34xx: I/O error #1 (read 0x12/0x1e)
msp34xx: I/O error #2 (read
Yet more followup with myself I can reproduce this problem on
2.4.0-test10-pre1 every time. I'm using the ide-scsi and usb-storage
modules to trigger the bug -- loading and then unloading either one causes
/proc/scsi to not be cleaned up properly.
As yet, nobody has indicated to me that
Olaf Titz wrote:
Still, it would be nice to recover that 4 MB when the system
doesn't have any memory left.
Yup. The X server could give back the memory for some cases like the
background without too much hackery.
Then Linux only needs to implement SIGDANGER, which has been talked
Sorry if you get multiple copies of this--I have tried sending twice
already and have yet to see it on the kernel-list.
Jordan
Here are hdparms for all my devices--
`hdparm -i /dev/hda` IBM Deskstar 7200 RPM:
/dev/hda:
Model=IBM-DTLA-307075, FwRev=TXAOA50C, SerialNo=YS0YSF3Z455
Config={
On Tue, Oct 10, 2000 at 01:42:51PM -0400, Mark Hahn wrote:
Btw, reading the ATA/ATAPI-6 specs I think UDMA66 should work on a
setup where would be just one drive and a really short, 40-wire cable
without problems as well. I've even seen systems shipped like that.
uh, what part
My first contribution to kernel =) Someone please look over this one
carefully =)
Thanks
--- vgacon.c.bakTue Oct 10 13:50:09 2000
+++ vgacon.cTue Oct 10 14:48:06 2000
@@ -27,6 +27,9 @@
* flashing on RHS of screen during heavy console scrolling .
* Oct 1996, Paul
On Tue, Oct 10, 2000 at 12:32:50PM -0300, Rik van Riel wrote:
On Tue, 10 Oct 2000, Ingo Oeser wrote:
before you argue endlessly about the "Right OOM Killer (TM)", I
did a small patch to allow replacing the OOM killer at runtime.
So now you can stop arguing about the one and only OOM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It seems that there was some mangling problems going on with the
message I sent last night, so I wanted to try to re-send it with a
proper signature this time...
Hi everyone,
I just wanted to let everyone know that we have changed the
Karim,
I've been back through an initial evaluation we did for LTT, back in May.
One of the feature we highlighted we'd like to see was an ability to
specify custom formatting templates. Our original OS/2 trace facility
allowed the user to generate formatting templates which would specify
On Tue, Oct 10, 2000 at 02:08:45PM -0400, [EMAIL PROTECTED] wrote:
I am one of those people that uses PCMCIA on an SMP machine, I also
use 2.4. Aside from the very occasional problem, I don't see any
locking issues. Is it possible to just leave it as is with a warning?
I think the
Hi all
Has anyone tried testing CBQ with 2.3.99 pre2 kernel. I tried to set up
CBQ on an ATM interface and was not able to notice any differentiation or
treatment to packets even when I use 'bounded' with the tc commands.
I tried to test it with a 2.2.10 kernel using ds-8 and appropriate tc,
And I suggest this addition (cfr. the other fbcon-*.c since 2.4.0-test5-pre5):
Done. I have alot more big changes coming :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
On Mon, 9 Oct 2000 [EMAIL PROTECTED] wrote:
2. Capable Of Corrupting Your FS/data
* Non-atomic page-map operations can cause loss of dirty bit on
pages (sct, alan)
Is anybody looking into fixing this bug ?
9. To Do
* mm-rss is modified in some places without holding
On Tue, 10 Oct 2000, Tom Rini wrote:
On Tue, Oct 10, 2000 at 12:32:50PM -0300, Rik van Riel wrote:
On Tue, 10 Oct 2000, Ingo Oeser wrote:
before you argue endlessly about the "Right OOM Killer (TM)", I
did a small patch to allow replacing the OOM killer at runtime.
So now you
2.2.18pre15 defines udelay as (in file include/asm-i386/delay.h) :
...
extern void __bad_udelay(void);
...
#define udelay(n) (__builtin_constant_p(n) ? \
((n) 2 ? __bad_udelay() : __const_udelay((n) *
0x10c6ul)) : \
__udelay(n))
...
It seems __bad_udelay is not
Marcelo Tosatti [EMAIL PROTECTED] writes:
2.2.18pre15 defines udelay as (in file include/asm-i386/delay.h) :
...
extern void __bad_udelay(void);
...
#define udelay(n) (__builtin_constant_p(n) ? \
((n) 2 ? __bad_udelay() : __const_udelay((n) *
0x10c6ul)) : \
Hi,
Finally got around to trying out 2.4.0test9. I'm going to do some VM
performance comparisons (incidentally because VM should be a carefully
measured science not random cool idea of the day which we have seen too
much of recently).
Unfortunately, I can't start fair tests yet because UDMA3
On Mon, Aug 14, 2000 at 11:55:13PM +0100, Athanasius wrote:
I'm on 2.2.17pre13 (not the latest I know, I need to sort out
compiling latest and a reboot), my Mitsumi CR-4804TE CD-R/RW drive seems
to work happily enough with xcdroast to write one disk, but then goes
into super sulk mode,
On Tue, Oct 10, 2000 at 06:10:48PM -0700, James Simmons wrote:
Dave,
This patch fixed the problems, for now. The system now boots OK, and seems to
run OK (have not hit it very hard yet since it currently runs without a
heatsink). Tnanks...
Cheers//Frank
Oops... looks like I was
On Tue, 10 Oct 2000, Kurt Garloff wrote:
Actually, 2.0e3 did include one rather important fix which solved the
Uh. Fix? This sounds like working around very broken devices to me, or
are devices allowed to wreak havoc if sync negotiation is tried in spite
of not being advertised in inquiry
Basically you have drive that caught in the word93 rules change.
However, the error you got were real and the kernel did properly respeed
the drive to one step slower. The problem above prevented you from going
from ATA66 to ATA44, thus you fell to ATA33.
You RHS 7.0 kernel does not have all
On Tue, 10 Oct 2000, Andre Hedrick wrote:
Basically you have drive that caught in the word93 rules change.
However, the error you got were real and the kernel did properly respeed
the drive to one step slower. The problem above prevented you from going
from ATA66 to ATA44, thus you fell
Not directly, but pci_dev knows about netdevice, so you can scan the
pci_dev's
to find a match with the required netdevice. (Or do a similar match search
on base_addr)
Not I suspect reliably.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Initializing CPU#0
You are using a SMP kernel on a `386 UP machine. That tends to make
these burps show up. It is harmless, though.
It says this either way
Console: colour VGA+ 80x25
Calibrating delay loop... 3.10 BogoMIPS
This shows something I don't understand. Either the counter
Ok, I've narrowed it down to the changes to mtrr.c in test8
Looks like the Cyrix III changes broke things.
Didn't something similar happen when these changes made it into
a 2.2.18pre ? Alan?
2.2.18pre12 or so had a bug with Winchip but its fixed in pre15 I believe,
at least my winchip is
Also set this option "CONFIG_IDEDMA_IVB" because you are in the
transistion period of drive manufacturing.
On Tue, 10 Oct 2000, Chris Evans wrote:
On Tue, 10 Oct 2000, Andre Hedrick wrote:
Basically you have drive that caught in the word93 rules change.
However, the error you got
1 - 100 of 320 matches
Mail list logo
