Re: linux-2.4.0-test10 and X4.0.1 don't like each other on Libretto110CT

2000-11-07 Thread Miles Lane
You must upgrade to the latest release: 4.0.1e The fix for this problem went into 4.0.1d, but since you need to upgrade, you might as well get the latest code. Miles On Wed, 8 Nov 2000, David Luyer wrote: > > I'm having problems with X 4.0.1 and 2.4.0-test kernels on a Toshiba

linux-2.4.0-test10 and X4.0.1 don't like each other on Libretto 110CT

2000-11-07 Thread David Luyer
I'm having problems with X 4.0.1 and 2.4.0-test kernels on a Toshiba Libretto 110CT. Is this likely to be related to a known problem or can someone recommend some random intermediate kernel versions to try (binary elimination avoiding known-bad kernel versions...)? H/w: Toshiba Libretto 110CT

Re: Linux-2.4.0-test10

2000-11-07 Thread Zephaniah E. Hull
On Tue, Nov 07, 2000 at 11:22:37AM +0100, Ragnar Hojland Espinosa wrote: > > You have a voodoo3 or voodoo5 with X4, and the DRI X4 module loaded. > > > > Or am I wrong? > > v3.. bingo :) Comment out the 'Load "dri"' line from /etc/X11/XF86Config-4, I'm working on debugging the problems.

Re: Linux-2.4.0-test10

2000-11-07 Thread Ragnar Hojland Espinosa
On Fri, Nov 03, 2000 at 01:25:10AM -0500, [EMAIL PROTECTED] wrote: > > Just happened with test10, same circumstances .. font map got corrupted, and > > noise on the screen. Switching back and forth from X to a vc fixed it, tho. > > > > Sort of amusing that it (apparently) only happens with ppp

Re: Linux-2.4.0-test10

2000-11-07 Thread Ragnar Hojland Espinosa
On Fri, Nov 03, 2000 at 01:25:10AM -0500, [EMAIL PROTECTED] wrote: Just happened with test10, same circumstances .. font map got corrupted, and noise on the screen. Switching back and forth from X to a vc fixed it, tho. Sort of amusing that it (apparently) only happens with ppp + wget

Re: Linux-2.4.0-test10

2000-11-07 Thread Zephaniah E. Hull
On Tue, Nov 07, 2000 at 11:22:37AM +0100, Ragnar Hojland Espinosa wrote: snip You have a voodoo3 or voodoo5 with X4, and the DRI X4 module loaded. Or am I wrong? v3.. bingo :) Comment out the 'Load "dri"' line from /etc/X11/XF86Config-4, I'm working on debugging the problems.

linux-2.4.0-test10 and X4.0.1 don't like each other on Libretto 110CT

2000-11-07 Thread David Luyer
I'm having problems with X 4.0.1 and 2.4.0-test kernels on a Toshiba Libretto 110CT. Is this likely to be related to a known problem or can someone recommend some random intermediate kernel versions to try (binary elimination avoiding known-bad kernel versions...)? H/w: Toshiba Libretto 110CT

Re: linux-2.4.0-test10 and X4.0.1 don't like each other on Libretto110CT

2000-11-07 Thread Miles Lane
You must upgrade to the latest release: 4.0.1e The fix for this problem went into 4.0.1d, but since you need to upgrade, you might as well get the latest code. Miles On Wed, 8 Nov 2000, David Luyer wrote: I'm having problems with X 4.0.1 and 2.4.0-test kernels on a Toshiba

Re: Linux-2.4.0-test10

2000-11-04 Thread H. Peter Anvin
Followup to: <[EMAIL PROTECTED]> By author:"Marco d'Itri" <[EMAIL PROTECTED]> In newsgroup: linux.dev.kernel > > On Nov 02, "Stephen C. Tweedie" <[EMAIL PROTECTED]> wrote: > > >2.2 O_SYNC is actually broken too --- it doesn't sync all metadata (in > >particular, it doesn't update the

Re: Linux-2.4.0-test10

2000-11-04 Thread H. Peter Anvin
Followup to: [EMAIL PROTECTED] By author:"Marco d'Itri" [EMAIL PROTECTED] In newsgroup: linux.dev.kernel On Nov 02, "Stephen C. Tweedie" [EMAIL PROTECTED] wrote: 2.2 O_SYNC is actually broken too --- it doesn't sync all metadata (in particular, it doesn't update the inode), but I'd

Re: Linux-2.4.0-test10

2000-11-03 Thread Ben Ford
I have this problem also. I am running vesafb and X4.01 w/ a voodoo3500. Switching to a vc sometimes gives you black text (hiliting w/ mouse fixes it) and alternating green and red pixels across the top of the screen. -b [EMAIL PROTECTED] wrote: > On Thu, Nov 02, 2000 at 07:38:56PM +0100,

Re: Linux-2.4.0-test10

2000-11-03 Thread Ben Ford
I have this problem also. I am running vesafb and X4.01 w/ a voodoo3500. Switching to a vc sometimes gives you black text (hiliting w/ mouse fixes it) and alternating green and red pixels across the top of the screen. -b [EMAIL PROTECTED] wrote: On Thu, Nov 02, 2000 at 07:38:56PM +0100,

Re: Linux-2.4.0-test10

2000-11-02 Thread kernel
On Thu, Nov 02, 2000 at 07:38:56PM +0100, Ragnar Hojland Espinosa wrote: > On Thu, Nov 02, 2000 at 06:57:06PM +0100, Ragnar Hojland Espinosa wrote: > > Well, here never did until today :) With test9, I had left the box idle > > Just happened with test10, same circumstances .. font map got

RE: Linux-2.4.0-test10

2000-11-02 Thread James Simmons
> I have a similar hardware list and I don't observe any of these problems on > 2.4.0-test10x. Is it possibly a hardware conflict somewhere? > > What I do see occasionally is if X was ever heavy on the memory usage (say > I've run GIMP for a couple of hours) then the text console's font set

RE: Linux-2.4.0-test10

2000-11-02 Thread CRADOCK, Christopher
that way. Chris. > -Original Message- > From: M.H.VanLeeuwen [SMTP:[EMAIL PROTECTED]] > Sent: Thursday, November 02, 2000 12:44 AM > To: CRADOCK, Christopher > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: Linux-2.4.0-test10 > > "CRADOCK, C

Re: Linux-2.4.0-test10

2000-11-02 Thread Ragnar Hojland Espinosa
On Thu, Nov 02, 2000 at 06:57:06PM +0100, Ragnar Hojland Espinosa wrote: > Well, here never did until today :) With test9, I had left the box idle Just happened with test10, same circumstances .. font map got corrupted, and noise on the screen. Switching back and forth from X to a vc fixed

Re: Linux-2.4.0-test10

2000-11-02 Thread Ragnar Hojland Espinosa
On Wed, Nov 01, 2000 at 06:44:25PM -0600, M.H.VanLeeuwen wrote: > "CRADOCK, Christopher" wrote: > > I have a similar hardware list and I don't observe any of these problems on > > 2.4.0-test10x. Is it possibly a hardware conflict somewhere? > > > > What I do see occasionally is if X was ever

Re: Linux-2.4.0-test10

2000-11-02 Thread Ragnar Hojland Espinosa
On Wed, Nov 01, 2000 at 06:44:25PM -0600, M.H.VanLeeuwen wrote: "CRADOCK, Christopher" wrote: I have a similar hardware list and I don't observe any of these problems on 2.4.0-test10x. Is it possibly a hardware conflict somewhere? What I do see occasionally is if X was ever heavy on the

Re: Linux-2.4.0-test10

2000-11-02 Thread Ragnar Hojland Espinosa
On Thu, Nov 02, 2000 at 06:57:06PM +0100, Ragnar Hojland Espinosa wrote: Well, here never did until today :) With test9, I had left the box idle Just happened with test10, same circumstances .. font map got corrupted, and noise on the screen. Switching back and forth from X to a vc fixed it,

RE: Linux-2.4.0-test10

2000-11-02 Thread CRADOCK, Christopher
that way. Chris. -Original Message- From: M.H.VanLeeuwen [SMTP:[EMAIL PROTECTED]] Sent: Thursday, November 02, 2000 12:44 AM To: CRADOCK, Christopher Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Linux-2.4.0-test10 "CRADOCK, Christopher" wrote: I have

RE: Linux-2.4.0-test10

2000-11-02 Thread James Simmons
I have a similar hardware list and I don't observe any of these problems on 2.4.0-test10x. Is it possibly a hardware conflict somewhere? What I do see occasionally is if X was ever heavy on the memory usage (say I've run GIMP for a couple of hours) then the text console's font set gets

Re: Linux-2.4.0-test10

2000-11-02 Thread kernel
On Thu, Nov 02, 2000 at 07:38:56PM +0100, Ragnar Hojland Espinosa wrote: On Thu, Nov 02, 2000 at 06:57:06PM +0100, Ragnar Hojland Espinosa wrote: Well, here never did until today :) With test9, I had left the box idle Just happened with test10, same circumstances .. font map got

Re: Linux-2.4.0-test10

2000-11-01 Thread Vitezslav Samel
Hi! > My list of 2.4.0-testX problems > > Problem description: > > 1. kernel compiled w/o FB support. When attempting to switch > back to X from VC1-6 system locks hard for SMP. Nada thing > fixes this except hard reset... no Alt-SysRq-B, nothing > DRI not enabled.

Re: Linux-2.4.0-test10

2000-11-01 Thread David Ford
Yes..long standing bug, and I don't have sufficient time to get my feet wet in the IDE dept and fix it. -d "M.H.VanLeeuwen" wrote: > > Disable PIIXn tuning and recompile your kernel. How does it fare now? > > Yep, disabling (opposite of "enabling") does allow the kernel to boot just fine. >

Re: Linux-2.4.0-test10

2000-11-01 Thread Jeff Garzik
Andi Kleen wrote: > On Tue, Oct 31, 2000 at 08:55:13PM +, Alan Cox wrote: > > What about the fact anyone can crash a box using ioctls on net > > devices and waiting for an unload - was this fixed ? > The ioctls of network devices are generally unsafe on SMP, because > they run

Re: Linux-2.4.0-test10

2000-11-01 Thread M.H.VanLeeuwen
"CRADOCK, Christopher" wrote: > > I have a similar hardware list and I don't observe any of these problems on > 2.4.0-test10x. Is it possibly a hardware conflict somewhere? > > What I do see occasionally is if X was ever heavy on the memory usage (say > I've run GIMP for a couple of hours) then

Re: Linux-2.4.0-test10

2000-11-01 Thread M.H.VanLeeuwen
David Ford wrote: > > "M.H.VanLeeuwen" wrote: > > > 3. Enabling PIIX4, kernel locks hard when printing the partition > >tables for hdc. hdc has no partitions. > >I think this problem is on Ted's problem list??? > > Disable PIIXn tuning and recompile your kernel. How does it fare

Re: Linux-2.4.0-test10

2000-11-01 Thread David Ford
"M.H.VanLeeuwen" wrote: > 3. Enabling PIIX4, kernel locks hard when printing the partition >tables for hdc. hdc has no partitions. >I think this problem is on Ted's problem list??? Disable PIIXn tuning and recompile your kernel. How does it fare now? -d -- "The difference between

Re: [linux-usb-devel] Patch: linux-2.4.0-test10-pre7/drivers/usb/usb.c driver matching bug

2000-11-01 Thread Greg KH
On Wed, Nov 01, 2000 at 09:35:18AM -0800, David Brownell wrote: > With the USB driver updates I've already seen, it looks like an > upcoming 2.4 kernel may no longer need those driver scripts; not > sure about the 2.2 backports though. I think one of the "rules" is that the 2.2.x kernel

Re: [linux-usb-devel] Patch: linux-2.4.0-test10-pre7/drivers/usb/usb.cdriver matching bug

2000-11-01 Thread David Brownell
> linux-2.4.0-test10-pre7/drivers/usb/usb.c introduced a really > cool feature, where USB drivers can declare a data structure that > describes the various ID bytes of the USB devices that they are > relevant to. It's the same tool architecture used with PCI: modules.pci

Re: Linux-2.4.0-test10

2000-11-01 Thread kuznet
Hello! > On Tue, Oct 31, 2000 at 08:55:13PM +, Alan Cox wrote: > > What about the fact anyone can crash a box using ioctls on net > > devices and waiting for an unload - was this fixed ? What do you mean? If I understood you correclty, this has been fixed in early 2.3 and never

RE: Linux-2.4.0-test10

2000-11-01 Thread CRADOCK, Christopher
until the next reboot. Console driver failing to reset something? Chris Cradock > -Original Message- > From: M.H.VanLeeuwen [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, November 01, 2000 6:03 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re:

Re: Linux-2.4.0-test10

2000-11-01 Thread Tigran Aivazian
On Wed, 1 Nov 2000, Alan Cox wrote: > > for microcode update as family=6? The manuals suggest that test for ">" is > > correct, i.e. that Intel will maintain compatibility with P6 wrt microcode > > update. > > > > Perhaps Richard can clarify this? > > Until we know what the preventium IV does

Re: Linux-2.4.0-test10

2000-11-01 Thread Alan Cox
> for microcode update as family=6? The manuals suggest that test for ">" is > correct, i.e. that Intel will maintain compatibility with P6 wrt microcode > update. > > Perhaps Richard can clarify this? Until we know what the preventium IV does on microcode behaviour it seems wisest to test for

Re: Linux-2.4.0-test10

2000-11-01 Thread Mikael Pettersson
On Wed, 1 Nov 2000, Tigran Aivazian wrote: >But it contains an erroneous part in microcode.c: > >- if (c->x86_vendor != X86_VENDOR_INTEL || c->x86 < 6){ >+ if (c->x86_vendor != X86_VENDOR_INTEL || c->x86 != 6){ >printk(KERN_ERR "microcode: CPU%d not an Intel P6\n",

Re: Linux-2.4.0-test10

2000-11-01 Thread Tigran Aivazian
On Tue, 31 Oct 2000, Linus Torvalds wrote: > > Ok, test10-final is out there now. This has no _known_ bugs that I > consider show-stoppers, for what it's worth. Linus, But it contains an erroneous part in microcode.c: - if (c->x86_vendor != X86_VENDOR_INTEL || c->x86 < 6){ + if

Re: Linux-2.4.0-test10

2000-11-01 Thread Andi Kleen
On Tue, Oct 31, 2000 at 08:55:13PM +, Alan Cox wrote: > What about the fact anyone can crash a box using ioctls on net > devices and waiting for an unload - was this fixed ? The ioctls of network devices are generally unsafe on SMP, because they run with kernel lock dropped now

Re: Linux-2.4.0-test10

2000-11-01 Thread Andi Kleen
On Tue, Oct 31, 2000 at 08:55:13PM +, Alan Cox wrote: What about the fact anyone can crash a box using ioctls on net devices and waiting for an unload - was this fixed ? The ioctls of network devices are generally unsafe on SMP, because they run with kernel lock dropped now but

Re: Linux-2.4.0-test10

2000-11-01 Thread Tigran Aivazian
On Tue, 31 Oct 2000, Linus Torvalds wrote: Ok, test10-final is out there now. This has no _known_ bugs that I consider show-stoppers, for what it's worth. Linus, But it contains an erroneous part in microcode.c: - if (c-x86_vendor != X86_VENDOR_INTEL || c-x86 6){ + if

Re: Linux-2.4.0-test10

2000-11-01 Thread Mikael Pettersson
On Wed, 1 Nov 2000, Tigran Aivazian wrote: But it contains an erroneous part in microcode.c: - if (c-x86_vendor != X86_VENDOR_INTEL || c-x86 6){ + if (c-x86_vendor != X86_VENDOR_INTEL || c-x86 != 6){ printk(KERN_ERR "microcode: CPU%d not an Intel P6\n", cpu_num);

Re: Linux-2.4.0-test10

2000-11-01 Thread Alan Cox
for microcode update as family=6? The manuals suggest that test for "" is correct, i.e. that Intel will maintain compatibility with P6 wrt microcode update. Perhaps Richard can clarify this? Until we know what the preventium IV does on microcode behaviour it seems wisest to test for == not

Re: Linux-2.4.0-test10

2000-11-01 Thread Tigran Aivazian
On Wed, 1 Nov 2000, Alan Cox wrote: for microcode update as family=6? The manuals suggest that test for "" is correct, i.e. that Intel will maintain compatibility with P6 wrt microcode update. Perhaps Richard can clarify this? Until we know what the preventium IV does on microcode

RE: Linux-2.4.0-test10

2000-11-01 Thread CRADOCK, Christopher
until the next reboot. Console driver failing to reset something? Chris Cradock -Original Message- From: M.H.VanLeeuwen [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, November 01, 2000 6:03 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Linux-2.4.0-test10 FYI

Re: Linux-2.4.0-test10

2000-11-01 Thread kuznet
Hello! On Tue, Oct 31, 2000 at 08:55:13PM +, Alan Cox wrote: What about the fact anyone can crash a box using ioctls on net devices and waiting for an unload - was this fixed ? What do you mean? If I understood you correclty, this has been fixed in early 2.3 and never

Re: [linux-usb-devel] Patch: linux-2.4.0-test10-pre7/drivers/usb/usb.cdriver matching bug

2000-11-01 Thread David Brownell
linux-2.4.0-test10-pre7/drivers/usb/usb.c introduced a really cool feature, where USB drivers can declare a data structure that describes the various ID bytes of the USB devices that they are relevant to. It's the same tool architecture used with PCI: modules.pcimap (and now

Re: [linux-usb-devel] Patch: linux-2.4.0-test10-pre7/drivers/usb/usb.c driver matching bug

2000-11-01 Thread Greg KH
On Wed, Nov 01, 2000 at 09:35:18AM -0800, David Brownell wrote: With the USB driver updates I've already seen, it looks like an upcoming 2.4 kernel may no longer need those driver scripts; not sure about the 2.2 backports though. I think one of the "rules" is that the 2.2.x kernel shouldn't

Re: Linux-2.4.0-test10

2000-11-01 Thread David Ford
"M.H.VanLeeuwen" wrote: 3. Enabling PIIX4, kernel locks hard when printing the partition tables for hdc. hdc has no partitions. I think this problem is on Ted's problem list??? Disable PIIXn tuning and recompile your kernel. How does it fare now? -d -- "The difference between

Re: Linux-2.4.0-test10

2000-11-01 Thread M.H.VanLeeuwen
David Ford wrote: "M.H.VanLeeuwen" wrote: 3. Enabling PIIX4, kernel locks hard when printing the partition tables for hdc. hdc has no partitions. I think this problem is on Ted's problem list??? Disable PIIXn tuning and recompile your kernel. How does it fare now? Yep,

Re: Linux-2.4.0-test10

2000-11-01 Thread M.H.VanLeeuwen
"CRADOCK, Christopher" wrote: I have a similar hardware list and I don't observe any of these problems on 2.4.0-test10x. Is it possibly a hardware conflict somewhere? What I do see occasionally is if X was ever heavy on the memory usage (say I've run GIMP for a couple of hours) then the

Re: Linux-2.4.0-test10

2000-11-01 Thread Jeff Garzik
Andi Kleen wrote: On Tue, Oct 31, 2000 at 08:55:13PM +, Alan Cox wrote: What about the fact anyone can crash a box using ioctls on net devices and waiting for an unload - was this fixed ? The ioctls of network devices are generally unsafe on SMP, because they run with

Re: Linux-2.4.0-test10

2000-11-01 Thread David Ford
Yes..long standing bug, and I don't have sufficient time to get my feet wet in the IDE dept and fix it. -d "M.H.VanLeeuwen" wrote: Disable PIIXn tuning and recompile your kernel. How does it fare now? Yep, disabling (opposite of "enabling") does allow the kernel to boot just fine. PIIXn

Re: Linux-2.4.0-test10

2000-11-01 Thread Vitezslav Samel
Hi! My list of 2.4.0-testX problems Problem description: 1. kernel compiled w/o FB support. When attempting to switch back to X from VC1-6 system locks hard for SMP. Nada thing fixes this except hard reset... no Alt-SysRq-B, nothing DRI not enabled. Video card

Re: Linux-2.4.0-test10

2000-10-31 Thread Linus Torvalds
On Tue, 31 Oct 2000, Miles Lane wrote: > > Were there no changes between test10-pre7 and test10? > I notice you didn't send out a Changelist. > > The Changelists help me focus my testing. Sorry. Here it is.. Linus - - final: - Jeff Garzik: ISA network driver

Re: Linux-2.4.0-test10

2000-10-31 Thread adrian
On Tue, 31 Oct 2000, Linus Torvalds wrote: [snip] > Naah, he mainly just does some browsing with netscape, and (don't tell a > soul) plays QuakeIII with the door locked. > > Linus Although he might find that 2.2.18pre18 gives better frame rates. :) 1024x768, Max detail,

Re: Linux-2.4.0-test10

2000-10-31 Thread Miles Lane
Linus, Were there no changes between test10-pre7 and test10? I notice you didn't send out a Changelist. The Changelists help me focus my testing. Thanks, Miles - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED]

Re: Linux-2.4.0-test10

2000-10-31 Thread M.H.VanLeeuwen
FYI, My list of 2.4.0-testX problems Further details, .config, etc...available if needed Martin 2.4.0-test10 and earlier problem list: Problem | UP UP-APIC SMP | 1 | OK OK

Re: Linux-2.4.0-test10

2000-10-31 Thread Jeremy Fitzhardinge
On Tue, Oct 31, 2000 at 08:55:13PM +, Alan Cox wrote: > Does autofs4 work yet Autofs4 was fixed in 2.4.0-test10-pre6 or so. Autofs4 for 2.2.x has been working for some time, though I just updated the 2.2 patch so it doesn't stomp on autofs (v3). J PGP signature

Patch: linux-2.4.0-test10-pre7/drivers/usb/usb.c driver matching bug

2000-10-31 Thread Adam J. Richter
linux-2.4.0-test10-pre7/drivers/usb/usb.c introduced a really cool feature, where USB drivers can declare a data structure that describes the various ID bytes of the USB devices that they are relevant to. Updated versions of depmod and hotplug are then used so that the appropriate USB

Re: Linux-2.4.0-test10

2000-10-31 Thread Tom Rini
On Tue, Oct 31, 2000 at 12:41:55PM -0800, Linus Torvalds wrote: > Ok, test10-final is out there now. This has no _known_ bugs that I > consider show-stoppers, for what it's worth. Sure, it's not a critical bug or anything but hey. One more time: This is a very minor patch for

Re: Linux-2.4.0-test10

2000-10-31 Thread Paul Jakma
On Tue, 31 Oct 2000, Alan Cox wrote: > Less Critical: > Does autofs4 work yet has been apparently working fine for me for a while on 2.4test and 2.2+patch. (while==not noticed any major problems in last couple of months) > Alan regards, -- Paul Jakma [EMAIL PROTECTED] PGP5 key:

Re: Linux-2.4.0-test10

2000-10-31 Thread Linus Torvalds
On Tue, 31 Oct 2000, Rik van Riel wrote: > On Tue, 31 Oct 2000, Linus Torvalds wrote: > > > > Ok, test10-final is out there now. This has no _known_ bugs that > > I consider show-stoppers, for what it's worth. > > > > And when I don't know of a bug, it doesn't exist. Let us > > rejoice. In

Re: Linux-2.4.0-test10

2000-10-31 Thread Alan Cox
> Ok, test10-final is out there now. This has no _known_ bugs that I > consider show-stoppers, for what it's worth. The fact power management even handling is completely broken and crashes on unfortunately timed module unloads doesnt count ? More importantly has the bug when you can use the

Re: Linux-2.4.0-test10

2000-10-31 Thread Rik van Riel
On Tue, 31 Oct 2000, Linus Torvalds wrote: > Ok, test10-final is out there now. This has no _known_ bugs that > I consider show-stoppers, for what it's worth. > > And when I don't know of a bug, it doesn't exist. Let us > rejoice. In traditional kernel naming tradition, this kernel > hereby

Linux-2.4.0-test10

2000-10-31 Thread Linus Torvalds
Ok, test10-final is out there now. This has no _known_ bugs that I consider show-stoppers, for what it's worth. And when I don't know of a bug, it doesn't exist. Let us rejoice. In traditional kernel naming tradition, this kernel hereby gets anointed as one of the "greased weasel" kernel

Linux-2.4.0-test10

2000-10-31 Thread Linus Torvalds
Ok, test10-final is out there now. This has no _known_ bugs that I consider show-stoppers, for what it's worth. And when I don't know of a bug, it doesn't exist. Let us rejoice. In traditional kernel naming tradition, this kernel hereby gets anointed as one of the "greased weasel" kernel

Re: Linux-2.4.0-test10

2000-10-31 Thread Rik van Riel
On Tue, 31 Oct 2000, Linus Torvalds wrote: Ok, test10-final is out there now. This has no _known_ bugs that I consider show-stoppers, for what it's worth. And when I don't know of a bug, it doesn't exist. Let us rejoice. In traditional kernel naming tradition, this kernel hereby gets

Re: Linux-2.4.0-test10

2000-10-31 Thread Alan Cox
Ok, test10-final is out there now. This has no _known_ bugs that I consider show-stoppers, for what it's worth. The fact power management even handling is completely broken and crashes on unfortunately timed module unloads doesnt count ? More importantly has the bug when you can use the

Re: Linux-2.4.0-test10

2000-10-31 Thread Linus Torvalds
On Tue, 31 Oct 2000, Rik van Riel wrote: On Tue, 31 Oct 2000, Linus Torvalds wrote: Ok, test10-final is out there now. This has no _known_ bugs that I consider show-stoppers, for what it's worth. And when I don't know of a bug, it doesn't exist. Let us rejoice. In traditional

Re: Linux-2.4.0-test10

2000-10-31 Thread Paul Jakma
On Tue, 31 Oct 2000, Alan Cox wrote: Less Critical: Does autofs4 work yet has been apparently working fine for me for a while on 2.4test and 2.2+patch. (while==not noticed any major problems in last couple of months) Alan regards, -- Paul Jakma [EMAIL PROTECTED] PGP5 key:

Re: Linux-2.4.0-test10

2000-10-31 Thread Tom Rini
On Tue, Oct 31, 2000 at 12:41:55PM -0800, Linus Torvalds wrote: Ok, test10-final is out there now. This has no _known_ bugs that I consider show-stoppers, for what it's worth. Sure, it's not a critical bug or anything but hey. One more time: This is a very minor patch for fs/nls/Config.in,

Patch: linux-2.4.0-test10-pre7/drivers/usb/usb.c driver matching bug

2000-10-31 Thread Adam J. Richter
linux-2.4.0-test10-pre7/drivers/usb/usb.c introduced a really cool feature, where USB drivers can declare a data structure that describes the various ID bytes of the USB devices that they are relevant to. Updated versions of depmod and hotplug are then used so that the appropriate USB

Re: Linux-2.4.0-test10

2000-10-31 Thread Jeremy Fitzhardinge
On Tue, Oct 31, 2000 at 08:55:13PM +, Alan Cox wrote: Does autofs4 work yet Autofs4 was fixed in 2.4.0-test10-pre6 or so. Autofs4 for 2.2.x has been working for some time, though I just updated the 2.2 patch so it doesn't stomp on autofs (v3). J PGP signature

Re: Linux-2.4.0-test10

2000-10-31 Thread M.H.VanLeeuwen
FYI, My list of 2.4.0-testX problems Further details, .config, etc...available if needed Martin 2.4.0-test10 and earlier problem list: Problem | UP UP-APIC SMP | 1 | OK OK

Re: Linux-2.4.0-test10

2000-10-31 Thread Miles Lane
Linus, Were there no changes between test10-pre7 and test10? I notice you didn't send out a Changelist. The Changelists help me focus my testing. Thanks, Miles - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED]

Re: Linux-2.4.0-test10

2000-10-31 Thread adrian
On Tue, 31 Oct 2000, Linus Torvalds wrote: [snip] Naah, he mainly just does some browsing with netscape, and (don't tell a soul) plays QuakeIII with the door locked. Linus Although he might find that 2.2.18pre18 gives better frame rates. :) 1024x768, Max detail, 32bit,

Re: Linux-2.4.0-test10

2000-10-31 Thread Linus Torvalds
On Tue, 31 Oct 2000, Miles Lane wrote: Were there no changes between test10-pre7 and test10? I notice you didn't send out a Changelist. The Changelists help me focus my testing. Sorry. Here it is.. Linus - - final: - Jeff Garzik: ISA network driver cleanup,

Patch: modularizing partition parsing in linux-2.4.0-test10-pre6

2000-10-30 Thread Adam J. Richter
104 [EMAIL PROTECTED] \ / San Jose, California 95129-1034 +1 408 261-6630 | g g d r a s i l United States of America fax +1 408 261-6631 "Free Software For The Rest Of Us." --CUT HERE diff --new-file -u -

Patch: modularizing partition parsing in linux-2.4.0-test10-pre6

2000-10-30 Thread Adam J. Richter
104 [EMAIL PROTECTED] \ / San Jose, California 95129-1034 +1 408 261-6630 | g g d r a s i l United States of America fax +1 408 261-6631 "Free Software For The Rest Of Us." --CUT HERE diff --new-file -u -

linux-2.4.0-test10-pre6: Trigraphs in drivers/pci/devlist.h

2000-10-28 Thread Horst von Brand
I understand you are in charge of this per MAINTAINERS, it not, I apologize for bothering you. Red Hat 7, i686, gcc-20001027 (from CVS) complains about '??)' trigraphs at lines 1278 and 6367. Should that be just '(?)', or perhaps 'xx'? (egcs-1.1.2 keeps quiet). [Yes, trigraphs are bletcherous.

linux-2.4.0-test10-pre6: Trigraphs in drivers/pci/devlist.h

2000-10-28 Thread Horst von Brand
I understand you are in charge of this per MAINTAINERS, it not, I apologize for bothering you. Red Hat 7, i686, gcc-20001027 (from CVS) complains about '??)' trigraphs at lines 1278 and 6367. Should that be just '(?)', or perhaps 'xx'? (egcs-1.1.2 keeps quiet). [Yes, trigraphs are bletcherous.

Re: crash when booting linux-2.4.0-test10-pre5

2000-10-25 Thread Brian Gerst
Sebastian Benoit wrote: > > Hi, > > i have a PPro here with an AMI MegaRAID controller. > System is RedHat 7 + e2fsprogs-1.19, modutils-2.3.19, util-linux-2.10o > > 2.4.0-test10-pre5 is compiled with gcc 2.7.3.2 and and crashes > when running 'mount -o remount,rw /' during boot. > It also

Re: crash when booting linux-2.4.0-test10-pre5

2000-10-25 Thread Andrew Stubbs
ash when booting linux-2.4.0-test10-pre5 > > Hi, > > i have a PPro here with an AMI MegaRAID controller. > System is RedHat 7 + e2fsprogs-1.19, modutils-2.3.19, util-linux-2.10o > > 2.4.0-test10-pre5 is compiled with gcc 2.7.3.2 and and crashes > when running 'mount -o

crash when booting linux-2.4.0-test10-pre5

2000-10-25 Thread Sebastian Benoit
Hi, i have a PPro here with an AMI MegaRAID controller. System is RedHat 7 + e2fsprogs-1.19, modutils-2.3.19, util-linux-2.10o 2.4.0-test10-pre5 is compiled with gcc 2.7.3.2 and and crashes when running 'mount -o remount,rw /' during boot. It also complains that /proc isn't mounted (it is

crash when booting linux-2.4.0-test10-pre5

2000-10-25 Thread Sebastian Benoit
Hi, i have a PPro here with an AMI MegaRAID controller. System is RedHat 7 + e2fsprogs-1.19, modutils-2.3.19, util-linux-2.10o 2.4.0-test10-pre5 is compiled with gcc 2.7.3.2 and and crashes when running 'mount -o remount,rw /' during boot. It also complains that /proc isn't mounted (it is

Re: crash when booting linux-2.4.0-test10-pre5

2000-10-25 Thread Andrew Stubbs
PROTECTED] Sent: Wednesday, October 25, 2000 3:52 PM Subject: crash when booting linux-2.4.0-test10-pre5 Hi, i have a PPro here with an AMI MegaRAID controller. System is RedHat 7 + e2fsprogs-1.19, modutils-2.3.19, util-linux-2.10o 2.4.0-test10-pre5 is compiled with gcc 2.7.3.2 and and cra

Re: crash when booting linux-2.4.0-test10-pre5

2000-10-25 Thread Brian Gerst
Sebastian Benoit wrote: Hi, i have a PPro here with an AMI MegaRAID controller. System is RedHat 7 + e2fsprogs-1.19, modutils-2.3.19, util-linux-2.10o 2.4.0-test10-pre5 is compiled with gcc 2.7.3.2 and and crashes when running 'mount -o remount,rw /' during boot. It also complains

Re: aic7xxx problem on linux-2.4.0-test10-pre1

2000-10-12 Thread Jens Axboe
PROTECTED]> * SuSE Labs --- /opt/kernel/linux-2.4.0-test10-pre1/drivers/scsi/sr_ioctl.c Mon Sep 11 02:49:27 2000 +++ drivers/scsi/sr_ioctl.c Thu Oct 12 19:01:09 2000 @@ -341,7 +341,7 @@ sr_cmd[7] = ti->cdti_trk1; sr_cmd[8] = ti->cdti_ind1; -

Re: aic7xxx problem on linux-2.4.0-test10-pre1

2000-10-12 Thread Jens Axboe
--- /opt/kernel/linux-2.4.0-test10-pre1/drivers/scsi/sr_ioctl.c Mon Sep 11 02:49:27 2000 +++ drivers/scsi/sr_ioctl.c Thu Oct 12 19:01:09 2000 @@ -341,7 +341,7 @@ sr_cmd[7] = ti-cdti_trk1; sr_cmd[8] = ti-cdti_ind1; - result = sr_do_ioctl(target

aic7xxx problem on linux-2.4.0-test10-pre1

2000-10-11 Thread Young-Ho Cha
I have adaptec 20160 scsi adapter and plextor 32x cdrom. I played audio cd with gtcd(gnome app) and eject cdrom with gtcd(eject button) , gtcd died and dmesg out... -- kernel BUG at /usr/src/linux-2.4.0-test10/include/asm/pci.h:61! invalid operand: CPU:0 EIP:0010:[] EFLAGS

aic7xxx problem on linux-2.4.0-test10-pre1

2000-10-11 Thread Young-Ho Cha
I have adaptec 20160 scsi adapter and plextor 32x cdrom. I played audio cd with gtcd(gnome app) and eject cdrom with gtcd(eject button) , gtcd died and dmesg out... -- kernel BUG at /usr/src/linux-2.4.0-test10/include/asm/pci.h:61! invalid operand: CPU:0 EIP:0010:[d1f2e6a4] EFLAGS