| View previous topic :: View next topic |
| Author |
Message |
meyerm
Veteran
Joined: 27 Jun 2002
Posts: 1311
Location: Munich / Germany
|
 Posted: Fri Apr 07, 2006 4:21 pm Post subject: strange "hangups" with a new DELL latitude D810 |
 |
|
Hi there,
first let me say, the problem ist not deterministic (of course not... :-/ ). I can not reproduce it - it just happens sometimes.
From time to time, my new DELL notebook simply hangs when it ran several hours (but then it is also capable of running 3 days even over night without having problems). Running programs continue to run, but nothing can be started (so a login is also impossible). I redirected the log-output to a console so I could at least have a look at it. The reason is that Linux can no longer access the harddrive. This happened with some 2.6.15 kernels and also with the 2.6.16 kernels (I'm using the gentoo-sources).
The error message last time was (there are perhaps typing errors since I had to write it from the screen... by hand! With a pencil! To paper!  ).
| Code: | ata1: command 0x35 timeout, stat 0xd0 host-stat 0x24
ata1: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status 0xd0 { Busy }
sd 0:0:0:0: SCSI error: return code = 0x8000002
sda: Current: sense key=0xb
ASC=0x47 ASCQ=0x0
end_request: I/O Error, dev sda, sector 97884108
Buffer I/O error on device sda6, logical block 0
lost page write due to I/O error on sda6
ATA: abnormal status 0xD0 in port 0x1F7
ATA: abnormal status 0xD0 in port 0x1F7
ATA: abnormal status 0xD0 in port 0x1F7 |
Any more questions? Thank you very much for reading! |
|
| Back to top |
|
 |
PMcCauley
Apprentice
Joined: 14 Mar 2006
Posts: 283
Location: Alberta, Canada
|
| Posted: Fri Apr 07, 2006 8:21 pm Post subject: |
|
|
Have you ran the diagnostics? F12 on the dell splash screen and choose diagnostics. Other than that you could double check your kernel configuration and watch for chipset and SATA related items.
Patrick |
|
| Back to top |
|
|
meyerm
Veteran
Joined: 27 Jun 2002
Posts: 1311
Location: Munich / Germany
|
| Posted: Sun Apr 09, 2006 12:16 am Post subject: |
|
|
Hi,
thanks for answering and sorry for my late reaction. But I needed some time where I didn't use the laptop. So today I ran all the tests from the firmware diagnostics and also everything from the diag-partition. That took some time. But no errors were found. Also the harddrive seems to be ok.
The kernel has the relevant options set:
| Code: | CONFIG_BLK_DEV_PIIX=y
CONFIG_SCSI_ATA_PIIX=y
CONFIG_SCSI_SATA=y
CONFIG_SCSI_SATA_INTEL_COMBINED=y |
I also don't see anything special within the dmesg output.
| Code: | Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide0: I/O resource 0x1F0-0x1F7 not free.
ide0: ports already in use, skipping probe
Probing IDE interface ide1...
input: AT Translated Set 2 keyboard as /class/input/input0
input: PS/2 Mouse as /class/input/input1
input: AlpsPS/2 ALPS GlidePoint as /class/input/input2
hdc: _NEC DVD+/-RW ND-6650A, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
libata version 1.20 loaded.
ata_piix 0000:00:1f.2: version 1.05
ACPI: PCI Interrupt 0000:00:1f.2[B] -> Link [LNKB] -> GSI 7 (level, low) -> IRQ 7
ata: 0x170 IDE port busy
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xBFA0 irq 14
ata1: dev 0 cfg 49:2f00 82:346b 83:7f09 84:4003 85:3469 86:3c09 87:4003 88:203f
ata1: dev 0 ATA-6, max UDMA/100, 195371568 sectors: LBA48
ata1(0): applying bridge limits
ata1: dev 0 configured for UDMA/100
scsi0 : ata_piix
Vendor: ATA Model: ST9100823A Rev: 8.03
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
sd 0:0:0:0: Attached scsi disk sda |
The smartmon tools are showing the following (it's a sata hd, but I guess this works even though there are some glitches like temperature...). Are the values ok?
| Code: | yavin ~ # smartctl -d ata -a /dev/sda
smartctl version 5.33 [i686-pc-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: ST9100823A
Serial Number: 3LG1RNP0
Firmware Version: 8.03
User Capacity: 100,030,242,816 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 6
ATA Standard is: ATA/ATAPI-6 T13 1410D revision 2
Local Time is: Sun Apr 9 02:12:07 2006 CEST
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: (0x82) Offline data collection activity
was completed without error.
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: ( 426) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No 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.
No General Purpose Logging support.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 111) minutes.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 064 053 034 Pre-fail Always - 214685111
3 Spin_Up_Time 0x0003 095 095 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 101
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 072 060 030 Pre-fail Always - 15577414
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1540
10 Spin_Retry_Count 0x0013 100 100 034 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 109
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 109
193 Load_Cycle_Count 0x0032 041 041 000 Old_age Always - 119806
194 Temperature_Celsius 0x0022 043 044 000 Old_age Always - 43 (Lifetime Min/Max 0/17)
195 Hardware_ECC_Recovered 0x001a 064 053 000 Old_age Always - 214685111
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0
202 TA_Increase_Count 0x0032 100 253 000 Old_age Always - 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% 1533 -
# 2 Short offline Completed without error 00% 0 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay. |
Thank you,
M |
|
| Back to top |
|
|
kerstman
n00b
Joined: 27 Nov 2004
Posts: 68
|
| Posted: Sun Apr 09, 2006 10:11 am Post subject: |
|
|
| I occasionally get the same error. I'm using an AMD 64, with 2 Serial ATA drives. One drive I had for some time, and no errors. I then installed a second Western Digital drive, and rebuilt the system to use LVM2. That was fine for a while, but now I get these random lockups as well. |
|
| Back to top |
|
|
Maf
Guru
Joined: 15 May 2005
Posts: 310
|
| Posted: Sun Nov 12, 2006 4:31 pm Post subject: |
|
|
Hi there, recently I encounter this error as well
| Quote: |
I redirected the log-output to a console so I could at least have a look at it.
|
can you tell me where to set this? |
|
| Back to top |
|
|
meyerm
Veteran
Joined: 27 Jun 2002
Posts: 1311
Location: Munich / Germany
|
| Posted: Sun Nov 12, 2006 4:44 pm Post subject: |
|
|
| Maf wrote: | | Hi there, recently I encounter this error as well |
That's bad to hear  I didn't have this problem for some time now - I'm always updating to the newest stuff in ~x86
| Maf wrote: | | can you tell me where to set this? |
That depends on you syslogd. When you're using syslog-ng f.ex., you could add the following line to your config (/etc/syslog-ng/syslog-ng.conf):
| Code: |
source src_all {
unix-stream("/dev/log");
pipe("/proc/kmsg");
internal();
};
destination console_all { pipe("/dev/tty12"); };
log { source(src_all); destination(console_all); };
|
Then you get the messages on you console nr. 12.
Good luck! |
|
| Back to top |
|
|
|
Kernel & Hardware
