Quoting [EMAIL PROTECTED]:
Quoting Jeremy Chadwick [EMAIL PROTECTED]:
Based on my experiences with my workplace-provided T60p, it's safe to
say I'll never recommend a Lenovo product. The temperatures of these
laptops are absolutely insane, supported by an incredibly loud fan. I'm
not
On Tue, Jun 03, 2008 at 11:13:27AM -0400, [EMAIL PROTECTED] wrote:
Quoting [EMAIL PROTECTED]:
Quoting Jeremy Chadwick [EMAIL PROTECTED]:
Based on my experiences with my workplace-provided T60p, it's safe to
say I'll never recommend a Lenovo product. The temperatures of these
laptops
Quoting Jeremy Chadwick [EMAIL PROTECTED]:
Based on my experiences with my workplace-provided T60p, it's safe to
say I'll never recommend a Lenovo product. The temperatures of these
laptops are absolutely insane, supported by an incredibly loud fan. I'm
not interested in a product that can
On Tue, Jun 03, 2008 at 11:12:41AM -0400, [EMAIL PROTECTED] wrote:
Quoting Jeremy Chadwick [EMAIL PROTECTED]:
Based on my experiences with my workplace-provided T60p, it's safe to
say I'll never recommend a Lenovo product. The temperatures of these
laptops are absolutely insane, supported
On Wednesday 04 June 2008 07:25:13 am Jeremy Chadwick wrote:
On Tue, Jun 03, 2008 at 11:13:27AM -0400, [EMAIL PROTECTED] wrote:
Quoting [EMAIL PROTECTED]:
Quoting Jeremy Chadwick [EMAIL PROTECTED]:
Based on my experiences with my workplace-provided T60p, it's safe to
say I'll never
On Wed, Jun 04, 2008 at 07:45:12AM -0500, Josh Paetzel wrote:
Hi,
I'm interested in whatever cooling solutions people have...
For my T60 i made a perl script for controlling the fans and
the cpu speed. A few months ago i changed it to work together
with powerd and i must say, i got it pretty
I wouldn't report this if not for one coincidence (which is described
below). I have too little facts, so this is more of a mystery problem
tale than a real problem report.
There are two systems:
1. old, slow, i386, UP, 7-STABLE
2. new, fast, amd64, MP, 6.3-RELEASE
Systems are located at
On Wed, Jun 04, 2008 at 06:07:47PM +0300, Andriy Gapon wrote:
I wouldn't report this if not for one coincidence (which is described
below). I have too little facts, so this is more of a mystery problem
tale than a real problem report.
There are two systems:
1. old, slow, i386, UP,
on 04/06/2008 18:23 Kostik Belousov said the following:
On Wed, Jun 04, 2008 at 06:07:47PM +0300, Andriy Gapon wrote:
[snip]
dumps are done on live filesystems using -L.
[snip]
4. both systems have gjournal support (on 6.X it is added via a
non-official patch), there are gjournaled filesystems
On Wed, Jun 04, 2008 at 06:33:45PM +0300, Andriy Gapon wrote:
on 04/06/2008 18:23 Kostik Belousov said the following:
On Wed, Jun 04, 2008 at 06:07:47PM +0300, Andriy Gapon wrote:
[snip]
dumps are done on live filesystems using -L.
[snip]
4. both systems have gjournal support (on 6.X it
On Wed, Jun 04, 2008 at 06:33:45PM +0300, Andriy Gapon wrote:
on 04/06/2008 18:23 Kostik Belousov said the following:
On Wed, Jun 04, 2008 at 06:07:47PM +0300, Andriy Gapon wrote:
[snip]
dumps are done on live filesystems using -L.
[snip]
4. both systems have gjournal support (on 6.X it
Richard Arends wrote:
On Wed, Jun 04, 2008 at 07:45:12AM -0500, Josh Paetzel wrote:
Hi,
I'm interested in whatever cooling solutions people have...
I didn't follow this thread earlier because I don't have this laptop,
but I wonder if anyone has offered the suggestion to blow out all the
Okay, I totally understand that FreeBSD wants people to upgrade from
6.2 to 6.3. But given that 6.3 is still experiencing bugs with things
that are working fine and stable in 6.2, this is a pretty hard case to
make.
This is also a fairly significant investment in terms of time and
money
Jo Rhett wrote:
Okay, I totally understand that FreeBSD wants people to upgrade from 6.2
to 6.3.
It isn't that we want people to upgrade, it's that we are trying to be
realistic regarding what we have the resources to support.
But given that 6.3 is still experiencing bugs with things that
On Tuesday 03 June 2008 03:04:18 pm Peter Jeremy wrote:
BTW, your MUA's list-reply configuration don't recognize that
freebsd-stable@ and stable@ are aliases.
Yes, kmail is broken and the authors refuse to fix it. It happens on reply to
a foo@ e-mail (it changes the 'To' to 'freebsd-foo@'
On Tuesday 03 June 2008 10:49:41 pm Doug Barton wrote:
Carlos A. M. dos Santos wrote:
On Mon, May 26, 2008 at 3:24 AM, Jeremy Chadwick [EMAIL PROTECTED]
wrote:
On Sun, May 25, 2008 at 11:52:06PM -0300, Carlos A. M. dos Santos wrote:
I have been struglling with sysinstall, attempting to
Doug Barton wrote:
Jo Rhett wrote:
Okay, I totally understand that FreeBSD wants people to upgrade from
6.2 to 6.3.
It isn't that we want people to upgrade, it's that we are trying to be
realistic regarding what we have the resources to support.
But given that 6.3 is still experiencing
Jo Rhett wrote:
Okay, I totally understand that FreeBSD wants people to upgrade from 6.2
to 6.3. But given that 6.3 is still experiencing bugs with things that
are working fine and stable in 6.2, this is a pretty hard case to make.
Can you describe the bugs that are affecting you?
This is
On Wed, 2008-06-04 at 07:45 -0500, Josh Paetzel wrote:
On Wednesday 04 June 2008 07:25:13 am Jeremy Chadwick wrote:
On Tue, Jun 03, 2008 at 11:13:27AM -0400, [EMAIL PROTECTED] wrote:
Quoting [EMAIL PROTECTED]:
Quoting Jeremy Chadwick [EMAIL PROTECTED]:
Based on my experiences with
Scott Long wrote:
Jo Rhett wrote:
Okay, I totally understand that FreeBSD wants people to upgrade from
6.2 to 6.3. But given that 6.3 is still experiencing bugs with things
that are working fine and stable in 6.2, this is a pretty hard case to
make.
Can you describe the bugs that are
Stephen Clark wrote:
Scott Long wrote:
Jo Rhett wrote:
Okay, I totally understand that FreeBSD wants people to upgrade from
6.2 to 6.3. But given that 6.3 is still experiencing bugs with
things that are working fine and stable in 6.2, this is a pretty hard
case to make.
Can you describe
On Wed, Jun 04, 2008 at 11:00:41AM -0700, Doug Barton wrote:
Jo Rhett wrote:
...
But given that 6.3 is still experiencing bugs with things that
are working fine and stable in 6.2, this is a pretty hard case to make.
I admit to not having been following 6.x too closely, but are these
Hi,
I have boxes with 6.2-x86 to 7.0-amd64 with CPUs from AMD and Intel ranging
between Athlon64, Pentium4, Xeon processors.
OK I have setup powerd and when I run powerd I see (for example):
idle time 90%, decreasing clock speed from 2978 MHz to 2605 MHz
idle time 90%, decreasing clock
As some of you may know the FreeBSD Project has been attempting to shift
over from Feature based releases to Time based releases as far as
trying to schedule them goes. Lets just say that's still a work in
progress (as in doing that with FreeBSD 7.0 didn't work out so well).
This is the
The problem is not powerd but cpufreq. While cpufreq appears to work
well on my Athlon X2, it has never worked on any of my Core2Duo or
Core-based Xeon servers.
This is a great shame as these newer Intel chips have the capability to
clock up and down very quickly and seamlessly.
Who can
Clifton Royston wrote:
On Wed, Jun 04, 2008 at 11:00:41AM -0700, Doug Barton wrote:
Jo Rhett wrote:
...
But given that 6.3 is still experiencing bugs with things that
are working fine and stable in 6.2, this is a pretty hard case to make.
I admit to not having been following 6.x too closely,
Andrew Snow wrote:
The problem is not powerd but cpufreq. While cpufreq appears to work
well on my Athlon X2, it has never worked on any of my Core2Duo or
Core-based Xeon servers.
This is a great shame as these newer Intel chips have the capability to
clock up and down very quickly and
Hi.
After recent upgrading from 6.3-RC1/mpd-5.0rc1 to 6.3-STABLE/mpd-5.1
some of my PPPoE servers started to crash with about weekly period.
Usually they just just hang without rebooting and core dumping. Consoles
are inaccessible. All I have got from them was:
kernel: Fatal trap 12: page
My PC has built-in intel G33 graphics, which I'm trying to get to work
in something better then vesa.
Following the instructions in
http://lists.freebsd.org/pipermail/freebsd-stable/2008-January/039638.html
I have compiled and installed the driver and kernel modules from the git
trees for drm and
Evren Yurtesen wrote:
When you say that it doesnt work, does it give an error or? In my case
it doesnt give any errors just says it set it but I see that nothing is
set.
Here's one box:
CPU: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz
cpu0: ACPI CPU on acpi0
est0: Enhanced SpeedStep
Andrew Snow wrote:
Evren Yurtesen wrote:
When you say that it doesnt work, does it give an error or? In my case
it doesnt give any errors just says it set it but I see that nothing
is set.
Here's one box:
CPU: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz
cpu0: ACPI CPU on acpi0
est0:
On Thu, Jun 05, 2008 at 08:33:24AM +1000, Andrew Snow wrote:
Evren Yurtesen wrote:
When you say that it doesnt work, does it give an error or? In my case
it doesnt give any errors just says it set it but I see that nothing is
set.
Here's one box:
CPU: Intel(R) Core(TM)2 Duo CPU
Roland Smith wrote:
On Thu, Jun 05, 2008 at 08:33:24AM +1000, Andrew Snow wrote:
Here's another one:
CPU: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz
cpu0: ACPI CPU on acpi0
est0: Enhanced SpeedStep Frequency Control on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est:
On Wed, Jun 04, 2008 at 04:41:45PM -0500, Kevin Kinsey wrote:
Clifton Royston wrote:
For example, if I take a 6.3R CD, or build one for 6-RELENG, is there
a way to do an upgrade in place on each server? Or would it work
better to do a build from recent source on the development server,
On Jun 4, 2008, at 11:00 AM, Doug Barton wrote:
But given that 6.3 is still experiencing bugs with things that are
working fine and stable in 6.2, this is a pretty hard case to make.
I admit to not having been following 6.x too closely, but are these
things that have been reported, or
On Thu, Jun 05, 2008 at 01:21:35AM +0200, Greg Byshenk wrote:
On Wed, Jun 04, 2008 at 04:41:45PM -0500, Kevin Kinsey wrote:
Clifton Royston wrote:
For example, if I take a 6.3R CD, or build one for 6-RELENG, is there
a way to do an upgrade in place on each server? Or would it work
On Jun 4, 2008, at 11:39 AM, Kris Kennaway wrote:
Also, it's not like anyone should have been caught by surprise by
the 6.2 EoL; the expiry date has been advertised since the 6.2
release itself.
It has changed multiple times. I keep reviewing and finding 6.3 bugs
outstanding, and then
On Jun 4, 2008, at 12:00 PM, Scott Long wrote:
Can you describe the bugs that are affecting you?
gmirror failures, 3ware raid driver timeouts, bge0 problems. All
three in production use on dozens of systems.
This is also a fairly significant investment in terms of time and
money for any
On Jun 4, 2008, at 4:45 PM, Edwin Groothuis wrote:
We have about 40 servers which were running 6.1 and 6.2 and the
seven busy ones (application servers which do mail and proxying,
and the database servers) hung *dead* every week. One per day.
I'm sorry to hear that. Our servers have never
Jo Rhett wrote:
On Jun 4, 2008, at 11:39 AM, Kris Kennaway wrote:
Also, it's not like anyone should have been caught by surprise by the
6.2 EoL; the expiry date has been advertised since the 6.2 release
itself.
It has changed multiple times. I keep reviewing and finding 6.3 bugs
On Wed, Jun 04, 2008 at 10:43:27AM -1000, Clifton Royston wrote:
On Wed, Jun 04, 2008 at 11:00:41AM -0700, Doug Barton wrote:
Jo Rhett wrote:
...
But given that 6.3 is still experiencing bugs with things that
are working fine and stable in 6.2, this is a pretty hard case to make.
I
Jo Rhett wrote:
On Jun 4, 2008, at 12:00 PM, Scott Long wrote:
Can you describe the bugs that are affecting you?
gmirror failures, 3ware raid driver timeouts, bge0 problems. All three
in production use on dozens of systems.
Give me specific details on the 3ware and bge problems.
Scott
Jo Rhett wrote:
On Jun 4, 2008, at 11:39 AM, Kris Kennaway wrote:
Also, it's not like anyone should have been caught by surprise by
the 6.2 EoL; the expiry date has been advertised since the 6.2
release itself.
It has changed multiple times. I keep reviewing and finding 6.3
bugs
On Jun 4, 2008, at 5:05 PM, Scott Long wrote:
Jo Rhett wrote:
On Jun 4, 2008, at 12:00 PM, Scott Long wrote:
Can you describe the bugs that are affecting you?
gmirror failures, 3ware raid driver timeouts, bge0 problems. All
three in production use on dozens of systems.
Give me specific
- Original Message -
From: Jo Rhett [EMAIL PROTECTED]
I'm sorry to hear that. Our servers have never hung with 6.2.
Reboots only occurred to satisfy kernel security patches.
But with 6.3 there are many open bug reports about our exact hardware,
and I'd prefer to avoid swapping
On Wed, Jun 04, 2008 at 05:24:42PM -0700, Jo Rhett wrote:
On Jun 4, 2008, at 5:17 PM, Steven Hartland wrote:
I wouldn't be surprised if these are not new bugs, just something
that others have noticed later than 6.2 and I'd suggest you actually
try 6.3 to see if they are in fact an issue for
Jo Rhett wrote:
On Jun 4, 2008, at 5:05 PM, Scott Long wrote:
Jo Rhett wrote:
On Jun 4, 2008, at 12:00 PM, Scott Long wrote:
Can you describe the bugs that are affecting you?
gmirror failures, 3ware raid driver timeouts, bge0 problems. All
three in production use on dozens of systems.
On Thursday 05 June 2008 02:26:29 Jo Rhett wrote:
On Jun 4, 2008, at 5:05 PM, Scott Long wrote:
Jo Rhett wrote:
On Jun 4, 2008, at 12:00 PM, Scott Long wrote:
Can you describe the bugs that are affecting you?
gmirror failures, 3ware raid driver timeouts, bge0 problems. All
three in
If this is so important to you - contribute to the project and/or hire
a FreeBSD developer.
(Ah, the Curse of Open Source Projects..)
Adrian
2008/6/5 Jo Rhett [EMAIL PROTECTED]:
On Jun 4, 2008, at 5:17 PM, Steven Hartland wrote:
I wouldn't be surprised if these are not new bugs, just
On Jun 4, 2008, at 5:30 PM, Steven Hartland wrote:
That's unfortunate. One thing you might want to check is are there
any changes in those areas between 6.2 and 6.3 e.g. if its a bug
with a specific driver but said driver has had no commits or
not commits in the specific area then it may be
On Jun 4, 2008, at 5:35 PM, Edwin Groothuis wrote:
Use the eat-your-own-food approach (while not knowing what the 500
systems do): Make sure you use the same hardware and software as
what is in production. Upgrade it first, run it for two weeks. If
it doesn't, fallback and see where it went
On Jun 4, 2008, at 5:48 PM, Max Laier wrote:
Because the people who support FreeBSD 6.2 are also knee-deep in major
projects of their own!? We try try to not introduce regressions as we
move forward supporting new features and hardware, but unless people
put
in some effort of their own
On Jun 4, 2008, at 5:44 PM, Scott Long wrote:
Really, if it's such a big issue that you have time to bitch an moan
on the mailing lists, I don't understand why you don't have time to
also
help a goddamned developer identify the problem. Are you actually
experiencing problems with 6.3, or
I'm going to be offline for a week starting now, so please don't read
my lack of answers as anything other than out of town. Sorry.
For clarity: I'm not asking for anyone to fix anything. I honestly
believe most developers are addressing problems as fast as they can.
I'd help them in
54 matches
Mail list logo
