On 9/15/06, Conrad Burger <[EMAIL PROTECTED]> wrote:
Hi
Has anyone been able to solve the problem with the bce driver on 6.1-stable?
I am running 6.1-stable(200609013)AMD64 on a Dell 1950 with a SMP kernel.
The system boots up fine. When I copy data to an nfs mount the bce network
interface ti
On 6-STABLE, those "Error 22" messages on boot, show up too slowly,
one character at a time, at about one line every 30 seconds, which delays
the boot process on almost 20 (twenty) minutes. After that huge delay, the
disc information is shown and the file system is fsck'ed, as usually. However,
di
On 9/9/06, Matthew Jacob <[EMAIL PROTECTED]> wrote:
> >
> > Insofar as the Error 22- that's normal to see those for verbose
> > booting. They should be more informative as to why those are
> > occurring.
> >
>
> You're right. Those messages are evident only while verbose booting,
> so, I'm not re
If by "all the time" you mean every time certain disk operations
are performed (tarball extraction, files download...), then, yes.
All the time. Otherwise, no error shows up.
Hmm. Okay. I'll work on this.
>
> Insofar as the Error 22- that's normal to see those for verbose
> booting. They sho
On 9/9/06, Matthew Jacob <[EMAIL PROTECTED]> wrote:
Oops- mangled reply.
On 9/9/06, Matthew Jacob <[EMAIL PROTECTED]> wrote:
> >
> > is gone, but a new error message appears as often as the former,
> > and under the same circumstances:
> >
> > > mpt0: QUEUE_FULL: Bus 0x00 Target 0x00 Depth 128
Oops- mangled reply.
On 9/9/06, Matthew Jacob <[EMAIL PROTECTED]> wrote:
>
> is gone, but a new error message appears as often as the former,
> and under the same circumstances:
>
> > mpt0: QUEUE_FULL: Bus 0x00 Target 0x00 Depth 128
Do you see these all the time? If so I'll have to connect
is gone, but a new error message appears as often as the former,
and under the same circumstances:
> mpt0: QUEUE_FULL: Bus 0x00 Target 0x00 Depth 128
--
Alex
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/fr
I've update to the latest 7-CURRENT (last night, 10pm CST) and now
the previous error message
mpt0: Unhandled Event Notify Frame. Event 0xe (ACK not required).
(http://www.bsd.org.mx/~alex/logs/messages.CURRENT.0902)
is gone, but a new error message appears as often as the former,
and under th
On Mon, Sep 04, 2006 at 02:34:14PM -0500, Alex Salazar wrote:
> On 9/4/06, Morten A. Middelthon <[EMAIL PROTECTED]> wrote:
> >On Mon, Sep 04, 2006 at 07:47:21AM +0200, Morten A. Middelthon wrote:
> >> On Sat, Sep 02, 2006 at 04:23:21AM -0500, Alex Salazar wrote:
> >> > Apologies for the long messag
On 9/4/06, Morten A. Middelthon <[EMAIL PROTECTED]> wrote:
On Mon, Sep 04, 2006 at 07:47:21AM +0200, Morten A. Middelthon wrote:
> On Sat, Sep 02, 2006 at 04:23:21AM -0500, Alex Salazar wrote:
> > Apologies for the long message, and thanks in advance for any response.
> >
> > I've just bought one
On Mon, Sep 04, 2006 at 07:47:21AM +0200, Morten A. Middelthon wrote:
> On Sat, Sep 02, 2006 at 04:23:21AM -0500, Alex Salazar wrote:
> > Apologies for the long message, and thanks in advance for any response.
> >
> > I've just bought one of those new generation Dell servers, specifically,
> > the
On Sat, Sep 02, 2006 at 04:23:21AM -0500, Alex Salazar wrote:
> Apologies for the long message, and thanks in advance for any response.
>
> I've just bought one of those new generation Dell servers, specifically,
> the PowerEdge 1950.
>
> This is a dual Intel Dual Core Xeon 5050, 3.0 GHz, 667MHz
On 9/2/06, Matthew Jacob <[EMAIL PROTECTED]> wrote:
> > As a workaround, I disabled the APICs (hint.apic.0.disabled),
> and that ~15 minutes delay at boot up, now was gone. Fine.
>
> (BTW, 7-CURRENT has the same problem, but without that huge delay)
Do you have APIC disabled for 7-CURRENT also?
Thank you :-) I am myself considering hardware from the same vendor
and I assume others are as well, so I appreciate the effort.
It's a Tier One vendor- you can rest assured that FreeBSD will support it.
___
freebsd-stable@freebsd.org mailing list
htt
> > Yup, sounds like a mess here.
> But is there a solution or workaround rather than just concluding?
Well, I've collected some info and am trying to sort through all of
the stories. There certainly is something wrong with recent mpt(4) and
I'm trying to figure out what. It affects some people's
>
> Yup, sounds like a mess here.
But is there a solution or workaround rather than just concluding?
Well, I've collected some info and am trying to sort through all of
the stories. There certainly is something wrong with recent mpt(4) and
I'm trying to figure out what. It affects some people'
> mpt0: Timedout requests already complete. Interrupts may not be functioning.
>
I've seen this on Supermicro EM64T in the past on 7-current, but that
went away about 3-4 weeks ago. It really seemed to me that this was
indeed an interrupt related problem.
Yup, sounds like a mess here.
But is th
The OS booted up and the SAS controller was now detected and supported by
the mpt(4) driver:
---
mpt0: port 0xec00-0xecff mem 0xfc4fc000-0xfc4f,
0xfc4e-0xfc4e irq 64 at device 8.0 on pci2
mpt0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xec00
mpt0: Reserved 0x4000 bytes for rid 0x1
Apologies for the long message, and thanks in advance for any response.
I've just bought one of those new generation Dell servers, specifically,
the PowerEdge 1950.
This is a dual Intel Dual Core Xeon 5050, 3.0 GHz, 667MHz FSB,
1GB 533MHz RAM, system.
This server has a LSI Logic SAS 5/i integra
19 matches
Mail list logo
