On Sun, 24 Jul 2005, Mike Tancsa wrote:
At 12:00 AM 24/07/2005, Karl Denninger wrote:
Finally, any pointers on a 2 port PCI SATA board that (1) is KNOWN to
work, (2) has EXTERNAL SATA connections, and (3) isn't one of those
whiz-bang all-in-one-RAID thingies that costs $500?
3ware makes an
On Sat, 23 Jul 2005, Karl Denninger wrote:
PR being filed now.
When you've filed the PR and get a PR# receipt back, please forward me the
PR# receipt.
FYI, your spam filter thinks every message I send you as spam. It's not
impossible it might think the same of the GNATS source address,
Those cards all have (and appear to require) PCI-64 (double-connector) bus
plug-ins. For those of us with single PCI bus slots (e.g. those of us who
don't have Opterons), that simply won't work unless I'm missing something.
--
--
Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids
On Sun, Jul 24, 2005 at 03:04:09PM +0100, Robert Watson wrote:
On Sat, 23 Jul 2005, Karl Denninger wrote:
PR being filed now.
When you've filed the PR and get a PR# receipt back, please forward me
the PR# receipt.
FYI, your spam filter thinks every message I send you as spam. It's
At 10:20 AM 24/07/2005, Karl Denninger wrote:
Those cards all have (and appear to require) PCI-64 (double-connector) bus
plug-ins. For those of us with single PCI bus slots (e.g. those of us who
don't have Opterons), that simply won't work unless I'm missing something.
I have used the 3ware
Update - it appears that as long as I only use ONE of the two channels on
the card, it works ok.
I've got a buildworld running right now on the Sandbox, but with only
one of the two disks attached. So far, no errors.
So it would appear that the problem IS related to the previously-reported
3Ware cards will work with 32 bit PCI buses.
At 10:20 AM 7/24/2005, Karl Denninger wrote:
Those cards all have (and appear to require) PCI-64 (double-connector) bus
plug-ins. For those of us with single PCI bus slots (e.g. those of us who
don't have Opterons), that simply won't work unless I'm
On Sat, Jul 23, 2005 at 11:00:55PM -0500, Karl Denninger wrote:
On Sun, Jul 24, 2005 at 05:43:34AM +0200, Erik Trulsson wrote:
On Sat, Jul 23, 2005 at 09:01:36PM -0500, Karl Denninger wrote:
Done.
Note that the Bustek and Adaptec cards which exhibit the problem BOTH
identify the
On Sun, Jul 24, 2005 at 07:58:20PM +0200, Erik Trulsson wrote:
On Sat, Jul 23, 2005 at 11:00:55PM -0500, Karl Denninger wrote:
Should not there be an EXPLICIT note in the release notes for hardware that
this chipset WILL NOT WORK PROPERLY?
It does seem to work for many users, or there would
On Sun, Jul 24, 2005 at 07:58:20PM +0200, Erik Trulsson wrote:
Most likely the bug you have run into is difficult or impossible to
reproduce on other hardware than the particular combination you are using.
FWIW my earlier post about it appearing to work with only one disk on the
chain was
At 02:13 PM 24/07/2005, Karl Denninger wrote:
On Sun, Jul 24, 2005 at 07:58:20PM +0200, Erik Trulsson wrote:
Most likely the bug you have run into is difficult or impossible to
reproduce on other hardware than the particular combination you are using.
FWIW my earlier post about it appearing
On Fri, 22 Jul 2005, Danny Howard wrote:
While I agree with Karl that introducing instability is a very bad
thing, I guess we now have an answer to Karl's vexation yesterday: [
http://lists.freebsd.org/pipermail/freebsd-stable/2005-July/017210.html
]
What I don't understand Robert is
On Fri, 22 Jul 2005, Karl Denninger wrote:
It is definitely NOT fixed in 6.0-BETA1
Within SECONDS of starting a buildworld after the provider rebuild
completed, I got this...
Could you file a PR based on this report? Specifically, if you could
include:
- The error output below.
- If
On Sat, Jul 23, 2005 at 08:53:02PM +0100, Robert Watson wrote:
On Fri, 22 Jul 2005, Danny Howard wrote:
While I agree with Karl that introducing instability is a very bad
thing, I guess we now have an answer to Karl's vexation yesterday: [
Done.
Note that the Bustek and Adaptec cards which exhibit the problem BOTH
identify the same (on two different machines) as SII 3112 boards, and
BOTH fail.
There are minor differences in the interrupts and memory mapping used
(which is to be expected, as there are peripherals in the production
On Sat, Jul 23, 2005 at 09:01:36PM -0500, Karl Denninger wrote:
Done.
Note that the Bustek and Adaptec cards which exhibit the problem BOTH
identify the same (on two different machines) as SII 3112 boards, and
BOTH fail.
There are minor differences in the interrupts and memory mapping
On Sun, Jul 24, 2005 at 05:43:34AM +0200, Erik Trulsson wrote:
On Sat, Jul 23, 2005 at 09:01:36PM -0500, Karl Denninger wrote:
Done.
Note that the Bustek and Adaptec cards which exhibit the problem BOTH
identify the same (on two different machines) as SII 3112 boards, and
BOTH fail.
At 12:00 AM 24/07/2005, Karl Denninger wrote:
Finally, any pointers on a 2 port PCI SATA board that (1) is KNOWN to
work, (2) has EXTERNAL SATA connections, and (3) isn't one of those
whiz-bang all-in-one-RAID thingies that costs $500?
3ware makes an excellent 2 port SATA card (8000 series)
Karl Denninger wrote:
As I pointed out in my PR, make -j4 buildworld is more than sufficient
to demonstrate the problem.
( ... )
I'll pull over 6.0-BETA1, rebuild the array (that is the time-consuming
part of this test - takes 6-8 hours for the rebuild to run) and see if it
fails during a
It is definitely NOT fixed in 6.0-BETA1
Within SECONDS of starting a buildworld after the provider rebuild
completed, I got this...
GEOM_MIRROR: Device boot: provider ad4s1 detected.
GEOM_MIRROR: Device boot: rebuilding provider ad4s1.
GEOM_MIRROR: Device boot: provider ad6s1 detected.
On Fri, Jul 22, 2005 at 02:40:09PM -0500, Karl Denninger wrote:
It is definitely NOT fixed in 6.0-BETA1
Within SECONDS of starting a buildworld after the provider rebuild
completed, I got this...
GEOM_MIRROR: Device boot: provider ad4s1 detected.
GEOM_MIRROR: Device boot: rebuilding
On Fri, Jul 22, 2005 at 02:53:57PM -0500, Karl Denninger wrote:
[...]
Note carefully from this that there is NO ERROR INDICATION AS TO WHY THE
DISK DETACHED!
At least with the 5.x problems you'd SEE an error before it went BOOM.
This time around, nope - just death.
What's worse, the
On Fri, Jul 22, 2005 at 07:53:00PM -0700, Danny Howard wrote:
On Fri, Jul 22, 2005 at 02:53:57PM -0500, Karl Denninger wrote:
[...]
Note carefully from this that there is NO ERROR INDICATION AS TO WHY THE
DISK DETACHED!
At least with the 5.x problems you'd SEE an error before it went
23 matches
Mail list logo
