lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 19 Mar 2007 08:09:24 -0400 From: Jeff Garzik <jeff@...zik.org> To: Christian <christiand59@....de> CC: linux-kernel@...r.kernel.org Subject: Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ Christian wrote: > On Monday 19 March 2007 03:48:14 you wrote: >> Christian wrote: >>> On Sunday 18 March 2007 06:43:09 you wrote: >>>> Christian wrote: >>>>>> This does indeed look like a drive side issue to me (the controller is >>>>>> reporting CPBs with response flags 2 which as far as I can tell >>>>>> indicates it's still waiting for the drive to complete the request). >>>>> I have been using this hw-config (SATA II, NCQ) since the nvidia ADMA >>>>> support made it in the -mm kernel (maybe around 2.6.19-mm? or even >>>>> earlyer). I'm seeing this problem excessively since I upgraded to >>>>> 2.6.21-rc3-mm1. I think something got broken recently... >>>> Can you post the result of "hdparm -I /dev/sdX"? >>> Output generated on 2.6.21-rc3-mm1 #3 SMP PREEMPT >>> >>> user@...ntu:~$ sudo hdparm -I /dev/sda >>> >>> /dev/sda: >>> >>> ATA device, with non-removable media >>> Model Number: SAMSUNG HD401LJ >>> Serial Number: S0HVJ1FL900207 >>> Firmware Revision: ZZ100-15 >>> Standards: >>> Used: ATA/ATAPI-7 T13 1532D revision 4a >>> Supported: 7 6 5 4 >>> Configuration: >>> Logical max current >>> cylinders 16383 16383 >>> heads 16 16 >>> sectors/track 63 63 >>> -- >>> CHS current addressable sectors: 16514064 >>> LBA user addressable sectors: 268435455 >>> LBA48 user addressable sectors: 781422768 >>> device size with M = 1024*1024: 381554 MBytes >>> device size with M = 1000*1000: 400088 MBytes (400 GB) >> That's a fairly recent drive. Does the problem go away if you downgrade >> the kernel? > > Yes, for me the problem was introduced recently. I have moved around terabytes > (sic!) on my discs with older kernels and I never got errors. I may have missed the answer to this before, but: does the problem go away if you disable preempt? Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists