Bug 3733

Summary: x86_64 unknown partition table with Windows Logical Disk Manger compiled
Product: File System Reporter: Rob Rosenfeld (rob)
Component: OtherAssignee: Andries Brouwer (aeb)
Status: CLOSED CODE_FIX    
Severity: normal    
Priority: P2    
Hardware: i386   
OS: Linux   
Kernel Version: 2.6.7, 2.6.8, 2.6.9 x86_64 Subsystem:
Regression: --- Bisected commit-id:
Attachments: .config

Description Rob Rosenfeld 2004-11-11 10:15:27 UTC
Distribution:          Gentoo gentoo-dev-sources 2.6.9-r1
Hardware Environment:  I-Will DK8N w/ nForce3 250 
Software Environment:  see .config attached
Problem Description:   If I compile the kernel with Windows Logical Disk Manager
support, I get a kernel panic on boot.  I have not tried other Advanced
Partition types.  I have tried where my boot drive is PATA, SATA using
deprecated support, and SATA using libata.  I have not tried on x86.  

snips from dmesg when boot drive is on SATA using libata.  similar messages
occur for other scenarios:

scsi1 : sata_nv
        . . . drive details . . .
SCSI device sda:  . . . more details . . .
SCSI device sda: drive cache: write back
        /dev/scsi/host0/bus0/target0/lun0: unknown partition table
.
.
clipped dmesg
.
.
VFS: Cannot open root device "sda3" or unknown-block(8,3)
Please append a correct "root=" boot option
Kernel panic: VFS:  Unable to mount root fs on sda3 

The same issue also seemst to be discussed in http://kerneltrap.org/node/view/970

The bug was first submitted to Gentoo
(http://bugs.gentoo.org/show_bug.cgi?id=67597) but they indicate it belongs
upstream.  

Steps to reproduce: 
1.  in make menuconfig hit Y on 
File Systems -> Partition Types -> Advanced Partition Selection 
and 
Advanced Partition Selection -> Windows Logical Disk Manager (Dynamic Disk)
support (NEW)
2.  Select AMD-Opteron/Athlon64 under 
Processor type and features -> Processor family
Comment 1 Rob Rosenfeld 2004-11-11 10:16:21 UTC
Created attachment 4017 [details]
.config

config that generates bug attached
Comment 2 Andries Brouwer 2004-11-19 06:40:00 UTC
User error caused by confusing configuration setup.
Improved Kconfig.