Duh, mea stupida. I misread your message. You're trying to get
the Promise IDE working at 100, no? My Asus A7V133 has the 686b
which does ATA100 without having to rely on the Promise chipset,
and that seems to work fine. But if it helps to know, I've got an
A7V with the 686a and I use the
On Wed, Apr 18, 2001 at 02:34:05PM -0400, Ben Pfaff wrote:
Jani Monoses [EMAIL PROTECTED] writes:
does the atyfb or aty128fb support this chip?
Device id of 4c4d.
Using 2.4.3-ac7.
I have a Rage Mobility with the same device ID on my laptop
(Compaq Armada M700) but haven't been
On Wed, Apr 18, 2001 at 10:21:53PM -0400, Manuel Ignacio Monge Garcia wrote:
El Mi 18 Abr 2001 15:16, escribiste:
I don't know about other possible problems with the kernel, but you must
use an 80 wire IDE cable for UDMA66/100 to work.
---Primary IDE---Secondary
I was wondering whether the swsusp work might form a useful basis
for the eventual ACPI implementation of the to-disk hibernation
stuff:
I (and others) have looked at it. It's a pretty cool patch, but it
really isn't the right way to do things.
swsusp is most definitely the
Hmm...
I already started (long ago, and abandoned since due to lack of time :-( )
down another path; I'd like to resurrect it...
My lightweight-semaphores were actually even simpler in userspace:
* the userspace struct was just a signed count and a file handle.
* Uncontended case is exactly like
Right, so I'll check what eject(1) does. It might eject the disk even if it
failed to unmount.
It shouldn't be able to. But check and see what happens.
(1) There are many different programs all called eject(1).
I find at least four of them on this machine.
(2) I missed the start of
On Thu, Apr 19, 2001 at 07:49:45AM +0800, Andrew Chan wrote:
Greetings,
I am running a relaying sendmail box and I would like it to be able to
handle up to 600 or so concurrent (incoming or outgoing) connections.
I tried that and discovered that TONS of incoming connections are stuck at
On Wed, 18 Apr 2001, TroyBenjegerdes wrote:
Well, on kernel 2.2.19 on a 'regular' PC box (celeron 533), it works
better than the 1.07b version from scyld.com, but it still gets tripped up
pretty bad by nfs traffic. (Have you tried NFS on your board at all?). It
Not tried NFS yet...
Jeremy Jackson wrote:
currently all the kernel's heuristics are feed-back control loops.
what you are asking for is a feed-forward system: a way for the application
to tell kernel "I'm only reading this once, so after I'm done, throw it out
straight away"
and "I'm only writing this data, so
This was originally a private reply to Patrick Mochel, but the e-mail
kept getting longer and longer :)
The current state of PCI PM is this:
pci_enable_device (1) enables IO and mem decoding, (2) assigns/routes
the PCI IRQ, and (3) brings the device to D0 using pci_set_power_state.
Linus
Hi List(s)
For a firewall setup I need to know in which range applications like
rsh, or better yet the rresvport() libc function allocate reserved ports.
Do I have to expect ports in the whole 1..1024 range (maybe omitting those
already in use by other servers) or is only a limited range used
Alon Ziv wrote:
Hmm...
I already started (long ago, and abandoned since due to lack of time :-( )
down another path; I'd like to resurrect it...
My lightweight-semaphores were actually even simpler in userspace:
* the userspace struct was just a signed count and a file handle.
*
On Thu, Apr 19, 2001 at 10:20:48AM +0200, Alon Ziv wrote:
My lightweight-semaphores were actually even simpler in userspace:
* the userspace struct was just a signed count and a file handle.
* Uncontended case is exactly like Linus' version (i.e., down() is decl +
js, up() is incl()).
* The
On Thu, 19 Apr 2001, Abramo Bagnara wrote:
Alon Ziv wrote:
Hmm...
I already started (long ago, and abandoned since due to lack of time :-( )
down another path; I'd like to resurrect it...
My lightweight-semaphores were actually even simpler in userspace:
* the userspace struct
hello,all.now i'm completely confused with the meaning of
some system limits on kernel 2.4.3.there are three main
limits that i concern:NR_OPEN,NR_FILE,and OPEN_MAX.i didn't
find NR_INODE anywhere.is that due to the change of the
allocation mechanism of inodes?in limits.h of the source file
of
Hi ! Glad to see things moving around Power Management ;)
This was originally a private reply to Patrick Mochel, but the e-mail
kept getting longer and longer :)
Note: we have setup a list for PM issues
http://lists.sourceforge.net/lists/listinfo/linux-pm-devel
Not very much used yet, but I,
Hi ! Glad to see things moving around Power Management ;)
This was originally a private reply to Patrick Mochel, but the e-mail
kept getting longer and longer :)
Note: we have setup a list for PM issues
http://lists.sourceforge.net/lists/listinfo/linux-pm-devel
Not very much used yet, but I,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
"Grover, Andrew" writes:
| I don't think I understand that first sentence. (Let me respond anyways ;-)
Doh! Sorry, what I meant was that (if I'm understanding this right!)
the AML interpreter being
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
(cc'd to the acpi list, where people have also been talking about
this recently...)
Ookhoi writes:
| I tried swsusp on my vaio (also a c1ve :-) and it didn't work because it
| (said it) couldn't stop
On Thu, Apr 19, 2001 at 11:19:31AM +0100, Benjamin Herrenschmidt wrote:
Hi ! Glad to see things moving around Power Management ;)
This was originally a private reply to Patrick Mochel, but the e-mail
kept getting longer and longer :)
Note: we have setup a list for PM issues
Sorry to repeat .. I didn't see this go out on the list and I haven't
had any reply. So let's ask again. Is this a new coding error in ll_rw_blk?
-
The following has been lost from __make_request() in ll_rw_blk.c since
2.4.2 (incl):
out:
- if (!q-plugged)
-
Alexander Viro wrote:
I suspect that simple pipe with would be sufficient to handle contention
case - nothing fancy needed (read when you need to block, write upon up()
when you have contenders)
Would something along the lines of (inline as needed, etc.)
down:
lock decl count
Martin Hamilton wrote:
FWIW, I didn't have any luck with the 2.4.3 swsusp-v8pre3 patch - my
C1VE suspended to disk, but on re-reading the memory image from swap
space the machine reset and we were back to the LILO prompt fsck.
I can confirm Martin's experience, I got the same results.
Akos
On Thu, Apr 19 2001, Peter T. Breuer wrote:
Sorry to repeat .. I didn't see this go out on the list and I haven't
had any reply. So let's ask again. Is this a new coding error in ll_rw_blk?
-
The following has been lost from __make_request() in ll_rw_blk.c since
2.4.2
Hello,
True, I plead guilty to the "replying at 3:30am" sin. :-) I meant to reply
to Roberto's mail, and accidentally replied to yours..
That's what I thought ...
Anyway, Roberto, if you could give the starfire driver in 2.2.19 a try,
I'd appreciate it. You mentioned looking at the code,
Rik van Riel wrote:
On Thu, 19 Apr 2001, Daniel Phillips wrote:
Jan Harkes wrote:
On Thu, Apr 19, 2001 at 02:27:48AM +0200, Daniel Phillips wrote:
more memory. If you have enough memory, the inode cache won't thrash,
and even when it does, it does so gracefully - performance falls
Thanks for your answer, and I still have some questions.
(private)(masquerade)(public)
If I ping public host from private host using this command:
ping 140.113.1.1
What trigger ICMP message? The "ping" binary program?
AND
How masquerade gateway know the original packet port information?
Rik van Riel wrote:
On Thu, 19 Apr 2001, Daniel Phillips wrote:
OK, now I know what's happening, the next question is, what should be
dones about it. If anything.
[ discovered by alexey on #kernelnewbies ]
One thing we should do is make sure the buffer cache code sets
the
OK .. thanks Jens. Sorry about the repeat .. my nameserver lost its fix
on the root servers thanks to some hurried upgrades, and sendmail
started quietly bouncing mail for "not having" a dns entry, and you
know about deja. Probably the list dropped me for the bounces.
Those are my excuses.
Support for DS1302 is available in the CRIS port.
A patch for 2.4.3 (and a lot of other stuff you don't need) is available in
http://developer.axis.com/download/devboard_lx/R1_0_0/
/Johan
- Original Message -
From: Grant Erickson [EMAIL PROTECTED]
To: Linux I2C Mailing List [EMAIL
I tested my systems to try to reproduce the recently reported SCSI
tape corruptions. I did not find any errors, the tape works OK.
Linux version 2.4.3 (olaf@bigred) (gcc version 2.95.2 2220 (Debian GNU/Linux)) #1
Sat Mar 31 11:51:54 CEST 2001
K6-III-400, 96MB
NCR53C815 SCSI controller
HP
Hello all,
I have read on lwn.net that the patch that makes children run first after
a fork has been integrated in the latest pre-kernel.
I am a little bit concerned by that, as I have begun to write a program
that monitors process using ptrace. The difficulty is to ptrace-attach
the child in a
Hi,
I'm trying to set up a PC with two (gig)ether cards as a test system in
which a router/firewall/what have you/ could be inserted between the two
ether cards. Then I want to send various lumps of test traffic between
the two.
Unfortunatly Linux is being a little too helpful - whatever the
Hi Jens,
I applied your patch to 2.4.4-pre4. It compiled fine, but crashed during
boot (just right after the IDE init) with
---
Uniform CD-ROM driver Revision: 3.12
Unable to handle kernel NULL pointer dereference at virtual address
printing eip: ...
Oops:
...
I've compiled 2.4.3-ac9 with support for PNP BIOS. I understand that this
is a new feature experimental and the feedback is requested.
Thanks
The setting is BIOS is to use irq 7 and dma 3. I normally use "options
parport_pc io=0x378 irq=7 dma=3" in /etc/modules.conf, but this time I
On Wed, 18 Apr 2001, Rik van Riel wrote:
One thing we should do is make sure the buffer cache code sets
the referenced bit on pages, so we don't recycle buffer cache
pages early.
This should leave more space for the buffercache and lead to us
reclaiming the (now unused) space in the
On Thu, Apr 19 2001, Stefan Jaschke wrote:
Hi Jens,
I applied your patch to 2.4.4-pre4. It compiled fine, but crashed during
boot (just right after the IDE init) with
---
Uniform CD-ROM driver Revision: 3.12
Unable to handle kernel NULL pointer dereference at virtual
My lightweight-semaphores were actually even simpler in userspace:
* the userspace struct was just a signed count and a file handle.
* Uncontended case is exactly like Linus' version (i.e., down() is decl +
js, up() is incl()).
* The contention syscall was (in my implementation) an ioctl on
On Thu, Apr 19 2001, Peter T. Breuer wrote:
Besides, the above hunk was removed because it is wrong. For devices
using plugging, we would re-call the request_fn while the device was
already active and serving requests. Not only is this a performance hit
Not sure about that ...
It _is_
Erm... Folks, can -s_inode_size be not a power of 2? Both
libext2fs and kernel break in that case. Example:
dd if=/dev/zero of=foo bs=1024 count=20480
mkfs -I 192 foo
corrupts memory and segfaults. Reason: ext2_read_inode() (same problem
is present in the kernel version of said beast)
When I ran raw I/O SCSI read/write test with 2.4.1 kernel
on our IA64 8way SMP box, kernel paniced and following
message was displayed.
Aiee, killing interrupt handler!
No stack trace and register dump are displayed.
Then I analyze FSB traces around the panic, and found that
following
Hello all,
I have read on lwn.net that the patch that makes children run first after
a fork has been integrated in the latest pre-kernel.
I am a little bit concerned by that, as I have begun to write a program
that monitors process using ptrace. The difficulty is to ptrace-attach
the
[EMAIL PROTECTED] said:
IMHO an abstracted interface at this point is overengineering. Maybe
later it will make sense, though.
Absolutely not. It makes sense now. The abstracted interface is not required
just to combine the interface to APM and ACPI. What John said was
"ACPI != PM". Note
I applied your patch to 2.4.4-pre4. It compiled fine, but crashed during
boot (just right after the IDE init) with
This should fix it.
It boots now. But I still cannot read a DVD-RAM disk (same behavior
as before):
# strace dd of=/dev/null if=/dev/hdc bs=2k count=3
open("/dev/hdc",
On Thu, Apr 19, 2001 at 11:19:31AM +0100, Benjamin Herrenschmidt wrote:
Hi ! Glad to see things moving around Power Management ;)
This was originally a private reply to Patrick Mochel, but the e-mail
kept getting longer and longer :)
Note: we have setup a list for PM issues
Chris Wedgwood wrote:
On Wed, Apr 18, 2001 at 09:27:12PM -0500, Rico Tudor wrote:
Another problem area is ECC monitoring. I'm still waiting for
info from ServerWorks, and so is Dan Hollis. Alexander Stohr has
even submitted code to Jim Foster for approval, without evident
On Thu, Apr 19 2001, Stefan Jaschke wrote:
I applied your patch to 2.4.4-pre4. It compiled fine, but crashed during
boot (just right after the IDE init) with
This should fix it.
It boots now. But I still cannot read a DVD-RAM disk (same behavior
as before):
This is really strange,
On Wed, 18 Apr 2001, Scott Prader wrote:
the 'latest RAD toolkits' now THERE'S something decent worth quoting, I
hope you won't mind me doing so. :) So, going back to the above, and
again, let me know if i'm wrong here, you're saying that in order to
support a decent X server project, there
"A month of sundays ago Jens Axboe wrote:"
On Thu, Apr 19 2001, Peter T. Breuer wrote:
So the consensus is that I should enable plugging while the plugging
function is still here and do nothing when it goes? I must say I don't
think it should really "go", since that means I have to add a
On Thursday 19 April 2001 14:15, Jens Axboe wrote:
This is really strange, are you sure your drive is ok? Does mounting
dvd-rom and cd-rom's work fine?
OK. I'll check again with 2.4.4-pre4+patches:
(1) Mounting the SuSE DVD-ROM (-t iso9660) from /dev/hdc on /dvd and
reading from /dvd
When I ran raw I/O SCSI read/write test with 2.4.1 kernel
on our IA64 8way SMP box, kernel paniced and following
message was displayed.
Aiee, killing interrupt handler!
(1) Wait in rw_raw_dev() while io_count is positive.
Stephen submitted a chunk of raw i/o fixes which are in
In ens.mailing-lists.linux-kernel, you wrote:
It seems to me that what you really want is a fork option to create the
child in a suspended state.
Yes, or a clone option (using ptrace, I can always change on the fly
the fork system call into a clone system call and add whatever option I
- Some devices just can't be brought back to life from D3 state without
a PCI reset (ATI Rage M3 for example) and that require some arch specific
support (when it's possible at all).
Putting on a driver author hat what I want is
pci_power_on_generic
pci_power_off_generic
On Thu, Apr 19 2001, Stefan Jaschke wrote:
On Thursday 19 April 2001 14:15, Jens Axboe wrote:
This is really strange, are you sure your drive is ok? Does mounting
dvd-rom and cd-rom's work fine?
OK. I'll check again with 2.4.4-pre4+patches:
(1) Mounting the SuSE DVD-ROM (-t iso9660) from
"Jens Axboe wrote:"
Examine _why_ you don't want plugging. In 2.2, you would have to edit
the kernel manually to disable it for your device.
True. Except that I borrowed a major which already got that special
treatment.
For 2.4, as long as
there
Hello,
Anyway, Roberto, if you could give the starfire driver in 2.2.19 a try,
I'd appreciate it. You mentioned looking at the code, did you actually
test it?
Ok, I replaced the motherboard and did the remaining tests. Everything
looks fine up to 3 quadboards, 2 3c905C and one eepro100. The
- Some devices just can't be brought back to life from D3 state without
a PCI reset (ATI Rage M3 for example) and that require some arch specific
support (when it's possible at all).
Putting on a driver author hat what I want is
pci_power_on_generic
pci_power_off_generic
On 19 Apr 2001, Andreas Jaeger wrote:
ISO C demands that at process startup all FPU traps are masked. You
can set specific traps with the functions in fenv.h from the C
library, for details read the manual: info libc
Andreas
Thanks, this is what I needed. I guessed that there was
On Wed, Apr 18, 2001 at 10:49:01PM -0600, Andreas Dilger wrote:
However, I'm not sure that your reasoning for removing these is correct.
For example, one symbol that I saw was CONFIG_EXT2_CHECK, which is code
that used to be enabled in the kernel, but is currently #ifdef'd out with
the above
I'm getting strange Oopses with 2.2.17 on an AMD Athlon 1.2 GHz machine.
They all happen in about the same place in free_wait() called by
do_select(). I don't see a special pattern when I look at the failing
addresses, but then, I'm not a kernel expert...
The strange thing is that exactly this
On Thu, Apr 19 2001, Peter T. Breuer wrote:
"Jens Axboe wrote:"
Examine _why_ you don't want plugging. In 2.2, you would have to edit
the kernel manually to disable it for your device.
True. Except that I borrowed a major which already got that special
treatment.
Ok
Benjamin Herrenschmidt wrote:
- On SMP, we need some way to stop other CPUs in the scheduler
while running the last round of sleep (putting devices to sleep) at least
until all IO layers in Linux can properly handle blocking of IO queues
while the device sleeps.
I think either Rusty or
null = 'do absolutely nothing'
generic = 'do D3 as per the specification'
The idea being the PM layer would go around calling
dev-power_off(dev);
as a default notifier for PCI devices.
Ok, I see. I didn't understand that the functions you were talking about
would be defaults to put
Just an addition to the sample:
fds[3] = sem3;
fds[4] = sem4;
fds[5] = sem5;
fds[6] = sem6;
.. and wait for any of them? or for all together?
and sure have this mixed with descriptors.
Wellknown win32 api WaitForMultipleObjects provides such
functionality, and having something like
that would
OK - agreed. But while I have your attention...
"Jens Axboe wrote:"
On the contrary, you are now given an exceptional opportunity to clean
up your code and get rid of blk_queue_pluggable and your noop plugging
function.
In summary: blk_queue_pluggable can be removed for all driver codes
Hi,
WHen i upgrade from 2.2 to 2.4, my first version was 2.4.1,
in which i upgraded my quota utils to 3.00 and then converted to the new
quota formats for 2.4.
my last 2.4 upgrade was 2.4.2ac23, quotas work fine on that.
but when i run 2.4.3 they dont. quota -v on a user shows just blank space
On Thu, Apr 19 2001, Peter T. Breuer wrote:
OK - agreed. But while I have your attention...
"Jens Axboe wrote:"
On the contrary, you are now given an exceptional opportunity to clean
up your code and get rid of blk_queue_pluggable and your noop plugging
function.
In summary:
On Tue, 17 Apr 2001 12:48:48 -0700 (PDT) Linus Torvalds wrote:
[deletia]
/*
* a fast semaphore is a 128-byte opaque thing,
* aligned on a 128-byte boundary. This is partly
* to minimize false sharing in the L1 (we assume
* that 128-byte
Hello,
I have a process which eats all the memory available
(buy making a loop of mallocs, writing and reading the
malloc'd memory) called memoryEater (to torture test
the memory system before going to a production system)
My kernel is 2.4.2smp on a 4 way Alpha machine with 8 Go
of RAM.
Can't say i'm actively working on it but I've emailed Nevil to see if
he knows of any RTFM work that is being done on Linux.
Although here's some observations:
Userspace pcap meters (such as NeTreMet) can measure traffic IP stack
doesn't even see (useful for a probe on a span port for instance)
Vojtech Pavlik ([EMAIL PROTECTED]) wrote :
On Wed, Apr 18, 2001 at 10:21:53PM -0400, Manuel Ignacio Monge Garcia wrote:
El Mi 18 Abr 2001 15:16, escribiste:
I don't know about other possible problems with the kernel, but you must
use an 80 wire IDE cable for UDMA66/100 to work.
"Jens Axboe wrote:"
[ptb wrote]
through merge_reqeusts function controls.
My unease derives, I think, from the fact that I have occasionally used
plugging for other purposes. Namely for throttling the device. These
uses have always been experimental and uniformly unsuccessful, because
Manuel Ignacio Monge Garcia ([EMAIL PROTECTED]) wrote :
Hi. I have a ASUS A7V133 Motherboard with AMD ThinderBird 1 Ghz, and
PDC20265/VIA. I've tried all the possible combinations on "IDE, ATA and ATAPI
Block devices". I've read the "Unofficial Asus A7V and Linux ATA100
"Quasi-Mini-Howto"
Hello, Alan!
The setting is BIOS is to use irq 7 and dma 3. I normally use "options
parport_pc io=0x378 irq=7 dma=3" in /etc/modules.conf, but this time I
commented them out hoping that the driver will ask BIOS.
PnPBIOS: Parport found PNPBIOS PNP0401 at io=0378,0778 irq=7 dma=-1
Do
Andre Hedrick ([EMAIL PROTECTED]) wrote :
Hi Dan,
This was sent to me the other day, is this waht you are talking about?
Cheers,
+ /*
+*Turn off PCI Latency timeout (set to 0 clocks)
+*/
+ pci_write_config_byte(dev, 0x75, 0x80);
Is turning off PCI
hi
I am working on a kernel module which requires the addition of a large
number of kernel timers to expire statistical values ( including time
) maintained in a table.
One alternative would be to use a single timer and traverse the entire
table and use the existing system time to expire the
I am doing some embedded development with the 2.4.x series and have noticed
a few things..
1) In 2.4.2 in order to compile with module support you also had to turn on
smp support. This has been fixed in the 2.4.3 release. This bloated the
kernel image to 600k+ which in an embedded world is not
Hi,
This updates the nm256_audio driver to the 2.4 PCI API.
Patch is against 2.4.3-ac9, verified on Sony VAIO Laptop.
Ciao, Marcus
Index: drivers/sound/nm256_audio.c
===
RCS file:
On Thu, 19 Apr 2001, Marc Karasek did have cause to say:
2) In 2.4.3 the console port using ttySX is broken. It dumps fine to the
terminal but when you get to a point of entering data (login, configuration
scripts, etc) the terminal does not accept any input.
Most gettys and such take a
On Thu, 19 Apr 2001, Marc Karasek wrote:
I am doing some embedded development with the 2.4.x series and have noticed
a few things..
[SNIPPED...]
2) In 2.4.3 the console port using ttySX is broken. It dumps fine to the
terminal but when you get to a point of entering data (login,
Marcus Meissner wrote:
Hi,
This updates the nm256_audio driver to the 2.4 PCI API.
Patch is against 2.4.3-ac9, verified on Sony VAIO Laptop.
"verified" is the really important part with this driver, since its
really finicky. I have a patch I would love to bounce to you in
private, that
On Thu, 19 Apr 2001, Alon Ziv wrote:
* the userspace struct was just a signed count and a file handle.
The main reason I wanted to avoid a filehandle is just because it's
another name space that people already use, and that people know what the
semantics are for (ie "open()" is _defined_ to
We have found that one of our programs can cause system-wide
corruption of the x86 FPU under 2.2.16 and 2.2.17. That is, after we
run this program, the FPU gives bad results to all subsequent
processes.
We see this problem on dual 550MHz Xeons with 1GB RAM. We have 64 of
these things, and we
-Original Message-
From: Marc Karasek
To: 'Richard B. Johnson '
Sent: 4/19/01 11:53 AM
Subject: RE: Bug in serial.c
Did something change between 2.4.2 2.4.3? Under 2.4.2 I did not have
to init the terminal (are you refering to the host or client side?) and
just accepted the
On Thu, Apr 19, 2001 at 11:56:01AM -0400, Jeff Garzik wrote:
Marcus Meissner wrote:
Hi,
This updates the nm256_audio driver to the 2.4 PCI API.
Patch is against 2.4.3-ac9, verified on Sony VAIO Laptop.
"verified" is the really important part with this driver, since its
really
-Original Message-
From: Marc Karasek
To: 'Disconnect '
Sent: 4/19/01 11:49 AM
Subject: RE: Bug in serial.c
I have changed everything to point to /dev/ttyS0. The settings in
lilo.conf (I am booting from a floppy to emulate the embedded space) are
all for ttyS0. Lilo pritns to the
On Thu, 19 Apr 2001, Abramo Bagnara wrote:
[ Using file descriptors ]
This would also permit:
- to have poll()
- to use mmap() to obtain the userspace area
It would become something very near to sacred Unix dogmas ;-)
No, this is NOT what the UNIX dogmas are all about.
When UNIX says
Helge Hafting wrote:
Jeremy Jackson wrote:
currently all the kernel's heuristics are feed-back control loops.
what you are asking for is a feed-forward system: a way for the application
to tell kernel "I'm only reading this once, so after I'm done, throw it out
straight away"
and
On Thu, Apr 19, 2001 at 04:46:03PM +0200, David Balazic wrote:
Vojtech Pavlik ([EMAIL PROTECTED]) wrote :
On Wed, Apr 18, 2001 at 10:21:53PM -0400, Manuel Ignacio Monge Garcia wrote:
El Mi 18 Abr 2001 15:16, escribiste:
I don't know about other possible problems with the kernel,
Praveen Rajendran wrote:
hi
I am working on a kernel module which requires the addition of a large
number of kernel timers to expire statistical values ( including time
) maintained in a table.
One alternative would be to use a single timer and traverse the entire
table and use the
Bob McElrath [[EMAIL PROTECTED]] wrote:
Andrea Arcangeli [[EMAIL PROTECTED]] wrote:
So please try to reproduce the hang with 2.4.4pre3 with those two
patches applied:
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.4pre3aa3/00_alpha-numa-3
Hi!
Both kernel 2.4.2 and 2.4.3 have an error in handling magneto-
optical disks (MOs) with 2048-byte blocks when they are formatted
with FAT.
Conditions
--
- Kernel 2.4.2 or 2.4.3 (most likely ALL 2.4.x kernels)
- MO with 2048-byte blocks (e.g. 3.5" 640 MB)
On Thu, 19 Apr 2001, Alan Cox wrote:
can libraries use fast semaphores behind the back of the user? They might
well want to use the semaphores exactly for things like memory allocator
locking etc. But libc certainly cant use fd's behind peoples backs.
libc is entitled to, and most
Linus Torvalds wrote:
On Thu, 19 Apr 2001, Abramo Bagnara wrote:
[ Using file descriptors ]
This would also permit:
- to have poll()
- to use mmap() to obtain the userspace area
It would become something very near to sacred Unix dogmas ;-)
No, this is NOT what the UNIX
On Thu, Apr 19, 2001 at 11:21:17AM -0500, Bob McElrath wrote:
I'm at 2 days uptime now, and have not seen the process-table-hang.
Looks like this fixed it. Previously I would get a hang in the first
day or so. I'm using your alpha-numa-3 and rwsem-generic-4 against
2.4.4pre3.
good, thanks
udma 5 is ata100 udma4 is 66 so it's seeing your disk fine...
as far as the 27MB/s goes, it actually testing the disk and that's
what it got for throughput... that's acutally a pretty good number, on the
diamondmax 80 I get 23MB/s
/dev/hde:
Model=Maxtor 98196H8, FwRev=ZAH814Y0,
On Thu, Apr 19, 2001 at 03:25:33PM +0200, Martin Buck wrote:
I'm getting strange Oopses with 2.2.17 on an AMD Athlon 1.2 GHz machine.
[...]
BTW, I didn't mention it explicitly, but this kernel is *not*
Athlon-optimized (since I used it for several months on a P II and IIRC,
2.2.17 didn't offer
NIIBE Yutaka wrote:
Sometime, we have setting like following (say, in the migration
process of changing IP networks, or perhaps wrong way of load
balancing):
+--+
|eth0 eth1 |
+--+
| |
---+---+
Current
On Thu, Apr 19, 2001 at 09:01:53PM +0900, Takanori Kawano wrote:
When I ran raw I/O SCSI read/write test with 2.4.1 kernel
on our IA64 8way SMP box, kernel paniced and following
message was displayed.
Could you try again with 2.4.4pre4 plus the below patch?
libc is entitled to, and most definitely does exactly that. Take a look at
things like gethostent, getpwent etc etc.
Ehh.. I will bet you $10 USD that if libc allocates the next file
descriptor on the first "malloc()" in user space (in order to use the
semaphores for mm protection),
1 - 100 of 551 matches
Mail list logo
