Bug 327518

Summary: "HPA unlocked" causes wrong disk geometry
Product: [openSUSE] openSUSE 10.3 Reporter: Forgotten User eTk6BCeiKJ <forgotten_eTk6BCeiKJ>
Component: KernelAssignee: E-mail List <kernel-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: forgotten_eTk6BCeiKJ, jkosina
Version: RC 1   
Target Milestone: ---   
Hardware: i386   
OS: openSUSE 10.3   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Forgotten User eTk6BCeiKJ 2007-09-22 20:14:46 UTC
installing opensuse 10.3 RC1
HPA unlocked seems to leads to an incorrect disk geometry (5GB instead of 40GB)

dmesg output

SCSI subsystem initialized
libata version 3.00 loaded.
ata_piix 0000:00:1f.1: version 2.11
PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1f.1 to 64
scsi0 : ata_piix
scsi1 : ata_piix
ata1: PATA max UDMA/100 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001ffa0 irq 14
ata2: PATA max UDMA/100 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001ffa8 irq 15
ata1.00: ATA-5: ST380021A, 3.19, max UDMA/100
ata1.00: 156301488 sectors, multi 16: LBA
ata1.01: HPA unlocked: 78125000 -> 11056496, native 78165360
ata1.01: ATA-5: WDC WD400BB-75CAA0, 16.06V16, max UDMA/100
ata1.01: 11056496 sectors, multi 16: LBA
ata1.00: configured for UDMA/100
ata1.01: configured for UDMA/100
ata2.00: ATAPI: _NEC DV-5800A, 1.92, max UDMA/33
ata2.01: ATAPI: LITE-ON DVDRW SOHW-832S, VS0M, max UDMA/33
ata2.00: configured for UDMA/33
ata2.01: configured for UDMA/33
scsi 0:0:0:0: Direct-Access     ATA      ST380021A        3.19 PQ: 0 ANSI: 5
scsi 0:0:1:0: Direct-Access     ATA      WDC WD400BB-75CA 16.0 PQ: 0 ANSI: 5
scsi 1:0:0:0: CD-ROM            _NEC     DV-5800A         1.92 PQ: 0 ANSI: 5
scsi 1:0:1:0: CD-ROM            LITE-ON  DVDRW SOHW-832S  VS0M PQ: 0 ANSI: 5


My /dev/sdb disk is now 688 cylinders instead of 4863

More error occured after that

 sdb1 sdb2 sdb3 sdb4 < >
 sdb: p2 exceeds device capacity
 sdb: p3 exceeds device capacity
 sdb: p4 exceeds device capacity

attempt to access beyond end of device
sdb: rw=0, want=17446406, limit=11056496
Buffer I/O error on device sdb2, logical block 7662912
attempt to access beyond end of device
sdb: rw=0, want=35503652, limit=11056496
Buffer I/O error on device sdb4, logical block 0
attempt to access beyond end of device
sdb: rw=0, want=35503652, limit=11056496
Buffer I/O error on device sdb4, logical block 0
attempt to access beyond end of device
sdb: rw=0, want=35503652, limit=11056496
Buffer I/O error on device sdb4, logical block 0
attempt to access beyond end of device




modinfo libata
filename:       /lib/modules/2.6.22.5-23-default/kernel/drivers/ata/libata.ko
version:        3.00
license:        GPL
description:    Library module for ATA devices
author:         Jeff Garzik
srcversion:     29B094F9DE351C57BA2297A
depends:        scsi_mod
supported:      yes
vermagic:       2.6.22.5-23-default SMP mod_unload 586
parm:           atapi_enabled:Enable discovery of ATAPI devices (0=off, 1=on) (int)
parm:           atapi_dmadir:Enable ATAPI DMADIR bridge support (0=off, 1=on) (int)
parm:           atapi_passthru16:Enable ATA_16 passthru for ATAPI devices; on by default (0=off, 1=on) (int)
parm:           fua:FUA support (0=off, 1=on) (int)
parm:           ignore_hpa:Ignore HPA limit (0=keep BIOS limits, 1=ignore limits, using full disk) (int)
parm:           pata_dma:Use DMA on PATA devices (int)
parm:           ata_probe_timeout:Set ATA probing timeout (seconds) (int)
parm:           noacpi:Disables the use of ACPI in suspend/resume when set (int)
Comment 1 Forgotten User eTk6BCeiKJ 2007-09-22 21:08:07 UTC
when booting with libata.ignore_hpa=1
same result
ata1.01: HPA unlocked: 78125000 -> 11056496, native 78165360


when booting with libata.ignore_hpa=0
works fine
ata1.01: HPA detected: current 78125000, native 78165360

Comment 2 Jiri Kosina 2007-09-24 11:50:43 UTC
This is very probably duplicate of bug #325552. If you feel different, please reopen the bug.

*** This bug has been marked as a duplicate of bug 325552 ***