ACPI hotplug

ACPI hotplug

[Paul Ionescu]

Hi,

I just read that 2.6.11-rc1 does support ACPI hotplug.
What does this really mean ?
I found some new files in /sys/firmware:
find /sys/firmware/ | grep eject
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB7/URTH/UPDK/eject
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB0/URTH/UPDK/eject
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/SCND/MSTR/eject
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT1/eject
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/FDC/FDD0/eject

But what can I do with them, and what else is there for hotplug ?
Does it support docking stations ?

Thanks,
Paul



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

Re: ACPI hotplug

[Keshavamurthy Anil S]

On Thu, Jan 13, 2005 at 03:02:37PM +0100, Paul Ionescu wrote:
> Hi,
> 
> I just read that 2.6.11-rc1 does support ACPI hotplug.
> What does this really mean ?

2.6.11-rc1 now supports physical CPU hotplug and these eject files
were added to support the same. Once the cpu's are logically offlined,
they can be physically removed by echoing 1 onto the eject file
under _SB/PCI0/LSBX/CPUX/eject.


> I found some new files in /sys/firmware:
> find /sys/firmware/ | grep eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB7/URTH/UPDK/eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB0/URTH/UPDK/eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/SCND/MSTR/eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT1/eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/FDC/FDD0/eject

Looks like your DSDT has _EJx methods for many other types of devices,
either you can enhance these devices drivers to support user
mode eject or you can simply not create "eject" file.

> 
> But what can I do with them, and what else is there for hotplug ?
> Does it support docking stations ?

Does this "eject" file has any side effects which needs to be addressed,
please let me know.

-Anil




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

Re: ACPI hotplug

[Rajesh Shah]

On Thu, Jan 13, 2005 at 03:02:37PM +0100, Paul Ionescu wrote:
> 
> I just read that 2.6.11-rc1 does support ACPI hotplug.
> What does this really mean ?
> I found some new files in /sys/firmware:
> find /sys/firmware/ | grep eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB7/URTH/UPDK/eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB0/URTH/UPDK/eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/SCND/MSTR/eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT1/eject
> /sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/FDC/FDD0/eject
> 
The new ACPI code is to  support _physical_ insertion/removal of
cpus and "containers" (nodes) that have cpus and memory. This
requires firmware/platform support.  Linux already supports ACPI
(as well as SHPC/PCI-Express) based physical insertion/removal of
IO adapters independent of the new code in 2.6.11-rc1. The ACPI 
namespace you listed above shows ACPI ejectable IO devices. This
is handled by the existing acpiphp code, not the new processor
or container code.

Rajesh



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

Re: ACPI hotplug

[Paul Ionescu]

Hi Rajesh,

I was hoping that I can use my docking station without
being necessary to boot docked.
But is not the case.
I tried this way:
Booted normaly, loaded acpiphp (even said found a pci
slot), then plug the ThinkPad in the dockingstation,
but nothing happened. No new devices get added.
Then I tried to boot in the dockingstation and while I
see all the new devices (this was always the case), I
cannot remove the laptop from the docking station
because it does not senses I push the eject button on
it.


Thanks,
Paul
--- Rajesh Shah <rajesh.shah-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:

> On Thu, Jan 13, 2005 at 03:02:37PM +0100, Paul
> Ionescu wrote:
> > 
> > I just read that 2.6.11-rc1 does support ACPI
> hotplug.
> > What does this really mean ?
> > I found some new files in /sys/firmware:
> > find /sys/firmware/ | grep eject
> >
>
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB7/URTH/UPDK/eject
> >
>
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB0/URTH/UPDK/eject
> >
>
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/SCND/MSTR/eject
> >
>
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT1/eject
> >
>
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/FDC/FDD0/eject
> > 
> The new ACPI code is to  support _physical_
> insertion/removal of
> cpus and "containers" (nodes) that have cpus and
> memory. This
> requires firmware/platform support.  Linux already
> supports ACPI
> (as well as SHPC/PCI-Express) based physical
> insertion/removal of
> IO adapters independent of the new code in
> 2.6.11-rc1. The ACPI 
> namespace you listed above shows ACPI ejectable IO
> devices. This
> is handled by the existing acpiphp code, not the new
> processor
> or container code.
> 
> Rajesh
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

Re: ACPI hotplug

[Paul Ionescu]

Hi Keshavamurthy,

The eject files have no any side effect for me.
I just tried to play with them for my devices.

I tried on a docked computer and I have this:
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB7/URTH/UPDK/eject
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB0/URTH/UPDK/eject
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/SCND/MSTR/eject
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCI1/DOCK/eject
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/UART/eject
Trying to echo 1 >
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCI1/DOCK/eject
did not undocked the laptop as I hoped.

I thought I can use my docking station without being
necessary to boot docked.
But is not the case.
I tried this way:
Booted normaly, loaded acpiphp (even said found a pci
slot), then plug the ThinkPad in the dockingstation,
but nothing happened. No new devices get added.
Then I tried to boot in the dockingstation and while I
see all the new devices (this was always the case), I
cannot remove the laptop from the docking station
because it does not senses I push the eject button on
it.


Thanks,
Paul
--- Keshavamurthy Anil S
<anil.s.keshavamurthy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:

> On Thu, Jan 13, 2005 at 03:02:37PM +0100, Paul
> Ionescu wrote:
> > Hi,
> > 
> > I just read that 2.6.11-rc1 does support ACPI
> hotplug.
> > What does this really mean ?
> 
> 2.6.11-rc1 now supports physical CPU hotplug and
> these eject files
> were added to support the same. Once the cpu's are
> logically offlined,
> they can be physically removed by echoing 1 onto the
> eject file
> under _SB/PCI0/LSBX/CPUX/eject.
> 
> 
> > I found some new files in /sys/firmware:
> > find /sys/firmware/ | grep eject
> >
>
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB7/URTH/UPDK/eject
> >
>
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB0/URTH/UPDK/eject
> >
>
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/SCND/MSTR/eject
> >
>
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT1/eject
> >
>
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/FDC/FDD0/eject
> 
> Looks like your DSDT has _EJx methods for many other
> types of devices,
> either you can enhance these devices drivers to
> support user
> mode eject or you can simply not create "eject"
> file.
> 
> > 
> > But what can I do with them, and what else is
> there for hotplug ?
> > Does it support docking stations ?
> 
> Does this "eject" file has any side effects which
> needs to be addressed,
> please let me know.
> 
> -Anil
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

Re: ACPI hotplug

[Rajesh Shah]

On Sat, Jan 15, 2005 at 02:14:53AM -0800, Paul Ionescu wrote:
> 
> I was hoping that I can use my docking station without
> being necessary to boot docked.

I see. Docking functionality needs more support that does
not live in acpiphp. There have been some recent posts,
for example, about docking support in Thinkpads and
this functionality is separately enabled by a different
ACPI config option. Grep for ACPI_IBM in acpi/Kconfig
and see Documentation/ibm-acpi.txt for more details.

Rajesh



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

Re: ACPI hotplug

[Paul Ionescu]

Hi Rajesh,

I do have an IBM Thinkpad, and I am using IBM_ACPI
module. But this module is limited in functionality
until we get proper ACPI hotplug support.

The problem is that current acpi implementation cannot
dynamically add devices not existant at boot time, or
this is what I was told.
If I boot docked in, I have more ACPI devices than if
I boot undocked, and that info is not possible for
ACPI to get dynamically when I plug the laptop in
docking station. (IE: find /sys/firmware/acpi produces
different output for docked and undocked laptop).
IBM_ACPI module deals with some non ACPI standard
functionality, but it says in the README file that you
need to have booted with the laptop docked, otherwise
it is unable to see the devices.

Thanks,
Paul


--- Rajesh Shah <rajesh.shah-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:

> On Sat, Jan 15, 2005 at 02:14:53AM -0800, Paul
> Ionescu wrote:
> > 
> > I was hoping that I can use my docking station
> without
> > being necessary to boot docked.
> 
> I see. Docking functionality needs more support that
> does
> not live in acpiphp. There have been some recent
> posts,
> for example, about docking support in Thinkpads and
> this functionality is separately enabled by a
> different
> ACPI config option. Grep for ACPI_IBM in
> acpi/Kconfig
> and see Documentation/ibm-acpi.txt for more details.
> 
> Rajesh
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

Re: ACPI hotplug

[Rajesh Shah]

On Mon, Jan 17, 2005 at 02:17:51PM -0800, Paul Ionescu wrote:
> 
> I do have an IBM Thinkpad, and I am using IBM_ACPI
> module. But this module is limited in functionality

OK.

> If I boot docked in, I have more ACPI devices than if
> I boot undocked, and that info is not possible for
> ACPI to get dynamically when I plug the laptop in

I see. Can you please send the dmesg output after enabling
debug messages in acpiphp (acpiphp supports a "debug"
module param)?  I'd like to see if acpiphp is even 
installing a notify handler and triggering at dock.

Also, can you send the lspci -vv output with the 
laptop docked at boot time? 

Thanks,
Rajesh



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

RE: ACPI hotplug

[Li, Shaohua]

Hi,
Docking station generally includes a PCI bridge, some PCI devices and/or
some PNP devices. Support docking station hotplug isn't so easy. You
must support PCI bridge hotplug (acpiphp possibly can do something, but
it doesn't support bridge hotplug. In addition, the docking bridge in
Thinkpad is very special, it's a transparent bridge. Normal PCI hotplug
can't support it.) and support PNP device hotplug (PNPACPI is designed
to do it, but now it doesn't support hotplug). IBM_ACPI just can do
eject and dock, but can't enumerate devices under the dock.

Thanks,
Shaohua

>> I do have an IBM Thinkpad, and I am using IBM_ACPI
>> module. But this module is limited in functionality
>
>OK.
>
>> If I boot docked in, I have more ACPI devices than if
>> I boot undocked, and that info is not possible for
>> ACPI to get dynamically when I plug the laptop in
>
>I see. Can you please send the dmesg output after enabling
>debug messages in acpiphp (acpiphp supports a "debug"
>module param)?  I'd like to see if acpiphp is even
>installing a notify handler and triggering at dock.
>
>Also, can you send the lspci -vv output with the
>laptop docked at boot time?


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

RE: ACPI hotplug

[Paul Ionescu]

Hi Li,

I tried to undock with IBM_ACPI in kernel 2.6.10, and
it hang my laptop.
Then I tried to dock my laptop with IBM_ACPI, it
docked OK (fans starts, led lit), but no new devices
appears like you expected.
Now, I can live with the fact that I have to boot in
dock to see all devices, but what bothers me is that
after booting in dock, and ACPI seeing all devices, I
still can undock/dock reliably even if ACPI has all
the info it needs.

Thanks,
Paul


--- "Li, Shaohua" <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:

> Hi,
> Docking station generally includes a PCI bridge,
> some PCI devices and/or
> some PNP devices. Support docking station hotplug
> isn't so easy. You
> must support PCI bridge hotplug (acpiphp possibly
> can do something, but
> it doesn't support bridge hotplug. In addition, the
> docking bridge in
> Thinkpad is very special, it's a transparent bridge.
> Normal PCI hotplug
> can't support it.) and support PNP device hotplug
> (PNPACPI is designed
> to do it, but now it doesn't support hotplug).
> IBM_ACPI just can do
> eject and dock, but can't enumerate devices under
> the dock.
> 
> Thanks,
> Shaohua
> 
> >> I do have an IBM Thinkpad, and I am using
> IBM_ACPI
> >> module. But this module is limited in
> functionality
> >
> >OK.
> >
> >> If I boot docked in, I have more ACPI devices
> than if
> >> I boot undocked, and that info is not possible
> for
> >> ACPI to get dynamically when I plug the laptop in
> >
> >I see. Can you please send the dmesg output after
> enabling
> >debug messages in acpiphp (acpiphp supports a
> "debug"
> >module param)?  I'd like to see if acpiphp is even
> >installing a notify handler and triggering at dock.
> >
> >Also, can you send the lspci -vv output with the
> >laptop docked at boot time?
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

Re: ACPI hotplug

[Paul Ionescu]

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

Hi Rajesh,

I attached the info requested.
I also attached a "find /sys/firmware" when docked.
I have played a little more with this and here is what
I found:
If I booted undocked, when I insert the laptop in
dock, the dock is still silent and I receive a  
acpiphp_glue: handle_hotplug_event_func: Bus check
notify on \_SB_.PCI0.PCI1.DOCK
acpiphp_glue: No new device found

Then when I do "echo dock > /proc/acpi/ibm/dock", it
started the fans and leds, but no other event or
notify is received, and of course no new devices are
found.
Then I do "echo undock > /proc/acpi/ibm/dock", and
press the dock button to undock the laptop, it does
undock, but no event or notify received.

Then I booted in dock, all devices are there, but when
I undock, no event or notify is received, and of
course, all devices are still present after undocking,
which is false. I think this is why it used to hang
here, because it tried to use an unexisting device.


Best regars,
Paul




--- Rajesh Shah <rajesh.shah-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:

> On Mon, Jan 17, 2005 at 02:17:51PM -0800, Paul
> Ionescu wrote:
> > 
> > I do have an IBM Thinkpad, and I am using IBM_ACPI
> > module. But this module is limited in
> functionality
> 
> OK.
> 
> > If I boot docked in, I have more ACPI devices than
> if
> > I boot undocked, and that info is not possible for
> > ACPI to get dynamically when I plug the laptop in
> 
> I see. Can you please send the dmesg output after
> enabling
> debug messages in acpiphp (acpiphp supports a
> "debug"
> module param)?  I'd like to see if acpiphp is even 
> installing a notify handler and triggering at dock.
> 
> Also, can you send the lspci -vv output with the 
> laptop docked at boot time? 
> 
> Thanks,
> Rajesh
> 
> 


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - 250MB free storage. Do more. Manage less. 
http://info.mail.yahoo.com/mail_250

[-- Attachment #2: acpiphp.log --]
[-- Type: application/octet-stream, Size: 9691 bytes --]

Jan 18 09:27:46 r50p kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.4
Jan 18 09:27:46 r50p kernel: acpiphp_glue: found PCI-to-PCI bridge at PCI 0000:00:1e.0
Jan 18 09:27:46 r50p kernel: acpiphp_glue: 16bit I/O range: 4000-8fff
Jan 18 09:27:46 r50p kernel: acpiphp_glue: 32bit Memory range: c0200000-cfffffff
Jan 18 09:27:46 r50p kernel: acpiphp_glue: 32bit Prefetchable memory range: e8000000-efffffff
Jan 18 09:27:46 r50p kernel: acpiphp_glue: _HPP evaluation failed
Jan 18 09:27:46 r50p kernel: acpiphp_pci: Device 0000:02:00.0
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[0] 0xb0000000 - 0xb0000fff (0x200)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = 00000000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=b0000000 req_size =1000 node=c1e28c24, base=c0200000, length=fe00000
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[7] 0x60000000 - 0x603fffff (0x1200)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = 00000000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=60000000 req_size =400000 node=f7d4d938, base=e8000000, length=8000000
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[8] 0x60400000 - 0x607fffff (0x200)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = 00000000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=60400000 req_size =400000 node=c1e28c24, base=c0200000, length=fe00000
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[9] 0x4000 - 0x40ff (0x100)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = 00000000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=4000 req_size =100 node=f7c13e60, base=4000, length=5000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 2nd req_base=4000 req_size =100 node=f7c13e60, base=4000, length=5000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : split 2
Jan 18 09:27:46 r50p kernel: acpiphp_res: : got one!!!
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[10] 0x4400 - 0x44ff (0x100)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = 00000000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=4400 req_size =100 node=c1f0b6fc, base=4100, length=4f00
Jan 18 09:27:46 r50p kernel: acpiphp_res: : split 1
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 2nd req_base=4400 req_size =100 node=c1f0b6fc, base=4400, length=4c00
Jan 18 09:27:46 r50p kernel: acpiphp_res: : split 2
Jan 18 09:27:46 r50p kernel: acpiphp_res: : got one!!!
Jan 18 09:27:46 r50p kernel: acpiphp_pci: Device 0000:02:00.1
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[0] 0xb1000000 - 0xb1000fff (0x200)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = 00000000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=b1000000 req_size =1000 node=c1e28c24, base=c0200000, length=fe00000
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[7] 0x60800000 - 0x60bfffff (0x1200)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = 00000000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=60800000 req_size =400000 node=f7d4d938, base=e8000000, length=8000000
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[8] 0x60c00000 - 0x60ffffff (0x200)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = 00000000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=60c00000 req_size =400000 node=c1e28c24, base=c0200000, length=fe00000
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[9] 0x4800 - 0x48ff (0x100)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = f7c13e60
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->base = 0x4500
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next->base = 0x4100
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=4800 req_size =100 node=f7c13e60, base=4100, length=300
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=4800 req_size =100 node=f48116fc, base=4500, length=4b00
Jan 18 09:27:46 r50p kernel: acpiphp_res: : split 1
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 2nd req_base=4800 req_size =100 node=f48116fc, base=4800, length=4800
Jan 18 09:27:46 r50p kernel: acpiphp_res: : split 2
Jan 18 09:27:46 r50p kernel: acpiphp_res: : got one!!!
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[10] 0x4c00 - 0x4cff (0x100)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = f481190c
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->base = 0x4100
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next->base = 0x4900
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=4c00 req_size =100 node=f7c13e60, base=4100, length=300
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=4c00 req_size =100 node=c1f0b6fc, base=4500, length=300
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=4c00 req_size =100 node=f481190c, base=4900, length=4700
Jan 18 09:27:46 r50p kernel: acpiphp_res: : split 1
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 2nd req_base=4c00 req_size =100 node=f481190c, base=4c00, length=4400
Jan 18 09:27:46 r50p kernel: acpiphp_res: : split 2
Jan 18 09:27:46 r50p kernel: acpiphp_res: : got one!!!
Jan 18 09:27:46 r50p kernel: acpiphp_pci: Device 0000:02:01.0
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[0] 0xc0220000 - 0xc023ffff (0x200)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = 00000000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=c0220000 req_size =20000 node=c1e28c24, base=c0200000, length=fe00000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : split 1
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 2nd req_base=c0220000 req_size =20000 node=c1e28c24, base=c0220000, length=fde0000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : split 2
Jan 18 09:27:46 r50p kernel: acpiphp_res: : got one!!!
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[1] 0xc0200000 - 0xc020ffff (0x200)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = f481190c
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->base = 0xc0240000
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next->base = 0xc0200000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=c0200000 req_size =10000 node=f481190c, base=c0200000, length=20000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 2nd req_base=c0200000 req_size =10000 node=f481190c, base=c0200000, length=20000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : split 2
Jan 18 09:27:46 r50p kernel: acpiphp_res: : got one!!!
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[2] 0x8000 - 0x803f (0x101)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = c1f0b6fc
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->base = 0x4100
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next->base = 0x4500
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=8000 req_size =40 node=f7c13e60, base=4100, length=300
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=8000 req_size =40 node=c1f0b6fc, base=4500, length=300
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=8000 req_size =40 node=f48116fc, base=4900, length=300
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=8000 req_size =40 node=c1f0b8e0, base=4d00, length=4300
Jan 18 09:27:46 r50p kernel: acpiphp_res: : split 1
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 2nd req_base=8000 req_size =40 node=c1f0b8e0, base=8000, length=1000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : split 2
Jan 18 09:27:46 r50p kernel: acpiphp_res: : got one!!!
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[6] 0x0 - 0xffff (0x7200)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = 00000000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=0 req_size =10000 node=f7d4d938, base=e8000000, length=8000000
Jan 18 09:27:46 r50p kernel: acpiphp_pci: Device 0000:02:02.0
Jan 18 09:27:46 r50p kernel: acpiphp_pci: BAR[0] 0xc0210000 - 0xc021ffff (0x200)
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next = f7ccab1c
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->base = 0xc0210000
Jan 18 09:27:46 r50p kernel: acpiphp_res: *head->next->base = 0xc0240000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 1st req_base=c0210000 req_size =10000 node=c1e28c24, base=c0210000, length=10000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : 2nd req_base=c0210000 req_size =10000 node=c1e28c24, base=c0210000, length=10000
Jan 18 09:27:46 r50p kernel: acpiphp_res: : got one!!!
Jan 18 09:27:46 r50p kernel: acpiphp_glue: found ACPI PCI Hotplug slot at PCI 02:03 Slot:-1
Jan 18 09:27:46 r50p kernel: acpiphp_glue: Bridge resource:
Jan 18 09:27:46 r50p kernel: acpiphp_res: I/O resource:
Jan 18 09:27:46 r50p kernel: acpiphp_res: [00] 00004100 - 000043ff
Jan 18 09:27:46 r50p kernel: acpiphp_res: [01] 00004500 - 000047ff
Jan 18 09:27:46 r50p kernel: acpiphp_res: [02] 00004900 - 00004bff
Jan 18 09:27:46 r50p kernel: acpiphp_res: [03] 00008040 - 00008fff
Jan 18 09:27:46 r50p kernel: acpiphp_res: [04] 00004d00 - 00007fff
Jan 18 09:27:46 r50p kernel: acpiphp_res: MEM resource:
Jan 18 09:27:46 r50p kernel: acpiphp_res: [00] c0240000 - cfffffff
Jan 18 09:27:46 r50p kernel: acpiphp_res: PMEM resource:
Jan 18 09:27:46 r50p kernel: acpiphp_res: [00] e8000000 - efffffff
Jan 18 09:27:46 r50p kernel: acpiphp_res: BUS resource:
Jan 18 09:27:46 r50p kernel: acpiphp_glue: Bus2 1slot(s)
Jan 18 09:27:46 r50p kernel: acpiphp_glue: Total 1slots
Jan 18 09:27:46 r50p kernel: acpiphp: Slot [4294967295] registered

Here I docked the thinkpad:

Jan 18 09:28:26 r50p kernel: acpiphp_glue: handle_hotplug_event_func: Bus check notify on \_SB_.PCI0.PCI1.DOCK
Jan 18 09:28:26 r50p kernel: acpiphp_glue: No new device found

When I docked the thinkpad, the dock was still dead, untill I did "echo dock > /proc/acpi/ibm/dock" and then it started the fans and leds.
But the above notify was received just as soon as I docked the thinkpad, and the dock was still silent (no fans, no leds).
When I echo-ed dock in /proc/acpi/ibm/dock, the dock started some leds and fan, but the acpiphp was not receiving anything new.



[-- Attachment #3: lspci-docked --]
[-- Type: application/octet-stream, Size: 17520 bytes --]

Here is a brief lspci:

00:00.0 Host bridge: Intel Corp. 82855PM Processor to I/O Controller (rev 03)
00:01.0 PCI bridge: Intel Corp. 82855PM Processor to AGP Controller (rev 03)
00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corp. 82801 Mobile PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corp. 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4-M) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc M10 NT [FireGL Mobility T2] (rev 80)
02:00.0 CardBus bridge: Texas Instruments PCI4520 PC card Cardbus Controller (rev 01)
02:00.1 CardBus bridge: Texas Instruments PCI4520 PC card Cardbus Controller (rev 01)
02:01.0 Ethernet controller: Intel Corp. 82540EP Gigabit Ethernet Controller (Mobile) (rev 03)
02:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
02:03.0 PCI bridge: Texas Instruments PCI2032 PCI Docking Bridge
09:00.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 02)
09:00.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 02)
09:01.0 IDE interface: Silicon Image, Inc. (formerly CMD Technology Inc) PCI0648 (rev 01)
09:02.0 CardBus bridge: Texas Instruments PCI1420
09:02.1 CardBus bridge: Texas Instruments PCI1420
0e:00.0 Ethernet controller: 3Com Corporation 3cCFE575CT CardBus [Cyclone] (rev 10)

and lspci -vv

00:00.0 Host bridge: Intel Corp. 82855PM Processor to I/O Controller (rev 03)
	Subsystem: IBM: Unknown device 0529
	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
	Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
	Capabilities: [e4] Vendor Specific Information
	Capabilities: [a0] AGP version 2.0
		Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
		Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=x1

00:01.0 PCI bridge: Intel Corp. 82855PM Processor to AGP Controller (rev 03) (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: 96
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: c0100000-c01fffff
	Prefetchable memory behind bridge: e0000000-e7ffffff
	Secondary status: 66Mhz+ FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-

00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01) (prog-if 00 [UHCI])
	Subsystem: IBM: Unknown device 052d
	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 5
	Region 4: I/O ports at 1800 [size=32]

00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01) (prog-if 00 [UHCI])
	Subsystem: IBM: Unknown device 052d
	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 7
	Region 4: I/O ports at 1820 [size=32]

00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01) (prog-if 00 [UHCI])
	Subsystem: IBM: Unknown device 052d
	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 7
	Region 4: I/O ports at 1840 [size=32]

00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01) (prog-if 20 [EHCI])
	Subsystem: IBM: Unknown device 052e
	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 D routed to IRQ 11
	Region 0: Memory at c0000000 (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 Corp. 82801 Mobile PCI Bridge (rev 81) (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
	Bus: primary=00, secondary=02, subordinate=0f, sec-latency=64
	I/O behind bridge: 00004000-00009fff
	Memory behind bridge: c0200000-cfffffff
	Prefetchable memory behind bridge: e8000000-f00fffff
	Secondary status: 66Mhz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-

00:1f.0 ISA bridge: Intel Corp. 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
	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 Corp. 82801DBM (ICH4-M) IDE Controller (rev 01) (prog-if 8a [Master SecP PriP])
	Subsystem: IBM: Unknown device 052d
	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 7
	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]
	Region 5: Memory at 5ff79000 (32-bit, non-prefetchable) [size=1K]

00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus Controller (rev 01)
	Subsystem: IBM: Unknown device 052d
	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 5
	Region 4: I/O ports at 1880 [size=32]

00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
	Subsystem: IBM: Unknown device 0554
	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 5
	Region 0: I/O ports at 1c00 [size=256]
	Region 1: I/O ports at 18c0 [size=64]
	Region 2: Memory at c0000c00 (32-bit, non-prefetchable) [size=512]
	Region 3: Memory at c0000800 (32-bit, non-prefetchable) [size=256]
	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-

00:1f.6 Modem: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01) (prog-if 00 [Generic])
	Subsystem: IBM: Unknown device 0525
	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 5
	Region 0: I/O ports at 2400 [size=256]
	Region 1: I/O ports at 2000 [size=128]
	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-

01:00.0 VGA compatible controller: ATI Technologies Inc M10 NT [FireGL Mobility T2] (rev 80) (prog-if 00 [VGA])
	Subsystem: IBM: Unknown device 054f
	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 5
	Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
	Region 1: I/O ports at 3000 [size=256]
	Region 2: Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [58] AGP version 2.0
		Status: RQ=80 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
		Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none>
	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-

02:00.0 CardBus bridge: Texas Instruments PCI4520 PC card Cardbus Controller (rev 01)
	Subsystem: IBM: Unknown device 0552
	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: 168, Cache Line Size 20
	Interrupt: pin A routed to IRQ 5
	Region 0: Memory at b0000000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=02, secondary=12, subordinate=15, sec-latency=176
	Memory window 0: 60000000-603ff000 (prefetchable)
	Memory window 1: 60400000-607ff000
	I/O window 0: 00004000-000040ff
	I/O window 1: 00004400-000044ff
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
	16-bit legacy interface ports at 0001

02:00.1 CardBus bridge: Texas Instruments PCI4520 PC card Cardbus Controller (rev 01)
	Subsystem: IBM: Unknown device 0552
	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: 168, Cache Line Size 20
	Interrupt: pin B routed to IRQ 5
	Region 0: Memory at b1000000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=02, secondary=16, subordinate=19, sec-latency=176
	Memory window 0: 60800000-60bff000 (prefetchable)
	Memory window 1: 60c00000-60fff000
	I/O window 0: 00004800-000048ff
	I/O window 1: 00004c00-00004cff
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
	16-bit legacy interface ports at 0001

02:01.0 Ethernet controller: Intel Corp. 82540EP Gigabit Ethernet Controller (Mobile) (rev 03)
	Subsystem: IBM PRO/1000 MT Mobile Connection
	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: 64 (63750ns min), Cache Line Size 08
	Interrupt: pin A routed to IRQ 5
	Region 0: Memory at c0240000 (32-bit, non-prefetchable) [size=128K]
	Region 1: Memory at c0200000 (32-bit, non-prefetchable) [size=64K]
	Region 2: I/O ports at 8000 [size=64]
	Capabilities: [dc] 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-

02:02.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
	Subsystem: Unknown device 17ab:8331
	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: 80 (2500ns min, 7000ns max), Cache Line Size 08
	Interrupt: pin A routed to IRQ 7
	Region 0: Memory at c0210000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [44] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=2 PME-

02:03.0 PCI bridge: Texas Instruments PCI2032 PCI Docking Bridge (prog-if 01 [Subtractive decode])
	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: 64, Cache Line Size 08
	Bus: primary=02, secondary=09, subordinate=0f, sec-latency=68
	I/O behind bridge: 00000000-00000fff
	Memory behind bridge: 00000000-000fffff
	Prefetchable memory behind bridge: 00000000-000fffff
	Secondary status: 66Mhz- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
	Capabilities: [80] Power Management version 1
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
		Bridge: PM- B3+

09:00.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 02)
	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: 132 (4000ns min, 10000ns max)
	Interrupt: pin A routed to IRQ 5
	Region 0: Memory at f0000000 (32-bit, prefetchable) [size=4K]

09:00.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 02)
	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: 64 (1000ns min, 63750ns max)
	Interrupt: pin A routed to IRQ 5
	Region 0: Memory at f0001000 (32-bit, prefetchable) [size=4K]

09:01.0 IDE interface: Silicon Image, Inc. (formerly CMD Technology Inc) PCI0648 (rev 01) (prog-if 8f [Master SecP SecO PriP PriO])
	Subsystem: Silicon Image, Inc. (formerly CMD Technology Inc) PCI0648
	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: 64 (500ns min, 1000ns max)
	Interrupt: pin A routed to IRQ 5
	Region 0: I/O ports at 9020 [size=8]
	Region 1: I/O ports at 9014 [size=4]
	Region 2: I/O ports at 9018 [size=8]
	Region 3: I/O ports at 9010 [size=4]
	Region 4: I/O ports at 9000 [size=16]
	Capabilities: [60] Power Management version 1
		Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=3 PME-

09:02.0 CardBus bridge: Texas Instruments PCI1420
	Subsystem: IBM: Unknown device 0148
	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: 168, Cache Line Size 20
	Interrupt: pin A routed to IRQ 7
	Region 0: Memory at b2000000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=09, secondary=0a, subordinate=0d, sec-latency=176
	Memory window 0: 61000000-613ff000 (prefetchable)
	Memory window 1: 61400000-617ff000
	I/O window 0: 00005000-000050ff
	I/O window 1: 00005400-000054ff
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt+ PostWrite+
	16-bit legacy interface ports at 0001

09:02.1 CardBus bridge: Texas Instruments PCI1420
	Subsystem: IBM: Unknown device 0148
	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: 168, Cache Line Size 20
	Interrupt: pin A routed to IRQ 7
	Region 0: Memory at b3000000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=09, secondary=0e, subordinate=11, sec-latency=176
	Memory window 0: 61800000-61bff000 (prefetchable)
	Memory window 1: 61c00000-61fff000
	I/O window 0: 00005800-000058ff
	I/O window 1: 00005c00-00005cff
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt- PostWrite+
	16-bit legacy interface ports at 0001

0e:00.0 Ethernet controller: 3Com Corporation 3cCFE575CT CardBus [Cyclone] (rev 10)
	Subsystem: 3Com Corporation FE575C-3Com 10/100 LAN CardBus-Fast Ethernet
	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: 64 (2500ns min, 1250ns max)
	Interrupt: pin A routed to IRQ 7
	Region 0: I/O ports at 5800 [size=128]
	Region 1: Memory at 61c00000 (32-bit, non-prefetchable) [size=128]
	Region 2: Memory at 61c00080 (32-bit, non-prefetchable) [size=128]
	Expansion ROM at 61800000 [disabled] [size=128K]
	Capabilities: [50] Power Management version 1
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=1 PME-


[-- Attachment #4: sys-firmware-docked --]
[-- Type: application/octet-stream, Size: 3612 bytes --]

/sys/firmware/
/sys/firmware/acpi
/sys/firmware/acpi/namespace
/sys/firmware/acpi/namespace/ACPI
/sys/firmware/acpi/namespace/ACPI/_TZ
/sys/firmware/acpi/namespace/ACPI/_TZ/THM0
/sys/firmware/acpi/namespace/ACPI/_SB
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/AC9M
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB7
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB7/URTH
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB7/URTH/UPDK
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB7/URTH/UPDK/eject
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB2
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB1
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB0/URTH
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB0/URTH/UPDK
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/USB0/URTH/UPDK/eject
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/SCND
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/SCND/MSTR
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/SCND/MSTR/eject
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/PRIM
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/IDE0/PRIM/MSTR
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCI1
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCI1/DOCK
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCI1/DOCK/CBS3
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCI1/DOCK/CBS2
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCI1/DOCK/IDE1
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCI1/DOCK/IDE1/PRIM
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCI1/DOCK/IDE1/PRIM/MSTR
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCI1/DOCK/eject
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCI1/CBS1
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/PCI1/CBS0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/AGP
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/AGP/VID
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/AGP/VID/DVI0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/AGP/VID/TV0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/AGP/VID/CRT0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/AGP/VID/LCD0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/HKEY
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/AC
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/BAT0
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/EC/PUBS
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/FIR
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/LPT
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/UART
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/UART/eject
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/MOU
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/KBD
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/RTC
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/FPU
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/SPKR
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/DMAC
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/TIMR
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/PIC
/sys/firmware/acpi/namespace/ACPI/_SB/PCI0/LPC/SIO
/sys/firmware/acpi/namespace/ACPI/_SB/SLPB
/sys/firmware/acpi/namespace/ACPI/_SB/LID
/sys/firmware/acpi/namespace/ACPI/_SB/MEM
/sys/firmware/acpi/namespace/ACPI/_SB/LNKH
/sys/firmware/acpi/namespace/ACPI/_SB/LNKG
/sys/firmware/acpi/namespace/ACPI/_SB/LNKF
/sys/firmware/acpi/namespace/ACPI/_SB/LNKE
/sys/firmware/acpi/namespace/ACPI/_SB/LNKD
/sys/firmware/acpi/namespace/ACPI/_SB/LNKC
/sys/firmware/acpi/namespace/ACPI/_SB/LNKB
/sys/firmware/acpi/namespace/ACPI/_SB/LNKA
/sys/firmware/acpi/namespace/ACPI/CPU
/sys/firmware/acpi/namespace/ACPI/PWRF