Re: goodbye

2001-04-07 Thread Graham Murray
Matti Aarnio <[EMAIL PROTECTED]> writes: > I just verified this particular aspect of VGER's MTA > configurations. It has been unmodified since 21-Mar-2000, > that is, over a year... On the subject of vger configuration, the FAQ states that vger "will" start using ECN as of 22

Re: goodbye

2001-04-07 Thread Stephen Satchell
At 09:02 PM 4/7/01 -0700, Joseph Carter wrote: >Not always an option. There are many places in the world in which your >ISP is a monopoly. And even in your simplistic view of the world, there >are many places in the United States where you are held captibe by not >having more than one local

Re: aic7xxx 6.1.10 and 2.4.4-pre1

2001-04-07 Thread lists
Well my aicxxx problems continue: I did it again and indeed verified similar error messages as I had under stock 2.4.3 and 2.4.3+aic 6.1.8. This time it died during boot itself starting with complaints from ssh/xinet et al - then I started seeing the scsi errors. (I believe I had also

Re: goodbye

2001-04-07 Thread David Fries
On Sun, Apr 08, 2001 at 02:32:28AM +0300, Matti Aarnio wrote: > On Tue, Apr 03, 2001 at 06:14:33PM -0700, Michael Peddemors wrote: > Well, comparing how much spam goes thru linux-mm vs. linux-kernel, > I would say our methods are fairly effective. > > The incentive behind the

Re: aic7xxx 6.1.10 and 2.4.4-pre1

2001-04-07 Thread lists
I used 5000ms. I still freeze up with 2.4.3 + 6.1.10. Unfortunately i could not see any messages and nothing got logged. This time an fsck allowed me to boot back to 2.4.1. The visible symptoms were the same as before (2.4.3 + 6.1.8) but this time I was unable to flip virtual consoles before

Re: goodbye

2001-04-07 Thread Ralf Baechle
On Sun, Apr 08, 2001 at 02:32:28AM +0300, Matti Aarnio wrote: > The incentive behind the DUL is to force users not to post > straight out to the world, but to use their ISP's servers > for outbound email --- normal M$ users do that, after all. > Only spammers - and UNIX

Re: goodbye

2001-04-07 Thread Joseph Carter
On Sun, Apr 08, 2001 at 12:56:21PM +1000, john slee wrote: > > Some ISPs rely on crap software & OS to process email, and have other > > so you don't use those ISPs Not always an option. There are many places in the world in which your ISP is a monopoly. And even in your simplistic view of

patch-2.4.4-pre1.bz2 fails

2001-04-07 Thread Garst R. Reese
patching kernel 2.4.3 in /usr/src/linux cd /usr/src bunzip2 -c ~/kpatch/patch-2.4.4-pre1.bz2 | patch -p0 -E as I have done hundreds of times. tons of failed hunks and previously applied patches. I can patch my backup of 2.4.0 -> 2.4.1 -> 2.4.2 -> 2.4.3 with no problem. Please cc me as I can only

Re: goodbye

2001-04-07 Thread john slee
On Sat, Apr 07, 2001 at 07:07:20PM -0700, Colonel wrote: > Some ISPs rely on crap software & OS to process email, and have other so you don't use those ISPs > bad habits besides. Censorship usually does more bad than good > (especially since dealing with 80% of the spam is trivial for >

RE: Compaq proliant ML-350 - IDE & SCSI

2001-04-07 Thread Cagle, John
On 04/07/2001 21:55:53, Alexandru Barloiu Nicolae wrote: > I am trying to use the DMA on the ide drives. After the reboot Dma is > enabled but if I don't disable it with hdparm the system freezes at heavy > work (copy something from a drive to the other). The SCSI works ok. Without > the DMA the

Re: goodbye

2001-04-07 Thread Colonel
In list.kernel, you wrote: > >On Tue, Apr 03, 2001 at 06:14:33PM -0700, Michael Peddemors wrote: >> I think that this is one list where we have to keep the ability to post >> from individuals separate from the need to make sure that their ISP or >> company is compliant to a set a of rules.. The

Re: uninteruptable sleep

2001-04-07 Thread Anton Blanchard
> That happened to me with 2.4.2-ac28 when I tried using DRM. > I also got the following messages in syslog. > > /var/log/messages.1:Mar 31 12:15:04 joker kernel: > [drm:r128_do_wait_for_fifo] *ERROR* r128_do_wait_for_fifo failed! You need to replace down(...->mmap_sem), up(...->mmap_sem) with

Re: P-III Oddity.

2001-04-07 Thread Dave Jones
On Sat, 7 Apr 2001, Trevor Hemsley wrote: > I've got this on my dual processor P-III 600MHz. One of the cpus in > this box reports cpuid level 2, the other 3. Serial number is disabled > in the BIOS. Interesting, the cpu serial number isn't being disabled on the 2nd CPU. Most odd. Well, we

Re: aic7xxx 6.1.10 breaks 2.4.3-ac3

2001-04-07 Thread Justin T. Gibbs
>Once you said 'here is my site for this certain soft updates', you can't >excpect that people do not check it in a regular basis, did you announce >anything or not. I'm not expecting anything. I just find it amusing when people grab stuff that has no instructions, don't look at what they've

Re: aic7xxx 6.1.10 and 2.4.4-pre1

2001-04-07 Thread Justin T. Gibbs
>NORET_TYPE void panic(const char * fmt, ...) >__attribute__ ((NORET_AND format (printf, 1, 2))); >^ > >Similar cases, compare include/linux/raid/md_k.h:pers_to_level() in >2.4.3 and 2.4.3-ac3. Then gcc is not honoring the attribute. The only way for that

Re: P-III Oddity.

2001-04-07 Thread CaT
On Sat, Apr 07, 2001 at 09:56:40PM +0200, Dave Jones wrote: > On Sat, 7 Apr 2001, Rogier Wolff wrote: > > > One machine regularly crashes. > > Linux version 2.2.16-3 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 >19990314/Linux (egcs-1.1.2 release)) #1 Mon Jun 19 19:11:44 EDT 2000 > > Probably

Re: aic7xxx 6.1.10 and 2.4.4-pre1

2001-04-07 Thread J . A . Magallon
On 04.08 Justin T. Gibbs wrote: > > > > In file included from aic7xxx_linux.c:131: > > aic7xxx_osm.h: In function `ahc_pci_read_config': > > aic7xxx_osm.h:862: warning: control reaches end of non-void function > > This is because panic() is not marked as a "no return" function. So,

Re: aic7xxx 6.1.10 breaks 2.4.3-ac3

2001-04-07 Thread J . A . Magallon
On 04.08 Justin T. Gibbs wrote: > > Actually, I would say, "Apply the 2.4.3 patch. It will probably apply > cleanly to your kernel. If it doesn't, and you don't know enough C > to correct the problem, you shouldn't be playing around with kernel > patches." > Below is inlined the patch that

Re: [Lse-tech] Re: [PATCH for 2.5] preemptible kernel

2001-04-07 Thread Paul McKenney
> > > > 2. Isn't it possible to get in trouble even on a UP if a task > > > > is preempted in a critical region? For example, suppose the > > > > preempting task does a synchronize_kernel()? > > > > > > Ugly. I guess one way to solve it would be to readd the 2.2 scheduler > > >

Re: [Lse-tech] Re: [PATCH for 2.5] preemptible kernel

2001-04-07 Thread Paul McKenney
> > I see your point here, but need to think about it. One question: > > isn't it the case that the alternative to using synchronize_kernel() > > is to protect the read side with explicit locks, which will themselves > > suppress preemption? If so, why not just suppress preemption on the read

ATM with kernel 2.4.x

2001-04-07 Thread Stéphane Borel
Hello, we're trying to make a ForeRunnerLE 155 card work and we face several problems: -with kernel 2.4.3, we get unresolved symbol as we insmod lec -with kernel 2.4.0-2.4.2 the sytem hangs when we try to start the atm softs (ilmid) So it only works with kernel <= 2.4.0-test12. We're using

Re: aic7xxx 6.1.10 breaks 2.4.3-ac3

2001-04-07 Thread Justin T. Gibbs
>> To be expected as you didn't apply the patch to scsi_lib.c that makes >> scsi_unblock_host() actually run the device queues to start the system >> back up again. >> > >There is no patch for 2.4.3-ac3. You could say, well if you want 6.1.10, >use plain 2.4.3. Actually, I would say, "Apply the

Re: goodbye

2001-04-07 Thread Matti Aarnio
On Tue, Apr 03, 2001 at 06:14:33PM -0700, Michael Peddemors wrote: > This would be a shame, as he has been a valuable resource.. > Why has the list become more restrictive? I just verified this particular aspect of VGER's MTA configurations. It has been unmodified since

Re: aic7xxx 6.1.10 and 2.4.4-pre1

2001-04-07 Thread Justin T. Gibbs
> So I started again - installed redhat 7.0.9. > took 2.4.4-pre1 and patched it with > linux-aic7xxx-6.1.10-2.4.3.patch > > Patch applied cleanly but when I compile it complains a little: > > In file included from aic7xxx_linux.c:131: > aic7xxx_osm.h: In function

Lost timer configuration

2001-04-07 Thread Shane Wegner
Hi, As this doesn't seem to do anything, I'm not too concerned. However, I'm getting messages like these in my kernlog quite regularly. Apr 7 15:20:31 continuum kernel: probable hardware bug: clock timer configuration lost - probably a VIA686a. Apr 7 15:20:31 continuum kernel: probable

Re: P-III Oddity.

2001-04-07 Thread Trevor Hemsley
On Sat, 7 Apr 2001 19:58:15, Dave Jones <[EMAIL PROTECTED]> wrote: > On Sat, 7 Apr 2001, Rogier Wolff wrote: > > > One machine regularly crashes. > > Linux version 2.2.16-3 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 >19990314/Linux (egcs-1.1.2 release)) #1 Mon Jun 19 19:11:44 EDT 2000 > >

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Jeff Garzik
Gunther Mayer wrote: > More module interdependencies == More complicated == More clueless users With module autoloading, they don't have to care about module interdependencies. The primary thing people care about is what string is passed to modprobe. When that changes, things break. As long

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Jeff Garzik
Gunther Mayer wrote: > Jeff Garzik wrote: > > Gunther Mayer wrote: > > > Hardware has always needed quirks (linux-2.4.3 has about 60 occurences > > > of the word "quirks", not to mention workaround, blacklist and other synonyms)! > > > > > > Please apply this little patch instead of wasting time

Re: processes stuck in D state

2001-04-07 Thread Barry K. Nathan
Pau Aliagas wrote: > Since 2.2.4-ac28 and 2.4.3 I keep on getting processes in D state that I > cannot kill, usually mozilla or nautilus which use a large amount of RAM. I don't have time to help debug this, but I'm getting this too, with 2.4.3 final. The previous kernel I ran was 2.4.3-pre4,

loop problems continue in 2.4.3

2001-04-07 Thread Ian Eure
i'm still having loopback problems with linux 2.4.3, even though they were supposed to be fixed. it doesn't deadlock my maching right away anymore, but instead causes a kernel panic after 4-6 uses of the loop device. the message i get is: "Kernel panic: Invalid blocksize passed to set_blocksize"

Re: Multi-function PCI devices

2001-04-07 Thread Jeff Garzik
Linus Torvalds wrote: > It only means that you should probably approach it as being a special > "invisible PCI bridge", and basically have a specific driver for that > chip that acts as a _bridge_ driver. > > Writing a bridge driver is not that hard: your init routine will > instantiate the

aic7xxx 6.1.10 and 2.4.4-pre1

2001-04-07 Thread lists
I had tried 6.1.8 + 2.4.3 and had problems which included messages like 'aic7xxx_abort returns 8194' and machine froze up shortly after X started. This on redhat 7.0. Sorry but since I was unable to even boot back the prev kernel (2.4.0) I cant provide any more detailed information.

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Jeff Garzik
Gunther Mayer wrote: > > Jeff Garzik wrote: > > > Like I mentioned in a > > previous message, the Via parport code is ugly and should go into a Via > > superio driver. It is simply not scalable to consider the alternative > > -- add superio code to parport_pc.c for each ISA bridge out there.

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Tim Waugh
On Sat, Apr 07, 2001 at 10:21:11PM +0200, Gunther Mayer wrote: > Many users will be surprised if they must load another module > (e.g."pci_multiio") to get their parallel and serial ports working. > > Thus _must not_ happen in the stable release. Yes, I agree. I am planning for

Re: Multi-function PCI devices

2001-04-07 Thread Linus Torvalds
In article <[EMAIL PROTECTED]>, Michael Reinelt <[EMAIL PROTECTED]> wrote: > >The card shows up on the PCI bus as one device. For the card provides >both serial and parallel ports, it will be driven by two subsystems, the >serial and the parallel driver. Tough. The PCI specification has a

Re: [Lse-tech] Re: [PATCH for 2.5] preemptible kernel

2001-04-07 Thread Andi Kleen
On Fri, Apr 06, 2001 at 06:25:36PM -0700, Paul McKenney wrote: > I see your point here, but need to think about it. One question: > isn't it the case that the alternative to using synchronize_kernel() > is to protect the read side with explicit locks, which will themselves > suppress preemption?

Unresolved symbol in 2.4.4p1, ia32

2001-04-07 Thread Jonathan Hudson
depmod: *** Unresolved symbols in /lib/modules/2.4.4-pre1/kernel/drivers/ide/ide-cd.o depmod: strstr depmod: *** Unresolved symbols in /lib/modules/2.4.4-pre1/kernel/drivers/parport/parport.o depmod: strstr - To unsubscribe from this list: send the line

Config files for Compaq Presario 1800T Laptop

2001-04-07 Thread Michael D. Crawford
I have found that kernel 2.4.3 and XFree86 4.0.3 work very well on my Compaq Presario 1800T laptop. I did a lot of fiddling to get things just right, so to make things easer for other Presario 1800 owners I have archived my kernel .config, lilo.conf and XF86Config files here:

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Gunther Mayer
Gérard Roudier wrote: > > On Sat, 7 Apr 2001, Tim Waugh wrote: > > > On Sat, Apr 07, 2001 at 08:42:35PM +0200, Gunther Mayer wrote: > > > > > Please apply this little patch instead of wasting time by > > > finger-pointing and arguing. > > > > This patch would make me happy. > > > > It would

Re: i810_audio.c: Clicks while playing audio

2001-04-07 Thread Doug Ledford
Naren Devaiah wrote: > > Hi, > > On a HP Vectra VL 400 with a i815 motherboard playing a .wav file (haven't > tried anything else) causes the sound to be played with a lot of periodic > clicks. > The kernel is 2.4.3 > dmesg shows: > Intel 810 + AC97 Audio, version 0.01, 17:25:00 Apr 6 2001 >

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Gunther Mayer
Jeff Garzik wrote: > Like I mentioned in a > previous message, the Via parport code is ugly and should go into a Via > superio driver. It is simply not scalable to consider the alternative > -- add superio code to parport_pc.c for each ISA bridge out there. I > think the same principle

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Gunther Mayer
Jeff Garzik wrote: > > Gunther Mayer wrote: > > Hardware has always needed quirks (linux-2.4.3 has about 60 occurences > > of the word "quirks", not to mention workaround, blacklist and other synonyms)! > > > > Please apply this little patch instead of wasting time by finger-pointing > > and

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Gunther Mayer
Jeff Garzik wrote: > > Tim Waugh wrote: > > It would allow support for new multi-IO cards to generally be the > > addition of about two lines to two files (which is currently how it's > > done), rather than having separate mutant hybrid monstrosity drivers > > for each card (IMHO).. > > ;-) >

Re: [PATCH for 2.5] preemptible kernel

2001-04-07 Thread Rusty Russell
In message you write: > > Priority inversion is not handled in Linux kernel ATM BTW, there > > are already situations where a realtime task can cause a deadlock > > with some lower priority system thread (I believe there is at least > > one

Re: P-III Oddity.

2001-04-07 Thread Dave Jones
On Sat, 7 Apr 2001, Rogier Wolff wrote: > One machine regularly crashes. > Linux version 2.2.16-3 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 >19990314/Linux (egcs-1.1.2 release)) #1 Mon Jun 19 19:11:44 EDT 2000 Probably unrelated to the issue below. Try a more recent 2.2 ? > cpuid level

Re: Multi-function PCI devices

2001-04-07 Thread Tim Waugh
On Sat, Apr 07, 2001 at 03:40:13PM -0400, Jeff Garzik wrote: > Who said you have to have a separate driver for every single multi-IO > card? A single driver could support all serial+parallel multi-IO cards, > for example. Okay, I misunderstood. I'll take a look at doing this for 2.4. First

[PATCH][RFC] appling pressure to icache and dcache - simplified

2001-04-07 Thread Ed Tomlinson
Hi, Rik asked, "Can it be made simpler?" So I went back to the basics, inserted a printk in kswapd and watched the dentry_stat and inodes_stat numbers for a while. I observed the following pattern. The dentry cache grows as does the number of unused entries in it. Unless we shrink this

Re: Multi-function PCI devices

2001-04-07 Thread Jeff Garzik
Tim Waugh wrote: > If we have to do this, then Gunther's approach (multifunc_quirks or > whatever) looks a lot better than having a separate driver for every > single multi-IO card. Who said you have to have a separate driver for every single multi-IO card? A single driver could support all

Re: [PATCH for 2.5] preemptible kernel

2001-04-07 Thread Paul McKenney
Andi, thank you for the background! More comments interspersed... > On Fri, Apr 06, 2001 at 04:52:25PM -0700, Paul McKenney wrote: > > 1. On a busy system, isn't it possible for a preempted task > > to stay preempted for a -long- time, especially if there are > > lots of real-time

P-III Oddity.

2001-04-07 Thread Rogier Wolff
Hi, One machine regularly crashes. Linux version 2.2.16-3 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Jun 19 19:11:44 EDT 2000 processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 7 model name : Pentium

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Gérard Roudier
On Sat, 7 Apr 2001, Tim Waugh wrote: > On Sat, Apr 07, 2001 at 08:42:35PM +0200, Gunther Mayer wrote: > > > Please apply this little patch instead of wasting time by > > finger-pointing and arguing. > > This patch would make me happy. > > It would allow support for new multi-IO cards to

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Tim Waugh
On Sat, Apr 07, 2001 at 03:23:12PM -0400, Jeff Garzik wrote: > It's just ugly to keep hacking in special cases to handle hardware > that is multifunction like this. I just don't want it to be a huge chore to add support for these cards. Would everyone be happy if (say)

Re: Multi-function PCI devices

2001-04-07 Thread Jeff Garzik
Tim Waugh wrote: > > On Sat, Apr 07, 2001 at 01:23:27PM -0400, Jeff Garzik wrote: > > > You asked in your last message to show you code, here is a short > > example. Note that I would love to rip out the SUPERIO code in parport > > and make it a separate driver like this short, contrived

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Jeff Garzik
Tim Waugh wrote: > It would allow support for new multi-IO cards to generally be the > addition of about two lines to two files (which is currently how it's > done), rather than having separate mutant hybrid monstrosity drivers > for each card (IMHO).. ;-) My point of view is that hacking the

Re: Multi-function PCI devices

2001-04-07 Thread Tim Waugh
On Sat, Apr 07, 2001 at 03:01:57PM +0200, Gérard Roudier wrote: > PCI multi I/O boards _shall_ provide a separate function for each kind of > IO. Those that donnot are kind of PCI messy IO boards. But they don't. What are you going to do about it? > Cheap for whom? For the guys who make

Re: Multi-function PCI devices

2001-04-07 Thread Tim Waugh
On Sat, Apr 07, 2001 at 01:23:27PM -0400, Jeff Garzik wrote: > You asked in your last message to show you code, here is a short > example. Note that I would love to rip out the SUPERIO code in parport > and make it a separate driver like this short, contrived example. Much > more modular than

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Tim Waugh
On Sat, Apr 07, 2001 at 02:53:23PM -0400, Jeff Garzik wrote: > As has been explained, the current API supports this just fine without > modification. The current API makes it much harder to support the breadth of hardware we're talking about. The hardware has quirks, and this quirk is so

Re: 2.4 kernel hangs on 486 machine at boot

2001-04-07 Thread Brian Gerst
Pavel Machek wrote: > > Hi! > > > > > Problem: Linux kernel 2.4 consistently hangs at boot on 486 machine > > > > > > > > Shortly after lilo starts the kernel it hangs at the following message: > > > > Checking if this processor honours the WP bit even in supervisor mode... > > > > > > > > > >

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Tim Waugh
On Sat, Apr 07, 2001 at 08:42:35PM +0200, Gunther Mayer wrote: > Please apply this little patch instead of wasting time by > finger-pointing and arguing. This patch would make me happy. It would allow support for new multi-IO cards to generally be the addition of about two lines to two files

Re: Multi-function PCI devices

2001-04-07 Thread Tim Waugh
On Sat, Apr 07, 2001 at 11:04:38AM +0200, Gérard Roudier wrote: > Given your description, this board is certainly not a multi-fonction PCI > device. Multi-function PCI devices provide separate resources for each > function in a way that allows each function to be driven by separate > software

Re: aic7xxx 6.1.10 breaks 2.4.3-ac3

2001-04-07 Thread J . A . Magallon
On 04.07 Justin T. Gibbs wrote: > > That's not a sufficient way to upgrade. The tar files are there for > people who are porting the driver to other platforms. You should always > use the patches to upgrade as they often touch other portions of the > Linux kernel that need fixes in order to

Compaq proliant ML-350 - IDE & SCSI

2001-04-07 Thread Alexandru Barloiu Nicolae
I am trying to use the DMA on the ide drives. After the reboot Dma is enabled but if I don't disable it with hdparm the system freezes at heavy work (copy something from a drive to the other). The SCSI works ok. Without the DMA the system barely moves root@light:~# hdparm -t -T /dev/hda

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Jeff Garzik
Gunther Mayer wrote: > Hardware has always needed quirks (linux-2.4.3 has about 60 occurences > of the word "quirks", not to mention workaround, blacklist and other synonyms)! > > Please apply this little patch instead of wasting time by finger-pointing > and arguing. > > Martin, comments? Is

Re: 2.4 kernel hangs on 486 machine at boot

2001-04-07 Thread Pavel Machek
Hi! > > > Problem: Linux kernel 2.4 consistently hangs at boot on 486 machine > > > > > > Shortly after lilo starts the kernel it hangs at the following message: > > > Checking if this processor honours the WP bit even in supervisor mode... > > > > > > > Does this happen on 2.4.3-ac kernel

Writing to MO-Drive hangs the system

2001-04-07 Thread Detlev Offenbach
Hi out there, I have a problem with my 2.4.3 kernel. I have a 650 MB MO-Disk attached to my computer via SCSI. Partitioning and formatting a disk works fine. However, if the disk is formatted with a DOS filesystem, writing something to it hangs the whole system. Not even the Ctrl-Alt-Del

i810_audio.c: Clicks while playing audio

2001-04-07 Thread Naren Devaiah
Hi, On a HP Vectra VL 400 with a i815 motherboard playing a .wav file (haven't tried anything else) causes the sound to be played with a lot of periodic clicks. The kernel is 2.4.3 dmesg shows: Intel 810 + AC97 Audio, version 0.01, 17:25:00 Apr 6 2001 PCI: Enabling device 00:1f.5 ( ->

Re: Multi-function PCI devices

2001-04-07 Thread Jeff Garzik
Michael Reinelt wrote: > But what I want to know before I spend time (and not-earning-money :-) > into this, I want to know: Is this the right way (TM)? How do other > multiport cards deal with this issue? > > This is a specific question to the serial and parallel maintainers: are > there cards

Re: PATCH for Broken PCI Multi-IO in 2.4.3 (serial+parport)

2001-04-07 Thread Gunther Mayer
Tim Waugh wrote: > > On Sat, Apr 07, 2001 at 04:57:29AM -0400, Jeff Garzik wrote: > > > Where is this patch available? I haven't heard of an extension to the > > pci id tables, so I wonder if it's really in the queue for the official > > kernel. > > It is.

Let init know user wants to shutdown

2001-04-07 Thread Pavel Machek
Hi! Init should get to know that user pressed power button (so it can do shutdown and poweroff). Plus, it is nice to let user know that we can read such event. [I hunted bug for few hours, thinking that kernel does not get the event at all]. Here's patch to do that. Please apply,

Serious bug in ACPI enumeration

2001-04-07 Thread Pavel Machek
Hi! My "toshiba workaround" was not toshiba specific: you stopped scanning at first device that was not present. That's bad, you have to continue scanning. Here's fix. Pavel --- clean/drivers/acpi/namespace/nsxfobj.c Sun Apr

FYI: ACPI devices put into proc

2001-04-07 Thread Pavel Machek
Hi! Here it how it looks just now. This is work in progress, but feel free to apply. [You may want to restructure it somehow, move it into different place maybe, and call its init from convient place]. Oh, and "ACPI_OK" should be killed. It is too easy to write it instead of AE_OK.

Re: Multi-function PCI devices

2001-04-07 Thread Michael Reinelt
Gérard Roudier wrote: > > > Tim Waugh wrote: > > > > Adding PCI entries to both serial.c and parport_pc.c was that easy > > > > > > And that's how it should be, IMHO. There needs to be provision for > > > more than one driver to be able to talk to any given PCI device. > > > > True, true,

2.4.3-ac2 -- How do I determine if shm is being used?

2001-04-07 Thread Miles Lane
I have mounted: none on /var/shm type shm (rw) tmpfs on /dev/shm type tmpfs (rw) Yet, running "x11perf -shmput10" gives me: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 146 (MIT-SHM) Minor opcode of

Re: Multi-function PCI devices

2001-04-07 Thread Jeff Garzik
Brian Gerst wrote: > Gérard Roudier wrote: > > Given your description, this board is certainly not a multi-fonction PCI > > device. Multi-function PCI devices provide separate resources for each > > function in a way that allows each function to be driven by separate > > software drivers. A

UDMA(66) drive coming up as UDMA(33)?

2001-04-07 Thread David St.Clair
I'm trying to get my hard drive to use UDMA/66. I'm thinking the cable is not being detected. When the HPT366 bios is set to UDMA 4; using hdparm -t, I get a transfer rate of 19.51 MB/s. When the HPT366 bios is set to PIO 4 the transfer rate is the same. Is this normal for a UDMA/66 drive? What

Re: Multi-function PCI devices

2001-04-07 Thread Jeff Garzik
Tim Waugh wrote: > > On Sat, Apr 07, 2001 at 01:33:25PM +0200, Michael Reinelt wrote: > > > Adding PCI entries to both serial.c and parport_pc.c was that easy > > And that's how it should be, IMHO. There needs to be provision for > more than one driver to be able to talk to any given PCI

Re: NLS: koi8-u support

2001-04-07 Thread Volodymyr M . Lisivka
On 2001.04.06 22:21:35 +0300 [EMAIL PROTECTED] wrote: > Hello! > > It was added already. But charset name is koi8-ru for > some strange reason Sound good. koi8-ru extends koi8-u(RFC-2319) only by one Byelorussian letter. But standartization of koi8-ru is not finished at this moment and

Re: Multi-function PCI devices

2001-04-07 Thread Gérard Roudier
On Sat, 7 Apr 2001, Michael Reinelt wrote: > Tim Waugh wrote: > > > > On Sat, Apr 07, 2001 at 01:33:25PM +0200, Michael Reinelt wrote: > > > > > Adding PCI entries to both serial.c and parport_pc.c was that easy > > > > And that's how it should be, IMHO. There needs to be provision for

Re: Multi-function PCI devices

2001-04-07 Thread Gérard Roudier
On Sat, 7 Apr 2001, Michael Reinelt wrote: > Brian Gerst wrote: > > > > Gérard Roudier wrote: > > > > > > On Sat, 7 Apr 2001, Michael Reinelt wrote: > > > > > > > The card shows up on the PCI bus as one device. For the card provides > > > > both serial and parallel ports, it will be driven by

Re: aic7xxx 6.1.10 breaks 2.4.3-ac3

2001-04-07 Thread Justin T. Gibbs
>Hi. > >Subject says it all. > >With latest updates, i just deleted the kernel aic7xxx subtree, put instead >the updated (from people.freebsd.org) tree, and built. All went fine >until (and including) 6.1.9. That's not a sufficient way to upgrade. The tar files are there for people who are

Re: linux 2.2.19 smp interrupt problems?

2001-04-07 Thread Armin Obersteiner
hi! thanx, worked. the old driver should be default for 8129 (selecting it for 8139 should be deprecated) and the new one for 8139 ... > > everything seems to work fine. are these interrupt problems "bad" or merely > > indicators of a high load. can/should one get rid of them? > > > Could

aic7xxx 6.1.10 breaks 2.4.3-ac3

2001-04-07 Thread J . A . Magallon
Hi. Subject says it all. With latest updates, i just deleted the kernel aic7xxx subtree, put instead the updated (from people.freebsd.org) tree, and built. All went fine until (and including) 6.1.9. 6.1.10 just stops after the init messages and stays there forever. scsi0 : Adaptec AIC7XXX

Re: Multi-function PCI devices

2001-04-07 Thread Michael Reinelt
Tim Waugh wrote: > > On Sat, Apr 07, 2001 at 01:33:25PM +0200, Michael Reinelt wrote: > > > Adding PCI entries to both serial.c and parport_pc.c was that easy > > And that's how it should be, IMHO. There needs to be provision for > more than one driver to be able to talk to any given PCI

Kernel panic when trying to mount a scsi cdrom.

2001-04-07 Thread Alexandre et/ou Sophie Beneteau
[1.] One line summary of the problem: Kernel panic when trying to mount a scsi cdrom. [2.] Full description of the problem/report: Since version 2.4.2, I get a kernel panic everytime I try to mount an iso9660 cdrom : # mount /dev/scd0 /cdrom Detected scsi CD-ROM sr0 at scsi0, channel 0, id

Re: Multi-function PCI devices

2001-04-07 Thread Michael Reinelt
Brian Gerst wrote: > > Gérard Roudier wrote: > > > > On Sat, 7 Apr 2001, Michael Reinelt wrote: > > > > > The card shows up on the PCI bus as one device. For the card provides > > > both serial and parallel ports, it will be driven by two subsystems, the > > > serial and the parallel driver. > >

Re: Multi-function PCI devices

2001-04-07 Thread Brian Gerst
Gérard Roudier wrote: > > On Sat, 7 Apr 2001, Michael Reinelt wrote: > > > Hi there, > > > > I've got a problem with my communication card: It's a PCI card with a > > NetMos chip, and it provides two serial and one parallel port. It's not > > officially supported by the linux kernel, so I wrote

Re: Multi-function PCI devices

2001-04-07 Thread Tim Waugh
On Sat, Apr 07, 2001 at 01:33:25PM +0200, Michael Reinelt wrote: > Adding PCI entries to both serial.c and parport_pc.c was that easy And that's how it should be, IMHO. There needs to be provision for more than one driver to be able to talk to any given PCI device. Tim. */ PGP signature

Re: Multi-function PCI devices

2001-04-07 Thread Gérard Roudier
On Sat, 7 Apr 2001, Michael Reinelt wrote: > Hi there, > > I've got a problem with my communication card: It's a PCI card with a > NetMos chip, and it provides two serial and one parallel port. It's not > officially supported by the linux kernel, so I wrote my own patch and > sent it to the

problem when booting 2.4.3 from a floppy disk

2001-04-07 Thread François Dupoux
Hi, I have a strange bug when trying to boot a kernel-2.4.3 (official release) from an 1.44 MB floppy disk. Just after the "Loading...", there is an infinite loop, and this message is printed: 0200 AX: 0212 BX: BC00 CX: 5101 DX: 0200 AX: 0212 BX: BC00 CX: 5101 DX: The

ISIcom cards by Multi-tech

2001-04-07 Thread Michael Reinelt
Hi there, who is maintaining the isicom driver? A customer of mine uses such a card in a linux server, when we upgraded from kernel 2.0 to 2.4.3 this week, there have been some minor problems with this card. There is a driver in the official 2.4 tree, but it seems quite old. There are newer

Re: Multi-function PCI devices

2001-04-07 Thread Michael Reinelt
Jeff Garzik wrote: > > Michael Reinelt wrote: > > basically an extension of the pci id tables; and I hope it's in the > > queue for the official kernel. > > Where is this patch available? I haven't heard of an extension to the > pci id tables, so I wonder if it's really in the queue for the

Re: Proper way to release binary driver?

2001-04-07 Thread Christopher Turcksin
Hello, I would like to thank everybody who replied to my question yesterday. There were a lot of good suggestions and examples for me to go and look at. The conclusion we had come to between ourselves here was already very similar to most things suggested, but we were running into some

Re: linux 2.2.19 smp interrupt problems?

2001-04-07 Thread Manfred Spraul
> > everything seems to work fine. are these interrupt problems "bad" or merely > indicators of a high load. can/should one get rid of them? > Could you try the 8139too driver? It's a bug in the rtl8139 driver, and under really high load it can cause crashes. -- Manfred - To

Re: Multi-function PCI devices

2001-04-07 Thread Tim Waugh
On Sat, Apr 07, 2001 at 04:57:29AM -0400, Jeff Garzik wrote: > Where is this patch available? I haven't heard of an extension to the > pci id tables, so I wonder if it's really in the queue for the official > kernel. It is. http://people.redhat.com/twaugh/patches/> The 'extension' is just

reporting a kernel bug

2001-04-07 Thread Petri Järvinen
[1.] One line summary of the problem: machine freezes [2.] Full description of the problem/report: machine freezes when daily.cron runs itself [3.] Keywords (i.e., modules, networking, kernel): kernel [4.] Kernel version (from /proc/version): Linux version 2.4.3s1 (root@setri) (gcc version

Re: Multi-function PCI devices

2001-04-07 Thread Jeff Garzik
Michael Reinelt wrote: > I've got a problem with my communication card: It's a PCI card with a > NetMos chip, and it provides two serial and one parallel port. It's not > officially supported by the linux kernel, so I wrote my own patch and > sent it to the parallel, serial and pci maintainer.

Re: 2.4.3 tcp window id causes problems talking to windows clients

2001-04-07 Thread Alan Cox
> to be working quite well (except for the lack of swap reclamation-- I > appreciate the reasoning, but it makes upgrading older machines very > difficult.) However, I would rather, for maintenance and sanity -ac will acquire swap cache reclaim in time, dunno about Linus tree but I assume it

Re: syslog insmod please!

2001-04-07 Thread Russell King
On Fri, Apr 06, 2001 at 01:50:29PM +0100, Philip Blundell wrote: > Floating point on ARM is indeed something of a crock, but that particular case > used to work -- can you tell where it's going wrong? See entry-armv.S, > about line 680, for the very bad hack that was supposed to facilitate this

Re: Proper way to release binary driver?

2001-04-07 Thread Alan Cox
> We had hoped that MODVERSIONS would allow us to provide a single (or at > most a few) binary driver. Kernels with even minor version numbers are > supposed to be stable (even if they are buggy) ie. not have wildly > changing kernel interfaces. They have a stable API. THe ABI thing is an

Multi-function PCI devices

2001-04-07 Thread Michael Reinelt
Hi there, I've got a problem with my communication card: It's a PCI card with a NetMos chip, and it provides two serial and one parallel port. It's not officially supported by the linux kernel, so I wrote my own patch and sent it to the parallel, serial and pci maintainer. The patch itself is

  1   2   >