* 2.6.5 yenta_socket irq 10: nobody cared!
@ 2004-04-05 2:06 Kitt Tientanopajai
0 siblings, 0 replies; 13+ messages in thread
From: Kitt Tientanopajai @ 2004-04-05 2:06 UTC (permalink / raw)
To: linux-kernel
Hello,
I use 2.6.5 on Acer TravelMate 361 Evi. It has built-in orinoco card hardwired to a cardbus controller. lspci reports three cardbus controller on my notebook:
01:05.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 01)
Subsystem: Lucent Technologies: Unknown device ab01
Flags: medium devsel, IRQ 10
Memory at 10001000 (32-bit, non-prefetchable) [disabled] [size=4K]
Bus: primary=01, secondary=02, subordinate=05, sec-latency=176
I/O window 0: 00000000-00000003 [disabled]
I/O window 1: 00000000-00000003 [disabled]
16-bit legacy interface ports at 0001
01:09.0 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller (rev 02)
Subsystem: Acer Incorporated [ALI]: Unknown device 1022
Flags: stepping, slow devsel, IRQ 11
Memory at 10002000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=01, secondary=06, subordinate=09, sec-latency=176
I/O window 0: 00000000-00000003
I/O window 1: 00000000-00000003
16-bit legacy interface ports at 0001
01:09.1 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller (rev 02)
Subsystem: Acer Incorporated [ALI]: Unknown device 1022
Flags: stepping, slow devsel, IRQ 11
Memory at 10003000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=01, secondary=0a, subordinate=0d, sec-latency=176
I/O window 0: 00000000-00000003
I/O window 1: 00000000-00000003
16-bit legacy interface ports at 0001
When I start pcmcia service I got this messages:
Apr 5 06:23:24 peorth kernel: Linux Kernel Card Services
Apr 5 06:23:24 peorth kernel: options: [pci] [cardbus] [pm]
Apr 5 06:23:24 peorth kernel: PCI: Enabling device 0000:01:05.0 (0000 -> 0002)
Apr 5 06:23:24 peorth kernel: Yenta: CardBus bridge found at 0000:01:05.0 [12a3:ab01]
Apr 5 06:23:24 peorth kernel: Yenta: Enabling burst memory read transactions
Apr 5 06:23:24 peorth kernel: Yenta: Using CSCINT to route CSC interrupts to PCI
Apr 5 06:23:24 peorth kernel: Yenta: Routing CardBus interrupts to PCI
Apr 5 06:23:25 peorth kernel: Yenta: ISA IRQ mask 0x0000, PCI irq 10
Apr 5 06:23:25 peorth kernel: Socket status: 30000011
Apr 5 06:23:25 peorth kernel: Yenta: CardBus bridge found at 0000:01:09.0 [1025:1022]
Apr 5 06:23:27 peorth kernel: irq 10: nobody cared!
Apr 5 06:23:27 peorth kernel: Call Trace:
Apr 5 06:23:27 peorth kernel: [<c0108eca>] __report_bad_irq+0x2a/0x90
Apr 5 06:23:27 peorth kernel: [<c0108fc0>] note_interrupt+0x70/0xb0
Apr 5 06:23:27 peorth kernel: [<c0109270>] do_IRQ+0x120/0x130
Apr 5 06:23:27 peorth kernel: [<c0107618>] common_interrupt+0x18/0x20
Apr 5 06:23:27 peorth kernel: [<c01217ee>] do_softirq+0x3e/0xa0
Apr 5 06:23:27 peorth kernel: [<c010924a>] do_IRQ+0xfa/0x130
Apr 5 06:23:27 peorth kernel: [<c0107618>] common_interrupt+0x18/0x20
Apr 5 06:23:27 peorth kernel: [<c0113286>] delay_pmtmr+0x16/0x20
Apr 5 06:23:27 peorth kernel: [<c01cf512>] __delay+0x12/0x20
Apr 5 06:23:27 peorth kernel: [<d0da29fe>] yenta_probe_irq+0xfe/0x140 [yenta_socket]
Apr 5 06:23:27 peorth kernel: [<d0da2a7a>] yenta_get_socket_capabilities+0x3a/0x70 [yenta_socket]
Apr 5 06:23:27 peorth kernel: [<d0da2dc7>] yenta_probe+0x1a7/0x240 [yenta_socket]
Apr 5 06:23:27 peorth kernel: [<c01d3712>] pci_device_probe_static+0x52/0x70
Apr 5 06:23:27 peorth kernel: [<c01d376c>] __pci_device_probe+0x3c/0x50
Apr 5 06:23:27 peorth kernel: [<c01d37ac>] pci_device_probe+0x2c/0x50
Apr 5 06:23:27 peorth kernel: [<c0232b1f>] bus_match+0x3f/0x70
Apr 5 06:23:27 peorth kernel: [<c0232c4c>] driver_attach+0x5c/0xa0
Apr 5 06:23:27 peorth kernel: [<c0232f78>] bus_add_driver+0xa8/0xc0
Apr 5 06:23:27 peorth kernel: [<c02333cf>] driver_register+0x2f/0x40
Apr 5 06:23:27 peorth kernel: [<c01d399c>] pci_register_driver+0x5c/0x90
Apr 5 06:23:27 peorth kernel: [<d0d9400f>] yenta_socket_init+0xf/0x11 [yenta_socket]
Apr 5 06:23:27 peorth kernel: [<c0134722>] sys_init_module+0x142/0x280
Apr 5 06:23:27 peorth kernel: [<c0107459>] sysenter_past_esp+0x52/0x71
Apr 5 06:23:27 peorth kernel:
Apr 5 06:23:27 peorth kernel: handlers:
Apr 5 06:23:27 peorth kernel: [<d0d55890>] (snd_intel8x0_interrupt+0x0/0x240 [snd_intel8x0])
Apr 5 06:23:27 peorth kernel: [<d0d4da10>] (ohci_irq_handler+0x0/0x860 [ohci1394])
Apr 5 06:23:27 peorth kernel: [<d0da18a0>] (yenta_interrupt+0x0/0x40 [yenta_socket])
Apr 5 06:23:27 peorth kernel: Disabling IRQ #10
Apr 5 06:23:27 peorth kernel: Yenta: ISA IRQ mask 0x00b8, PCI irq 11
Apr 5 06:23:27 peorth kernel: Socket status: 30000006
Apr 5 06:23:27 peorth kernel: Yenta: CardBus bridge found at 0000:01:09.1 [1025:1022]
Apr 5 06:23:27 peorth kernel: Yenta: ISA IRQ mask 0x00b8, PCI irq 11
Apr 5 06:23:27 peorth kernel: Socket status: 30000410
Apr 5 06:23:30 peorth cardmgr[3347]: watching 3 sockets
Apr 5 06:23:30 peorth kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Apr 5 06:23:30 peorth kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x240-0x247 0x370-0x38f 0x4d0-0x4d7
Apr 5 06:23:30 peorth kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Apr 5 06:23:30 peorth kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
Apr 5 06:23:30 peorth cardmgr[3349]: socket 0: Lucent Technologies WaveLAN/IEEE Adapter
Apr 5 06:23:31 peorth cardmgr[3349]: unsupported card in socket 2
Apr 5 06:23:31 peorth cardmgr[3349]: product info: "O2Micro", "SmartCardBus Reader", "V1.0"
Apr 5 06:23:31 peorth cardmgr[3349]: manfid: 0xffff, 0x0001
I can use iwconfig to control the orinoco card located in socket 0 but it seems that the card cannot send any packet and ifconfig shows TX errors on the interface.
This also happened in 2.6.2, 2.6.3 and 2.6.4. Currently, I have to use 2.4 + pcmcia-cs to use pcmcia. (2.4 kernel-pcmcia cause system freeze if I modprobe yenta-socket).
How can I make my orinoco card works on 2.6 ?
TIA
kitt
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.6.5 yenta_socket irq 10: nobody cared!
@ 2004-04-06 0:27 Daniel Ritz
2004-04-06 2:35 ` Kitt Tientanopajai
0 siblings, 1 reply; 13+ messages in thread
From: Daniel Ritz @ 2004-04-06 0:27 UTC (permalink / raw)
To: Kitt Tientanopajai; +Cc: linux-kernel
this is a known problem with the acer travelmate 361. it reports IRQ 11 for
the O2Micro cardbus bridge when it is in reality IRQ 10.
see:
http://www.naos.co.nz/hardware/laptop/acer-361evi/x94.html#AEN138
and
http://sourceforge.net/tracker/index.php?func=detail&aid=533863&group_id=2405&atid=102405
please give a full dmesg and a lspci -vvvn.
are you using ACPI?
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.6.5 yenta_socket irq 10: nobody cared!
2004-04-06 0:27 2.6.5 yenta_socket irq 10: nobody cared! Daniel Ritz
@ 2004-04-06 2:35 ` Kitt Tientanopajai
2004-04-07 15:41 ` Daniel Ritz
0 siblings, 1 reply; 13+ messages in thread
From: Kitt Tientanopajai @ 2004-04-06 2:35 UTC (permalink / raw)
To: daniel.ritz; +Cc: linux-kernel
Hi,
> this is a known problem with the acer travelmate 361. it reports IRQ 11 for
> the O2Micro cardbus bridge when it is in reality IRQ 10.
>
> see:
> http://www.naos.co.nz/hardware/laptop/acer-361evi/x94.html#AEN138
> and
> http://sourceforge.net/tracker/index.php?func=detail&aid=533863&group_id=2405&atid=102405
Thanks for info. I'll try that.
> please give a full dmesg and a lspci -vvvn.
> are you using ACPI?
My boot param is "acpi=on pci=noacpi", below is output from dmesg and lspci.
kitt
--
$ dmesg
Linux version 2.6.5 (root@peorth.kitty.in.th) (gcc version 3.3.2 20031022 (Red Hat Linux 3.3.2-1)) #1 Mon Apr 5 06:06:17 ICT 2004
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000000f7e0000 (usable)
BIOS-e820: 000000000f7e0000 - 000000000f7e8000 (ACPI data)
BIOS-e820: 000000000f7e8000 - 000000000f800000 (ACPI NVS)
BIOS-e820: 000000000f800000 - 0000000010000000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
247MB LOWMEM available.
On node 0 totalpages: 63456
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 59360 pages, LIFO batch:14
HighMem zone: 0 pages, LIFO batch:1
DMI 2.3 present.
ACPI: RSDP (v000 Acer ) @ 0x000fe030
ACPI: RSDT (v001 Acer TM360 0x00000001 Acer 0x00000000) @ 0x0f7e0000
ACPI: FADT (v001 Acer TM360 0x00000001 Acer 0x00000000) @ 0x0f7e0054
ACPI: BOOT (v001 Acer TM360 0x00000001 Acer 0x00000000) @ 0x0f7e002c
ACPI: DSDT (v001 Acer AN360 0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: PM-Timer IO Port: 0xf108
Built 1 zonelists
Kernel command line: ro root=/dev/hda2 acpi=on pci=noacpi vga=791 rhgb
Initializing CPU#0
PID hash table entries: 1024 (order 10: 8192 bytes)
Detected 999.945 MHz processor.
Using pmtmr for high-res timesource
Console: colour dummy device 80x25
Memory: 247580k/253824k available (1931k kernel code, 5508k reserved, 752k data, 144k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 1982.46 BogoMIPS
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383f9ff 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel(R) Pentium(R) III Mobile CPU 1000MHz stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf0200, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040326
ACPI: IRQ9 SCI: Edge set to Level Trigger.
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: PCI Interrupt Link [PILA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PILB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [PILC] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PILD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PILE] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [PILF] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [PILG] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PILH] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: Embedded Controller [EC0] (gpe 29)
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Using IRQ router PIIX/ICH [8086/248c] at 0000:00:1f.0
PCI: IRQ 0 for device 0000:00:1f.1 doesn't match PIRQ mask - try pci=usepirqmaskPCI: Found IRQ 11 for device 0000:00:1f.1
PCI: Sharing IRQ 11 with 0000:00:02.0
PCI: Sharing IRQ 11 with 0000:00:1d.0
vesafb: framebuffer at 0x98000000, mapped to 0xd000e000, size 8000k
vesafb: mode is 1024x768x16, linelength=2048, pages=4
vesafb: protected mode interface info at 00ff:44f0
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
fb0: VESA VGA frame buffer device
Simple Boot Flag at 0x6e set to 0x1
Machine check exception polling timer started.
IA-32 Microcode Update Driver: v1.13 <tigran@veritas.com>
udf: registering filesystem
ACPI: AC Adapter [AC] (on-line)
ACPI: Battery Slot [BAT0] (battery present)
ACPI: Power Button (FF) [PWRF]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Lid Switch [LID]
ACPI: Processor [CPU0] (supports C1 C2 C3)
ACPI: Thermal Zone [THR1] (39 C)
ACPI: Thermal Zone [THR2] (33 C)
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Console: switching to colour frame buffer device 128x48
lp: driver loaded but no devices found
Real Time Clock Driver v1.12
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel 830M Chipset.
agpgart: Maximum main memory to use for agp memory: 196M
agpgart: Detected 8060K stolen memory.
agpgart: AGP aperture is 128M @ 0x98000000
mtrr: 0x98000000,0x8000000 overlaps existing 0x98000000,0x400000
[drm] Initialized i830 1.3.2 20021108 on minor 0
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
PCI: Found IRQ 10 for device 0000:00:1f.6
PCI: Sharing IRQ 10 with 0000:00:1f.3
PCI: Sharing IRQ 10 with 0000:00:1f.5
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH3M: IDE controller at PCI slot 0000:00:1f.1
PCI: Found IRQ 11 for device 0000:00:1f.1
PCI: Sharing IRQ 11 with 0000:00:02.0
PCI: Sharing IRQ 11 with 0000:00:1d.0
ICH3M: chipset revision 1
ICH3M: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xa890-0xa897, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xa898-0xa89f, BIOS settings: hdc:DMA, hdd:pio
hda: TOSHIBA MK4025GAS, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: DV-28E-B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 78140160 sectors (40007 MB), CHS=65535/16/63, UDMA(100)
hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
hdc: ATAPI 24X DVD-ROM drive, 256kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
mice: PS/2 mouse device common for all mice
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
Synaptics Touchpad, model: 1
Firmware: 4.6
180 degree mounted touchpad
Sensor: 18
new absolute packet format
Touchpad has extended capability bits
-> four buttons
-> multifinger detection
-> palm detection
input: SynPS/2 Synaptics TouchPad on isa0060/serio4
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
arp_tables: (C) 2002 David S. Miller
NET: Registered protocol family 1
NET: Registered protocol family 17
ACPI: (supports S0 S1 S3 S4 S4bios S5)
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 144k freed
mtrr: base(0x98000000) is not aligned on a size(0x180000) boundary
PCI: Found IRQ 11 for device 0000:00:02.0
PCI: Sharing IRQ 11 with 0000:00:1d.0
PCI: Sharing IRQ 11 with 0000:00:1f.1
mtrr: 0x98000000,0x8000000 overlaps existing 0x98000000,0x400000
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
USB Universal Host Controller Interface driver v2.2
PCI: Found IRQ 11 for device 0000:00:1d.0
PCI: Sharing IRQ 11 with 0000:00:02.0
PCI: Sharing IRQ 11 with 0000:00:1f.1
uhci_hcd 0000:00:1d.0: Intel Corp. 82801CA/CAM USB (Hub #1)
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: irq 11, io base 0000a4a0
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PCI: Found IRQ 11 for device 0000:00:1d.1
PCI: Sharing IRQ 11 with 0000:01:09.0
PCI: Sharing IRQ 11 with 0000:01:09.1
uhci_hcd 0000:00:1d.1: Intel Corp. 82801CA/CAM USB (Hub #2)
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: irq 11, io base 0000a4e0
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
PCI: Found IRQ 11 for device 0000:00:1d.2
uhci_hcd 0000:00:1d.2: Intel Corp. 82801CA/CAM USB (Hub #3)
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: irq 11, io base 0000a800
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
usb 1-1: new low speed USB device using address 2
input: USB HID v1.10 Mouse [A4Tech USB Optical Mouse] on usb-0000:00:1d.0-1
EXT3 FS on hda2, internal journal
Adding 506036k swap on /dev/hda3. Priority:-1 extents:1
PCI: Found IRQ 10 for device 0000:00:1f.5
PCI: Sharing IRQ 10 with 0000:00:1f.3
PCI: Sharing IRQ 10 with 0000:00:1f.6
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 50448 usecs
intel8x0: clocking to 48000
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ohci1394: $Rev: 1172 $ Ben Collins <bcollins@debian.org>
PCI: Found IRQ 10 for device 0000:01:03.0
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[10] MMIO=[80100000-801007ff] Max Packet=[2048]
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0120900300000000]
microcode: error! Bad data in microcode data file
microcode: Error in the microcode data
e100: Intel(R) PRO/100 Network Driver, 3.0.17
e100: Copyright(c) 1999-2004 Intel Corporation
PCI: Found IRQ 10 for device 0000:01:08.0
PCI: Sharing IRQ 10 with 0000:01:05.0
e100: eth0: e100_probe: addr 0x80101000, irq 10, MAC addr 00:00:E2:61:54:AE
mtrr: base(0x98000000) is not aligned on a size(0x180000) boundary
PCI: Found IRQ 11 for device 0000:00:02.0
PCI: Sharing IRQ 11 with 0000:00:1d.0
PCI: Sharing IRQ 11 with 0000:00:1f.1
mtrr: 0x98000000,0x8000000 overlaps existing 0x98000000,0x400000
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
cdrom: This disc doesn't have any tracks I recognize!
Synaptics driver lost sync at byte 4
Synaptics driver resynced.
Synaptics driver lost sync at byte 1
Synaptics driver lost sync at byte 1
Synaptics driver lost sync at byte 1
Synaptics driver resynced.
ip_tables: (C) 2000-2002 Netfilter core team
e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
PCI: Found IRQ 10 for device 0000:00:1f.6
PCI: Sharing IRQ 10 with 0000:00:1f.3
PCI: Sharing IRQ 10 with 0000:00:1f.5
PCI: Setting latency timer of device 0000:00:1f.6 to 64
spurious 8259A interrupt: IRQ7.
cdrom: This disc doesn't have any tracks I recognize!
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
PCI: Enabling device 0000:01:05.0 (0000 -> 0002)
PCI: Found IRQ 10 for device 0000:01:05.0
PCI: Sharing IRQ 10 with 0000:01:08.0
Yenta: CardBus bridge found at 0000:01:05.0 [12a3:ab01]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta: ISA IRQ mask 0x0000, PCI irq 10
Socket status: 30000011
PCI: Found IRQ 11 for device 0000:01:09.0
PCI: Sharing IRQ 11 with 0000:00:1d.1
PCI: Sharing IRQ 11 with 0000:01:09.1
Yenta: CardBus bridge found at 0000:01:09.0 [1025:1022]
irq 10: nobody cared!
Call Trace:
[<c0108eca>] __report_bad_irq+0x2a/0x90
[<c0108fc0>] note_interrupt+0x70/0xb0
[<c0109270>] do_IRQ+0x120/0x130
[<c0107618>] common_interrupt+0x18/0x20
[<c01217ee>] do_softirq+0x3e/0xa0
[<c010924a>] do_IRQ+0xfa/0x130
[<c0107618>] common_interrupt+0x18/0x20
[<c0113284>] delay_pmtmr+0x14/0x20
[<c01cf512>] __delay+0x12/0x20
[<d0de29fe>] yenta_probe_irq+0xfe/0x140 [yenta_socket]
[<d0de2a7a>] yenta_get_socket_capabilities+0x3a/0x70 [yenta_socket]
[<d0de2dc7>] yenta_probe+0x1a7/0x240 [yenta_socket]
[<c01d3712>] pci_device_probe_static+0x52/0x70
[<c01d376c>] __pci_device_probe+0x3c/0x50
[<c01d37ac>] pci_device_probe+0x2c/0x50
[<c0232b1f>] bus_match+0x3f/0x70
[<c0232c4c>] driver_attach+0x5c/0xa0
[<c0232f78>] bus_add_driver+0xa8/0xc0
[<c02333cf>] driver_register+0x2f/0x40
[<c01d399c>] pci_register_driver+0x5c/0x90
[<d0d9400f>] yenta_socket_init+0xf/0x11 [yenta_socket]
[<c0134722>] sys_init_module+0x142/0x280
[<c0107459>] sysenter_past_esp+0x52/0x71
handlers:
[<d0d55890>] (snd_intel8x0_interrupt+0x0/0x240 [snd_intel8x0])
[<d0d4da10>] (ohci_irq_handler+0x0/0x860 [ohci1394])
[<d0d3e1d0>] (e100_intr+0x0/0x5a0 [e100])
[<d0da15c0>] (snd_intel8x0_interrupt+0x0/0x230 [snd_intel8x0m])
[<d0de18a0>] (yenta_interrupt+0x0/0x40 [yenta_socket])
Disabling IRQ #10
Yenta: ISA IRQ mask 0x00b8, PCI irq 11
Socket status: 30000006
PCI: Found IRQ 11 for device 0000:01:09.1
PCI: Sharing IRQ 11 with 0000:00:1d.1
PCI: Sharing IRQ 11 with 0000:01:09.0
Yenta: CardBus bridge found at 0000:01:09.1 [1025:1022]
Yenta: ISA IRQ mask 0x00b8, PCI irq 11
Socket status: 30000410
$ lspci -vvvn
00:00.0 Class 0600: 8086:3575 (rev 03)
Subsystem: 1025:1022
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 <unassigned> (32-bit, prefetchable)
Capabilities: <available only to root>
00:02.0 Class 0300: 8086:3577 (rev 03)
Subsystem: 1025:1022
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 11
Region 0: Memory at 98000000 (32-bit, prefetchable) [size=128M]
Region 1: Memory at 90100000 (32-bit, non-prefetchable) [size=512K]
Capabilities: <available only to root>
00:02.1 Class 0380: 8086:3577
Subsystem: 1025:1022
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-
Region 0: Memory at 88000000 (32-bit, prefetchable) [size=128M]
Region 1: Memory at 80200000 (32-bit, non-prefetchable) [size=512K]
Capabilities: <available only to root>
00:1d.0 Class 0c03: 8086:2482 (rev 01)
Subsystem: 1025:1022
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 11
Region 4: I/O ports at a4a0 [size=32]
00:1d.1 Class 0c03: 8086:2484 (rev 01)
Subsystem: 1025:1022
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 11
Region 4: I/O ports at a4e0 [size=32]
00:1d.2 Class 0c03: 8086:2487 (rev 01)
Subsystem: 1025:1022
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 11
Region 4: I/O ports at a800 [size=32]
00:1e.0 Class 0604: 8086:2448 (rev 41)
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=01, subordinate=01, sec-latency=0
I/O behind bridge: 00007000-00007fff
Memory behind bridge: 80100000-801fffff
Prefetchable memory behind bridge: fff00000-000fffff
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
00:1f.0 Class 0601: 8086:248c (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 Class 0101: 8086:248a (rev 01) (prog-if 8a [Master SecP PriP])
Subsystem: 1025:1022
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 11
Region 0: I/O ports at <ignored>
Region 1: I/O ports at <ignored>
Region 2: I/O ports at <ignored>
Region 3: I/O ports at <ignored>
Region 4: I/O ports at a890 [size=16]
Region 5: Memory at 10000000 (32-bit, non-prefetchable) [size=1K]
00:1f.3 Class 0c05: 8086:2483 (rev 01)
Subsystem: 1025:1022
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 8000 [size=32]
00:1f.5 Class 0401: 8086:2485 (rev 01)
Subsystem: 1025:1022
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 10
Region 0: I/O ports at 9800 [size=256]
Region 1: I/O ports at 9c00 [size=64]
00:1f.6 Class 0703: 8086:2486 (rev 01)
Subsystem: 1025:1022
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 10
Region 0: I/O ports at a000 [size=256]
Region 1: I/O ports at a400 [size=128]
01:03.0 Class 0c00: 104c:8026 (prog-if 10)
Subsystem: 1025:1022
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: 32 (500ns min, 1000ns max), cache line size 08
Interrupt: pin A routed to IRQ 10
Region 0: Memory at 80100000 (32-bit, non-prefetchable) [size=2K]
Region 1: Memory at 80104000 (32-bit, non-prefetchable) [size=16K]
Capabilities: <available only to root>
01:05.0 Class 0607: 104c:ac50 (rev 01)
Subsystem: 12a3:ab01
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 08
Interrupt: pin A routed to IRQ 10
Region 0: Memory at 10001000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=01, secondary=02, subordinate=05, sec-latency=176
Memory window 0: 10400000-107ff000 (prefetchable)
Memory window 1: 10800000-10bff000
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
01:08.0 Class 0200: 8086:1031 (rev 41)
Subsystem: 1025:1022
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, 14000ns max), cache line size 08
Interrupt: pin A routed to IRQ 10
Region 0: Memory at 80101000 (32-bit, non-prefetchable) [size=4K]
Region 1: I/O ports at 7000 [size=64]
Capabilities: <available only to root>
01:09.0 Class 0607: 1217:6933 (rev 02)
Subsystem: 1025:1022
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 168
Interrupt: pin A routed to IRQ 11
Region 0: Memory at 10002000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=01, secondary=06, subordinate=09, sec-latency=176
Memory window 0: 10c00000-10fff000 (prefetchable)
Memory window 1: 11000000-113ff000
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
01:09.1 Class 0607: 1217:6933 (rev 02)
Subsystem: 1025:1022
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 168
Interrupt: pin A routed to IRQ 11
Region 0: Memory at 10003000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=01, secondary=0a, subordinate=0d, sec-latency=176
Memory window 0: 11400000-117ff000 (prefetchable)
Memory window 1: 11800000-11bff000
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
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.6.5 yenta_socket irq 10: nobody cared!
2004-04-06 2:35 ` Kitt Tientanopajai
@ 2004-04-07 15:41 ` Daniel Ritz
2004-04-07 19:24 ` Kitt Tientanopajai
0 siblings, 1 reply; 13+ messages in thread
From: Daniel Ritz @ 2004-04-07 15:41 UTC (permalink / raw)
To: Kitt Tientanopajai; +Cc: linux-kernel
On Tuesday 06 April 2004 04:35, Kitt Tientanopajai wrote:
> Hi,
>
> > this is a known problem with the acer travelmate 361. it reports IRQ 11 for
> > the O2Micro cardbus bridge when it is in reality IRQ 10.
> >
> > see:
> > http://www.naos.co.nz/hardware/laptop/acer-361evi/x94.html#AEN138
> > and
> > http://sourceforge.net/tracker/index.php?func=detail&aid=533863&group_id=2405&atid=102405
>
> Thanks for info. I'll try that.
>
> > please give a full dmesg and a lspci -vvvn.
> > are you using ACPI?
>
> My boot param is "acpi=on pci=noacpi", below is output from dmesg and lspci.
>
>
> kitt
>
> --
>
> $ dmesg
looks like you need a little workaround in the interuput routing code...please
apply the attached patch, send dmesg output plus output of dmidecode
( http://www.nongnu.org/demidecode/ ).
on the other side it could be that the o2micro bridge is wrongly programmed.
what looks a bit weired is that both functions of the o2micro show Pin A
routed to IRQ 11. this could be wrong. i'm reading the spec now.
do you happen to have the redmond OS on this machine? it would be nice to see
which interrupt windoze assignes to the o2micro bridge.
and one more question: any change in the interrupt assignment if you use full ACPI?
--- 1.36/arch/i386/pci/irq.c Fri Feb 27 06:48:13 2004
+++ edited/arch/i386/pci/irq.c Wed Apr 7 13:57:44 2004
@@ -542,8 +542,6 @@
r->name = "SIS";
r->get = pirq_sis_get;
r->set = pirq_sis_set;
- DBG("PCI: Detecting SiS router at %02x:%02x\n",
- rt->rtr_bus, rt->rtr_devfn);
return 1;
}
--- 1.17/arch/i386/pci/pci.h Mon Mar 1 07:20:00 2004
+++ edited/arch/i386/pci/pci.h Wed Apr 7 13:56:51 2004
@@ -4,7 +4,7 @@
* (c) 1999 Martin Mares <mj@ucw.cz>
*/
-#undef DEBUG
+#define DEBUG
#ifdef DEBUG
#define DBG(x...) printk(x)
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.6.5 yenta_socket irq 10: nobody cared!
2004-04-07 15:41 ` Daniel Ritz
@ 2004-04-07 19:24 ` Kitt Tientanopajai
2004-04-07 20:25 ` Daniel Ritz
0 siblings, 1 reply; 13+ messages in thread
From: Kitt Tientanopajai @ 2004-04-07 19:24 UTC (permalink / raw)
To: daniel.ritz; +Cc: linux-kernel
Hi
> looks like you need a little workaround in the interuput routing code...please
> apply the attached patch, send dmesg output plus output of dmidecode
> ( http://www.nongnu.org/demidecode/ ).
Guess so, I've tried on 2.6.5 with acpi=off, pci=biosirq, and excluded irq 11 in /etc/pcmcia/config.opts. They still routed to irq 11.
Anyway, my orinoco card (hardwired on TI cardbus controller) works with 2.4.xx + pcmcia-cs package using i82365 and do_scan=0. But the system freezed when I inserted a PCMCIA card into one of those controlled by o2micro. Below is dmesg when I start pcmcia service on 2.4.22-6_1.2174.nptl:
Linux PCMCIA Card Services 3.2.7
kernel build: 2.4.22-6_1.2174.nptl_01tlecustom #7 Mon Apr 5 05:31:52 ICT 2004
options: [pci] [cardbus] [apm]
Intel ISA/PCI/CardBus PCIC probe:
PCI: Found IRQ 10 for device 01:05.0
PCI: Sharing IRQ 10 with 01:08.0
TI 1410 rev 01 PCI-to-CardBus at slot 01:05, mem 0x10001000
host opts [0]: [pci only] [pci irq 10] [lat 32/176] [bus 2/5]
PCI card interrupts, PCI status changes
PCI: Found IRQ 11 for device 01:09.0
PCI: Sharing IRQ 11 with 00:1d.1
PCI: Sharing IRQ 11 with 01:09.1
PCI: Found IRQ 11 for device 01:09.1
PCI: Sharing IRQ 11 with 00:1d.1
PCI: Sharing IRQ 11 with 01:09.0
O2Micro OZ6933 rev 02 PCI-to-CardBus at slot 01:09, mem 0x10002000
host opts [0]: [pci/way] [pci irq 11] [lat 32/176] [bus 6/9]
host opts [1]: [pci/way] [pci irq 11] [lat 32/176] [bus 10/13]
ISA irqs (default) = 3,4,5,7 PCI status changes
cs: memory probe 0xa0000000-0xa0ffffff: clean.
orinoco.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
orinoco_cs.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
cs: IO port probe 0x0100-0x037f: excluding 0x240-0x247 0x378-0x37f
cs: IO port probe 0x0400-0x04ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: IO port probe 0x0c00-0x0cff: clean.
eth1: Station identity 001f:0001:0006:0010
eth1: Looks like a Lucent/Agere firmware version 6.16
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:02:2D:46:11:44
eth1: Station name "HERMES I"
eth1: ready
eth1: index 0x01: Vcc 3.3, irq 10, io 0x0100-0x
> on the other side it could be that the o2micro bridge is wrongly programmed.
> what looks a bit weired is that both functions of the o2micro show Pin A
> routed to IRQ 11. this could be wrong. i'm reading the spec now.
>
> do you happen to have the redmond OS on this machine? it would be nice to see
> which interrupt windoze assignes to the o2micro bridge.
Ah, I'm about to tell you this :) Win XP used irq 9 for all cardbus bridges.
> and one more question: any change in the interrupt assignment if you use full ACPI?
The bridges still used irq 11 when I passed just "acpi=on".
I have a few questions here: do I need APIC and IO-APIC in the kernel ? I used to enable them but /proc/interrupts showed only XT-PIC so I disabled them. And, should I try to upgrade the BIOS ?
Below is dmesg / dmidecode after patched.
# dmesg
h table entries: 1024 (order 10: 8192 bytes)
Detected 999.945 MHz processor.
Using pmtmr for high-res timesource
Console: colour dummy device 80x25
Memory: 247580k/253824k available (1931k kernel code, 5508k reserved, 755k data, 144k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 1982.46 BogoMIPS
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: After generic identify, caps: 0383f9ff 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383f9ff 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps: 0383f9ff 00000000 00000000 00000040
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: Intel(R) Pentium(R) III Mobile CPU 1000MHz stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
NET: Registered protocol family 16
PCI: BIOS32 Service Directory structure at 0xc00f0280
PCI: BIOS32 Service Directory entry at 0xf0210
PCI: BIOS probe returned s=00 hw=01 ver=02.10 l=01
PCI: PCI BIOS revision 2.10 entry at 0xf0200, last bus=1
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040326
ACPI: IRQ9 SCI: Edge set to Level Trigger.
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
PCI: IDE base address fixup for 0000:00:1f.1
PCI: IDE base address trash cleared for 0000:00:1f.1
PCI: Scanning for ghost devices on bus 0
PCI: Scanning for ghost devices on bus 1
Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
ACPI: PCI Interrupt Link [PILA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PILB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [PILC] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PILD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [PILE] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [PILF] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
ACPI: PCI Interrupt Link [PILG] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [PILH] (IRQs 3 4 5 6 7 9 10 11 12 14 15)
ACPI: Embedded Controller [EC0] (gpe 29)
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Peer bridge fixup
PCI: IRQ init
PCI: Interrupt Routing Table found at 0xc00fb700
00:02 slot=00 0:60/0800 1:00/0000 2:00/0000 3:00/0000
00:1f slot=00 0:60/1ef8 1:61/1ef8 2:62/1ef8 3:63/1ef8
00:1d slot=00 0:60/0800 1:63/0800 2:62/0800 3:00/0000
01:09 slot=00 0:63/0800 1:63/0800 2:00/0000 3:00/0000
01:08 slot=00 0:68/0400 1:00/0000 2:00/0000 3:00/0000
01:03 slot=00 0:69/0400 1:00/0000 2:00/0000 3:00/0000
01:05 slot=00 0:68/0400 1:00/0000 2:00/0000 3:00/0000
PCI: Attempting to find IRQ router for 8086:248c
PCI: Using IRQ router PIIX/ICH [8086/248c] at 0000:00:1f.0
PCI: IRQ fixup
0000:00:1f.1: ignoring bogus IRQ 255
IRQ for 0000:00:1f.1:0 -> PIRQ 60, mask 1ef8, excl 0000<4>PCI: IRQ 0 for device 0000:00:1f.1 doesn't match PIRQ mask - try pci=usepirqmask
-> newirq=0 -> got IRQ 11
PCI: Found IRQ 11 for device 0000:00:1f.1
PCI: Sharing IRQ 11 with 0000:00:02.0
PCI: Sharing IRQ 11 with 0000:00:1d.0
PCI: Allocating resources
PCI: Resource 98000000-9fffffff (f=1208, d=0, p=0)
PCI: Resource 90100000-9017ffff (f=200, d=0, p=0)
PCI: Resource 88000000-8fffffff (f=1208, d=0, p=0)
PCI: Resource 80200000-8027ffff (f=200, d=0, p=0)
PCI: Resource 0000a4a0-0000a4bf (f=101, d=0, p=0)
PCI: Resource 0000a4e0-0000a4ff (f=101, d=0, p=0)
PCI: Resource 0000a800-0000a81f (f=101, d=0, p=0)
PCI: Resource 0000a890-0000a89f (f=101, d=0, p=0)
PCI: Resource 00008000-0000801f (f=101, d=0, p=0)
PCI: Resource 00009800-000098ff (f=101, d=0, p=0)
PCI: Resource 00009c00-00009c3f (f=101, d=0, p=0)
PCI: Resource 0000a000-0000a0ff (f=101, d=0, p=0)
PCI: Resource 0000a400-0000a47f (f=101, d=0, p=0)
PCI: Resource 80100000-801007ff (f=200, d=0, p=0)
PCI: Resource 80104000-80107fff (f=200, d=0, p=0)
PCI: Resource 80101000-80101fff (f=200, d=0, p=0)
PCI: Resource 00007000-0000703f (f=101, d=0, p=0)
PCI: Sorting device list...
vesafb: framebuffer at 0x98000000, mapped to 0xd000e000, size 8000k
vesafb: mode is 1024x768x16, linelength=2048, pages=4
vesafb: protected mode interface info at 00ff:44f0
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
fb0: VESA VGA frame buffer device
Simple Boot Flag at 0x6e set to 0x1
Machine check exception polling timer started.
IA-32 Microcode Update Driver: v1.13 <tigran@veritas.com>
udf: registering filesystem
ACPI: AC Adapter [AC] (on-line)
ACPI: Battery Slot [BAT0] (battery present)
ACPI: Power Button (FF) [PWRF]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Lid Switch [LID]
ACPI: Processor [CPU0] (supports C1 C2 C3)
ACPI: Thermal Zone [THR1] (57 C)
ACPI: Thermal Zone [THR2] (51 C)
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Console: switching to colour frame buffer device 128x48
lp: driver loaded but no devices found
Real Time Clock Driver v1.12
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel 830M Chipset.
agpgart: Maximum main memory to use for agp memory: 196M
agpgart: Detected 8060K stolen memory.
agpgart: AGP aperture is 128M @ 0x98000000
mtrr: 0x98000000,0x8000000 overlaps existing 0x98000000,0x400000
[drm] Initialized i830 1.3.2 20021108 on minor 0
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
IRQ for 0000:00:1f.6:1 -> PIRQ 61, mask 1ef8, excl 0000 -> newirq=10 -> got IRQ 10
PCI: Found IRQ 10 for device 0000:00:1f.6
PCI: Sharing IRQ 10 with 0000:00:1f.3
PCI: Sharing IRQ 10 with 0000:00:1f.5
Using anticipatory io scheduler
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH3M: IDE controller at PCI slot 0000:00:1f.1
IRQ for 0000:00:1f.1:0 -> PIRQ 60, mask 1ef8, excl 0000 -> newirq=11 -> got IRQ 11
PCI: Found IRQ 11 for device 0000:00:1f.1
PCI: Sharing IRQ 11 with 0000:00:02.0
PCI: Sharing IRQ 11 with 0000:00:1d.0
ICH3M: chipset revision 1
ICH3M: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xa890-0xa897, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xa898-0xa89f, BIOS settings: hdc:DMA, hdd:pio
hda: TOSHIBA MK4025GAS, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: DV-28E-B, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 78140160 sectors (40007 MB), CHS=65535/16/63, UDMA(100)
hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
hdc: ATAPI 24X DVD-ROM drive, 256kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
mice: PS/2 mouse device common for all mice
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
Synaptics Touchpad, model: 1
Firmware: 4.6
180 degree mounted touchpad
Sensor: 18
new absolute packet format
Touchpad has extended capability bits
-> four buttons
-> multifinger detection
-> palm detection
input: SynPS/2 Synaptics TouchPad on isa0060/serio4
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 32768)
arp_tables: (C) 2002 David S. Miller
NET: Registered protocol family 1
NET: Registered protocol family 17
ACPI: (supports S0 S1 S3 S4 S4bios S5)
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 144k freed
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
USB Universal Host Controller Interface driver v2.2
IRQ for 0000:00:1d.0:0 -> PIRQ 60, mask 0800, excl 0000 -> newirq=11 -> got IRQ 11
PCI: Found IRQ 11 for device 0000:00:1d.0
PCI: Sharing IRQ 11 with 0000:00:02.0
PCI: Sharing IRQ 11 with 0000:00:1f.1
uhci_hcd 0000:00:1d.0: Intel Corp. 82801CA/CAM USB (Hub #1)
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: irq 11, io base 0000a4a0
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
IRQ for 0000:00:1d.1:1 -> PIRQ 63, mask 0800, excl 0000 -> newirq=11 -> got IRQ 11
PCI: Found IRQ 11 for device 0000:00:1d.1
PCI: Sharing IRQ 11 with 0000:01:09.0
PCI: Sharing IRQ 11 with 0000:01:09.1
uhci_hcd 0000:00:1d.1: Intel Corp. 82801CA/CAM USB (Hub #2)
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: irq 11, io base 0000a4e0
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
IRQ for 0000:00:1d.2:2 -> PIRQ 62, mask 0800, excl 0000 -> newirq=11 -> got IRQ 11
PCI: Found IRQ 11 for device 0000:00:1d.2
uhci_hcd 0000:00:1d.2: Intel Corp. 82801CA/CAM USB (Hub #3)
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: irq 11, io base 0000a800
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
usb 1-1: new low speed USB device using address 2
input: USB HID v1.10 Mouse [A4Tech USB Optical Mouse] on usb-0000:00:1d.0-1
EXT3 FS on hda2, internal journal
Adding 506036k swap on /dev/hda3. Priority:-1 extents:1
IRQ for 0000:00:1f.5:1 -> PIRQ 61, mask 1ef8, excl 0000 -> newirq=10 -> got IRQ 10
PCI: Found IRQ 10 for device 0000:00:1f.5
PCI: Sharing IRQ 10 with 0000:00:1f.3
PCI: Sharing IRQ 10 with 0000:00:1f.6
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 49566 usecs
intel8x0: clocking to 48000
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda7, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ohci1394: $Rev: 1172 $ Ben Collins <bcollins@debian.org>
IRQ for 0000:01:03.0:0 -> PIRQ 69, mask 0400, excl 0000 -> newirq=10 -> got IRQ 10
PCI: Found IRQ 10 for device 0000:01:03.0
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[10] MMIO=[80100000-801007ff] Max Packet=[2048]
ieee1394: Host added: ID:BUS[0-00:1023] GUID[0120900300000000]
microcode: error! Bad data in microcode data file
microcode: Error in the microcode data
e100: Intel(R) PRO/100 Network Driver, 3.0.17
e100: Copyright(c) 1999-2004 Intel Corporation
IRQ for 0000:01:08.0:0 -> PIRQ 68, mask 0400, excl 0000 -> newirq=10 -> got IRQ 10
PCI: Found IRQ 10 for device 0000:01:08.0
PCI: Sharing IRQ 10 with 0000:01:05.0
e100: eth0: e100_probe: addr 0x80101000, irq 10, MAC addr 00:00:E2:61:54:AE
mtrr: base(0x98000000) is not aligned on a size(0x180000) boundary
IRQ for 0000:00:02.0:0 -> PIRQ 60, mask 0800, excl 0000 -> newirq=11 -> got IRQ 11
PCI: Found IRQ 11 for device 0000:00:02.0
PCI: Sharing IRQ 11 with 0000:00:1d.0
PCI: Sharing IRQ 11 with 0000:00:1f.1
mtrr: 0x98000000,0x8000000 overlaps existing 0x98000000,0x400000
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
cdrom: This disc doesn't have any tracks I recognize!
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
PCI: Enabling device 0000:01:05.0 (0000 -> 0002)
IRQ for 0000:01:05.0:0 -> PIRQ 68, mask 0400, excl 0000 -> newirq=10 -> got IRQ 10
PCI: Found IRQ 10 for device 0000:01:05.0
PCI: Sharing IRQ 10 with 0000:01:08.0
Yenta: CardBus bridge found at 0000:01:05.0 [12a3:ab01]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta: ISA IRQ mask 0x0000, PCI irq 10
Socket status: 30000011
IRQ for 0000:01:09.0:0 -> PIRQ 63, mask 0800, excl 0000 -> newirq=11 -> got IRQ 11
PCI: Found IRQ 11 for device 0000:01:09.0
PCI: Sharing IRQ 11 with 0000:00:1d.1
PCI: Sharing IRQ 11 with 0000:01:09.1
Yenta: CardBus bridge found at 0000:01:09.0 [1025:1022]
irq 10: nobody cared!
Call Trace:
[<c0108eca>] __report_bad_irq+0x2a/0x90
[<c0108fc0>] note_interrupt+0x70/0xb0
[<c0109270>] do_IRQ+0x120/0x130
[<c0107618>] common_interrupt+0x18/0x20
[<c01217ee>] do_softirq+0x3e/0xa0
[<c010924a>] do_IRQ+0xfa/0x130
[<c0107618>] common_interrupt+0x18/0x20
[<c0113284>] delay_pmtmr+0x14/0x20
[<c01cf512>] __delay+0x12/0x20
[<d0dba9fe>] yenta_probe_irq+0xfe/0x140 [yenta_socket]
[<d0dbaa7a>] yenta_get_socket_capabilities+0x3a/0x70 [yenta_socket]
[<d0dbadc7>] yenta_probe+0x1a7/0x240 [yenta_socket]
[<c01d3712>] pci_device_probe_static+0x52/0x70
[<c01d376c>] __pci_device_probe+0x3c/0x50
[<c01d37ac>] pci_device_probe+0x2c/0x50
[<c0232b1f>] bus_match+0x3f/0x70
[<c0232c4c>] driver_attach+0x5c/0xa0
[<c0232f78>] bus_add_driver+0xa8/0xc0
[<c02333cf>] driver_register+0x2f/0x40
[<c01d399c>] pci_register_driver+0x5c/0x90
[<d0dbe00f>] yenta_socket_init+0xf/0x11 [yenta_socket]
[<c0134722>] sys_init_module+0x142/0x280
[<c0107459>] sysenter_past_esp+0x52/0x71
handlers:
[<d0913890>] (snd_intel8x0_interrupt+0x0/0x240 [snd_intel8x0])
[<d090ba10>] (ohci_irq_handler+0x0/0x860 [ohci1394])
[<d0db98a0>] (yenta_interrupt+0x0/0x40 [yenta_socket])
Disabling IRQ #10
Yenta: ISA IRQ mask 0x00b8, PCI irq 11
Socket status: 30000006
IRQ for 0000:01:09.1:0 -> PIRQ 63, mask 0800, excl 0000 -> newirq=11 -> got IRQ 11
PCI: Found IRQ 11 for device 0000:01:09.1
PCI: Sharing IRQ 11 with 0000:00:1d.1
PCI: Sharing IRQ 11 with 0000:01:09.0
Yenta: CardBus bridge found at 0000:01:09.1 [1025:1022]
Yenta: ISA IRQ mask 0x00b8, PCI irq 11
Socket status: 30000410
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x240-0x247 0x378-0x38f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
orinoco.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
orinoco_cs.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
eth1: Station identity 001f:0001:0006:0010
eth1: Looks like a Lucent/Agere firmware version 6.16
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:02:2D:46:11:44
eth1: Station name "HERMES I"
eth1: ready
eth1: index 0x01: Vcc 3.3, irq 10, io 0x0100-0x013f
[root@peorth root]# dmidecode
# dmidecode 2.2
SMBIOS 2.3 present.
37 structures occupying 1234 bytes.
Table at 0x000FB880.
Handle 0x0000
DMI type 0, 19 bytes.
BIOS Information
Vendor: ACER
Version: V3.3 R01-B1 EN
Release Date: 12/10/2001
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 512 kB
Characteristics:
ISA is supported
PCI is supported
PC Card (PCMCIA) is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
3.5"/720 KB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
AGP is supported
Smart battery is supported
Handle 0x0100
DMI type 1, 25 bytes.
System Information
Manufacturer: Acer
Product Name: TravelMate 360
Version: -1
Serial Number: 9145S0111T209003A4K000
UUID: FFFFD8C7-F860-2BB7-11D6-A4A3AB8B57C8
Wake-up Type: <OUT OF SPEC>
Handle 0x0200
DMI type 2, 8 bytes.
Base Board Information
Manufacturer: Acer
Product Name: Intel Almador-M
Version: -1
Serial Number: 9145S0111T209003A4K000
Handle 0x0300
DMI type 3, 13 bytes.
Chassis Information
Manufacturer: Acer
Type: Notebook
Lock: Not Present
Version: -1
Serial Number: 9145S0111T209003A4K000
Asset Tag:
Boot-up State: Unknown
Power Supply State: Unknown
Thermal State: Unknown
Security Status: Unknown
Handle 0x0400
DMI type 4, 32 bytes.
Processor Information
Socket Designation: U11
Type: Central Processor
Family: Pentium III
Manufacturer: Intel
ID: B1 06 00 00 FF F9 83 03
Signature: Type 0, Family 6, Model B, Stepping 1
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
MMX (MMX technology supported)
FXSR (Fast floating-point save and restore)
SSE (Streaming SIMD extensions)
Version: Pentium(R) III
Voltage: 1.6 V
External Clock: 133 MHz
Max Speed: 1000 MHz
Current Speed: 1000 MHz
Status: Unpopulated
Upgrade: Daughter Board
L1 Cache Handle: 0x0700
L2 Cache Handle: 0x0701
L3 Cache Handle: Not Provided
Handle 0x0500
DMI type 5, 20 bytes.
Memory Controller Information
Error Detecting Method: None
Error Correcting Capabilities:
None
Supported Interleave: Unknown
Current Interleave: Unknown
Maximum Memory Module Size: 256 MB
Maximum Total Memory Size: 512 MB
Supported Speeds:
Unknown
Supported Memory Types:
DIMM
SDRAM
Memory Module Voltage: 3.3 V
Associated Memory Slots: 2
0x0600
0x0601
Enabled Error Correcting Capabilities:
None
Handle 0x0600
DMI type 6, 12 bytes.
Memory Module Information
Socket Designation: DM2
Bank Connections: None
Current Speed: Unknown
Type: Unknown
Installed Size: Not Installed (Single-bank Connection)
Enabled Size: Not Installed (Single-bank Connection)
Error Status: OK
Handle 0x0601
DMI type 6, 12 bytes.
Memory Module Information
Socket Designation: CN22
Bank Connections: 2 3
Current Speed: Unknown
Type: DIMM SDRAM
Installed Size: 256 MB (Single-bank Connection)
Enabled Size: 256 MB (Single-bank Connection)
Error Status: OK
Handle 0x0700
DMI type 7, 19 bytes.
Cache Information
Socket Designation: U11
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 32 KB
Maximum Size: 32 KB
Supported SRAM Types:
Unknown
Installed SRAM Type: Unknown
Speed: Unknown
Error Correction Type: Unknown
System Type: Unified
Associativity: Unknown
Handle 0x0701
DMI type 7, 19 bytes.
Cache Information
Socket Designation: U37
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Write Back
Location: Internal
Installed Size: 512 KB
Maximum Size: 512 KB
Supported SRAM Types:
Pipeline Burst
Synchronous
Installed SRAM Type: Pipeline Burst
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: Fully Associative
Handle 0x0800
DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: CN2
Internal Connector Type: None
External Reference Designator: Serial 1
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x0801
DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: U1
Internal Connector Type: None
External Reference Designator: Infrared
External Connector Type: Infrared
Port Type: Other
Handle 0x0802
DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: CN3
Internal Connector Type: None
External Reference Designator: Parallel
External Connector Type: DB-25 female
Port Type: Parallel Port ECP
Handle 0x0803
DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: CN1
Internal Connector Type: None
External Reference Designator: KEYBOARD
External Connector Type: PS/2
Port Type: Keyboard Port
Handle 0x0804
DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: CN1
Internal Connector Type: None
External Reference Designator: MOUSE
External Connector Type: PS/2
Port Type: Mouse Port
Handle 0x0805
DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: CN5
Internal Connector Type: None
External Reference Designator: USB
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0806
DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: CN6
Internal Connector Type: None
External Reference Designator: USB
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0807
DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: CN26
Internal Connector Type: None
External Reference Designator: MODEM
External Connector Type: RJ-11
Port Type: Modem Port
Handle 0x0808
DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: U49
Internal Connector Type: None
External Reference Designator: LAN
External Connector Type: RJ-45
Port Type: Network Port
Handle 0x0809
DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: CN24
Internal Connector Type: Proprietary
External Reference Designator: LINE-IN JACK
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x080A
DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: CN24
Internal Connector Type: Proprietary
External Reference Designator: HEADPHONE-OUT JACK
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x080B
DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: CN24
Internal Connector Type: Proprietary
External Reference Designator: MICROPHONE-IN JACK
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x080C
DMI type 8, 9 bytes.
Port Connector Information
Internal Reference Designator: CN2
Internal Connector Type: None
External Reference Designator: EXTERNAL DISPLAY
External Connector Type: DB-15 female
Port Type: Video Port
Handle 0x0900
DMI type 9, 13 bytes.
System Slot Information
Designation: CN13A
Type: 32-bit PC Card (PCMCIA)
Current Usage: Available
Length: Long
ID: Adapter 0, Socket 1
Characteristics:
5.0 V is provided
3.3 V is provided
PME signal is supported
Handle 0x0901
DMI type 9, 13 bytes.
System Slot Information
Designation: CN13B
Type: 32-bit PC Card (PCMCIA)
Current Usage: Available
Length: Long
ID: Adapter 0, Socket 2
Characteristics:
5.0 V is provided
3.3 V is provided
PME signal is supported
Handle 0x0A00
DMI type 10, 8 bytes.
On Board Device Information
Type: Video
Status: Enabled
Description: Trident 9525DVD
On Board Device Information
Type: Sound
Status: Enabled
Description: Intel AC97
Handle 0x0D00
DMI type 13, 22 bytes.
BIOS Language Information
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x1000
DMI type 16, 15 bytes.
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 256 MB
Error Information Handle: Not Provided
Number Of Devices: 2
Handle 0x1100
DMI type 17, 23 bytes.
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: No Module Installed
Form Factor: DIMM
Set: 2
Locator: DM2
Bank Locator: BANK 0
Type: SDRAM
Type Detail: Synchronous
Speed: Unknown
Handle 0x1101
DMI type 17, 23 bytes.
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 256 MB
Form Factor: DIMM
Set: 2
Locator: CN22
Bank Locator: BANK 1
Type: SDRAM
Type Detail: Synchronous
Speed: Unknown
Handle 0x1300
DMI type 19, 15 bytes.
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0000FFFFFFF
Range Size: 256 MB
Physical Array Handle: 0x1000
Partition Width: 0
Handle 0x1400
DMI type 20, 19 bytes.
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000000003FF
Range Size: 1 kB
Physical Device Handle: 0x1100
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Handle 0x1401
DMI type 20, 19 bytes.
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0000FFFFFFF
Range Size: 256 MB
Physical Device Handle: 0x1101
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Handle 0x1500
DMI type 21, 7 bytes.
Built-in Pointing Device
Type: Touch Pad
Interface: PS/2
Buttons: 4
Handle 0x1600
DMI type 22, 16 bytes.
Portable Battery
Location: On the Right-hand side
Manufacturer:
Manufacture Date:
Serial Number:
Name:
Chemistry: Lithium Ion
Design Capacity: Unknown
Design Voltage: Unknown
SBDS Version:
Maximum Error: 6%
Handle 0x2000
DMI type 32, 11 bytes.
System Boot Information
Status: No errors detected
Handle 0x7F00
DMI type 127, 4 bytes.
End Of Table
Wrong DMI structures length: 1234 bytes announced, structures occupy 1228 bytes.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.6.5 yenta_socket irq 10: nobody cared!
2004-04-07 19:24 ` Kitt Tientanopajai
@ 2004-04-07 20:25 ` Daniel Ritz
2004-04-08 7:37 ` Kitt Tientanopajai
0 siblings, 1 reply; 13+ messages in thread
From: Daniel Ritz @ 2004-04-07 20:25 UTC (permalink / raw)
To: Kitt Tientanopajai; +Cc: linux-kernel
On Wednesday 07 April 2004 21:24, Kitt Tientanopajai wrote:
> Hi
>
> > looks like you need a little workaround in the interuput routing code...please
> > apply the attached patch, send dmesg output plus output of dmidecode
> > ( http://www.nongnu.org/demidecode/ ).
>
> Guess so, I've tried on 2.6.5 with acpi=off, pci=biosirq, and excluded irq 11 in /etc/pcmcia/config.opts. They still routed to irq 11.
>
>
just as an information: there is a newer BIOS here:
ftp://ftp.support.acer-euro.com/notebook/TravelMate_36x/bios/avb10sus.zip
ok, try the attached one...at least it compiles..
rgds
-daniel
--- 1.36/arch/i386/pci/irq.c Fri Feb 27 06:48:13 2004
+++ edited/arch/i386/pci/irq.c Wed Apr 7 22:15:11 2004
@@ -22,6 +22,7 @@
#define PIRQ_VERSION 0x0100
int broken_hp_bios_irq9;
+int acer_tm360_irqrouting;
static struct irq_routing_table *pirq_table;
@@ -745,6 +744,13 @@
dev->irq = 11;
pci_write_config_byte(dev, PCI_INTERRUPT_LINE, 11);
r->set(pirq_router_dev, dev, pirq, 11);
+ }
+
+ /* same for Acer Travelmate 360, but with CB and irq 11 -> 10 */
+ if (acer_tm360_irqrouting && pirq == 0x63 && dev->irq == 11) {
+ dev->irq = 10;
+ pci_write_config_byte(dev, PCI_INTERRUPT_LINE, 10);
+ r->set(pirq_router_dev, dev, pirq, 10);
}
/*
--- 1.56/arch/i386/kernel/dmi_scan.c Sun Mar 21 06:33:07 2004
+++ edited/arch/i386/kernel/dmi_scan.c Wed Apr 7 22:19:57 2004
@@ -360,6 +360,22 @@
}
/*
+ * Work around broken Acer TravelMate 360 Notebooks which assign Cardbus to
+ * IRQ 11 even though it is actually wired to IRQ 10
+ */
+static __init int fix_acer_tm360_irqrouting(struct dmi_blacklist *d)
+{
+#ifdef CONFIG_PCI
+ extern int acer_tm360_irqrouting;
+ if (acer_tm360_irqrouting == 0)
+ {
+ acer_tm360_irqrouting = 1;
+ printk(KERN_INFO "%s detected - fixing broken IRQ routing\n", d->ident);
+ }
+#endif
+ return 0;
+}
+/*
* Check for clue free BIOS implementations who use
* the following QA technique
*
@@ -890,6 +906,13 @@
MATCH(DMI_PRODUCT_VERSION, "HP Pavilion Notebook Model GE"),
MATCH(DMI_BOARD_VERSION, "OmniBook N32N-736")
} },
+
+ { fix_acer_tm360_irqrouting, "Acer TravelMate 36x Laptop", {
+ MATCH(DMI_SYS_VENDOR, "Acer"),
+ MATCH(DMI_PRODUCT_NAME, "TravelMate 360"),
+ NO_MATCH, NO_MATCH
+ } },
+
/*
@@ -1028,6 +1051,12 @@
MATCH(DMI_BIOS_VERSION, "ASUS A7V ACPI BIOS Revision 1007"),
NO_MATCH }},
+ { disable_acpi_pci, "Acer TravelMate 36x Laptop", {
+ MATCH(DMI_SYS_VENDOR, "Acer"),
+ MATCH(DMI_PRODUCT_NAME, "TravelMate 360"),
+ NO_MATCH, NO_MATCH
+ } },
+
#endif
{ NULL, }
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.6.5 yenta_socket irq 10: nobody cared!
2004-04-07 20:25 ` Daniel Ritz
@ 2004-04-08 7:37 ` Kitt Tientanopajai
2004-04-08 15:17 ` Daniel Ritz
0 siblings, 1 reply; 13+ messages in thread
From: Kitt Tientanopajai @ 2004-04-08 7:37 UTC (permalink / raw)
To: daniel.ritz; +Cc: linux-kernel
Hi,
> ok, try the attached one...at least it compiles..
>
> rgds
> -daniel
Yes, the patch does work :) Now, I can insert card to the slot controlled by o2micro, no freeze :) My orinoco on TI controller works nicely too, no TX error anymore :)
Thank you very much for your help.
kitt
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.6.5 yenta_socket irq 10: nobody cared!
2004-04-08 7:37 ` Kitt Tientanopajai
@ 2004-04-08 15:17 ` Daniel Ritz
2004-04-09 2:30 ` Kitt Tientanopajai
0 siblings, 1 reply; 13+ messages in thread
From: Daniel Ritz @ 2004-04-08 15:17 UTC (permalink / raw)
To: Kitt Tientanopajai; +Cc: linux-kernel
On Thursday 08 April 2004 09:37, Kitt Tientanopajai wrote:
> Hi,
>
> > ok, try the attached one...at least it compiles..
> >
> > rgds
> > -daniel
>
> Yes, the patch does work :) Now, I can insert card to the slot controlled by o2micro, no freeze :) My orinoco on TI controller works nicely too, no TX error anymore :)
>
> Thank you very much for your help.
> kitt
>
you're welcome. but i now have the feeling that it's wrong. so another question:
my patch also changes the interrupt assignment for the USB controller at 00:1d.1
so the question is: does this one work ok? or is there an interrupt storm as soon
as you use the device? (like with yenta_socket before)
i looked at the spec of the o2micro controller. from your kernel 2.4-with-pcmcia-cs
output i can see that the o2micro is configured in pci/way mode which means
interrupts are serialized. so it is possible that the INTA/INTB pins are not
connected on the o2micro. the serial interrupt controller in the 82801CAM
assignes INTA on serial to PIRQA, INTB to PIRQB and so on...
so if the o2micro's INTA are actually connected, it's easy: just set the bit
in the config register and be done with it. if it's not connected than it's
harder. we need to find the right interrupt assignment for the serial
interrupt controller.
can you please undo my previous patch and apply the attached one instead.
the socket may be not working, but it prints the relevant registers from
the o2micro chip.
-daniel
===== drivers/pcmcia/yenta_socket.c 1.53 vs edited =====
--- 1.53/drivers/pcmcia/yenta_socket.c Thu Mar 25 11:20:36 2004
+++ edited/drivers/pcmcia/yenta_socket.c Thu Apr 8 16:56:07 2004
@@ -665,6 +665,7 @@
#include "ti113x.h"
#include "ricoh.h"
#include "topic.h"
+#include "o2micro.h"
enum {
CARDBUS_TYPE_DEFAULT = -1,
@@ -673,7 +674,8 @@
CARDBUS_TYPE_TI12XX,
CARDBUS_TYPE_TI1250,
CARDBUS_TYPE_RICOH,
- CARDBUS_TYPE_TOPIC97
+ CARDBUS_TYPE_TOPIC97,
+ CARDBUS_TYPE_O2MICRO,
};
/*
@@ -713,6 +715,9 @@
[CARDBUS_TYPE_TOPIC97] = {
.override = topic97_override,
},
+ [CARDBUS_TYPE_O2MICRO] = {
+ .override = o2micro_override,
+ },
};
@@ -1030,6 +1035,13 @@
CB_ID(PCI_VENDOR_ID_TOSHIBA, PCI_DEVICE_ID_TOSHIBA_TOPIC97, TOPIC97),
CB_ID(PCI_VENDOR_ID_TOSHIBA, PCI_DEVICE_ID_TOSHIBA_TOPIC100, TOPIC97),
+
+ CB_ID(PCI_VENDOR_ID_O2, PCI_DEVICE_ID_O2_6729, O2MICRO),
+ CB_ID(PCI_VENDOR_ID_O2, PCI_DEVICE_ID_O2_6730, O2MICRO),
+ CB_ID(PCI_VENDOR_ID_O2, PCI_DEVICE_ID_O2_6812, O2MICRO),
+ CB_ID(PCI_VENDOR_ID_O2, PCI_DEVICE_ID_O2_6832, O2MICRO),
+ CB_ID(PCI_VENDOR_ID_O2, PCI_DEVICE_ID_O2_6836, O2MICRO),
+ CB_ID(PCI_VENDOR_ID_O2, PCI_DEVICE_ID_O2_6933, O2MICRO),
/* match any cardbus bridge */
CB_ID(PCI_ANY_ID, PCI_ANY_ID, DEFAULT),
===== drivers/pcmcia/i82365.c 1.49 vs edited =====
--- 1.49/drivers/pcmcia/i82365.c Sun Mar 14 21:10:41 2004
+++ edited/drivers/pcmcia/i82365.c Thu Apr 8 17:07:06 2004
@@ -65,7 +65,6 @@
#include "cirrus.h"
#include "vg468.h"
#include "ricoh.h"
-#include "o2micro.h"
#ifdef DEBUG
static const char *version =
===== drivers/pcmcia/o2micro.h 1.3 vs edited =====
--- 1.3/drivers/pcmcia/o2micro.h Sat Oct 19 01:11:25 2002
+++ edited/drivers/pcmcia/o2micro.h Thu Apr 8 16:59:14 2004
@@ -48,6 +48,9 @@
#ifndef PCI_DEVICE_ID_O2_6812
#define PCI_DEVICE_ID_O2_6812 0x6872
#endif
+#ifndef PCI_DEVICE_ID_O2_6933
+#define PCI_DEVICE_ID_O2_6933 0x6933
+#endif
/* Additional PCI configuration registers */
@@ -103,6 +106,10 @@
#define O2_MODE_D_W97_IRQ 0x40
#define O2_MODE_D_ISA_IRQ 0x80
+#define O2_MODE_D_IRQ_PCPCI 0x00
+#define O2_MODE_D_IRQ_SER 0x02
+#define O2_MODE_D_IRQ_PCI 0x03
+
#define O2_MHPG_DMA 0x3c
#define O2_MHPG_CHANNEL 0x07
#define O2_MHPG_CINT_ENA 0x08
@@ -119,5 +126,25 @@
#define O2_MODE_E_SPKR_OUT 0x02
#define O2_MODE_E_LED_OUT 0x08
#define O2_MODE_E_SKTA_ACTV 0x10
+
+static int o2micro_override(struct yenta_socket *socket)
+{
+ u8 mode_d;
+ u32 mux_ctrl;
+
+ mode_d = config_readb(socket, O2_MODE_D);
+ mux_ctrl = config_readl(socket, O2_MUX_CONTROL);
+
+ printk(KERN_INFO "Yenta O2: socket %s, Mux Ctrk: %08x, Mode D: %02x\n",
+ pci_name(socket->dev), mux_ctrl, mode_d);
+
+ /* XXX: hack: make sure PCI interrupt are not serialized */
+ if ((mode_d & O2_MODE_D_IRQ_MODE) == O2_MODE_D_IRQ_SER) {
+ mux_ctrl &= ~O2_MUX_SER_PCI;
+ config_writel(socket, O2_MUX_CONTROL, mux_ctrl);
+ }
+
+ return 0;
+}
#endif /* _LINUX_O2MICRO_H */
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.6.5 yenta_socket irq 10: nobody cared!
2004-04-08 15:17 ` Daniel Ritz
@ 2004-04-09 2:30 ` Kitt Tientanopajai
2004-04-09 17:41 ` Daniel Ritz
0 siblings, 1 reply; 13+ messages in thread
From: Kitt Tientanopajai @ 2004-04-09 2:30 UTC (permalink / raw)
To: daniel.ritz; +Cc: linux-kernel
Hi,
> you're welcome. but i now have the feeling that it's wrong. so another question:
> my patch also changes the interrupt assignment for the USB controller at 00:1d.1
> so the question is: does this one work ok? or is there an interrupt storm as soon
> as you use the device? (like with yenta_socket before)
Ah, right, TM361 has two USB ports, one of them has usb mouse attached and seem to be okay. Another one does not work after applying your patch. This is dmesg when I connect Sony Clie to sync data through the USB port, the pilot-xfer cannot sync any data and then exit without any crash/freeze.
usb 1-2: new full speed USB device using address 3
drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OS
drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5
usb 1-2: palm_os_4_probe - error -32 getting connection info
visor 1-2:1.0: Handspring Visor / Palm OS converter detected
usb 1-2: Handspring Visor / Palm OS converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
usb 1-2: Handspring Visor / Palm OS converter now attached to ttyUSB1 (or usb/tts/1 for devfs)
usbcore: registered new driver visor
drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver v2.1
usb 1-2: USB disconnect, address 3
visor 1-2:1.0: device disconnected
visor ttyUSB0: visor_write - usb_submit_urb(write bulk) failed with status = -19
visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0
visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1
> can you please undo my previous patch and apply the attached one instead.
> the socket may be not working, but it prints the relevant registers from
> the o2micro chip.
Sure, this is dmesg after patch.
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
PCI: Enabling device 0000:01:05.0 (0000 -> 0002)
PCI: Found IRQ 10 for device 0000:01:05.0
PCI: Sharing IRQ 10 with 0000:01:08.0
Yenta: CardBus bridge found at 0000:01:05.0 [12a3:ab01]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta: ISA IRQ mask 0x0000, PCI irq 10
Socket status: 30000011
PCI: Found IRQ 11 for device 0000:01:09.0
PCI: Sharing IRQ 11 with 0000:00:1d.1
PCI: Sharing IRQ 11 with 0000:01:09.1
Yenta: CardBus bridge found at 0000:01:09.0 [1025:1022]
Yenta O2: socket 0000:01:09.0, Mux Ctrk: 0c00200f, Mode D: 00
irq 10: nobody cared!
Call Trace:
[<c0108eca>] __report_bad_irq+0x2a/0x90
[<c0108fc0>] note_interrupt+0x70/0xb0
[<c0109270>] do_IRQ+0x120/0x130
[<c0107618>] common_interrupt+0x18/0x20
[<c01217ee>] do_softirq+0x3e/0xa0
[<c010924a>] do_IRQ+0xfa/0x130
[<c0107618>] common_interrupt+0x18/0x20
[<c0113284>] delay_pmtmr+0x14/0x20
[<c01cf512>] __delay+0x12/0x20
[<d0da2abe>] yenta_probe_irq+0xfe/0x140 [yenta_socket]
[<d0da2b3a>] yenta_get_socket_capabilities+0x3a/0x70 [yenta_socket]
[<d0da2e87>] yenta_probe+0x1a7/0x240 [yenta_socket]
[<c01d3712>] pci_device_probe_static+0x52/0x70
[<c01d376c>] __pci_device_probe+0x3c/0x50
[<c01d37ac>] pci_device_probe+0x2c/0x50
[<c0232b1f>] bus_match+0x3f/0x70
[<c0232c4c>] driver_attach+0x5c/0xa0
[<c0232f78>] bus_add_driver+0xa8/0xc0
[<c02333cf>] driver_register+0x2f/0x40
[<c01d399c>] pci_register_driver+0x5c/0x90
[<d0d9500f>] yenta_socket_init+0xf/0x11 [yenta_socket]
[<c0134722>] sys_init_module+0x142/0x280
[<c0107459>] sysenter_past_esp+0x52/0x71
handlers:
[<d0d55890>] (snd_intel8x0_interrupt+0x0/0x240 [snd_intel8x0])
[<d0d4da10>] (ohci_irq_handler+0x0/0x860 [ohci1394])
[<d0da18a0>] (yenta_interrupt+0x0/0x40 [yenta_socket])
Disabling IRQ #10
Yenta: ISA IRQ mask 0x00b8, PCI irq 11
Socket status: 30000006
PCI: Found IRQ 11 for device 0000:01:09.1
PCI: Sharing IRQ 11 with 0000:00:1d.1
PCI: Sharing IRQ 11 with 0000:01:09.0
Yenta: CardBus bridge found at 0000:01:09.1 [1025:1022]
Yenta O2: socket 0000:01:09.1, Mux Ctrk: 0c00200f, Mode D: 00
Yenta: ISA IRQ mask 0x0038, PCI irq 11
Socket status: 30000410
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x240-0x247 0x378-0x38f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
orinoco.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
orinoco_cs.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
eth1: Station identity 001f:0001:0006:0010
eth1: Looks like a Lucent/Agere firmware version 6.16
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:02:2D:46:11:44
eth1: Station name "HERMES I"
eth1: ready
eth1: index 0x01: Vcc 3.3, irq 10, io 0x0100-0x013f
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.6.5 yenta_socket irq 10: nobody cared!
2004-04-09 2:30 ` Kitt Tientanopajai
@ 2004-04-09 17:41 ` Daniel Ritz
2004-04-10 3:18 ` Kitt Tientanopajai
0 siblings, 1 reply; 13+ messages in thread
From: Daniel Ritz @ 2004-04-09 17:41 UTC (permalink / raw)
To: Kitt Tientanopajai; +Cc: linux-kernel, David Hinds
On Friday 09 April 2004 04:30, Kitt Tientanopajai wrote:
> Hi,
>
> > you're welcome. but i now have the feeling that it's wrong. so another question:
> > my patch also changes the interrupt assignment for the USB controller at 00:1d.1
> > so the question is: does this one work ok? or is there an interrupt storm as soon
> > as you use the device? (like with yenta_socket before)
>
> Ah, right, TM361 has two USB ports, one of them has usb mouse attached and seem to be okay.
> Another one does not work after applying your patch. This is dmesg when I connect Sony Clie to
> sync data through the USB port, the pilot-xfer cannot sync any data and then exit without any
> crash/freeze.
with my first patch applied, does the mouse work on the second port?
>
> usb 1-2: new full speed USB device using address 3
> drivers/usb/serial/usb-serial.c: USB Serial support registered for Generic
> usbcore: registered new driver usbserial
> drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
> drivers/usb/serial/usb-serial.c: USB Serial support registered for Handspring Visor / Palm OS
> drivers/usb/serial/usb-serial.c: USB Serial support registered for Sony Clie 3.5
> usb 1-2: palm_os_4_probe - error -32 getting connection info
> visor 1-2:1.0: Handspring Visor / Palm OS converter detected
> usb 1-2: Handspring Visor / Palm OS converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
> usb 1-2: Handspring Visor / Palm OS converter now attached to ttyUSB1 (or usb/tts/1 for devfs)
> usbcore: registered new driver visor
> drivers/usb/serial/visor.c: USB HandSpring Visor / Palm OS driver v2.1
> usb 1-2: USB disconnect, address 3
> visor 1-2:1.0: device disconnected
> visor ttyUSB0: visor_write - usb_submit_urb(write bulk) failed with status = -19
> visor ttyUSB0: Handspring Visor / Palm OS converter now disconnected from ttyUSB0
> visor ttyUSB1: Handspring Visor / Palm OS converter now disconnected from ttyUSB1
>
> > can you please undo my previous patch and apply the attached one instead.
> > the socket may be not working, but it prints the relevant registers from
> > the o2micro chip.
>
> Sure, this is dmesg after patch.
>
> Linux Kernel Card Services
> options: [pci] [cardbus] [pm]
> PCI: Enabling device 0000:01:05.0 (0000 -> 0002)
> PCI: Found IRQ 10 for device 0000:01:05.0
> PCI: Sharing IRQ 10 with 0000:01:08.0
> Yenta: CardBus bridge found at 0000:01:05.0 [12a3:ab01]
> Yenta: Enabling burst memory read transactions
> Yenta: Using CSCINT to route CSC interrupts to PCI
> Yenta: Routing CardBus interrupts to PCI
> Yenta: ISA IRQ mask 0x0000, PCI irq 10
> Socket status: 30000011
> PCI: Found IRQ 11 for device 0000:01:09.0
> PCI: Sharing IRQ 11 with 0000:00:1d.1
> PCI: Sharing IRQ 11 with 0000:01:09.1
> Yenta: CardBus bridge found at 0000:01:09.0 [1025:1022]
> Yenta O2: socket 0000:01:09.0, Mux Ctrk: 0c00200f, Mode D: 00
ok, i made a mistake here. in o2micro.h it should have been
mode_d = exca_readb(socket, O2_MODE_D);
(exca_readb, not config_readb)
but then the Mux control register already looks ok:
PCI INTA and INTB are routed to the PCI pins
so i really don't know why lspci shows pin A routed to irq 11 for both
functions...the o2micro spec says the interrupt pin register always contains
pin B for function 1.
so i CCed dave hinds as he may know the o2micro bridge a bit better.
could you try to replace the function o2micro_override() in drivers/pcmcia/o2micro.h
with this one?
static int o2micro_override(struct yenta_socket *socket)
{
u8 mode_a, mode_b, mode_c, mode_d;
u32 mux_ctrl;
mode_a = exca_readb(socket, O2_MODE_A);
mode_b = exca_readb(socket, O2_MODE_B);
mode_c = exca_readb(socket, O2_MODE_C);
mode_d = exca_readb(socket, O2_MODE_D);
mux_ctrl = config_readl(socket, O2_MUX_CONTROL);
printk(KERN_INFO "Yenta O2: socket %s, Mux Ctrl: %08x, Mode A: %02x, B: %02x, C: %02x, D: %02x\n",
pci_name(socket->dev), mux_ctrl, mode_a, mode_b, mode_c, mode_d);
/* enable O2Micro mode */
mode_b &= ~O2_MODE_B_IDENT;
mode_b |= O2_MODE_B_ID_O2;
exca_writeb(socket, O2_MODE_B, mode_d);
/* XXX: hack: enable PCI only mode */
mode_d |= O2_MODE_D_IRQ_PCI;
exca_writeb(socket, O2_MODE_D, mode_d);
return 0;
}
so we're in PCI only mode. if it's still not working, then it's the interrupt
routing from the bios i think
-daniel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.6.5 yenta_socket irq 10: nobody cared!
2004-04-09 17:41 ` Daniel Ritz
@ 2004-04-10 3:18 ` Kitt Tientanopajai
2004-04-10 16:14 ` Daniel Ritz
0 siblings, 1 reply; 13+ messages in thread
From: Kitt Tientanopajai @ 2004-04-10 3:18 UTC (permalink / raw)
To: daniel.ritz; +Cc: linux-kernel, dhinds
Hi
> > > you're welcome. but i now have the feeling that it's wrong. so another question:
> > > my patch also changes the interrupt assignment for the USB controller at 00:1d.1
> > > so the question is: does this one work ok? or is there an interrupt storm as soon
> > > as you use the device? (like with yenta_socket before)
> >
> > Ah, right, TM361 has two USB ports, one of them has usb mouse attached and seem to be okay.
> > Another one does not work after applying your patch. This is dmesg when I connect Sony Clie to
> > sync data through the USB port, the pilot-xfer cannot sync any data and then exit without any
> > crash/freeze.
>
> with my first patch applied, does the mouse work on the second port?
Yes, usb mouse works. And when I discovered that clie sync did not work on on one port, I just replace mouse with clie sync cable, and sync data through it successfully.
> > Linux Kernel Card Services
> > options: [pci] [cardbus] [pm]
> > PCI: Enabling device 0000:01:05.0 (0000 -> 0002)
> > PCI: Found IRQ 10 for device 0000:01:05.0
> > PCI: Sharing IRQ 10 with 0000:01:08.0
> > Yenta: CardBus bridge found at 0000:01:05.0 [12a3:ab01]
> > Yenta: Enabling burst memory read transactions
> > Yenta: Using CSCINT to route CSC interrupts to PCI
> > Yenta: Routing CardBus interrupts to PCI
> > Yenta: ISA IRQ mask 0x0000, PCI irq 10
> > Socket status: 30000011
> > PCI: Found IRQ 11 for device 0000:01:09.0
> > PCI: Sharing IRQ 11 with 0000:00:1d.1
> > PCI: Sharing IRQ 11 with 0000:01:09.1
> > Yenta: CardBus bridge found at 0000:01:09.0 [1025:1022]
> > Yenta O2: socket 0000:01:09.0, Mux Ctrk: 0c00200f, Mode D: 00
>
> ok, i made a mistake here. in o2micro.h it should have been
> mode_d = exca_readb(socket, O2_MODE_D);
> (exca_readb, not config_readb)
>
> but then the Mux control register already looks ok:
> PCI INTA and INTB are routed to the PCI pins
>
> so i really don't know why lspci shows pin A routed to irq 11 for both
> functions...the o2micro spec says the interrupt pin register always contains
> pin B for function 1.
>
> so i CCed dave hinds as he may know the o2micro bridge a bit better.
>
> could you try to replace the function o2micro_override() in drivers/pcmcia/o2micro.h
> with this one?
replaced, and here is the dmesg.
rgds,
kitt
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
PCI: Enabling device 0000:01:05.0 (0000 -> 0002)
PCI: Found IRQ 10 for device 0000:01:05.0
PCI: Sharing IRQ 10 with 0000:01:08.0
Yenta: CardBus bridge found at 0000:01:05.0 [12a3:ab01]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta: ISA IRQ mask 0x0000, PCI irq 10
Socket status: 30000011
PCI: Found IRQ 11 for device 0000:01:09.0
PCI: Sharing IRQ 11 with 0000:00:1d.1
PCI: Sharing IRQ 11 with 0000:01:09.1
Yenta: CardBus bridge found at 0000:01:09.0 [1025:1022]
Yenta O2: socket 0000:01:09.0, Mux Ctrl: 0c00200f, Mode A: 00, B: 00, C: 00, D: 42
irq 10: nobody cared!
Call Trace:
[<c0108eca>] __report_bad_irq+0x2a/0x90
[<c0108fc0>] note_interrupt+0x70/0xb0
[<c0109270>] do_IRQ+0x120/0x130
[<c0107618>] common_interrupt+0x18/0x20
[<c01217ee>] do_softirq+0x3e/0xa0
[<c010924a>] do_IRQ+0xfa/0x130
[<c0107618>] common_interrupt+0x18/0x20
[<c0113284>] delay_pmtmr+0x14/0x20
[<c01cf512>] __delay+0x12/0x20
[<d0dbaace>] yenta_probe_irq+0xfe/0x140 [yenta_socket]
[<d0dbab4a>] yenta_get_socket_capabilities+0x3a/0x70 [yenta_socket]
[<d0dbae97>] yenta_probe+0x1a7/0x240 [yenta_socket]
[<c01d3712>] pci_device_probe_static+0x52/0x70
[<c01d376c>] __pci_device_probe+0x3c/0x50
[<c01d37ac>] pci_device_probe+0x2c/0x50
[<c0232b1f>] bus_match+0x3f/0x70
[<c0232c4c>] driver_attach+0x5c/0xa0
[<c0232f78>] bus_add_driver+0xa8/0xc0
[<c02333cf>] driver_register+0x2f/0x40
[<c01d399c>] pci_register_driver+0x5c/0x90
[<d0dbe00f>] yenta_socket_init+0xf/0x11 [yenta_socket]
[<c0134722>] sys_init_module+0x142/0x280
[<c0107459>] sysenter_past_esp+0x52/0x71
handlers:
[<d0913890>] (snd_intel8x0_interrupt+0x0/0x240 [snd_intel8x0])
[<d090ba10>] (ohci_irq_handler+0x0/0x860 [ohci1394])
[<d0db98a0>] (yenta_interrupt+0x0/0x40 [yenta_socket])
Disabling IRQ #10
Yenta: ISA IRQ mask 0x0000, PCI irq 11
Socket status: 30000006
PCI: Found IRQ 11 for device 0000:01:09.1
PCI: Sharing IRQ 11 with 0000:00:1d.1
PCI: Sharing IRQ 11 with 0000:01:09.0
Yenta: CardBus bridge found at 0000:01:09.1 [1025:1022]
Yenta O2: socket 0000:01:09.1, Mux Ctrl: 0c00200f, Mode A: 00, B: 00, C: 50, D: 43
Yenta: ISA IRQ mask 0x0000, PCI irq 11
Socket status: 30000410
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.6.5 yenta_socket irq 10: nobody cared!
2004-04-10 3:18 ` Kitt Tientanopajai
@ 2004-04-10 16:14 ` Daniel Ritz
2004-04-10 19:40 ` Kitt Tientanopajai
0 siblings, 1 reply; 13+ messages in thread
From: Daniel Ritz @ 2004-04-10 16:14 UTC (permalink / raw)
To: Kitt Tientanopajai; +Cc: linux-kernel
On Saturday 10 April 2004 05:18, Kitt Tientanopajai wrote:
> Hi
>
> > > > you're welcome. but i now have the feeling that it's wrong. so another question:
> > > > my patch also changes the interrupt assignment for the USB controller at 00:1d.1
> > > > so the question is: does this one work ok? or is there an interrupt storm as soon
> > > > as you use the device? (like with yenta_socket before)
> > >
> > > Ah, right, TM361 has two USB ports, one of them has usb mouse attached and seem to be okay.
> > > Another one does not work after applying your patch. This is dmesg when I connect Sony Clie to
> > > sync data through the USB port, the pilot-xfer cannot sync any data and then exit without any
> > > crash/freeze.
> >
> > with my first patch applied, does the mouse work on the second port?
>
> Yes, usb mouse works. And when I discovered that clie sync did not work on on one port, I just replace mouse with clie sync cable, and sync data through it successfully.
>
so you say with my first patch both USB ports are working then? so clie sync only
works on one of the ports but the mouse on both?
> > could you try to replace the function o2micro_override() in drivers/pcmcia/o2micro.h
> > with this one?
>
> replaced, and here is the dmesg.
>
ok, it's the interrupt routing, not the chip config. i think the first patch that
adds the tm361 to the dmi_scan problem table is correct then. real good
QA from acer: hack the BIOS, boot it with windows and if it works, ship it...
it works with windows because it assigned all the devices to the same irq
i'll submit it later to andrew morton.
rgds
-daniel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: 2.6.5 yenta_socket irq 10: nobody cared!
2004-04-10 16:14 ` Daniel Ritz
@ 2004-04-10 19:40 ` Kitt Tientanopajai
0 siblings, 0 replies; 13+ messages in thread
From: Kitt Tientanopajai @ 2004-04-10 19:40 UTC (permalink / raw)
To: daniel.ritz; +Cc: linux-kernel
Hi
> so you say with my first patch both USB ports are working then? so clie sync only
> works on one of the ports but the mouse on both?
I've just tested the usb ports with your first patch again. Now both ports are working, at least for usb mouse, clie sync, and usb storage. So, I think your first patch is okay. Sorry that I did not test them thoroughly at the first time.
> ok, it's the interrupt routing, not the chip config. i think the first patch that
> adds the tm361 to the dmi_scan problem table is correct then. real good
> QA from acer: hack the BIOS, boot it with windows and if it works, ship it...
> it works with windows because it assigned all the devices to the same irq
>
> i'll submit it later to andrew morton.
Please do so. I hope the patch will be included in 2.6.6. Anyway, thanks again for your help.
rgds,
kitt
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2004-04-10 19:40 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-04-06 0:27 2.6.5 yenta_socket irq 10: nobody cared! Daniel Ritz
2004-04-06 2:35 ` Kitt Tientanopajai
2004-04-07 15:41 ` Daniel Ritz
2004-04-07 19:24 ` Kitt Tientanopajai
2004-04-07 20:25 ` Daniel Ritz
2004-04-08 7:37 ` Kitt Tientanopajai
2004-04-08 15:17 ` Daniel Ritz
2004-04-09 2:30 ` Kitt Tientanopajai
2004-04-09 17:41 ` Daniel Ritz
2004-04-10 3:18 ` Kitt Tientanopajai
2004-04-10 16:14 ` Daniel Ritz
2004-04-10 19:40 ` Kitt Tientanopajai
-- strict thread matches above, loose matches on Subject: below --
2004-04-05 2:06 Kitt Tientanopajai
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).