Skip to contentSkip to conversation

[[email protected]: Re: v2.6 vs v3.0]

[email protected]: Re: v2.6 vs v3.0 Murray J. Root 1 participant 1 message Sep 29, 2002

lore
Share & tools
lore
#0 lore raw

Accidentally hit reply instead of list:

----- Forwarded message from "Murray J. Root" <[email protected]> -----

From: "Murray J. Root" <[email protected]>
To: Jens Axboe <[email protected]>
Subject: Re: v2.6 vs v3.0
Date: Sun, 29 Sep 2002 19:55:05 -0400
User-Agent: Mutt/1.4i

Quoted 33 lines · Jens Axboe
Quoted 11 lines · Murray J. Root
Quoted 10 lines · Jens Axboe
Quoted 8 lines · On Sun, Sep 29 2002, [email protected] wrote:
Quoted 4 lines

Anyway, people who are having VM trouble with the current 2.5.x series, please _complain_, and tell what your workload is. Don't sit silent and make us think we're good to go.. And if Ingo is right, I'll do the 3.0.x thing.

I think the broken IDE in 2.5.x has meant that it got seriously less testing overall than previous development trees :-(. Maybe after halloween when it stabilises a bit more we'll get more reports in.

Quoted 7 lines
Quoted 6 lines

2.5 is definitely desktop stable, so please test it if you can. Until recently there was a personal show stopper for me, the tasklist deadline. Now 2.5 is happily running on my desktop as well.

2.5 IDE stability should be just as good as 2.4-ac.

Hmm - our definitions must be different.

Not necessarily, you may just have worse luck than me.

Quoted 11 lines

ASUS P4S533 (SiS645DX chipset)
P4 2Ghz
1G PC2700 RAM

Disable SMP, enable APIC & IO APIC
Get "WARNING - Unexpected IO APIC found"
system freezes

Disable IO APIC, enable ACPI
system detects ACPI, builds table, freezes.

Quoted 9 lines
Quoted 5 lines

Disable ACPI, enable ide-scsi in the kernel
kernel panic analyzing hdc

None of these have been reported because I haven't had time to do all the work involved in making a report that anyone on the team will read.

But you have time to write this email and complain that it doesn't work? -> /dev/null, until you send proper reports.

I wasn't complaining - only pointing out that it wasn't ready yet. Writing the email took a few seconds. Getting the info for a proper bug report takes a long time, especially considering that one omission will get this response from you (and most other team members).
Debugging kernel's is NOT what I do with my time - just something I *thought* would be appreciated, since my mainboard/chipset is relatively new and not many people have it. Since only perfect reports are welcome, I'll refrain from submitting any in the future.

Signature · 19 lines
Murray J. Root
------------------------------------------------
DISCLAIMER: http://www.goldmark.org/jeff/stupid-disclaimers/
------------------------------------------------
Mandrake on irc.openprojects.net:
  #mandrake & #mandrake-linux = help for newbies 
  #mdk-cooker = Mandrake Cooker 


----- End forwarded message -----

-- 
Murray J. Root
------------------------------------------------
DISCLAIMER: http://www.goldmark.org/jeff/stupid-disclaimers/
------------------------------------------------
Mandrake on irc.openprojects.net:
  #mandrake & #mandrake-linux = help for newbies 
  #mdk-cooker = Mandrake Cooker