In 2.4 there used to be a megaide driver for certain ata raid controllers.
In 2.6 I can't access more than my /dev/hda , I can see my other 4, I can create filesystems on them, but I can't mount them
Anyone knows how to use these on a 2.6 kernel (Centos 4.2)
greetings
Kris
00:02.0 RAID bus controller: Silicon Image, Inc. SiI 0649 Ultra ATA/100 PCI to ATA Host Controller (rev 02) Subsystem: Compaq Computer Corporation Integrated Ultra ATA-100 IDE RAID Controller Flags: bus master, medium devsel, latency 64, IRQ 5 I/O ports at 2010 [size=8] I/O ports at 2018 [size=4] I/O ports at 2020 [size=8] I/O ports at 2028 [size=4] I/O ports at 2030 [size=16] Capabilities: [60] Power Management version 2
On Thu, 2005-12-29 at 12:33 +0100, Kris Buytaert wrote:
In 2.4 there used to be a megaide driver for certain ata raid controllers.
Replyhing to myselve.
It seems you have to use dmraid
[root@cnode1 init.d]# dmraid -s *** Active Set name : lsi_cdhajaiciia size : 78165359 stride : 128 type : stripe status : ok subsets: 0 devs : 1 spares : 0 *** Active Set name : lsi_cdhajaiciib size : 78165359 stride : 128 type : stripe status : ok subsets: 0 devs : 1 spares : 0 *** Active Set name : lsi_cdhajaiciic size : 78165359 stride : 128 type : stripe status : ok subsets: 0 devs : 1 spares : 0 *** Active Set name : lsi_cdhajaiciid size : 78165359 stride : 128 type : stripe status : ok subsets: 0 devs : 1 spares : 0
show the devices but still I can put an ext3 filesystem on my /dev/hdd1 but I can't mount it .
Anyone got a clue .. ?
greetz
Kris
In 2.6 I can't access more than my /dev/hda , I can see my other 4, I can create filesystems on them, but I can't mount them
Anyone knows how to use these on a 2.6 kernel (Centos 4.2)
greetings
Kris
00:02.0 RAID bus controller: Silicon Image, Inc. SiI 0649 Ultra ATA/100 PCI to ATA Host Controller (rev 02) Subsystem: Compaq Computer Corporation Integrated Ultra ATA-100 IDE RAID Controller Flags: bus master, medium devsel, latency 64, IRQ 5 I/O ports at 2010 [size=8] I/O ports at 2018 [size=4] I/O ports at 2020 [size=8] I/O ports at 2028 [size=4] I/O ports at 2030 [size=16] Capabilities: [60] Power Management version 2
On Thu, 2005-12-29 at 14:14 +0100, Kris Buytaert wrote:
On Thu, 2005-12-29 at 12:33 +0100, Kris Buytaert wrote:
In 2.4 there used to be a megaide driver for certain ata raid controllers.
Replyhing to myselve.
It seems you have to use dmraid
[root@cnode1 init.d]# dmraid -s *** Active Set name : lsi_cdhajaiciia size : 78165359 stride : 128 type : stripe status : ok subsets: 0 devs : 1 spares : 0 *** Active Set name : lsi_cdhajaiciib size : 78165359 stride : 128 type : stripe status : ok subsets: 0 devs : 1 spares : 0 *** Active Set name : lsi_cdhajaiciic size : 78165359 stride : 128 type : stripe status : ok subsets: 0 devs : 1 spares : 0 *** Active Set name : lsi_cdhajaiciid size : 78165359 stride : 128 type : stripe status : ok subsets: 0 devs : 1 spares : 0
show the devices but still I can put an ext3 filesystem on my /dev/hdd1 but I can't mount it .
That would be very strange....
what does this show:
fdisk -l /dev/hdd
(is it full size?)
Anyone got a clue .. ?
There is improved megaraid support for the new kernel here from upstream:
http://people.redhat.com/~jbaron/rhel4/
You might give that a try.
greetz
Kris
In 2.6 I can't access more than my /dev/hda , I can see my other 4, I can create filesystems on them, but I can't mount them
Anyone knows how to use these on a 2.6 kernel (Centos 4.2)
greetings
Kris
00:02.0 RAID bus controller: Silicon Image, Inc. SiI 0649 Ultra ATA/100 PCI to ATA Host Controller (rev 02) Subsystem: Compaq Computer Corporation Integrated Ultra ATA-100 IDE RAID Controller Flags: bus master, medium devsel, latency 64, IRQ 5 I/O ports at 2010 [size=8] I/O ports at 2018 [size=4] I/O ports at 2020 [size=8] I/O ports at 2028 [size=4] I/O ports at 2030 [size=16] Capabilities: [60] Power Management version 2
On Thu, 2005-12-29 at 07:54 -0600, Johnny Hughes wrote:
On Thu, 2005-12-29 at 14:14 +0100, Kris Buytaert wrote:
On Thu, 2005-12-29 at 12:33 +0100, Kris Buytaert wrote:
In 2.4 there used to be a megaide driver for certain ata raid controllers.
That would be very strange....
what does this show:
fdisk -l /dev/hdd
(is it full size?)
[root@cnode1 ~]# fdisk -l /dev/hdd
Disk /dev/hdd: 40.0 GB, 40020664320 bytes 16 heads, 63 sectors/track, 77545 cylinders Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System /dev/hdd1 1 77545 39082648+ 83 Linux
[root@cnode1 ~]# dmsetup ls lsi_cdhajaiciid (253, 3) lsi_cdhajaiciic (253, 2) lsi_cdhajaiciib (253, 1) lsi_cdhajaiciia (253, 0)
Yep it is
Anyone got a clue .. ?
There is improved megaraid support for the new kernel here from upstream:
Right nice link with no docs or pointers what Downloading .. I`ll be reporting later on my progress :)
greetz
On Thu, 2005-12-29 at 16:11 +0100, Kris Buytaert wrote:
On Thu, 2005-12-29 at 07:54 -0600, Johnny Hughes wrote:
On Thu, 2005-12-29 at 14:14 +0100, Kris Buytaert wrote:
On Thu, 2005-12-29 at 12:33 +0100, Kris Buytaert wrote:
In 2.4 there used to be a megaide driver for certain ata raid controllers.
That would be very strange....
what does this show:
fdisk -l /dev/hdd
(is it full size?)
[root@cnode1 ~]# fdisk -l /dev/hdd
Disk /dev/hdd: 40.0 GB, 40020664320 bytes 16 heads, 63 sectors/track, 77545 cylinders Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System /dev/hdd1 1 77545 39082648+ 83 Linux
[root@cnode1 ~]# dmsetup ls lsi_cdhajaiciid (253, 3) lsi_cdhajaiciic (253, 2) lsi_cdhajaiciib (253, 1) lsi_cdhajaiciia (253, 0)
Yep it is
Anyone got a clue .. ?
There is improved megaraid support for the new kernel here from upstream:
Right nice link with no docs or pointers what Downloading .. I`ll be reporting later on my progress :)
Right ... that is because that is a RHEL test kernel ... and that is the pre-release RHEL4 test place.
No support from us (or them) on those kernels ... just a place to get the cutting edge testing RHEL kernels to see if they fix your problems.
I would NOT use that in production :)
kernel: powernow-k8: failing targ, change pending bit set
...just wondering what that msg means...was hitting really regular then stopped...like it was hitting /var/log/messages bout every 3 secs
thx
John Rose
...just wondering what that msg means...was hitting really regular then stopped...like it was hitting /var/log/messages bout every 3 secs
Bit of googling turned up a statement from the AMD kids that says the following We've started seeing this internally in AMD QA. The bit that the processor uses to indicate that it is in the process of changing frequencies (aka the pending change bit) is not clearing. The powernow-k8 driver cannot change frequencies until the previous change has completed.
Because this is happening on the hardware side, my best guess is that the problem is not software related. We've reported the problem to the AMD hardware debug team and they're investigating. I'll put out a patch when we have a solution.
-Mark Langsdorf AMD, Inc.
The other information I've seen says that it's likely related to processor speed stepping and not recovering properly etc.
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
Jim Perrin wrote:
...just wondering what that msg means...was hitting really regular then stopped...like it was hitting /var/log/messages bout every 3 secs
Bit of googling turned up a statement from the AMD kids that says the following We've started seeing this internally in AMD QA. The bit that the processor uses to indicate that it is in the process of changing frequencies (aka the pending change bit) is not clearing. The powernow-k8 driver cannot change frequencies until the previous change has completed.
Because this is happening on the hardware side, my best guess is that the problem is not software related. We've reported the problem to the AMD hardware debug team and they're investigating. I'll put out a patch when we have a solution.
-Mark Langsdorf AMD, Inc.
The other information I've seen says that it's likely related to processor speed stepping and not recovering properly etc.
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
There was something on the SuSE AMD64 list a few weeks back about this. In fact, what you googled up looks like part of that thread verbatim. They said there that it is something in generic kernel code (not SuSE-, & presumably CentOS-, specific) & that folks were toiling furiously to get it fixed. Might be a while till it makes it into more settled EL code, however ....
More errata fixed in software, oh joy!
Isn't there a way to just disable "PowerNow!"/"Cool'n Quiet" altogether in the meantime?
There was something on the SuSE AMD64 list a few weeks back about this. In fact, what you googled up looks like part of that thread verbatim. They said there that it is something in generic kernel code (not SuSE-, & presumably CentOS-, specific) & that folks were toiling furiously to get it fixed. Might be a while till it makes it into more settled EL code, however ....
It should. It is verbatim. From this link. http://lists.suse.com/archive/suse-amd64/2005-Sep/0129.html
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
Jim Perrin wrote:
There was something on the SuSE AMD64 list a few weeks back about this. In fact, what you googled up looks like part of that thread verbatim. They said there that it is something in generic kernel code (not SuSE-, & presumably CentOS-, specific) & that folks were toiling furiously to get it fixed. Might be a while till it makes it into more settled EL code, however ....
It should. It is verbatim. From this link. http://lists.suse.com/archive/suse-amd64/2005-Sep/0129.html
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
That *would* explain that, wouldn't it :-).
On Tue, 2006-01-03 at 19:05 -0500, Jim Perrin wrote:
...just wondering what that msg means...was hitting really regular then stopped...like it was hitting /var/log/messages bout every 3 secs
Bit of googling turned up a statement from the AMD kids that says the following We've started seeing this internally in AMD QA. The bit that the processor uses to indicate that it is in the process of changing frequencies (aka the pending change bit) is not clearing. The powernow-k8 driver cannot change frequencies until the previous change has completed.
Because this is happening on the hardware side, my best guess is that the problem is not software related. We've reported the problem to the AMD hardware debug team and they're investigating. I'll put out a patch when we have a solution.
-Mark Langsdorf AMD, Inc.
The other information I've seen says that it's likely related to processor speed stepping and not recovering properly etc.
-- Jim Perrin
ummmm ok....I will keep monitoring this system...I just swapped out processors today...the powernow-k8 msg was doing it but then...the system is running fine...seems like it anyway...I did not mean that the whole sys "stopped" just that the powernow msgs stopped.
right now...I just wanna see it run 2-3 or so days w/out goin nuts like the other proc did that I just replaced lol
thx
jr
On Tue, 2006-01-03 at 19:05 -0500, Jim Perrin wrote:
...just wondering what that msg means...was hitting really regular then stopped...like it was hitting /var/log/messages bout every 3 secs
Bit of googling turned up a statement from the AMD kids that says the following We've started seeing this internally in AMD QA. The bit that the processor uses to indicate that it is in the process of changing frequencies (aka the pending change bit) is not clearing. The powernow-k8 driver cannot change frequencies until the previous change has completed.
Because this is happening on the hardware side, my best guess is that the problem is not software related. We've reported the problem to the AMD hardware debug team and they're investigating. I'll put out a patch when we have a solution.
-Mark Langsdorf AMD, Inc.
The other information I've seen says that it's likely related to processor speed stepping and not recovering properly etc.
kk I got this powernow-k8 to repeat.
I run off a kvm switch. if I say, leave kwrite /var/log/messages @ full screen...no matter if I switch computers...that msg will not log.
if I x out the messages log...leave that computer ...only a small window of the console is open...then I come back and bring up the log file...the powernow msgs are back...
this is all for what it's worth
thx
John Rose
On Tue, 2006-01-03 at 20:30 -0600, rado wrote:
On Tue, 2006-01-03 at 19:05 -0500, Jim Perrin wrote:
...just wondering what that msg means...was hitting really regular then stopped...like it was hitting /var/log/messages bout every 3 secs
Bit of googling turned up a statement from the AMD kids that says the following We've started seeing this internally in AMD QA. The bit that the processor uses to indicate that it is in the process of changing frequencies (aka the pending change bit) is not clearing. The powernow-k8 driver cannot change frequencies until the previous change has completed.
Because this is happening on the hardware side, my best guess is that the problem is not software related. We've reported the problem to the AMD hardware debug team and they're investigating. I'll put out a patch when we have a solution.
-Mark Langsdorf AMD, Inc.
The other information I've seen says that it's likely related to processor speed stepping and not recovering properly etc.
kk I got this powernow-k8 to repeat.
I run off a kvm switch. if I say, leave kwrite /var/log/messages @ full screen...no matter if I switch computers...that msg will not log.
if I x out the messages log...leave that computer ...only a small window of the console is open...then I come back and bring up the log file...the powernow msgs are back...
this is all for what it's worth
I have noticed this same message in my console at startup and in my logs on my ASUS K8V-X ... I have been ignoring it for a year :)
On Tue, 2006-01-03 at 20:39 -0600, Johnny Hughes wrote:
On Tue, 2006-01-03 at 20:30 -0600, rado wrote:
On Tue, 2006-01-03 at 19:05 -0500, Jim Perrin wrote:
...just wondering what that msg means...was hitting really regular then stopped...like it was hitting /var/log/messages bout every 3 secs
Bit of googling turned up a statement from the AMD kids that says the following We've started seeing this internally in AMD QA. The bit that the processor uses to indicate that it is in the process of changing frequencies (aka the pending change bit) is not clearing. The powernow-k8 driver cannot change frequencies until the previous change has completed.
Because this is happening on the hardware side, my best guess is that the problem is not software related. We've reported the problem to the AMD hardware debug team and they're investigating. I'll put out a patch when we have a solution.
-Mark Langsdorf AMD, Inc.
The other information I've seen says that it's likely related to processor speed stepping and not recovering properly etc.
kk I got this powernow-k8 to repeat.
I run off a kvm switch. if I say, leave kwrite /var/log/messages @ full screen...no matter if I switch computers...that msg will not log.
if I x out the messages log...leave that computer ...only a small window of the console is open...then I come back and bring up the log file...the powernow msgs are back...
this is all for what it's worth
I have noticed this same message in my console at startup and in my logs on my ASUS K8V-X ... I have been ignoring it for a year :)
well, I think ASUS is a pretty highly touted mb too and if it works for you then it works for me as well...move on to bigger and better huh?
thx
jr
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thursday 29 December 2005 13:14, Kris Buytaert wrote:
If you're using DMRaid you shouldn't be accessing /dev/hd anything. dmraid -ay activates the raid set and a device should be created under /dev/mapper/. Please note it's a while since I used dmraid but that's how it used to work IIRC.
On Thu, 2005-12-29 at 12:33 +0100, Kris Buytaert wrote:
In 2.4 there used to be a megaide driver for certain ata raid controllers.
Replyhing to myselve.
It seems you have to use dmraid
[root@cnode1 init.d]# dmraid -s *** Active Set name : lsi_cdhajaiciia size : 78165359 stride : 128 type : stripe status : ok subsets: 0 devs : 1 spares : 0 *** Active Set name : lsi_cdhajaiciib size : 78165359 stride : 128 type : stripe status : ok subsets: 0 devs : 1 spares : 0 *** Active Set name : lsi_cdhajaiciic size : 78165359 stride : 128 type : stripe status : ok subsets: 0 devs : 1 spares : 0 *** Active Set name : lsi_cdhajaiciid size : 78165359 stride : 128 type : stripe status : ok subsets: 0 devs : 1 spares : 0
show the devices but still I can put an ext3 filesystem on my /dev/hdd1 but I can't mount it .
Anyone got a clue .. ?
greetz
Kris
In 2.6 I can't access more than my /dev/hda , I can see my other 4, I can create filesystems on them, but I can't mount them
Anyone knows how to use these on a 2.6 kernel (Centos 4.2)
greetings
Kris
00:02.0 RAID bus controller: Silicon Image, Inc. SiI 0649 Ultra ATA/100 PCI to ATA Host Controller (rev 02) Subsystem: Compaq Computer Corporation Integrated Ultra ATA-100 IDE RAID Controller Flags: bus master, medium devsel, latency 64, IRQ 5 I/O ports at 2010 [size=8] I/O ports at 2018 [size=4] I/O ports at 2020 [size=8] I/O ports at 2028 [size=4] I/O ports at 2030 [size=16] Capabilities: [60] Power Management version 2
-
Bryan J. Smith -
Jim Perrin -
Johnny Hughes -
Kris Buytaert -
rado -
Rob Hall -
William A. Mahaffey III