possible bug in pd6729

[Wolfram Sang]

Hi John,

On Thu, Sep 10, 2009 at 07:50:35PM -0500, John G. Heim wrote:

> The only real problem is that that error message keeps coming up on the  
> console. I can show you that too. I've done a text screen cap and I'll 
> paste that in below under the output from dmesg.

Well, there are more problems. Can you also attach the output from lspci -vvv?
BTW which laptop are we talking about? I seem to have missed that. Which BIOS
version do you use? Is this the latest one?

> Here is the output from dmesg:
>
> [    0.000000] Initializing cgroup subsys cpu
> [    0.000000] Linux version 2.6.26-1-486 (Debian 2.6.26-13lenny2)  

Any chance to try a newer kernel? 2.6.31 would be great, but Debian also has
2.6.30 images for lenny (in backports).

> (dannf at debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian  
> 4.1.2-25)) #1 Fri Mar 13 17:25:45 UTC 2009

Please take care that such logs are not line-wrapped. It makes them hard to
read.

> [    0.340810] PCI: Probing PCI hardware
> [    0.348021] PCI: Probing PCI hardware (bus 00)
> [    0.355624] PCI: Cannot allocate resource region 7 of bridge 0000:00:11.0
> [    0.360143] PCI: Cannot allocate resource region 8 of bridge 0000:00:11.0
> [    0.368023] PCI: Cannot allocate resource region 0 of device 0000:01:0a.0
> [    0.372023] system 00:04: iomem range 0x0-0x9ff could not be reserved
> [    0.376047] system 00:04: iomem range 0xe00-0xfff could not be reserved
> [    0.412205] system 00:05: ioport range 0x4d0-0x4d1 has been reserved
> [    0.450273] system 00:05: iomem range 0xfffe0000-0xffffffff could not 
> be reserved
> [    0.495111] system 00:05: iomem range 0xcc000-0xcc7ff has been reserved
> [    0.542842] PCI: Failed to allocate I/O resource #0:4 at 0 for 0000:01:0a.0
> [    0.583049] PCI: Bridge: 0000:00:11.0
> [    0.605027]   IO window: disabled.
> [    0.625433]   MEM window: disabled.
> [    0.646356]   PREFETCH window: disabled.
> [    0.669912] PCI: Setting latency timer of device 0000:00:11.0 to 64

That does not look good.

> [   50.280553] PCI: No IRQ known for interrupt pin A of device 
> 0000:00:13.0. Please try using pci=biosirq.

Did you try that?

> [   50.288828] pd6729: Cirrus PD6729 PCI to PCMCIA Bridge at 0xfcfc on irq 0
> [   50.293024] pd6729: ISA irqs = 3,5,7,9,10,11  polling status changes.
> [   50.676487] PCI: No IRQ known for interrupt pin A of device 
> 0000:01:0a.0. Please try using pci=biosirq.
> [   50.688869] pd6729: Cirrus PD6729 PCI to PCMCIA Bridge at 0x0 on irq 0
> [   50.693063] pd6729: ISA irqs = 3,5,7,9,10,11  polling status changes.

Ouch! There is really something wrong with the PCI-Setup.

Regards,

   Wolfram

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-pcmcia/attachments/20090911/3622dfcd/attachment.sig>