Re: VIA's Southbridge bug: Latest (pseudo-)patch

On Sat, 19 May 2001, Axel Thimm wrote: > This are the latest suggestions for handling the VIA Southbridge bug as > derived from the hardware site www.au-ja.de (Many thanks to doelf). Sorry - little off-topic. I can't find the clean answer anywhere. I use KT7A-RAID, with one disc connected to

Re: [RFD w/info-PATCH] device arguments from lookup, partion code

On Sat, 19 May 2001, Alan Cox wrote: > > Now that I'm awake and refreshed, yeah, that's awful. But > > echo "hot-add,slot=5,device=/dev/sda" >/dev/md0/control *is* sane. Heck, > > the system can even send back result codes that way. > > Only to an English speaker. I suspect Quebec City

Re: Negative inode-nr ?

On Sat, 19 May 2001, [iso-8859-1] Jakob Østergaard wrote: > What do you think of this ? > [root]# cat /proc/sys/fs/inode-nr > 157097-180 I think you should upgrade to a newer kernel; Al Viro fixed this bug and the fix went into 2.4.5-pre1. regards, Rik -- Virtual memory is like a

Re: PATCH: Make Acer Extensa 50X Sound work without hanging the whol

> since ages owners of a Extensa 50X notebook apply the following diff to the > kernel to make the sound work without hanging the whole system. With what sound card ? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More

Re: [RFD w/info-PATCH] device arguments from lookup, partion code

> Now that I'm awake and refreshed, yeah, that's awful. But > echo "hot-add,slot=5,device=/dev/sda" >/dev/md0/control *is* sane. Heck, > the system can even send back result codes that way. Only to an English speaker. I suspect Quebec City canadians would prefer a different command set. - To

Re: CML2 design philosophy heads-up

> Second, how many kernels does Redhat ship in order to have one for > 386/486/586/k6/Athlon . . . . > Quite a pain in the ass. And look at how much shit has to be built in > in order to get a kernel that works for everybody! People bitch at > Microsoft for doing it, then turn around and do

Re: VIA's Southbridge bug: Latest (pseudo-)patch

> This are the latest suggestions for handling the VIA Southbridge bug as > derived from the hardware site www.au-ja.de (Many thanks to doelf). I'd rather people left this except for the obvious fixed that were done for non VIA northbridge combinations until 2.5. 2.4 is not an appropriate place

PATCH: Make Acer Extensa 50X Sound work without hanging the whol

Hello, since ages owners of a Extensa 50X notebook apply the following diff to the kernel to make the sound work without hanging the whole system. I've no idea if anybody ever suggested to put this in the mainstream kernel, so do I. Note: I modified the original patch to work with 2.4 but I

Re: Hang on boot using latest -ac kernels with irda

> Code; c0204004<= >0: 66 81 78 5c 0f 03 cmpw $0x30f,0x5c(%eax) <= Someone passed NULL to a netdevice notifier. That isnt allowed. Your call trace indicates that it was passed by dev_open which would itself have oopsed in that situation. Beats me, and I also

Q: ioctl BLKGETSIZE return value units?

Hi, What are the units of the return value of the BLKGETSIZE ioctl on Linux? Is it allways in units of 512 bytes or is it in units of sector size bytes as returned by BLKSSZGET ioctl? Thanks in advance. Best regards, Anton -- Anton Altaparmakov (replace at with @) Linux NTFS

Q: fdatasync on block device?

Hi, Could someone enlighten me whether fdatasync() system call on Linux, when called on the fd of an open()-ed block device, will result in the committing of all dirty device buffers to disk? If not, how do I achieve this? Should I use the BLKFLSBUF ioctl? Thanks in advance. Best regards,

Re: Why side-effects on open(2) are evil. (was Re: [RFD w/info-PATCH]device arguments from lookup)

On Sat, 19 May 2001, Abramo Bagnara wrote: > Can't this easily avoided if the needed action is not > > < /dev/zero/start_nuclear_war > or > > /dev/zero/start_nuclear_war > > but > > echo "I'm evil" > /dev/zero/start_nuclear_war Sure. And that's the right thing to do (not the implied

Negative inode-nr ?

Hello all, I was investigating a problem we believed we had with our monitoring software (from sysorb.com), where it failed to report the number of free and allocated inodes. However, looking into the problem I found that it's the kernel that's returning bogus values. What do you think of

Re: RTL8139 difficulties in 2.2, not in 2.4

On Sat, 19 May 2001, Matthias Andree wrote: > I'm having difficulties with a RTL8139 with Linux 2.2.19 (both drivers), > but not with Linux 2.4.4's 8139too driver. The card is an Allied Telesyn > AT-2500TX, the chip is reported as 8139C/rev. 0x10. The card shares its > IRQ 9 with an nVidia Riva

Re: Why side-effects on open(2) are evil. (was Re: [RFD w/info-PATCH]device arguments from lookup)

Alexander Viro wrote: > > Folks, before you get all excited about cramming side effects into > open(2), consider the following case: > > 1) opening "/dev/zero/start_nuclear_war" has a certain side effect. > > 2) Local user does the following: > ln -sf

Re: dget()

[EMAIL PROTECTED] said: > # cd /usr/src/linux > # find -name '*.[ch]' | ctags -L- & > > On 15 May 2001, Xavier Bestel wrote: > > # cd /usr/src/linux > > # make tags > > No, I never use that one because it skips very useful entries like the > ones from EXPORT_SYMBOL etc. Also, it only shows the

Re: Why side-effects on open(2) are evil. (was Re: [RFD w/info-PATCH]device arguments from lookup)

On Sat, 19 May 2001 [EMAIL PROTECTED] wrote: > > A lot of stuff relies on the fact that close(open(foo, O_RDONLY)) > > is a no-op. Breaking that assumption is a Bad Thing(tm). > > Also here I would like to agree. Unfortunately this is false. > Opening device files often has interesting side

Re: Why side-effects on open(2) are evil. (was Re: [RFD w/info-PATCH] device arguments from lookup)

Alexander Viro writes: > Folks, before you get all excited about cramming side effects > into open(2), consider ... I agree completely. > A lot of stuff relies on the fact that close(open(foo, O_RDONLY)) > is a no-op. Breaking that assumption is a Bad Thing(tm). Also here I would like to

Re: [RFD w/info-PATCH] device arguments from lookup, partion code

> ioctls are evil, period. At least with these names you can use normal > scripting and don't need any special tools. Every ioctl means a binary > that has no business to exist. That is not IMHO a rational argument. It isn't my fault that your shell does not support ioctls usefully. If you used

Why side-effects on open(2) are evil. (was Re: [RFD w/info-PATCH]device arguments from lookup)

Folks, before you get all excited about cramming side effects into open(2), consider the following case: 1) opening "/dev/zero/start_nuclear_war" has a certain side effect. 2) Local user does the following: ln -sf /dev/zero/start_nuclear_war bar while true; do

Re: alpha iommu fixes

On Fri, May 18, 2001 at 09:46:17PM +0400, Ivan Kokshaysky wrote: > The most interesting thing here is the pyxis "tbia" fix. > Whee! I can now copy files from SCSI to bus-master IDE, or > between two IDE drives on separate channels, or do other nice > things without hanging lx/sx164. :-) > The

Re: /dev/sch0 interface

On May 15, 6:35pm, "Jeff V. Merkey" wrote: } Subject: Re: /dev/sch0 interface > On Tue, May 15, 2001 at 11:44:23PM +, Thorsten Kranzkowski wrote: > > On Tue, May 15, 2001 at 03:08:01PM -0600, Jeff V. Merkey wrote: > > > Is anyone actuaslly using the /dev/sch0 interface for SCSI tape

[PATCH] winbond-840 update

Minor update to the winbond-840 driver: * improved SMP locking, one or 2 races fixed. * memory leak in _close fixed. * partial implementation of _suspend and _resume. The chip is disabled and restarted, but not yet put into sleep mode. [lack of hardware to test it] -- Manfred ---

Re: VIA/PDC/Athlon - IDE error theory

Wilfried Weissmann wrote: > > > hda: dma_intr: error=0x84 { DriveStatusError BadCRC } > > > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } > > CRC errors are cable errors so that bit is reasonable in itself > Could this be caused by the RAID configuration? The first sector of the

Re: Linux-2.4.4 failure to compile

On Fri, May 18, 2001 at 04:41:16PM +0600, Anuradha Ratnaweera wrote: > > On Fri, 18 May 2001, Lorenzo Marcantonio wrote: > > > On Thu, 17 May 2001, H. Peter Anvin wrote: > > > > > I think the header file you're talking about is the db1 header file, > > > which has nothing to do with yacc --

Re: [RFD w/info-PATCH] device arguments from lookup, partion codein userspace

Alexander Viro wrote: > > It's way past ugly. I knew you'd like it. It kind of makes sense, because it puts the two primary stream-of-bytes objects in Unix into the same namespace, with the same accessors. So if some random application is expecting a filename well heck, you just give it a

icache flushing in kernel/ptrace.c

I would like to change kernel/ptrace.c to call something else instead of flush_icache_page in access_one_page in kernel/ptrace.c. Currently it calls flush_icache_page on the page after modifying it. Now of course on many architectures (including PPC) we need to do some sort of i-cache flush -

RTL8139 difficulties in 2.2, not in 2.4

Hi, I'm having difficulties with a RTL8139 with Linux 2.2.19 (both drivers), but not with Linux 2.4.4's 8139too driver. The card is an Allied Telesyn AT-2500TX, the chip is reported as 8139C/rev. 0x10. The card shares its IRQ 9 with an nVidia Riva TNT 128 [NV04], rev. 4. (eth0 is a 3C900 Combo

Re: [RFD w/info-PATCH] device arguments from lookup, partion codein userspace

On Sat, 19 May 2001, Andrew Morton wrote: > So. When am I going to be able to: > > open("/bin/ls,-l,/etc/passwd", O_RDONLY); You are not. Think for a minute and you'll see why. Linus' idea of /dev/tty/ is marginally sane - it makes sense to consider that as configuring-upon-open. You

Re: VIA/PDC/Athlon - IDE error theory

Alan Cox wrote: > > hda: dma_intr: error=0x84 { DriveStatusError BadCRC } > > hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } > > CRC errors are cable errors so that bit is reasonable in itself Could this be caused by the RAID configuration? The first sector of the first disk holds

Re: [RFD w/info-PATCH] device arguments from lookup, partion code in userspace

[EMAIL PROTECTED] wrote: > > Hmm. You know that I wrote this long ago? Well, let's not get too hung up on the disk thing (yeah, I started it...). Ben's intent here is to *demonstrate* how argv-style info can be passed into device nodes. It seems neat, and nice. We can also make use of a

Re: [RFD w/info-PATCH] device arguments from lookup, partion code in userspace

Ben LaHaise <[EMAIL PROTECTED]> writes: > Hey folks, > > The work-in-progress patch for-demonstration-purposes-only below consists > of 3 major components, and is meant to start discussion about the future > direction of device naming and its interaction block layer. The main > motivations

Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace

Andrew Morton writes: > > (2) what about bootstrapping? how do you find the root device? > > Do you do "root=/dev/hda/offset=63,limit=1235823"? Bit nasty. > > Ben's patch makes initrd mandatory. Can this be fixed? I've *never* had to futz with initrd. Probably most

Re: [RFD w/info-PATCH] device arguments from lookup, partion code in userspace

From: Ben LaHaise <[EMAIL PROTECTED]> 3. Userspace partition code proposal Given the above two bits, here's a brief explaination of a proposal to move management of the partitioning scheme into userspace, along with portions of raid startup, lvm, uuid and

Re: CML2 design philosophy heads-up

In article <[EMAIL PROTECTED]> you wrote: > Second, how many kernels does Redhat ship in order to have one for > 386/486/586/k6/Athlon . . . . We build a lot of them :) > Quite a pain in the ass. And look at how much shit has to be built in > in order to get a kernel that works for

Re: alpha iommu fixes

On Fri, May 18, 2001 at 10:34:36PM -0400, Tom Vier wrote: > hose->sg_pci = iommu_arena_new(hose, 0xc000, 0x0800, 32768); > *(vip)CIA_IOC_PCI_W3_BASE = 0xc000 | 1; > *(vip)CIA_IOC_PCI_W3_MASK = (0x0800 - 1) & 0xfff0; > *(vip)CIA_IOC_PCI_T3_BASE =

Re: LANANA: To Pending Device Number Registrants

Hi! > > > > But no, I don't actually like sockets all that much myself. They are hard > > > > to use from scripts, and many more people are familiar with open/close and > > > > read/write. > > > > > > Agreed. > > > > > > It would be nice to use open/close/read/write for control and bulk and >

no ioctls for serial ports? [was Re: LANANA: To Pending Device Number Registrants]

Hi! > > > They might also be exactly the same channel, except with certain magic > > > bits set. The example peter gave was fine: tty devices could very usefully > > > be opened with something like > > > > > > fd = open("/dev/tty00/nonblock,9600,n8", O_RDWR); > > > > > > where we actually

Re: CML2 design philosophy heads-up

Pete Zaitcev wrote: >>[about Aunt Tullie] >>Because, for example, a kernel compile can be a part of the standard >>install now, and you will end up with a kernel built specifically for >>your machine that doesn't print 50 initialization failed messages on boot. >>[...] >>And you can also now

Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace

In article <[EMAIL PROTECTED]> I wrote: >The only problem I can see with this is that it removes one useful thing, >the ability to give a user access to a whole partition. > >chown wingel /dev/hda5 > >won't work anymore since there is no such device node. Apologies, this should have gone

Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace

In article <[EMAIL PROTECTED]> you write: >3. Userspace partition code proposal > > Given the above two bits, here's a brief explaination of a > proposal to move management of the partitioning scheme into > userspace, along with portions of raid startup, lvm, uuid and >

Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace

Alexander Viro wrote: > > > (2) what about bootstrapping? how do you find the root device? > > Do you do "root=/dev/hda/offset=63,limit=1235823"? Bit nasty. > > Ben's patch makes initrd mandatory. > Can this be fixed? I've *never* had to futz with initrd. Probably most systems are the

Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace

On Sat, 19 May 2001, Andrew Morton wrote: > Alexander Viro wrote: > > > > > (2) what about bootstrapping? how do you find the root device? > > > Do you do "root=/dev/hda/offset=63,limit=1235823"? Bit nasty. > > > > Ben's patch makes initrd mandatory. > > > > Can this be fixed? I've

VIA's Southbridge bug: Latest (pseudo-)patch

This are the latest suggestions for handling the VIA Southbridge bug as derived from the hardware site www.au-ja.de (Many thanks to doelf). Could a linux kernel specialist review and form this pseudo-patch to a real kernel patch? Given the "old" patch found in 2.4.4 I could have written the part

Re: LANANA: To Pending Device Number Registrants

[EMAIL PROTECTED] (Jonathan Lundell) wrote on 17.05.01 in : > At 11:23 PM +0200 2001-05-17, Kai Henningsen wrote: > >[EMAIL PROTECTED] (Jonathan Lundell) wrote on 15.05.01 in > >: > > > >> What about: > >> > >> 1

Re: LANANA: To Pending Device Number Registrants

[EMAIL PROTECTED] (Johannes Erdfelt) wrote on 17.05.01 in <[EMAIL PROTECTED]>: > On Thu, May 17, 2001, Kai Henningsen <[EMAIL PROTECTED]> wrote: > > [EMAIL PROTECTED] (Johannes Erdfelt) wrote on 15.05.01 in > > <[EMAIL PROTECTED]>: > > > > > I had always made the assumption that sockets were

"Why We Should All Test the New Linux Kernel" updated

I have updated my article "Why We Should All Test the New Linux Kernel" that was originally posted on Advogato just before 2.4.0 was release and posted it in a new location: http://linuxquality.sunsite.dk/articles/whytestkernel/ I welcome your comments, please write to [EMAIL PROTECTED] A

Hang on boot using latest -ac kernels with irda

Hello, My HP Omnibook 5700CTX running redhat 7.0 and kernel 2.4.4-ac8 and up (I haven't verified on older kernels) hangs on boot when bringing up interface lo. Sometimes I experience an Oops at this point, one of which I have copied by hand and decoded below. When I boot a kernel without irda,

Re: Using Parallel Port to Receive Signals

>I am trying to use the data port of parallel port to receive data, so I= > set the bit 5 of the control port to enable the bi-directional port, b= >ut it doesn't work. My parallel supports SPP/EPP/ECP mode, does it sup= >port bi-directional mode? if yes, how can I config it? You might have to

Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace

On Sat, 19 May 2001, Ben LaHaise wrote: > On Sat, 19 May 2001, Alexander Viro wrote: > > > On Sat, 19 May 2001, Ben LaHaise wrote: > > > > > It's not done yet, but similar techniques would be applied. I envision > > > that a raid device would support operations such as > > >

Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace

On Sat, 19 May 2001, Andrew Clausen wrote: > Alexander Viro wrote: > > On Sat, 19 May 2001, Andrew Clausen wrote: > > > > > (1) these issues are independent. The partition parsing could > > > be done in user space, today, by blkpg, if I read the code correctly > > > ;-) (there's an ioctl

Re: Linux scalability?

On Fri, 18 May 2001, Sean Hunter wrote: > Why would you want to run a web server with 8 processors rather than four > webservers with 2 each? As you might already know, after the interviews to Mingo I assumed, that a major portion of the achievements was enabled by the 2.4 scalability

Re: Linux scalability?

On 18 May 2001, reiser.angus wrote: > not really the same box > look at the disk subsystem > 7 x 9GB 10KRPM Drives and 1 x 18GB 15KRPM (html+log & os) for Win2000 > 5 x 9GB 10KRPM Drives (html+log+os) for TUX 2.0 > this is sufficient for a such difference Don't you think that all the really

Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace

On Sat, 19 May 2001, Alexander Viro wrote: > On Sat, 19 May 2001, Ben LaHaise wrote: > > > It's not done yet, but similar techniques would be applied. I envision > > that a raid device would support operations such as > > open("/dev/md0/slot=5,hot-add=/dev/sda") > > Think for a moment and

Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace

On Sat, 19 May 2001, Ben LaHaise wrote: > It's not done yet, but similar techniques would be applied. I envision > that a raid device would support operations such as > open("/dev/md0/slot=5,hot-add=/dev/sda") Think for a moment and you'll see why it's not only ugly as hell, but simply won't

Re: Linux 2.4.4 folks

Hi, On Sat, 19 May 2001, Peter Zaitsev wrote: > Hello linux-kernel, > > I've trying to move some of my servers to 2.4.4 kernel from 2.2.x. > Everything goes fine, notable perfomance increase occures, but the > problem is I'm really often touch the following problem: > The problem is

Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace

On Sat, 19 May 2001, Andrew Clausen wrote: > (1) these issues are independent. The partition parsing could > be done in user space, today, by blkpg, if I read the code correctly > ;-) (there's an ioctl for [un]registering partitions) Never > tried it though ;-) I tried to imply that through

Re: Bad udelay usage in drivers/net/aironet4500_card.c

H . J . Lu wrote: > > In 2.4.4, drivers/net/aironet4500_card.c has > udelay(10); > udelay(20); > udelay(25); > > But on ia32, you cannot use more than 2 for udelay (). You will get > undefined symbol, __bad_udelay. mv driver.c driver.c~ sed 's/udelay\(

Linux RAID5 issues.

Hello linux-kernel, I'm using software raid5 on about 30 servers, and Yet twice I had a serious data loss becouse of the behavior of linux RAID device. In several cases I've got more then one of drives completely disconnected. I have no ideas why this happened but this had

Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace

On Sat, 19 May 2001, Andrew Clausen wrote: > (1) these issues are independent. The partition parsing could > be done in user space, today, by blkpg, if I read the code correctly > ;-) (there's an ioctl for [un]registering partitions) Never > tried it though ;-) ioctls are even more evil

Linux 2.4.4 folks

Hello linux-kernel, I've trying to move some of my servers to 2.4.4 kernel from 2.2.x. Everything goes fine, notable perfomance increase occures, but the problem is I'm really often touch the following problem: __alloc_pages: 1-order allocation failed. __alloc_pages: 1-order allocation

Re: Linux 2.4.4-ac10

On Fri, 18 May 2001, Rik van Riel wrote: > On Fri, 18 May 2001, Stephen C. Tweedie wrote: > > On Fri, May 18, 2001 at 07:44:39PM -0300, Rik van Riel wrote: > > > > > This is the core of why we cannot (IMHO) have a discussion > > > of whether a patch introducing new VM tunables can go in: > > >

MSI6321 + PDC20265 + reiserfs + IBM deskstar => kernel BUG

Running kernel 2.4.4 w/Jeff Garzik's via-apic patch, using reiserfs on a IBM Deskstar on the PDC20265 of a MSI-6321, some weird shtuff starts happening. # mount /dev/hde /mnt reiserfs: checking transaction log (device 21:00) ... hde: timeout waiting for DMA ide_dmaproc: chipset

Re: CML2 design philosophy heads-up

>[about Aunt Tullie] > Because, for example, a kernel compile can be a part of the standard > install now, and you will end up with a kernel built specifically for > your machine that doesn't print 50 initialization failed messages on boot. >[...] > And you can also now run a kernel built for

Re: Linux-2.4.4 failure to compile

On Fri, 18 May 2001, Lorenzo Marcantonio wrote: > On Thu, 17 May 2001, H. Peter Anvin wrote: > > > I think the header file you're talking about is the db1 header file, > > which has nothing to do with yacc -- it's the Berkeley libdb version 1, > > which is a pretty bad thing to require. > > >

[RFD w/info-PATCH] device arguments from lookup, partion code inuserspace

Hey folks, The work-in-progress patch for-demonstration-purposes-only below consists of 3 major components, and is meant to start discussion about the future direction of device naming and its interaction block layer. The main motivations here are the wasting of minor numbers for partitions,

Re: Linux-2.4.4 failure to compile

On Fri, 18 May 2001, Lorenzo Marcantonio wrote: On Thu, 17 May 2001, H. Peter Anvin wrote: I think the header file you're talking about is the db1 header file, which has nothing to do with yacc -- it's the Berkeley libdb version 1, which is a pretty bad thing to require. I've got

Re: CML2 design philosophy heads-up

[about Aunt Tullie] Because, for example, a kernel compile can be a part of the standard install now, and you will end up with a kernel built specifically for your machine that doesn't print 50 initialization failed messages on boot. [...] And you can also now run a kernel built for your

MSI6321 + PDC20265 + reiserfs + IBM deskstar = kernel BUG

Running kernel 2.4.4 w/Jeff Garzik's via-apic patch, using reiserfs on a IBM Deskstar on the PDC20265 of a MSI-6321, some weird shtuff starts happening. # mount /dev/hde /mnt reiserfs: checking transaction log (device 21:00) ... hde: timeout waiting for DMA ide_dmaproc: chipset

Re: Linux 2.4.4-ac10

On Fri, 18 May 2001, Rik van Riel wrote: On Fri, 18 May 2001, Stephen C. Tweedie wrote: On Fri, May 18, 2001 at 07:44:39PM -0300, Rik van Riel wrote: This is the core of why we cannot (IMHO) have a discussion of whether a patch introducing new VM tunables can go in: there is no

Linux 2.4.4 folks

Hello linux-kernel, I've trying to move some of my servers to 2.4.4 kernel from 2.2.x. Everything goes fine, notable perfomance increase occures, but the problem is I'm really often touch the following problem: __alloc_pages: 1-order allocation failed. __alloc_pages: 1-order allocation

Linux RAID5 issues.

Hello linux-kernel, I'm using software raid5 on about 30 servers, and Yet twice I had a serious data loss becouse of the behavior of linux RAID device. In several cases I've got more then one of drives completely disconnected. I have no ideas why this happened but this had

Re: Bad udelay usage in drivers/net/aironet4500_card.c

H . J . Lu wrote: In 2.4.4, drivers/net/aironet4500_card.c has udelay(10); udelay(20); udelay(25); But on ia32, you cannot use more than 2 for udelay (). You will get undefined symbol, __bad_udelay. mv driver.c driver.c~ sed 's/udelay\(

Re: Linux 2.4.4 folks

Hi, On Sat, 19 May 2001, Peter Zaitsev wrote: Hello linux-kernel, I've trying to move some of my servers to 2.4.4 kernel from 2.2.x. Everything goes fine, notable perfomance increase occures, but the problem is I'm really often touch the following problem: allocation failures

Re: Linux scalability?

On 18 May 2001, reiser.angus wrote: not really the same box look at the disk subsystem 7 x 9GB 10KRPM Drives and 1 x 18GB 15KRPM (html+log os) for Win2000 5 x 9GB 10KRPM Drives (html+log+os) for TUX 2.0 this is sufficient for a such difference Don't you think that all the really needed

Re: Linux scalability?

On Fri, 18 May 2001, Sean Hunter wrote: Why would you want to run a web server with 8 processors rather than four webservers with 2 each? As you might already know, after the interviews to Mingo I assumed, that a major portion of the achievements was enabled by the 2.4 scalability

HangOops on boot using latest -ac kernels with irda

Hello, My HP Omnibook 5700CTX running redhat 7.0 and kernel 2.4.4-ac8 and up (I haven't verified on older kernels) hangs on boot when bringing up interface lo. Sometimes I experience an Oops at this point, one of which I have copied by hand and decoded below. When I boot a kernel without irda,

Re: Using Parallel Port to Receive Signals

I am trying to use the data port of parallel port to receive data, so I= set the bit 5 of the control port to enable the bi-directional port, b= ut it doesn't work. My parallel supports SPP/EPP/ECP mode, does it sup= port bi-directional mode? if yes, how can I config it? You might have to

Why We Should All Test the New Linux Kernel updated

I have updated my article Why We Should All Test the New Linux Kernel that was originally posted on Advogato just before 2.4.0 was release and posted it in a new location: http://linuxquality.sunsite.dk/articles/whytestkernel/ I welcome your comments, please write to [EMAIL PROTECTED] A number

Re: LANANA: To Pending Device Number Registrants

[EMAIL PROTECTED] (Johannes Erdfelt) wrote on 17.05.01 in [EMAIL PROTECTED]: On Thu, May 17, 2001, Kai Henningsen [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] (Johannes Erdfelt) wrote on 15.05.01 in [EMAIL PROTECTED]: I had always made the assumption that sockets were created because

Re: LANANA: To Pending Device Number Registrants

[EMAIL PROTECTED] (Jonathan Lundell) wrote on 17.05.01 in p05100301b72a335d4b61@[10.128.7.49]: At 11:23 PM +0200 2001-05-17, Kai Henningsen wrote: [EMAIL PROTECTED] (Jonathan Lundell) wrote on 15.05.01 in p05100316b7272cdfd50c@[207.213.214.37]: What about: 1 (network domain). I

VIA's Southbridge bug: Latest (pseudo-)patch

This are the latest suggestions for handling the VIA Southbridge bug as derived from the hardware site www.au-ja.de (Many thanks to doelf). Could a linux kernel specialist review and form this pseudo-patch to a real kernel patch? Given the old patch found in 2.4.4 I could have written the part

Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace

In article [EMAIL PROTECTED] you write: 3. Userspace partition code proposal Given the above two bits, here's a brief explaination of a proposal to move management of the partitioning scheme into userspace, along with portions of raid startup, lvm, uuid and mount by

Re: [RFD w/info-PATCH] device arguments from lookup, partion code inuserspace

In article [EMAIL PROTECTED] I wrote: The only problem I can see with this is that it removes one useful thing, the ability to give a user access to a whole partition. chown wingel /dev/hda5 won't work anymore since there is no such device node. Apologies, this should have gone to

Re: CML2 design philosophy heads-up

Pete Zaitcev wrote: [about Aunt Tullie] Because, for example, a kernel compile can be a part of the standard install now, and you will end up with a kernel built specifically for your machine that doesn't print 50 initialization failed messages on boot. [...] And you can also now run a kernel

no ioctls for serial ports? [was Re: LANANA: To Pending Device Number Registrants]

Hi! They might also be exactly the same channel, except with certain magic bits set. The example peter gave was fine: tty devices could very usefully be opened with something like fd = open(/dev/tty00/nonblock,9600,n8, O_RDWR); where we actually open up exactly the same

Re: LANANA: To Pending Device Number Registrants

Hi! But no, I don't actually like sockets all that much myself. They are hard to use from scripts, and many more people are familiar with open/close and read/write. Agreed. It would be nice to use open/close/read/write for control and bulk and sockets for interrupt

Re: alpha iommu fixes

On Fri, May 18, 2001 at 10:34:36PM -0400, Tom Vier wrote: hose-sg_pci = iommu_arena_new(hose, 0xc000, 0x0800, 32768); *(vip)CIA_IOC_PCI_W3_BASE = 0xc000 | 1; *(vip)CIA_IOC_PCI_W3_MASK = (0x0800 - 1) 0xfff0; *(vip)CIA_IOC_PCI_T3_BASE = 0x8000

Re: CML2 design philosophy heads-up

In article [EMAIL PROTECTED] you wrote: Second, how many kernels does Redhat ship in order to have one for 386/486/586/k6/Athlon . . . . We build a lot of them :) Quite a pain in the ass. And look at how much shit has to be built in in order to get a kernel that works for everybody!

Re: VIA/PDC/Athlon - IDE error theory

Alan Cox wrote: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } CRC errors are cable errors so that bit is reasonable in itself Could this be caused by the RAID configuration? The first sector of the first disk holds the

icache flushing in kernel/ptrace.c

I would like to change kernel/ptrace.c to call something else instead of flush_icache_page in access_one_page in kernel/ptrace.c. Currently it calls flush_icache_page on the page after modifying it. Now of course on many architectures (including PPC) we need to do some sort of i-cache flush -

Re: VIA/PDC/Athlon - IDE error theory

Wilfried Weissmann wrote: hda: dma_intr: error=0x84 { DriveStatusError BadCRC } hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } CRC errors are cable errors so that bit is reasonable in itself Could this be caused by the RAID configuration? The first sector of the Yes, it's

Re: Linux-2.4.4 failure to compile

On Fri, May 18, 2001 at 04:41:16PM +0600, Anuradha Ratnaweera wrote: On Fri, 18 May 2001, Lorenzo Marcantonio wrote: On Thu, 17 May 2001, H. Peter Anvin wrote: I think the header file you're talking about is the db1 header file, which has nothing to do with yacc -- it's the

[PATCH] winbond-840 update

Minor update to the winbond-840 driver: * improved SMP locking, one or 2 races fixed. * memory leak in _close fixed. * partial implementation of _suspend and _resume. The chip is disabled and restarted, but not yet put into sleep mode. [lack of hardware to test it] -- Manfred ---

Re: /dev/sch0 interface

On May 15, 6:35pm, Jeff V. Merkey wrote: } Subject: Re: /dev/sch0 interface On Tue, May 15, 2001 at 11:44:23PM +, Thorsten Kranzkowski wrote: On Tue, May 15, 2001 at 03:08:01PM -0600, Jeff V. Merkey wrote: Is anyone actuaslly using the /dev/sch0 interface for SCSI tape changers in

Re: alpha iommu fixes

On Fri, May 18, 2001 at 09:46:17PM +0400, Ivan Kokshaysky wrote: The most interesting thing here is the pyxis tbia fix. Whee! I can now copy files from SCSI to bus-master IDE, or between two IDE drives on separate channels, or do other nice things without hanging lx/sx164. :-) The pyxis tbia

Re: dget()

[EMAIL PROTECTED] said: # cd /usr/src/linux # find -name '*.[ch]' | ctags -L- On 15 May 2001, Xavier Bestel wrote: # cd /usr/src/linux # make tags No, I never use that one because it skips very useful entries like the ones from EXPORT_SYMBOL etc. Also, it only shows the current

Negative inode-nr ?

Hello all, I was investigating a problem we believed we had with our monitoring software (from sysorb.com), where it failed to report the number of free and allocated inodes. However, looking into the problem I found that it's the kernel that's returning bogus values. What do you think of

Q: fdatasync on block device?

Hi, Could someone enlighten me whether fdatasync() system call on Linux, when called on the fd of an open()-ed block device, will result in the committing of all dirty device buffers to disk? If not, how do I achieve this? Should I use the BLKFLSBUF ioctl? Thanks in advance. Best regards,

Q: ioctl BLKGETSIZE return value units?

Hi, What are the units of the return value of the BLKGETSIZE ioctl on Linux? Is it allways in units of 512 bytes or is it in units of sector size bytes as returned by BLKSSZGET ioctl? Thanks in advance. Best regards, Anton -- Anton Altaparmakov aia21 at cam.ac.uk (replace at

<    1   2   3   4   >