Re: REVISED: Experimentation with Athlon and fast_page_copy

Aaron Tiensivu wrote: > > What still stands out is that exactly _zero_ people have reported the same > > problem with non VIA chipset Athlons. > > This might be grasping at straws [...] This could be (total conjecture) > related somehow to the corruption bugs they are admitting to in > the

Re: REVISED: Experimentation with Athlon and fast_page_copy

On Sat, May 05, 2001 at 03:51:13PM +1200, Chris Wedgwood wrote: > I don't see how they figure, but in case there was any doubt I > have a VIA KT133A/686B board (Abit KT7A) and don't experience > anything resembling disk corruption unless the box crashes for > some other reason. I

Re: Possible PCI subsystem bug in 2.4

Alan Cox <[EMAIL PROTECTED]> writes: > > Seriously. With the general attitude of distrusting BIOS's I have > > been amazed at the number of things linux expects the BIOS to get > > right. In practice windows seem to trust the BIOS much less than > > linux does. > > It becomes more and more

Bus error - Shortly later kernel lockup, many MTRR registers

Hello, I hope I am doing this correctly per the BUG-REPORTING doc. 1. Bus error - Shortly later kernel lockup MTRR registers 2. My kernel has locked up 3 times since moving to the 2.4.x kernel. I am not excaly sure of what triggers it but it does always happen while I am actively

Win98 Setup ignores partition table, corrupts filesystems

Bill sez: "All Your Partition Are Belong To Us." Do you have the pleasure of installing or using multiple operating systems, one of which is a Microsoft product? Then the following information may be of great importance to you. Failure to pay attention to warning symptoms will result in

Athlon and fast_page_copy: What's it worth ? :)

Hi, Before I go any further with this investigation, I'd like to get an idea of how much of a performance improvement the K7 fast_page_copy will give me. Can someone suggest the best benchmark to test the speed of this routine? Thanks, Seth - To unsubscribe from this list: send the line

Re: 2.4.x APM interferes with FA311TX/natsemi.o

On Tue, 1 May 2001, Alan Cox wrote: > > When the call > > apm_bios_call_simple(APM_FUNC_SET_STATE, 0x100, APM_STATE_READY, ) > > is made, the PMEEN (PME enable) bit in the CCSR register on my FA311 > > mysteriously changes from 0 to 1, causing the card to stop processing > > The Linux driver

Re: REVISED: Experimentation with Athlon and fast_page_copy

Chris Wedgwood wrote: > > On Fri, May 04, 2001 at 05:26:57PM -0700, Joseph Carter wrote: > > I don't see how they figure, but in case there was any doubt I > have a VIA KT133A/686B board (Abit KT7A) and don't experience > anything resembling disk corruption unless the box crashes

Re: PROBLEM: 2.4.5pre1 will not boot

Gordon Sadler wrote: > > On Fri, May 04, 2001 at 01:28:23AM -0700, Seth Goldberg wrote:Seth Goldberg ><[EMAIL PROTECTED]> > > Gordon Sadler wrote: > > > > > > On Fri, May 04, 2001 at 12:43:22AM -0700, Seth Goldberg wrote: > > > > Hi, > > Hi, > > > > Have you tried compiling ther kernel with

Re: PROBLEM: 2.4.5pre1 will not boot

On Fri, May 04, 2001 at 01:28:23AM -0700, Seth Goldberg wrote:Seth Goldberg <[EMAIL PROTECTED]> > Gordon Sadler wrote: > > > > On Fri, May 04, 2001 at 12:43:22AM -0700, Seth Goldberg wrote: > > > Hi, > Hi, > > Have you tried compiling ther kernel with Athlon optimiztions turned > off (try >

Re: anybody home at device@lanana.org?

Hello Peter , Would also please drop a line as to what is going on to the rest of the community as well . Tia , JimL On 23 Apr 2001, H. Peter Anvin wrote: > Followup to: <[EMAIL PROTECTED]> > By author:Kipp Cannon <[EMAIL PROTECTED]> > In newsgroup: linux.dev.kernel > >

Re: REVISED: Experimentation with Athlon and fast_page_copy

> What still stands out is that exactly _zero_ people have reported the same > problem with non VIA chipset Athlons. Sorry Alan, but... My (very) old Athlon 550 (model 1, stepping 2) show it on my MSI MS-6167 (AMD Irongate C4) with your 2.4.4-ac5, now :-( Even with or without apm/acpi enabled.

[PATCH] (was Re: 2.4.4 & IPv6 oopses)

Pekka Savola writes: > struct in6_addr *saddr = NULL; > [...] > if (skb && ipv6_chk_addr(>nh.ipv6h->saddr, dev)) > saddr = >nh.ipv6h->saddr; > [...] > ndisc_send_ns(dev, neigh, target, target, saddr); > [...] > This check apparently fails? and saddr is left

Re: How to debug a 2.4.4 tulip problem?

On Sat, 5 May 2001, Manfred Spraul wrote: > Do you know if transmit or receive is slow? tcpdump on both ends of > the ping might help. Sorry, I don't currently know. OK, the next time I see this, I'll give tulip-diag a whirl and report back. Until then, I can't really provide any more

Compressed iso9660 filesystem

Okay, I think I now feel comfortable enough that I think I can unleash this on the world... I have made an extension to iso9660/RockRidge to allow for transparent uncompression of block-compressed files. Because the files are block-compressed, random access is fast; it uses a 32K blocksize

Re: How to debug a 2.4.4 tulip problem?

> > What information should I gather when the card is wedged to aid in > debugging? Is 'lspci -xxx' enough? Any suggestions would be welcome. > tulip-diag from www.scyld.com. Do you know if transmit or receive is slow? tcpdump on both ends of the ping might help. - To unsubscribe from this

CML2 1.4.0, aka "brutality and heuristics"

The latest version is always available at http://www.tuxedo.org/~esr/cml2/ Release 1.4.0: Fri May 4 18:18:15 EDT 2001 * Ugly hack for recovery from inconsistent configurations. We've spent a lot of time and effort recently arguing about elaborate recovery algorithms for the extremely

How to debug a 2.4.4 tulip problem?

Hello, I'm having a small intermittent problem with the tulip driver in linux 2.4.4, and I'm looking for some guidance on how to debug it. What happens is that on one of my boxes the card ocasionally gets wedged. That is, network traffic gets painfully slow, e.g. pinging another host on the

Re: REVISED: Experimentation with Athlon and fast_page_copy

On Fri, May 04, 2001 at 06:26:14PM -0400, Aaron Tiensivu wrote: > This might be grasping at straws I remember VIA problem in the "good old > days" of Socket 7 with CPU/PCI Prefetches and especially Read-around-Write > settings that would cause issues like we're seeing with the Athlon >

Re: [PATCH] 3 one-liner bugfixes

Manfred Spraul wrote: > > + else > + fl->fl_type & ~F_INPROGRESS; ^^ > + unlock_kernel(); > + return ret; > } The last patch was incorrect. Corrected version attached. -- Manfred // $Header$ // Kernel Version: // VERSION = 2 //

Re: Setting kernel options at compile time.

Followup to: By author:(Chip Schweiss) [EMAIL PROTECTED] In newsgroup: linux.dev.kernel > > The catch I'm running into is RPLD cannot pass parameters to the kernel > and without this setting the system has video problem, most likely

Re: [PATCH] 3 one-liner bugfixes

Linus Torvalds wrote: > > On Sat, 5 May 2001, Manfred Spraul wrote: > > > > * missing/wrong lock_kernel calls in fs/fcntl.c: getlk/setlk run without > > the big kernel lock. The ..64 function acquire the lock. > > This is wrong. The big lock (if it is needed, but I thought the current > locking

Re: SMP races in proc with thread_struct

On 04 May 2001 15:11:37 +0200, Andreas Schwab <[EMAIL PROTECTED]> wrote: >Keith Owens <[EMAIL PROTECTED]> writes: >|> Wrap the reference to the parent task structure with exception table >|> recovery code, like copy_from_user(). > >Exception tables only protect accesses to user virtual memory.

Re: [linux-usb-devel] pegasus + MediaGX: Oops in khubd,the continuing story?

> I suspect the ohci driver currently. I've been reviewing it a little and it > is full of code written by someone who does not know about pci write posting. I think there's a lot of that going around ... I don't think any of what you mentioned was in the Documentation/pci.txt writeup, or any

Re: Setting kernel options at compile time.

Chip Schweiss wrote: > > I'm trying to get a 2.2.19 kernel loaded on an i810 system using RPLD on > a diskless system. I can get the kernel loaded and running. The > problem is the i810 needs the kernel parameter "mem=xxxM" set to tell > the kernel how much memory the system has since the on

Re: Memory management issues with 2.4.4

Marcelo Tosatti wrote: > > On Wed, 2 May 2001, Jorge Nerin wrote: > >> Short version: >> Under very heavy thrashing (about four hours) the system either lockups >> or OOM handler kills a task even when there is swap space left. > > > First of all, please try to reproduce the problem

Linux 2.4.4-ac5

ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/ Intermediate diffs are available from http://www.bzimage.org Please test this code **carefully** if using an HPT366/370 IDE controller as there are driver changes there. Otherwise its mostly

Re: REVISED: Experimentation with Athlon and fast_page_copy

> What still stands out is that exactly _zero_ people have reported the same > problem with non VIA chipset Athlons. This might be grasping at straws I remember VIA problem in the "good old days" of Socket 7 with CPU/PCI Prefetches and especially Read-around-Write settings that would cause

Re: 2.4.4-ac4 - oops on unload "cdrom" module

On Fri, May 04 2001, Pavel Roskin wrote: > > The following patch fixes unloading of cdrom module when no cdrom driver > > loaded (2.4.5-pre, 2.4.4-ac): > > It works for me. Thank you! You have even managed to find out that I had > my CD-ROM disconnected :-) > > By the way, shouldn't we register

Re: [Patch] sis_main.c

Sorry --- /usr/src/linux/drivers/video/sis/sis_main.c Fri Feb 9 11:30:23 2001 +++ ./sis_main.cFri May 4 07:34:47 2001 @@ -1030,6 +1030,10 @@ if (heap.pohFreeList == NULL) { poha = kmalloc(OH_ALLOC_SIZE, GFP_KERNEL); + if(!poha) { +

Re: 2.4.4-ac4 - oops on unload "cdrom" module

On Fri, May 04 2001, Andrzej Krzysztofowicz wrote: > > This oops happens when I run "rmmod cdrom" on a 2.4.4-ac4 kernel with > > CONFIG_SYSCTL enabled. It doesn't happen if CONFIG_SYSCTL is disabled. > > > > sr_mod isn't loaded at this point. Reference to sd_mod looks weird. After > > this oops

Re: [PATCH] 3 one-liner bugfixes

On Sat, 5 May 2001, Manfred Spraul wrote: > > * missing/wrong lock_kernel calls in fs/fcntl.c: getlk/setlk run without > the big kernel lock. The ..64 function acquire the lock. This is wrong. The big lock (if it is needed, but I thought the current locking should be safe) should be pushed

Re: Setting kernel options at compile time.

> a diskless system. I can get the kernel loaded and running. The > problem is the i810 needs the kernel parameter "mem=xxxM" set to tell > the kernel how much memory the system has since the on the i810 the > kernel doesn't know how much was taken for video. The BIOS itself marks off the

Setting kernel options at compile time.

I'm trying to get a 2.2.19 kernel loaded on an i810 system using RPLD on a diskless system. I can get the kernel loaded and running. The problem is the i810 needs the kernel parameter "mem=xxxM" set to tell the kernel how much memory the system has since the on the i810 the kernel doesn't

[PATCH] 3 one-liner bugfixes

Hi Linus, I found a 3 small bugs: * mm/slab.c: the offslab_limit calculation used 2 instead of sizeof(kmem_bufctl_t) [==4]. Cosmetic bug, since offslab_limit is never reached. * expand_stack is not down_read() safe, but used in the page-in path. Fix is trivial. * missing/wrong lock_kernel

TCP Timer granularity

Hi, Can anyone tell me what is the granularity of the TCP timer in kernel 2.4? Can I have microsecond timers? What's the value I need to use for the field "tcp_opt.timer.expires" if I need to have something like 20 ms timer? shreeni.

Re: [Patch] sis_main.c

On Fri, May 04, 2001 at 07:58:59AM -0700, Christopher Kanaan wrote: > Hello, > I am a working with Dawson Englers meta compilation group at Stanford. > Here is a patch for sis_main.c Basically the patch checks to see > if kmalloc returns null. This patch applies to kernel version 2.4.4

Re: 2.4.4-ac4 - oops on unload "cdrom" module

Hi, Andrzej! > The following patch fixes unloading of cdrom module when no cdrom driver > loaded (2.4.5-pre, 2.4.4-ac): It works for me. Thank you! You have even managed to find out that I had my CD-ROM disconnected :-) By the way, shouldn't we register sysctl, /proc/sys/dev/cdrom/ and

[Patch] sis_main.c

Hello, I am a working with Dawson Englers meta compilation group at Stanford. Here is a patch for sis_main.c Basically the patch checks to see if kmalloc returns null. This patch applies to kernel version 2.4.4 Thanks, Christopher Kanaan --- /usr/src/linux/drivers/video/sis/sis_main.c Fri

Re: [PATCH] SMP race in ext2 - metadata corruption.

On Fri, 4 May 2001, Alan Cox wrote: > > iso9660 alas doesn't allow you to do that. You can speed it up by reading > the entire file into memory rather than paging it in (or reading it in and > then executing it). iso9660 layout is pretty constrained and designed for > linear file reads Note

Re: [linux-usb-devel] pegasus + MediaGX: Oops in khubd, the continuing story?

> The Oops'es are mostly in the khubd process, but they sometimes appear in other > programs (insmod, ifconfig). They always lead to an immedate panic, and nothing I suspect the ohci driver currently. I've been reviewing it a little and it is full of code written by someone who does not know

Re: DPT I2O RAID and Linux I2O

> When I look at the source from the i2o driver, i find that my module will > have to primary create an handler to respond to the messages, but does the > configuration of the i2o should be done by my module or it is gonna be done > by the functions I cant use right now ? (i2o_pci_enable...) You

Re: Sending packets from within the kernel

On Fri, May 04, 2001 at 02:09:16PM -0700, [EMAIL PROTECTED] wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hello, > > I am working on an kernel module which forwards TCP segments from one > interface to another (basic routing, no proxy or listener socket), but > which needs to be

Re: REVISED: Experimentation with Athlon and fast_page_copy

> prefetch 320(%0) can fetch memory behind the end of the source page. > Perhaps it accesses memory in the ISA hole, or beyond the end of memory? > Could you post the e820 map from dmesg? > > It's possible to build manually a memory map. > Could you build one with wide margins from "dangerous"

Re: 3ware 6410 RAID 10 performance?

On Fri, May 04, 2001 at 02:03:35PM -0700, Adam Radford wrote: > Larry, > > If there's anything to fix in the driver for this problem I'd be interested, > however I have not seen this problem before. > > What benchmark (and options) are you running? bonnie++ ? > > BTW... I am the author of the

[OOPS] pegasus + MediaGX: Oops in khubd, the continuing story?

Well, I got fed up with all those Oops'es, so I started scribbling one on a piece of paper. This is what ksymoops makes of it: ksymoops 2.4.1 on i586 2.4.4. Options used -V (default) -k /var/log/ksymoops/20010504223943.ksyms (specified) -l

Re: [patch] 2.4.4 alpha semaphores optimization

On Thu, May 03, 2001 at 07:47:47PM +0400, Ivan Kokshaysky wrote: > Initially I tried to use __builtin_expect in the rwsem.h, but found > that it doesn't help at all in the small inline functions - it works > as expected only in a reasonably large block of code. Eh? Would you give me an example

Re: [PATCH] strtok -> strsep (The Easy Cases)

Rusty Russell <[EMAIL PROTECTED]> schrieb am 04.05.01: > In message <01050413055100.00907@golmepha> you write: > > Am Freitag, 4. Mai 2001 02:57 schrieb Rusty Russell: > > > There are two cases where the substitution is problematic: > > > > Yes, but... > > > > The cases which my patch modifies

Re: [patch] 2.4.4 alpha semaphores optimization

On Thu, May 03, 2001 at 07:47:47PM +0400, Ivan Kokshaysky wrote: > - removed some mb's for non-SMP This isn't correct. Either you need atomic updates or you don't. If you don't, then you shouldn't be using ll/sc at all. If you do (perhaps to coordinate with devices) then the barriers are

Sending packets from within the kernel

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I am working on an kernel module which forwards TCP segments from one interface to another (basic routing, no proxy or listener socket), but which needs to be able to generate some segments completely independently of the client<-->server

Re: 2.4.4-ac4 - oops on unload "cdrom" module

> This oops happens when I run "rmmod cdrom" on a 2.4.4-ac4 kernel with > CONFIG_SYSCTL enabled. It doesn't happen if CONFIG_SYSCTL is disabled. > > sr_mod isn't loaded at this point. Reference to sd_mod looks weird. After > this oops the "cdrom" module remains in memory in the "deleted" state.

Re: [PATCH] SMP race in ext2 - metadata corruption.

> Now, if you want to speed up accesses, there are things you can do. You > can lay out the filesystem in the access order - trace the IO accesses at > bootup ("which file, which offset, which metadata block?") and lay out the > blocks of the files in exactly the right order. Then you will get

Re: REVISED: Experimentation with Athlon and fast_page_copy

> the memory copy in the fast_page_copy routine. The machine then > proceeded > not to stop at my panic, but I got my "normal" oopses. I then had an Ok > idea and removed all the prefetch instructions from the beginning of the > routine and tried the resultin kernel. I now have no crashes. >

Re: [OT] Interrupting select.

Hi, "Peter T. Breuer" <[EMAIL PROTECTED]> writes: > "A month of sundays ago Alan Cox wrote:" > > > What IS the magic combination that makes select interruptible > > > by honest-to-goodness non-blocked signals! > > man > > > > [seriously man sigaction] > > Equally seriously .. all signals are

RFC: new zero copy pipe

I've rewritten the single copy pipe code again. Main changes: * doesn't use map_user_kiobuf anymore. That function locked the pages into memory. DoS attacks were possible. Now pages stay pageable. * simpler code, fewer loops. * support added for set_fs(KERNEL_DS)+pipe_write * all transfers that

3c900 card and kernel 2.4.3

Hi there, when i install kernel 2.4.3 or higher on my slackware system the card (3c900) gets detected but doesn't do anything, i also get the line "using NWAY 8" or something like that (had to switch back to 2.4.2 to type e-mail) wondered if anyone else had this problem and if there's some way

Re: 3ware 6410 RAID 10 performance?

And yet more data - Under 2.2.15 using 3ware's driver rather than the one shipped with the kernel, one complete read goes at 35MB/sec (nice). The second one starts out there and then drops down to 4MB/sec at the 1.2GB offset. Here's the cool part - if I unmount, rmmod the driver, insmod,

Re: added a new feature: disable pc speaker

Quoth Nico Schottelius: > Can somebody give me a hint where to find documentation about > sysctl and howto use/program that ? > This is what Simon and David suggested. > > But as long as I am not able to make sysctl's, I would like > to add this feature under the General setup. > > What do

pegasus + MediaGX: Oops in khubd, the continuing story?

Hi'all, I'm experiencing loads of intermittent Oops'es when loading the pegasus driver (for an SMC 2202) on my MediaGX-equipped (Webplayer) systems. A scan of the lists turned up more problems with the MediaGX (which contains an OHCI implementation in the 5530 companion chip) in combination with

Re: added a new feature: disable pc speaker

> > setterm -blength 0 (text) > > xset b 0 (X11) > > Well, some buggy programs don't care about you turning off beeping in > X. I think gnome-terminal or such has its own checkbox for turning > beeps on or off. Exactly. > I still agree that this is fixing userspace bugs in the kernel, and

Re: 3ware 6410 RAID 10 performance?

More data: the test file is 2GB in size. When I do a reboot and time the reading of the entire file, the first time the performance is great, 27MB. The second time it sucks, 2.7MB. I tried clearing memory by allocating and pounding on an array of 512MB (size of main mem), that clears out memory

Re: Maximum files per Directory

On Friday, May 04, 2001 01:15:22 PM -0600 Andreas Dilger <[EMAIL PROTECTED]> wrote: > Chris writes: >> On Tuesday, May 01, 2001 04:57:02 PM -0600 Andreas Dilger >> <[EMAIL PROTECTED]> wrote: >> > I see that reiserfs plays some tricks with the directory i_nlink count. >> > If you exceed 64536

Re: [PATCH] SMP race in ext2 - metadata corruption.

Alexander Viro writes: > > > On Fri, 4 May 2001, Richard Gooch wrote: > > > I don't bother splitting /usr off /. I gave up doing that when disc > > became cheap. There's no point anymore. And since I have a lightweight > > Yes, there is. Locality. Resistance to fs fuckups. Resistance to >

RE added a new feature: disable pc speaker

Keith Owens wrote: > On Fri, 04 May 2001 13:37:08 +0200, > Nico Schottelius <[EMAIL PROTECTED]> wrote: > >I have searched a long time for a method to disable the internal > >speaker for every application, every daemon and so on. > > Userspace problem, userspace fix. This sounds good :)

3ware 6410 RAID 10 performance?

I'm looking for people who know about the 3ware 6410 driver. I've got one of these and sometimes it goes fast and sometimes it doesn't. The bad case seems to happen after memory has a lot of cached blocks in it. I've tried 2.2.15, 2.4.4, and 2.4.3-ac9 and they all behave pretty similarly.

Re: [PATCH] SMP race in ext2 - metadata corruption.

On Fri, 4 May 2001, Richard Gooch wrote: > I don't bother splitting /usr off /. I gave up doing that when disc > became cheap. There's no point anymore. And since I have a lightweight Yes, there is. Locality. Resistance to fs fuckups. Resistance to disk fuckups. Easier to restore from tape.

Re: REVISED: Experimentation with Athlon and fast_page_copy

Seth Goldberg wrote: > > Hi, > > After removing my head from my a**, I revised the code that checks > the memory copy in the fast_page_copy routine. The machine then > proceeded > not to stop at my panic, but I got my "normal" oopses. I then had an > idea and removed all the prefetch

[Patch] encapsulate shmem access to shmem_inode_info

Hi, On 24 Apr 2001, Christoph Rohland wrote: > Hi Al, > > On Tue, 24 Apr 2001, Alexander Viro wrote: >> So yes, IMO having such patches available _is_ a good thing. And in >> 2.5 we definitely want them in the tree. If encapsulation part gets >> there during 2.4 and separate allocation is

Re: [PATCH] SMP race in ext2 - metadata corruption.

Alexander Viro writes: > > > On Fri, 4 May 2001, Richard Gooch wrote: > > > > Two of them: use less bloated shell (and link it statically) and > > > clean your rc scripts. > > > > No, because I'm not using the latest bloated version of bash, and I'm > > Umm... Last version of bash I could

Re: REVISED: Experimentation with Athlon and fast_page_copy

On Fri, 4 May 2001, Manfred Spraul wrote: | > --- | > > __asm__ __volatile__ ( | > 158c157 | > < "3: movw $0x1AEB, 1b\n" | > --- | > > "3: movw $0x1AEB, 1b\n" /* jmp on 26 bytes */ | > 166c165 | > < */ | > --- | > > | > 170c169 | > < "1: nop\n"

RE: DPT I2O RAID and Linux I2O

> Ok thats nothing to do with I2O itself. Some hardware has the messaging > layer built into it as the messenger is very simple and stuff > like the 21554 > are using in I2O controllers. > > You might find i2o_pci.c and the i2o_core message passing code interesting > but probably not that much.

Re: [PATCH] SMP race in ext2 - metadata corruption.

On Fri, 4 May 2001, Richard Gooch wrote: > > Two of them: use less bloated shell (and link it statically) and > > clean your rc scripts. > > No, because I'm not using the latest bloated version of bash, and I'm Umm... Last version of bash I could call not bloated was _long_ time ago.

Re: REVISED: Experimentation with Athlon and fast_page_copy

> --- > > __asm__ __volatile__ ( > 158c157 > < "3: movw $0x1AEB, 1b\n" > --- > > "3: movw $0x1AEB, 1b\n" /* jmp on 26 bytes */ > 166c165 > < */ > --- > > > 170c169 > < "1: nop\n" /* prefetch 320(%0)\n" */ > --- > > "1: prefetch

Re: Maximum files per Directory

Chris writes: > On Tuesday, May 01, 2001 04:57:02 PM -0600 Andreas Dilger > <[EMAIL PROTECTED]> wrote: > > I see that reiserfs plays some tricks with the directory i_nlink count. > > If you exceed 64536 links in a directory, it reverts to "1" and no longer > > tracks the link count. > > Correct.

Re: [PATCH] SMP race in ext2 - metadata corruption.

On Fri, 4 May 2001, Alexander Viro wrote: > > ObProcfs: I don't think that walking the page tables is a good way to > compute RSS, especially since VM maintains the thing. Well, the VM didn't always use to maintain the stuff it does now, so I bet that most of the code is just old code that

Re: [PATCH] SMP race in ext2 - metadata corruption.

On Fri, May 04 2001, Richard Gooch wrote: > The idea I had (motivated by the desire to eliminate random disc > seeks, which is the limiting factor in how fast my boxes boot) was: > > - init(8) issues an ioctl(2) on the root FS block device which turns > on recording of block reads (it records

Re: [PATCH] SMP race in ext2 - metadata corruption.

Alexander Viro writes: > > > On Fri, 4 May 2001, Richard Gooch wrote: > > > However, doing an ioctl(2) on the block device won't help. So the > > question is, where to add the hook? One possibility is the FS, and > > record inum,bnum pairs. But of course we don't have a way of accessing > >

Patch for ymfpci in 2.4.4

Hello: Here are updates from ALSA. The interrupt acknowledge has a potential bug report for it in RH bugzilla. Power-up fix I include "just because", Alan bounced it to me from sound-hackers; Also Jeff Garzik asked for it. I wanted to include it with full PM support, but perhaps not. -- Pete

Re: [PATCH] SMP race in ext2 - metadata corruption.

On Fri, 4 May 2001, Richard Gooch wrote: > However, doing an ioctl(2) on the block device won't help. So the > question is, where to add the hook? One possibility is the FS, and > record inum,bnum pairs. But of course we don't have a way of accessing > via inum in user-space. So that's no

Re: X15 alpha release: as fast as TUX but in user space

On 04-May-2001 Fabio Riccardi wrote: > ok, I'm totally ignorant here, what is a pipelined request? http://www.w3.org/Protocols/HTTP/Performance/Pipeline.html A pipelined application implementation buffers its output before writing it to the underlying TCP stack, roughly equivalent to what

Re: added a new feature: disable pc speaker

Quoth Keith Owens: > Userspace problem, userspace fix. > > setterm -blength 0 (text) > xset b 0 (X11) Well, some buggy programs don't care about you turning off beeping in X. I think gnome-terminal or such has its own checkbox for turning beeps on or off. I still agree that this is

Re: [PATCH] SMP race in ext2 - metadata corruption.

On Fri, 4 May 2001, Linus Torvalds wrote: > > On Fri, 4 May 2001, Alexander Viro wrote: > > > > Ehh... There _is_ a way to deal with that, but it's deeply Albertesque: ^^^ > > * add pagecache access for block device >

Re: [PATCH] SMP race in ext2 - metadata corruption.

Linus Torvalds writes: > Now, if you want to speed up accesses, there are things you can > do. You can lay out the filesystem in the access order - trace the > IO accesses at bootup ("which file, which offset, which metadata > block?") and lay out the blocks of the files in exactly the right >

Re: modularized SYSENTER support

> Q. How come the handler doesn't manage so called "bottom halves" or >"soft IRQs"? > A. There is no need for this. Soft IRQs can only appear at exit from >hardware interrupt handlers. Indeed, we can't count on user app. >being around and performing a system call when it comes to

Re: X15 alpha release: as fast as TUX but in user space

ok, I'm totally ignorant here, what is a pipelined request? btw: please be kind with my mistakes, X15 _is_ alpha code anyway... :) - Fabio Ingo Molnar wrote: > yet another anomaly i noticed. X15 does not appear to handle pipelined > HTTP/1.1 requests properly, it ignores the second request

Re: X15 alpha release

Ingo, I'm really impressed by your feedback! How do you manage to discover so many things? I fixed the bug, and checked that it hadn't affected my specweb results. Indeed specweb never issues closing 1.1 connections, it would use a 1.0 request with close in that case. Moreover even if a

Re: [PATCH] SMP race in ext2 - metadata corruption.

On Fri, 4 May 2001, Alexander Viro wrote: > > Ehh... There _is_ a way to deal with that, but it's deeply Albertesque: > * add pagecache access for block device > * put your "real" root on /dev/loop0 (setup from initrd) > * dd You're one sick puppy. Now, the above is

[PATCH][RFC] Re: SMP races in proc with thread_struct

Linus, could you consider the patch below? As it is, access to /proc//status of dead process with dead parent is possible and leads to access to freed memory. Besides, cd /proc/ means that even after is gone, readdir() _and_ lookup on /proc/ work. Patch makes sure that ->p_pptr is NULL

Re: Possible PCI subsystem bug in 2.4

On 4 May 2001, Eric W. Biederman wrote: > > There are a couple of options here. > 1) read the MTRRs unless the BIOS is braindead it will set up that area as >write-back. At any rate we shouldn't ever try to allocate a pci region >that is write-back cached. This one I'd really hesitate

Re: [PATCH] SMP race in ext2 - metadata corruption.

On Fri, 4 May 2001, Linus Torvalds wrote: > Now, if you want to speed up accesses, there are things you can do. You > can lay out the filesystem in the access order - trace the IO accesses at > bootup ("which file, which offset, which metadata block?") and lay out the > blocks of the files in

Re: [PATCH] SMP race in ext2 - metadata corruption.

On Fri, 4 May 2001, Andrea Arcangeli wrote: > On Fri, May 04, 2001 at 01:56:14PM +0200, Jens Axboe wrote: > > Or you can rewrite block_read/write to use the page cache, in which case > > you'd have more luck doing the above. > > once block_dev is in pagecache there will obviously be no-way to

Re: smp_send_stop() and disable_local_APIC()

"Eric W. Biederman" wrote: > > "Matt D. Robinson" <[EMAIL PROTECTED]> writes: > > > It looks like around 2.3.30 or so, someone added the call > > disable_local_APIC() to smp_send_stop(). I'm not sure what the > > intention was, but I'm getting some strange behavior as a result > > based on

Re: X15 alpha release: as fast as TUX but in user space (fwd)

um, presumably this new magic page won't eliminate the old syscall entry points. so just use those for UML. -dean On Fri, 4 May 2001, Pavel Machek wrote: > Hi! > > > > > That means that for fooling closed-source statically-linked binary, > > > > > > If they are using glibc then you have the

Re: [PATCH] SMP race in ext2 - metadata corruption.

On Fri, 4 May 2001, Rogier Wolff wrote: > > Linus Torvalds wrote: > > > > Ehh. Doing that would be extremely stupid, and would slow down your boot > > and nothing more. > > Ehhh, Linus, Linearly reading my harddisk goes at 26Mb per second. You obviously didn't read my explanation of _why_ it

REVISED: Experimentation with Athlon and fast_page_copy

Hi, After removing my head from my a**, I revised the code that checks the memory copy in the fast_page_copy routine. The machine then proceeded not to stop at my panic, but I got my "normal" oopses. I then had an idea and removed all the prefetch instructions from the beginning of the

Re: dhcp problem with realtek 8139 clone with rh 7.1

Alan Cox wrote: > > > I've had the same problem with the 8139too drivers and DHCP. The reason > > I figure it must be the drivers is because in the 2.4.3 kernel, I'm able > > to use the 8139too drivers with DHCP without any problems. In 2.4.4 it > > locks my system. > > Multiple such reports

Re: [patch] 2.4.4 alpha semaphores optimization

On Fri, May 04, 2001 at 09:02:33PM +0400, Ivan Kokshaysky wrote: > But I can't imagine how this "feature" could be useful in a real life :-) It will be required by the time we can fork more than 2^16 tasks (which I'm wondering if it could be just the case if you use CLONE_PID as root, I didn't

Re: [patch] 2.4.4 alpha semaphores optimization

On Fri, May 04, 2001 at 04:33:59PM +0200, Andrea Arcangeli wrote: > the 2^16 limit is not a per-user limit it is a global one so the max > user process ulimit is irrelevant. > > Only the number of pid and the max number of tasks supported by the > architecture is a relevant limit for this.

Re: dhcp problem with realtek 8139 clone with rh 7.1

> I've had the same problem with the 8139too drivers and DHCP. The reason > I figure it must be the drivers is because in the 2.4.3 kernel, I'm able > to use the 8139too drivers with DHCP without any problems. In 2.4.4 it > locks my system. Multiple such reports - seems the 8139too update

Re: Possible PCI subsystem bug in 2.4

> Seriously. With the general attitude of distrusting BIOS's I have > been amazed at the number of things linux expects the BIOS to get > right. In practice windows seem to trust the BIOS much less than > linux does. It becomes more and more obvious over time exactly why. One problem however

  1   2   3   4   >