Prev: I2C driver of Topcliff PCH
Next: Don't apply for write lock on tasklist_lock if parent doesn't ptrace other processes
From: Pierre Ossman on 15 Jul 2010 15:50
On Thu, 20 May 2010 18:28:52 +0200
Pierre Ossman <pierre-list(a)ossman.eu> wrote:

>
> Controller now taken out of the picture and I no longer see any errors
> on either filesystem nor direct disk level.
>
> I have a sil3132 of a different OEM brand here. I'll try that in that
> pci-e slot next.
>

Status update:

1. Putting the other sil3132 controller did not make any problems
appear.

2. Next I swapped that controller with the one next to it to test if
this specific board design in combination with this specific slot was
causing the issues. Still no corruption.

3. Today I put the "bad" controller back in, but in a different slot.
Still not seeing any issues.

I could move it back to the inital slot to see if the problem
reappears, but I'm just happy the system is error free again so I'll
write this off as a temporary glitch or a bad combination of card and
slot.

Rgds
--
-- Pierre Ossman

WARNING: This correspondence is being monitored by FRA, a
Swedish intelligence agency. Make sure your server uses
encryption for SMTP traffic and consider using PGP for
end-to-end encryption.
 | 
Pages: 1
Prev: I2C driver of Topcliff PCH
Next: Don't apply for write lock on tasklist_lock if parent doesn't ptrace other processes