ASUS A7V/Thunderbird 1GHz lockup problems observation w/fix for me
Ever since building this system there have been spontaneous and unpredictable lockups, usually at least once per day. Sometimes several per day. The lockup is sometimes preceded by X starting to display things strangely (on a Voodoo 3 w/XF 4.X). Then I have a few minutes to reboot before it hangs (can't log in using ssh from another system.) With the Northbridge discussion, I couldn't pinpoint anything to fix it, so I started experimenting. Things got better by upgrading the BIOS; but still many hangs. I've discovered that changing the CPU voltage from the default to 1.75V results in a stable system. Higher than that doesn't work. Lower still gets lockups. It doesn't look like everyone has this problem with similar setups. But if there are others, I wanted to share this discovery. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
ASUS A7V/Thunderbird 1GHz lockup problems observation w/fix for me
Ever since building this system there have been spontaneous and unpredictable lockups, usually at least once per day. Sometimes several per day. The lockup is sometimes preceded by X starting to display things strangely (on a Voodoo 3 w/XF 4.X). Then I have a few minutes to reboot before it hangs (can't log in using ssh from another system.) With the Northbridge discussion, I couldn't pinpoint anything to fix it, so I started experimenting. Things got better by upgrading the BIOS; but still many hangs. I've discovered that changing the CPU voltage from the default to 1.75V results in a stable system. Higher than that doesn't work. Lower still gets lockups. It doesn't look like everyone has this problem with similar setups. But if there are others, I wanted to share this discovery. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2ac12 (vt82c686 info)
> No, just the vt82c686. vt82c686a and vt82c686b are OK. So can the vt82c686 be replaced with one of these other chips? What action is available to owners of MBs with chips that don't work w/Linux? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux 2.4.2ac12 (vt82c686 info)
No, just the vt82c686. vt82c686a and vt82c686b are OK. So can the vt82c686 be replaced with one of these other chips? What action is available to owners of MBs with chips that don't work w/Linux? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
What is 2.4.0-test10: md1 has overlapping physical units with md2!
Is this something to be concerned about? It sounds like a disaster waiting to happen from the message. This is on 2 systems (with similar disk setups [same other than size]). dmesg from bootup: Nov 18 16:31:01 mwg kernel: md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 Nov 18 16:31:01 mwg kernel: raid1 personality registered Nov 18 16:31:01 mwg kernel: md.c: sizeof(mdp_super_t) = 4096 Nov 18 16:31:01 mwg kernel: autodetecting RAID arrays Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus0/target0/lun0/part1's sb offset: 524544 [events: 0056] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus0/target0/lun0/part3's sb offset: 4194688 [events: 0055] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus0/target0/lun0/part4's sb offset: 24771008 [events: 0058] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus1/target0/lun0/part1's sb offset: 524544 [events: 0056] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus1/target0/lun0/part3's sb offset: 4194688 [events: 0055] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus1/target0/lun0/part4's sb offset: 24771008 [events: 0058] Nov 18 16:31:01 mwg kernel: autorun ... Nov 18 16:31:01 mwg kernel: considering ide/host0/bus1/target0/lun0/part4 ... Nov 18 16:31:01 mwg kernel: adding ide/host0/bus1/target0/lun0/part4 ... Nov 18 16:31:01 mwg kernel: adding ide/host0/bus0/target0/lun0/part4 ... Nov 18 16:31:01 mwg kernel: created md2 Nov 18 16:31:01 mwg kernel: bind Nov 18 16:31:01 mwg kernel: bind Nov 18 16:31:01 mwg kernel: running: Nov 18 16:31:01 mwg kernel: now! Nov 18 16:31:01 mwg kernel: ide/host0/bus1/target0/lun0/part4's event counter: 0058 Nov 18 16:31:01 mwg kernel: ide/host0/bus0/target0/lun0/part4's event counter: 0058 Nov 18 16:31:01 mwg kernel: md: md2: raid array is not clean -- starting background reconstruction Nov 18 16:31:01 mwg kernel: md2: max total readahead window set to 124k Nov 18 16:31:01 mwg kernel: md2: 1 data-disks, max readahead per data-disk: 124k Nov 18 16:31:01 mwg kernel: raid1: device ide/host0/bus1/target0/lun0/part4 operational as mirror 1 Nov 18 16:31:01 mwg kernel: raid1: device ide/host0/bus0/target0/lun0/part4 operational as mirror 0 Nov 18 16:31:01 mwg kernel: raid1: raid set md2 not clean; reconstructing mirrors Nov 18 16:31:01 mwg kernel: raid1: raid set md2 active with 2 out of 2 mirrors Nov 18 16:31:01 mwg kernel: md: updating md2 RAID superblock on device Nov 18 16:31:01 mwg kernel: ide/host0/bus1/target0/lun0/part4 [events: 0059](write) ide/host0/bus1/target0/lun0/part4's sb offset: 24771008 Nov 18 16:31:01 mwg kernel: md: syncing RAID array md2 Nov 18 16:31:01 mwg kernel: md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc. Nov 18 16:31:01 mwg kernel: md: using maximum available idle IO bandwith (but not more than 10 KB/sec) for reconstruction. Nov 18 16:31:01 mwg kernel: md: using 124k window, over a total of 24771008 blocks. Nov 18 16:31:01 mwg kernel: ide/host0/bus0/target0/lun0/part4 [events: 0059](write) ide/host0/bus0/target0/lun0/part4's sb offset: 24771008 Nov 18 16:31:01 mwg kernel: . Nov 18 16:31:01 mwg kernel: considering ide/host0/bus1/target0/lun0/part3 ... Nov 18 16:31:02 mwg kernel: adding ide/host0/bus1/target0/lun0/part3 ... Nov 18 16:31:02 mwg kernel: adding ide/host0/bus0/target0/lun0/part3 ... Nov 18 16:31:02 mwg kernel: created md1 Nov 18 16:31:02 mwg kernel: bind Nov 18 16:31:02 mwg kernel: bind Nov 18 16:31:02 mwg kernel: running: Nov 18 16:31:02 mwg kernel: now! Nov 18 16:31:02 mwg kernel: ide/host0/bus1/target0/lun0/part3's event counter: 0055 Nov 18 16:31:02 mwg kernel: ide/host0/bus0/target0/lun0/part3's event counter: 0055 Nov 18 16:31:02 mwg kernel: md: md1: raid array is not clean -- starting background reconstruction Nov 18 16:31:02 mwg kernel: md1: max total readahead window set to 124k Nov 18 16:31:02 mwg kernel: md1: 1 data-disks, max readahead per data-disk: 124k Nov 18 16:31:02 mwg kernel: raid1: device ide/host0/bus1/target0/lun0/part3 operational as mirror 1 Nov 18 16:31:02 mwg kernel: raid1: device ide/host0/bus0/target0/lun0/part3 operational as mirror 0 Nov 18 16:31:02 mwg kernel: raid1: raid set md1 not clean; reconstructing mirrors Nov 18 16:31:02 mwg kernel: raid1: raid set md1 active with 2 out of 2 mirrors Nov 18 16:31:02 mwg kernel: md: updating md1 RAID superblock on device Nov 18 16:31:02 mwg kernel: ide/host0/bus1/target0/lun0/part3 [events: 0056](write) ide/host0/bus1/target0/lun0/part3's sb offset: 4194688 Nov 18 16:31:02 mwg kernel: md: serializing resync, md1 has overlapping physical units with md2! Nov 18 16:31:02 mwg kernel: ide/host0/bus0/target0/lun0/part3 [events: 0056](write) ide/host0/bus0/target0/lun0/part3's sb offset: 4194688 Nov 18 16:31:02 mwg kernel: . Nov 18 16:31:02 mwg kernel: considering ide/host0/bus1/target0/lun0/part1 ... Nov 18 16:31:02 mwg
What is 2.4.0-test10: md1 has overlapping physical units with md2!
Is this something to be concerned about? It sounds like a disaster waiting to happen from the message. This is on 2 systems (with similar disk setups [same other than size]). dmesg from bootup: Nov 18 16:31:01 mwg kernel: md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12 Nov 18 16:31:01 mwg kernel: raid1 personality registered Nov 18 16:31:01 mwg kernel: md.c: sizeof(mdp_super_t) = 4096 Nov 18 16:31:01 mwg kernel: autodetecting RAID arrays Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus0/target0/lun0/part1's sb offset: 524544 [events: 0056] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus0/target0/lun0/part3's sb offset: 4194688 [events: 0055] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus0/target0/lun0/part4's sb offset: 24771008 [events: 0058] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus1/target0/lun0/part1's sb offset: 524544 [events: 0056] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus1/target0/lun0/part3's sb offset: 4194688 [events: 0055] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus1/target0/lun0/part4's sb offset: 24771008 [events: 0058] Nov 18 16:31:01 mwg kernel: autorun ... Nov 18 16:31:01 mwg kernel: considering ide/host0/bus1/target0/lun0/part4 ... Nov 18 16:31:01 mwg kernel: adding ide/host0/bus1/target0/lun0/part4 ... Nov 18 16:31:01 mwg kernel: adding ide/host0/bus0/target0/lun0/part4 ... Nov 18 16:31:01 mwg kernel: created md2 Nov 18 16:31:01 mwg kernel: bindide/host0/bus0/target0/lun0/part4,1 Nov 18 16:31:01 mwg kernel: bindide/host0/bus1/target0/lun0/part4,2 Nov 18 16:31:01 mwg kernel: running: ide/host0/bus1/target0/lun0/part4ide/host0/bus0/target0/lun0/part4 Nov 18 16:31:01 mwg kernel: now! Nov 18 16:31:01 mwg kernel: ide/host0/bus1/target0/lun0/part4's event counter: 0058 Nov 18 16:31:01 mwg kernel: ide/host0/bus0/target0/lun0/part4's event counter: 0058 Nov 18 16:31:01 mwg kernel: md: md2: raid array is not clean -- starting background reconstruction Nov 18 16:31:01 mwg kernel: md2: max total readahead window set to 124k Nov 18 16:31:01 mwg kernel: md2: 1 data-disks, max readahead per data-disk: 124k Nov 18 16:31:01 mwg kernel: raid1: device ide/host0/bus1/target0/lun0/part4 operational as mirror 1 Nov 18 16:31:01 mwg kernel: raid1: device ide/host0/bus0/target0/lun0/part4 operational as mirror 0 Nov 18 16:31:01 mwg kernel: raid1: raid set md2 not clean; reconstructing mirrors Nov 18 16:31:01 mwg kernel: raid1: raid set md2 active with 2 out of 2 mirrors Nov 18 16:31:01 mwg kernel: md: updating md2 RAID superblock on device Nov 18 16:31:01 mwg kernel: ide/host0/bus1/target0/lun0/part4 [events: 0059](write) ide/host0/bus1/target0/lun0/part4's sb offset: 24771008 Nov 18 16:31:01 mwg kernel: md: syncing RAID array md2 Nov 18 16:31:01 mwg kernel: md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc. Nov 18 16:31:01 mwg kernel: md: using maximum available idle IO bandwith (but not more than 10 KB/sec) for reconstruction. Nov 18 16:31:01 mwg kernel: md: using 124k window, over a total of 24771008 blocks. Nov 18 16:31:01 mwg kernel: ide/host0/bus0/target0/lun0/part4 [events: 0059](write) ide/host0/bus0/target0/lun0/part4's sb offset: 24771008 Nov 18 16:31:01 mwg kernel: . Nov 18 16:31:01 mwg kernel: considering ide/host0/bus1/target0/lun0/part3 ... Nov 18 16:31:02 mwg kernel: adding ide/host0/bus1/target0/lun0/part3 ... Nov 18 16:31:02 mwg kernel: adding ide/host0/bus0/target0/lun0/part3 ... Nov 18 16:31:02 mwg kernel: created md1 Nov 18 16:31:02 mwg kernel: bindide/host0/bus0/target0/lun0/part3,1 Nov 18 16:31:02 mwg kernel: bindide/host0/bus1/target0/lun0/part3,2 Nov 18 16:31:02 mwg kernel: running: ide/host0/bus1/target0/lun0/part3ide/host0/bus0/target0/lun0/part3 Nov 18 16:31:02 mwg kernel: now! Nov 18 16:31:02 mwg kernel: ide/host0/bus1/target0/lun0/part3's event counter: 0055 Nov 18 16:31:02 mwg kernel: ide/host0/bus0/target0/lun0/part3's event counter: 0055 Nov 18 16:31:02 mwg kernel: md: md1: raid array is not clean -- starting background reconstruction Nov 18 16:31:02 mwg kernel: md1: max total readahead window set to 124k Nov 18 16:31:02 mwg kernel: md1: 1 data-disks, max readahead per data-disk: 124k Nov 18 16:31:02 mwg kernel: raid1: device ide/host0/bus1/target0/lun0/part3 operational as mirror 1 Nov 18 16:31:02 mwg kernel: raid1: device ide/host0/bus0/target0/lun0/part3 operational as mirror 0 Nov 18 16:31:02 mwg kernel: raid1: raid set md1 not clean; reconstructing mirrors Nov 18 16:31:02 mwg kernel: raid1: raid set md1 active with 2 out of 2 mirrors Nov 18 16:31:02 mwg kernel: md: updating md1 RAID superblock on device Nov 18 16:31:02 mwg kernel: ide/host0/bus1/target0/lun0/part3 [events: 0056](write) ide/host0/bus1/target0/lun0/part3's sb offset: 4194688 Nov 18 16:31:02 mwg kernel: md: serializing resync, md1 has overlapping physical units with md2! Nov 18
