linux-kernel - Re: 2.6.34-rc2 breaks via82cxxx Host Protected Area

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100327020934.GA8224@spacedout.fries.net>
Date:	Fri, 26 Mar 2010 21:09:35 -0500
From:	David Fries <david@...es.net>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: 2.6.34-rc2 breaks via82cxxx Host Protected Area

On Fri, Mar 26, 2010 at 08:42:26PM -0400, Jeff Garzik wrote:
> On 03/26/2010 08:36 PM, David Fries wrote:
>> On Fri, Mar 26, 2010 at 08:12:26PM -0400, Jeff Garzik wrote:
>>> On 03/26/2010 07:21 PM, David Fries wrote:
>>>> The kernel fails to see the entire disk with 2.6.34-rc2 with VIA
>>>> vt82c586b chipset.  I tracked it down to commit
>>>> f931a5d5785d7b7c44871bd7ad2762e29dfddf29 "via82cxxx: workaround h/w
>>>> bugs" and reverting just that one solves the problem, or just
>>>> commenting out just one outb write in that change.
>>>>
>>>> via82cxxx 0000:00:07.1: VIA vt82c586b (rev 41) IDE UDMA33
>>>> via82cxxx 0000:00:07.1: IDE controller (0x1106:0x0571 rev 0x06)
>>>> via82cxxx 0000:00:07.1: not 100% native mode: will probe irqs later
>>>>
>>>> Note the kernel panic is intentional as I'm given the test kernel an
>>>> invalid root device, so that I can suspend to disk, try a kernel,
>>>> resume and pick up where I left off.  It does have a side benefit of
>>>> dumping the size of all partitions.
>>>>
>>>> 2.6.34-rc2 unmodified, fails and sees 30985416 KiB for the last
>>>> partition.
>>>> ide-gd driver 1.18
>>>> hda: max request size: 128KiB
>>>> hda: 66055248 sectors (33820 MB) w/7936KiB Cache, CHS=65531/16/63
>>>> hda: cache flushes supported
>>>>    hda: hda1 hda2 hda3
>>>> hda: p3 size 236037312 exceeds device capacity, enabling native capacity
>>>> hda: p3 size 236037312 exceeds device capacity, limited to end of disk
>>>> ide-cd driver 5.00
>>>> ...
>>>> Please append a correct "root=" boot option; here are the available partitions:
>>>> 0300        33027624 hda driver: ide-gd
>>>>     0301           49391 hda1
>>>>     0302         1992816 hda2
>>>>     0303        30985416 hda3
>>>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(22,2)

> All these errors related to unknown-block(22,2) are it trying to find  
> /dev/hdX, when libata uses the SCSI block devices /dev/sdX
>
> These errors are unrelated to HPA, and are a standard issue encountered  
> when moving from legacy IDE driver to libata.

added
libata.dma=0 libata.ignore_hpa=1
and it's showing the full disk again, thanks for pointing that out,
I'm just not used to giving module parameters on the kernel command
line.  Now I'll see what Bartlomiej Zolnierkiewicz has to say about
his patch which broke via82cxxx.

scsi0 : pata_via
scsi1 : pata_via
ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0xe400 irq 14
ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0xe408 irq 15
ata1.00: HPA unlocked: 66055248 -> 240121728, native 240121728
ata1.00: ATA-7: Maxtor 6Y120P0, YAR41BW0, max UDMA/133
ata1.00: 240121728 sectors, multi 16: LBA 
ata1.00: configured for PIO4
scsi 0:0:0:0: Direct-Access     ATA      Maxtor 6Y120P0   YAR4 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 240121728 512-byte logical blocks: (122 GB/114 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
ata2.01: ATAPI: PLEXTOR CD-R   PX-W4012A, 1.06, max UDMA/33
ata2.01: configured for PIO4
scsi 1:0:1:0: CD-ROM            PLEXTOR  CD-R   PX-W4012A 1.06 PQ: 0 ANSI: 5
...
VFS: Cannot open root device "1602" or unknown-block(22,2)
Please append a correct "root=" boot option; here are the available partitions:
0800       120060864 sda driver: sd
  0801           49391 sda1
  0802         1992816 sda2
  0803       118018656 sda3
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(22,2)

-- 
David Fries <david@...es.net>
http://fries.net/~david/ (PGP encryption key available)
--
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/