[arch-general] Update to 2.6.34.3-1 & LTS 2.6.32.18-1 killed dmraid box??
David C. Rankin
drankinatty at suddenlinkmail.com
Tue Aug 17 14:27:12 EDT 2010
On 08/17/2010 10:39 AM, Rogutės Sparnuotos wrote:
> So all that you see after the grub prompt is this (including the dots)?
>
> root(1,5)
> bzimage.....
>
> What if you put 'debug' there, so that the line reads:
>
> kernel /vmlinuz26 root=/dev/mapper/nvidia_baaccajap5 ro debug
What it says in total is:
Booting 'Arch Linux on Archangel'
root (hd1,5)
Filesystem Type ext2fs, partition type 0x83
kernel /vmlinuz26 root=/dev/mapper/nvidia_baaccajap5 ro debug
[Linux-BzImage, setup=0x3200, size=0x1ff440]
(then it sits and reboots)
This must have something to do with how 2.6.34.3 handles dmraid, because after
a failed boot, the bios reports the second array as "Unhealthy". (It is fine).
Simply powering off and back on re-syncs the array and it boots into LTS just fine.
Adding debug makes no difference.
What does this look like to you? Broken dmraid for nv8200 chipset in 2.6.34.3?
I know this is *not* a generic dmraid, nvraid or 2.6.34.3 issue, because to
trouble-shoot I updated my *regular* server (Tyan Computer Tomcat K8E (S2865))
to 2.6.34.3 and it uses nv_sata and dmraid as well. Updated without an issue.
The working server has the following dmraid config and lspci info:
[12:57 nirvana:/home/david] # dmraid -r
/dev/sdb: nvidia, "nvidia_ddddhhfh", mirror, ok, 1465149166 sectors, data@ 0
/dev/sda: nvidia, "nvidia_ddddhhfh", mirror, ok, 1465149166 sectors, data@ 0
[12:57 nirvana:/home/david] # dmraid -s
*** Active Set
name : nvidia_ddddhhfh
size : 1465149056
stride : 128
type : mirror
status : ok
subsets: 0
devs : 2
spares : 0
lspci info:
00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
(prog-if 85 [Master SecO PriO])
Subsystem: Tyan Computer Tomcat K8E (S2865)
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23
I/O ports at 09f0 [size=8]
I/O ports at 0bf0 [size=4]
I/O ports at 0970 [size=8]
I/O ports at 0b70 [size=4]
I/O ports at d400 [size=16]
Memory at febfc000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Kernel driver in use: sata_nv
Kernel modules: ata_generic, pata_acpi, sata_nv, ide-pci-generic
00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3)
(prog-if 85 [Master SecO PriO])
Subsystem: Tyan Computer Tomcat K8E (S2865)
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22
I/O ports at 09e0 [size=8]
I/O ports at 0be0 [size=4]
I/O ports at 0960 [size=8]
I/O ports at 0b60 [size=4]
I/O ports at c000 [size=16]
Memory at febfb000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Kernel driver in use: sata_nv
Kernel modules: ata_generic, pata_acpi, sata_nv, ide-pci-generic
On the test server where 2.6.34.3 will *not* boot you have (running LTS):
[13:04 archangel:/home/david] # dmraid -r
/dev/sda: nvidia, "nvidia_fdaacfde", mirror, ok, 976773166 sectors, data@ 0
/dev/sdb: nvidia, "nvidia_baaccaja", mirror, ok, 1465149166 sectors, data@ 0
/dev/sdc: nvidia, "nvidia_fdaacfde", mirror, ok, 976773166 sectors, data@ 0
/dev/sdd: nvidia, "nvidia_baaccaja", mirror, ok, 1465149166 sectors, data@ 0
[13:04 archangel:/home/david] # dmraid -s
*** Active Set
name : nvidia_fdaacfde
size : 976773120
stride : 128
type : mirror
status : ok
subsets: 0
devs : 2
spares : 0
*** Active Set
name : nvidia_baaccaja
size : 1465149056
stride : 128
type : mirror
status : ok
subsets: 0
devs : 2
spares : 0
lspci info:
00:09.0 RAID bus controller: nVidia Corporation MCP78S [GeForce 8200] SATA
Controller (RAID mode) (rev a2)
Subsystem: Micro-Star International Co., Ltd. Device 7374
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 28
I/O ports at b080 [size=8]
I/O ports at b000 [size=4]
I/O ports at ac00 [size=8]
I/O ports at a880 [size=4]
I/O ports at a800 [size=16]
Memory at f9e76000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [44] Power Management version 2
Capabilities: [8c] SATA HBA v1.0
Capabilities: [b0] MSI: Enable+ Count=1/8 Maskable- 64bit+
Capabilities: [ec] HyperTransport: MSI Mapping Enable+ Fixed+
Kernel driver in use: ahci
Kernel modules: ahci
The big difference I see is that my main server 'nirvana' uses:
Kernel driver in use: sata_nv
Kernel modules: ata_generic, pata_acpi, sata_nv, ide-pci-generic
which is working just fine with 2.6.34.3 while the test box 'archangel' uses:
Kernel driver in use: ahci
Kernel modules: ahci
so it looks like the problem is in the ahci module and dmraid. Now how to fix? I
have always used this box with mkinitcpio.conf configured with:
MODULES="dm_mod dm_mirror sata_nv"
I'll go see if I can rebuild with the ahci module loaded in the initramfs and
see if that helps. But regardless, there is a bug somewhere. LTS boots fine in
this config and 2.6.34.3 doesn't??
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
More information about the arch-general
mailing list