Christian wrote:
On Sunday 18 March 2007 06:43:09 you wrote:
Christian wrote:
This does indeed look like a drive side issue to me (the controller is
reporting CPBs with response flags 2 which as far as I can tell
indicates it's still waiting for the drive to complete the request).
Tejun Heo wrote:
Pablo Sebastian Greco wrote:
Tejun Heo wrote:
* Pablo, the bug you saw was bad interaction between blacklisted NCQ
device and dynamic queue depth adjustment. Patches are submitted to fix
the problem. Just drop the blacklist patch. Your drives should work
fine in NCQ
Tejun Heo wrote:
* Pablo, the bug you saw was bad interaction between blacklisted NCQ
device and dynamic queue depth adjustment. Patches are submitted to fix
the problem. Just drop the blacklist patch. Your drives should work
fine in NCQ mode. My gut feeling is that your problem is power rela
help
by providing debug data?
Thanks,
Marcus
On 1/23/07, Tejun Heo <[EMAIL PROTECTED]> wrote:
Pablo Sebastian Greco wrote:
> Well, it took me a few days, but I think I'm ready to report back.
One
> of the drives was failing, and it stopped after rewiring power
supply so
> th
Arjan van de Ven wrote:
Pablo Sebastian Greco wrote:
2296:427426436 134563009 PCI-MSI-edge
eth1
2297:252252 135926471257 PCI-MSI-edge
eth0
this suggests that cores would be busy rather than only one
-
Yes, but you are
Arjan van de Ven wrote:
Marc Donner wrote:
see http://www.irqbalance.org to get irqbalance
I now have tried irqloadbalance, but the same problem.
can you send me the output of
cat /proc/interrupts
(taken when you are or have been loading the network)
maybe there's something fishy going
Tejun Heo wrote:
Hello, Pablo.
Please apply common hardware debugging method. You know, swap drives.
Use separate power supply for disks, swap cables, etc...
It seems more like a hardware problem at this point.
Thanks.
Well, it took me a few days, but I think I'm ready to report back. On
Pablo Sebastian Greco wrote:
Tejun Heo wrote:
Pablo Sebastian Greco wrote:
After an uptime of 13:34 under heavy load and no errors, I'm pretty
sure your patch is correct. Is there a way to backport this to
2.6.18.x?
I forgot this (even though I implemented it) but you can tur
Tejun Heo wrote:
Pablo Sebastian Greco wrote:
After an uptime of 13:34 under heavy load and no errors, I'm pretty
sure your patch is correct. Is there a way to backport this to 2.6.18.x?
I forgot this (even though I implemented it) but you can turn off NCQ by
doing the foll
Pablo Sebastian Greco wrote:
Tejun Heo wrote:
Pablo Sebastian Greco wrote:
By crash I mean the whole system going down, having to reset the entire
machine.
I'm sending you 4 files:
dmesg: current boot dmesg, just a boot, because no errors appeared
after
last crash, since the server i
Tejun Heo wrote:
Pablo Sebastian Greco wrote:
By crash I mean the whole system going down, having to reset the entire
machine.
I'm sending you 4 files:
dmesg: current boot dmesg, just a boot, because no errors appeared after
last crash, since the server is out of production right now (e
First of all, thanks for everything, and my excuses if I'm doing
anything wrong, this is my first lkml mail, but I've read all the faq,
so should be OK.
This is the machine with the problem:
Intel ServerBoard S5000VSA
Dual Core Xeon 2.66 (Intel(R) Xeon(TM) CPU 2.66GHz stepping 04)
4G Kingston
1
12 matches
Mail list logo
