>(And sorry to pick on Matt, heh.) Trent.
You can pick on me all you like. I'll get to it when I can. Or won't. I
have 3 kids and three mortgages at present (no they're not related), so
I tend to be distracted from socially meaningful projects.
___
f
Matthew Fleming wrote:
As an aside, this is a quad-core in one package CPU (an X3363). On both
this box and a similar one with an X5470, console messages continue to
print out after "the system has been halted - press any key to reboot" -
in particular, the shutdown makes a bunch of the "beh
I use it all the time for compiles on top of nfs
On 6/18/07, Rong-en Fan <[EMAIL PROTECTED]> wrote:
I'm running 6.2-RELEASE, and I am wondering
if using nullfs w/ rw is safe in a production environment?
My impression is that ro nullfs is ok, but not rw.
Is this still the case?
Regards,
Rong-En
Just so you know... after having done a large number of SCSI target
mode implementations and having seen what initiators do, it's
Microsoft that is the closest to actually adhering to and using the
SCSI standards correctly.
On 7/20/07, Torfinn Ingolfsen <[EMAIL PROTECTED]> wrote:
On Fri, 20 Jul
working with Erik on this now...
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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
>
> 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'
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
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
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
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 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
There was some interest in QLogic's part a couple of years ago to get
4000 support and they contacted me, but I was pretty much uninterested
in it as a project. Go poke them again and see if they want to try.
Why do you think an iSCSI HBA would be of any benefit to anything
other than the target
Or LSI-Logic.
On 9/29/06, Wilko Bulte <[EMAIL PROTECTED]> wrote:
On Fri, Sep 29, 2006 at 06:01:25PM -0300, Eduardo Meyer wrote..
> How sad :~
>
> But thank you for the quick reply. I hope bsdstats initiative may help
> somehow this kind of problem.
All this said, I think you will find a Qlogic
Just to add a data point: I just upgraded feral.com to the latest
RELENG_6 branch. I have a dual port em for internal networks and I've
never seen the problems reported.
Also, for -current, things have now been stable again for the last
week or so for em on multiple machines (most of which have d
I would recommend staying with FreeBSD-5.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
That's an odd one. It means that the DMA of the ICB failed.
Three questions:
a) Tell me more about this system
b) Is this still a problem for the latest RELENG_6 branch changes?
c) Can you try a test kernel?
On 10/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I having problems getting thi
est version to see if it would fail again
and it continued to work. *sigh*
The good news, I am working. The bad news is I am not sure what was
really wrong.
Thanks for you help,
Dave
On 10/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On 10/10/06, Matthew Jacob <[EMAIL PROTECT
YMMV and your message is content free. I use sio all the time as a
[EMAIL PROTECTED] w/o any problems.
On 11/12/06, Sergey Matveychuk <[EMAIL PROTECTED]> wrote:
Do you know an old sio driver is hardly usable?
There are many silo overflows, working with a terminal device is a
nightmare. There wa
[i'm on vacation now]
Hmm- I thought I put in code so you should only see one of those. I'll
check this out when I get back next week.
On 11/21/06, Dave <[EMAIL PROTECTED]> wrote:
We have a new SunFire X4100 box and so I figured I would try 6.2 RC1
on it. Everything seems to work with the excep
- 2006 Nov 7-CURRENT snapshot probes the two HDDs case, but the HDDs
are recognized as very slow devices such as 6MB/s, and accessing
it makes the box freeze, too.
The 6MB/s thing I'm working on now. I have no clue about the other
issues at this time.
.
I see. BTW, I confirmed that mpt worked on the November snapshot
except the data transfer rate was 6.6MB/s. Is it worth trying the
latest current?
Just fixed, I think, as of last night.
___
freebsd-stable@freebsd.org mailing list
http://lists.
Brute force things to try, IMO:
a) Try a different (non-adaptec) SCSI controller
b) Run non-SMP
c) Swap motherboard
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[E
Helpful information would be:
a) Release
b) Connection Topology
It looks like you're going through a switch. Your short term solution
will be to zone your box and the CX300 together excluding all else.
A longer term solution is for me to MFC the new SAN evaluation code
which is a bit less har
On 2/5/07, Eduardo Meyer <[EMAIL PROTECTED]> wrote:
On 2/5/07, Matthew Jacob <[EMAIL PROTECTED]> wrote:
> Helpful information would be:
>
> a) Release
> b) Connection Topology
>
> It looks like you're going through a switch. Your short term solution
>
Generally speaking, the LSI-Logic cards are faster, at least for 2Gb,
in terms of IOPS.
However, the LSI-Logic firmware is less capable of coping with
complicated topologies and the mpt(4) driver is less mature than
isp(4).
Another thing to keep in mind is that for new cards (as opposed to
'EBay
It's been seen before but the fix isn't know yet.
On 3/27/07, Richard Tector <[EMAIL PROTECTED]> wrote:
I'm suffering from very slow write performance on a Dell PowerEdge 860
with the SAS5/IR controller (mpt driver) running either 6.2-RELEASE or
6.2-STABLE with sources from yesterday. The contro
not at the momeny- it's really that I won't have time until april
On 3/27/07, Richard Tector <[EMAIL PROTECTED]> wrote:
Matthew Jacob wrote:
> It's been seen before but the fix isn't know yet.
>
> On 3/27/07, Richard Tector <[EMAIL PROTECTED]> wro
On 4/1/07, Richard Tector <[EMAIL PROTECTED]> wrote:
Matthew Jacob wrote:
> On 3/27/07, Richard Tector <[EMAIL PROTECTED]> wrote:
>> Matthew Jacob wrote:
>> > It's been seen before but the fix isn't know yet.
>> >
>> > On 3/27/07, Ric
pleasep pooint out what the error is, and are you booting verbose?
On 4/1/07, JoaoBR <[EMAIL PROTECTED]> wrote:
with new sources I get an mpt error which is not present with sources from
march 28
mpt0: port 0xdc00-0xdcff mem
0xfd7e-0xfd7f,0xfd7c-0xfd7d irq 16 at device 4.0 on
this reset bus didn't and do not happen with some day older sources:
> > (xpt0:mpt0:0:-1:-1): reset bus
Well, don't worry about it. It's always been happening.
no, I do not boot verbose
Thanks. I'll make this message show up under 'bootverbose' only.,
> > ...
> > da0 at mpt0 bus 0 tar
> > > > (xpt0:mpt0:0:-1:-1): reset bus
periph:sim:channel:target:lun
target == lun == -1 == wildcard, so the initial bus reset applies to a
nexus for all targets and luns on that channel on that sim (mpt0) on
that periph (xpt0)
would you mind to tell why it happens and this "-1" values ?
___
Is there any news on the performance of this card?
I personally have not been able to reproduce the problem. It seems to
occur whether in Integrated Raid or not. It seems to be related to
specific backplanes and drives. It's an important problem to solve I
agree.
__
hanks.
On 4/24/07, J. Martin Petersen <[EMAIL PROTECTED]> wrote:
Matthew Jacob wrote:
>>
>> Is there any news on the performance of this card?
>>
>
> I personally have not been able to reproduce the problem. It seems to
> occur whether in Integrated Raid or not. It
Sorry- my bad. I'll fix shortly.
On 5/10/07, FreeBSD Tinderbox <[EMAIL PROTECTED]> wrote:
TB --- 2007-05-10 14:42:44 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2007-05-10 14:42:44 - starting RELENG_5 tinderbox run for sparc64/sparc64
TB --- 2007-05-10 14:42:44 - cleaning the obje
FWIW, IMO- don't wire- use glabel instead.
On 5/25/07, Scott Long <[EMAIL PROTECTED]> wrote:
Vivek Khera wrote:
> On May 25, 2007, at 11:22 AM, Scott Long wrote:
>
>> Look in /sys/conf/NOTES for a long discussion on wiring SCSI device
>> order.
>
> Thanks! That looks like it should do the trick
Sigh. Sorry. I'm on it.
On 2/5/06, FreeBSD Tinderbox <[EMAIL PROTECTED]> wrote:
> TB --- 2006-02-05 11:55:13 - tinderbox 2.3 running on freebsd-stable.sentex.ca
> TB --- 2006-02-05 11:55:13 - starting RELENG_5 tinderbox run for
> sparc64/sparc64
> TB --- 2006-02-05 11:55:13 - cleaning the object
Too late. Scott beat me to it.
On 2/5/06, Matthew Jacob <[EMAIL PROTECTED]> wrote:
> Sigh. Sorry. I'm on it.
>
>
> On 2/5/06, FreeBSD Tinderbox <[EMAIL PROTECTED]> wrote:
> > TB --- 2006-02-05 11:55:13 - tinderbox 2.3 running on
> > freebsd-stable
I must have missed something here. What's the problem that causes
contigmalloc to be called here? If this is to do with > 4GB of memory, that
was fixed in -CURRENT over a month ago.
-Original Message-
From: Ganbold [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 02, 2006 10:28 PM
To: Kris K
On Mon, 3 Apr 2006, Scott Long wrote:
Matthew Jacob wrote:
I must have missed something here. What's the problem that causes
contigmalloc to be called here? If this is to do with > 4GB of memory, that
was fixed in -CURRENT over a month ago.
He's using 6.0-RELEASE.
A reaso
>
> mhh, isn't mpt only a SCSI controller (not a RAID controller)?
Not in some configurations.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
The mpt driver was just MFC'd, but that won't help the adaptec issue.
There is a remote chance that somebody I'm doing work for will want a
FreeBSD driver for the adaptec card, but that won't be for a couple of
months.
It's a huge PITA- the SuperMicro boards are nice , but they don't get
along w
I'm assuming that this is just stale information for the Tinderbox.
There is no mpt_freebsd.c defined in sys/conf/files any more.
On 6/8/06, FreeBSD Tinderbox <[EMAIL PROTECTED]> wrote:
TB --- 2006-06-08 21:32:20 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2006-06-08 21:32:20 - s
Ah- never mind- my bad.
On 6/8/06, Matthew Jacob <[EMAIL PROTECTED]> wrote:
I'm assuming that this is just stale information for the Tinderbox.
There is no mpt_freebsd.c defined in sys/conf/files any more.
On 6/8/06, FreeBSD Tinderbox <[EMAIL PROTECTED]> wrote:
> TB ---
Well, I have to say that I had to reboot my 6.1 gateway on Sunday. It
was 5.X prior to this and never had to be rebooted.
On 6/26/06, Marc G. Fournier <[EMAIL PROTECTED]> wrote:
Okay, now this is getting ridiculous .. and for all those that have been
helping me debug things over the past few da
Yes, the 234X cards have been supported for quite a while.
DELL has a clone card which up until recently wasn't supported.
The 236X/63XX cards are not yet supported.
On 4/14/05, wsk <[EMAIL PROTECTED]> wrote:
> folks:
> Can the Qlogic 2340 Fibre Channel card works on FreeBSD now?
> DELL release
Yeah, sorry- the newer QLogic cards have firmware that has a different
protocol that I haven't written the code for yet.
In general, always load the firmware module as well. *EVENTUALLY*
we'll be able to unload it and reclaim the member.
On 5/2/05, Danny Braniss <[EMAIL PROTECTED]> wrote:
> > On
What an amusing rant. As far as I can tell, I've always been banned
from your Inbox whether I called you BIll, Paul, Wpaul, or
OMisterWizard!
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscri
Hmm- I doesn't recall "name not mentioned" telling me about this
earlier- perhaps he can dig up the mail as I haven't had any mail from
him directly in years that I recall.
Is the tinderbox still failing? I haven't seen that mail- maybe I'm not
on the list it's being sent to?
There are two
On Thu, 2 Feb 2006, Matthew Jacob wrote:
MJ>Is the tinderbox still failing? I haven't seen that mail- maybe I'm not on
MJ>the list it's being sent to?
You may look into either stable@ or spar64@
Ah. I'm subscribed to neither. Okay- thanks for the headsup that it
I would think that the tinderboxes should run 100% the same flags as
what normal release builds use. Nothing more, nothing less.
What I would like to see is a pointer to a procedure and tools to make
sure builds aren't broken.
I've been refreshing my memory about email going back about 5
On Fri, 27 Oct 2000, Mike Smith wrote:
> >
> > There are some things which are broken in -stable that need to be
> > fixed (alpha booting, e.g.). We'll try to leave the world a better
> > place for our efforts.
>
> -stable world builds, installs and boots on my pws433 as of earlier
> today (w
I'll look at it when I next spend a couple of days on this NIC (hopefully next
week).
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
I'm not sure what you're talking about here with this test program
(deleted)- unless you've dorked with MAXPHYS defines, the maximum you
can any tape record at is 64K.
>
> > I'm not sure that this is right. The NetBSD driver will do the same
> > behaviour at this point.
>
> Maybe it has been c
> 3) Multi-Initiator on SCSI? Don't make me laugh. Every FC drive has two
> ports as standard. Multi-Initiator is built in.
A word of caution about this- there is a lot of buggy driver f/w for the
dual ports.
> 6) Fibrechannel drives do not consume 50% more than SCSI drives unless you
What doe
> > > 6) Fibrechannel drives do not consume 50% more than SCSI drives unless you
> >
> > What does this mean?
>
> Sorry, it was meant to be "50% more power".
To be sure!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
56 matches
Mail list logo
