https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c1 --- Comment #1 from pgnet _ 2009-01-07 09:15:30 MST --- forgot to mention, the above scenario already includes a changed, grep INITRD_MODULES /etc/sysconfig/kernel #INITRD_MODULES="processor thermal sata_nv pata_amd fan jbd ext3 raid1 dm_mod edd" INITRD_MODULES="sata_sil24 processor thermal sata_nv pata_amd fan jbd ext3 raid1 dm_mod edd" and a subsequent mkinitrd -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c2 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |pgnet.trash@gmail.com --- Comment #2 from Tejun Heo 2009-01-12 20:15:58 MST --- Can you please attach /var/log/boot.msg? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c4 --- Comment #4 from pgnet _ 2009-01-12 21:49:49 MST --- Created an attachment (id=264673) --> (https://bugzilla.novell.com/attachment.cgi?id=264673) serial console output @ crash, with sata_sil24 card & attached drives (In reply to comment #2)

Can you please attach /var/log/boot.msg?

Dealing with other Novell issues, I was convinced to upgrade to Opensuse 11.1. OS 11.1 with the SATA card installed, but the attached drive array turned off, boots just fine, as it did before, into either kernel-default or kernel-xen. However, now, with the drives powered up, won't boot -- but crashes. So, I can't, atm, get you your requested /var/log/boot.msg. I _have_ attached (console.txt) serial console output which, I hope, may provide you the info you need ... ? I'll also check 'irqpoll' in a few minutes here ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c6 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|pgnet.trash@gmail.com | --- Comment #6 from Tejun Heo 2009-01-13 20:41:01 MST --- Hmm... the oops probably is a separate issue. Does specifying "libata.force=1.5Gbps" make any difference? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c7 pgnet _ changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW --- Comment #7 from pgnet _ 2009-01-13 21:21:49 MST --- Created an attachment (id=264924) --> (https://bugzilla.novell.com/attachment.cgi?id=264924) console crash output with addition of libata.force=1.5Gps Since last efforts, I've DL'd Win7 beta (not my favorite, btw!) to check & update as required all BIOS, etc. Motherboard BIOS was upgraded, SATA card didn't need it. That given, per your request, booting to, title openSUSE_11_1 CONSOLE root (hd0,0) kernel /vmlinuz root=/dev/VG_Dom0/LV_ROOT resume=/dev/md1 \ showopts elevator=cfq iommu=soft irqpoll libata.force=1.5Gbps \ vga=0x31a console=tty0 console=ttyS0,57600n8 initrd /initrd I get a crash (attached ...). Hrm. I thought the irpoll fixed that ... will remove and try again, just for check. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c9 --- Comment #9 from Tejun Heo 2009-01-13 21:48:40 MST --- Does the controller and hard drive work properly under windows? Your two crash logs are completely different and it seems to indicate hardware problem. Can you please trigger the crash several times and try to see whether those are actually related to the parameter you're specifying or they were just coincidental. Also, please capture each crash. Let's try to find some pattern. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c10 --- Comment #10 from pgnet _ 2009-01-13 21:59:57 MST ---

Does the controller and hard drive work properly under windows?

Yes. Perfectly. I was able to create partitions on the individual drives, &/or create RAID arrays, and partition at will. The I was able to install different versions of the Windows drivers, and -- presuming that there's some sort of checking when you do so -- received no errors/warnings, and was able to repeat all functions at will. The gParted disks also allow be to partition at will (though, afaict, no raid capability). I test that capability by partitioning in gParted as NTFS/FAT and then accessing in Win7. No problems experienced.

Your two crash logs are completely different and it seems to indicate hardware problem.

Can you please trigger the crash several times and try to see whether those are actually related to the parameter you're specifying or they were just coincidental. Also, please capture each crash. Let's try to find some

I had not thought to compare ... :-/ Though, the differences *may* be on 'either side' of updates to the Mobo BIOS , the migrate from Opensuse 11.0 -> 11.1, or monkeying with loaded modules, etc. pattern. I'll repeat a number of crashes, changing nothing in the interim, capture each console output, and zip into an attachment. Back asap. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c12 pgnet _ changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|pgnet.trash@gmail.com | --- Comment #12 from pgnet _ 2009-01-13 22:51:13 MST --- . -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c14 --- Comment #14 from pgnet _ 2009-01-14 08:58:38 MST --- Created an attachment (id=265042) --> (https://bugzilla.novell.com/attachment.cgi?id=265042) console etc output with mem=3G adding mem=3G to kernel options, boots to kernel-default & kernel-xen both complete, no crash kernel-default case: PCI-attached drives appear, and can be accessed via fdisk & partitioner kernel-xen case: drives, again, not available -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c15 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trenn@novell.com --- Comment #15 from Tejun Heo 2009-01-14 19:26:37 MST --- Let's concentrate on kernel-default first. Something is wrong with 64bit DMA support on that machine. I'm quite sure that 64bit DMA support on sil24 controller is fine, so it's very likely that your PCI or host bridge can't handle 64bit DMA and thus corrupts data left and right when it happens. cc'ing Thomas. Thomas, sorry to bother you but do you happen to know who should I be bugging for possible chipset bugs? It seems we'll need to blacklist this chipset for 64bit DMA. pgnet_, can you please post the output of "lspci -nn"? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c17 --- Comment #17 from Tejun Heo 2009-01-14 20:52:56 MST --- mem=4G should work too. I just wanted to be on the safe side. Your pci/host bridge is either dropping data w/ 64bit address thrown at it by the controller or, more in much more scary scenario, writing it to some random place (most likely with upper 32bit of address clipped). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c19 --- Comment #19 from pgnet _ 2009-01-14 21:29:15 MST ---

mem=4G should work too

just fyi, it does. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c21 --- Comment #21 from Tejun Heo 2009-01-14 22:30:19 MST --- Heh... you'll get to keep your hardware. :-) It just means marking the bridge as incapable of 64bit DMA. The kernel will fall back to iommu. The performance hit shouldn't noticeable in most cases. Windows probably is already using iommu. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c23 --- Comment #23 from Tejun Heo 2009-01-14 23:40:03 MST --- Most likely the mobo. No, for 64bit capable controllers, iommu is not used as the controller can directly address all the memories. Does iommu=force work? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c25 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gregkh@novell.com, | |rjw@novell.com --- Comment #25 from Tejun Heo 2009-01-15 22:57:23 MST --- cc'ing Rafael and Greg. Can one of you guys take over here? It seems the chipset needs to be quirked. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c29 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |pgnet.trash@gmail.com --- Comment #29 from Tejun Heo 2009-01-21 06:11:43 MST --- pgnet_ can you please post the output of "lspci -nnvvvxxx"? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c31 --- Comment #31 from pgnet _ 2009-02-02 11:50:02 MST --- have there perchance been any updates/commits on this? none that i can see in RELEASE branch, but, perhaps in Factory? elsewhere? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c33 --- Comment #33 from pgnet _ 2009-02-05 08:19:56 MST --- the mobo's already @ the latest bios, v5.8 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c35 --- Comment #35 from pgnet _ 2009-02-05 09:33:51 MST --- @ install, setenv VER "2.6.27.14-bug463829_dbg0_d49a1108" rpm -i kernel-default-base-${VER}.x86_64.rpm kernel-default-${VER}.x86_64.rpm Kernel image: /boot/vmlinuz-2.6.27.14-bug463829_dbg0_d49a1108-default Initrd image: /boot/initrd-2.6.27.14-bug463829_dbg0_d49a1108-default Root device: /dev/VG_Dom0/LV_ROOT (mounted on / as ext3) Resume device: /dev/VG_Swap/LV_SWAP Device md3 not handled Script /lib/mkinitrd/setup/72-block.sh failed! Setting up /lib/modules/2.6.27.14-bug463829_dbg0_d49a1108-default Kernel image: /boot/vmlinuz-2.6.27.14-bug463829_dbg0_d49a1108-default Initrd image: /boot/initrd-2.6.27.14-bug463829_dbg0_d49a1108-default Root device: /dev/VG_Dom0/LV_ROOT (mounted on / as ext3) Resume device: /dev/VG_Swap/LV_SWAP Device md3 not handled Script /lib/mkinitrd/setup/72-block.sh failed! b4 proceeding, are these: Device md3 not handled Script /lib/mkinitrd/setup/72-block.sh failed! a concern that 1st needs to be addressed ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c37 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |pgnet.trash@gmail.com --- Comment #37 from Tejun Heo 2009-02-05 18:32:44 MST --- Hmm... have no idea what went wrong with the initial mkinitrd, strange. Anyways, can you please verify that the drives are actually functional? Make a fs, copy files, run md5sum on them, etc.. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c39 --- Comment #39 from pgnet _ 2009-02-05 23:05:59 MST --- Created an attachment (id=270674) --> (https://bugzilla.novell.com/attachment.cgi?id=270674) console output of subsequent failure to boot well ... despite working seemingly OK, the box hangs at subsequent reboot. relevant serial console output is attached. only way to get back to a prompt is single-user boot, and remove the /etc/fstab mount entries for the sata_sil24 attached devices. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User fifachen@sina.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c41 --- Comment #41 from peer chen 2009-02-09 02:52:02 MST --- We found the related bug in database and wrong BIOS setting cause this issue. Please blacklist this model platform and use software iommu for 4g above DMA access since the latest BIOS also have same problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c43 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|teheo@novell.com |pgnet.trash@gmail.com --- Comment #43 from Tejun Heo 2009-02-09 22:02:36 MST --- Peer Chen, thanks for verifying but the problem is that the debug kernel disables DAC (64bit DMA) on the board and pgnet_ is still seeing data corruption. Maybe something wrong with GART IOMMU too? pgnet_, can you please try "iommu=soft"? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c45 pgnet _ changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|pgnet.trash@gmail.com | --- Comment #45 from pgnet _ 2009-02-10 00:24:12 MST --- with, iommu=soft the results are the same as documented in the attachment above "exercise' of sata_sil24 attached drives with debug kernel" https://bugzilla.novell.com/attachment.cgi?id=270674 everything works with the attached drives -- intially @ reboot with mounts in /etc/fstab, failed boot/crash until /etc/fstab entries are removed. then, not trace of the VGs i created on the drives. let me know if its worthwhile trying different kernel options at this point. thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c47 pgnet _ changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|pgnet.trash@gmail.com | --- Comment #47 from pgnet _ 2009-02-10 11:07:07 MST --- Created an attachment (id=271618) --> (https://bugzilla.novell.com/attachment.cgi?id=271618) tests of iommu= settings with kernel-default & kernel-bug... these results, using 'simpler' format & test, are different & confusing ... kernel-default + iommu=soft -> NO DISKS kernel-default + iommu=force -> OK kernel-bug... + iommu=force -> OK kernel-bug... + iommu=soft -> OK kernel-default + (NO iommu=...) -> kernel OOPS could the reformat using gParted have 'cleared up' some disk corruption that cfdisk might have missed? next? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c49 --- Comment #49 from pgnet _ 2009-02-10 12:22:23 MST --- Created an attachment (id=271652) --> (https://bugzilla.novell.com/attachment.cgi?id=271652) test RAID array creation on attached drives w/ kernel-debug+iommu=soft i'm able to boot to kernel-debug+iommu=soft, with /etc/fstab mounts defined. but, attempt to create RAID-1 array across attached drives fails with: mdadm: device /dev/sda1 not suitable for any style of array -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c51 pgnet _ changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|pgnet.trash@gmail.com | --- Comment #51 from pgnet _ 2009-02-10 20:27:45 MST --- 1. Boot kernel to test. No fstab entry or raid array. cat /etc/fstab | grep /dev/sd -> (empty) cat /proc/mdstat | egrep "sda|sdb" -> (empty) reboot (kernel opts: splash=silent showopts vga=0x31a console=tty0 console=ttyS0,57600n8) ... uname -ri 2.6.27.14-bug463829_dbg0_d49a1108-default x86_64

Please make sure the device to test is not used by any FS before doing the test. umount /dev/sda umount: /dev/sda: not mounted

2. dd if=testA.iso of=TESTTMPFILE bs=1M count=512 3. sha1sum TESTTMPFILE 0c9887a542db36a6f122f1f9f7a6ae1049e661ef TESTTMPFILE 4. dd if=TESTTMPFILE of=/dev/sda bs=1M count=512 512+0 records in 512+0 records out 536870912 bytes (537 MB) copied, 21.6985 s, 24.7 MB/s 5. for ((i=0;i<3;i++)); do dd if=/dev/sda of=TESTOUT bs=1M count=512; sha1sum TESTOUT; done 512+0 records in 512+0 records out 536870912 bytes (537 MB) copied, 9.23539 s, 58.1 MB/s 0c9887a542db36a6f122f1f9f7a6ae1049e661ef TESTOUT 512+0 records in 512+0 records out 536870912 bytes (537 MB) copied, 8.19274 s, 65.5 MB/s 0c9887a542db36a6f122f1f9f7a6ae1049e661ef TESTOUT 512+0 records in 512+0 records out 536870912 bytes (537 MB) copied, 9.90022 s, 54.2 MB/s 0c9887a542db36a6f122f1f9f7a6ae1049e661ef TESTOUT -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c53 pgnet _ changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|pgnet.trash@gmail.com | --- Comment #53 from pgnet _ 2009-02-11 09:54:17 MST --- (In reply to comment #52)

Thanks, and after reboot, you still get the same values when you repeat only the reading and checksumming part of the test?

apparently, yes. @ previous test, sha1sum TESTOUT 0c9887a542db36a6f122f1f9f7a6ae1049e661ef TESTOUT checking, uname -ri 2.6.27.14-bug463829_dbg0_d49a1108-default x86_64 reboot ... for ((i=0;i<3;i++)); do dd if=/dev/sda of=TESTOUT bs=1M count=512; sha1sum TESTOUT; done 512+0 records in 512+0 records out 536870912 bytes (537 MB) copied, 11.176 s, 48.0 MB/s 0c9887a542db36a6f122f1f9f7a6ae1049e661ef TESTOUT 512+0 records in 512+0 records out 536870912 bytes (537 MB) copied, 2.8667 s, 187 MB/s 0c9887a542db36a6f122f1f9f7a6ae1049e661ef TESTOUT 512+0 records in 512+0 records out 536870912 bytes (537 MB) copied, 3.58828 s, 150 MB/s 0c9887a542db36a6f122f1f9f7a6ae1049e661ef TESTOUT

If so, can you please try again with something larger than 4G?

re-do, with > 4GB dd if=/dev/urandom of=TESTTMPFILE bs=1M count=5120 5120+0 records in 5120+0 records out 5368709120 bytes (5.4 GB) copied, 1045.78 s, 5.1 MB/s sha1sum TESTTMPFILE 06be6cd14f9ff6555da2bd8573d9e56f292330a3 TESTTMPFILE dd if=TESTTMPFILE of=/dev/sda bs=1M count=5120 5120+0 records in 5120+0 records out 5368709120 bytes (5.4 GB) copied, 168.142 s, 31.9 MB/s for ((i=0;i<3;i++)); do dd if=/dev/sda of=TESTOUT bs=1M count=5120; sha1sum TESTOUT; done 5120+0 records in 5120+0 records out 5368709120 bytes (5.4 GB) copied, 79.4242 s, 67.6 MB/s 06be6cd14f9ff6555da2bd8573d9e56f292330a3 TESTOUT 5120+0 records in 5120+0 records out 5368709120 bytes (5.4 GB) copied, 85.0126 s, 63.2 MB/s 06be6cd14f9ff6555da2bd8573d9e56f292330a3 TESTOUT 5120+0 records in 5120+0 records out 5368709120 bytes (5.4 GB) copied, 76.8508 s, 69.9 MB/s 06be6cd14f9ff6555da2bd8573d9e56f292330a3 TESTOUT reboot ... for ((i=0;i<3;i++)); do dd if=/dev/sda of=TESTOUT bs=1M count=5120; sha1sum TESTOUT; done 5120+0 records in 5120+0 records out 5368709120 bytes (5.4 GB) copied, 92.8563 s, 57.8 MB/s 06be6cd14f9ff6555da2bd8573d9e56f292330a3 TESTOUT 5120+0 records in 5120+0 records out 5368709120 bytes (5.4 GB) copied, 91.8821 s, 58.4 MB/s 06be6cd14f9ff6555da2bd8573d9e56f292330a3 TESTOUT 5120+0 records in 5120+0 records out 5368709120 bytes (5.4 GB) copied, 82.8299 s, 64.8 MB/s 06be6cd14f9ff6555da2bd8573d9e56f292330a3 TESTOUT

It's really strange ...

!! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c55 pgnet _ changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|pgnet.trash@gmail.com | --- Comment #55 from pgnet _ 2009-02-12 09:45:03 MST --- cfdisk /dev/sda mkfs.ext3 -L EXTA /dev/sda1 mke2fs 1.41.1 (01-Sep-2008) Filesystem label=EXTA OS type: Linux ... mount /dev/sda1 /mnt/EXTA mount | grep sda /dev/sda1 on /mnt/EXTA type ext3 (rw) dd if=/dev/urandom of=TESTTMPFILE bs=1M count=5120 sha1sum TESTTMPFILE 35f9d84b37e215e212682863b53e7728ad0272d5 TESTTMPFILE cp TESTTMPFILE /mnt/EXTA/ sha1sum /mnt/EXTA/TESTTMPFILE 35f9d84b37e215e212682863b53e7728ad0272d5 /mnt/EXTA/TESTTMPFILE for ((i=0;i<3;i++)); do cp -f /mnt/EXTA/TESTTMPFILE TESTOUT; sha1sum TESTOUT; done 35f9d84b37e215e212682863b53e7728ad0272d5 TESTOUT 35f9d84b37e215e212682863b53e7728ad0272d5 TESTOUT 35f9d84b37e215e212682863b53e7728ad0272d5 TESTOUT reboot ... ?? server:/home/work # Write failed: Host is down .. mount /dev/sda1 /mnt/EXTA for ((i=0;i<3;i++)); do cp -f /mnt/EXTA/TESTTMPFILE TESTOUT; sha1sum TESTOUT; done 35f9d84b37e215e212682863b53e7728ad0272d5 TESTOUT 35f9d84b37e215e212682863b53e7728ad0272d5 TESTOUT 35f9d84b37e215e212682863b53e7728ad0272d5 TESTOUT -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c57 pgnet _ changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|pgnet.trash@gmail.com | --- Comment #57 from pgnet _ 2009-02-15 20:29:19 MST --- (In reply to comment #56)

pgnet_, thanks for verifying. I don't have much experience with lvm but as far as I can see the disk itself is now working properly. Can you please try the lvm again? I don't really see why it wouldn't work.

hi, here's the ext3-on-lvm scenario i think you want ... cfdisk /dev/sda -> Linux LVM pvcreate /dev/sda1 vgcreate -s 32 /dev/VGTEST /dev/sda1 lvcreate -n LVTEST -l 100%FREE /dev/VGTEST mkfs.ext3 -L EXTLVA /dev/VGTEST/LVTEST mke2fs 1.41.1 (01-Sep-2008) Filesystem label=EXTLVA OS type: Linux ... mount /dev/VGTEST/LVTEST /mnt/EXTLVA mount | grep LVTEST /dev/mapper/VGTEST-LVTEST on /mnt/EXTLVA type ext3 (rw) sha1sum TESTTMPFILE 35f9d84b37e215e212682863b53e7728ad0272d5 TESTTMPFILE cp TESTTMPFILE /mnt/EXTLVA/ sha1sum /mnt/EXTLVA/TESTTMPFILE 35f9d84b37e215e212682863b53e7728ad0272d5 /mnt/EXTLVA/TESTTMPFILE for ((i=0;i<3;i++)); do cp -f /mnt/EXTLVA/TESTTMPFILE TESTOUT; sha1sum TESTOUT; done 35f9d84b37e215e212682863b53e7728ad0272d5 TESTOUT 35f9d84b37e215e212682863b53e7728ad0272d5 TESTOUT 35f9d84b37e215e212682863b53e7728ad0272d5 TESTOUT reboot .. mount /dev/VGTEST/LVTEST /mnt/EXTLVA for ((i=0;i<3;i++)); do cp -f /mnt/EXTLVA/TESTTMPFILE TESTOUT; sha1sum TESTOUT; done 35f9d84b37e215e212682863b53e7728ad0272d5 TESTOUT 35f9d84b37e215e212682863b53e7728ad0272d5 TESTOUT 35f9d84b37e215e212682863b53e7728ad0272d5 TESTOUT -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c58 --- Comment #58 from Tejun Heo 2009-02-24 23:20:28 MST --- Sorry about the delay but it looks like it's working, or am I missing something? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c60 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|teheo@novell.com |pgnet.trash@gmail.com --- Comment #60 from Tejun Heo 2009-02-25 17:32:26 MST --- Yeap, seeing that raw partitions work just fine (have you been using them for the time being? Have you noticed anything?), dm/md/lvm should work just fine. Can you please try that? As for xen, if the default kernel is fixed, I think it will behave the same. There's nothing arch or vm specific. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c62 pgnet _ changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|pgnet.trash@gmail.com | --- Comment #62 from pgnet _ 2009-02-25 22:48:50 MST --- Created an attachment (id=275544) --> (https://bugzilla.novell.com/attachment.cgi?id=275544) test of debug kernel with FS on LVM on RAID_1 summary: boot to "debug" kernel-default; @ grub, root (hd0,0) kernel /vmlinuz-2.6.27.14-bug463829_dbg0_d49a1108-default root=/dev/VG_Dom0/LV_ROOT resume=/dev/VG_Swap/LV_SWAP splash=silent showopts vga=0x31a console=tty0 console=ttyS0,57600n8 initrd /initrd-2.6.27.14-bug463829_dbg0_d49a1108-default /dev/sda -> sda1, sda2 /dev/sdb -> sdb1, sdb2 /dev/md4 -> sda1 + sdb1 VG, LVM 100%, xfs /dev/md5 -> sda2 + sdb2 VG, LVM 66%, ext3 VG, LVM 33%, ext3 manual mount(s) multiple > 5GB file-system copies, sha1sums OK reboot manual mount(s) multiple > 5GB file-system copies, sha1sums OK mod /etc/fstab reboot mounts OK multiple > 5GB file-system copies, sha1sums OK looks good, with no kernel cmd_line mods required in grub. (question: really no "iommu=..." required/recommended ?) 'gory details' -> attachment ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c64 --- Comment #64 from pgnet _ 2009-02-26 08:29:50 MST --- (In reply to comment #63)

Yes, no iommu parameter necessary.

thanks for clarifying.

Can you please keep it running for a few days and see whether anything explodes?

that's going to be a challenge if not in xen ... overnight (but of course, not 'using' the drives) is doable. since yesterday, the two 'new' raid arrays have been 'RESYNCING' (that sure takes awhile!). /dev/md5 is 100% done; md4 is 74% done, atm. afaict, no errors.

I'm a bit worried because you previously reported lvm didn't work even with the patched kernel.

as am i. however, since earlier tests, i've: -- ensured i 'pvremove -ff' before 'pvcreate'. i've found that simply reformatting doesn't always (that's what's confusing ... seems to depend on where i stop/restart the manual procedures) clear all the info off the drive. if there's an errant pv around, that'll cause problems. -- made sure to _manually_ add the new raid arrays' UUIDs to mdadm.conf. "Partitioner" seems to do it automatically, but manually creating the arrays does not. without the mod, the raid arrays don't start and the lvms on the raid arrays are never recognized. i'm not sure whether there's a step in the manual process (mdadm ... ?) that _should_ do the mdadm.conf mods. :-/

Thanks.

you too. this has been a long thread -- not much help from me. your help's appreciated. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c66 --- Comment #66 from pgnet _ 2009-02-26 10:27:14 MST --- re: the fail to assemble the raid array @ bott without prior edit/add of mdadm.conf, @ http://www.mail-archive.com/linux-raid@vger.kernel.org/msg10641.html "If you have your disk/controller and md drivers built into the kernel, AND marked the partitions as "linux raid autodetect", kernel may assemble them right at boot. But I don't remember if the kernel will even consider v.1 superblocks for its auto- assembly. In any way, don't rely on the kernel to do this work, in-kernel assembly code is very simplistic and works up to a moment when anything changes/breaks. It's almost the same code as was in old raidtools..." per above, i _have_ marked those partitions (/dev/sd{a,b}{1,2}) as "linux raid autodetect", w/ cfdisk. the comments above seem to imply that under 'sufficient' conditions, the kernel may (can? will?) assemble the array correctly at boot. and, it seems that's _without_ prior manual edit of mdadm.conf. if that's true (is it?), then the question is why, with the debug kernel in-place, are those arrays NOT getting assembled without the mdadm.conf manual edit? is the info above wrong, are mdadm or kernel assembly not working in-general, or is it something in the debug kernel's implementation? thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c68 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|teheo@novell.com |pgnet.trash@gmail.com --- Comment #68 from Tejun Heo 2009-02-26 22:31:52 MST --- Okay, here's the xen kernel. http://htj.dyndns.org/export/testing/sl111-x86_64-xen-bug463829_dbg0/ As for the autodetection, md is not built into the kernel. You can trigger the auto scan manually tho. At any rate, using the yast storage tool to configure devices should do the right thing. And the patch of course is not in SL111 or SLE11 tree yet. It hasn't been verified to fix the problem. It will be included in the SL111 and SLE11 kernel when it's verified (will probably be released as part of kernel update). Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c70 --- Comment #70 from Tejun Heo 2009-02-26 23:01:06 MST --- Force upgrading it (-U --force) should work. It will replace the original kernel. Hmmm... not sure whether you can install it side-by-side tho. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c72 pgnet _ changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|teheo@novell.com |pgnet.trash@gmail.com --- Comment #72 from pgnet _ 2009-02-27 12:42:19 MST --- Created an attachment (id=276115) --> (https://bugzilla.novell.com/attachment.cgi?id=276115) serial console output comparing boot to -xen & -default debug kerns in the attached zip file, there's 2 txt files debug-default.txt debug-xen.txt containing snips from the console output for the OK-boot to kernel-default & FAIL'd-boot to kernel-xen, respectively. note the differences @ '1st encounter' with the attached sata_sil24 drives. something's clearly different -- is it likely a result of the kernel, or xen itslef? fyi, boot to distro's kernel-xen & kernel-default (i.e., without ext sata drives in use) is OK as well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c74 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |teheo@novell.com --- Comment #74 from Tejun Heo 2009-03-01 05:19:09 MST --- Eh... looks like irq routing problem. Have no idea whatsoever what's wrong with the xen build tho. I've never used xen before. Does irqpoll help? If not, can you please try to verify the original fix with the default kernel to a reasonable level (overnight stress test or something)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c76 --- Comment #76 from pgnet _ 2009-03-01 08:56:33 MST --- digging around, i've found "bonnie++", which looks like the right sort of 'stress'. i'll let bonnie++ -d /home/stor/BACKUPS/ -u pgn:users -x 512 run as the aformentioned stress test & report back. if there's a different test you'd suggest, let me know. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c78 --- Comment #78 from pgnet _ 2009-03-01 22:51:38 MST --- (In reply to comment #77)

bonnie++ is fine but it would be nice to have something which can verify data integrity in parallel. ie. repeatedly making n copies of a large file and checksumming them. Thanks.

no problem. added it in, and will let it crunch ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c80 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|teheo@novell.com |pgnet.trash@gmail.com --- Comment #80 from Tejun Heo 2009-03-02 17:18:13 MST --- Great, just in case, the file is larger than memory size, right? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c82 --- Comment #82 from Tejun Heo 2009-03-02 17:37:09 MST --- Yes, or you can just change the script such that the output files are first copied to T_OUT_$j and after all the copies are complete, sha1sum is run on each T_OUT files. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c84 --- Comment #84 from Tejun Heo 2009-03-02 18:01:45 MST --- Thanks. Regarding xen, I probably did something wrong while building it. If the -default kernel works fine with the patch, -xen should too. After checking the fix patch in, you can try the KOTD -xen kernel. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c86 --- Comment #86 from Tejun Heo 2009-03-02 18:33:18 MST --- (In reply to comment #85)

...

After checking the fix patch in,

check it in to where? i have no repository rights ...

or do you mean _you_ have checked something in?

Yeap, I meant me checking into SUSE kernel tree.

...

you can try the KOTD -xen kernel.

ok, that's "kernel of the day", it seems. where do those hide? nothing on Webpin ...

you don't mean these:

http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory

do you ?

sorry, some things are not (yet) obvious to us mere mortals

Sorry about not being clear. The following link actually. http://ftp.suse.com/pub/projects/kernel/kotd/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c88 pgnet _ changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|pgnet.trash@gmail.com | --- Comment #88 from pgnet _ 2009-03-03 09:13:15 MST --- fyi, overnight stress test, started @ ~ 7pm MST, 2009-03-02, no errors & checksums are all consistent ... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c90 --- Comment #90 from pgnet _ 2009-03-03 22:38:59 MST --- thanks! i'll subseqeuntly try out the -xen kernel, and report back with findings. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c92 pgnet _ changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #92 from pgnet _ 2009-03-04 17:47:16 MST --- reopening for comment, or redirect. (In reply to comment #84)

Regarding xen, I probably did something wrong while building it. If the -default kernel works fine with the patch, -xen should too.

I'm not so sure it's 'you' :-/ please read on ... (In reply to comment #91)

Patches committed to SLE11_BRANCH. Resolving as FIXED.

Please wait a day or two and try the SLE11_BRANCH kotd kernel for xen. Thanks.

------------------------------------------------------------------- Wed Mar 4 06:49:54 CET 2009 - teheo@suse.de

- patches.arch/x86-fix-nodac: x86: fix iommu=nodac parameter handling (bnc#463829). - patches.arch/x86-mcp51-no-dac: x86: disallow DAC for MCP51 PCI bridge (bnc#463829).

noting, rpm -qp --changelog $LOC/kernel-xen-base-${VER1}.x86_64.rpm ... * Wed Mar 04 2009 teheo@suse.de - patches.arch/x86-fix-nodac: x86: fix iommu=nodac parameter handling (bnc#463829). - patches.arch/x86-mcp51-no-dac: x86: disallow DAC for MCP51 PCI bridge (bnc#463829). ... and installing, rpm -qa | grep SLE11_BRANCH kernel-default-extra-2.6.27.19-SLE11_BRANCH_20090304073920_1eb029c9 kernel-default-2.6.27.19-SLE11_BRANCH_20090304073920_1eb029c9 kernel-xen-base-2.6.27.19-SLE11_BRANCH_20090304073920_1eb029c9 kernel-xen-extra-2.6.27.19-SLE11_BRANCH_20090304073920_1eb029c9 kernel-default-base-2.6.27.19-SLE11_BRANCH_20090304073920_1eb029c9 kernel-xen-2.6.27.19-SLE11_BRANCH_20090304073920_1eb029c9 booting to, ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 11.1 - 2.6.27.19-SLE11_BRANCH_20090304073920_1eb029c9 root (hd0,0) kernel /vmlinuz-2.6.27.19-SLE11_BRANCH_20090304073920_1eb029c9-default root=/dev/VG_Dom0/LV_ROOT resume=/dev/VG_Swap/LV_SWAP splash=silent showopts vga=0x31a console=tty0 console=ttyS0,57600n8 initrd /initrd-2.6.27.19-SLE11_BRANCH_20090304073920_1eb029c9-default is OK, uname -ri 2.6.27.19-SLE11_BRANCH_20090304073920_1eb029c9-default x86_64 and, the ext drive arrays are 'up', fdisk -l /dev/md4 /dev/md5 Disk /dev/md4: 650.0 GB, 650002580480 bytes 2 heads, 4 sectors/track, 158692036 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk identifier: 0x00000000 Disk /dev/md4 doesn't contain a valid partition table Disk /dev/md5: 350.1 GB, 350199382016 bytes 2 heads, 4 sectors/track, 85497896 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk identifier: 0x00000000 Disk /dev/md5 doesn't contain a valid partition table and, the LV's mounted, df -H | grep stor/ 650G 9.7G 641G 2% /home/stor/MEDIA 228G 9.9G 207G 5% /home/stor/BACKUPS 118G 9.9G 102G 9% /home/stor/DATA but, booting to the -xen variant, ###Don't change this comment - YaST2 identifier: Original name: xen### title Xen -- openSUSE 11.1 - 2.6.27.19-SLE11_BRANCH_20090304073920_1eb029c9 root (hd0,0) kernel /xen.gz dom0_mem=768M loglvl=all loglvl_guest=all vga=gfx-1280x1024x32 console=vga,com1 com1=57600,8n1 module /vmlinuz-2.6.27.19-SLE11_BRANCH_20090304073920_1eb029c9-xen root=/dev/VG_Dom0/LV_ROOT resume=/dev/VG_Swap/LV_SWAP showopts splash=silent vga=0x31a console=tty0 console=xvc0,57600 elevator=cfq max_loop=64 module /initrd-2.6.27.19-SLE11_BRANCH_20090304073920_1eb029c9-xen crash with the same symptoms as reported above -- no drives, and no OK boot :-/ if the problem's not @kernel (is it?), then is it xen, mdadm, or something else? and, should this be _moved_ 'there', or others simply 'invited in' here? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c93 --- Comment #93 from Tejun Heo 2009-03-04 18:54:32 MST --- Does iommu=usedac change anything for xen? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c95 --- Comment #95 from Tejun Heo 2009-03-04 19:11:13 MST --- What do you mean by 'crash'? The sil24 timeouts? Can you attach the kernel log? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c97 --- Comment #97 from Tejun Heo 2009-03-04 19:31:34 MST --- Thanks. It looks like IRQ delivery problem for sil24 controller. If iommu=usedac doesn't change anything, it's likely to be a separate issue. Can you please file a separate bug report? Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=463829 User pgnet.trash@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=463829#c99 --- Comment #99 from pgnet _ 2009-03-04 19:48:16 MST --- done: https://bugzilla.novell.com/show_bug.cgi?id=482220 thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.