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 Libre
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.
Zepha
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
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
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, Rag
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 corru
> 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
n't say I do my debugging 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-test
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,
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 heav
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. Vide
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.
> P
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 wit
"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
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?
"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 'i
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 reap
et gets
trashed 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]
> Sub
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 o
> 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 =
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",
>cp
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 (c
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 bu
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,
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,
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]
Please
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
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
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,
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: htt
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 tra
> 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 proc
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
33 matches
Mail list logo
