Re: possible bug in pd6729
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.00] Initializing cgroup subsys cpu [0.00] 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). (da...@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 :00:11.0 [0.360143] PCI: Cannot allocate resource region 8 of bridge :00:11.0 [0.368023] PCI: Cannot allocate resource region 0 of device :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 0xfffe-0x 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...@0 for :01:0a.0 [0.583049] PCI: Bridge: :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 :00:11.0 to 64 That does not look good. [ 50.280553] PCI: No IRQ known for interrupt pin A of device :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 :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/ | signature.asc Description: Digital signature ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: possible bug in pd6729
- Original Message - From: Komuro komurojun-...@nifty.com (1) Does your pcmcia card work properly, if you remove the code below? (while loop) (2)Please post the full dmesg (with the docking station). Well, the pcmcia slots on the docking station don't work. But the ones on the laptop themselves work even when the unit is plugged into the docking station. 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. Here is the output from dmesg: [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.26-1-486 (Debian 2.6.26-13lenny2) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 Fri Mar 13 17:25:45 UTC 2009 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 000a (usable) [0.00] BIOS-e820: 000f0e9c - 0010 (reserved) [0.00] BIOS-e820: 0010 - 0380 (usable) [0.00] BIOS-e820: 0e9c - 0001 (reserved) [0.00] 56MB LOWMEM available. [0.00] Entering add_active_range(0, 0, 14336) 0 entries of 256 used [0.00] Zone PFN ranges: [0.00] DMA 0 - 4096 [0.00] Normal 4096 -14336 [0.00] Movable zone start PFN for each node [0.00] early_node_map[1] active PFN ranges [0.00] 0:0 -14336 [0.00] On node 0 totalpages: 14336 [0.00] DMA zone: 32 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 4064 pages, LIFO batch:0 [0.00] Normal zone: 80 pages used for memmap [0.00] Normal zone: 10160 pages, LIFO batch:1 [0.00] Movable zone: 0 pages used for memmap [0.00] DMI not present or invalid. [0.00] ACPI Error (tbxfroot-0218): A valid RSDP was not found [20080321] [0.00] Allocating PCI resources starting at 1000 (gap: 0380:fc7f0e9c) [0.00] PM: Registered nosave memory: 000a - 000f1000 [0.00] PM: Registered nosave memory: 000f1000 - 0010 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 14224 [0.00] Kernel command line: root=/dev/hda1 ro console=ttyS0,19200n8 [0.00] No local APIC present or hardware disabled [0.00] mapped APIC to b000 (01072000) [0.00] Initializing CPU#0 [0.00] PID hash table entries: 256 (order: 8, 1024 bytes) [0.00] Detected 150.857 MHz processor. [0.004000] Console: colour VGA+ 80x25 [0.004000] console [ttyS0] enabled [0.004000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [0.004000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [0.004000] Memory: 47212k/57344k available (1694k kernel code, 9724k reserved, 745k data, 320k init, 0k highmem) [0.004000] virtual kernel memory layout: [0.004000] fixmap : 0xfffb3000 - 0xf000 ( 304 kB) [0.004000] vmalloc : 0xc400 - 0xfffb1000 ( 959 MB) [0.004000] lowmem : 0xc000 - 0xc380 ( 56 MB) [0.004000] .init : 0xc0364000 - 0xc03b4000 ( 320 kB) [0.004000] .data : 0xc02a7b33 - 0xc0362000 ( 745 kB) [0.004000] .text : 0xc010 - 0xc02a7b33 (1694 kB) [0.004000] Checking if this processor honours the WP bit even in supervisor mode...Ok. [0.004000] CPA: page pool initialized 1 of 1 pages preallocated [0.085432] Calibrating delay using timer specific routine.. 302.58 BogoMIPS (lpj=605176) [0.096006] Security Framework initialized [0.16] SELinux: Disabled at boot. [0.104006] Capability LSM initialized [0.108006] Mount-cache hash table entries: 512 [0.113892] Initializing cgroup subsys ns [0.120007] Initializing cgroup subsys cpuacct [0.124007] Initializing cgroup subsys devices [0.128008] Intel Pentium with F0 0F bug - workaround enabled. [0.132008] [0.136008] CPU: Intel Pentium MMX stepping 04 [0.152009] Checking 'hlt' instruction... OK. [0.191655] Freeing SMP alternatives: 0k freed [0.196012] ACPI: Core revision 20080321 [0.200012] ACPI Exception (tbxface-0629): AE_NO_ACPI_TABLES, While loading namespace from ACPI tables [20080321] [0.212013] ACPI: Unable to load the System Description Tables [0.219562] net_namespace: 652 bytes [0.224014] Booting paravirtualized kernel on bare hardware [0.231336] NET: Registered protocol family 16 [0.237311] EISA bus registered [0.248376] PCI: PCI BIOS revision 2.10 entry at 0xf618e, last bus=1 [0.256016] PCI: Using configuration type 1 for base access [0.260016] Setting up standard PCI resources [
Re: possible bug in pd6729
- Original Message - rom: Wolfram Sang w.s...@pengutronix.de To: John G. Heim jh...@math.wisc.edu c: Komuro komurojun-...@nifty.com; linux-pcmcia@lists.infradead.org Sent: Friday, September 11, 2009 1:28 AM Subject: Re: possible bug in pd6729 :00:13.0. Please try using pci=3Dbiosirq. Did you try that? I don't know what it means. I tried googling it but all I got was a lot of other log dumps with the same message. I hate to make excuses but I am also blind and its difficult for me to scan long web pages with 100s of lines of log dumps. While I was trying to give you the diagnostic stuff you asked for, I found a workaround of sorts. I booted with a serial console,console=ttyS0, and the error messages no longer appear on the regular console. So now I can log in there and use the laptop as normal. The error messages still appear on the serial console but I could direct them to ttyS1 and then they'd go no where, I guess. I'm not sure what happens if you write to a serial port that doesn't really exist. ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: possible bug in pd6729
:00:13.0. Please try using pci=3Dbiosirq. Did you try that? I don't know what it means. I tried googling it but all I got was a lot of other log dumps with the same message. I hate to make excuses but I am also blind and its difficult for me to scan long web pages with 100s of lines of log dumps. Ah, okay. Well, it is just a kernel parameter. So you could try adding 'pci=biosirq' to the kernel command line and check if it works better now. While I was trying to give you the diagnostic stuff you asked for, I found a workaround of sorts. I booted with a serial Would you mind sending the 'lspci -vvv' output nevertheless? It might be useful for debugging similar cases. Regards, Wolfram -- Pengutronix e.K. | Wolfram Sang| Industrial Linux Solutions | http://www.pengutronix.de/ | signature.asc Description: Digital signature ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: Re: possible bug in pd6729
Hi,
[ 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.
The io_base of pd6729 in your docking station is 0,
so this is PCI setup problem.
Please try the following patch.
Best Regards
Komuro
--- a/drivers/pcmcia/pd6729.c.orig 2009-09-12 11:14:37.0 +0900
+++ b/drivers/pcmcia/pd6729.c2009-09-12 11:40:01.0 +0900
@@ -641,6 +641,12 @@
if ((ret = pci_enable_device(dev)))
goto err_out_free_mem;
+ if ((unsigned long long)pci_resource_start(dev, 0) == 0) {
+ printk(KERN_INFO pd6729: failed to load the driver.
+since the io_base is 0.\n);
+ goto err_out_free_mem;
+ }
+
printk(KERN_INFO pd6729: Cirrus PD6729 PCI to PCMCIA Bridge
at 0x%llx on irq %d\n,
(unsigned long long)pci_resource_start(dev, 0), dev-irq);
___
Linux PCMCIA reimplementation list
http://lists.infradead.org/mailman/listinfo/linux-pcmcia
