On 7/26/2010 2:51 PM, Harald Schmalzbauer wrote:
On 26.07.2010 18:19
Harald:
Your patch looks clear. Now that the 8.1 mess is over, we
should move quickly to bring up as many of the recent changes
to -current as stable/8.
George V. Neville-Neil already already got started on some of
On 26.07.2010 18:19, Brian A. Seklecki (CFI NOC) wrote:
> On 7/19/2010 12:00 PM, Harald Schmalzbauer wrote:
>> **/
>> -/*$FreeBSD: src/sys/dev/e1000/if_igb.h,v 1.4.2.2.2.1 2010/06/14
>> 02:09:06 kensmith Exp $*/
>> +/*$FreeBS
>
>
> Haralad:
>
> It looks
On 7/19/2010 12:00 PM, Harald Schmalzbauer wrote:
**/
-/*$FreeBSD: src/sys/dev/e1000/if_igb.h,v 1.4.2.2.2.1 2010/06/14 02:09:06
kensmith Exp $*/
+/*$FreeBS
Haralad:
It looks like your patch is identical to the patch RFP'd from HEAD
to branches/stab
On Mon, 19 Jul 2010, Brian A. Seklecki wrote:
On Thu, 2010-07-15 at 10:53 -0700, Jack Vogel wrote:
The fact that I WISH it to be MFC'd doesn't mean that I am actually
given permission to do so.
It seems 8.1 release was tagged on Saturday so we're proper-f*
I can appreciate your frustra
On Thu, 2010-07-15 at 10:53 -0700, Jack Vogel wrote:
> The fact that I WISH it to be MFC'd doesn't mean that I am actually
> given permission to do so.
It seems 8.1 release was tagged on Saturday so we're proper-fucked
(we will have to run local patches on all 1850s and 2850s for the
duratio
On Jul 15, 2010, at 7:48 PM, Steve Polyack wrote:
> On 07/15/10 13:31, Michael Tuexen wrote:
>> On Jul 15, 2010, at 6:50 PM, Brian A. Seklecki wrote:
>>
>>
>>>
It may have gone in before the RELENG_8_1 tag/branch occurred? SVN
r209309
Jacks's change went into stable/
> As Brian stated, the change has already been MFC'd into stable/8 (June
> 18th) with the following comment from Jack:
>
> "MFC to RELENG8.1 asap"
>
I also dont see the issue listed on:
http://wiki.freebsd.org/Releng/8.1TODO
If someone can put it on there, even if the RELENG engineer doesn
The fact that I WISH it to be MFC'd doesn't mean that I am actually given
permission to do so.
Jack
On Thu, Jul 15, 2010 at 10:48 AM, Steve Polyack wrote:
> On 07/15/10 13:31, Michael Tuexen wrote:
>
>> On Jul 15, 2010, at 6:50 PM, Brian A. Seklecki wrote:
>>
>>
>>
>>>
>>>
It may have gon
On 07/15/10 13:31, Michael Tuexen wrote:
On Jul 15, 2010, at 6:50 PM, Brian A. Seklecki wrote:
It may have gone in before the RELENG_8_1 tag/branch occurred? SVN
r209309
Jacks's change went into stable/8 on June 18:
Also, did anyone provide feedback on SVN r209959 to
head/
On Jul 15, 2010, at 6:50 PM, Brian A. Seklecki wrote:
>
>> It may have gone in before the RELENG_8_1 tag/branch occurred? SVN
>> r209309
>>
>> Jacks's change went into stable/8 on June 18:
>>
>
> Also, did anyone provide feedback on SVN r209959 to
> head/sys/dev/e1000/if_em.c ?
>
> It's s
> It may have gone in before the RELENG_8_1 tag/branch occurred? SVN
> r209309
>
> Jacks's change went into stable/8 on June 18:
>
Also, did anyone provide feedback on SVN r209959 to
head/sys/dev/e1000/if_em.c ?
It's saying "8.1 MFC", so you might want to ask people to test that on
stable/
On Tue, 2010-07-13 at 21:18 +0200, Harald Schmalzbauer wrote:
> Jack Vogel schrieb am 18.06.2010 20:01 (localtime):
> > Yes, the commits today are slated to get into 8.1, at least that's my
> > understanding.
> >
> > Jack
>
> Hello, is this still on the to-merge-before-8.1-RELEASE list?
Its hard
Jack Vogel schrieb am 18.06.2010 20:01 (localtime):
Yes, the commits today are slated to get into 8.1, at least that's my
understanding.
Jack
Hello, is this still on the to-merge-before-8.1-RELEASE list?
Thanks,
-Harry
...
Adding Jack Vogel of Intel to the CC list, as he's been working on
On Fri, 18 Jun 2010, Jack Vogel wrote:
Yes, the commits today are slated to get into 8.1, at least that's my
understanding.
Lets hope so; its looking very promising on the systems I'm able to test
on.
We should ask 82541EI and Dell 9th gen PowerEdge users to test them right
away.
~BAS
Yes, the commits today are slated to get into 8.1, at least that's my
understanding.
Jack
On Fri, Jun 18, 2010 at 10:46 AM, Brandon Gooch wrote:
> On Tue, Jun 1, 2010 at 2:37 PM, Jeremy Chadwick
> wrote:
> > On Tue, Jun 01, 2010 at 03:18:39PM -0400, Brian A. Seklecki wrote:
> >> = Re-posted f
On Tue, Jun 1, 2010 at 2:37 PM, Jeremy Chadwick
wrote:
> On Tue, Jun 01, 2010 at 03:18:39PM -0400, Brian A. Seklecki wrote:
>> = Re-posted from freebsd-hardware@, since this is more of a bug
>> report than a hardware comparability inquiry / buying strategy
>> discussion. ==
>>
>> All:
>>
>> Ha
On Tue, Jun 01, 2010 at 03:18:39PM -0400, Brian A. Seklecki wrote:
> = Re-posted from freebsd-hardware@, since this is more of a bug
> report than a hardware comparability inquiry / buying strategy
> discussion. ==
>
> All:
>
> Has anyone upgraded their PowerEdge 1850s to 8.0-PL or
> RELEN
= Re-posted from freebsd-hardware@, since this is more of a bug
report than a hardware comparability inquiry / buying strategy
discussion. ==
All:
Has anyone upgraded their PowerEdge 1850s to 8.0-PL or
RELENG_8 -stable? We're seeing problems where 7.2-PL and
6.3-PL were not affected on
is problem. Please let me
know ASAP if it works for you.
Scott
Interestingly enough, FreeBSD booted fine on the machine installed
(updated from 7.0 to 7.1-RELEASE-p4).
This machine is a PowerEdge 1850 bios A04 with Perc 4*e*/Si bios
H430 / fwVer 521S.
When booting a drive from this machine
dated from 7.0 to 7.1-RELEASE-p4).
This machine is a PowerEdge 1850 bios A04 with Perc 4*e*/Si bios H430
/ fwVer 521S.
When booting a drive from this machine in another PowerEdge 1850,
bios A07 Perc 4e/Si bios H435 FwVer 5B2D
it drops to the mount r
7.1-RELEASE-p4.
Interestingly enough, FreeBSD booted fine on the machine installed
(updated from 7.0 to 7.1-RELEASE-p4).
This machine is a PowerEdge 1850 bios A04 with Perc 43/Si bios H430 /
fwVer 521S.
When booting a drive from this machine in another PowerEdge 1850, bios
A07 Perc 4e/Si
machine is a PowerEdge 1850 bios A04 with Perc 43/Si bios H430 /
fwVer 521S.
When booting a drive from this machine in another PowerEdge 1850, bios
A07 Perc 4e/Si bios H435 FwVer 5B2D
it drops to the can mount root prompt, similar as reported originally,
see http://omx.ch/om/stuff
Brian A. Seklecki wrote:
NOTE: You're using the 4e/Si, which we have as well. We're experiencing
random crashes on the 1850/8th gen, as a result of a (believed) DMA bug
introduced into 7.x
Just to note, we are only seeing these issues in combination with megarc
(/usr/ports/sysutils/megarc)
> amr0: Firmware 521X, BIOS H430, 256MB RAM
> amr0: delete logical drives supported by controller
Any time!
NOTE: You're using the 4e/Si, which we have as well. We're experiencing
random crashes on the 1850/8th gen, as a result of a (believed) DMA bug
introduced into 7.x
Please let us know i
On Wed, 2009-02-11 at 10:38 -0500, Brian A. Seklecki wrote:
> There's already discussion about this in the archives. We're aware and
> working on it.
>
> Set:
> /boo/loader.conf
> kern.cam.scsi_delay=2
> As a work-around for now.
Many thanks for your answer, it fixed the problem for now.
Now
ware and
working on it.
Set:
/boo/loader.conf
kern.cam.scsi_delay=2
As a work-around for now.
Tracking the megarc memory corruption (and general amr(4) problems with
the PERC4) at:
http://www.freebsd.org/cgi/query-pr.cgi?pr=128082
~BAS
> poweredge 1950, but it failed completely
Hello,
This afternoon I wanted to upgrade to 7.1 two good old dell PowerEdge
servers which were running FreeBSD 6.x. It went fine and quickly on the
poweredge 1950, but it failed completely on the poweredge 1850.
Facts:
- boot cd and setup / operation of freebsd 6.x or 7.0 is fine
Message
I've got Dell PowerEdge 1850 (2G RAM, 2x78G SCSI RAID, 2xXEON) running
FreeBSD 6.1 SMP installed by the hosting provider and I can't make
buildworld on it.
Here's my /etc/make.conf:
PERL_VER=5.8.8
PERL_VERSION=5.8.8
Here's the output of `make buildworld`.
===> usr.sbin
On Oct 5, 2004, at 2:32 AM, Key Dof wrote:
Ok Great, what about the Raid controller PERC 4e/SI ?
Call Dell and ask to speak to a server configuration engineer. They
*really* know what they're talking about. Having an account with Dell
makes this easier. Ask this engineer what chipset is on thi
> Ok Great, what about the Raid controller PERC 4e/SI ?
We're not using any RAID stuff on ours, but the SCSI stuff works
fine with the mpt driver.
David.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
Ok Great, what about the Raid controller PERC 4e/SI ?
Thanks
On Mon, 2004-10-04 at 21:01, David Malone wrote:
> On Mon, Oct 04, 2004 at 04:03:03PM +0200, Jorn Argelo wrote:
> > Anyway, if I get it right it runs an dual Xeon with EM64T. If you want to use
> > that you will need the AMD64 port of F
On Mon, Oct 04, 2004 at 04:03:03PM +0200, Jorn Argelo wrote:
> Anyway, if I get it right it runs an dual Xeon with EM64T. If you want to use
> that you will need the AMD64 port of FreeBSD 5.2.1. I'm not sure if EM64T is
> backwards compatible with the x86 instruction code, so 4.10 will not be an
>
On Mon, 04 Oct 2004 13:59:19 +0200, Key Dof wrote
> Hi,
> Did anyone try to use fbsd 4.10 on a dell poweredge 1850? i am
> intending to buy one but i need to be sure that i can run fbsd on it
> (scsi, raid and network).
> Thanks
>
> ___
Quoting Key Dof <[EMAIL PROTECTED]>:
[...]
> Did anyone try to use fbsd 4.10 on a dell poweredge 1850?
Yes.
[...]
--
Sahil Tandon
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe,
Hi,
Did anyone try to use fbsd 4.10 on a dell poweredge 1850? i am
intending to buy one but i need to be sure that i can run fbsd on it
(scsi, raid and network).
Thanks
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo
35 matches
Mail list logo
