+ Reply to Thread
Results 1 to 2 of 2

Thread: Typic RAM error messages

  1. #1
    joseph's Avatar
    joseph is offline Website Master Achievements:
    500 Experience Points1000 Experience Points5000 Experience Points10000 Experience PointsRecommendation Second Class
    joseph has disabled reputation
    Join Date
    2008-09-08
    Posts
    412

    Default Typic RAM error messages

    EDAC k8 MC0: general bus error: participating processor(local node response), time-out(no timeout) memory transaction type(generic read), mem or i/o(mem access), cache level(generic)
    MC0: CE page 0x6e705, offset 0x870, grain 8, syndrome 0xebe8, row 0, channel 1, label "": k8_edac
    EDAC k8 MC0: extended error code: ECC chipkill x4 error
    EDAC k8 MC0: general bus error: participating processor(local node origin), time-out(no timeout) memory transaction type(generic read), mem or i/o(mem access), cache level(generic)
    MC0: CE page 0x1c482, offset 0x870, grain 8, syndrome 0xebe8, row 0, channel 1, label "": k8_edac
    EDAC k8 MC0: extended error code: ECC chipkill x4 error
    EDAC k8 MC0: general bus error: participating processor(local node origin), time-out(no timeout) memory transaction type(generic read), mem or i/o(mem access), cache level(generic)
    MC0: CE page 0x26ddc, offset 0x9b8, grain 8, syndrome 0xebe8, row 0, channel 1, label "": k8_edac
    EDAC k8 MC0: extended error code: ECC chipkill x4 error
    EDAC k8 MC0: general bus error: participating processor(local node origin), time-out(no timeout) memory transaction type(generic read), mem or i/o(mem access), cache level(generic)
    MC0: CE page 0x1c482, offset 0x870, grain 8, syndrome 0xebe8, row 0, channel 1, label "": k8_edac
    EDAC k8 MC0: extended error code: ECC chipkill x4 error
    EDAC k8 MC0: general bus error: participating processor(local node origin), time-out(no timeout) memory transaction type(generic read), mem or i/o(mem access), cache level(generic)
    MC0: CE page 0x1c482, offset 0x870, grain 8, syndrome 0xebe8, row 0, channel 1, label "": k8_edac
    EDAC k8 MC0: extended error code: ECC chipkill x4 error
    EDAC k8 MC0: general bus error: participating processor(local node response), time-out(no timeout) memory transaction type(generic read), mem or i/o(mem access), cache level(generic)
    MC0: CE page 0x1c482, offset 0x870, grain 8, syndrome 0xebe8, row 0, channel 1, label "": k8_edac
    EDAC k8 MC0: extended error code: ECC chipkill x4 error
    EDAC k8 MC0: general bus error: participating processor(local node origin), time-out(no timeout) memory transaction type(generic read), mem or i/o(mem access), cache level(generic)
    MC0: CE page 0x6e705, offset 0x870, grain 8, syndrome 0xebe8, row 0, channel 1, label "": k8_edac
    EDAC k8 MC0: extended error code: ECC chipkill x4 error
    EDAC k8 MC0: general bus error: participating processor(local node origin), time-out(no timeout) memory transaction type(generic read), mem or i/o(mem access), cache level(generic)
    MC0: CE page 0x1c482, offset 0x870, grain 8, syndrome 0xebe8, row 0, channel 1, label "": k8_edac
    EDAC k8 MC0: extended error code: ECC chipkill x4 error
    EDAC k8 MC0: general bus error: participating processor(local node origin), time-out(no timeout) memory transaction type(generic read), mem or i/o(mem access), cache level(generic)
    MC0: CE page 0x6e705, offset 0x870, grain 8, syndrome 0xebe8, row 0, channel 1, label "": k8_edac
    EDAC k8 MC0: extended error code: ECC chipkill x4 error
    EDAC k8 MC0: general bus error: participating processor(local node response), time-out(no timeout) memory transaction type(generic read), mem or i/o(mem access), cache level(generic)
    MC0: CE page 0x6e705, offset 0x870, grain 8, syndrome 0xebe8, row 0, channel 1, label "": k8_edac
    EDAC k8 MC0: extended error code: ECC chipkill x4 error

    Just faced this error message on a HP DL145 G2,
    There should be some bad sticks of RAM.
    Anyway the best solution should be replace the RAM that you currently used.

  2. #2
    joseph's Avatar
    joseph is offline Website Master Achievements:
    500 Experience Points1000 Experience Points5000 Experience Points10000 Experience PointsRecommendation Second Class
    joseph has disabled reputation
    Join Date
    2008-09-08
    Posts
    412

    Default Reiserfs warning message

    I suspect the message is caused by corrupted file system logs.

    EXT3-fs: mounted filesystem with ordered data mode.
    reiserfs: found format "3.6" with standard journal
    reiserfs:warning: CONFIG_REISERFS_CHECK is set ON
    reiserfs:warning: - it is slow mode for debugging.
    reiserfs: checking transaction log (device sd(8,5)) ...
    for (sd(8,5))
    sd(8,5): journal-1153: found in header: first_unflushed_offset 4845, last_flushed_trans_id 12961150
    sd(8,5): journal-1206: Starting replay from offset 4845, trans_id 12961151
    sd(8,5): journal-1299: Setting newest_mount_id to 15
    sd(8,5):Using r5 hash to sort names
    reiserfs: found format "3.6" with standard journal
    reiserfs:warning: CONFIG_REISERFS_CHECK is set ON
    reiserfs:warning: - it is slow mode for debugging.
    reiserfs: checking transaction log (device sd(8,6)) ...
    for (sd(8,6))
    sd(8,6): journal-1153: found in header: first_unflushed_offset 3151, last_flushed_trans_id 12826209
    sd(8,6): journal-1006: found valid transaction start offset 3151, len 2 id 12824805
    sd(8,6): journal-1206: Starting replay from offset 3151, trans_id 12826210
    sd(8,6): journal-1037: journal_read_transaction, offset 3151, len 2 mount_id 12
    sd(8,6): journal-1039: journal_read_trans skipping because 3151 is too old
    sd(8,6): journal-1299: Setting newest_mount_id to 15
    sd(8,6):Using r5 hash to sort names
    reiserfs: found format "3.6" with standard journal
    reiserfs:warning: CONFIG_REISERFS_CHECK is set ON
    reiserfs:warning: - it is slow mode for debugging.
    reiserfs: checking transaction log (device sd(8,7)) ...
    for (sd(8,7))
    sd(8,7): journal-1153: found in header: first_unflushed_offset 6806, last_flushed_trans_id 12577681
    sd(8,7): journal-1206: Starting replay from offset 6806, trans_id 12577682
    sd(8,7): journal-1299: Setting newest_mount_id to 15
    sd(8,7):Using r5 hash to sort names
    e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex

+ Reply to Thread

Similar Threads

  1. yum update spawns error messages
    By kev200 in forum Linux Newbie
    Replies: 2
    Last Post: 2009-09-24, 03:35 AM
  2. [Dell] Typic SCSI error message
    By joseph in forum Hardware Forum
    Replies: 0
    Last Post: 2008-11-11, 02:42 PM
  3. Typic database error!
    By joseph in forum Localized Support
    Replies: 0
    Last Post: 2008-09-15, 11:04 AM
  4. Typic SCSI hardware error
    By joseph in forum General Storage
    Replies: 3
    Last Post: 2008-09-15, 04:48 AM
  5. rsync typic error messages
    By joseph in forum Linux System
    Replies: 0
    Last Post: 2008-09-15, 04:16 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts