Can not find the cdrom device in /dev/ on xen 3.0.3

Can not find the cdrom device in /dev/ on xen 3.0.3

[Liang Yang]

Hello,

I just did a fresh installation of Xen 3.0.3. However, I can not find my 
cd-rom device under /dev/ after I booted into Xen. If I booted into Linux 
native (RHELAS 4.4), CD-ROM device is there and listed as /dev/cdrom. I know 
Xen changed the CD-ROM access mode from HVM domain. But for Xen domain0, it 
should still be listed as /dev/cdrom, right?

I think the driver for CD-ROM must be already loaded and it is hided by Xen 
somehow. I checked a Linux Server beta version which has integrated Xen on 
the same platform, I can find the cdrom device in /dev/. I remember Xen 
3.0.2 does not have this problem either.

Could anyone share some solutions?

Thanks,

Liang

Can not find the cdrom device in /dev/ after booted into xen(3.0.3)

[Liang Yang]

Hello,

I just did a fresh installation of Xen 3.0.3. However, I can not find my
cd-rom device under /dev/ after I booted into Xen. If I booted into Linux
native (RHELAS 4.4), CD-ROM device is there and listed as /dev/cdrom. I know
Xen changed the CD-ROM access mode from HVM domain. But for Xen domain0, it
should still be listed as /dev/cdrom, right?

I think the driver for CD-ROM must be already loaded and it is hided by Xen
somehow. I checked a Linux Server beta version which has integrated Xen on
the same platform, I can find the cdrom device in /dev/. I remember Xen
3.0.2 does not have this problem either.

Could anyone share some solutions?

Thanks,

Liang

RE: [Xen-users] Can not find the cdrom device in /dev/ after booted into xen(3.0.3)

[Petersson, Mats]

 

> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com 
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Liang Yang
> Sent: 01 December 2006 16:12
> To: xen-devel@lists.xensource.com
> Cc: xen-users@lists.xensource.com
> Subject: [Xen-users] Can not find the cdrom device in /dev/ 
> after booted into xen(3.0.3)
> 
> Hello,
> 
> I just did a fresh installation of Xen 3.0.3. However, I can 
> not find my
> cd-rom device under /dev/ after I booted into Xen. If I 
> booted into Linux
> native (RHELAS 4.4), CD-ROM device is there and listed as 
> /dev/cdrom. I know
> Xen changed the CD-ROM access mode from HVM domain. But for 
> Xen domain0, it
> should still be listed as /dev/cdrom, right?

/dev/cdrom is a "link" to the actual /dev/[sh]d[abcd] device that is the
CDROM drive. As far as I understand, it's normally created by the
distributions initrd. You may be able to disassemble your distributions
initrd and find the line that creates this link - but the fact is that
different distributions do this slightly differently. 

Much easier to just use /dev/[sh]d[abcd] for your cdrom. 

--
Mats
> 
> I think the driver for CD-ROM must be already loaded and it 
> is hided by Xen
> somehow. I checked a Linux Server beta version which has 
> integrated Xen on
> the same platform, I can find the cdrom device in /dev/. I 
> remember Xen
> 3.0.2 does not have this problem either.
> 
> Could anyone share some solutions?
> 
> Thanks,
> 
> Liang
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 
> 
> 

Re: [Xen-users] Can not find the cdrom device in /dev/ after booted into xen(3.0.3)

[Liang Yang]

Hi Mats,

Thanks for your reply. I still have two questions:
1. Your answer still does not explain why Linux native listed the CD-ROM 
device as /dev/cdrom while Xen Linux (using the same distribution, i.e. RHEL 
Server 4.4) does not.

2. If I want to install HVM Linux from CDROM instead of file image, how can 
I define the cdrom in .hvm file:
disk = [ 'phy:/dev/sdb,hda,w', 'phy:/dev/cdrom,hdc:cdrom,r' ] will not work 
as /dev/cdrom is not available. Then I tried disk = [ 'phy:/dev/sdb,hda,w', 
'phy:/dev/hdc,hdc:cdrom,r' ]. It still does not work as /dev/hdc is not 
available either.

How can I create /dev/hdc for my cd-rom?

Regards,

Liang

----- Original Message ----- 
From: "Petersson, Mats" <Mats.Petersson@amd.com>
To: "Liang Yang" <multisyncfe991@hotmail.com>; 
<xen-devel@lists.xensource.com>
Cc: <xen-users@lists.xensource.com>
Sent: Friday, December 01, 2006 9:22 AM
Subject: RE: [Xen-users] Can not find the cdrom device in /dev/ after booted 
into xen(3.0.3)




> -----Original Message-----
> From: xen-users-bounces@lists.xensource.com
> [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Liang Yang
> Sent: 01 December 2006 16:12
> To: xen-devel@lists.xensource.com
> Cc: xen-users@lists.xensource.com
> Subject: [Xen-users] Can not find the cdrom device in /dev/
> after booted into xen(3.0.3)
>
> Hello,
>
> I just did a fresh installation of Xen 3.0.3. However, I can
> not find my
> cd-rom device under /dev/ after I booted into Xen. If I
> booted into Linux
> native (RHELAS 4.4), CD-ROM device is there and listed as
> /dev/cdrom. I know
> Xen changed the CD-ROM access mode from HVM domain. But for
> Xen domain0, it
> should still be listed as /dev/cdrom, right?

/dev/cdrom is a "link" to the actual /dev/[sh]d[abcd] device that is the
CDROM drive. As far as I understand, it's normally created by the
distributions initrd. You may be able to disassemble your distributions
initrd and find the line that creates this link - but the fact is that
different distributions do this slightly differently.

Much easier to just use /dev/[sh]d[abcd] for your cdrom.

--
Mats
>
> I think the driver for CD-ROM must be already loaded and it
> is hided by Xen
> somehow. I checked a Linux Server beta version which has
> integrated Xen on
> the same platform, I can find the cdrom device in /dev/. I
> remember Xen
> 3.0.2 does not have this problem either.
>
> Could anyone share some solutions?
>
> Thanks,
>
> Liang
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
>
> 

Re: Re: [Xen-users] Can not find the cdrom device in /dev/ after booted into xen(3.0.3)

[Keir Fraser]

On 1/12/06 16:38, "Liang Yang" <multisyncfe991@hotmail.com> wrote:

> 2. If I want to install HVM Linux from CDROM instead of file image, how can
> I define the cdrom in .hvm file:
> disk = [ 'phy:/dev/sdb,hda,w', 'phy:/dev/cdrom,hdc:cdrom,r' ] will not work
> as /dev/cdrom is not available. Then I tried disk = [ 'phy:/dev/sdb,hda,w',
> 'phy:/dev/hdc,hdc:cdrom,r' ]. It still does not work as /dev/hdc is not
> available either.
> 
> How can I create /dev/hdc for my cd-rom?

When you boot native RHEL4.4, what is /dev/cdrom a symlink to? You should
try using the target of the symlink as the physical device target in your
HVM config file. If the target of the symlink also does not exist when
running on Xen then it is likely that your XenLinux kernel does not include
an appropriate driver for your CDROM device. Perhaps it is a SATA drive
connected to a SATA chipset for which our kernel does not have a driver?

 -- Keir

RE: [Xen-devel] Re: Can not find the cdrom device in /dev/ after booted into xen(3.0.3)

[Petersson, Mats]

 

> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com 
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
> Keir Fraser
> Sent: 01 December 2006 16:45
> To: Liang Yang; Petersson, Mats; xen-devel@lists.xensource.com
> Cc: xen-users@lists.xensource.com
> Subject: Re: [Xen-devel] Re: [Xen-users] Can not find the 
> cdrom device in /dev/ after booted into xen(3.0.3)
> 
> On 1/12/06 16:38, "Liang Yang" <multisyncfe991@hotmail.com> wrote:
> 
> > 2. If I want to install HVM Linux from CDROM instead of 
> file image, how can
> > I define the cdrom in .hvm file:
> > disk = [ 'phy:/dev/sdb,hda,w', 'phy:/dev/cdrom,hdc:cdrom,r' 
> ] will not work
> > as /dev/cdrom is not available. Then I tried disk = [ 
> 'phy:/dev/sdb,hda,w',
> > 'phy:/dev/hdc,hdc:cdrom,r' ]. It still does not work as 
> /dev/hdc is not
> > available either.
> > 
> > How can I create /dev/hdc for my cd-rom?
> 
> When you boot native RHEL4.4, what is /dev/cdrom a symlink 
> to? You should
> try using the target of the symlink as the physical device 
> target in your
> HVM config file. If the target of the symlink also does not exist when
> running on Xen then it is likely that your XenLinux kernel 
> does not include
> an appropriate driver for your CDROM device. Perhaps it is a 
> SATA drive
> connected to a SATA chipset for which our kernel does not 
> have a driver?

I'd say that the most likely scenario is that /dev/hdc isn't the device
that is your CDROM. If your hard-disk is /dev/sd<something>, then
chances are that the /dev/hda could be the CDROM drive (as, indeed, it
could be even on a machine that uses /dev/hd<something> as the "disk
device", since you could very well connect the first IDE controller to
the CDROM and the second to the DISK, or some such). 

--
Mats
> 
>  -- Keir
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 

Re: [Xen-devel] Re: Can not find the cdrom device in /dev/ after booted into xen(3.0.3)

[Liang Yang]

Hi Keir and Mats,

When I booted into native RHEL4.4, /dev/cdrom is linked to hda. My CD-ROM is 
the only IDE device and my OS hard disk is the SATA. When I booted into 
Xen(on the same platform with the same distribution) I can NOT find ANY hd* 
device under /dev/ (SATA hard disk is listed correctly though). So what Mats 
said does not apply here. Could this be a bug for Xen 3.0.3?

Best regards,

Liang

----- Original Message ----- 
From: "Keir Fraser" <keir@xensource.com>
To: "Liang Yang" <multisyncfe991@hotmail.com>; "Petersson, Mats" 
<Mats.Petersson@amd.com>; <xen-devel@lists.xensource.com>
Cc: <xen-users@lists.xensource.com>
Sent: Friday, December 01, 2006 9:44 AM
Subject: Re: [Xen-devel] Re: [Xen-users] Can not find the cdrom device in 
/dev/ after booted into xen(3.0.3)


> On 1/12/06 16:38, "Liang Yang" <multisyncfe991@hotmail.com> wrote:
>
>> 2. If I want to install HVM Linux from CDROM instead of file image, how 
>> can
>> I define the cdrom in .hvm file:
>> disk = [ 'phy:/dev/sdb,hda,w', 'phy:/dev/cdrom,hdc:cdrom,r' ] will not 
>> work
>> as /dev/cdrom is not available. Then I tried disk = [ 
>> 'phy:/dev/sdb,hda,w',
>> 'phy:/dev/hdc,hdc:cdrom,r' ]. It still does not work as /dev/hdc is not
>> available either.
>>
>> How can I create /dev/hdc for my cd-rom?
>
> When you boot native RHEL4.4, what is /dev/cdrom a symlink to? You should
> try using the target of the symlink as the physical device target in your
> HVM config file. If the target of the symlink also does not exist when
> running on Xen then it is likely that your XenLinux kernel does not 
> include
> an appropriate driver for your CDROM device. Perhaps it is a SATA drive
> connected to a SATA chipset for which our kernel does not have a driver?
>
> -- Keir
>
> 

Re: Re: [Xen-users] Can not find the cdrom device in /dev/ after booted into xen(3.0.3)

[Keir Fraser]

On 1/12/06 17:23, "Liang Yang" <multisyncfe991@hotmail.com> wrote:

> When I booted into native RHEL4.4, /dev/cdrom is linked to hda. My CD-ROM is
> the only IDE device and my OS hard disk is the SATA. When I booted into
> Xen(on the same platform with the same distribution) I can NOT find ANY hd*
> device under /dev/ (SATA hard disk is listed correctly though). So what Mats
> said does not apply here. Could this be a bug for Xen 3.0.3?

Where does your rootfs reside? Obviously not on an IDE HD I guess... Can you
send boot output of native and Xen kernels, and also output of lsmod?

 -- Keir

Re: Can not find the cdrom device in /dev/ after booted into xen(3.0.3)

[Tim Post]

On Fri, 2006-12-01 at 09:12 -0700, Liang Yang wrote:
> Hello,
> 
> I just did a fresh installation of Xen 3.0.3. However, I can not find my
> cd-rom device under /dev/ after I booted into Xen. If I booted into Linux
> native (RHELAS 4.4), CD-ROM device is there and listed as /dev/cdrom. I know
> Xen changed the CD-ROM access mode from HVM domain. But for Xen domain0, it
> should still be listed as /dev/cdrom, right?

Should be.

> I think the driver for CD-ROM must be already loaded and it is hided by Xen
> somehow. I checked a Linux Server beta version which has integrated Xen on
> the same platform, I can find the cdrom device in /dev/. I remember Xen
> 3.0.2 does not have this problem either.
> 
> Could anyone share some solutions?
> 

Please post the output of lsmod and lspci so the list can help you
diagnose the issue. My guess is your IDE was loaded via insmod in
linuxrc and was not picked up by a depmod when xen installed.

Uncommon, but not the first time I've seen it in RHEL.

> Thanks,
> 
> Liang
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

logs attached. Re: [Xen-users] Can not find the cdrom device in /dev/ afterbooted into xen(3.0.3)

[Liang Yang]

[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]

Hi Tim, Keir and Mats,

I attached all the detailed log files (text file format). The file extension 
indicate the version of environment. Please take a look.

Thanks,

Liang

----- Original Message ----- 
From: "Tim Post" <tim.post@netkinetics.net>
To: "Liang Yang" <multisyncfe991@hotmail.com>
Cc: <xen-devel@lists.xensource.com>; <xen-users@lists.xensource.com>
Sent: Friday, December 01, 2006 11:05 AM
Subject: Re: [Xen-users] Can not find the cdrom device in /dev/ afterbooted 
into xen(3.0.3)


> On Fri, 2006-12-01 at 09:12 -0700, Liang Yang wrote:
>> Hello,
>>
>> I just did a fresh installation of Xen 3.0.3. However, I can not find my
>> cd-rom device under /dev/ after I booted into Xen. If I booted into Linux
>> native (RHELAS 4.4), CD-ROM device is there and listed as /dev/cdrom. I 
>> know
>> Xen changed the CD-ROM access mode from HVM domain. But for Xen domain0, 
>> it
>> should still be listed as /dev/cdrom, right?
>
> Should be.
>
>> I think the driver for CD-ROM must be already loaded and it is hided by 
>> Xen
>> somehow. I checked a Linux Server beta version which has integrated Xen 
>> on
>> the same platform, I can find the cdrom device in /dev/. I remember Xen
>> 3.0.2 does not have this problem either.
>>
>> Could anyone share some solutions?
>>
>
> Please post the output of lsmod and lspci so the list can help you
> diagnose the issue. My guess is your IDE was loaded via insmod in
> linuxrc and was not picked up by a depmod when xen installed.
>
> Uncommon, but not the first time I've seen it in RHEL.
>
>> Thanks,
>>
>> Liang
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>
> 

[-- Attachment #2: boot.xen --]
[-- Type: application/octet-stream, Size: 4864 bytes --]

Dec  1 11:15:16 localhost syslog: syslogd startup succeeded
Dec  1 11:15:16 localhost syslog: klogd startup succeeded
Dec  1 11:15:16 localhost irqbalance: irqbalance startup succeeded
Dec  1 11:15:16 localhost portmap: portmap startup succeeded
Dec  1 11:15:16 localhost nfslock: rpc.statd startup succeeded
Dec  1 11:15:17 localhost rpcidmapd: rpc.idmapd startup succeeded
Dec  1 11:15:17 localhost netfs: Mounting other filesystems:  succeeded
Dec  1 11:15:17 localhost rc: Starting lm_sensors:  succeeded
Dec  1 11:15:17 localhost autofs: automount startup succeeded
Dec  1 11:15:18 localhost smartd: smartd startup succeeded
Dec  1 11:15:18 localhost acpid: acpid startup succeeded
Dec  1 04:14:22 localhost rc.sysinit: -e 
Dec  1 11:15:18 localhost rc: Starting hpoj:  succeeded
Dec  1 04:14:26 localhost start_udev: Starting udev:  succeeded 
Dec  1 04:14:32 localhost rc.sysinit: -e 
Dec  1 04:14:42 localhost sysctl: net.ipv4.ip_forward = 0 
Dec  1 04:14:42 localhost sysctl: net.ipv4.conf.default.rp_filter = 1 
Dec  1 04:14:42 localhost sysctl: net.ipv4.conf.default.accept_source_route = 0 
Dec  1 04:14:42 localhost sysctl: kernel.sysrq = 0 
Dec  1 04:14:42 localhost sysctl: kernel.core_uses_pid = 1 
Dec  1 04:14:42 localhost rc.sysinit: Configuring kernel parameters:  succeeded 
Dec  1 11:14:43 localhost date: Fri Dec  1 11:14:43 MST 2006 
Dec  1 11:14:43 localhost rc.sysinit: Setting clock  (localtime): Fri Dec  1 11:14:43 MST 2006 succeeded 
Dec  1 11:14:43 localhost rc.sysinit: Loading default keymap succeeded 
Dec  1 11:14:43 localhost rc.sysinit: Setting hostname localhost.localdomain:  succeeded 
Dec  1 11:14:43 localhost rc.sysinit: Checking root filesystem succeeded 
Dec  1 11:14:43 localhost rc.sysinit: Remounting root filesystem in read-write mode:  succeeded 
Dec  1 11:14:44 localhost lvm.static:   1 logical volume(s) in volume group VG_Dom8_Linux now active 
Dec  1 11:14:44 localhost rc.sysinit: Setting up Logical Volume Management: succeeded 
Dec  1 11:14:44 localhost rc.sysinit: Checking filesystems succeeded 
Dec  1 11:14:44 localhost rc.sysinit: Mounting local filesystems:  succeeded 
Dec  1 11:14:44 localhost rc.sysinit: Enabling local filesystem quotas:  succeeded 
Dec  1 11:14:45 localhost rc.sysinit: Enabling swap space:  succeeded 
Dec  1 11:14:45 localhost microcode_ctl: microcode_ctl startup succeeded 
Dec  1 11:14:45 localhost sysstat: Calling the system activity data collector (sadc):  
Dec  1 11:14:45 localhost sysstat:  
Dec  1 11:14:45 localhost rc: Starting sysstat:  succeeded 
Dec  1 11:14:45 localhost readahead_early: Starting background readahead:  
Dec  1 11:14:46 localhost rc: Starting readahead_early:  succeeded 
Dec  1 11:15:10 localhost kudzu:  succeeded 
Dec  1 11:15:10 localhost rc: Starting pcmcia:  succeeded 
Dec  1 11:15:10 localhost sysctl: net.ipv4.ip_forward = 0 
Dec  1 11:15:10 localhost sysctl: net.ipv4.conf.default.rp_filter = 1 
Dec  1 11:15:10 localhost sysctl: net.ipv4.conf.default.accept_source_route = 0 
Dec  1 11:15:21 localhost cups: cupsd startup succeeded
Dec  1 11:15:10 localhost sysctl: kernel.sysrq = 0 
Dec  1 11:15:10 localhost sysctl: kernel.core_uses_pid = 1 
Dec  1 11:15:10 localhost network: Setting network parameters:  succeeded 
Dec  1 11:15:11 localhost network: Bringing up loopback interface:  succeeded 
Dec  1 11:15:11 localhost ifup:  
Dec  1 11:15:21 localhost sshd:  succeeded
Dec  1 11:15:11 localhost ifup: Determining IP information for eth0... 
Dec  1 11:15:21 localhost xinetd: xinetd startup succeeded
Dec  1 11:15:11 localhost NET: /sbin/dhclient-script : updated /etc/resolv.conf 
Dec  1 11:15:11 localhost ifup:  done. 
Dec  1 11:15:11 localhost network: Bringing up interface eth0:  succeeded 
Dec  1 11:15:16 localhost network: Bringing up interface eth1:  succeeded 
Dec  1 11:15:22 localhost sendmail: sendmail startup succeeded
Dec  1 11:15:22 localhost sendmail: sm-client startup succeeded
Dec  1 11:15:23 localhost gpm: gpm startup succeeded
Dec  1 11:15:23 localhost iiim: htt startup succeeded
Dec  1 11:15:25 localhost canna:  succeeded
Dec  1 11:15:25 localhost crond: crond startup succeeded
Dec  1 11:15:26 localhost xfs: xfs startup succeeded
Dec  1 11:15:27 localhost anacron: anacron startup succeeded
Dec  1 11:15:27 localhost atd: atd startup succeeded
Dec  1 11:15:27 localhost readahead: Starting background readahead: 
Dec  1 11:15:27 localhost rc: Starting readahead:  succeeded
Dec  1 11:15:28 localhost messagebus: messagebus startup succeeded
Dec  1 11:15:29 localhost cups-config-daemon: cups-config-daemon startup succeeded
Dec  1 11:15:29 localhost haldaemon: haldaemon startup succeeded
Dec  1 11:15:37 localhost NET: /sbin/dhclient-script : updated /etc/resolv.conf
Dec  1 11:15:38 localhost rc: Starting xend:  succeeded

[-- Attachment #3: lspci.native --]
[-- Type: application/octet-stream, Size: 2939 bytes --]

00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub (rev 92)
00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev 92)
00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev 92)
00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 6-7 (rev 92)
00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev 92)
00:10.0 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
00:10.1 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
00:10.2 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 92)
00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 92)
00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 92)
00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 92)
00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09)
00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09)
00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09)
00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09)
00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09)
00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA Storage Controller IDE (rev 09)
00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09)
01:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01)
01:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01)
02:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01)
02:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01)
03:00.0 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge A (rev 09)
03:00.2 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge B (rev 09)
08:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 02)
0a:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
0a:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
0b:01.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)

[-- Attachment #4: lsmod.native --]
[-- Type: application/octet-stream, Size: 1015 bytes --]

Module                  Size  Used by
parport_pc             26180  1 
lp                     12488  0 
parport                34760  2 parport_pc,lp
autofs4                19204  0 
sunrpc                137660  1 
dm_mirror              21456  0 
dm_multipath           18696  0 
button                  6928  0 
battery                 9732  0 
ac                      5252  0 
ipv6                  227424  10 
uhci_hcd               29968  0 
ehci_hcd               29704  0 
hw_random               6040  0 
i2c_i801                8716  0 
i2c_core               20864  1 i2c_i801
e1000                  99892  0 
floppy                 57156  0 
ext3                  118024  2 
jbd                    53524  1 ext3
dm_mod                 52888  3 dm_mirror,dm_multipath
mptscsih               33616  0 
mptbase                47584  1 mptscsih
ata_piix               10116  4 
libata                 56080  1 ata_piix
sd_mod                 16640  5 
scsi_mod              127400  3 mptscsih,libata,sd_mod

[-- Attachment #5: dmesg_ide.native --]
[-- Type: application/octet-stream, Size: 788 bytes --]

BIOS-provided physical RAM map:
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
CPU: After generic identify, caps: bfebfbff 20000000 00000000 00000000 0004e3bd 00000000 00000001
CPU: After vendor identify, caps: bfebfbff 20000000 00000000 00000000 0004e3bd 00000000 00000001
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
Boot video device is 0000:0b:01.0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ESB2: IDE controller at PCI slot 0000:00:1f.1
    ide0: BM-DMA at 0x1860-0x1867, BIOS settings: hda:DMA, hdb:pio
Probing IDE interface ide0...
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
ide-floppy driver 0.99.newide

[-- Attachment #6: boot.native --]
[-- Type: application/octet-stream, Size: 4872 bytes --]

Dec  1 11:08:31 localhost syslog: syslogd startup succeeded
Dec  1 11:08:31 localhost syslog: klogd startup succeeded
Dec  1 11:08:31 localhost irqbalance: irqbalance startup succeeded
Dec  1 11:08:31 localhost portmap: portmap startup succeeded
Dec  1 11:08:31 localhost nfslock: rpc.statd startup succeeded
Dec  1 11:08:31 localhost rpcidmapd: rpc.idmapd startup succeeded
Dec  1 11:08:31 localhost netfs: Mounting other filesystems:  succeeded
Dec  1 11:08:31 localhost rc: Starting lm_sensors:  succeeded
Dec  1 11:08:32 localhost autofs: automount startup succeeded
Dec  1 11:08:32 localhost smartd: smartd startup succeeded
Dec  1 11:08:32 localhost acpid: acpid startup succeeded
Dec  1 11:08:32 localhost rc: Starting hpoj:  succeeded
Dec  1 04:07:56 localhost rc.sysinit: -e 
Dec  1 04:07:57 localhost start_udev: Starting udev:  succeeded 
Dec  1 04:08:02 localhost rc.sysinit: -e 
Dec  1 04:08:10 localhost sysctl: net.ipv4.ip_forward = 0 
Dec  1 04:08:10 localhost sysctl: net.ipv4.conf.default.rp_filter = 1 
Dec  1 04:08:10 localhost sysctl: net.ipv4.conf.default.accept_source_route = 0 
Dec  1 04:08:10 localhost sysctl: kernel.sysrq = 0 
Dec  1 04:08:10 localhost sysctl: kernel.core_uses_pid = 1 
Dec  1 04:08:10 localhost rc.sysinit: Configuring kernel parameters:  succeeded 
Dec  1 11:08:09 localhost date: Fri Dec  1 11:08:09 MST 2006 
Dec  1 11:08:09 localhost rc.sysinit: Setting clock  (localtime): Fri Dec  1 11:08:09 MST 2006 succeeded 
Dec  1 11:08:09 localhost rc.sysinit: Loading default keymap succeeded 
Dec  1 11:08:09 localhost rc.sysinit: Setting hostname localhost.localdomain:  succeeded 
Dec  1 11:08:09 localhost rc.sysinit: Checking root filesystem succeeded 
Dec  1 11:08:09 localhost rc.sysinit: Remounting root filesystem in read-write mode:  succeeded 
Dec  1 11:08:12 localhost lvm.static:   1 logical volume(s) in volume group VG_Dom8_Linux now active 
Dec  1 11:08:12 localhost rc.sysinit: Setting up Logical Volume Management: succeeded 
Dec  1 11:08:13 localhost rc.sysinit: Checking filesystems succeeded 
Dec  1 11:08:13 localhost rc.sysinit: Mounting local filesystems:  succeeded 
Dec  1 11:08:13 localhost rc.sysinit: Enabling local filesystem quotas:  succeeded 
Dec  1 11:08:13 localhost rc.sysinit: Enabling swap space:  succeeded 
Dec  1 11:08:14 localhost microcode_ctl: microcode_ctl startup succeeded 
Dec  1 11:08:14 localhost sysstat: Calling the system activity data collector (sadc):  
Dec  1 11:08:14 localhost sysstat:  
Dec  1 11:08:14 localhost rc: Starting sysstat:  succeeded 
Dec  1 11:08:35 localhost cups: cupsd startup succeeded
Dec  1 11:08:14 localhost readahead_early: Starting background readahead:  
Dec  1 11:08:14 localhost rc: Starting readahead_early:  succeeded 
Dec  1 11:08:26 localhost kudzu:  succeeded 
Dec  1 11:08:26 localhost rc: Starting pcmcia:  succeeded 
Dec  1 11:08:35 localhost sshd:  succeeded
Dec  1 11:08:26 localhost sysctl: net.ipv4.ip_forward = 0 
Dec  1 11:08:26 localhost sysctl: net.ipv4.conf.default.rp_filter = 1 
Dec  1 11:08:26 localhost sysctl: net.ipv4.conf.default.accept_source_route = 0 
Dec  1 11:08:35 localhost xinetd: xinetd startup succeeded
Dec  1 11:08:26 localhost sysctl: kernel.sysrq = 0 
Dec  1 11:08:26 localhost sysctl: kernel.core_uses_pid = 1 
Dec  1 11:08:26 localhost network: Setting network parameters:  succeeded 
Dec  1 11:08:26 localhost network: Bringing up loopback interface:  succeeded 
Dec  1 11:08:26 localhost ifup:  
Dec  1 11:08:26 localhost ifup: Determining IP information for eth0... 
Dec  1 11:08:35 localhost sendmail: sendmail startup succeeded
Dec  1 11:08:26 localhost NET: /sbin/dhclient-script : updated /etc/resolv.conf 
Dec  1 11:08:35 localhost sendmail: sm-client startup succeeded
Dec  1 11:08:26 localhost ifup:  done. 
Dec  1 11:08:26 localhost network: Bringing up interface eth0:  succeeded 
Dec  1 11:08:31 localhost network: Bringing up interface eth1:  succeeded 
Dec  1 11:08:36 localhost gpm: gpm startup succeeded
Dec  1 11:08:36 localhost iiim: htt startup succeeded
Dec  1 11:08:38 localhost canna:  succeeded
Dec  1 11:08:38 localhost crond: crond startup succeeded
Dec  1 11:08:39 localhost xfs: xfs startup succeeded
Dec  1 11:08:39 localhost anacron: anacron startup succeeded
Dec  1 11:08:39 localhost atd: atd startup succeeded
Dec  1 11:08:40 localhost readahead: Starting background readahead: 
Dec  1 11:08:40 localhost rc: Starting readahead:  succeeded
Dec  1 11:08:40 localhost messagebus: messagebus startup succeeded
Dec  1 11:08:40 localhost cups-config-daemon: cups-config-daemon startup succeeded
Dec  1 11:08:41 localhost haldaemon: haldaemon startup succeeded
Dec  1 11:08:41 localhost xend: grep: /proc/xen/capabilities: No such file or directory
Dec  1 11:08:41 localhost rc: Starting xend:  succeeded

[-- Attachment #7: lspci.xen --]
[-- Type: application/octet-stream, Size: 2939 bytes --]

00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub (rev 92)
00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev 92)
00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev 92)
00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 6-7 (rev 92)
00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev 92)
00:10.0 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
00:10.1 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
00:10.2 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 92)
00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 92)
00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 92)
00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 92)
00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09)
00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09)
00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09)
00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09)
00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09)
00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA Storage Controller IDE (rev 09)
00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09)
01:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01)
01:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01)
02:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01)
02:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01)
03:00.0 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge A (rev 09)
03:00.2 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge B (rev 09)
08:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 02)
0a:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
0a:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
0b:01.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)

[-- Attachment #8: lsmod.xen --]
[-- Type: application/octet-stream, Size: 1505 bytes --]

Module                  Size  Used by
bridge                 57876  0 
parport_pc             44484  1 
lp                     15908  0 
parport                41288  2 parport_pc,lp
autofs4                24452  0 
sunrpc                157500  1 
binfmt_misc            16008  1 
dm_mirror              27216  0 
dm_multipath           24840  0 
dm_mod                 62488  3 dm_mirror,dm_multipath
video                  19716  0 
thermal                17160  0 
processor              26420  1 thermal
fan                     8708  0 
container               8704  0 
button                 10640  0 
battery                13444  0 
ac                      8964  0 
tsdev                  11968  0 
ipv6                  282336  10 
usbhid                 53472  0 
uhci_hcd               38032  0 
ehci_hcd               38280  0 
usbcore               137092  4 usbhid,uhci_hcd,ehci_hcd
hw_random               9880  0 
i2c_i801               12812  0 
i2c_core               25984  1 i2c_i801
e1000                 119604  0 
mptscsih               41936  0 
mptbase                56288  1 mptscsih
piix                   14852  0 [permanent]
ide_generic             5376  0 [permanent]
aacraid                63104  0 
ext3                  139528  2 
jbd                    63380  1 ext3
ide_disk               22144  0 
ata_piix               14852  4 
libata                 68368  1 ata_piix
sd_mod                 22528  5 
scsi_mod              142472  4 mptscsih,aacraid,libata,sd_mod

[-- Attachment #9: dmesg_ide.xen --]
[-- Type: application/octet-stream, Size: 441 bytes --]

PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
Boot video device is 0000:0b:01.0
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Probing IDE interface ide0...
Probing IDE interface ide1...
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ESB2: IDE controller at PCI slot 0000:00:1f.1
ESB2: port 0x01f0 already claimed by ide0
ESB2: neither IDE port enabled (BIOS)

[-- Attachment #10: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: logs attached. Re: [Xen-users] Can not find the cdrom device in /dev/ afterbooted into xen(3.0.3)

[Keir Fraser]

On 1/12/06 6:27 pm, "Liang Yang" <multisyncfe991@hotmail.com> wrote:

> Hi Tim, Keir and Mats,
> 
> I attached all the detailed log files (text file format). The file extension
> indicate the version of environment. Please take a look.

ESB2 should be supported by the piix IDE driver. Which XenLinux kernel
config are you using? Either you need the driver compiled into the kernel,
or you need to load it as a module. Look for a line containing
CONFIG_BLK_DEV_PIIX in your .config -- it should be "=m" or "=y".

If it's compiled as a module, and you installed the modules on your
filesystem, you may be able to fire up the CDROM drive by typing 'modprobe
piix'.

 -- Keir

Re: [Xen-devel] Re: logs attached. Re: Can not find the cdrom device in /dev/ afterbooted into xen(3.0.3)

[Liang Yang]

I just download Xen source and do "make world;make 
install;depmod..;mkinitrd...". I don't know which config file will be used 
if I build Xen like this (maybe the config-2.6.16.29-xen under the directory 
dist/install/boot).

 I did a grep with "CONFIG_BLK_DEV_PIIX" and found it it set to m in the 
config-2.6.16.29-xen. I did a modprobe piix, however my CD-ROM is still not 
fired up (nothing is show up /dev/ as either cdrom or hd*).

Liang

----- Original Message ----- 
From: "Keir Fraser" <keir@xensource.com>
To: "Liang Yang" <multisyncfe991@hotmail.com>; <tim.post@netkinetics.net>; 
"Petersson, Mats" <Mats.Petersson@amd.com>
Cc: <xen-devel@lists.xensource.com>; <xen-users@lists.xensource.com>
Sent: Friday, December 01, 2006 11:34 AM
Subject: [Xen-devel] Re: logs attached. Re: [Xen-users] Can not find the 
cdrom device in /dev/ afterbooted into xen(3.0.3)


> On 1/12/06 6:27 pm, "Liang Yang" <multisyncfe991@hotmail.com> wrote:
>
>> Hi Tim, Keir and Mats,
>>
>> I attached all the detailed log files (text file format). The file 
>> extension
>> indicate the version of environment. Please take a look.
>
> ESB2 should be supported by the piix IDE driver. Which XenLinux kernel
> config are you using? Either you need the driver compiled into the kernel,
> or you need to load it as a module. Look for a line containing
> CONFIG_BLK_DEV_PIIX in your .config -- it should be "=m" or "=y".
>
> If it's compiled as a module, and you installed the modules on your
> filesystem, you may be able to fire up the CDROM drive by typing 'modprobe
> piix'.
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 

Re: Re: logs attached. Re: [Xen-users] Can not find the cdrom device in /dev/ afterbooted into xen(3.0.3)

[Keir Fraser]

Actually, now I look closer it seems that on native the IDE I/O ports are
detected as 0x1860-0x1867, but the Xen kernel is failing to detect this and
is then failing to register at the default 0x1f0, probably because a legacy
ISA IDE driver is registered there. So there is definitely something odd
going on here but tracking it down will probably require adding some kernel
tracing (e.g., to ide_hwif_configure(), to determine why it is failing to
find the special location of the IDE I/O ports).

 -- Keir

On 1/12/06 6:48 pm, "Liang Yang" <multisyncfe991@hotmail.com> wrote:

> I just download Xen source and do "make world;make
> install;depmod..;mkinitrd...". I don't know which config file will be used
> if I build Xen like this (maybe the config-2.6.16.29-xen under the directory
> dist/install/boot).
> 
>  I did a grep with "CONFIG_BLK_DEV_PIIX" and found it it set to m in the
> config-2.6.16.29-xen. I did a modprobe piix, however my CD-ROM is still not
> fired up (nothing is show up /dev/ as either cdrom or hd*).
> 
> Liang
> 
> ----- Original Message -----
> From: "Keir Fraser" <keir@xensource.com>
> To: "Liang Yang" <multisyncfe991@hotmail.com>; <tim.post@netkinetics.net>;
> "Petersson, Mats" <Mats.Petersson@amd.com>
> Cc: <xen-devel@lists.xensource.com>; <xen-users@lists.xensource.com>
> Sent: Friday, December 01, 2006 11:34 AM
> Subject: [Xen-devel] Re: logs attached. Re: [Xen-users] Can not find the
> cdrom device in /dev/ afterbooted into xen(3.0.3)
> 
> 
>> On 1/12/06 6:27 pm, "Liang Yang" <multisyncfe991@hotmail.com> wrote:
>> 
>>> Hi Tim, Keir and Mats,
>>> 
>>> I attached all the detailed log files (text file format). The file
>>> extension
>>> indicate the version of environment. Please take a look.
>> 
>> ESB2 should be supported by the piix IDE driver. Which XenLinux kernel
>> config are you using? Either you need the driver compiled into the kernel,
>> or you need to load it as a module. Look for a line containing
>> CONFIG_BLK_DEV_PIIX in your .config -- it should be "=m" or "=y".
>> 
>> If it's compiled as a module, and you installed the modules on your
>> filesystem, you may be able to fire up the CDROM drive by typing 'modprobe
>> piix'.
>> 
>> -- Keir
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Re: logs attached. Re: [Xen-users] Can not find the cdrom device in /dev/ afterbooted into xen(3.0.3)

[Keir Fraser]

Lspci -vvv output for native and Xen kernels may be useful, just for device
00:1f.1 (the IDE device). Then we could see which I/O resources the device
is claiming in each case

 -- Keir

On 1/12/06 6:56 pm, "Keir Fraser" <keir@xensource.com> wrote:

> Actually, now I look closer it seems that on native the IDE I/O ports are
> detected as 0x1860-0x1867, but the Xen kernel is failing to detect this and
> is then failing to register at the default 0x1f0, probably because a legacy
> ISA IDE driver is registered there. So there is definitely something odd
> going on here but tracking it down will probably require adding some kernel
> tracing (e.g., to ide_hwif_configure(), to determine why it is failing to
> find the special location of the IDE I/O ports).
> 
>  -- Keir
> 
> On 1/12/06 6:48 pm, "Liang Yang" <multisyncfe991@hotmail.com> wrote:
> 
>> I just download Xen source and do "make world;make
>> install;depmod..;mkinitrd...". I don't know which config file will be used
>> if I build Xen like this (maybe the config-2.6.16.29-xen under the directory
>> dist/install/boot).
>> 
>>  I did a grep with "CONFIG_BLK_DEV_PIIX" and found it it set to m in the
>> config-2.6.16.29-xen. I did a modprobe piix, however my CD-ROM is still not
>> fired up (nothing is show up /dev/ as either cdrom or hd*).
>> 
>> Liang
>> 
>> ----- Original Message -----
>> From: "Keir Fraser" <keir@xensource.com>
>> To: "Liang Yang" <multisyncfe991@hotmail.com>; <tim.post@netkinetics.net>;
>> "Petersson, Mats" <Mats.Petersson@amd.com>
>> Cc: <xen-devel@lists.xensource.com>; <xen-users@lists.xensource.com>
>> Sent: Friday, December 01, 2006 11:34 AM
>> Subject: [Xen-devel] Re: logs attached. Re: [Xen-users] Can not find the
>> cdrom device in /dev/ afterbooted into xen(3.0.3)
>> 
>> 
>>> On 1/12/06 6:27 pm, "Liang Yang" <multisyncfe991@hotmail.com> wrote:
>>> 
>>>> Hi Tim, Keir and Mats,
>>>> 
>>>> I attached all the detailed log files (text file format). The file
>>>> extension
>>>> indicate the version of environment. Please take a look.
>>> 
>>> ESB2 should be supported by the piix IDE driver. Which XenLinux kernel
>>> config are you using? Either you need the driver compiled into the kernel,
>>> or you need to load it as a module. Look for a line containing
>>> CONFIG_BLK_DEV_PIIX in your .config -- it should be "=m" or "=y".
>>> 
>>> If it's compiled as a module, and you installed the modules on your
>>> filesystem, you may be able to fire up the CDROM drive by typing 'modprobe
>>> piix'.
>>> 
>>> -- Keir
>>> 
>>> 
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>> 
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
> 

Re: Re: logs attached. Re: [Xen-users] Can not findthe cdrom device in /dev/ afterbooted into xen(3.0.3)

[Liang Yang]

[-- Attachment #1: Type: text/plain, Size: 3590 bytes --]

See attached.

----- Original Message ----- 
From: "Keir Fraser" <keir@xensource.com>
To: "Keir Fraser" <keir@xensource.com>; "Liang Yang" 
<multisyncfe991@hotmail.com>; <tim.post@netkinetics.net>; "Petersson, Mats" 
<Mats.Petersson@amd.com>
Cc: <xen-devel@lists.xensource.com>; <xen-users@lists.xensource.com>
Sent: Friday, December 01, 2006 11:58 AM
Subject: Re: [Xen-devel] Re: logs attached. Re: [Xen-users] Can not findthe 
cdrom device in /dev/ afterbooted into xen(3.0.3)


> Lspci -vvv output for native and Xen kernels may be useful, just for 
> device
> 00:1f.1 (the IDE device). Then we could see which I/O resources the device
> is claiming in each case
>
> -- Keir
>
> On 1/12/06 6:56 pm, "Keir Fraser" <keir@xensource.com> wrote:
>
>> Actually, now I look closer it seems that on native the IDE I/O ports are
>> detected as 0x1860-0x1867, but the Xen kernel is failing to detect this 
>> and
>> is then failing to register at the default 0x1f0, probably because a 
>> legacy
>> ISA IDE driver is registered there. So there is definitely something odd
>> going on here but tracking it down will probably require adding some 
>> kernel
>> tracing (e.g., to ide_hwif_configure(), to determine why it is failing to
>> find the special location of the IDE I/O ports).
>>
>>  -- Keir
>>
>> On 1/12/06 6:48 pm, "Liang Yang" <multisyncfe991@hotmail.com> wrote:
>>
>>> I just download Xen source and do "make world;make
>>> install;depmod..;mkinitrd...". I don't know which config file will be 
>>> used
>>> if I build Xen like this (maybe the config-2.6.16.29-xen under the 
>>> directory
>>> dist/install/boot).
>>>
>>>  I did a grep with "CONFIG_BLK_DEV_PIIX" and found it it set to m in the
>>> config-2.6.16.29-xen. I did a modprobe piix, however my CD-ROM is still 
>>> not
>>> fired up (nothing is show up /dev/ as either cdrom or hd*).
>>>
>>> Liang
>>>
>>> ----- Original Message -----
>>> From: "Keir Fraser" <keir@xensource.com>
>>> To: "Liang Yang" <multisyncfe991@hotmail.com>; 
>>> <tim.post@netkinetics.net>;
>>> "Petersson, Mats" <Mats.Petersson@amd.com>
>>> Cc: <xen-devel@lists.xensource.com>; <xen-users@lists.xensource.com>
>>> Sent: Friday, December 01, 2006 11:34 AM
>>> Subject: [Xen-devel] Re: logs attached. Re: [Xen-users] Can not find the
>>> cdrom device in /dev/ afterbooted into xen(3.0.3)
>>>
>>>
>>>> On 1/12/06 6:27 pm, "Liang Yang" <multisyncfe991@hotmail.com> wrote:
>>>>
>>>>> Hi Tim, Keir and Mats,
>>>>>
>>>>> I attached all the detailed log files (text file format). The file
>>>>> extension
>>>>> indicate the version of environment. Please take a look.
>>>>
>>>> ESB2 should be supported by the piix IDE driver. Which XenLinux kernel
>>>> config are you using? Either you need the driver compiled into the 
>>>> kernel,
>>>> or you need to load it as a module. Look for a line containing
>>>> CONFIG_BLK_DEV_PIIX in your .config -- it should be "=m" or "=y".
>>>>
>>>> If it's compiled as a module, and you installed the modules on your
>>>> filesystem, you may be able to fire up the CDROM drive by typing 
>>>> 'modprobe
>>>> piix'.
>>>>
>>>> -- Keir
>>>>
>>>>
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> http://lists.xensource.com/xen-devel
>>>>
>>>
>>>
>>> _______________________________________________
>>> Xen-devel mailing list
>>> Xen-devel@lists.xensource.com
>>> http://lists.xensource.com/xen-devel
>>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 

[-- Attachment #2: lspci_vvv.native --]
[-- Type: application/octet-stream, Size: 33418 bytes --]

00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Interrupt: pin A routed to IRQ 0
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable-
		Address: fee00000  Data: 0000
	Capabilities: [6c] Express Root Port (Slot-) IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s unlimited, L1 unlimited
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed 2.5Gb/s, Width x4, ASPM L0s, Port 0
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x4
		Root: Correctable- Non-Fatal- Fatal- PME-
	Capabilities: [100] Advanced Error Reporting

00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev 92) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=00, secondary=01, subordinate=07, sec-latency=0
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: c8100000-c81fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable-
		Address: fee00000  Data: 0000
	Capabilities: [6c] Express Root Port (Slot-) IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s unlimited, L1 unlimited
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 2
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
		Root: Correctable- Non-Fatal- Fatal- PME-
	Capabilities: [100] Advanced Error Reporting

00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev 92) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=00, secondary=08, subordinate=08, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: c8200000-c82fffff
	Prefetchable memory behind bridge: 00000000c2000000-00000000c2100000
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable-
		Address: fee00000  Data: 0000
	Capabilities: [6c] Express Root Port (Slot+) IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s unlimited, L1 unlimited
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 4
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
		Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug- Surpise-
		Slot: Number 0, PowerLimit 0.000000
		Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
		Slot: AttnInd Off, PwrInd Off, Power-
		Root: Correctable- Non-Fatal- Fatal- PME-
	Capabilities: [100] Advanced Error Reporting

00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 6-7 (rev 92) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=00, secondary=09, subordinate=09, sec-latency=0
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable-
		Address: fee00000  Data: 0000
	Capabilities: [6c] Express Root Port (Slot+) IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s unlimited, L1 unlimited
		Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 6
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
		Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug- Surpise-
		Slot: Number 0, PowerLimit 0.000000
		Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
		Slot: AttnInd Off, PwrInd Off, Power-
		Root: Correctable- Non-Fatal- Fatal- PME-
	Capabilities: [100] Advanced Error Reporting

00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 255
	Region 0: Memory at c8000000 (64-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
		Address: fee00000  Data: 0000
	Capabilities: [6c] Express Unknown type IRQ 0
		Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed unknown, Width x0, ASPM unknown, Port 0
		Link: Latency L0s <64ns, L1 <1us
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed unknown, Width x0

00:10.0 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:10.1 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:10.2 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=0
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: c8300000-c83fffff
	Prefetchable memory behind bridge: 00000000c2200000-00000000c2200000
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [40] Express Root Port (Slot+) IRQ 0
		Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
		Device: Latency L0s unlimited, L1 unlimited
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed 2.5Gb/s, Width x4, ASPM L0s L1, Port 1
		Link: Latency L0s <256ns, L1 <4us
		Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x4
		Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+
		Slot: Number 1, PowerLimit 28.000000
		Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
		Slot: AttnInd Unknown, PwrInd Unknown, Power-
		Root: Correctable- Non-Fatal- Fatal- PME-
	Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
		Address: 00000000  Data: 0000
	Capabilities: [90] #0d [0000]
	Capabilities: [a0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Unknown (5)

00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09) (prog-if 00 [UHCI])
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 185
	Region 4: I/O ports at 1800 [size=32]

00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09) (prog-if 00 [UHCI])
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 193
	Region 4: I/O ports at 1820 [size=32]

00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09) (prog-if 00 [UHCI])
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin C routed to IRQ 177
	Region 4: I/O ports at 1840 [size=32]

00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09) (prog-if 20 [EHCI])
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 185
	Region 0: Memory at c8000400 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Debug port

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9) (prog-if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=32
	I/O behind bridge: 00004000-00004fff
	Memory behind bridge: c8400000-c84fffff
	Prefetchable memory behind bridge: 00000000d0000000-00000000d7f00000
	Secondary status: 66Mhz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
	Capabilities: [50] #0d [0000]

00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0

00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09) (prog-if 8a [Master SecP PriP])
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 177
	Region 0: I/O ports at <unassigned>
	Region 1: I/O ports at <unassigned>
	Region 2: I/O ports at <unassigned>
	Region 3: I/O ports at <unassigned>
	Region 4: I/O ports at 1860 [size=16]

00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA Storage Controller IDE (rev 09) (prog-if 8f [Master SecP SecO PriP PriO])
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 193
	Region 0: I/O ports at 1890 [size=8]
	Region 1: I/O ports at 1884 [size=4]
	Region 2: I/O ports at 1888 [size=8]
	Region 3: I/O ports at 1880 [size=4]
	Region 4: I/O ports at 1870 [size=16]
	Region 5: Memory at c8000800 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin B routed to IRQ 10
	Region 4: I/O ports at 1100 [size=32]

01:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=01, secondary=02, subordinate=06, sec-latency=0
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [44] Express Upstream Port IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: SlotPowerLimit 0.000000
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 4096 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 0
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] #0d [0000]
	Capabilities: [100] Advanced Error Reporting

01:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 10
	Bus: primary=01, secondary=07, subordinate=07, sec-latency=64
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [44] Express PCI/PCI-X Bridge IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 256 bytes, MaxReadReq 256 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 0
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
	Capabilities: [6c] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] #0d [0000]
	Capabilities: [d8] PCI-X bridge device.
		Secondary Status: 64bit+, 133MHz+, SCD-, USC-, SCO-, SRD- Freq=3
		Status: Bus=0 Dev=0 Func=3 64bit- 133MHz- SCD- USC-, SCO-, SRD-
		: Upstream: Capacity=65535, Commitment Limit=65535
		: Downstream: Capacity=65535, Commitment Limit=65535
	Capabilities: [100] Advanced Error Reporting

02:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=02, secondary=03, subordinate=05, sec-latency=0
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [44] Express Downstream Port (Slot-) IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 2048 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 0
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
	Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] #0d [0000]
	Capabilities: [100] Advanced Error Reporting

02:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=02, secondary=06, subordinate=06, sec-latency=0
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [44] Express Downstream Port (Slot-) IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 2048 bytes
		Link: Supported Speed 2.5Gb/s, Width x4, ASPM L0s, Port 0
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x4
	Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] #0d [0000]
	Capabilities: [100] Advanced Error Reporting

03:00.0 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge A (rev 09) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 10
	Bus: primary=03, secondary=04, subordinate=04, sec-latency=64
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [44] Express PCI/PCI-X Bridge IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal+ Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 0
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
	Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [6c] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [d8] PCI-X bridge device.
		Secondary Status: 64bit+, 133MHz+, SCD-, USC-, SCO-, SRD- Freq=2
		Status: Bus=3 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, SCO-, SRD-
		: Upstream: Capacity=65535, Commitment Limit=65535
		: Downstream: Capacity=65535, Commitment Limit=65535
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [300] Power Budgeting

03:00.2 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge B (rev 09) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 10
	Bus: primary=03, secondary=05, subordinate=05, sec-latency=64
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [44] Express PCI/PCI-X Bridge IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal+ Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 0
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
	Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [6c] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [d8] PCI-X bridge device.
		Secondary Status: 64bit+, 133MHz+, SCD-, USC-, SCO-, SRD- Freq=3
		Status: Bus=3 Dev=0 Func=2 64bit- 133MHz- SCD- USC-, SCO-, SRD-
		: Upstream: Capacity=65535, Commitment Limit=65535
		: Downstream: Capacity=65535, Commitment Limit=65535
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [300] Power Budgeting

08:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 02)
	Subsystem: LSI Logic / Symbios Logic: Unknown device 3080
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Interrupt: pin A routed to IRQ 9
	Region 0: I/O ports at 2000 [size=256]
	Region 1: Memory at c8210000 (64-bit, non-prefetchable) [size=16K]
	Region 3: Memory at c8200000 (64-bit, non-prefetchable) [size=64K]
	[virtual] Expansion ROM at c2000000 [disabled] [size=2M]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] Express Endpoint IRQ 0
		Device: Supported: MaxPayload 4096 bytes, PhantFunc 0, ExtTag+
		Device: Latency L0s <64ns, L1 <1us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s L1, Port 0
		Link: Latency L0s <64ns, L1 <1us
		Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
	Capabilities: [98] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [b0] MSI-X: Enable- Mask- TabSize=1
		Vector table: BAR=1 offset=00002000
		PBA: BAR=1 offset=00003000
	Capabilities: [100] Advanced Error Reporting

0a:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
	Subsystem: Intel Corporation: Unknown device 115e
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Interrupt: pin A routed to IRQ 209
	Region 0: Memory at c8320000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at c8300000 (32-bit, non-prefetchable) [size=128K]
	Region 2: I/O ports at 3000 [size=32]
	[virtual] Expansion ROM at c2200000 [disabled] [size=128K]
	Capabilities: [c8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [d0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable+
		Address: 00000000fee00000  Data: 40d1
	Capabilities: [e0] Express Endpoint IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <512ns, L1 <64us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
		Link: Supported Speed 2.5Gb/s, Width x4, ASPM L0s, Port 0
		Link: Latency L0s <4us, L1 <64us
		Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x4
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 64-92-0b-ff-ff-17-15-00

0a:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
	Subsystem: Intel Corporation: Unknown device 115e
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Interrupt: pin B routed to IRQ 217
	Region 0: Memory at c8360000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at c8340000 (32-bit, non-prefetchable) [size=128K]
	Region 2: I/O ports at 3020 [size=32]
	[virtual] Expansion ROM at c2220000 [disabled] [size=128K]
	Capabilities: [c8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [d0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable+
		Address: 00000000fee00000  Data: 40d9
	Capabilities: [e0] Express Endpoint IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <512ns, L1 <64us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
		Link: Supported Speed 2.5Gb/s, Width x4, ASPM L0s, Port 0
		Link: Latency L0s <4us, L1 <64us
		Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x4
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 64-92-0b-ff-ff-17-15-00

0b:01.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02) (prog-if 00 [VGA])
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR+ FastB2B+
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 66 (2000ns min), Cache Line Size 08
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at d0000000 (32-bit, prefetchable) [size=128M]
	Region 1: I/O ports at 4000 [size=256]
	Region 2: Memory at c8400000 (32-bit, non-prefetchable) [size=64K]
	[virtual] Expansion ROM at c8420000 [disabled] [size=128K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-


[-- Attachment #3: lspci_vvv.xen --]
[-- Type: application/octet-stream, Size: 33410 bytes --]

00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Interrupt: pin A routed to IRQ 0
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable-
		Address: fee00000  Data: 0000
	Capabilities: [6c] Express Root Port (Slot-) IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s unlimited, L1 unlimited
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed 2.5Gb/s, Width x4, ASPM L0s, Port 0
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x4
		Root: Correctable- Non-Fatal- Fatal- PME-
	Capabilities: [100] Advanced Error Reporting

00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev 92) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=00, secondary=01, subordinate=07, sec-latency=0
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: c8100000-c81fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable-
		Address: fee00000  Data: 0000
	Capabilities: [6c] Express Root Port (Slot-) IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s unlimited, L1 unlimited
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 2
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
		Root: Correctable- Non-Fatal- Fatal- PME-
	Capabilities: [100] Advanced Error Reporting

00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev 92) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=00, secondary=08, subordinate=08, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: c8200000-c82fffff
	Prefetchable memory behind bridge: 00000000c2000000-00000000c2100000
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable-
		Address: fee00000  Data: 0000
	Capabilities: [6c] Express Root Port (Slot+) IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s unlimited, L1 unlimited
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 4
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
		Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug- Surpise-
		Slot: Number 0, PowerLimit 0.000000
		Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
		Slot: AttnInd Off, PwrInd Off, Power-
		Root: Correctable- Non-Fatal- Fatal- PME-
	Capabilities: [100] Advanced Error Reporting

00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 6-7 (rev 92) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=00, secondary=09, subordinate=09, sec-latency=0
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable-
		Address: fee00000  Data: 0000
	Capabilities: [6c] Express Root Port (Slot+) IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s unlimited, L1 unlimited
		Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 6
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
		Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug- Surpise-
		Slot: Number 0, PowerLimit 0.000000
		Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
		Slot: AttnInd Off, PwrInd Off, Power-
		Root: Correctable- Non-Fatal- Fatal- PME-
	Capabilities: [100] Advanced Error Reporting

00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 255
	Region 0: Memory at c8000000 (64-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
		Address: fee00000  Data: 0000
	Capabilities: [6c] Express Unknown type IRQ 0
		Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed unknown, Width x0, ASPM unknown, Port 0
		Link: Latency L0s <64ns, L1 <1us
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed unknown, Width x0

00:10.0 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:10.1 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:10.2 Host bridge: Intel Corporation 5000 Series Chipset Error Reporting Registers (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev 92)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-

00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=00, secondary=0a, subordinate=0a, sec-latency=0
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: c8300000-c83fffff
	Prefetchable memory behind bridge: 00000000c2200000-00000000c2200000
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [40] Express Root Port (Slot+) IRQ 0
		Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
		Device: Latency L0s unlimited, L1 unlimited
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed 2.5Gb/s, Width x4, ASPM L0s L1, Port 1
		Link: Latency L0s <256ns, L1 <4us
		Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
		Link: Speed 2.5Gb/s, Width x4
		Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+
		Slot: Number 1, PowerLimit 28.000000
		Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq-
		Slot: AttnInd Unknown, PwrInd Unknown, Power-
		Root: Correctable- Non-Fatal- Fatal- PME-
	Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable-
		Address: 00000000  Data: 0000
	Capabilities: [90] #0d [0000]
	Capabilities: [a0] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Unknown (5)

00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09) (prog-if 00 [UHCI])
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 18
	Region 4: I/O ports at 1800 [size=32]

00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09) (prog-if 00 [UHCI])
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 19
	Region 4: I/O ports at 1820 [size=32]

00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09) (prog-if 00 [UHCI])
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin C routed to IRQ 17
	Region 4: I/O ports at 1840 [size=32]

00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09) (prog-if 20 [EHCI])
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 18
	Region 0: Memory at c8000400 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [58] Debug port

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9) (prog-if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Bus: primary=00, secondary=0b, subordinate=0b, sec-latency=32
	I/O behind bridge: 00004000-00004fff
	Memory behind bridge: c8400000-c84fffff
	Prefetchable memory behind bridge: 00000000d0000000-00000000d7f00000
	Secondary status: 66Mhz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
	Capabilities: [50] #0d [0000]

00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0

00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09) (prog-if 8a [Master SecP PriP])
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin A routed to IRQ 17
	Region 0: I/O ports at <unassigned>
	Region 1: I/O ports at <unassigned>
	Region 2: I/O ports at <unassigned>
	Region 3: I/O ports at <unassigned>
	Region 4: I/O ports at 1860 [size=16]

00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA Storage Controller IDE (rev 09) (prog-if 8f [Master SecP SecO PriP PriO])
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0
	Interrupt: pin B routed to IRQ 19
	Region 0: I/O ports at 1890 [size=8]
	Region 1: I/O ports at 1884 [size=4]
	Region 2: I/O ports at 1888 [size=8]
	Region 3: I/O ports at 1880 [size=4]
	Region 4: I/O ports at 1870 [size=16]
	Region 5: Memory at c8000800 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09)
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Interrupt: pin B routed to IRQ 10
	Region 4: I/O ports at 1100 [size=32]

01:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=01, secondary=02, subordinate=06, sec-latency=0
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [44] Express Upstream Port IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: SlotPowerLimit 0.000000
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 4096 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 0
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] #0d [0000]
	Capabilities: [100] Advanced Error Reporting

01:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 10
	Bus: primary=01, secondary=07, subordinate=07, sec-latency=64
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [44] Express PCI/PCI-X Bridge IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 256 bytes, MaxReadReq 256 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 0
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
	Capabilities: [6c] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] #0d [0000]
	Capabilities: [d8] PCI-X bridge device.
		Secondary Status: 64bit+, 133MHz+, SCD-, USC-, SCO-, SRD- Freq=3
		Status: Bus=0 Dev=0 Func=3 64bit- 133MHz- SCD- USC-, SCO-, SRD-
		: Upstream: Capacity=65535, Commitment Limit=65535
		: Downstream: Capacity=65535, Commitment Limit=65535
	Capabilities: [100] Advanced Error Reporting

02:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=02, secondary=03, subordinate=05, sec-latency=0
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [44] Express Downstream Port (Slot-) IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 2048 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 0
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
	Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] #0d [0000]
	Capabilities: [100] Advanced Error Reporting

02:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Bus: primary=02, secondary=06, subordinate=06, sec-latency=0
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [44] Express Downstream Port (Slot-) IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 2048 bytes
		Link: Supported Speed 2.5Gb/s, Width x4, ASPM L0s, Port 0
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x4
	Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] #0d [0000]
	Capabilities: [100] Advanced Error Reporting

03:00.0 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge A (rev 09) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 10
	Bus: primary=03, secondary=04, subordinate=04, sec-latency=64
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [44] Express PCI/PCI-X Bridge IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal+ Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 0
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
	Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [6c] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [d8] PCI-X bridge device.
		Secondary Status: 64bit+, 133MHz+, SCD-, USC-, SCO-, SRD- Freq=2
		Status: Bus=3 Dev=0 Func=0 64bit- 133MHz- SCD- USC-, SCO-, SRD-
		: Upstream: Capacity=65535, Commitment Limit=65535
		: Downstream: Capacity=65535, Commitment Limit=65535
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [300] Power Budgeting

03:00.2 PCI bridge: Intel Corporation 6700PXH PCI Express-to-PCI Bridge B (rev 09) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 10
	Bus: primary=03, secondary=05, subordinate=05, sec-latency=64
	I/O behind bridge: 0000f000-00000fff
	Memory behind bridge: fff00000-000fffff
	Prefetchable memory behind bridge: 00000000fff00000-0000000000000000
	Secondary status: 66Mhz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [44] Express PCI/PCI-X Bridge IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal+ Fatal+ Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
		Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s, Port 0
		Link: Latency L0s unlimited, L1 unlimited
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
	Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [6c] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [d8] PCI-X bridge device.
		Secondary Status: 64bit+, 133MHz+, SCD-, USC-, SCO-, SRD- Freq=3
		Status: Bus=3 Dev=0 Func=2 64bit- 133MHz- SCD- USC-, SCO-, SRD-
		: Upstream: Capacity=65535, Commitment Limit=65535
		: Downstream: Capacity=65535, Commitment Limit=65535
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [300] Power Budgeting

08:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 02)
	Subsystem: LSI Logic / Symbios Logic: Unknown device 3080
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Interrupt: pin A routed to IRQ 9
	Region 0: I/O ports at 2000 [size=256]
	Region 1: Memory at c8210000 (64-bit, non-prefetchable) [size=16K]
	Region 3: Memory at c8200000 (64-bit, non-prefetchable) [size=64K]
	[virtual] Expansion ROM at c2000000 [disabled] [size=2M]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] Express Endpoint IRQ 0
		Device: Supported: MaxPayload 4096 bytes, PhantFunc 0, ExtTag+
		Device: Latency L0s <64ns, L1 <1us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
		Link: Supported Speed 2.5Gb/s, Width x8, ASPM L0s L1, Port 0
		Link: Latency L0s <64ns, L1 <1us
		Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x8
	Capabilities: [98] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [b0] MSI-X: Enable- Mask- TabSize=1
		Vector table: BAR=1 offset=00002000
		PBA: BAR=1 offset=00003000
	Capabilities: [100] Advanced Error Reporting

0a:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
	Subsystem: Intel Corporation: Unknown device 115e
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at c8320000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at c8300000 (32-bit, non-prefetchable) [size=128K]
	Region 2: I/O ports at 3000 [size=32]
	[virtual] Expansion ROM at c2200000 [disabled] [size=128K]
	Capabilities: [c8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [d0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [e0] Express Endpoint IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <512ns, L1 <64us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
		Link: Supported Speed 2.5Gb/s, Width x4, ASPM L0s, Port 0
		Link: Latency L0s <4us, L1 <64us
		Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x4
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 64-92-0b-ff-ff-17-15-00

0a:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
	Subsystem: Intel Corporation: Unknown device 115e
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size 08
	Interrupt: pin B routed to IRQ 18
	Region 0: Memory at c8360000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at c8340000 (32-bit, non-prefetchable) [size=128K]
	Region 2: I/O ports at 3020 [size=32]
	[virtual] Expansion ROM at c2220000 [disabled] [size=128K]
	Capabilities: [c8] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-
	Capabilities: [d0] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [e0] Express Endpoint IRQ 0
		Device: Supported: MaxPayload 256 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <512ns, L1 <64us
		Device: AtnBtn- AtnInd- PwrInd-
		Device: Errors: Correctable- Non-Fatal- Fatal+ Unsupported-
		Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 512 bytes
		Link: Supported Speed 2.5Gb/s, Width x4, ASPM L0s, Port 0
		Link: Latency L0s <4us, L1 <64us
		Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
		Link: Speed 2.5Gb/s, Width x4
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 64-92-0b-ff-ff-17-15-00

0b:01.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02) (prog-if 00 [VGA])
	Subsystem: Super Micro Computer Inc: Unknown device 8080
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR+ FastB2B+
	Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
	Latency: 66 (2000ns min), Cache Line Size 08
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at d0000000 (32-bit, prefetchable) [size=128M]
	Region 1: I/O ports at 4000 [size=256]
	Region 2: Memory at c8400000 (32-bit, non-prefetchable) [size=64K]
	[virtual] Expansion ROM at c8420000 [disabled] [size=128K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-


[-- Attachment #4: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Re: logs attached. Re: [Xen-users] Can not findthe cdrom device in /dev/ afterbooted into xen(3.0.3)

[Keir Fraser]

Looks like the I/O ports are allocated correctly to the device in both cases
(both Xen and native). So I have no idea why the IDE PCI probing code isn't
picking up on this. At this point I'd be adding tracing to the two kernels
to find out where their probing paths diverge.

 -- Keir

On 1/12/06 7:19 pm, "Liang Yang" <multisyncfe991@hotmail.com> wrote:

> See attached.
> 
> ----- Original Message -----
> From: "Keir Fraser" <keir@xensource.com>
> To: "Keir Fraser" <keir@xensource.com>; "Liang Yang"
> <multisyncfe991@hotmail.com>; <tim.post@netkinetics.net>; "Petersson, Mats"
> <Mats.Petersson@amd.com>
> Cc: <xen-devel@lists.xensource.com>; <xen-users@lists.xensource.com>
> Sent: Friday, December 01, 2006 11:58 AM
> Subject: Re: [Xen-devel] Re: logs attached. Re: [Xen-users] Can not findthe
> cdrom device in /dev/ afterbooted into xen(3.0.3)
> 
> 
>> Lspci -vvv output for native and Xen kernels may be useful, just for
>> device
>> 00:1f.1 (the IDE device). Then we could see which I/O resources the device
>> is claiming in each case
>> 
>> -- Keir
>> 
>> On 1/12/06 6:56 pm, "Keir Fraser" <keir@xensource.com> wrote:
>> 
>>> Actually, now I look closer it seems that on native the IDE I/O ports are
>>> detected as 0x1860-0x1867, but the Xen kernel is failing to detect this
>>> and
>>> is then failing to register at the default 0x1f0, probably because a
>>> legacy
>>> ISA IDE driver is registered there. So there is definitely something odd
>>> going on here but tracking it down will probably require adding some
>>> kernel
>>> tracing (e.g., to ide_hwif_configure(), to determine why it is failing to
>>> find the special location of the IDE I/O ports).
>>> 
>>>  -- Keir
>>> 
>>> On 1/12/06 6:48 pm, "Liang Yang" <multisyncfe991@hotmail.com> wrote:
>>> 
>>>> I just download Xen source and do "make world;make
>>>> install;depmod..;mkinitrd...". I don't know which config file will be
>>>> used
>>>> if I build Xen like this (maybe the config-2.6.16.29-xen under the
>>>> directory
>>>> dist/install/boot).
>>>> 
>>>>  I did a grep with "CONFIG_BLK_DEV_PIIX" and found it it set to m in the
>>>> config-2.6.16.29-xen. I did a modprobe piix, however my CD-ROM is still
>>>> not
>>>> fired up (nothing is show up /dev/ as either cdrom or hd*).
>>>> 
>>>> Liang
>>>> 
>>>> ----- Original Message -----
>>>> From: "Keir Fraser" <keir@xensource.com>
>>>> To: "Liang Yang" <multisyncfe991@hotmail.com>;
>>>> <tim.post@netkinetics.net>;
>>>> "Petersson, Mats" <Mats.Petersson@amd.com>
>>>> Cc: <xen-devel@lists.xensource.com>; <xen-users@lists.xensource.com>
>>>> Sent: Friday, December 01, 2006 11:34 AM
>>>> Subject: [Xen-devel] Re: logs attached. Re: [Xen-users] Can not find the
>>>> cdrom device in /dev/ afterbooted into xen(3.0.3)
>>>> 
>>>> 
>>>>> On 1/12/06 6:27 pm, "Liang Yang" <multisyncfe991@hotmail.com> wrote:
>>>>> 
>>>>>> Hi Tim, Keir and Mats,
>>>>>> 
>>>>>> I attached all the detailed log files (text file format). The file
>>>>>> extension
>>>>>> indicate the version of environment. Please take a look.
>>>>> 
>>>>> ESB2 should be supported by the piix IDE driver. Which XenLinux kernel
>>>>> config are you using? Either you need the driver compiled into the
>>>>> kernel,
>>>>> or you need to load it as a module. Look for a line containing
>>>>> CONFIG_BLK_DEV_PIIX in your .config -- it should be "=m" or "=y".
>>>>> 
>>>>> If it's compiled as a module, and you installed the modules on your
>>>>> filesystem, you may be able to fire up the CDROM drive by typing
>>>>> 'modprobe
>>>>> piix'.
>>>>> 
>>>>> -- Keir
>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Xen-devel mailing list
>>>>> Xen-devel@lists.xensource.com
>>>>> http://lists.xensource.com/xen-devel
>>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xensource.com
>>>> http://lists.xensource.com/xen-devel
>>> 
>> 
>> 
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Re: logs attached. Re: [Xen-users] Can not findthe cdrom device in /dev/ afterbooted into xen(3.0.3)

[Alan]

On Fri, 01 Dec 2006 19:24:33 +0000
Keir Fraser <keir@xensource.com> wrote:

> Looks like the I/O ports are allocated correctly to the device in both cases
> (both Xen and native). So I have no idea why the IDE PCI probing code isn't
> picking up on this. At this point I'd be adding tracing to the two kernels
> to find out where their probing paths diverge.

Looking over the current kernel code it is known to work in the non-Xen
case. The native mode on the ESB2 has other problems recently reported
but they would cause hangs later with stuck interrupts. Since I've got
bugs filed on this I know the detection works outside of Xen.

The old IDE probe code predates PCI so conveniently the PCI side of the
scan logic is all in setup-pci.c. Modules registering with ide during
init are added to a list and all run post init, modules added later get
their setup methods run immediately. Thus you can trace loading the piix
module pretty directly through idepci_register_driver and
ide_setup_pci_device, beyond that you are pretty much out of PCI territory

Re: [Xen-devel] Re: logs attached. Re: Can not findthe cdrom device in /dev/ afterbooted into xen(3.0.3)

[Tim Post]

On Fri, 2006-12-01 at 12:19 -0700, Liang Yang wrote:
> See attached.
> Hi Tim, Keir and Mats,
> 
> I attached all the detailed log files (text file format). The file
extension 
> indicate the version of environment. Please take a look.
> 
> Thanks,
> 
> Liang
> 

Thought I'd add, it looks like your board is breaking up IDE and SATA on
two continents and both devices should be accessible.. however, you may
still need sr_mod too.

sr_mod, ide_cd and cdrom may do it if ide_cd and cdrom alone do not. It
depends on your MB (and type of cdrom). If its a burner, just ide_cd and
cdrom *should* get you read access to at least see the device, but I try
to avoid Intel and I'm not quite sure. 

If its a lite-on burner (or similar), chances are you may need sr_mod as
its treated as a SCSI device when its writing, and its not showing up
because the device isn't initializing properly. Well, it is, but
modprobe doesn't think it is.

I have no idea why ide_cd won't see it in read only .. can you check
dmesg to see if one of the three modules failed to load?


To recap

modprobe sr_mod
modprobe ide_cd
modprobe cdrom

Best,
-Tim

Re: Re: logs attached. Re: [Xen-users] Can not find the cdrom device in /dev/ afterbooted into xen(3.0.3)

[Alan]

On Fri, 01 Dec 2006 18:56:38 +0000
Keir Fraser <keir@xensource.com> wrote:

> Actually, now I look closer it seems that on native the IDE I/O ports are
> detected as 0x1860-0x1867, but the Xen kernel is failing to detect this and
> is then failing to register at the default 0x1f0, probably because a legacy
> ISA IDE driver is registered there.

More likely becaue as you already said the I/O ports are at 0x1860-1867.
In native mode an ATA channel honours the PCI spec, in legacy mode it
uses magic hard coded addresses.

Also if the device is on the SATA side you need libata and drivers/ata
support not the legacy PIIX driver for the old drivers/ide code.

Alan

Re: Re: logs attached. Re: [Xen-users] Can not find the cdrom device in /dev/ afterbooted into xen(3.0.3)

[Keir Fraser]

On 1/12/06 7:10 pm, "Alan" <alan@lxorguk.ukuu.org.uk> wrote:

> Also if the device is on the SATA side you need libata and drivers/ata
> support not the legacy PIIX driver for the old drivers/ide code.

The Xen lsmod is listing libata and ata_piix *and* the legacy piix module.
So it should probably work one way or the other. I assume native is using
the legacy driver since the drive appears as /dev/hda, not /dev/sdx.

 -- Keir

Re: [Xen-devel] Re: logs attached. Re: Can not find the cdrom device in /dev/ afterbooted into xen(3.0.3)

[Tim Post]

On Fri, 2006-12-01 at 11:48 -0700, Liang Yang wrote:
> I just download Xen source and do "make world;make 
> install;depmod..;mkinitrd...". I don't know which config file will be used 
> if I build Xen like this (maybe the config-2.6.16.29-xen under the directory 
> dist/install/boot).
> 
>  I did a grep with "CONFIG_BLK_DEV_PIIX" and found it it set to m in the 
> config-2.6.16.29-xen. I did a modprobe piix, however my CD-ROM is still not 
> fired up (nothing is show up /dev/ as either cdrom or hd*).
> 

what does modprobe ide_cd do for you? Remember its going to show up
as /dev/hd(b)? (c)? when its loaded.

If modprobe throws an error for that, something is *really* wrong.

the lspci from the native dump shows a bunch of undetected hardware, the
lspci from Xen looks quite a bit better.

I see ide_generic, but no ide_cd ... Give it a whirl and please post
back with results.

> Liang

Best,
-Tim

Re: Can not find the cdrom device in /dev/ after booted into xen(3.0.3)

[Tim Post]

On Fri, 2006-12-01 at 09:12 -0700, Liang Yang wrote:

> 
> Could anyone share some solutions?
> 
> Thanks,
> 
> Liang
> 

I forgot to ask, did you install from source or binary packages?

Re: [Xen-users] Can not find the cdrom device in /dev/ afterbooted into xen(3.0.3)

[Liang Yang]

Hi Tim,

I installed from source. I still think it could be caused by Xen instead of 
RHEL. The reason I tested RHEL 4.4 with Xen version which is older than 
3.0.3 and I don't have such problems. I also tested RHEL 5 Beta which has 
Xen integrated and it does not have this problem either.

Regards,

Liang

----- Original Message ----- 
From: "Tim Post" <tim.post@netkinetics.net>
To: "Liang Yang" <multisyncfe991@hotmail.com>
Cc: <xen-devel@lists.xensource.com>; <xen-users@lists.xensource.com>
Sent: Friday, December 01, 2006 11:28 AM
Subject: Re: [Xen-users] Can not find the cdrom device in /dev/ afterbooted 
into xen(3.0.3)


> On Fri, 2006-12-01 at 09:12 -0700, Liang Yang wrote:
>
>>
>> Could anyone share some solutions?
>>
>> Thanks,
>>
>> Liang
>>
>
> I forgot to ask, did you install from source or binary packages?
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>