Namespace look up failure - What does this mean?


Recommended Posts

My Syslog contains these errors (highlighted in red from unmenu).  What does it mean?

 

Oct 25 15:03:28 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110413/psargs-359) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node f506c0f0), AE_NOT_FOUND (20110413/psparse-536) (Errors)

Oct 25 15:03:28 Tower kernel: ata9.00: ATA-8: WDC WD20EARS-00MVWB0, 51.0AB51, max UDMA/133 (Drive related)

Oct 25 15:03:28 Tower kernel: ata9.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA (Drive related)

Oct 25 15:03:28 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110413/psargs-359) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node f506c258), AE_NOT_FOUND (20110413/psparse-536) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110413/psargs-359) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node f506c210), AE_NOT_FOUND (20110413/psparse-536) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110413/psargs-359) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node f506c1c8), AE_NOT_FOUND (20110413/psparse-536) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110413/psargs-359) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node f506c138), AE_NOT_FOUND (20110413/psparse-536) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110413/psargs-359) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node f506c180), AE_NOT_FOUND (20110413/psparse-536) (Errors)

Oct 25 15:03:28 Tower kernel: ata14.00: ATA-8: WDC WD20EARS-00S8B1, 80.00A80, max UDMA/133 (Drive related)

Oct 25 15:03:28 Tower kernel: ata14.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA (Drive related)

Oct 25 15:03:28 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110413/psargs-359) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT0._GTF] (Node f506c0f0), AE_NOT_FOUND (20110413/psparse-536) (Errors)

Oct 25 15:03:28 Tower kernel: ata13.00: ATA-8: WDC WD30EZRX-00MMMB0, 80.00A80, max UDMA/133 (Drive related)

Oct 25 15:03:28 Tower kernel: ata13.00: 5860533168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA (Drive related)

Oct 25 15:03:28 Tower kernel: ata10.00: ATA-8: WDC WD20EARS-00S8B1, 80.00A80, max UDMA/133 (Drive related)

Oct 25 15:03:28 Tower kernel: ata10.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA (Drive related)

Oct 25 15:03:28 Tower kernel: ata12.00: ATA-8: WDC WD20EARS-00S8B1, 80.00A80, max UDMA/133 (Drive related)

Oct 25 15:03:28 Tower kernel: ata12.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA (Drive related)

Oct 25 15:03:28 Tower kernel: ata11.00: ATA-8: WDC WD20EARS-00S8B1, 80.00A80, max UDMA/133 (Drive related)

Oct 25 15:03:28 Tower kernel: ata11.00: 3907029168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA (Drive related)

Oct 25 15:03:28 Tower kernel: ata9.00: configured for UDMA/133 (Drive related)

Oct 25 15:03:28 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110413/psargs-359) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node f506c258), AE_NOT_FOUND (20110413/psparse-536) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110413/psargs-359) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT3._GTF] (Node f506c1c8), AE_NOT_FOUND (20110413/psparse-536) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110413/psargs-359) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT1._GTF] (Node f506c138), AE_NOT_FOUND (20110413/psparse-536) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110413/psargs-359) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT2._GTF] (Node f506c180), AE_NOT_FOUND (20110413/psparse-536) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110413/psargs-359) (Errors)

Oct 25 15:03:28 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node f506c210), AE_NOT_FOUND (20110413/psparse-536) (Errors)

Link to comment

It means they all have the string of letters "error" somewhere in them.  (the criteria for coloring them "red" in the syslog viewer in unMENU.)

 

Other than that, the messages themselves usually indicate that ACPI has been disabled in the BIOS (or disabled with 'noacpi' in your syslinux.conf file),

or, ACPI is poorly implemented in the BIOS,

or, the BIOS is using ACPI features not yet implemented in the linux kernel.

 

Look first for a BIOS update for your MB, make sure you've not disabled ACPI in the BIOS, and other than that, ignore the messages if everything seems to be working.

 

Joe L.

Link to comment

It wasn't causing a problem so I ignored it.  Now it appears that it is causing trouble.  Suddenly my write speeds on all drives have dropped to virtually 0.  I am getting the following errors when I try to write a file . . .

 

Oct 29 12:32:00 Tower cache_dirs: ----------------------------------------------

Oct 29 12:32:00 Tower cache_dirs: cache_dirs process ID 1975 started, To terminate it, type: cache_dirs -q

Oct 29 12:39:20 Tower kernel: ata13.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors)

Oct 29 12:39:20 Tower kernel: ata13.00: failed command: SMART (Minor Issues)

Oct 29 12:39:20 Tower kernel: ata13.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in (Drive related)

Oct 29 12:39:20 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors)

Oct 29 12:39:20 Tower kernel: ata13.00: status: { DRDY } (Drive related)

Oct 29 12:39:20 Tower kernel: ata13: hard resetting link (Minor Issues)

Oct 29 12:39:21 Tower kernel: ata13: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related)

Oct 29 12:39:21 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110413/psargs-359) (Errors)

Oct 29 12:39:21 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node f506c210), AE_NOT_FOUND (20110413/psparse-536) (Errors)

Oct 29 12:39:21 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20110413/psargs-359) (Errors)

Oct 29 12:39:21 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT4._GTF] (Node f506c210), AE_NOT_FOUND (20110413/psparse-536) (Errors)

Oct 29 12:39:21 Tower kernel: ata13.00: configured for UDMA/133 (Drive related)

Oct 29 12:39:21 Tower kernel: ata13: EH complete (Drive related)

 

Reading is still fine. 

 

I looked in the bios but can not find any reference to ACPI.

 

Help!

Link to comment

It's happening on all 11 disks in the array so I doubt a smart report will help but I'm running one now will attach when complete.

 

Syslog is attached

 

Smart Report for Disk 11

 

=== START OF INFORMATION SECTION ===

Model Family:    Western Digital Caviar Green (Adv. Format) family

Device Model:    WDC WD20EARS-00MVWB0

Serial Number:    WD-WCAZA1585472

Firmware Version: 51.0AB51

User Capacity:    2,000,398,934,016 bytes

Device is:        In smartctl database [for details use: -P show]

ATA Version is:  8

ATA Standard is:  Exact ATA specification draft version not indicated

Local Time is:    Tue Oct 30 10:28:55 2012 ICT

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

 

=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED

 

General SMART Values:

Offline data collection status:  (0x84) Offline data collection activity

was suspended by an interrupting command from host.

Auto Offline Data Collection: Enabled.

Self-test execution status:      (  0) The previous self-test routine completed

without error or no self-test has ever

been run.

Total time to complete Offline

data collection: (39480) seconds.

Offline data collection

capabilities: (0x7b) SMART execute Offline immediate.

Auto Offline data collection on/off support.

Suspend Offline collection upon new

command.

Offline surface scan supported.

Self-test supported.

Conveyance Self-test supported.

Selective Self-test supported.

SMART capabilities:            (0x0003) Saves SMART data before entering

power-saving mode.

Supports SMART auto save timer.

Error logging capability:        (0x01) Error logging supported.

General Purpose Logging supported.

Short self-test routine

recommended polling time: (  2) minutes.

Extended self-test routine

recommended polling time: ( 255) minutes.

Conveyance self-test routine

recommended polling time: (  5) minutes.

SCT capabilities:       (0x3035) SCT Status supported.

SCT Feature Control supported.

SCT Data Table supported.

 

SMART Attributes Data Structure revision number: 16

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG    VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate    0x002f  200  200  051    Pre-fail  Always      -      0

  3 Spin_Up_Time            0x0027  167  164  021    Pre-fail  Always      -      6641

  4 Start_Stop_Count        0x0032  097  097  000    Old_age  Always      -      3161

  5 Reallocated_Sector_Ct  0x0033  200  200  140    Pre-fail  Always      -      0

  7 Seek_Error_Rate        0x002e  200  200  000    Old_age  Always      -      0

  9 Power_On_Hours          0x0032  079  079  000    Old_age  Always      -      15946

10 Spin_Retry_Count        0x0032  100  100  000    Old_age  Always      -      0

11 Calibration_Retry_Count 0x0032  100  100  000    Old_age  Always      -      0

12 Power_Cycle_Count      0x0032  100  100  000    Old_age  Always      -      349

192 Power-Off_Retract_Count 0x0032  200  200  000    Old_age  Always      -      210

193 Load_Cycle_Count        0x0032  196  196  000    Old_age  Always      -      14300

194 Temperature_Celsius    0x0022  114  103  000    Old_age  Always      -      36

196 Reallocated_Event_Count 0x0032  200  200  000    Old_age  Always      -      0

197 Current_Pending_Sector  0x0032  200  200  000    Old_age  Always      -      0

198 Offline_Uncorrectable  0x0030  200  200  000    Old_age  Offline      -      0

199 UDMA_CRC_Error_Count    0x0032  200  200  000    Old_age  Always      -      0

200 Multi_Zone_Error_Rate  0x0008  200  200  000    Old_age  Offline      -      0

 

SMART Error Log Version: 1

No Errors Logged

 

SMART Self-test log structure revision number 1

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error

# 1  Short offline      Completed without error      00%    15939        -

syslog-2012-10-30.txt

Link to comment

You are using Bios rev.09

 

Oct 29 12:31:05 Tower kernel: DMI: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Z77X-D3H, BIOS F9 05/31/2012

 

I suspect you have rev 1.0 of the motherboard (there is also rev.1.1) and the BIOS is now up to F15 - http://www.gigabyte.com/products/product-page.aspx?pid=4144#bios

 

Flash the BIOS, restore the default values, then go back and disable any unused hardware features (audio, serial and parallel ports, firewire, IDE controllers, etc.) and give it a try.

 

Link to comment

Thanks for the suggestions.  I tried that but it hasn't helped except I am no longer getting error messages in the sys log.  However write speeds are 200 - 600k (yes k).  Read speeds are normal.  Huh, just as I was typing that a copy I had running aborted and the same errors are back in the syslog.

 

Any other ideas?

 

I've attached a new syslog with the updated bios.

 

syslog-2012-10-31.txt

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.