Re: test11-pre6 still very broken

2000-11-21 Thread Thomas Sailer
Vojtech Pavlik wrote: > Oops? I thought the paired controller there is for OSes not being able > to handle EHCI yet? So that USB works even for those ... I think EHCI > should handle even 1.x devices ... I may be wrong, though. Check the Intel EHCI spec. Esp. the chapter about port handover...

Re: test11-pre6 still very broken

2000-11-21 Thread Vojtech Pavlik
On Mon, Nov 20, 2000 at 01:37:23PM +0100, Thomas Sailer wrote: > > I hope EHCI makes it all moot. Some way or another. > > Only for USB2 devices. EHCI is supposed to be paired with an existing > UHCI or OHCI controller core that is supposed to take over the USB connector > if an USB 1.x hub or d

Re: [PATCH] semaphore fairness patch against test11-pre6

2000-11-20 Thread Andrew Morton
Linus Torvalds wrote: > > ... > > I'll think about this some more. One thing I noticed is that the > "wake_up(&sem->wait);" at the end of __down() is kind of bogus: we don't > actually want to wake anybody up at that point at all, it's just that if > we don't wake anybody up we'll end up having

Re: test11-pre6 still very broken

2000-11-20 Thread Thomas Sailer
Linus Torvalds wrote: > I'd disagree. UHCI has tons of advantages, not the least of which is > [Cthat it was there first and is widely available. If OHCI hadn't been > done we'd have _one_ nice good USB controller implementation instead of UHCI has a couple of disadvantages, though (and some o

RE: videodev.c won't compile in test11-pre6/pre7/final

2000-11-19 Thread Frank Davis
Hello, The undeclared variables are defined in include/linux/videodev.h , which is included in videodev.c . ... #define VID_TYPE_SUBCAPTURE 512 #define VID_TYPE_MPEG_DECODER 1024 #define VID_TYPE_MPEG_ENCODER 2048 #define VID_TYPE_MJPEG_DECODER 4096 #define VID_TYPE_MJPEG_ENCODER 8192 ... Reg

videodev.c won't compile in test11-pre6/pre7/final

2000-11-19 Thread Ari Pollak
I was going to report this back in pre6, but I thought someone had caught it already.. When the bttv driver is enbabled as a module in test11, make modules fails with: videodev.c: In function `videodev_proc_read': videodev.c:283: `VID_TYPE_MPEG_DECODER' undeclared (first use in this function) vid

2.4.0-test11-pre6 Destroyed vfat filesystem

2000-11-19 Thread John McCutchan
Hello, After I mounted my windows partition under 2.4.0-test11pre6 the file system was corrupted. John - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.o

Re: test11-pre6 still very broken

2000-11-19 Thread Pavel Machek
Hi! > >One note for the archives, if you are presented a choice between a OHCI > >or a UHCI controller, go for the OHCI. It has a "cleaner" interface, > >handles more of the logic in the silicon, and due to this provides > >faster transfers. > > I'd disagree. UHCI has tons of advantages, not t

Re: [PATCH] semaphore fairness patch against test11-pre6

2000-11-19 Thread Linus Torvalds
On Sun, 19 Nov 2000, Andrew Morton wrote: > > I don't see a path where David's patch can cause a lost wakeup in the > way you describe. Basically, if there are two up() calls, they might end up waking up only one process, because the same process goes to sleep twice. That's wrong. It should wa

Re: [PATCH] semaphore fairness patch against test11-pre6

2000-11-19 Thread Andrew Morton
Linus Torvalds wrote: > > ... > But the algorithm itself should allow for other values. In fact, I think > that you'll find that it works fine if you switch to non-exclusive > wait-queues, and the only reason you see the repeatable D states is > exactly the case where we didn't "take" the semapho

Re: [PATCH] semaphore fairness patch against test11-pre6

2000-11-18 Thread Linus Torvalds
On Sun, 19 Nov 2000, Andrew Morton wrote: > > Has anyone tried it on SMP? I get fairly repeatable instances of immortal > `D'-state processes with this patch. Too bad. I really thought it should be safe to do. > The patch isn't right - it allows `sleepers' to increase without bound. > But it

Re: [PATCH] semaphore fairness patch against test11-pre6

2000-11-18 Thread Andrew Morton
Christoph Rohland wrote: > > Hi David, > > David Mansfield <[EMAIL PROTECTED]> writes: > > If you can find the time to check this out more completely, I recommend > > it, because it seems like a great improvement to be able to accurately > > see vmstat numbers in times of system load. I hope th

Re: test11-pre6 still very broken

2000-11-18 Thread Linus Torvalds
In article <[EMAIL PROTECTED]>, Greg KH <[EMAIL PROTECTED]> wrote: >On Fri, Nov 17, 2000 at 11:25:50PM -0800, Ben Ford wrote: >> Here is lspci output from the laptop in question. Is this not UHCI? > >Yes it is. Just a bit funny if you think about it, but with Intel and >Via putting the UHCI cor

[PATCH] linux/time.h name space pollution in 2.4.0-test11-pre6/pre7

2000-11-18 Thread Werner Almesberger
Hi Linus, include/linux/time.h leaks out mktime, creating a possible conflict with POSIX mktime. This patch puts mktime and a few helper functions into #ifdef __KERNEL__ Originally for 2.4.0-test11-pre6, but applies also to 2.4.0-test11-pre7 Cheers, Werner

Re: [PATCH] semaphore fairness patch against test11-pre6

2000-11-18 Thread Christoph Rohland
Hi David, David Mansfield <[EMAIL PROTECTED]> writes: > If you can find the time to check this out more completely, I recommend > it, because it seems like a great improvement to be able to accurately > see vmstat numbers in times of system load. I hope the other side > effects are beneficial as

Re: test11-pre6 still very broken

2000-11-17 Thread Greg KH
On Fri, Nov 17, 2000 at 11:25:50PM -0800, Ben Ford wrote: > Here is lspci output from the laptop in question. Is this not UHCI? Yes it is. Just a bit funny if you think about it, but with Intel and Via putting the UHCI core into their chipsets I guess it makes sense. One note for the archives,

Re: test11-pre6 still very broken

2000-11-17 Thread Ben Ford
Here is lspci output from the laptop in question. Is this not UHCI? [ben@Juanita ben]$ /sbin/lspci 00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03) 00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03) 00:07.0 ISA bridge: Intel Corporati

Re: test11-pre6 still very broken

2000-11-17 Thread Jeff Garzik
Greg KH wrote: > > On Fri, Nov 17, 2000 at 09:27:19PM -0800, David Ford wrote: > > > > The second issue is usb. I now have two machines that lockup on boot in USB. > > One is the above workstation, the second is a Compaq laptop. Unfortunately > > I have no way of unplugging the USB hardware ins

Re: test11-pre6 still very broken

2000-11-17 Thread Greg KH
On Fri, Nov 17, 2000 at 09:27:19PM -0800, David Ford wrote: > > The second issue is usb. I now have two machines that lockup on boot in USB. > One is the above workstation, the second is a Compaq laptop. Unfortunately > I have no way of unplugging the USB hardware inside the laptop :P Can't yo

Re: test11-pre6 still very broken

2000-11-17 Thread David Ford
> > The mysterious lockups in test11-pre5 continue in test11-pre6. It is very > > difficult because the lockups appear to be kdb-specific (and kdb itself [...] > It could be that -test5 and -test6 break some assumption kdb makes. > It has been eminently stable here.

Re: test11-pre6 still very broken

2000-11-17 Thread Keith Owens
On Fri, 17 Nov 2000 20:00:49 + (GMT), Tigran Aivazian <[EMAIL PROTECTED]> wrote: >The mysterious lockups in test11-pre5 continue in test11-pre6. It is very >difficult because the lockups appear to be kdb-specific (and kdb itself >goes mad) but when there is no kdb there is ver

[PATCH] semaphore fairness patch against test11-pre6

2000-11-17 Thread David Mansfield
Hi Linus et al, I've applied your semaphore fairness patch (slightly fixed) below. It fixes my original bug report of vmstat, ps etc. stalls waiting for the mmap_sem. I can now run my memory 'hog' processes and actually see vmstat update every second even under heavy memory pressure. More impo

Re: test11-pre6 still very broken

2000-11-17 Thread Keith Owens
On Fri, 17 Nov 2000 20:00:49 + (GMT), Tigran Aivazian <[EMAIL PROTECTED]> wrote: >The mysterious lockups in test11-pre5 continue in test11-pre6. It is very >difficult because the lockups appear to be kdb-specific (and kdb itself >goes mad) but when there is no kdb there is ver

Re: test11-pre6 still very broken

2000-11-17 Thread H. Peter Anvin
Followup to: <[EMAIL PROTECTED]> By author:Tigran Aivazian <[EMAIL PROTECTED]> In newsgroup: linux.dev.kernel > > Hi, > > The mysterious lockups in test11-pre5 continue in test11-pre6. It is very > difficult because the lockups appear to be kdb-specific (and kdb

test11-pre6 still very broken

2000-11-17 Thread Tigran Aivazian
Hi, The mysterious lockups in test11-pre5 continue in test11-pre6. It is very difficult because the lockups appear to be kdb-specific (and kdb itself goes mad) but when there is no kdb there is very little useful information one can extract from a dead system... I will start removing kernel

linux-2.4.0-test11-pre6 fails to compile

2000-11-17 Thread Dan Podeanu
Hello everybody, When attempting to compile test11-pre6 it crashes out with: gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686 -DNTFS_IN_LINUX_KERNEL -DNTFS_VERSION=\"000607\" -c -o inode.o inode

Re: test11-pre6

2000-11-17 Thread Mike A. Harris
On Fri, 17 Nov 2000, Erik Andersen wrote: >> > - Rik Faith: DRM update to make it easier to sync up 2.2.x >> > - David Woodhouse: make old 16-bit pcmcia controllers work >> > again (ie i82365 and TCIC) >> Level I >> >> The list is getting shorter. > >WTF is "Level I" supposed to

Re: test11-pre6

2000-11-17 Thread Jeff Garzik
Chris Wedgwood wrote: > There are 'hotplug' additions -- these now mean the networking code > won't build without "CONFIG_HOTPLUG=y". > > What is the correct fix here; fix the networking code or just take > this option out and ensure hotplug functionality is no longer > compile-time dependent (al

[patch] hotplug fixes Re: test11-pre6

2000-11-17 Thread Tigran Aivazian
On Thu, 16 Nov 2000, Linus Torvalds wrote: > > The log-file says it all.. > > Linus No, I am sorry but it does not mention hotplug things in net/core/dev.c and they are broken. The fix below. Regards, Tigran diff -urN -X dontdiff linux/init/main.c work/init/main.c --- linux/ini

Correction.PATCH: 2.4.0-test11-pre6 NTFS: new_inode namespace clash fix

2000-11-17 Thread Anton Altaparmakov
WWW: http://www-stu.christs.cam.ac.uk/~aia21/ United Kingdom ICQ: 8561279 diff -ur linux-2.4.0-test11-pre6/fs/ntfs/inode.c linux/fs/ntfs/inode.c --- linux-2.4.0-test11-pre6/fs/ntfs/inode.c Wed Jun 21 18:10:02 2000 +++ linux/fs/ntfs/inode.c Fri Nov 17 11:08:32 2000 @@ -1

Re: test11-pre6

2000-11-17 Thread David Woodhouse
Missing up_and_exit() which is required for killing kernel threads on cleanup_module(). This patch also fixes JFFS and USB hub.c to use it. Index: include/linux/kernel.h === RCS file: /inst/cvs/linux/include/linux/kernel.h,v ret

Re: 2.4.0-test11-pre6 ntfs compile error

2000-11-17 Thread Anton Altaparmakov
At 10:23 17/11/2000, Anton Altaparmakov wrote: >At 05:38 17/11/2000, Alexander Viro wrote: >>On Fri, 17 Nov 2000, Frank Davis wrote: >> > Hello, >> > I just try to compile 2.4.0-test11-pre6, and received the following >> error (make modules): >> &g

Re: 2.4.0-test11-pre6 ntfs compile error

2000-11-17 Thread Anton Altaparmakov
At 05:38 17/11/2000, Alexander Viro wrote: >On Fri, 17 Nov 2000, Frank Davis wrote: > > Hello, > > I just try to compile 2.4.0-test11-pre6, and received the following > error (make modules): > > > > inode.c:1054 conflicting types for 'new_inode' >

PATCH: 2.4.0-test11-pre6 NTFS: new_inode namespace clash fix

2000-11-17 Thread Anton Altaparmakov
7;s College eMail: [EMAIL PROTECTED] Cambridge CB2 3BU WWW: http://www-stu.christs.cam.ac.uk/~aia21/ United Kingdom ICQ: 8561279 diff -ur linux-2.4.0-test11-pre6/fs/ntfs/fs.c linux/fs/ntfs/fs.c --- linux-2.4.0-test11-pre6/fs/ntfs/fs.cFri Nov 17 11:05:11 2000

Re: test11-pre6

2000-11-16 Thread Jeff V. Merkey
On Fri, Nov 17, 2000 at 12:30:46AM -0700, Erik Andersen wrote: > On Thu Nov 16, 2000 at 08:45:10PM -0700, Jeff V. Merkey wrote: > > > > > > - pre6: > > > - Intel: start to add Pentium IV specific stuff (128-byte cacheline > > > etc) > > > - David Miller: search-and-destroy places t

Re: test11-pre6

2000-11-16 Thread David Lang
Andersen <[EMAIL PROTECTED]> > To: Jeff V. Merkey <[EMAIL PROTECTED]> > Cc: Kernel Mailing List <[EMAIL PROTECTED]> > Subject: Re: test11-pre6 > > On Thu Nov 16, 2000 at 08:45:10PM -0700, Jeff V. Merkey wrote: > > > > > > - pre6: > >

2.4.0-test11-pre6 dev.c compile error

2000-11-16 Thread Jarosław Bekas
Hello I try to compile 2.4.0-test11-pre6, and recive error: gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686-c -o dev.o dev.c dev.c: In function `run_sbin_hotplug': dev.c:2736: `hotplug_path'

Re: test11-pre6

2000-11-16 Thread Erik Andersen
On Thu Nov 16, 2000 at 08:45:10PM -0700, Jeff V. Merkey wrote: > > > > - pre6: > > - Intel: start to add Pentium IV specific stuff (128-byte cacheline > > etc) > > - David Miller: search-and-destroy places that forget to mark us > > running after removing us from a wait-queue

Re: 2.4.0-test11-pre6 ntfs compile error

2000-11-16 Thread Alexander Viro
On Fri, 17 Nov 2000, Frank Davis wrote: > Hello, > I just try to compile 2.4.0-test11-pre6, and received the following error (make >modules): > > inode.c:1054 conflicting types for 'new_inode' > /usr/src/liunux/include/linux/fs.h:1153 previous declaration of

Re: 2.4.0-test11-pre6 fails compile (dev.c)

2000-11-16 Thread Jeff Garzik
Neil Brown wrote: > > On Thursday November 16, [EMAIL PROTECTED] wrote: > > FYI: > > > > gcc -D__KERNEL__ -I/usr/src/linux-2.4.0-test11/include -Wall -Wstrict-prototypes >-O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 >-march=i686-c -o dev.o dev.c > > dev.c

2.4.0-test11-pre6 ntfs compile error

2000-11-16 Thread Frank Davis
Hello, I just try to compile 2.4.0-test11-pre6, and received the following error (make modules): inode.c:1054 conflicting types for 'new_inode' /usr/src/liunux/include/linux/fs.h:1153 previous declaration of 'new_inode' make[2]: ***[inode.o]Error 1 make[2]: Leaving direct

Re: test11-pre6

2000-11-16 Thread David S. Miller
From: "Ying Chen/Almaden/IBM" <[EMAIL PROTECTED]> Date:Thu, 16 Nov 2000 19:02:25 -0800 You forgot about wakeup_bdflush(1) stuff. What are you talking about, did you even check the patch? Your changes are already in there. Later, David S. Miller [EMAIL PROTECTED] - To unsubscri

Re: 2.4.0-test11-pre6 fails compile (dev.c)

2000-11-16 Thread Neil Brown
On Thursday November 16, [EMAIL PROTECTED] wrote: > FYI: > > gcc -D__KERNEL__ -I/usr/src/linux-2.4.0-test11/include -Wall -Wstrict-prototypes -O2 >-fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 >-march=i686-c -o dev.o dev.c > dev.c: In function `run_sbin_hotplu

Re: test11-pre6

2000-11-16 Thread Ying Chen/Almaden/IBM
Linus, You forgot about wakeup_bdflush(1) stuff. Here is the patch again (against test10). === There are several places where schedule() is called after wakeup_bdflush(1) is called. This is completely unnecessary, since wakeup_bdflush(

2.4.0-test11-pre6 fails compile (dev.c)

2000-11-16 Thread Pete Clements
FYI: gcc -D__KERNEL__ -I/usr/src/linux-2.4.0-test11/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=i686-c -o dev.o dev.c dev.c: In function `run_sbin_hotplug': dev.c:2736: `hotplug_path' undeclared (first use in this

Re: test11-pre6

2000-11-16 Thread Jeff V. Merkey
On Thu, Nov 16, 2000 at 06:33:11PM -0800, Linus Torvalds wrote: > > The log-file says it all.. > > Linus > > - > > - pre6: > - Intel: start to add Pentium IV specific stuff (128-byte cacheline > etc) > - David Miller: search-and-destroy places that forget to ma

test11-pre6

2000-11-16 Thread Linus Torvalds
The log-file says it all.. Linus - - pre6: - Intel: start to add Pentium IV specific stuff (128-byte cacheline etc) - David Miller: search-and-destroy places that forget to mark us running after removing us from a wait-queue. - me: NFS client write-