Hi,
I've just attempted to consolidate two computers into one, putting a Silicon
Image SiI 3124 4 port eSATA controller (1095:3124) into my existing MythTV
backend (a Dell Dimension 3100), which has a Hauppauge PVR-350 (4444:0803)
in it.
The eSATA controller has 4 SATA drives attached to it, in a RAID-10
configuration, with LVM on top (hosting a JFS filesystem in a logical volume
if it makes a difference).
The problem I have is that the kernel has been panicking left and right
since I did this.
After a lot of swearing, and trial and error, I've narrowed down the crux of
the problem:
If I load the IVTV firmware, and am doing any sort of serious I/O on any of
the eSATA-connected drives, the kernel will panic (in what seems to be weird
and wonderful ways).
The ways I've been synthesizing I/O have been to just dd one of the disks to
/dev/null, or to get mdadm to do a RAID check (echo check >
/sys/block/md0/md/sync_action)
The way I've been triggering a firmware load is to just cat /dev/video0 out
to /dev/null
I can be exercising the disks happily, up until I trigger the firmware to
load, and then BOOM, it panics.
I've tried totally unloading the sata_sil24 driver, loading the firmware,
and the reloading sata_sil24, with the same results, so I don't believe it's
an ordering thing(yes, I've seen
http://ivtvdriver.org/index.php/Firmware#warning:_SCSI_devicename_collisions,
and I'm not sure this is still relevant, but I figure that unloading
sata_sil24 and loading the firmware, then loading sata_sil24 again should do
the trick). I've also tried completely unloading both ivtv and sata_sil24,
and reloading sata_sil24 first, then ivtv and the firmware. Same deal.
I've got some partial camera photos of some of the panics at
http://www.andrew.net.au/~apollock/ivtv+sii=oops/ and if it'll help at all,
I can do the requisite hoop jumping to try and get a higher-resolution
display attached and hopefully capture the entire back trace.
I've experienced this with 2.6.26 and 2.6.32, and a home-rolled 2.6.36 (I
tried to use kexec/kdump to get a dump, but the kdump kernel panicked for
some reason).
I've also tried disabling hyperthreading (by shutting down the second CPU).
Any thoughts, or assistance would be greatly appreciated.
regards
Andrew
_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users
I've just attempted to consolidate two computers into one, putting a Silicon
Image SiI 3124 4 port eSATA controller (1095:3124) into my existing MythTV
backend (a Dell Dimension 3100), which has a Hauppauge PVR-350 (4444:0803)
in it.
The eSATA controller has 4 SATA drives attached to it, in a RAID-10
configuration, with LVM on top (hosting a JFS filesystem in a logical volume
if it makes a difference).
The problem I have is that the kernel has been panicking left and right
since I did this.
After a lot of swearing, and trial and error, I've narrowed down the crux of
the problem:
If I load the IVTV firmware, and am doing any sort of serious I/O on any of
the eSATA-connected drives, the kernel will panic (in what seems to be weird
and wonderful ways).
The ways I've been synthesizing I/O have been to just dd one of the disks to
/dev/null, or to get mdadm to do a RAID check (echo check >
/sys/block/md0/md/sync_action)
The way I've been triggering a firmware load is to just cat /dev/video0 out
to /dev/null
I can be exercising the disks happily, up until I trigger the firmware to
load, and then BOOM, it panics.
I've tried totally unloading the sata_sil24 driver, loading the firmware,
and the reloading sata_sil24, with the same results, so I don't believe it's
an ordering thing(yes, I've seen
http://ivtvdriver.org/index.php/Firmware#warning:_SCSI_devicename_collisions,
and I'm not sure this is still relevant, but I figure that unloading
sata_sil24 and loading the firmware, then loading sata_sil24 again should do
the trick). I've also tried completely unloading both ivtv and sata_sil24,
and reloading sata_sil24 first, then ivtv and the firmware. Same deal.
I've got some partial camera photos of some of the panics at
http://www.andrew.net.au/~apollock/ivtv+sii=oops/ and if it'll help at all,
I can do the requisite hoop jumping to try and get a higher-resolution
display attached and hopefully capture the entire back trace.
I've experienced this with 2.6.26 and 2.6.32, and a home-rolled 2.6.36 (I
tried to use kexec/kdump to get a dump, but the kdump kernel panicked for
some reason).
I've also tried disabling hyperthreading (by shutting down the second CPU).
Any thoughts, or assistance would be greatly appreciated.
regards
Andrew
_______________________________________________
ivtv-users mailing list
ivtv-users@ivtvdriver.org
http://ivtvdriver.org/mailman/listinfo/ivtv-users