Hi, all!
On Mon, Aug 21, 2006 at 04:03:47AM +0200, Konstantin Saurbier wrote:
This errors are not driver or OS dependent such as they appear on
FreeBSD as well on different Linux distros.
Since not all controllers suffering of these errors it is maybe
depending on the firmware or
On Mon, Aug 21, 2006 at 09:10:53AM +0200, Patrick M. Hausen wrote:
Hi, all!
On Mon, Aug 21, 2006 at 04:03:47AM +0200, Konstantin Saurbier wrote:
This errors are not driver or OS dependent such as they appear on
FreeBSD as well on different Linux distros.
Since not all
Hi!
Am 21.08.2006 um 09:10 schrieb Patrick M. Hausen:
Hi, all!
On Mon, Aug 21, 2006 at 04:03:47AM +0200, Konstantin Saurbier wrote:
This errors are not driver or OS dependent such as they appear on
FreeBSD as well on different Linux distros.
Since not all controllers suffering of these
Hi, all!
On Mon, Aug 21, 2006 at 04:22:06PM +0900, Pyun YongHyeon wrote:
Several users reported em(4) watchdog errors but I couldn't reproduce
it on my system. A blind patch posted to net ML and I'd like to hear
success/failure report.
See
On Mon, Aug 21, 2006 at 04:03:47AM +0200, Konstantin Saurbier wrote:
Am 20.08.2006 um 18:20 schrieb Greg Byshenk:
What is different is that this was with a 3Ware RAID controller --
which made removing/raconfiguring/rebuilding much easier -- but I was
seeing the exact same errors.
No your
Hi!
On Sun, Aug 20, 2006 at 01:38:55PM +0100, Matt Dawson wrote:
I can confirm the same behaviour with a ULi M1689/Newcastle Athlon64 based
system running 6.1-RELEASE-p3 (i386). ad6 just detaches without warning and
it takes a reboot to bring it back. atacontrol reinit has no effect. Tried
On Monday 21 August 2006 13:00, [EMAIL PROTECTED] wrote:
I can confirm the same behaviour with a ULi M1689/Newcastle Athlon64
based system running 6.1-RELEASE-p3 (i386). ad6 just detaches without
warning and it takes a reboot to bring it back. atacontrol reinit has no
effect. Tried the
On Monday 21 August 2006 22:44, Matt Dawson wrote:
atacontrol detach ata3; atacontrol attach ata3 did.
Yes, that is the method for a controlled remove and reattach, a la hotplug
SATA. AIUI, though, if the drive goes AWOL on its own you need to reinit
the channel before issuing an atacontrol
Hello!
On Mon, Aug 21, 2006 at 02:14:16PM +0100, Matt Dawson wrote:
FWIW, the problem takes *far* longer to rear its head when the SATA
controller
has a PCI INT and IRQ to itself. Put a NIC onto a shared slot (a very Bad
Thing [TM] as the BIOS simply maps the INT to a single IRQ and both
Patrick M. Hausen wrote:
Hello!
On Mon, Aug 21, 2006 at 02:14:16PM +0100, Matt Dawson wrote:
FWIW, the problem takes *far* longer to rear its head when the SATA controller
has a PCI INT and IRQ to itself. Put a NIC onto a shared slot (a very Bad
Thing [TM] as the BIOS simply maps the INT to
Patrick M. Hausen wrote:
Hello!
On Mon, Aug 21, 2006 at 02:14:16PM +0100, Matt Dawson wrote:
FWIW, the problem takes *far* longer to rear its head when the SATA controller
has a PCI INT and IRQ to itself. Put a NIC onto a shared slot (a very Bad
Thing [TM] as the BIOS simply maps the INT to
Hi, Dominic!
On Mon, Aug 21, 2006 at 02:40:17PM +0100, Dominic Marks wrote:
hw.pci3.13.INTA.irq=17
The `13' value is the device number, you can find this in dmesg, same
for pciN.
So I tried this:
em1: Intel(R) PRO/1000 Network Connection Version - 6.0.5 port 0x5000-0x501f
mem
Patrick M. Hausen wrote:
Hi, Dominic!
On Mon, Aug 21, 2006 at 02:40:17PM +0100, Dominic Marks wrote:
hw.pci3.13.INTA.irq=17
The `13' value is the device number, you can find this in dmesg, same
for pciN.
So I tried this:
em1: Intel(R) PRO/1000 Network Connection Version - 6.0.5 port
Matt Dawson wrote:
On Monday 21 August 2006 13:00, [EMAIL PROTECTED] wrote:
I can confirm the same behaviour with a ULi M1689/Newcastle Athlon64
based system running 6.1-RELEASE-p3 (i386). ad6 just detaches without
warning and it takes a reboot to bring it back. atacontrol reinit has no
On Monday 21 August 2006 23:08, Dominic Marks wrote:
You can use device.hints(5) to do this.
I have the following in mine to force a RAID card and Sound card to
share IRQ 17.
You need to modify it to suit your environment.
hw.pci3.13.INTA.irq=17
The `13' value is the device number, you
Igor Robul wrote:
On Sat, Aug 19, 2006 at 04:39:55PM +0200, Miroslav Lachman wrote:
I upgraded to RELENG_6, changed all HW (whole servers and changed
Seagate HHDs to Samsung so every piece of HW is different from time of
my first post), but after one week I got the same error and system
On Sunday 20 August 2006 13:00, [EMAIL PROTECTED] wrote:
Do you mean different type of cables, or just another piece? I can't
change cables by myself, servers are dedicated from provider, but as I
can saw, they picked whole new machine from their HW storage and put new
Samsung disk drives in.
On Sun, Aug 20, 2006 at 01:38:55PM +0100, Matt Dawson wrote:
On Sunday 20 August 2006 13:00, [EMAIL PROTECTED] wrote:
Do you mean different type of cables, or just another piece? I can't
change cables by myself, servers are dedicated from provider, but as I
can saw, they picked whole new
Greg Byshenk wrote:
[...]
I am not sure if it is related, but... I experienced a similar sort of
problem, although the details in my case are quite different.
What was similar was that I would lose two ATA drives from an array,
inexplicably. Reconfiguring the same drives and rebuilding would
On Sun, Aug 20, 2006 at 07:51:29PM +0200, Miroslav Lachman wrote:
Greg Byshenk wrote:
[...]
This happened four times (with the same errors that have been discussed
here), running 6.1 STABLE as of June 22. Before attempting to RMA the
drives, I tried an updated kernel, 6.1 STABLE as of July
Hello!
On Sat, 19 Aug 2006, Miroslav Lachman wrote:
Aug 19 15:11:20 track ntpd[456]: kernel time sync enabled 2001
Aug 19 15:15:47 track kernel: ad6: FAILURE - device detached
Aug 19 15:15:47 track kernel: subdisk6: detached
Aug 19 15:15:47 track kernel: ad6: detached
I think that's a
Greg Byshenk wrote:
On Sun, Aug 20, 2006 at 07:51:29PM +0200, Miroslav Lachman wrote:
Greg Byshenk wrote:
[...]
This happened four times (with the same errors that have been discussed
here), running 6.1 STABLE as of June 22. Before attempting to RMA the
drives, I tried an updated kernel,
Miroslav Lachman wrote:
I upgraded to RELENG_6, changed all HW (whole servers and changed
Seagate HHDs to Samsung so every piece of HW is different from time of
my first post), but after one week I got the same error and system
reboot today:
Aug 19 15:11:20 track ntpd[456]: kernel time sync
Am 20.08.2006 um 18:20 schrieb Greg Byshenk:
On Sun, Aug 20, 2006 at 01:38:55PM +0100, Matt Dawson wrote:
On Sunday 20 August 2006 13:00, [EMAIL PROTECTED]
wrote:
Do you mean different type of cables, or just another piece? I can't
change cables by myself, servers are dedicated from
Johan Ström wrote:
[...]
Usually when the box has been rebooted before the failed component has
been rebuilt automaticly.. Solved with:
$ gmirror forget
$ gmirror insert gm0s1 ad4s1
And now its rebuilding ad4 again...
Any new hints? Should i try RELENG_6 instead?
I upgraded to RELENG_6,
On Sat, Aug 19, 2006 at 04:39:55PM +0200, Miroslav Lachman wrote:
I upgraded to RELENG_6, changed all HW (whole servers and changed
Seagate HHDs to Samsung so every piece of HW is different from time of
my first post), but after one week I got the same error and system
Just a try - have you
26 matches
Mail list logo
