Re: [bug, 2.5.29, (not IDE)] partition table (not) corruption?

[Marcin Dalecki]

Uz.ytkownik Ingo Molnar napisa?:
> On Thu, 8 Aug 2002, Marcin Dalecki wrote:
> 
> 
>>If you look at the boot messages from a kernel:
>>
>>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
>>  hda: 78140160 sectors, CHS=77520/16/63, UDMA(33)
>>  hda: hda1 hda4
>>
>>You can actually see the CHS info field.
> 
> 
> okay, here are the 2.4.18(-ish) and 2.5.30 CHS fields:
> 
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
> hda: 8418816 sectors (4310 MB) w/80KiB Cache, CHS=524/255/63, UDMA(33)
> hdc: 40132503 sectors (20548 MB) w/1900KiB Cache, CHS=39813/16/63, UDMA(33)
> hdb: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache
> 
> hda: QUANTUM FIREBALL SE4.3A, DISK drive
> hdb: RICOH CD-R/RW MP7083A, ATAPI CD/DVD-ROM drive
> hdc: QUANTUM FIREBALLP LM20.5, DISK drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
>  hda: 8418816 sectors w/80KiB Cache, CHS=14848/9/63, UDMA(33)
>  hda: hda1 hda2 < hda5 hda6 >
>  hdc: 40132503 sectors w/1900KiB Cache, CHS=39813/16/63, UDMA(33)
>  hdc: hdc1
> hdb: Disabling (U)DMA for RICOH CD-R/RW MP7083A
> hdb: DMA disabled
> hdb: ATAPI 32X CD-ROM CD-R/RW drive, 2048kB Cache
> 
> i have the bootlogs of this system back to 2.5.25 only, which also shows
> the wrong(?) CHS:
> 
> Linux version 2.5.25 (mingo@mars) (gcc version 2.96 20000731 (Red Hat Linux 7.2
> 2.96-101.9)) #3 SMP Tue Jul 9 21:12:18 CEST 2002
> 
> hda: QUANTUM FIREBALL SE4.3A, DISK drive
> hdb: RICOH CD-R/RW MP7083A, ATAPI CD/DVD-ROM drive
> hdc: QUANTUM FIREBALLP LM20.5, DISK drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> ide1 at 0x170-0x177,0x376 on irq 15
>  hda: 8418816 sectors w/80KiB Cache, CHS=14848/9/63
>  hda: [PTBL] [524/255/63] hda1 hda2 < hda5 hda6 >

^^^^^^^^^^^^^^^^^^^^^^^^^^^ This is actually the interresting
part. Well this is actually printed by
the partition grocking code. 255/63 *is* indicating LBA (linear)
access to the drive. It is really lilo who didn't parse the partition
table and was relying on the value returned by GETGEO ioctl instead.
At least lilo should automatically resort to LBA if C > 1024.

>  hdc: 40132503 sectors w/1900KiB Cache, CHS=39813/16/63
>  hdc: hdc1
> 
> 	Ingo
> 
>