Re: Poor SCSI drive performance on SMP machine, 2.2.16
WOOHOO, first report where I win one against the ever losing battle against SCSIparadox3, you made my evening... Also please add to the sign on I95 exit 2... ""Welcome to Maine", 'now you can go home, now'" Caution Moose will attempt to mate with cars carrying canoes in the winter. Cheers, Andre Hedrick Linux ATA Development On Sun, 28 Jan 2001, paradox3 wrote: > I have an SMP machine (dual PII 400s) running 2.2.16 with one 10,000 RPM IBM > 10 GB SCSI drive > (AIC 7890 on motherboard, using aic7xxx.o), and four various IDE drives. The > SCSI drive > performs the worst. In tests of writing 100 MB and sync'ing, one of my IDE > drives takes 31 seconds. The SCSI drive (while doing nothing else) took > 2 minutes, 10 seconds. This is extremely noticable in file transfers that > completely > monopolize the SCSI drive, and are much slower than when involving the IDE > drives. > After a large data operation on the SCSI drive, the system will hang for > several minutes. > Anyone know what could be causing this? Thanks. > > Attached are some data to help. > > > Thanks, > Para-dox ([EMAIL PROTECTED]) > > - 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/
Poor SCSI drive performance on SMP machine, 2.2.16
I have an SMP machine (dual PII 400s) running 2.2.16 with one 10,000 RPM IBM 10 GB SCSI drive (AIC 7890 on motherboard, using aic7xxx.o), and four various IDE drives. The SCSI drive performs the worst. In tests of writing 100 MB and sync'ing, one of my IDE drives takes 31 seconds. The SCSI drive (while doing nothing else) took 2 minutes, 10 seconds. This is extremely noticable in file transfers that completely monopolize the SCSI drive, and are much slower than when involving the IDE drives. After a large data operation on the SCSI drive, the system will hang for several minutes. Anyone know what could be causing this? Thanks. Attached are some data to help. Thanks, Para-dox ([EMAIL PROTECTED]) CPU0 CPU1 0: 43661720 59171710IO-APIC-edge timer 1: 233992 282694IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 8: 1 0IO-APIC-edge rtc 13: 1 0 XT-PIC fpu 14: 20 10IO-APIC-edge ide0 15: 46455293 50354306IO-APIC-edge ide1 16: 14508949 14462778 IO-APIC-level eth0 17:39395544293901 IO-APIC-level eth1 18: 750747 761816 IO-APIC-level aic7xxx NMI: 0 ERR: 0 PCI devices found: Bus 0, device 0, function 0: Host bridge: Intel 440BX - 82443BX Host (rev 2). Medium devsel. Master Capable. Latency=64. Prefetchable 32 bit memory at 0xe800 [0xe808]. Bus 0, device 1, function 0: PCI bridge: Intel 440BX - 82443BX AGP (rev 2). Medium devsel. Master Capable. Latency=64. Min Gnt=136. Bus 0, device 7, function 0: ISA bridge: Intel 82371AB PIIX4 ISA (rev 2). Medium devsel. Fast back-to-back capable. Master Capable. No bursts. Bus 0, device 7, function 1: IDE interface: Intel 82371AB PIIX4 IDE (rev 1). Medium devsel. Fast back-to-back capable. Master Capable. Latency=64. I/O at 0xf000 [0xf001]. Bus 0, device 7, function 2: USB Controller: Intel 82371AB PIIX4 USB (rev 1). Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=64. I/O at 0xe000 [0xe001]. Bus 0, device 7, function 3: Bridge: Intel 82371AB PIIX4 ACPI (rev 2). Medium devsel. Fast back-to-back capable. Bus 0, device 8, function 0: Ethernet controller: Intel 82557 (rev 5). Medium devsel. Fast back-to-back capable. IRQ 16. Master Capable. Latency=64. Min Gnt=8.Max Lat=56. Prefetchable 32 bit memory at 0xef101000 [0xef101008]. I/O at 0xe400 [0xe401]. Non-prefetchable 32 bit memory at 0xef00 [0xef00]. Bus 0, device 9, function 0: Ethernet controller: Winbond NE2000-PCI (rev 0). Medium devsel. Fast back-to-back capable. IRQ 17. I/O at 0xe800 [0xe801]. Bus 0, device 12, function 0: SCSI storage controller: Adaptec AIC-7890/1 (rev 0). Medium devsel. Fast back-to-back capable. BIST capable. IRQ 18. Master Capable. Latency=64. Min Gnt=39.Max Lat=25. I/O at 0xec00 [0xec01]. Non-prefetchable 64 bit memory at 0xef10 [0xef14]. Bus 1, device 0, function 0: VGA compatible controller: S3 Inc. ViRGE/GX2 (rev 6). Medium devsel. IRQ 16. Master Capable. Latency=64. Min Gnt=4.Max Lat=255. Non-prefetchable 32 bit memory at 0xe000 [0xe000].
Re: [PATCH] devfsd, compiling on glibc22x
Pierre Rousselet <[EMAIL PROTECTED]> writes: > for me : > make CFLAGS='-O2 -I. -D_GNU_SOURCE' > compiles without any patch. is it correct ? Yes. RTLD_NEXT is not in any standard, it's an extension available via -D_GNU_SOURCE. -- ---. ,-. 1325 Chesapeake Terrace Ulrich Drepper \,---' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com ` - 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/
Re: [PATCH] devfsd, compiling on glibc22x
David Ford wrote:
>
> This patch is simple, defines RTLD_NEXT if not previously defined.
>
> --- devfsd.c.orig Sat Jan 27 18:14:19 2001
> +++ devfsd.cSat Jan 27 18:15:46 2001
> @@ -165,6 +165,7 @@
> Last updated by Richard Gooch 3-JUL-2000: Added "-C
> /etc/modules.devfs"
>when calling modprobe(8). Fail if a configuration line has EXECUTE
> modprobe.
>
> +Updated by David Ford 27-JAN-2001: Added RTLD_NEXT define
>
> */
> #include
> @@ -221,6 +222,10 @@
> #define AC_MKNEWCOMPAT 8
> #define AC_RMOLDCOMPAT 9
> #define AC_RMNEWCOMPAT 10
> +
> +#ifndef RTLD_NEXT
> +# define RTLD_NEXT ((void *) -1l)
> +#endif
>
> struct permissions_type
> {
for me :
make CFLAGS='-O2 -I. -D_GNU_SOURCE'
compiles without any patch. is it correct ?
--
Pierre Rousselet <[EMAIL PROTECTED]>
-
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/
Re: ps hang in 241-pre10
Patch appears to work, for i in [0-9]*; do echo $i; cat $i/stat > /dev/null; done completes successfully with xmms running in "real-time" priority. Shawn. Marcelo Tosatti wrote: > On Sat, 27 Jan 2001, Linus Torvalds wrote: > > > > > > > On Sun, 28 Jan 2001, Marcelo Tosatti wrote: > > > > > > > > This is the smoking gun here, I bet, but I'd like to make sure I see the > > > > whole thing. I don't see _why_ we'd have deadlocked on __wait_on_page(), > > > > but I think this is the thread that hangs on to the mm semaphore. > > > > > > I was able to reproduce it here with dbench. > > > > > > Nothing is locked except this dbench thread (the only dbench thread): > > > > > > dbenchD C1C9FE64 5200 1013 1(L-TLB)1370 785 > > > Call Trace: [___wait_on_page+130/160] [truncate_list_pages+100/404] >[truncate_inode_pages+93/128] [iput+162/360] [dput+262/356] [fput+121/232] >[exit_mmap+218/292] > > > [mmput+56/80] [do_exit+208/680] [do_signal+566/656] [dput+25/356] >[path_release+13/60] [sys_newstat+100/112] [sys_read+188/196] [signal_return+20/24] > > > > Ok, this definitely seems to be the pattern. > > > > I don't see _what_ is going on, though. > > > > I know of one "known bug" in pre10: if you run out of swap-space with > > shared memory segments, it will do the wrong thing (return 1 without > > unlocking the page). xmms might trigger this, but I didn't think that > > dbench used shared memory? > > It does. Bingo. > > I'm not able to reproduce the problem here with your patch. > > Btw, there is another bug in shm_writepage() where it does not set the > page dirty in case of failure... > > - > 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/ - 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/
Re: vfat <-> vfat copying of ~700MB file, so slow!
On Fri, 26 Jan 2001 18:41:37 +0100, Pavel Machek <[EMAIL PROTECTED]> wrote: > Hi! > >> > Copying between vfat <-> vfat partitions is so slow. It seems >> > that it's vfat/msdos kernel driver problem because I tried to copy >> >> I reported this years ago, with a 700 kB file on a floppy and >> a 4 MB file on a Zip disk. In both cases mcopy was several times >> faster than the kernel code. > > Perhaps linear scan of FAT? Maybe. Quite likely, in fact. But there is no reason why fatfs can't store the current FAT cluster number in struct file's private data, making seeks, reads and writes O(1) (from O(n)). You'll have to give up using generic_file_read(), however. So it's not a trivial change. Ion -- It is better to keep your mouth shut and be thought a fool, than to open it and remove all doubt. - 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/
Re: broken Cyrix 486 cpuinfo in 2.4.0 [patch]
OK, I have fixed the problem I reported earlier. The following patch
makes my Cyrix 486-66 report with the same results as on 2.2.x.
If no one finds any problems with it, I'll send it on to Linus.
Vince
--- ./arch/i386/kernel/setup.c.orig Sat Jan 27 21:05:03 2001
+++ ./arch/i386/kernel/setup.c Sun Jan 28 00:51:11 2001
@@ -1866,7 +1866,8 @@
/* Detect Cyrix with disabled CPUID */
if ( c->x86 == 4 && test_cyrix_52div() ) {
strcpy(c->x86_vendor_id, "CyrixInstead");
- }
+ c->x86_vendor = X86_VENDOR_CYRIX;
+ } else
/* Detect NexGen with old hypercode */
if ( deep_magic_nexgen_probe() ) {
-
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/
Re: ps hang in 241-pre10
On Sun, 28 Jan 2001, Marcelo Tosatti wrote: > On Sat, 27 Jan 2001, Linus Torvalds wrote: > > > > > > > On Sun, 28 Jan 2001, Marcelo Tosatti wrote: > > > > > > > > This is the smoking gun here, I bet, but I'd like to make sure I see the > > > > whole thing. I don't see _why_ we'd have deadlocked on __wait_on_page(), > > > > but I think this is the thread that hangs on to the mm semaphore. > > > > > > I was able to reproduce it here with dbench. > > > > > > Nothing is locked except this dbench thread (the only dbench thread): > > > > > > dbenchD C1C9FE64 5200 1013 1(L-TLB)1370 785 > > > Call Trace: [___wait_on_page+130/160] [truncate_list_pages+100/404] >[truncate_inode_pages+93/128] [iput+162/360] [dput+262/356] [fput+121/232] >[exit_mmap+218/292] > > > [mmput+56/80] [do_exit+208/680] [do_signal+566/656] [dput+25/356] >[path_release+13/60] [sys_newstat+100/112] [sys_read+188/196] [signal_return+20/24] > > > > Ok, this definitely seems to be the pattern. > > > > I don't see _what_ is going on, though. > > > > I know of one "known bug" in pre10: if you run out of swap-space with > > shared memory segments, it will do the wrong thing (return 1 without > > unlocking the page). xmms might trigger this, but I didn't think that > > dbench used shared memory? > > It does. Bingo. > > I'm not able to reproduce the problem here with your patch. > > Btw, there is another bug in shm_writepage() where it does not set the > page dirty in case of failure... Why dont you just put set_page_dirty() back in page_launder() in case writepage() fails? Otherwise you'll have to do in every specific implementation of writepage(). - 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/
Re: ps hang in 241-pre10
On Sat, 27 Jan 2001, Linus Torvalds wrote: > > > On Sun, 28 Jan 2001, Marcelo Tosatti wrote: > > > > > > This is the smoking gun here, I bet, but I'd like to make sure I see the > > > whole thing. I don't see _why_ we'd have deadlocked on __wait_on_page(), > > > but I think this is the thread that hangs on to the mm semaphore. > > > > I was able to reproduce it here with dbench. > > > > Nothing is locked except this dbench thread (the only dbench thread): > > > > dbenchD C1C9FE64 5200 1013 1(L-TLB)1370 785 > > Call Trace: [___wait_on_page+130/160] [truncate_list_pages+100/404] >[truncate_inode_pages+93/128] [iput+162/360] [dput+262/356] [fput+121/232] >[exit_mmap+218/292] > > [mmput+56/80] [do_exit+208/680] [do_signal+566/656] [dput+25/356] >[path_release+13/60] [sys_newstat+100/112] [sys_read+188/196] [signal_return+20/24] > > Ok, this definitely seems to be the pattern. > > I don't see _what_ is going on, though. > > I know of one "known bug" in pre10: if you run out of swap-space with > shared memory segments, it will do the wrong thing (return 1 without > unlocking the page). xmms might trigger this, but I didn't think that > dbench used shared memory? It does. Bingo. I'm not able to reproduce the problem here with your patch. Btw, there is another bug in shm_writepage() where it does not set the page dirty in case of failure... - 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/
Re: Knowing what options a kernel was compiled with
On Sun, 28 Jan 2001 00:13:48 -0500, "Matthew Pitts" <[EMAIL PROTECTED]> wrote: >Some distributions DO include the config. It may be located >in the /boot dir with a name CONFIG-2.2.10 or similar. I >know that Caldera 2.3 shiped that way(2.4 may also). If you >have the install CDROM, the kernel source install may have >it (e.g. Linux-Mandrake 7.x). I know that some distributions ship .config but not all do. A long way down on my TODO list is "submit a requirement to FHS that .config, System.map and other kernel related text files must be shipped in directory ". I would like to be /lib/modules/`uname -r` since that directory is already kernel specific, but we have to handle kernels without modules and disks with restricted size in /lib. However that discussion is best held on the FHS/LSB lists, not l-k. - 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/
Re: sendfile+zerocopy: fairly sexy (nothing to do with ECN)
[EMAIL PROTECTED] wrote: > > Hello! > > > 2.4.1-pre10+zercopy, using read()/write(): 38.1% CPU > > write() on zc card is worse than normal write() by definition. > It generates split buffers. yes. The figures below show this. Disabling SG+checksums speeds up write() and send(). > Split buffers are more expensive and we have to pay for this. > You have paid too much for slow card though. 8) > > Do you measure load correctly? Yes. Quite confident about this. Here's the algorithm: 1: Run a cycle-soaker on each CPU on an otherwise unloaded system. See how much "work" they all do per second. 2: Run the cycle-soakers again, but with network traffic happening. See how much their "work" is reduced. Deduce networking CPU load from this difference. The networking code all runs SCHED_FIFO or in interrupt context, so the cycle-soakers have no effect upon the network code's access to the CPU. The "cycle-soakers" just sit there spinning and dirtying 10,000 cachelines per second. > > 2.4.1-pre10+zercopy, using read()/write(): 39.2% CPU* hardware tx >checksums disabled > > This is illegal combination of parameters. You force two memory accesses, > doing this. The fact that it does not add to load is dubious. 8)8) mm.. Perhaps with read()/write() the data is already in cache? Anyway, I've tweaked up the tool again so it can do send() or write() (then I looked at the implementation and wondered why I'd bothered). It also does TCP_CORK now. I ran another set of tests. The zerocopy patch improves sendfile() hugely but slows down send()/write() significantly, with a 3c905C: http://www.uow.edu.au/~andrewm/linux/#zc The kernels which were tested were 2.4.1-pre10 with and without the zerocopy patch. We only look at client load (the TCP sender). In all tests the link throughput was 11.5 mbytes/sec at all times (saturated 100baseT) unless otherwise noted. The client (the thing which sends data) is a dual 500MHz PII with a 3c905C. For the write() and send() tests, the chunk size was 64 kbytes. The workload was 63 files with an average length of 350 kbytes. CPU 2.4.1-pre10+zerocopy, using sendfile(): 9.6% 2.4.1-pre10+zerocopy, using send(): 24.1% 2.4.1-pre10+zerocopy, using write():24.2% 2.4.1-pre10+zerocopy, using sendfile(): 16.2% * checksums and SG disabled 2.4.1-pre10+zerocopy, using send(): 21.5% * checksums and SG disabled 2.4.1-pre10+zerocopy, using write():21.5% * checksums and SG disabled 2.4.1-pre10-vanilla, using sendfile(): 17.1% 2.4.1-pre10-vanilla, using send(): 21.1% 2.4.1-pre10-vanilla, using write(): 21.1% Bearing in mind that a large amount of the load is in the device driver, the zerocopy patch makes a large improvement in sendfile efficiency. But read() and send() performance is decreased by 10% - more than this if you factor out the constant device driver overhead. TCP_CORK makes no difference. The files being sent are much larger than a single frame. Conclusions: For a NIC which cannot do scatter/gather/checksums, the zerocopy patch makes no change in throughput in all case. For a NIC which can do scatter/gather/checksums, sendfile() efficiency is improved by 40% and send() efficiency is decreased by 10%. The increase and decrease caused by the zerocopy patch will in fact be significantly larger than these two figures, because the measurements here include a constant base load caused by the device driver. - - 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/
ADV: Why Pay To Win ?? Play Free Lotto
Title: Win $1,000,000 Today Play Free Lotto Register To Win A New Mercedes Benz Shop Major Retailers Sharper Image
Re: Knowing what options a kernel was compiled with
Matthew and Keith, Thank you to both of you for your input, info, and quick responses. I just wanted to make shure there weren't tricks still in the bag that I hadn't learned about in this area. I'll look for the config file. Jacob Anawalt Matthew Pitts wrote: > On Sun, 28 Jan 2001 16:06:57 +1100 > Keith Owens <[EMAIL PROTECTED]> wrote: > > On Sat, 27 Jan 2001 22:21:41 -0700, > > Jacob Anawalt <[EMAIL PROTECTED]> wrote: > > >Is there a way to know what options a running kernel was > > compiled with, > > >if you dont have access to the source or configure files > > it was compiled > > >off of? > > > > No. You have to insist that whoever distributes the > > kernel binary also > > distributes the .config file that it was compiled with. > > > > Don't bother arguing that the kernel should record this > > info, it has > > been discussed before and rejected. This is a problem > > for the > > distributors, not for the kernel. > Keith and Jacob, > Some distributions DO include the config. It may be located > in the /boot dir with a name CONFIG-2.2.10 or similar. I > know that Caldera 2.3 shiped that way(2.4 may also). If you > have the install CDROM, the kernel source install may have > it (e.g. Linux-Mandrake 7.x). > > Matthew > [EMAIL PROTECTED] - 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/
Re: Knowing what options a kernel was compiled with
On Sun, 28 Jan 2001 16:06:57 +1100 Keith Owens <[EMAIL PROTECTED]> wrote: > On Sat, 27 Jan 2001 22:21:41 -0700, > Jacob Anawalt <[EMAIL PROTECTED]> wrote: > >Is there a way to know what options a running kernel was > compiled with, > >if you dont have access to the source or configure files > it was compiled > >off of? > > No. You have to insist that whoever distributes the > kernel binary also > distributes the .config file that it was compiled with. > > Don't bother arguing that the kernel should record this > info, it has > been discussed before and rejected. This is a problem > for the > distributors, not for the kernel. Keith and Jacob, Some distributions DO include the config. It may be located in the /boot dir with a name CONFIG-2.2.10 or similar. I know that Caldera 2.3 shiped that way(2.4 may also). If you have the install CDROM, the kernel source install may have it (e.g. Linux-Mandrake 7.x). Matthew [EMAIL PROTECTED] - 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/
Re: Knowing what options a kernel was compiled with
On Sat, 27 Jan 2001 22:21:41 -0700, Jacob Anawalt <[EMAIL PROTECTED]> wrote: >Is there a way to know what options a running kernel was compiled with, >if you dont have access to the source or configure files it was compiled >off of? No. You have to insist that whoever distributes the kernel binary also distributes the .config file that it was compiled with. Don't bother arguing that the kernel should record this info, it has been discussed before and rejected. This is a problem for the distributors, not for the kernel. - 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/
Knowing what options a kernel was compiled with
Is there a way to know what options a running kernel was compiled with, if you dont have access to the source or configure files it was compiled off of? In particular, I am trying to discover if 'advanced router' and 'equal cost multi path' options are compiled into RH7 kernel-2.2.16-22. I would also like to know if there is a way to discover this information for other settings that do not have a /proc entry or other visible object (eg modules). I am not following this list currently, so if you would please include my email in the replies, I would appreciate it. tia, Jacob Anawalt - 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/
Re: ps hang in 241-pre10
On Sun, 28 Jan 2001, Marcelo Tosatti wrote:
> >
> > This is the smoking gun here, I bet, but I'd like to make sure I see the
> > whole thing. I don't see _why_ we'd have deadlocked on __wait_on_page(),
> > but I think this is the thread that hangs on to the mm semaphore.
>
> I was able to reproduce it here with dbench.
>
> Nothing is locked except this dbench thread (the only dbench thread):
>
> dbenchD C1C9FE64 5200 1013 1(L-TLB)1370 785
> Call Trace: [___wait_on_page+130/160] [truncate_list_pages+100/404]
>[truncate_inode_pages+93/128] [iput+162/360] [dput+262/356] [fput+121/232]
>[exit_mmap+218/292]
> [mmput+56/80] [do_exit+208/680] [do_signal+566/656] [dput+25/356]
>[path_release+13/60] [sys_newstat+100/112] [sys_read+188/196] [signal_return+20/24]
Ok, this definitely seems to be the pattern.
I don't see _what_ is going on, though.
I know of one "known bug" in pre10: if you run out of swap-space with
shared memory segments, it will do the wrong thing (return 1 without
unlocking the page). xmms might trigger this, but I didn't think that
dbench used shared memory?
There's also an ugliness in the truncate ordering. I don't think it should
matter, but I do believe it's conceptually wrong as-is.
Does this patch make any difference at all?
Linus
-
diff -u --recursive --new-file pre10/linux/mm/memory.c linux/mm/memory.c
--- pre10/linux/mm/memory.c Sat Jan 27 10:53:39 2001
+++ linux/mm/memory.c Sat Jan 27 19:12:35 2001
@@ -945,7 +945,6 @@
if (inode->i_size < offset)
goto do_expand;
inode->i_size = offset;
- truncate_inode_pages(mapping, offset);
spin_lock(&mapping->i_shared_lock);
if (!mapping->i_mmap && !mapping->i_mmap_shared)
goto out_unlock;
@@ -960,8 +959,7 @@
out_unlock:
spin_unlock(&mapping->i_shared_lock);
- /* this should go into ->truncate */
- inode->i_size = offset;
+ truncate_inode_pages(mapping, offset);
if (inode->i_op && inode->i_op->truncate)
inode->i_op->truncate(inode);
return;
diff -u --recursive --new-file pre10/linux/mm/shmem.c linux/mm/shmem.c
--- pre10/linux/mm/shmem.c Sat Jan 27 10:53:39 2001
+++ linux/mm/shmem.cSat Jan 27 19:50:08 2001
@@ -217,8 +217,11 @@
info = &page->mapping->host->u.shmem_i;
swap = __get_swap_page(2);
- if (!swap.val)
- return 1;
+ if (!swap.val) {
+ set_page_dirty(page);
+ UnlockPage(page);
+ return -ENOMEM;
+ }
spin_lock(&info->lock);
shmem_recalc_inode(page->mapping->host);
-
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/
[OT] Re: hotmail not dealing with ECN
On Sun, Jan 28, 2001 at 02:10:25AM +0100, Dominik Kubla wrote: > On Sat, Jan 27, 2001 at 07:11:59PM -0500, Gregory Maxwell wrote: > > It's this kind of ignorance that makes the internet a less secure and stable > > place. > > You have obviously absolutely no idea what you are talking about. Period. Your following comments show exactly who is has no idea of what he is talking about. Period. > > The network should not be a stateful device. If you need stateful > > firewalling the only place it should be implimented is on the end node. If > > management of that is a problem, then make an interface solve that problem > > insted of breaking the damn network. > > So how do you propose to secure devices like MRT's or X-Ray scanners or > life-support in a hospital? Nowadays this equipment is hooked to the > internal network of the hospital and protected by really paranoid > firewalls. Do you really want unneeded software on those devices? Oh yes! This provides you with virtually zero extra security. Now someone in the next room, perhaps the lobby, is free to attack the system... Which probably has very little extra security and trusts the network (after all, it's firewall protected). An attack against an Xray system is much more likely to come from inside the companies network. The only way to have firewall protection against even a simple majority of attacks is to implement a firewall per system. That would be expensive, and wasteful, so it makes a lot more sense to implement a firewall IN every system. Such a thing can be done at zero expense with practically no performance loss and not break the end-to-end model of the Internet. But such a simple solution would totally invalidate the use for most security 'experts' and their products. Firewalling is commodity. Cope. It's much more useful to push it to the end-node where it belongs. But look where security companies make their money The most common business affecting security violations are internal. Yes, many security companies are making most of their money selling expensive and pointless network profalatics. Why? For firewalling to be affordable on every system, it has to be free. Thats not profitable for security companies which is why you never hear it suggested, even though it actually can defend against the most common threats. The very fact that you bring up medical systems and suggest that I purposed leaving them unsecured shows that your only avenue for discussion was hysteria. > Or what about the computer systems in nuclear powerplants? In air defense > systems? Power grids? Water supply? > Oh come on! Just reread some of the newspapers back from Dec 31 1999! Mythology and hysteria. The same things that promotes the propagation of network degrading central firewalls. - 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/
Re: ps hang in 241-pre10
(ugh, sorry about last mail) On 27 Jan 2001, Linus Torvalds wrote: > In article <[EMAIL PROTECTED]>, David Ford <[EMAIL PROTECTED]> wrote: > >Unfortunately klogd reads /procerg. > > > >So the following is a painstakingly slow hand translation, I'll only print > >the D state entries unless someone asks otherwise. > > You seem to be pretty much able to reproduce this at will, right? > > I'd really like to see the raw System.map and dmesg output if your > syslogd doesn't do a proper job of getting the symbols interpreted: just > send the things by email, and I'll put something together. It's too > hard to interpret your half-way decoded thing, and I really want to see > what this xmms thing is doing.. > > >xmms D CACC5EA8 4116 713155 715 (NOTLB)1493 674 > >Call Trace: [] [] [] [] [] > >[] [] > > [] [] [] [] [] > > > >c01248e4 T ___wait_on_page > >c0124984 t __lock_page > > > >c01240dc t truncate_list_pages > >c0124268 T truncate_inode_pages > >c01242d4 t writeout_one_page > > This is the smoking gun here, I bet, but I'd like to make sure I see the > whole thing. I don't see _why_ we'd have deadlocked on __wait_on_page(), > but I think this is the thread that hangs on to the mm semaphore. I was able to reproduce it here with dbench. Nothing is locked except this dbench thread (the only dbench thread): dbenchD C1C9FE64 5200 1013 1(L-TLB)1370 785 Call Trace: [___wait_on_page+130/160] [truncate_list_pages+100/404] [truncate_inode_pages+93/128] [iput+162/360] [dput+262/356] [fput+121/232] [exit_mmap+218/292] [mmput+56/80] [do_exit+208/680] [do_signal+566/656] [dput+25/356] [path_release+13/60] [sys_newstat+100/112] [sys_read+188/196] [signal_return+20/24] - 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/
Re: Kernel 2.4.x and 2.4.1-preX - Higher latency then 2.2.xkernels?
It should also be noted, that while using GCC and other tasks, the latency has returned to 2.2 levels from my point. Before. If you want to me to do any testing I can do that. I applied the timepegs patch: Kernel timepegs enabled. See http://www.uow.edu.au/~andrewm/linux/ Shawn. > > > > Andrew, the patch HAS made a difference. For example, while untaring >glibc-2.2.1.tar.gz the > > system was not sluggish (mouse movements in X) etc. > > > > Seems to be a go for latency improvements on this system. > > hmm.. OK, thanks. > > Chris, this seems to be a worthwhile improvement to mainstream > reiserfs, independent of the low-latency thing. You can > probably achieve 10 milliseconds with just a few lines of > code - a subset of the patch which Shawn tested. (Unless you > were planning on magical algorithmic improvements...). > > I'm all set up to generate those few lines of code, so > I'll propose a patch later this week. > > - - 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/
Re: 2.4.1-pre10 deadlock (Re: ps hang in 241-pre10)
On Sun, 28 Jan 2001, Jens Axboe wrote: > On Sat, Jan 27 2001, Linus Torvalds wrote: > > > What was the trace of this? Just curious, the below case outlined by > > > Linus should be pretty generic, but I'd still like to know what > > > can lead to this condition. > > > > It was posted on linux-kernel - I don't save the dang things because I > > have too much in my "archives" as is ;) > > Ok I see it now, confused wrt the different threads... > > > > Good spotting. Actually I see one more problem with it too. If > > > we've started batching (under heavy I/O of course), we could > > > splice the pending list and wake up X number of sleepers, but > > > there's a) no guarentee that these sleepers will actually get > > > the requests if new ones keep flooding in > > > > (a) is ok. They'll go back to sleep - it's a loop waiting for requests.. > > My point is not that it's broken, but it will favor new comers > instead of tasks having blocked on a free slot already. So it > would still be nice to get right. > > > >and b) no guarentee > > > that X sleepers require X request slots. > > > > Well, IF they are sleeping (and thus, if the wake_up_nr() will trigger on > > them), they _will_ use a request. I don't think we have to worry about > > that. At most we will wake up "too many" - we'll wake up processes even > > though they end up not being able to get a request anyway because somebody > > else got to it first. And that's ok. It's the "wake up too few" that > > causes trouble, and I think that will be fixed by my suggestion. > > Yes they may end up sleeing right away again as per the above a) case > for instance. The logic now is 'we have X free slots now, wake up > x sleepers' where it instead should be 'we have X free slots now, > wake up people until the free list is exhausted'. > > > Now, I'd worred if somebody wants several requests at the same time, and > > doesn't feed them to the IO layer until it has gotten all of them. In that > > case, you can get starvation with many people having "reserved" their > > requests, and there not be enough free requests around to actually ever > > wake anybody up again. But the regular IO paths do not do this: they will > > all allocate a request and just submit it immediately, no "reservation". > > Right, the I/O path doesn't do this and it would seem more appropriate > to have such users use their own requests instead of eating from > the internal pool. > > -- > * Jens Axboe <[EMAIL PROTECTED]> > * SuSE Labs > - > 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/ > - 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/
Re: ps hang in 241-pre10
> Does anybody have a clue about what is different with xmms? > > Does it use KNI if it can, for example? We used to have a problem > with KNI+Athlons, for example. No, it doesn't. > It might also be that it's threading-related, and that XMMS is one > of the few things that uses threads. Things like that. I'm not an > XMMS user, can somebody who knows XMMS comment on things that it > does that are unusual? Yes, threads could be the thing that makes a difference. I can't think of anything else that is special about XMMS. -- Håvard Kvålen - 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/
RE: hotmail not dealing with ECN
> On Sat, Jan 27, 2001 at 02:18:31PM -0800, David Schwartz wrote: > > > Firewalling should be implemented on the hosts, perhaps with > > > centralized > > > policy management. In such a situation, there would be no > > > reason to filter > > > on funny IP options. > > That's madness. If you have to implement your firewalling > > on every host, > > what do you do when someone wants to run a new OS? Forbid it? > No a standard management interface would be followed by every host. Not > unlike configuring your ipaddress with DHCP. How does a standard interface help? Perhaps you don't understand the problem -- someone wants to use a new operating system that you no information about. You are willing to let it run on your network if and only if you can be assured it won't violate your firewall policy. So how does an interface guarantee that an unknown implementation of that interface will correctly implement it? And what about printers? Embedded systems? Legacy equipment? What about systems that have to run software that isn't as trusted as the implementation of the firewalls has to be? The net effect of having to trust every host to enforce your security policy is that you can't give anyone not trusted to enforce your security policy root access on any machine on your network. Or, to put it another way, you have to trust every machine on your network and every person who controls them as much as you trust your firewall. That's simply unacceptable in many applications. DS - 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/
Re: Kernel 2.4.x and 2.4.1-preX - Higher latency then 2.2.xkernels?
Shawn Starr wrote: > > Andrew, the patch HAS made a difference. For example, while untaring >glibc-2.2.1.tar.gz the > system was not sluggish (mouse movements in X) etc. > > Seems to be a go for latency improvements on this system. hmm.. OK, thanks. Chris, this seems to be a worthwhile improvement to mainstream reiserfs, independent of the low-latency thing. You can probably achieve 10 milliseconds with just a few lines of code - a subset of the patch which Shawn tested. (Unless you were planning on magical algorithmic improvements...). I'm all set up to generate those few lines of code, so I'll propose a patch later this week. - - 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/
Re: uptime for 2.2.13 on x86
> What happens the day the machine hits 497 days uptime? see http://www.eax.com/about/ for brief explanation of this. I'm sure others can add more but it should answer your question. -- Adam http://www.eax.com The Supreme Headquarters of the 32 bit registers - 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/
Re: Kernel 2.4.x and 2.4.1-preX - Higher latency then 2.2.xkernels?
Andrew, the patch HAS made a difference. For example, while untaring glibc-2.2.1.tar.gz the system was not sluggish (mouse movements in X) etc. Seems to be a go for latency improvements on this system. Shawn Starr wrote: > Applying now. > > Andrew Morton wrote: > > > Shawn, > > > > I've pretty much completed the low-latency patch against reiserfs. > > It seems to be a little more latency-prone than ext2, but under normal > > workloads it's not significant. The worst-case is 100 milliseconds, > > but that's when you're doing insane things to it. > > > > You may care to apply >http://www.uow.edu.au/~andrewm/linux/2.4.1-pre10-low-latency.patch > > against 2.4.1-pre10 and see if it "feels" different. I'd be surprised > > if it does, but the result would be interresting. > > > > Note that the low-latency capability must be enabled under the > > "Processor type and features" menu, and if you also enable the > > low-latency sysctl option, you'll need to > > > > echo 1 > /proc/sys/kernel/lowlatency > > > > to make it happen. Creature feep :) - 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/
Re: Kernel 2.4.0 loop device still hangs
Jens Axboe wrote: [snip] > > First of all, I'm all man (not up for debate) so it's Jens not Jen :-) > [snip] Doh! I beg your pardon. I must be blind. 8-) 8-) Mark - 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/
Re: Kernel 2.4.0 loop device still hangs
On Sat, Jan 27 2001, Mark Bratcher wrote: > Hey all, > > I applied the patch "loop-3", from Jen Axboe's 2.4.1-pre10 version, to > my 2.4.0 kernel as Jen had suggested we try for the loop device hang > problem. > > This patch appears to have gotten rid of the problem (at least after > testing it once in my previous scenario, which would normally fail 100% > of the time on 2.4.0 official). > > Thanks Jen! First of all, I'm all man (not up for debate) so it's Jens not Jen :-) > Can I continue running this patch on 2.4.0 with impunity, or do I need > to be careful of anything else? :-) It should be safe. Thanks for the feedback. -- * Jens Axboe <[EMAIL PROTECTED]> * SuSE Labs - 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/
uptime for 2.2.13 on x86
What happens the day the machine hits 497 days uptime? -- Lab tests show that use of micro$oft causes cancer in lab animals - 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/
[PATCH] devfsd, compiling on glibc22x
This patch is simple, defines RTLD_NEXT if not previously defined.
--- devfsd.c.orig Sat Jan 27 18:14:19 2001
+++ devfsd.cSat Jan 27 18:15:46 2001
@@ -165,6 +165,7 @@
Last updated by Richard Gooch 3-JUL-2000: Added "-C
/etc/modules.devfs"
when calling modprobe(8). Fail if a configuration line has EXECUTE
modprobe.
+Updated by David Ford 27-JAN-2001: Added RTLD_NEXT define
*/
#include
@@ -221,6 +222,10 @@
#define AC_MKNEWCOMPAT 8
#define AC_RMOLDCOMPAT 9
#define AC_RMNEWCOMPAT 10
+
+#ifndef RTLD_NEXT
+# define RTLD_NEXT ((void *) -1l)
+#endif
struct permissions_type
{
--
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
-
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/
Re: 2.4 Cpu usuage (display oddities more than anything)
Some oddities w/kapmd(2.4.0)... If I sit in X and do nothing other than run top or "vmstat 5", I get down to as low as 60% idle and 40% in system -- with kapmd getting 'charged' for the 40%. Then I go and run 'freeamp' and the CPU usage goes to 100% idle, presumably because kapmd never gets called because it's never in the idle loop for longer than 333ms. It's just weird and unnatural. Also forgive my ignorance but is it really possible playing VBR MP3's takes 0 measurable CPU? I've run the program for hours and a ps of 'freeamp' show either no measured cpu time or maybe 1 second...the kernel runs at at 100% idle for most of the time. I thought mp3 decompression was a cpu intensive operationweird... I guess I'm thinking -- maybe time in kapmd should be counted as 'idle'? -l - 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/
Re: 2.4.1-pre10 deadlock (Re: ps hang in 241-pre10)
On Sat, Jan 27 2001, Linus Torvalds wrote: > > What was the trace of this? Just curious, the below case outlined by > > Linus should be pretty generic, but I'd still like to know what > > can lead to this condition. > > It was posted on linux-kernel - I don't save the dang things because I > have too much in my "archives" as is ;) Ok I see it now, confused wrt the different threads... > > Good spotting. Actually I see one more problem with it too. If > > we've started batching (under heavy I/O of course), we could > > splice the pending list and wake up X number of sleepers, but > > there's a) no guarentee that these sleepers will actually get > > the requests if new ones keep flooding in > > (a) is ok. They'll go back to sleep - it's a loop waiting for requests.. My point is not that it's broken, but it will favor new comers instead of tasks having blocked on a free slot already. So it would still be nice to get right. > > and b) no guarentee > > that X sleepers require X request slots. > > Well, IF they are sleeping (and thus, if the wake_up_nr() will trigger on > them), they _will_ use a request. I don't think we have to worry about > that. At most we will wake up "too many" - we'll wake up processes even > though they end up not being able to get a request anyway because somebody > else got to it first. And that's ok. It's the "wake up too few" that > causes trouble, and I think that will be fixed by my suggestion. Yes they may end up sleeing right away again as per the above a) case for instance. The logic now is 'we have X free slots now, wake up x sleepers' where it instead should be 'we have X free slots now, wake up people until the free list is exhausted'. > Now, I'd worred if somebody wants several requests at the same time, and > doesn't feed them to the IO layer until it has gotten all of them. In that > case, you can get starvation with many people having "reserved" their > requests, and there not be enough free requests around to actually ever > wake anybody up again. But the regular IO paths do not do this: they will > all allocate a request and just submit it immediately, no "reservation". Right, the I/O path doesn't do this and it would seem more appropriate to have such users use their own requests instead of eating from the internal pool. -- * Jens Axboe <[EMAIL PROTECTED]> * SuSE Labs - 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/
Re: ECN: Clearing the air
On Sun, 28 Jan 2001, Chris Wedgwood wrote: > On Sat, Jan 27, 2001 at 07:23:51PM -0500, jamal wrote: > > suggested blocking ECN. Article at: > > >http://www.securityfocus.com/frames/?focus=ids&content=/focus/ids/articles/portscan.html > > the site is now ATM -- can someone briefly explain the logic in > blocking it? > It is Queso they quoted not nmap, sorry -- same thing. The idea is to "detect" port scanners. Queso sets the two TCP reserved bits in the SYN (now allocated for ECN). Some OSes reflect that back in the SYN-ACK (Linux < 2.0.2? for example was such a culprit). Queso could then use that information to narow down the OS detection. I suppose the idea is to detect Queso and react to it ;-> cheers, jamal - 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/
Re: 2.4.1-pre10 deadlock (Re: ps hang in 241-pre10)
On Sun, 28 Jan 2001, Jens Axboe wrote:
> >
> > So what happens is that somebody takes a page fault (and gets the mm
> > lock), tries to read something in, and never gets anything back, thus
> > leaving the MM locked.
>
> What was the trace of this? Just curious, the below case outlined by
> Linus should be pretty generic, but I'd still like to know what
> can lead to this condition.
It was posted on linux-kernel - I don't save the dang things because I
have too much in my "archives" as is ;)
> > Lorenzo, does the problem go away for you if you remove the
> >
> > if (!list_empty(&q->request_freelist[rw])) {
> > ...
> > }
> >
> > code from blkdev_release_request() in drivers/block/ll_rw_block.c?
>
> Good spotting. Actually I see one more problem with it too. If
> we've started batching (under heavy I/O of course), we could
> splice the pending list and wake up X number of sleepers, but
> there's a) no guarentee that these sleepers will actually get
> the requests if new ones keep flooding in
(a) is ok. They'll go back to sleep - it's a loop waiting for requests..
>and b) no guarentee
> that X sleepers require X request slots.
Well, IF they are sleeping (and thus, if the wake_up_nr() will trigger on
them), they _will_ use a request. I don't think we have to worry about
that. At most we will wake up "too many" - we'll wake up processes even
though they end up not being able to get a request anyway because somebody
else got to it first. And that's ok. It's the "wake up too few" that
causes trouble, and I think that will be fixed by my suggestion.
Now, I'd worred if somebody wants several requests at the same time, and
doesn't feed them to the IO layer until it has gotten all of them. In that
case, you can get starvation with many people having "reserved" their
requests, and there not be enough free requests around to actually ever
wake anybody up again. But the regular IO paths do not do this: they will
all allocate a request and just submit it immediately, no "reservation".
(Obviously, _submitting_ the request doesn't mean that we'd actually start
processing it, but if somebody ends up waiting for requests they'll do the
unplug that does start it all going, so effectively we can think of it as
a logical "start this request now" thing even if it gets delayed in order
to coalesce IO).
Linus
-
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/
Re: hotmail not dealing with ECN
Jamie Lokier said once upon a time (Fri, 26 Jan 2001): > Does ECN provide perceived benefits to the node using it? Why are you even making suggestions when you haven't even read the RFC? It seems that knowing what ECN is would be prerequisite to engaging in discussion about it. Dax - 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/
Re: ps hang in 241-pre10
In article <[EMAIL PROTECTED]>, David Ford <[EMAIL PROTECTED]> wrote: >Unfortunately klogd reads /procerg. > >So the following is a painstakingly slow hand translation, I'll only print >the D state entries unless someone asks otherwise. You seem to be pretty much able to reproduce this at will, right? I'd really like to see the raw System.map and dmesg output if your syslogd doesn't do a proper job of getting the symbols interpreted: just send the things by email, and I'll put something together. It's too hard to interpret your half-way decoded thing, and I really want to see what this xmms thing is doing.. >xmms D CACC5EA8 4116 713155 715 (NOTLB)1493 674 >Call Trace: [] [] [] [] [] >[] [] > [] [] [] [] [] > >c01248e4 T ___wait_on_page >c0124984 t __lock_page > >c01240dc t truncate_list_pages >c0124268 T truncate_inode_pages >c01242d4 t writeout_one_page This is the smoking gun here, I bet, but I'd like to make sure I see the whole thing. I don't see _why_ we'd have deadlocked on __wait_on_page(), but I think this is the thread that hangs on to the mm semaphore. Linus - 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/
Re: ps hang in 241-pre10
yes, I should also mention I have also a SoundBlaster 32AWE (0MB on the daughterboard). J Sloan wrote: > OK, here's the details you asked about: > > Soundblaster Awe 32 sound card > Voodoo 3 pci video card > Running Xfree86-4.0.0 (rpms from 3dfx.com) > Playing unreal tournament, no special game > options, just 800x600 graphics @ 16 bits. > > To recap, the symptoms (hung ps, etc) occurred > on kernel 2.4.1-pre8 + low latency patches. (but > I don't think the low latency patches had anything > to do with it, based on the other reports) > > Hope this helps > > jjs > > David Ford wrote: > > > On 2.4.0-ac12, I played music for about 30 minutes without any problems. I >started up an mpeg in xmms and it > > locked in short order. I'm sure now that it has something to do with the >graphics. What DGA or other config > > options do you have enabled for your game? > > > > What video and sound card? - 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/
Re: routing between different subnets on same if.
On Sat, 27 Jan 2001, Miquel van Smoorenburg wrote: > What about /proc/sys/net/ipv4/conf/*/rp_filter ? Should be zero > for the 192.* interface(s), I think. > i already have that enabled for security purposes helaas. > Mike. regards, -- Paul Jakma [EMAIL PROTECTED] [EMAIL PROTECTED] PGP5 key: http://www.clubi.ie/jakma/publickey.txt --- Fortune: DISCLAIMER: Use of this advanced computing technology does not imply an endorsement of Western industrial civilization. PS miquel, bitbucket will jouw email niet accepteren, komt terug met error "550 <[EMAIL PROTECTED]>... Domain has no existing recipients" - 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/
Re: hotmail not dealing with ECN
In message <[EMAIL PROTECTED]> you write: > I thought that most firewalls were supposed to be insanely paranoid. > Perhaps it would be considered a possible covert data channel, as > farfecthed as that may sound. If they were `insanely paranoid' they wouldn't just be doing packet filtering. The firewall designers can't have it both ways. 1) Dropping these packets is wrong, but it won't get fixed if noone pressures them to. Fixing this now also makes future standards enhancements easier, by bringing the 'net closer to compliance. 2) Sending RSTs is completely fucked up. Those firewalls are too braindamaged to live. Distros will probably turn ECN off, but maybe if we fix enough of the net, later versions may not. Rusty. -- Premature optmztion is rt of all evl. --DK - 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/
Re: SMP Athlon...(a quiet question)
Andre Hedrick wrote:
>
> ER, they work but must compile as PII/Celeron :-(
> A bunch of memcpy header stuff fails to compile
> current is one of the left overs in some cases.
>
> I will dive deeper in monday, just wanting some feed back first.
>
> Cheers,
>
> 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]
> Please read the FAQ at http://www.tux.org/lkml/
Hello Andre,
I think that there is no good way to use in_interrupt() in asm/string.h.
Circular dependencies.
I've been using some form of this patch since last May, posted here several
times. It moves the mmx style memcpy into lib.a (mmx.c). I lose some
inlining, but since k7 does branch prediction for call addresses, inline
functions are somewhat less of a win. Certainly the big speedup from mmx is
more than enough to pay for it.
Cheers,
Tom
--
The Daemons lurk and are dumb. -- Emerson
--- linux/arch/i386/lib/mmx.c.orig Wed Oct 27 21:30:39 1999
+++ linux/arch/i386/lib/mmx.c Tue Jun 6 04:20:01 2000
@@ -1,6 +1,7 @@
#include
#include
#include
+#include
/*
* MMX 3DNow! library helper functions
@@ -88,6 +89,21 @@
stts();
return p;
}
+
+void * __constant_mmx_memcpy3d(void * to, const void * from, size_t len)
+{
+ if(in_interrupt())
+ return __constant_memcpy(to, from, len);
+ return _mmx_memcpy(to, from, len);
+}
+
+void *__mmx_memcpy3d(void *to, const void *from, size_t len)
+{
+ if(in_interrupt())
+ return __memcpy(to, from, len);
+ return _mmx_memcpy(to, from, len);
+}
+
static void fast_clear_page(void *page)
{
--- linux/include/asm-i386/mmx.h.orig Tue Jun 6 03:05:02 2000
+++ linux/include/asm-i386/mmx.hTue Jun 6 04:25:27 2000
@@ -10,5 +10,7 @@
extern void *_mmx_memcpy(void *to, const void *from, size_t size);
extern void mmx_clear_page(void *page);
extern void mmx_copy_page(void *to, void *from);
+extern __inline__ void *__constant_mmx_memcpy3d(void * to, const void * from, size_t
+len);
+extern __inline__ void *__mmx_memcpy3d(void *to, const void *from, size_t len);
#endif
--- linux/include/asm-i386/string.h.origTue Jun 6 03:05:02 2000
+++ linux/include/asm-i386/string.h Tue Jun 6 04:30:37 2000
@@ -287,13 +287,6 @@
#ifdef CONFIG_X86_USE_3DNOW
-/* All this just for in_interrupt() ... */
-
-#include
-#include
-#include
-#include
-#include
#include
/*
@@ -302,16 +295,16 @@
static inline void * __constant_memcpy3d(void * to, const void * from, size_t len)
{
- if(len<512 || in_interrupt())
+ if(len<512)
return __constant_memcpy(to, from, len);
- return _mmx_memcpy(to, from, len);
+ return __constant_mmx_memcpy3d(to, from, len);
}
extern __inline__ void *__memcpy3d(void *to, const void *from, size_t len)
{
- if(len<512 || in_interrupt())
+ if(len<512)
return __memcpy(to, from, len);
- return _mmx_memcpy(to, from, len);
+ return __mmx_memcpy3d(to, from, len);
}
#define memcpy(t, f, n) \
Re: ps hang in 241-pre10
OK, here's the details you asked about: Soundblaster Awe 32 sound card Voodoo 3 pci video card Running Xfree86-4.0.0 (rpms from 3dfx.com) Playing unreal tournament, no special game options, just 800x600 graphics @ 16 bits. To recap, the symptoms (hung ps, etc) occurred on kernel 2.4.1-pre8 + low latency patches. (but I don't think the low latency patches had anything to do with it, based on the other reports) Hope this helps jjs David Ford wrote: > On 2.4.0-ac12, I played music for about 30 minutes without any problems. I started >up an mpeg in xmms and it > locked in short order. I'm sure now that it has something to do with the graphics. >What DGA or other config > options do you have enabled for your game? > > What video and sound card? - 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/
Re: Oops accessing file on 2048 bytes/sector vfat MO in 2.4.0
Moi!
On Fri, 26 Jan 2001, Stefan Meyknecht wrote:
> I receive a Kernel oops while copying a file from MO-drive (vfat) with
> 2048 bytes sector size. There is no problen with ext2 formatted MOs.
>
> I think it happens because the function pointer cfv_file_read of the
> struct cvf_format is initialized with null.
Yup, that's the cause.
> This oops is 100% reproducable with the kernels: 2.4.0, 2.4.1-pre3,
> 2.4.1-pre7 and 2.4.0-ac11 (probably all >= 2.4.0).
... and on a fair number < 2.4.0. The patch below will give you (dog slow)
read access to your FAT MOs. Apply in fs/fat/. And don't even think about
write() and mmap().
Regards,
Daniel.
--[snip]--
--- cvf.c.vanilla Mon Jan 1 22:46:20 2001
+++ cvf.c Mon Jan 1 23:31:23 2001
@@ -51,6 +51,9 @@
const char *buf,
size_t count,
loff_t *ppos);
+ssize_t bigblock_fat_file_read(struct file *filp, char *buf, size_t count,
+ loff_t *ppos);
+
struct cvf_format default_cvf = {
0, /* version - who cares? */
@@ -92,7 +95,7 @@
default_fat_access,
NULL,
default_fat_bmap,
- NULL,
+ bigblock_fat_file_read,
default_fat_file_write,
NULL,
NULL
--- file.c.vanilla Mon Jan 1 22:46:26 2001
+++ file.c Tue Jan 16 00:15:16 2001
@@ -4,6 +4,9 @@
* Written 1992,1993 by Werner Almesberger
*
* regular file handling primitives for fat-based filesystems
+ *
+ * 2001-1-1 Daniel Kobras <[EMAIL PROTECTED]>:
+ * Added quick&dirty read operation for large sector media.
*/
#define ASC_LINUX_VERSION(V, P, S) (((V) * 65536) + ((P) * 256) + (S))
@@ -114,6 +117,56 @@
return retval;
}
+/* This is a hack. No readahead and other fancy stuff, but hopefully enough
+ * to get MOs working again. [dk]
+ * FIXME: Not sure whether I got error checking right.
+ */
+ssize_t bigblock_fat_file_read(struct file *filp, char *buf, size_t count,
+ loff_t *ppos)
+{
+ struct inode *inode = filp->f_dentry->d_inode;
+ int phys, pos;
+ struct buffer_head *bh;
+ size_t to_go, done;
+ char *buf_start = buf;
+
+ /* Taken from 2.2 source. */
+ if (!S_ISREG(inode->i_mode) && !S_ISLNK(inode->i_mode))
+ return -EINVAL;
+
+ if (*ppos > inode->i_size || !count)
+ return 0;
+
+ if (inode->i_size - *ppos < count)
+ count = inode->i_size - *ppos;
+
+ pos = *ppos>>SECTOR_BITS;
+ to_go = SECTOR_SIZE - (*ppos&(SECTOR_SIZE-1));
+ goto _start;
+
+ do {
+ to_go = SECTOR_SIZE;
+_start:
+ phys = fat_bmap(inode, pos++);
+ if (!phys)
+ return -EIO;
+ bh = fat_bread(inode->i_sb, phys);
+ if (!bh)
+ return -EIO;
+ done = to_go > count ? count : to_go;
+ if (copy_to_user(buf, bh->b_data, done)) {
+ fat_brelse(inode->i_sb, bh);
+ return -EFAULT;
+ }
+ fat_brelse(inode->i_sb, bh);
+ buf += done;
+ *ppos += done;
+ } while ((count -= done));
+
+ return buf - buf_start;
+}
+
+
void fat_truncate(struct inode *inode)
{
struct msdos_sb_info *sbi = MSDOS_SB(inode->i_sb);
--- inode.c.vanilla Tue Jan 2 00:36:18 2001
+++ inode.c Tue Jan 2 00:22:04 2001
@@ -820,6 +820,9 @@
inode->i_size = CF_LE_L(de->size);
inode->i_op = &fat_file_inode_operations;
inode->i_fop = &fat_file_operations;
+ /* FIXME: mmap is broken with large hwblocks! [dk] */
+ if (sb->s_blocksize > 512)
+ inode->i_fop->mmap = NULL;
inode->i_mapping->a_ops = &fat_aops;
MSDOS_I(inode)->mmu_private = inode->i_size;
}
-
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/
Re: ps hang in 241-pre10
It is important to note that when I hit the magic key and rebooted (SUB), a split second before it rebooted, a stalled 'lspci' snapped back to life and printed out my expected data. -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 - 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/
Re: ps hang in 241-pre10
On 2.4.0-ac12, I played music for about 30 minutes without any problems. I started up an mpeg in xmms and it locked in short order. I'm sure now that it has something to do with the graphics. What DGA or other config options do you have enabled for your game? What video and sound card? I have an ATI Rage LT Pro AGP-133 according to lspci. -d J Sloan wrote: > Sorry, there was no xmms involved here - > > The behavior occurred while playing unreal tournament. > > But at least the sound card was in use, FWIW - > > jjs > > David Ford wrote: > > > We've narrowed it down to "we're all running xmms" when it happend. > > > > -d > > > > J Sloan wrote: > > > > > Just for the record, the system where I saw the problem > > > has only ext2 - > > > > -- > > 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 > > > > - > > 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/ -- 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 - 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/
Re: ps hang in 241-pre10
Unfortunately klogd reads /procerg. So the following is a painstakingly slow hand translation, I'll only print the D state entries unless someone asks otherwise. Prior to this: XMMS is running playing star wars mpeg. (regular user) (frozen) TOP is running (regular user) (frozen) while [ 1 ]; do ls -laR /proc ; done (regular user) (frozen) skill -9 xmms (root) (frozen) X 4.0.2 running, scp of 600meg file over pegasus usb ethernet (10Mbit). syslog caught: Jan 27 16:42:26 nifty kernel: SysRq: Show State Jan 27 16:42:26 nifty kernel: Jan 27 16:42:26 nifty kernel: freesibling Jan 27 16:42:26 nifty kernel: task PCstack pid father child younger older Jan 27 16:42:26 nifty kernel: init S CBFEBF2C 3184 1 0 187 (NOTLB) dmesg shows (only D state for brevity): top D CA98B3DC 4440 219158(NOTLB) Call Trace: [] [] [] [] [] [] [] c01078c8 T __down c0107964 T __down_interruptible c0107a28 T __down_trylock c0107a60 T __down_failed c0107a6c T __down_failed_interruptible c02f6a00 T stext_lock c02f827e A _etext c014b578 t proc_info_read c014b688 t mem_read c0131150 T sys_read c013121c T sys_write c0108d2c T system_call c0108d64 T ret_from_sys_call c010 t startup_32 c0100139 t is486 xmms D CACC5EA8 4116 713155 715 (NOTLB)1493 674 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] c01248e4 T ___wait_on_page c0124984 t __lock_page c01240dc t truncate_list_pages c0124268 T truncate_inode_pages c01242d4 t writeout_one_page c0144094 T remove_inode_hash c01440a8 T iput c01441fc T force_delete c01422a0 T dput c01423e4 T d_invalidate c0131c58 T fput c0131d28 T fget c012365c t unmap_fixup c0123788 t free_pgtables c012380c T do_munmap c0123a5c T sys_munmap ...ask if you want more xmms S C2979F30 0 715713 725 (NOTLB) Call Trace: [] [] [] [] [] [] xmms S C2B75F2C 1156 716715(NOTLB) 718 Call Trace: [] [] [] [] [] xmms S 7FFF 0 718715(NOTLB) 719 716 Call Trace: [] [] [] [] xmms S C2975F88 832 719715(NOTLB) 725 718 Call Trace: [] [] [] [] [] xmms S CA8D7F88 2672 725715(NOTLB) 719 Call Trace: [] [] [] [] c0114240 t process_timeout c0114288 T schedule_timeout c011431c T schedule_tail c0113d70 t remap_area_pages c0114020 T __ioremap c0108d2c T system_call c0108d64 T ret_from_sys_call lsD CA98B3DC 0 1896222(NOTLB) Call Trace: [] [] [] [] [] [] skill D CA98B3DC 0 1897187(NOTLB) Call Trace: [] [] [] [] [] [] c0107964 T __down_interruptible c0107a28 T __down_trylock c0107a60 T __down_failed c0107a6c T __down_failed_interruptible c02f6a00 T stext_lock c02f827e A _etext ... SysRq: Show Memory Mem-info: Free pages:2240kB ( 0kB HighMem) ( Active: 4153, inactive_dirty: 198, inactive_clean: 1077, free: 560 (383 766 1149) ) 31*4kB 1*8kB 1*16kB 0*32kB 0*64kB 0*128kB 0*256kB 1*512kB 0*1024kB 0*2048kB = 660kB) 125*4kB 5*8kB 1*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 1*1024kB 0*2048kB = 1580kB) = 0kB) Swap cache: add 3165, delete 547, find 25/124 Free swap:53104kB 49136 pages of RAM 0 pages of HIGHMEM 1798 reserved pages 2619 pages shared 2618 pages swap cached 0 pages in page table cache Buffer memory: 1276kB -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 - 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/
broken Cyrix 486 cpuinfo in 2.4.0
Hello, finally got around to upgrading my old cyrix 486-66 box to 2.4.0 [compiled it locally for the first time since the 2.1.1xx series. It took about 3.5 hours to compile the kernel. make dep took 30 minutes. make menuconfig was almost so slow as to be unusable]. In any case, the CPU is incorrectly reported as a NexGen chip, of all things. It was reported correctly in 2.2.x I do remember someone mentioning that the new cpuinfo code in 2.4.x might be untested on older chips. In any case attached is the 2.4 and 2.2 cpuinfo files. If I get a chance I might try to sort this out myself. Vince 2.4.0: (incorrect) processor : 0 vendor_id : NexGenDriven cpu family : 4 model : 0 model name : ff/00 stepping: unknown fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : no cpuid level : -1 wp : yes flags : bogomips: 26.52 2.2.16: (correct) processor : 0 vendor_id : CyrixInstead cpu family : 4 model : 4 model name : Cx486DX2 stepping: 2 fdiv_bug: no hlt_bug : no sep_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : -1 wp : yes flags : bogomips: 26.52 -- \ /\ /\ / Vince Weaver http://www.deater.net/weave \/__\/__\/ [EMAIL PROTECTED] Linux 2.4.0 on a K6-2+ - 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/
Re: hotmail not dealing with ECN
On Sat, 27 Jan 2001, Frank v Waveren wrote: > Why? Why not just zero them, and get both security and compatibility... > the problem is that you don't know what they mean, just zeroing them may break things (how will the sender know that you zeroed them). David Lang - 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/
SMP Athlon...(a quiet question)
ER, they work but must compile as PII/Celeron :-( A bunch of memcpy header stuff fails to compile current is one of the left overs in some cases. I will dive deeper in monday, just wanting some feed back first. Cheers, 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] Please read the FAQ at http://www.tux.org/lkml/
Re: VM breakdown, 2.4.0 family
On Sat, 27 Jan 2001, David Ford wrote: > I have Marcelo's patch. It isn't applicable because I am purposely not enabling any > swap. The problem is the system gets down to about 7 megs of buffers free and within > three seconds has become functionally dead. Zero response on any user input/output > device save the magic key. > > The system will then grind the harddrive solid for about 25-30 minutes then > everything will go silent. > > The brokenness is that the OOM code never activates. Can you show the result of Alt+SysRq+M when the system is dead? Thanks - 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/
Re: kernel boot problems
Maybe try enabling ATA/IDE driver as the configuration at compile time has changed. Using an old 2.2 '.config' will fail to enable the subsystem. However using a 2.4'.config' on a 2.2 compile will generally succeed in 90% of the flags. Cheers, On Sun, 28 Jan 2001, Derek Benson wrote: > Ryan> Hello all, > > Hi > > Ryan> I was wondering if someone might be able to help me. I have > Ryan> just compiled my kernel and set it up on a floppy to boot off a > Ryan> disk. I have it then use an image file to uncompress and get > Ryan> the filesystem off ,etc. Well when it boots it says it has > Ryan> uncompressed the filesystem image and then gives me this: > Ryan> Mounted Root (ext2 filesystem) readonly Freeing unused kernel > Ryan> memory: 212K freed Warning: unable to open an initial console > Ryan> Kernel panic: no init found. Try passing init= option to the > Ryan> kernel. > > Ryan> I know that I have init on the image, so what could I be doing > Ryan> wrong. It is probably something stupid that I am overlooking, > Ryan> but I thank you in advance. > > This is commonly seen when your /etc/fstab is pointing to the wrong partion > for root, or (I believe) on some older kernels where the location of the root > partition is contained within the kernel or on the boot sector somewhere. > (Forgive me for not being more explicit my memory fails me) Try man rdev > for changeing these values. > > Of course as someone else has noted there could be other reasons, but if > you are looking for something 'stupid' (believe me I've done this before > too) then this could be it. > > Try passing 'root=/dev/hda2' or whatever (without the '') to the kernel > at the boot prompt: > > lilo: linux root=/dev/hda1 single > > Replace linux above with the alias of your kernel. > > If you don't know what partiion root is on you can always cycle through > the partitions consecutively. (I've done this before when breaking into > linux boxes that I didn't build but had the job of maintaining). > > Once you have booted into single mode you can edit /etc/fstab to point to > the right place. Or else if thats correct just boot up with linux root=blah > and you'll be up and running! > > Hope this helps. > > derek > - > 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/ > 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] Please read the FAQ at http://www.tux.org/lkml/
Re: ps hang in 241-pre10
On Sat, Jan 27, 2001 at 04:42:45PM -0800, J Sloan wrote: > But at least the sound card was in use, FWIW - Not for me. My xmms was sitting idle when it froze. - 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/
Re: ps hang in 241-pre10
Sorry, there was no xmms involved here - The behavior occurred while playing unreal tournament. But at least the sound card was in use, FWIW - jjs David Ford wrote: > We've narrowed it down to "we're all running xmms" when it happend. > > -d > > J Sloan wrote: > > > Just for the record, the system where I saw the problem > > has only ext2 - > > -- > 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 > > - > 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/ - 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/
Re: ps hang in 241-pre10
Linus Torvalds wrote: > In article <[EMAIL PROTECTED]>, David Ford <[EMAIL PROTECTED]> > wrote: > > > >We've narrowed it down to "we're all running xmms" when it happend. > > Does anybody have a clue about what is different with xmms? Not sure. > Does it use KNI if it can, for example? We used to have a problem with > KNI+Athlons, for example. > > It might also be that it's threading-related, and that XMMS is one of > the few things that uses threads. Things like that. I'm not an XMMS > user, can somebody who knows XMMS comment on things that it does that > are unusual? If I was clued enough to know KNI, I could say for a certainty. I am assuming it's a form of MMX or related. My notebook is a mobile pII 366. I'm stress testing it now with ac12. I originally had pre9 on it. There is one difference other than that, I have Marcelo's bg aging patch on here which seems to have improved responsiveness significantly but I'll save that for another story. I've triggered it, report follows in next email. -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 - 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/
Re: patch for 2.4.0 disable printk
Stefani Seibold wrote:
>
> Second, i had change the macro so it calls now a inline funciton
> printk_inline which always return 0. So it should be now compatibel to the
> standard printk funciton.
A #define is better.
You see, even if printk is a null inline function,
printk("foo");
will still cause "foo" to appear in your output. Apparently
very recent versions of gcc have fixed this.
BTW: Graham Stoney prepared a similar patch for 2.2 last year.
You may be able to borrow some ideas from that work, and the
followup discussion.
http://www.uwsg.iu.edu/hypermail/linux/kernel/0004.2/0709.html
-
-
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/
Re: ps hang in 241-pre10
This system is the following: AcerOPEN AP53/AX Motherboard, Intel Pentium 200Mhz w/o MMX (1996-1997) Chipsets: 430HX, PIIX3 (EIDE) 64MB RAM EDO 60ns (Kingston brand) Linus Torvalds wrote: > In article <[EMAIL PROTECTED]>, David Ford <[EMAIL PROTECTED]> > wrote: > > > >We've narrowed it down to "we're all running xmms" when it happend. > > Does anybody have a clue about what is different with xmms? > > Does it use KNI if it can, for example? We used to have a problem with > KNI+Athlons, for example. > > It might also be that it's threading-related, and that XMMS is one of > the few things that uses threads. Things like that. I'm not an XMMS > user, can somebody who knows XMMS comment on things that it does that > are unusual? > > Linus > - > 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/ - 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/
Re: VM breakdown, 2.4.0 family
On Sat, 27 Jan 2001, David Ford wrote: > Since the testN series and up through ac12, I experience total loss of > control when memory is nearly exhausted. > > I start with 256M and eat it up with programs until there is only about > 7 megs left, no swap. From that point all user processes stall and the > disk begins to grind nonstop. It will continue to grind for about 25-30 > minutes until it goes completely silent. No processes get killed, no VM > messages are emitted. > > The only recourse is the magic key. If I reboot before the disk goes > silent I can cleanly kill X with sysrq-E and restart. > > If I wait until it goes silent, all is lost. I have to sysrq-SUB. > > Note, I do not have ANY swap enabled for these tests. > Could you try this patch and tell the result? http://bazar.conectiva.com.br/~marcelo/patches/v2.4/2.4.1pre10/bg_page_aging.patch Thanks - 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/
Re: ECN: Clearing the air
On Sat, 27 Jan 2001, jamal wrote: > > - ECN does not break things. It's brain damaged firewalls, Intrusion > detection systems, and load balancers that should be shot. > One intrusion detection "expert" was quoted suggesting the blocking of ECN > bits should be blocked because "nmap uses them" to probe systems. > should proof read before posting. The intrusion detection expert suggested blocking ECN. Article at: http://www.securityfocus.com/frames/?focus=ids&content=/focus/ids/articles /portscan.html cheers, jamal - 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/
Re: ps hang in 241-pre10
In article <[EMAIL PROTECTED]>, David Ford <[EMAIL PROTECTED]> wrote: > >We've narrowed it down to "we're all running xmms" when it happend. Does anybody have a clue about what is different with xmms? Does it use KNI if it can, for example? We used to have a problem with KNI+Athlons, for example. It might also be that it's threading-related, and that XMMS is one of the few things that uses threads. Things like that. I'm not an XMMS user, can somebody who knows XMMS comment on things that it does that are unusual? Linus - 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/
Re: Renaming lost+found
> A file-system without a lost+found directory is like love without sex. You mean, possible but leaving you unsatisfied? Well, I think a file system without a lost+found is a lot worse. Thunder --- Woah... I did a "cat /boot/vmlinuz >> /dev/audio" - and I think I heard god... - 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/
Re: Probably Off-topic Question...
Mark Smith wrote: > > On Fri, Jan 26, 2001 at 11:02:05AM -0700, Thunder from the hill wrote: > > > > > my vaio F-series used to sleep correctly under RH6.1. it now hangs > > > > > forever making the sleep mode much less useful. > > > i just push the sleep button. it used to work under RH6.1. under RH7.0 > > > it never wakes up. > > Well, this seems not to be right... > > Already any idea? > > i haven't had a chance to look at it. i'm not quite sure where to start > looking either. i suppose i could track down if there's any resource > still running? trying out different configurations. it's kinda annoying. > the battery drain on linux is pretty high so it would be useful to sleep > to save juice. not quite annoying enough yet to start debugging though. > too many other things above it on the sliding scale. Hmmm... Can you access objects on the penguin via network? Try using telnet, or better ssh, to be sure if it is a crash or a graphic error. Thunder --- Woah... I did a "cat /boot/vmlinuz >> /dev/audio" - and I think I heard god... - 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/
ECN: Clearing the air (fwd)
Just proves i am not on lk -- Forwarded message -- Date: Sat, 27 Jan 2001 19:05:38 -0500 (EST) From: jamal <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: ECN: Clearing the air On Fri, 26 Jan 2001 15:29:51 +, James Sutherland wrote: > Except you can't retry without ECN, because DaveM wants to do a > Microsoft and force ECN on everyone, whether they like it or not. I think there is some serious misinformation going on here. Hopefully, this will straighten things out: - ECN is not a standard that DaveM came up with, or some cabal within the Linux community pulled out of a hat. It was the Internet Engineering Task Force that endorsed it. If you want to blame anybody, blame the IETF. Specifically you should also blame Sally Floyd and KK Ramakrishnan who proposed it after years of research. In case those names dont ring a bell look, them up in the internet whos-who almanac. Dont ask me where you'll find one. In case the IETF doesnt ring a bell either to some people, it is the same standard body that made the internet happen. It is the same standard body that also ensures that although the internet is anarchical in nature, there are some simple governing rules that should be defined to keep it alive. They are called protocols. The IETF has a very simple motto "we believe in running code ...". [Although that's not neccesarily true these days, but let's not tread there]. People, Linux is no longer a baby. We are leaders as far as the internet is concerned. We are there first. We set trends and other follow. We have "running code" to flush out all the heretics out there. We have the best TCP/IP people in the world today coding for you and i. Blaspheming with "DaveM wants to pull a MS" doesnt help. We need to encourage these kind of activities because we are making the internet a better place. Yes, Al Gore might have funded some good causes on the internet, but today _we_ make them happen. - ECN is a good thing. It has been proven for years to be a good thing. Standards normally go through a experimental phase before becoming proposed standard. If you dont want it turn it off. - ECN is going to become a proposed standard perhaps by this coming IETF at Mineapolis. - A lot of OS vendors and good router vendors will be deploying ECN soon. There is nothing wrong with Linux being first. We code in the open, others prefer press releases. - ECN does not break things. It's brain damaged firewalls, Intrusion detection systems, and load balancers that should be shot. One intrusion detection "expert" was quoted suggesting the blocking of ECN bits should be blocked because "nmap uses them" to probe systems. Any commercial non-open-source entity designing and abusing reserved fields should at least have the courtesy of providing a config option to stop that abuse. If it was open source we would have fixed their sins. - Any design which blatantly ASSumes that "reserved" means no one should use something simply amazes me. The collegiate dictionary definition of "reserved" is: - Main Entry: reserve Pronunciation: ri-'z&rv Function: transitive verb Inflected Form(s): reserved; reserving Etymology: Middle English, from Middle French reserver, from Latin reservare, literally, to keep back, from re- + servare to keep -- more at CONSERVE Date: 14th century 1 a : to hold in reserve : keep back b : to set aside (part of the consecrated elements) at the Eucharist for future use c : to retain or hold over to a future time or place : DEFER d : to make legal reservation of 2 : to set or have set aside or apart synonym see KEEP - reservable /-'z&r-v&-b&l/ adjective --- Now where is the ambiguity in that? And where really is the ambiguity in the meaning of a TCP RST? Maybe an analogy in a very ambiguos protocol called "English Language" would help. The word "no" in response to the packet "davem please add an extra meaning to RST". Where is the ambiguity in that? phew! just my 2 .ca cents cheers, jamal - 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/
Re: kernel boot problems
Ryan> Hello all, Hi Ryan> I was wondering if someone might be able to help me. I have Ryan> just compiled my kernel and set it up on a floppy to boot off a Ryan> disk. I have it then use an image file to uncompress and get Ryan> the filesystem off ,etc. Well when it boots it says it has Ryan> uncompressed the filesystem image and then gives me this: Ryan> Mounted Root (ext2 filesystem) readonly Freeing unused kernel Ryan> memory: 212K freed Warning: unable to open an initial console Ryan> Kernel panic: no init found. Try passing init= option to the Ryan> kernel. Ryan> I know that I have init on the image, so what could I be doing Ryan> wrong. It is probably something stupid that I am overlooking, Ryan> but I thank you in advance. This is commonly seen when your /etc/fstab is pointing to the wrong partion for root, or (I believe) on some older kernels where the location of the root partition is contained within the kernel or on the boot sector somewhere. (Forgive me for not being more explicit my memory fails me) Try man rdev for changeing these values. Of course as someone else has noted there could be other reasons, but if you are looking for something 'stupid' (believe me I've done this before too) then this could be it. Try passing 'root=/dev/hda2' or whatever (without the '') to the kernel at the boot prompt: lilo: linux root=/dev/hda1 single Replace linux above with the alias of your kernel. If you don't know what partiion root is on you can always cycle through the partitions consecutively. (I've done this before when breaking into linux boxes that I didn't build but had the job of maintaining). Once you have booted into single mode you can edit /etc/fstab to point to the right place. Or else if thats correct just boot up with linux root=blah and you'll be up and running! Hope this helps. derek - 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/
Re: hotmail not dealing with ECN
On Sat, Jan 27, 2001 at 11:09:27PM +, James Sutherland wrote: > On Sat, 27 Jan 2001, David Schwartz wrote: > > > > > > Firewalling should be implemented on the hosts, perhaps with centralized > > > policy management. In such a situation, there would be no reason to filter > > > on funny IP options. > > > > That's madness. If you have to implement your firewalling on every host, > > what do you do when someone wants to run a new OS? Forbid it? > > Of course. Then you find out about some new problem you want to block, so > you spend the next week reconfiguring a dozen different OS firewalling > systems. Hrm... I'll stick with a proper firewall, TYVM! It's this kind of ignorance that makes the internet a less secure and stable place. The network should not be a stateful device. If you need stateful firewalling the only place it should be implimented is on the end node. If management of that is a problem, then make an interface solve that problem insted of breaking the damn network. - 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/
Re: hotmail not dealing with ECN
On Sat, Jan 27, 2001 at 02:18:31PM -0800, David Schwartz wrote: > > Firewalling should be implemented on the hosts, perhaps with centralized > > policy management. In such a situation, there would be no reason to filter > > on funny IP options. > > That's madness. If you have to implement your firewalling on every host, > what do you do when someone wants to run a new OS? Forbid it? No a standard management interface would be followed by every host. Not unlike configuring your ipaddress with DHCP. - 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/
Re: ps hang in 241-pre10
At the time I had temporary access to my notebook and had a mismatched System.map file :S -d Linus Torvalds wrote: > In article <[EMAIL PROTECTED]>, David Ford <[EMAIL PROTECTED]> wrote: > >I can quickly and easily duplicate it on my notebook by playing music or > >mpegs in xmms. It may take a few minutes but it's guaranteed. > > > >xmms stalls flat on it's face and anything accessing /proc stalls. If I get > >the time to do it, I'll take a gander at it with kdb. > > Please, if you see something like this, just do a simple > followed by while in text-mode. The > magic keystrokes will give a stack trace of the currently running > process and all processes respectively. -- 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 - 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/
Re: CBQ simply doesn't work
> #!/bin/bash > /sbin/insmod cls_fw > /sbin/insmod sch_prio > /sbin/insmod sch_cbq > /sbin/insmod cls__u32 myne here is cls_u32 > insmod: a module named sch_cbq already exists > insmod: cls__u32: no module by that name found but i use 2.4... and i just feel your classifier cannot work anymore... because of this module. Well, this just intrigue me... i just feel i could have done some similar mystake.. Regards, patrick mourlhon - 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/
Re: ps hang in 241-pre10
We've narrowed it down to "we're all running xmms" when it happend. -d J Sloan wrote: > Just for the record, the system where I saw the problem > has only ext2 - -- 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 - 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/
Re: VM breakdown, 2.4.0 family
I have Marcelo's patch. It isn't applicable because I am purposely not enabling any swap. The problem is the system gets down to about 7 megs of buffers free and within three seconds has become functionally dead. Zero response on any user input/output device save the magic key. The system will then grind the harddrive solid for about 25-30 minutes then everything will go silent. The brokenness is that the OOM code never activates. -d Ed Tomlinson wrote: > David Ford Wrote: > > >Since the testN series and up through ac12, I experience total loss of > >control when memory is nearly exhausted. > > > >I start with 256M and eat it up with programs until there is only about > >7 megs left, no swap. From that point all user processes stall and the > >disk begins to grind nonstop. It will continue to grind for about 25-30 > >minutes until it goes completely silent. No processes get killed, no VM > >messages are emitted. > > > >The only recourse is the magic key. If I reboot before the disk goes > >silent I can cleanly kill X with sysrq-E and restart. > > > >If I wait until it goes silent, all is lost. I have to sysrq-SUB. > > You might want to try: > > http://bazar.conectiva.com.br/~marcelo/patches/v2.4/2.4.1pre10/bg_page_aging.patch > > or > > ftp://ftp.cam.org/users/tomlins/pte_aging_limit_swaps.diff > > The first patch from Marcelo fixes a problem with aging the wrong pages. The > second patch is sort of a 'best of Marcelo' patch. It contains the aging fix > and adds conditional bg pte aging (if with activate fast than we age > down...). It also has code to trottle swapouts when under preasure - it only > swaps out as much as we need now. > > I have fives days of uptime with it here (on test9 and test10). > > Feedback Welcome, > > Ed Tomlinson <[EMAIL PROTECTED]> -- 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 - 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/
Re: routing between different subnets on same if.
In article <[EMAIL PROTECTED]>, Paul Jakma <[EMAIL PROTECTED]> wrote: >On Sat, 27 Jan 2001, Miquel van Smoorenburg wrote: > >> Did you enable forwarding with echo 1 > /proc/sys/net/ipv4/ip_forward ? >> > >yes. the machine already routes correctly between the 2 subnets and >the internet which is on a seperate interface. i also disabled >/proc/sys/net/ipv4/conf/all/send_redirects, to no avail. What about /proc/sys/net/ipv4/conf/*/rp_filter ? Should be zero for the 192.* interface(s), I think. Mike. - 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/
RE: hotmail not dealing with ECN
On Sat, 27 Jan 2001, David Schwartz wrote: > > > Firewalling should be implemented on the hosts, perhaps with centralized > > policy management. In such a situation, there would be no reason to filter > > on funny IP options. > > That's madness. If you have to implement your firewalling on every host, > what do you do when someone wants to run a new OS? Forbid it? Of course. Then you find out about some new problem you want to block, so you spend the next week reconfiguring a dozen different OS firewalling systems. Hrm... I'll stick with a proper firewall, TYVM! James. - 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/
CBQ simply doesn't work
I can't get the CBQ running on 2.2.17. Alexey look like he doesn't reply to his mails. I made one more man to check it over me. We both can't find a problem. The file with config info is attached. Eager for any idea Clock This is an excerpt from the kernel configuration: [*] QoS and/or fair queueing CBQ packet scheduler < > CSZ packet scheduler The simplest PRIO pseudoscheduler RED queue SFQ queue TEQL queue TBF queue [*] QoS support [*] Rate estimator [*] Packet classifier API Routing table based classifier Firewall based classifier U32 classifier Special RSVP classifier < > Special RSVP classifier for IPv6 [*] Ingres traffic policing ... [*] IP: multicasting [*] IP: advanced router This is a script that sets up the qos: #!/bin/bash /sbin/insmod cls_fw /sbin/insmod sch_prio /sbin/insmod sch_cbq /sbin/insmod cls__u32 /sbin/insmod cls_rsvp /sbin/insmod sch_red tc qdisc add dev ppp0 root handle 10: cbq bandwidth 28Kbit avpkt 1000 tc class add dev ppp0 parent 10:0 classid 10:1 cbq bandwidth 28Kbit rate 28Kbit allot 1514 weight 28Kbit prio 8 maxburst 20 avpkt 1000 tc class add dev ppp0 parent 10:1 classid 10:100 cbq bandwidth 28Kbit rate 16Kbit allot 1514 weight 16Kbit prio 5 maxburst 20 avpkt 1000 tc class add dev ppp0 parent 10:1 classid 10:200 cbq bandwidth 28Kbit rate 9Kbit allot 1514 weight 9Kbit prio 5 maxburst 20 avpkt 1000 tc class add dev ppp0 parent 10:1 classid 10:300 cbq bandwidth 28Kbit rate 3Kbit allot 1514 weight 3Kbit prio 5 maxburst 20 avpkt 1000 tc qdisc add dev ppp0 parent 10:100 sfq quantum 1514b perturb 15 tc qdisc add dev ppp0 parent 10:200 sfq quantum 1514b perturb 15 tc qdisc add dev ppp0 parent 10:300 sfq quantum 1514b perturb 15 This is what the script says when run just before testing: root@mspool:~# ./qos Using /lib/modules/2.2.17/misc/cls_fw.o insmod: a module named cls_fw already exists Using /lib/modules/2.2.17/misc/sch_prio.o insmod: a module named sch_prio already exists Using /lib/modules/2.2.17/misc/sch_cbq.o insmod: a module named sch_cbq already exists insmod: cls__u32: no module by that name found Using /lib/modules/2.2.17/misc/cls_rsvp.o insmod: a module named cls_rsvp already exists Using /lib/modules/2.2.17/misc/sch_red.o insmod: a module named sch_red already exists Config listings: root@mspool:~# tc qdisc show qdisc sfq 8036: dev ppp0 quantum 1514b perturb 15sec qdisc sfq 8035: dev ppp0 quantum 1514b perturb 15sec qdisc sfq 8034: dev ppp0 quantum 1514b perturb 15sec qdisc cbq 10: dev ppp0 rate 28Kbit (bounded,isolated) prio no-transmit root@mspool:~# tc class show dev ppp0 class cbq 10: root rate 28Kbit (bounded,isolated) prio no-transmit class cbq 10:100 parent 10:1 leaf 8034: rate 16Kbit prio 5 class cbq 10:1 parent 10: rate 28Kbit prio no-transmit class cbq 10:200 parent 10:1 leaf 8035: rate 9Kbit prio 5 class cbq 10:300 parent 10:1 leaf 8036: rate 3Kbit prio 5 root@mspool:~# tc filter show dev ppp0 filter parent 10: protocol ip pref 25 u32 filter parent 10: protocol ip pref 25 u32 fh 802: ht divisor 1 filter parent 10: protocol ip pref 25 u32 fh 802::800 order 2048 key ht 802 bkt 0 flowid 10:300 match 3e50554d/ at 16 filter parent 10: protocol ip pref 25 u32 fh 801: ht divisor 1 filter parent 10: protocol ip pref 25 u32 fh 801::800 order 2048 key ht 801 bkt 0 flowid 10:200 match 3e50554c/ at 16 filter parent 10: protocol ip pref 25 u32 fh 800: ht divisor 1 filter parent 10: protocol ip pref 25 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 10:100 match 3e50554a/ at 16 filter parent 10: protocol ip pref 50 u32 filter parent 10: protocol ip pref 50 u32 fh 802: ht divisor 1 filter parent 10: protocol ip pref 50 u32 fh 802::800 order 2048 key ht 802 bkt 0 flowid 10:300 match 3e50554d/ at 16 filter parent 10: protocol ip pref 50 u32 fh 801: ht divisor 1 filter parent 10: protocol ip pref 50 u32 fh 801::800 order 2048 key ht 801 bkt 0 flowid 10:200 match 3e50554c/ at 16 filter parent 10: protocol ip pref 50 u32 fh 800: ht divisor 1 filter parent 10: protocol ip pref 50 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 10:100 match 3e50554a/ at 16 filter parent 10: protocol ip pref 100 u32 filter parent 10: protocol ip pref 100 u32 fh 802: ht divisor 1 filter parent 10: protocol ip pref 100 u32 fh 802::800 order 2048 key ht 802 bkt 0
[PATCH] dynamic IP support for 2.4.0 (SIOCKILLADDR)
When the IP address of an interface changes, TCP connections with the
old source address are useless. Applications are not notified of this
and time out ordinarily, just as if nothing had happened. This is
behaviour isn't very helpful when you have a dynamic IP and know
you're probably not going to get the old one back. In that case, you
want processes to get errors when they try to use one of the dead
connections, so they can handle the disconnect more cleanly. Otherwise
fetchmail, etc. can just hang waiting for ages. Andi Kleen implemented
this functionality with a per interface flag in 2.2. See
ftp.suse.com:/pub/people/ak/v2.2/iff-dynamic*.
The following patch against 2.4.0 does it a different way. It
introduces a new ioctl, called SIOCKILLADDR. When this ioctl is
called, it makes all IPv4 sockets with the specified source address
return -ENETRESET when they are used.
Is this the right error number? I wasn't quite sure where the ioctl
should go to be in keeping with convention - I bunged it in
devinet_ioctl.
I patched userspace ppp-2.4.0 to use this functionality. It would be
better if SIOCKILLADDR were not used until we are sure that the new IP
is in fact different from the old one, but pppd in demand mode would
not notice that there were extant connections and so would not bring
up the link - so the problem would not be alleviated. Therefore
SIOCKILLADDR is used on disconnect. The functionality is activated
with the killoldaddr option. I would be happy to document it in the
manpage if it were accepted. Further the build process is cleaned up
slightly, as in the patch I sent on or around 8 October 2000.
diff -u --exclude *~ --recursive linux-2.4.0-orig/include/linux/sockios.h linux-hacked-dynip/include/linux/sockios.h
--- linux-2.4.0-orig/include/linux/sockios.h Sat Dec 30 00:20:32 2000
+++ linux-hacked-dynip/include/linux/sockios.h Sat Jan 27 17:04:34 2001
@@ -65,6 +65,7 @@
#define SIOCDIFADDR 0x8936 /* delete PA address */
#define SIOCSIFHWBROADCAST 0x8937 /* set hardware broadcast addr */
#define SIOCGIFCOUNT 0x8938 /* get number of devices */
+#define SIOCKILLADDR 0x8939 /* kill all connections with this local address */
#define SIOCGIFBR 0x8940 /* Bridging support */
#define SIOCSIFBR 0x8941 /* Set bridging options */
diff -u --exclude *~ --recursive linux-2.4.0-orig/include/net/tcp.h linux-hacked-dynip/include/net/tcp.h
--- linux-2.4.0-orig/include/net/tcp.h Fri Jan 5 21:41:37 2001
+++ linux-hacked-dynip/include/net/tcp.h Sat Jan 27 18:02:21 2001
@@ -787,9 +787,8 @@
extern int tcp_disconnect(struct sock *sk, int flags);
extern void tcp_unhash(struct sock *sk);
-
extern int tcp_v4_hash_connecting(struct sock *sk);
-
+extern void tcp_v4_zap_saddr(u32 saddr);
/* From syncookies.c */
extern struct sock *cookie_v4_check(struct sock *sk, struct sk_buff *skb,
diff -u --exclude *~ --recursive linux-2.4.0-orig/net/ipv4/af_inet.c linux-hacked-dynip/net/ipv4/af_inet.c
--- linux-2.4.0-orig/net/ipv4/af_inet.c Tue Jan 2 09:26:19 2001
+++ linux-hacked-dynip/net/ipv4/af_inet.c Sat Jan 27 18:27:38 2001
@@ -854,6 +854,7 @@
case SIOCSIFPFLAGS:
case SIOCGIFPFLAGS:
case SIOCSIFFLAGS:
+ case SIOCKILLADDR:
return(devinet_ioctl(cmd,(void *) arg));
case SIOCGIFBR:
case SIOCSIFBR:
diff -u --exclude *~ --recursive linux-2.4.0-orig/net/ipv4/devinet.c linux-hacked-dynip/net/ipv4/devinet.c
--- linux-2.4.0-orig/net/ipv4/devinet.c Sat Dec 30 00:22:05 2000
+++ linux-hacked-dynip/net/ipv4/devinet.c Sat Jan 27 21:09:48 2001
@@ -510,6 +510,7 @@
case SIOCSIFBRDADDR: /* Set the broadcast address */
case SIOCSIFDSTADDR: /* Set the destination address */
case SIOCSIFNETMASK: /* Set the netmask for the interface */
+ case SIOCKILLADDR: /* Kill all connections with this local address */
if (!capable(CAP_NET_ADMIN))
return -EACCES;
if (sin->sin_family != AF_INET)
@@ -536,7 +537,10 @@
break;
}
- if (ifa == NULL && cmd != SIOCSIFADDR && cmd != SIOCSIFFLAGS) {
+ if (ifa == NULL
+ && cmd != SIOCSIFADDR
+ && cmd != SIOCSIFFLAGS
+ && cmd != SIOCKILLADDR) {
ret = -EADDRNOTAVAIL;
goto done;
}
@@ -646,6 +650,9 @@
ifa->ifa_prefixlen = inet_mask_len(ifa->ifa_mask);
inet_insert_ifa(ifa);
}
+ break;
+ case SIOCKILLADDR: /* Kill all connections with this local address */
+ tcp_v4_zap_saddr(sin->sin_addr.s_addr);
break;
}
done:
diff -u --exclude *~ --recursive linux-2.4.0-orig/net/ipv4/tcp_ipv4.c linux-hacked-dynip/net/ipv4/tcp_ipv4.c
--- linux-2.4.0-orig/net/ipv4/tcp_ipv4.c Fri Jan 5 21:17:42 2001
+++ linux-hacked-dynip/net/ipv4/tcp_ipv4.c Sat Jan 27 18:07:25 2001
@@ -390,6 +390,38 @@
wake_up(&tcp_lhash_wait);
}
+/* Terminate all active connections with a local address equal to
+ * SADDR. If sysctl_ip_dynaddr is set, connections in the SYN_SENT
+ * state are not closed, because their source address will presumably
+ * be rewritten.
+ */
+void tcp_v4_zap_saddr(u32 saddr)
+{
+ int i;
+ rwlock_t *lock;
+ struct so
Re: Looking for comparison data on network stack prowess
David Ford writes: > I'm looking for some authoritative comparisons and discussions of the > current network stacks in *BSD and Linux. I.e. NET4 in Linux and > whatever is most current in *BSD. > > _PLEASE_ no flaming, no causing flamewar, nadda. > > I am writing an article for Linux.com and I am attempting to debunk > longstanding fallacies on both sides of the camp. I am aiming for a Start with the history: Net3 is not net3. Net2 is not net2. Linux did not steal the BSD stack. I recall that Alan Cox politely asked UCB to have it under the GPL, and was refused. It amazes me how Linux can be accused of stealing BSD network code while also being said to have poor network code... guess that means we broke it? Oh, BTW, BSD was _not_ the first OS with IP. The first was some horrid mainframe thing. Sometimes, he who codes last codes best. > truely neutral article which means I want to hear about the bad > as well as the good for both camps. Fair? Then this must be an equal-budget competition. SPECWeb99 is just that, with "infinity" as the budget. I think it has to be noted that BSDI has not accepted the challenge. That's just performance though, which isn't a problem for most people. I propose a feature and ease-of-use compatition. Each group gets to suggest a few interesting routing and firewalling problems. Maybe have a few Cisco and Microsoft fans try to stump us too. Then each group tries to find a solution that is fast, reliable, easy to understand, safe, easy to implement, and easy to maintain. The use of non-standard tools and patches is tolerated, but it greatly reduces your rank. (solutions can be tossed into a HOWTO as well) Example: You have a home LAN with one fixed IP address on an ISDN line, and another fixed IP address on a DSL line. You have domain names that point to the ISDN line's IP, and you want to convert over to using DSL exclusively. Connections initiated from outside ought to go out the way they came in (with the right IP!), and connections initiated from inside should go out the DSL line. There are plenty of ways the groups could challenge each other: PPPoE with dynamic IP assignment and decent firewall rules, bridging all packets with a Cisco MAC address, IPv6-to-IPv4, plain dial-on-demand into a strongly Microsoft-centric ISP, VLANs, a VPN, AppleTalk and IPX support, ECN bit removal, policy routing and bandwidth reservation... - 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/
Re: patch for 2.4.0 disable printk
Hi guys,
thanks for the feedback. This is now the second try of my disable printk
patch.
First i moved the option for disabling the prinbtk messages form the menu
character devices to kernel hacking.
Second, i had change the macro so it calls now a inline funciton
printk_inline which always return 0. So it should be now compatibel to the
standard printk funciton.
I hope you like the patch...
Greetings,
Stefani
-patch for 2.4.0 disable printk-
diff -u --recursive --new-file linux/Documentation/Configure.help
linux.noprintk/Documentation/Configure.help
--- linux/Documentation/Configure.help Thu Jan 4 22:00:55 2001
+++ linux.noprintk/Documentation/Configure.help Thu Jan 18 12:14:41 2001
@@ -12139,6 +12179,14 @@
If unsure, say Y, or else you won't be able to do much with your new
shiny Linux system :-)
+
+Disable kernel messages
+CONFIG_PRINTK
+ This option allows you to disable all kernel messages by overriding
+ the printk function with an empty macro.
+ On small embedded systems, this save a lot of rom and ram space. On
+ server or desktop systems you want human readable outputs, so it is
+ normally the best choice to say N to this option.
Support for console on virtual terminal
CONFIG_VT_CONSOLE
diff -u --recursive --new-file linux/include/asm-i386/spinlock.h
linux.noprintk/include/asm-i386/spinlock.h
--- linux/include/asm-i386/spinlock.h Thu Jan 4 23:50:46 2001
+++ linux.noprintk/include/asm-i386/spinlock.h Thu Jan 25 23:07:43 2001
@@ -5,8 +5,10 @@
#include
#include
+#ifndef CONFIG_PRINTK
extern int printk(const char * fmt, ...)
__attribute__ ((format (printf, 1, 2)));
+#endif
/* It seems that people are forgetting to
* initialize their spinlocks properly, tsk tsk.
diff -u --recursive --new-file linux/include/linux/kernel.h
linux.noprintk/include/linux/kernel.h
--- linux/include/linux/kernel.hMon Dec 11 21:49:54 2000
+++ linux.noprintk/include/linux/kernel.h Sat Jan 27 22:22:59 2001
@@ -68,8 +68,18 @@
extern int session_of_pgrp(int pgrp);
+#ifdef CONFIG_PRINTK
+#defineprintk(x...)printk_inline()
+
+static inline int printk_inline(void) __attribute__ ((const,unused));
+
+static inline int printk_inline(void) { return 0; }
+#else
+
asmlinkage int printk(const char * fmt, ...)
__attribute__ ((format (printf, 1, 2)));
+#endif
+
extern int console_loglevel;
diff -u --recursive --new-file linux/kernel/ksyms.c
linux.noprintk/kernel/ksyms.c
--- linux/kernel/ksyms.cWed Jan 3 01:45:37 2001
+++ linux.noprintk/kernel/ksyms.c Thu Jan 18 12:14:41 2001
@@ -439,7 +440,9 @@
/* misc */
EXPORT_SYMBOL(panic);
+#ifndef CONFIG_PRINTK
EXPORT_SYMBOL(printk);
+#endif
EXPORT_SYMBOL(sprintf);
EXPORT_SYMBOL(vsprintf);
EXPORT_SYMBOL(kdevname);
diff -u --recursive --new-file linux/kernel/printk.c
linux.noprintk/kernel/printk.c
--- linux/kernel/printk.c Sun Dec 31 03:16:13 2000
+++ linux.noprintk/kernel/printk.c Thu Jan 25 23:03:37 2001
@@ -25,7 +25,9 @@
#define LOG_BUF_LEN(16384)
#define LOG_BUF_MASK (LOG_BUF_LEN-1)
+#ifndef CONFIG_PRINTK
static char buf[1024];
+#endif
/* printk's without a loglevel use this.. */
#define DEFAULT_MESSAGE_LOGLEVEL 4 /* KERN_WARNING */
@@ -251,6 +253,20 @@
return do_syslog(type, buf, len);
}
+
+#ifdef CONFIG_PRINTK
+#undef printk
+
+#include
+
+asmlinkage int printk(const char *fmt, ...)
+{
+ return 0;
+}
+
+EXPORT_SYMBOL_NOVERS(printk);
+
+#else
asmlinkage int printk(const char *fmt, ...)
{
va_list args;
@@ -311,6 +322,7 @@
wake_up_interruptible(&log_wait);
return i;
}
+#endif
void console_print(const char *s)
{
diff -u --recursive --new-file linux/CREDITS linux.noprintk/CREDITS
--- linux/CREDITS Sun Dec 31 18:27:57 2000
+++ linux.noprintk/CREDITS Fri Jan 26 10:51:19 2001
@@ -2395,6 +2395,14 @@
S: Oldenburg
S: Germany
+N: Stefani Seibold
+E: [EMAIL PROTECTED]
+D: Possibility to disable all kernel messages by overload printk with a
+D: dummy macro (saves a lot of disk- and ramspace for embedded systems
+D: and rescue disks)
+S: Munich
+S: Germany
+
N: Darren Senn
E: [EMAIL PROTECTED]
D: Whatever I notice needs doing (so far: itimers, /proc)
diff -u --recursive --new-file linux/arch/alpha/config.in
linux.noprintk/arch/alpha/config.in
--- linux/arch/alpha/config.in Fri Dec 29 23:07:19 2000
+++ linux.noprintk/arch/alpha/config.in Sat Jan 27 22:37:20 2001
@@ -359,6 +359,7 @@
fi
bool 'Magic SysRq key' CONFIG_MAGIC_SYSRQ
+bool 'Disable kernel messages' CONFIG_PRINTK
bool 'Legacy kernel start address' CONFIG_ALPHA_LEGACY_START_ADDRESS
diff -u --recursive --new-file linux/arch/arm/config.in
linux.noprintk/arch/arm/config.in
--- linux/arch/arm/config.inThu Nov 16 21:51:28 2000
+++ linux.noprintk/arch/arm/config.in Sat Jan 27 22:34:57 2001
@@ -414,6 +414,7 @@
bool 'Verbose user fault messages' CONFIG_DEBUG_USER
bool 'Include debugging information in kernel binary' CONF
RE: hotmail not dealing with ECN
> Firewalling should be implemented on the hosts, perhaps with centralized > policy management. In such a situation, there would be no reason to filter > on funny IP options. That's madness. If you have to implement your firewalling on every host, what do you do when someone wants to run a new OS? Forbid it? DS - 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/
Re: routing between different subnets on same if.
On Sat, 27 Jan 2001, Miquel van Smoorenburg wrote: > Did you enable forwarding with echo 1 > /proc/sys/net/ipv4/ip_forward ? > yes. the machine already routes correctly between the 2 subnets and the internet which is on a seperate interface. i also disabled /proc/sys/net/ipv4/conf/all/send_redirects, to no avail. the setup is so: eth1: public IP eth0: 192.168.0/24 and 192.168.3/24 routing table has correct entries, the 2 private subnets are routed out thru dev eth0 with appropriate src. eventually i just installed a seperate NIC for 192.168.3/24 and it worked as i expected it to. however, i still need to know how to get linux 2.2 to do complete forwarding of packets between different logical subnets that share the same link.(i still have a couple more logical subnets that this machine has to route). So do i need a seperate NIC for each logical subnet? i'm sure i don't, but i don't see what i'm supposed to do with the 'ip' command? different scope or realm? or ... ?? > Mike. regards, -- Paul Jakma [EMAIL PROTECTED] [EMAIL PROTECTED] PGP5 key: http://www.clubi.ie/jakma/publickey.txt --- Fortune: "Nuclear war can ruin your whole compile." -- Karl Lehenbauer - 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/
Re: routing between different subnets on same if.
On Sat, 27 Jan 2001 [EMAIL PROTECTED] wrote: > did you install routed on the linux machine ? no i have my routes statically set, but that wouldn't make a difference. Routed just adds/deletes entries from the kernel table as neccessary and lets the kernel do the forwarding as neccessary. so it'd make no difference. regards, -- Paul Jakma [EMAIL PROTECTED] [EMAIL PROTECTED] PGP5 key: http://www.clubi.ie/jakma/publickey.txt --- Fortune: The greatest productive force is human selfishness. -- Robert Heinlein - 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/
Re: kernel boot problems
A few things come to mind: 1. Is your init statically linked or linked with shared libraries? If it's shared, do you have all the shared objects on your disk image in a place where they can be found (/lib, I hope)? You might try linking it statically (but stripped) just to make sure. 2. Is it in the path that the kernel is looking in? check init/main.c to see what your kernel is looking for (it's some educational reading anyway). 3. Even if 'init' isn't found, it should try to run /bin/sh as a last resort. I can't imagine you don't have one of those. 4. Is init executable? 5. "unable to open an initial console" probably means you don't have the necesary device nodes (refer to init/main.c) 6. If this doesn't help, there is a ramdisk FAQ that is well written... Good luck with it! Joe Ryan Hairyes wrote: > Hello all, > > I was wondering if someone might be able to help me. > I have just compiled my kernel and set it up on a floppy > to boot off a disk. I have it then use an image file to uncompress > and get the filesystem off ,etc. Well when it boots it says it has > uncompressed the filesystem image and then gives me this: > Mounted Root (ext2 filesystem) readonly > Freeing unused kernel memory: 212K freed > Warning: unable to open an initial console > Kernel panic: no init found. Try passing init= option to the kernel. > > I know that I have init on the image, so what could I be doing wrong. > It is probably something stupid that I am overlooking, but I thank you in > advance. > > Ryan > > - > 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/ - 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/
Re: es1371 freezes 2.4.0 hard
Quoth Jeff Garzik on Sat, Jan 27, 2001 at 09:22:45AM -0500: [...] > But removing pci_enable_device is incorrect; it merely avoids what > appears to be a bug with your Via irq routing. Would it be possible for > you to edit linux/arch/i386/kernel/pci-i386.h, and change the line near > the top from > #undef DEBUG > to > #define DEBUG 1 > and then send the output of 'dmesg -s 16384' to linux-kernel (and CC > me)? That will dump your PCI IRQ routing information, among other > details. Linux version 2.4.0 ([EMAIL PROTECTED]) (gcc version 2.95.3 20010111 (prerelease)) #9 Sat Jan 27 13:04:26 PST 2001 BIOS-provided physical RAM map: BIOS-e820: 0009fc00 @ (usable) BIOS-e820: 0400 @ 0009fc00 (usable) BIOS-e820: 0001 @ 000f (reserved) BIOS-e820: 0001 @ (reserved) BIOS-e820: 07ef @ 0010 (usable) BIOS-e820: d000 @ 07ff3000 (ACPI data) BIOS-e820: 3000 @ 07ff (ACPI NVS) On node 0 totalpages: 32752 zone(0): 4096 pages. zone(1): 28656 pages. zone(2): 0 pages. Kernel command line: BOOT_IMAGE=debug ro root=301 Initializing CPU#0 Detected 350.804 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 699.59 BogoMIPS Memory: 127048k/131008k available (822k kernel code, 3572k reserved, 293k data, 72k init, 0k highmem) Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes) Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 8192 (order: 4, 65536 bytes) CPU: Before vendor init, caps: 008021bf 808029bf , vendor = 2 CPU: L1 I Cache: 32K (32 bytes/line), D cache 32K (32 bytes/line) CPU: After vendor init, caps: 008021bf 808029bf 0002 CPU: After generic, caps: 008021bf 808029bf 0002 CPU: Common caps: 008021bf 808029bf 0002 CPU: AMD-K6(tm) 3D processor stepping 0c Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.37 (20001109) Richard Gooch ([EMAIL PROTECTED]) mtrr: detected mtrr type: AMD K6 PCI: BIOS32 Service Directory structure at 0xc00fafb0 PCI: BIOS32 Service Directory entry at 0xfb430 PCI: BIOS probe returned s=00 hw=11 ver=02.10 l=01 PCI: PCI BIOS revision 2.10 entry at 0xfb460, last bus=1 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: IDE base address fixup for 00:07.1 PCI: Scanning for ghost devices on bus 0 PCI: Scanning for ghost devices on bus 1 PCI: IRQ init PCI: Interrupt Routing Table found at 0xc00fde00 00:08 slot=01 0:01/deb8 1:02/deb8 2:03/deb8 3:05/deb8 00:09 slot=02 0:02/deb8 1:03/deb8 2:05/deb8 3:01/deb8 00:0a slot=03 0:03/deb8 1:05/deb8 2:01/deb8 3:02/deb8 00:0b slot=04 0:05/deb8 1:01/deb8 2:02/deb8 3:03/deb8 00:0c slot=05 0:01/deb8 1:02/deb8 2:03/deb8 3:05/deb8 00:07 slot=00 0:01/deb8 1:02/deb8 2:00/deb8 3:00/deb8 00:01 slot=00 0:01/deb8 1:02/deb8 2:03/deb8 3:05/deb8 PCI: Using IRQ router VIA [1106/0586] at 00:07.0 PCI: IRQ fixup 01:00.0: ignoring bogus IRQ 255 IRQ for 01:00.0:0 -> not found in routing table PCI: Allocating resources PCI: Resource e000-e3ff (f=1208, d=0, p=0) PCI: Resource e000-e00f (f=101, d=0, p=0) PCI: Resource e800-e83f (f=101, d=0, p=0) PCI: Resource ec00-ec7f (f=101, d=0, p=0) PCI: Resource e800-e87f (f=200, d=0, p=0) PCI: Resource e400-e4ff (f=200, d=0, p=0) PCI: Resource e600-e6ff (f=1208, d=0, p=0) PCI: Sorting device list... Activating ISA DMA hang workarounds. isapnp: Scanning for Pnp cards... isapnp: No Plug & Play device found Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 apm: BIOS version 1.2 Flags 0x07 (Driver version 1.14) Starting kswapd v1.8 Detected PS/2 Mouse Port. pty: 256 Unix98 ptys configured Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later VP_IDE: VIA vt82c586b IDE UDMA33 controller on pci0:7.1 ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA hda: WDC AC26400B, ATA DISK drive ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx hdc: ATAPI CD-ROM DRIVE 40X MAX, ATAPI CDROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: 12594960 sectors (6449 MB) w/512KiB Cache, CHS=784/255/63, UDMA(33) Partition check: /dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 > Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A 3c59x.c:LK1.1.11 13 Nov 2000 Donald Becker and others. http://www.scyld.com/network/vortex.html $Revision: 1.10
Re: Linux Post codes during runtime, possibly OT
Rogier Wolff wrote: > > You seem to state that if you want POST codes, you should find a > different port, modify the code, test the hell out of it, and then > submit the patch. > > That is NOT the right way to go about this: Port 0x80 is RESERVED for > POST usage, that's why it's always free. If people want to use it for > the original purpose then that is a pretty damn good reason to bump > the non-intended users of that port somewhere else. > Again, such bumping entails: - Modify the code - Test the hell out of it - Submit the patch > Now, we've found that small delays are reasonably well generated with > an "outb" to 0x80. So, indeed changing that to something else is going > to be tricky. > > All that I can think of right now is: > - Find a register that can be written without side effects in > "standard" hardware like a keyboard controller, or interrupt >controller. Especially good are ones that already require us to keep >a shadow value. Write the shadow variable to the register. > (Tricky: not interrupt safe!) > - Find a scratch register (like the one in the 16450). > > - Is port 0x81 possibly "quite often" free? > Who knows? That's the thing you're going to have to find out if you want to push this. Again, the only way anyone is ever going to find out is by doing *lots* of research (look at things like Ralf Brown's Interrupt List), *then* followed by lots and lots of testing to smoke out boxes that don't work for this. For what it's worth, I'm talking from experience -- I tried to switch it to port 0xED which I was told was used for this purpose by BIOS manufacturers. It didn't work. -hpa -- <[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - 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/
Re: [UPDATE] Zerocopy patches, against 2.4.1-pre10
Hi Alexey,
On Sat, 27 Jan 2001 [EMAIL PROTECTED] wrote:
> > fits the new Linux model a bit better, as it has one descriptor per
> > packet, not one per fragment (like the current implementation).
>
> Yes. Absence of such mode with acenic is big pain in ass.
And, at least for the starfire, using buffer descriptors eats up more
resources than using packet descriptors. So buffer descriptors are gone,
forever.
> Seems, this is pretty common bug. At least, perfect checksumming
> of chunks with any size and alignment is so big boast of
> alteon people, that it is clearly rather exception than rule. 8)8)
Oh well. Don't we wish hardware were perfect.. :-)
It's not too bad for the starfire, either, as it doesn't appear to suffer
from any alignment issues, and the only fragments it has problem with are
1-byte fragments (2-byte and larger are ok). And I'm still hoping that
Adaptec will release updated firmware (and that they will also approve the
inclusion of their firmware with the Linux driver).
If they don't approve it, maybe I'll add a config option so that the user
can download their own copy of the firmware from Adaptec's site, place it
in /etc somewhere, give the location to the driver and have the driver
open the files from kernel space and process them. It would be ugly
though, and a big PITA.
> I think you have to check for wrong combination of alignment/size and
> to call skb_checksum_help() and to disable checksumming if combination
> is bad.
Good, thanks a lot for the pointer. Maybe I went a bit overboard with my
fix, as I revert to CPU checksumming if *any* fragment (not just the last
one in the chain) has only 1 byte. But it seems to work well now.
I've attached a diff for the latest driver (and firmware) version, against
2.4.1pre10+zerocopy. Sorry about MIME, but my pine is currently broken
(strips trailing spaces/tabs).
And, one final question: is it worth it for me to extract just the Rx
checksumming changes and send them to Linux/Alan, or should I just wait
for zerocopy to be included?
Thanks,
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
diff -urNX diff_kernel_excludes
/usr/src/local/linux-2.4.vanilla/drivers/net/starfire.c
linux-2.4/drivers/net/starfire.c
--- /usr/src/local/linux-2.4.vanilla/drivers/net/starfire.c Fri Aug 11 15:57:58
2000
+++ linux-2.4/drivers/net/starfire.cSat Jan 27 12:44:35 2001
@@ -34,6 +34,10 @@
LK1.1.4 (jgarzik):
- Merge Becker version 1.03
+
+ LK1.2.0 (Ion Badulescu <[EMAIL PROTECTED]>)
+ - Support hardware Rx/Tx checksumming
+ - Add GFP firmware taken from Adaptec's Netware driver
*/
/* These identify the driver base version and may not be removed. */
@@ -43,11 +47,17 @@
" Updates and info at http://www.scyld.com/network/starfire.html\n";
static const char version3[] =
-" (unofficial 2.4.x kernel port, version 1.1.4, August 10, 2000)\n";
+" (unofficial 2.4.x kernel port, version 1.2.0, January 25, 2001)\n";
/* The user-configurable values.
These may be modified when a driver module is loaded.*/
+/*
+ * The current frame processor firmware fails to checksum a fragment
+ * of length 1. If and when this is fixed, the #define below can be removed.
+ */
+#define HAS_BROKEN_FIRMWARE
+
/* Used for tuning interrupt latency vs. overhead. */
static int interrupt_mitigation = 0x0;
@@ -117,12 +127,15 @@
#include
#include
+#include "starfire_firmware.h"
+
MODULE_AUTHOR("Donald Becker <[EMAIL PROTECTED]>");
MODULE_DESCRIPTION("Adaptec Starfire Ethernet driver");
MODULE_PARM(max_interrupt_work, "i");
MODULE_PARM(mtu, "i");
MODULE_PARM(debug, "i");
MODULE_PARM(rx_copybreak, "i");
+MODULE_PARM(interrupt_mitigation, "i");
MODULE_PARM(options, "1-" __MODULE_STRING(MAX_UNITS) "i");
MODULE_PARM(full_duplex, "1-" __MODULE_STRING(MAX_UNITS) "i");
@@ -256,19 +269,31 @@
TxThreshold=0x500B0,
CompletionHiAddr=0x500B4, TxCompletionAddr=0x500B8,
RxCompletionAddr=0x500BC, RxCompletionQ2Addr=0x500C0,
- CompletionQConsumerIdx=0x500C4,
+ CompletionQConsumerIdx=0x500C4, RxDMACtrl=0x500D0,
RxDescQCtrl=0x500D4, RxDescQHiAddr=0x500DC, RxDescQAddr=0x500E0,
RxDescQIdx=0x500E8, RxDMAStatus=0x500F0, RxFilterMode=0x500F4,
- TxMode=0x55000,
+ TxMode=0x55000, TxGfpMem=0x58000, RxGfpMem=0x5a000,
};
/* Bits in the interrupt status/mask registers. */
enum intr_status_bits {
- IntrNormalSummary=0x8000, IntrAbnormalSummary=0x0200,
- IntrRxDone=0x0300, IntrRxEmpty=0x10040, IntrRxPCIErr=0x8,
- IntrTxDone=0x4000, IntrTxEmpty=0x1000, IntrTxPCIErr=0x8,
- StatsMax=0x0800, LinkChange=0xf000,
- IntrTxDataLow=0x0004,
+ IntrLinkChange=0xf000, IntrStatsMax=0x0800,
+ IntrAbnormalSummary=0x0200, IntrGeneralTimer=0x0100,
+ Intr
Re: ps hang in 241-pre10
On Sat, Jan 27, 2001 at 04:33:42AM -0500, Shawn Starr wrote: > Yes, I have ReiserFS as well...hrm... I don't. - 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/
Re: Renaming lost+found
[EMAIL PROTECTED] writes: > On 01/26/01 01:19 PM James Lewis Nance <[EMAIL PROTECTED]> wrote: >> FWIW IBM's JFS file system does not have a lost+found directory. I dont >> remember if reiserfs does or not. > > Actually it does. > > From one of my rs/6000's sitting here, with a pretty much default AIX That is a completely different JFS. AIX 4 has an encumbered JFS that is tightly integrated into the VM system. IBM wrote a new JFS for OS/2 Warp Server. The new JFS is being ported to Linux and AIX 5. G should have called it jfs2 then. - 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/
Re: Linux Post codes during runtime, possibly OT
H. Peter Anvin wrote: > Rogier Wolff wrote: > > H. Peter Anvin wrote: > > > It output garbage to the 80h port in order to enforce I/O delays. > > > It's one of the safe ports to issue outs to. > > Yes, because it is reserved for POST codes. You can get "POST > > debugging cards" that simply have a BIN -> 7segement encoder and two 7 > > segment displays on them. They decode 0x80. That's what it's for. > Again, if you want to change it, find another safe port, test the hell > out of it, an *PUBLICIZE IT* so noone will use it in the future. I may have missed too much of the discussion, but I thought that the idea was that some people noted that their POST-code-cards don't really work all that well when Linux is running because Linux keeps on sending garbage to port 0x80. You seem to state that if you want POST codes, you should find a different port, modify the code, test the hell out of it, and then submit the patch. That is NOT the right way to go about this: Port 0x80 is RESERVED for POST usage, that's why it's always free. If people want to use it for the original purpose then that is a pretty damn good reason to bump the non-intended users of that port somewhere else. Now, we've found that small delays are reasonably well generated with an "outb" to 0x80. So, indeed changing that to something else is going to be tricky. All that I can think of right now is: - Find a register that can be written without side effects in "standard" hardware like a keyboard controller, or interrupt controller. Especially good are ones that already require us to keep a shadow value. Write the shadow variable to the register. (Tricky: not interrupt safe!) - Find a scratch register (like the one in the 16450). - Is port 0x81 possibly "quite often" free? Roger. -- ** [EMAIL PROTECTED] ** http://www.BitWizard.nl/ ** +31-15-2137555 ** *-- BitWizard writes Linux device drivers for any device you may have! --* * There are old pilots, and there are bold pilots. * There are also old, bald pilots. - 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/
check_dis(c|k)_change(|d): duplicated code
I was looking up linux code to find why /proc/partitions report 'hdc' instead of 'ide/host0/bus1/target0/lun0/cd' example: major minor #blocks name 8 01048575 scsi/host0/bus0/target6/lun0/disc 3 03140928 ide/host0/bus0/target0/lun0/disc 3 1 4000 ide/host0/bus0/target0/lun0/part1 3 23132864 ide/host0/bus0/target0/lun0/part2 3643167640 ide/host0/bus0/target1/lun0/disc 365 1 ide/host0/bus0/target1/lun0/part1 367 899136 ide/host0/bus0/target1/lun0/part3 368 165312 ide/host0/bus0/target1/lun0/part4 3691052289 ide/host0/bus0/target1/lun0/part5 370 983776 ide/host0/bus0/target1/lun0/part6 371 64480 ide/host0/bus0/target1/lun0/part7 22 0 648180 hdc I found a strange thing in 'fs/block_dev.c' there's a function 'check_disk_change' and in 'fs/devfs/base.c' there's a function 'check_disc_changed' They done exactly the same job. I think that one of these must be rewritted to call the other and it's not to me to tell you which one :-). -- Yann Droneaud <[EMAIL PROTECTED]> - 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/
Re: Linux Post codes during runtime, possibly OT
Rogier Wolff wrote: > > H. Peter Anvin wrote: > > Followup to: <[EMAIL PROTECTED]> > > By author:"Ian S. Nelson" <[EMAIL PROTECTED]> > > In newsgroup: linux.dev.kernel > > > > > > I'm curious. Why does Linux make that friendly 98/9a/88 looking > > > postcode pattern when it's running? DOS and DOS95 don't do that. > > > > > > I'm begining to feel like I can tell the system health by observing it, > > > kind of like "seeing the matrix." > > > It output garbage to the 80h port in order to enforce I/O delays. > > It's one of the safe ports to issue outs to. > > Yes, because it is reserved for POST codes. You can get "POST > debugging cards" that simply have a BIN -> 7segement encoder and two 7 > segment displays on them. They decode 0x80. That's what it's for. > Again, if you want to change it, find another safe port, test the hell out of it, an *PUBLICIZE IT* so noone will use it in the future. -hpa -- <[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt - 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/
Re: Renaming lost+found
Hi, On Fri, Jan 26, 2001 at 06:05:54PM -0200, Rodrigo Barbosa (aka morcego) wrote: > > I think JFS indeed doesn't have it. And ReiserFS doesn't too. This > should be common place for journaling filesystems. No, it's nothing to do with journaling or not. Even journaling filesystems can suffer IO errors or corrupt disk blocks, and any case where you have a file whose name has been lost due to such corruption needs to be dealt with by the fsck tool. Traditionally, fsck puts such files into lost+found, and in the presence of data corruption, it will still need to do so even with a journaling filesystem. ext3 uses lost+found in exactly the same way as ext2 for this reason. Cheers, Stephen - 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/
Re: the remount problem [2.4.0] kind of solved [patch]
Wichert Akkerman writes: > Previously Goswin Brederlow wrote: >> Maybe the kernel coud swap in the deleted libraries and keep it in >> memory or real swap from then on instead of blocking the fs. > > No, you have no idea how large the file might grow and you need to > keep that data somewhere. Grow? It makes little difference, since you can run out of filesystem space too. - 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/
Re: hotmail not dealing with ECN
On Sat, Jan 27, 2001 at 08:58:51PM +0100, Jamie Lokier wrote: [snip] > > I think that older Checkpoint firewalls (perhaps current?) zeroed out SACK > > on 'hide nat'ed connections. This causes unreasonable stalls for users on > > SACK enabled clients. Not cool. > > If both SACK and SACK_PERMITTED were zeroed out, the clients would > negotiate non-SACK connections and everythings ok. A performance > disadvantage relative to allowing SACK, but that's true of ECN as well. Some checkpoint firewalls have caused stalls on SACK enabled clients. I don't recall the exact configuration or method of action, but it does happen. I suspect that it didn't kill the SackOK but only the actual SACKs data. Breaking end-to-end is the path to maddness. Trusting practically any network that leaves a room is insane. Firewalling should be implemented on the hosts, perhaps with centralized policy management. In such a situation, there would be no reason to filter on funny IP options. - 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/
Re: SBF queueing?
Hello! > Has anyone decided to code a SFB (Stochastic Fair Blue) queue implementation > for Linux? I did not hear anything about this. > (http://www.eecs.umich.edu/~wuchang/blue/). The paper for it shows it > performing very well in comparison to RED. Yes, the algorithm looks interesting. Alexey - 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/
Re: hdd: set_drive_speed_status: status=0x51 { DriveReady SeekCompleteError }
On Sat, 27 Jan 2001, Jens Axboe wrote:
> On Sat, Jan 27 2001, Andre Hedrick wrote:
> > > I've been getting this during the boot sequence for quite some time now.
> > > They don't seem to impact the functionality of the drive any though. Just
> > > another extra-verbose kernel message I should ignore? :)
> > >
> > > (This is from the 2.4.1-pre10 btw.)
> > >
> > > hdd: CD-ROM TW 120D, ATAPI CD/DVD-ROM drive
> > > hdd: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
> > > hdd: set_drive_speed_status: error=0x04
> >
> > Means your device did not like that command and barfed.
> > status=0x51, error=0x04 == command aborted next
>
> My gut tells me that this is the 'get last written' command, and even
> with the quiet flag we get the IDE error status printed. Could you
> try and add
>
> goto use_toc;
>
> add the top of drivers/cdrom/cdrom.c:cdrom_get_last_written() and
> see if that makes the error disappear?
It is an ATA command not ATAPI.
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]
Please read the FAQ at http://www.tux.org/lkml/
Re: hotmail not dealing with ECN
Gregory Maxwell wrote: > > Why? Why not just zero them, and get both security and compatibility... > > Eeek! NO NO NO NO NO NO NO NO! > For ECN that would have worked, but that doesn't mean that something > couldn't have been implimented there that wouldn't have worked that way.. > > I think that older Checkpoint firewalls (perhaps current?) zeroed out SACK > on 'hide nat'ed connections. This causes unreasonable stalls for users on > SACK enabled clients. Not cool. If both SACK and SACK_PERMITTED were zeroed out, the clients would negotiate non-SACK connections and everythings ok. A performance disadvantage relative to allowing SACK, but that's true of ECN as well. -- Jamie - 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/
kernel boot problems
Hello all, I was wondering if someone might be able to help me. I have just compiled my kernel and set it up on a floppy to boot off a disk. I have it then use an image file to uncompress and get the filesystem off ,etc. Well when it boots it says it has uncompressed the filesystem image and then gives me this: Mounted Root (ext2 filesystem) readonly Freeing unused kernel memory: 212K freed Warning: unable to open an initial console Kernel panic: no init found. Try passing init= option to the kernel. I know that I have init on the image, so what could I be doing wrong. It is probably something stupid that I am overlooking, but I thank you in advance. Ryan - 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/
$B$*CN$i$;$G$9(B
28866 --- $B-j#J#M#P$N!X#E%a!<%k#D#M!Y$r$*FO$1CW$7$^$9!#(B --- -- http://www2.snowman.ne.jp/~nnet/ $B%N!<%9%M%C%H(B $B!&#C#G#IL5NA%@%&%s%m!<%I%Z!<%8(B $B!&7G<(HD!"%A%c%C%H!"%"%/%;%9%m%0!"%+%&%s%?!B??t$"$j(B $B!&%*!<%@!<#C#G#I$bhttp://www2.snowman.ne.jp/~nnet/ -- --- $B$3$N%a!<%k$O>pJsDs6!4k6H$+$i$N0MMj$K$h$j(B JMP$B$+$iG[?.$7$F$*$j$^$9!#(B $B-j%8%'%$%(%`%T!<(B [EMAIL PROTECTED] - 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/
Re: routing between different subnets on same if.
In article <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> wrote: >On Sat, 27 Jan 2001, Paul Jakma wrote: > >> On Sat, 27 Jan 2001 [EMAIL PROTECTED] wrote: >> >> > Hi Paul, >> > >> > I just think you might look for aliasing on your linux box. >> >> i have the aliasing, the aliased machine can ping IP's on both >> subnets. The machine is supposed to be a router though and clients on >> both subnets are setup to use it as their default router.. but it >> doesn't route... it notices that both IP's are on the same link and so >> just sends ICMP redirects. which doesn't help. :( >> >> i need linux to completely route between 2 IP's even though they are >> on the same link. Did you enable forwarding with echo 1 > /proc/sys/net/ipv4/ip_forward ? >did you install routed on the linux machine ? Routed is a daemon which speaks RIP to other routers. That isn't needed at all in this case. Mike. - 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/
Re: hdd: set_drive_speed_status: status=0x51 { DriveReady SeekCompleteError }
I gave it a whirl. Sadly, no change. On Sat, 27 Jan 2001, Jens Axboe wrote: > My gut tells me that this is the 'get last written' command, and even > with the quiet flag we get the IDE error status printed. Could you > try and add > > goto use_toc; > > add the top of drivers/cdrom/cdrom.c:cdrom_get_last_written() and > see if that makes the error disappear? -Jacob -- Reechani, Sentrosi, Vasi - 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/
Re: SBF queueing?
On Sat, Jan 27, 2001 at 07:52:32PM +0100, [EMAIL PROTECTED] wrote: > Hi Gregory! > You might have a look on linux/Documentation/networking/policy-routing.txt > I think this was down by Alexey Kuznetov Thanks for the quick reply. But that's not exactly what I was looking for. I was trying to find out if anyone was working on a peticular queueing algorithim that Linux doesn't currently have. > You might have a look to iproute + tc and HOWTO on advanced networking You mean this "HOWTO on advanced networking"? http://www.ds9a.nl/2.4Routing/ Look at the second authors name on the page. :) > patrick mourlhon - 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/
Re: hotmail not dealing with ECN
On Sat, Jan 27, 2001 at 02:20:32PM -0500, Gregory Maxwell wrote: > > Why? Why not just zero them, and get both security and compatibility... > Eeek! NO NO NO NO NO NO NO NO! > For ECN that would have worked, but that doesn't mean that something > couldn't have been implimented there that wouldn't have worked that way.. > I think that older Checkpoint firewalls (perhaps current?) zeroed out SACK > on 'hide nat'ed connections. This causes unreasonable stalls for users on > SACK enabled clients. Not cool. Point taken. So much for thinking simple... :-} -- Frank v Waveren Fingerprint: 0EDB 8787 fvw@[var.cx|dse.nl|stack.nl|chello.nl] ICQ#10074100 09B9 6EF5 6425 B855 Public key: http:[EMAIL PROTECTED] 7179 3036 E136 B85D - 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/
Re: hotmail not dealing with ECN
On Sat, Jan 27, 2001 at 07:18:09PM +0100, Frank v Waveren wrote: > On Sat, Jan 27, 2001 at 04:10:48AM +, David Wagner wrote: > > Practice being really, really paranoid. Think: You're designing a > > firewall; you've got some reserved bits, currently unused; any future code > > that uses them could behave in completely arbitrary and insecure ways, > > for all you know. Now recall that anything not known to be safe should > > be denied (in a good firewall) -- see Cheswick and Bellovin for why. > > When you take this point of view, it is completely understandable why > > firewalls designed before ECN was introduced might block it. > > Why? Why not just zero them, and get both security and compatibility... Eeek! NO NO NO NO NO NO NO NO! For ECN that would have worked, but that doesn't mean that something couldn't have been implimented there that wouldn't have worked that way.. I think that older Checkpoint firewalls (perhaps current?) zeroed out SACK on 'hide nat'ed connections. This causes unreasonable stalls for users on SACK enabled clients. Not cool. - 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/
Re: ps hang in 241-pre10
Just for the record, the system where I saw the problem has only ext2 - jjs Shawn Starr wrote: > Yes, I have ReiserFS as well...hrm... > > David Ford wrote: > > > I can quickly and easily duplicate it on my notebook by playing music or > > mpegs in xmms. It may take a few minutes but it's guaranteed. > > > > xmms stalls flat on it's face and anything accessing /proc stalls. If I get > > the time to do it, I'll take a gander at it with kdb. > > > > I have no patches applied to p10, I have reiserfs onboard but I highly doubt > > it's reiserfs. - 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/
