Re: 2.6.12 vs. /sbin/cardmgr
On Sat, 16 Jul 2005 11:36:45 -0500 (CDT), [EMAIL PROTECTED] (Bob Tracy) wrote: >rct wrote: >> Dominik Brodowski wrote: >> > On Sun, Jul 10, 2005 at 03:37:22PM -0500, Bob Tracy wrote: >> > > Dominik Brodowski wrote: >> > > > On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: >> > > > > (/sbin/cardmgr chewing up lots of CPU cycles with 2.6.12 kernel) >> > > > >> > > > Please post the output of "lspci" and "lsmod" as I'd like to know which >> > > > kind of PCMCIA bridge is in your notebook. >> > >> > OK, it's a plain TI1225. Could you try whether the bug is still existent in >> > 2.6.13-rc3, please? >> >> 2.6.13-rc3 works fine here. The "cardmgr" process is no longer chewing >> up lots of CPU time, and otherwise seems to be working correctly. Thanks! > >I spoke too soon :-(. The first boot on 2.6.13-rc3 was fine. Every >boot since then has reflected no change relative to the 2.6.12 behavior. >The "cardmgr" process racks up CPU time almost as fast as time >elapses: it's at the top of the "top" list. I turned off cardmgr for 2.6, CardBus works without it on slackware 'cos pciutils is patched to provide a helper, what is 'correct' way to test this? Toshiba laptop with ToPIC100 bridge, currently not working for PCCard 16-bit things because I turned off cardmgr. CardBus NIC works in 2.4 + 2.6 series. --Grant. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12 vs. /sbin/cardmgr
Hi! On Sat, Jul 16, 2005 at 11:36:45AM -0500, Bob Tracy wrote: > rct wrote: > > Dominik Brodowski wrote: > > > On Sun, Jul 10, 2005 at 03:37:22PM -0500, Bob Tracy wrote: > > > > Dominik Brodowski wrote: > > > > > On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: > > > > > > (/sbin/cardmgr chewing up lots of CPU cycles with 2.6.12 kernel) > > > > > > > > > > Please post the output of "lspci" and "lsmod" as I'd like to know > > > > > which > > > > > kind of PCMCIA bridge is in your notebook. > > > > > > OK, it's a plain TI1225. Could you try whether the bug is still existent > > > in > > > 2.6.13-rc3, please? > > > > 2.6.13-rc3 works fine here. The "cardmgr" process is no longer chewing > > up lots of CPU time, and otherwise seems to be working correctly. Thanks! > > I spoke too soon :-(. The first boot on 2.6.13-rc3 was fine. Every > boot since then has reflected no change relative to the 2.6.12 behavior. > The "cardmgr" process racks up CPU time almost as fast as time > elapses: it's at the top of the "top" list. Can you send me a dmesg of 2.6.13-rc3, please? Thanks, Dominik - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12 vs. /sbin/cardmgr
rct wrote: > Dominik Brodowski wrote: > > On Sun, Jul 10, 2005 at 03:37:22PM -0500, Bob Tracy wrote: > > > Dominik Brodowski wrote: > > > > On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: > > > > > (/sbin/cardmgr chewing up lots of CPU cycles with 2.6.12 kernel) > > > > > > > > Please post the output of "lspci" and "lsmod" as I'd like to know which > > > > kind of PCMCIA bridge is in your notebook. > > > > OK, it's a plain TI1225. Could you try whether the bug is still existent in > > 2.6.13-rc3, please? > > 2.6.13-rc3 works fine here. The "cardmgr" process is no longer chewing > up lots of CPU time, and otherwise seems to be working correctly. Thanks! I spoke too soon :-(. The first boot on 2.6.13-rc3 was fine. Every boot since then has reflected no change relative to the 2.6.12 behavior. The "cardmgr" process racks up CPU time almost as fast as time elapses: it's at the top of the "top" list. -- --- Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org [EMAIL PROTECTED] --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12 vs. /sbin/cardmgr
rct wrote: Dominik Brodowski wrote: On Sun, Jul 10, 2005 at 03:37:22PM -0500, Bob Tracy wrote: Dominik Brodowski wrote: On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: (/sbin/cardmgr chewing up lots of CPU cycles with 2.6.12 kernel) Please post the output of lspci and lsmod as I'd like to know which kind of PCMCIA bridge is in your notebook. OK, it's a plain TI1225. Could you try whether the bug is still existent in 2.6.13-rc3, please? 2.6.13-rc3 works fine here. The cardmgr process is no longer chewing up lots of CPU time, and otherwise seems to be working correctly. Thanks! I spoke too soon :-(. The first boot on 2.6.13-rc3 was fine. Every boot since then has reflected no change relative to the 2.6.12 behavior. The cardmgr process racks up CPU time almost as fast as time elapses: it's at the top of the top list. -- --- Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org [EMAIL PROTECTED] --- - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12 vs. /sbin/cardmgr
Hi! On Sat, Jul 16, 2005 at 11:36:45AM -0500, Bob Tracy wrote: rct wrote: Dominik Brodowski wrote: On Sun, Jul 10, 2005 at 03:37:22PM -0500, Bob Tracy wrote: Dominik Brodowski wrote: On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: (/sbin/cardmgr chewing up lots of CPU cycles with 2.6.12 kernel) Please post the output of lspci and lsmod as I'd like to know which kind of PCMCIA bridge is in your notebook. OK, it's a plain TI1225. Could you try whether the bug is still existent in 2.6.13-rc3, please? 2.6.13-rc3 works fine here. The cardmgr process is no longer chewing up lots of CPU time, and otherwise seems to be working correctly. Thanks! I spoke too soon :-(. The first boot on 2.6.13-rc3 was fine. Every boot since then has reflected no change relative to the 2.6.12 behavior. The cardmgr process racks up CPU time almost as fast as time elapses: it's at the top of the top list. Can you send me a dmesg of 2.6.13-rc3, please? Thanks, Dominik - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12 vs. /sbin/cardmgr
On Sat, 16 Jul 2005 11:36:45 -0500 (CDT), [EMAIL PROTECTED] (Bob Tracy) wrote: rct wrote: Dominik Brodowski wrote: On Sun, Jul 10, 2005 at 03:37:22PM -0500, Bob Tracy wrote: Dominik Brodowski wrote: On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: (/sbin/cardmgr chewing up lots of CPU cycles with 2.6.12 kernel) Please post the output of lspci and lsmod as I'd like to know which kind of PCMCIA bridge is in your notebook. OK, it's a plain TI1225. Could you try whether the bug is still existent in 2.6.13-rc3, please? 2.6.13-rc3 works fine here. The cardmgr process is no longer chewing up lots of CPU time, and otherwise seems to be working correctly. Thanks! I spoke too soon :-(. The first boot on 2.6.13-rc3 was fine. Every boot since then has reflected no change relative to the 2.6.12 behavior. The cardmgr process racks up CPU time almost as fast as time elapses: it's at the top of the top list. I turned off cardmgr for 2.6, CardBus works without it on slackware 'cos pciutils is patched to provide a helper, what is 'correct' way to test this? Toshiba laptop with ToPIC100 bridge, currently not working for PCCard 16-bit things because I turned off cardmgr. CardBus NIC works in 2.4 + 2.6 series. --Grant. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12 vs. /sbin/cardmgr
Dominik Brodowski wrote: > On Sun, Jul 10, 2005 at 03:37:22PM -0500, Bob Tracy wrote: > > Dominik Brodowski wrote: > > > On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: > > > > (/sbin/cardmgr chewing up lots of CPU cycles with 2.6.12 kernel) > > > > > > Please post the output of "lspci" and "lsmod" as I'd like to know which > > > kind of PCMCIA bridge is in your notebook. > > OK, it's a plain TI1225. Could you try whether the bug is still existent in > 2.6.13-rc3, please? 2.6.13-rc3 works fine here. The "cardmgr" process is no longer chewing up lots of CPU time, and otherwise seems to be working correctly. Thanks! -- --- Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org [EMAIL PROTECTED] --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12 vs. /sbin/cardmgr
Hi, On Sun, Jul 10, 2005 at 03:37:22PM -0500, Bob Tracy wrote: > Dominik Brodowski wrote: > > On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: > > > (/sbin/cardmgr chewing up lots of CPU cycles with 2.6.12 kernel) > > > > Please post the output of "lspci" and "lsmod" as I'd like to know which > > kind of PCMCIA bridge is in your notebook. OK, it's a plain TI1225. Could you try whether the bug is still existent in 2.6.13-rc3, please? Thanks, Dominik - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12 vs. /sbin/cardmgr
Hi, On Sun, Jul 10, 2005 at 03:37:22PM -0500, Bob Tracy wrote: Dominik Brodowski wrote: On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: (/sbin/cardmgr chewing up lots of CPU cycles with 2.6.12 kernel) Please post the output of lspci and lsmod as I'd like to know which kind of PCMCIA bridge is in your notebook. OK, it's a plain TI1225. Could you try whether the bug is still existent in 2.6.13-rc3, please? Thanks, Dominik - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12 vs. /sbin/cardmgr
Dominik Brodowski wrote: On Sun, Jul 10, 2005 at 03:37:22PM -0500, Bob Tracy wrote: Dominik Brodowski wrote: On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: (/sbin/cardmgr chewing up lots of CPU cycles with 2.6.12 kernel) Please post the output of lspci and lsmod as I'd like to know which kind of PCMCIA bridge is in your notebook. OK, it's a plain TI1225. Could you try whether the bug is still existent in 2.6.13-rc3, please? 2.6.13-rc3 works fine here. The cardmgr process is no longer chewing up lots of CPU time, and otherwise seems to be working correctly. Thanks! -- --- Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org [EMAIL PROTECTED] --- - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12 vs. /sbin/cardmgr
Dominik Brodowski wrote: > On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: > > (/sbin/cardmgr chewing up lots of CPU cycles with 2.6.12 kernel) > > Please post the output of "lspci" and "lsmod" as I'd like to know which > kind of PCMCIA bridge is in your notebook. -- lspci -v -- 00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03) Flags: bus master, medium devsel, latency 32 Memory at f400 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 1.0 00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 32 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: e000-efff Memory behind bridge: fc00-feff 00:03.0 CardBus bridge: Texas Instruments PCI1225 (rev 01) Subsystem: Dell Computer Corporation: Unknown device 00bb Flags: bus master, medium devsel, latency 168, IRQ 11 Memory at 1010 (32-bit, non-prefetchable) [size=4K] Bus: primary=00, secondary=02, subordinate=05, sec-latency=176 Memory window 0: 1040-107ff000 (prefetchable) Memory window 1: 1080-10bff000 I/O window 0: 4000-40ff I/O window 1: 4400-44ff 16-bit legacy interface ports at 0001 00:03.1 CardBus bridge: Texas Instruments PCI1225 (rev 01) Subsystem: Dell Computer Corporation: Unknown device 00bb Flags: bus master, medium devsel, latency 168, IRQ 11 Memory at 10101000 (32-bit, non-prefetchable) [size=4K] Bus: primary=00, secondary=06, subordinate=09, sec-latency=176 Memory window 0: 10c0-10fff000 (prefetchable) Memory window 1: 1100-113ff000 I/O window 0: 4800-48ff I/O window 1: 4c00-4cff 16-bit legacy interface ports at 0001 00:07.0 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) Flags: bus master, medium devsel, latency 0 00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) (prog-if 80 [Master]) Flags: bus master, medium devsel, latency 32 I/O ports at 0860 [size=16] 00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI]) Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at dce0 [size=32] 00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02) Flags: medium devsel, IRQ 9 00:08.0 Multimedia audio controller: ESS Technology ES1983S Maestro-3i PCI Audio Accelerator (rev 10) Subsystem: Dell Computer Corporation: Unknown device 00bb Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at d800 [size=256] Memory at faffe000 (32-bit, non-prefetchable) [size=8K] Capabilities: [c0] Power Management version 2 01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64) (prog-if 00 [VGA]) Subsystem: Dell Computer Corporation: Unknown device 00bb Flags: bus master, stepping, medium devsel, latency 32, IRQ 11 Memory at fd00 (32-bit, non-prefetchable) [size=16M] I/O ports at ec00 [size=256] Memory at fcfff000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at [disabled] [size=128K] Capabilities: [50] AGP version 1.0 Capabilities: [5c] Power Management version 1 06:00.0 Ethernet controller: Galileo Technology Ltd.: Unknown device 1fa6 (rev 07) Subsystem: D-Link System Inc: Unknown device 3b08 Flags: bus master, 66Mhz, medium devsel, latency 168, IRQ 11 Memory at 1100 (32-bit, non-prefetchable) [size=64K] Memory at 1101 (32-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 2 -- lsmod -- Module Size Used by parport_pc 37252 1 lp 12132 0 parport39048 2 parport_pc,lp irda 132120 0 crc_ccitt 1984 1 irda snd_seq_oss37376 0 snd_seq_midi_event 8320 1 snd_seq_oss snd_seq61552 4 snd_seq_oss,snd_seq_midi_event snd_seq_device 8876 2 snd_seq_oss,snd_seq snd_pcm_oss62784 0 snd_mixer_oss 21440 1 snd_pcm_oss snd_maestro3 24836 0 snd_ac97_codec 85432 1 snd_maestro3 snd_pcm 107012 3 snd_pcm_oss,snd_maestro3,snd_ac97_codec snd_timer 27972 2 snd_seq,snd_pcm snd_page_alloc 10564 1 snd_pcm snd61060 9 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_maestro3,snd_ac97_codec,snd_pcm,snd_timer soundcore 10272 1 snd ide_cd 44196 0 cdrom 42752 1 ide_cd pcmcia 28552 2 yenta_socket 23720 3 rsrc_nonstatic 13952 1
Re: 2.6.12 vs. /sbin/cardmgr
Hi, On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: > I've got a Mandrake 10.0 system with a 2.6.12 kernel presently. > Somewhere between 2.6.11 and 2.6.12, /sbin/cardmgr from the > pcmcia-cs-3.2.5-3mdk package decided it needs to consume incredible > amounts of CPU time when invoked the first time following a boot. > You can definitely notice the load on the system. > > Stopping cardmgr requires a "kill -9": softer kills are ignored. > Restarting cardmgr produces the following output: > > cardmgr[3731]: watching 2 sockets > cardmgr[3731]: could not adjust resource: IO ports 0xc00-0xcff: Device or > resource busy > cardmgr[3731]: could not adjust resource: IO ports 0x100-0x4ff: Device or > resource busy > cardmgr[3731]: could not adjust resource: memory 0xc-0xf: > Input/output error > cardmgr[3731]: could not adjust resource: memory 0x6000-0x60ff: > Input/output error > cardmgr[3731]: could not adjust resource: memory 0xa000-0xa0ff: > Input/output error > cardmgr[3731]: could not adjust resource: IO ports 0x1000-0x1fff: Device or > resource busy > cardmgr[3731]: could not adjust resource: IO ports 0xa00-0xaff: Device or > resource busy > > But at least it doesn't seem to be running around in tight circles at > this point :-). > > System is a Dell Latitude CPxJ notebook that continues to work fine > with 2.6.11 and older kernels. Any idea what changed between 2.6.11 > and 2.6.12 that might be causing this problem? I can probably provide > more info on request. Please post the output of "lspci" and "lsmod" as I'd like to know which kind of PCMCIA bridge is in your notebook. Dominik - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12 vs. /sbin/cardmgr
Hi, On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: I've got a Mandrake 10.0 system with a 2.6.12 kernel presently. Somewhere between 2.6.11 and 2.6.12, /sbin/cardmgr from the pcmcia-cs-3.2.5-3mdk package decided it needs to consume incredible amounts of CPU time when invoked the first time following a boot. You can definitely notice the load on the system. Stopping cardmgr requires a kill -9: softer kills are ignored. Restarting cardmgr produces the following output: cardmgr[3731]: watching 2 sockets cardmgr[3731]: could not adjust resource: IO ports 0xc00-0xcff: Device or resource busy cardmgr[3731]: could not adjust resource: IO ports 0x100-0x4ff: Device or resource busy cardmgr[3731]: could not adjust resource: memory 0xc-0xf: Input/output error cardmgr[3731]: could not adjust resource: memory 0x6000-0x60ff: Input/output error cardmgr[3731]: could not adjust resource: memory 0xa000-0xa0ff: Input/output error cardmgr[3731]: could not adjust resource: IO ports 0x1000-0x1fff: Device or resource busy cardmgr[3731]: could not adjust resource: IO ports 0xa00-0xaff: Device or resource busy But at least it doesn't seem to be running around in tight circles at this point :-). System is a Dell Latitude CPxJ notebook that continues to work fine with 2.6.11 and older kernels. Any idea what changed between 2.6.11 and 2.6.12 that might be causing this problem? I can probably provide more info on request. Please post the output of lspci and lsmod as I'd like to know which kind of PCMCIA bridge is in your notebook. Dominik - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.12 vs. /sbin/cardmgr
Dominik Brodowski wrote: On Sat, Jul 09, 2005 at 12:12:17AM -0500, Bob Tracy wrote: (/sbin/cardmgr chewing up lots of CPU cycles with 2.6.12 kernel) Please post the output of lspci and lsmod as I'd like to know which kind of PCMCIA bridge is in your notebook. -- lspci -v -- 00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03) Flags: bus master, medium devsel, latency 32 Memory at f400 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 1.0 00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03) (prog-if 00 [Normal decode]) Flags: bus master, 66Mhz, medium devsel, latency 32 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: e000-efff Memory behind bridge: fc00-feff 00:03.0 CardBus bridge: Texas Instruments PCI1225 (rev 01) Subsystem: Dell Computer Corporation: Unknown device 00bb Flags: bus master, medium devsel, latency 168, IRQ 11 Memory at 1010 (32-bit, non-prefetchable) [size=4K] Bus: primary=00, secondary=02, subordinate=05, sec-latency=176 Memory window 0: 1040-107ff000 (prefetchable) Memory window 1: 1080-10bff000 I/O window 0: 4000-40ff I/O window 1: 4400-44ff 16-bit legacy interface ports at 0001 00:03.1 CardBus bridge: Texas Instruments PCI1225 (rev 01) Subsystem: Dell Computer Corporation: Unknown device 00bb Flags: bus master, medium devsel, latency 168, IRQ 11 Memory at 10101000 (32-bit, non-prefetchable) [size=4K] Bus: primary=00, secondary=06, subordinate=09, sec-latency=176 Memory window 0: 10c0-10fff000 (prefetchable) Memory window 1: 1100-113ff000 I/O window 0: 4800-48ff I/O window 1: 4c00-4cff 16-bit legacy interface ports at 0001 00:07.0 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02) Flags: bus master, medium devsel, latency 0 00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) (prog-if 80 [Master]) Flags: bus master, medium devsel, latency 32 I/O ports at 0860 [size=16] 00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI]) Flags: bus master, medium devsel, latency 32, IRQ 11 I/O ports at dce0 [size=32] 00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02) Flags: medium devsel, IRQ 9 00:08.0 Multimedia audio controller: ESS Technology ES1983S Maestro-3i PCI Audio Accelerator (rev 10) Subsystem: Dell Computer Corporation: Unknown device 00bb Flags: bus master, medium devsel, latency 32, IRQ 5 I/O ports at d800 [size=256] Memory at faffe000 (32-bit, non-prefetchable) [size=8K] Capabilities: [c0] Power Management version 2 01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64) (prog-if 00 [VGA]) Subsystem: Dell Computer Corporation: Unknown device 00bb Flags: bus master, stepping, medium devsel, latency 32, IRQ 11 Memory at fd00 (32-bit, non-prefetchable) [size=16M] I/O ports at ec00 [size=256] Memory at fcfff000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at unassigned [disabled] [size=128K] Capabilities: [50] AGP version 1.0 Capabilities: [5c] Power Management version 1 06:00.0 Ethernet controller: Galileo Technology Ltd.: Unknown device 1fa6 (rev 07) Subsystem: D-Link System Inc: Unknown device 3b08 Flags: bus master, 66Mhz, medium devsel, latency 168, IRQ 11 Memory at 1100 (32-bit, non-prefetchable) [size=64K] Memory at 1101 (32-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 2 -- lsmod -- Module Size Used by parport_pc 37252 1 lp 12132 0 parport39048 2 parport_pc,lp irda 132120 0 crc_ccitt 1984 1 irda snd_seq_oss37376 0 snd_seq_midi_event 8320 1 snd_seq_oss snd_seq61552 4 snd_seq_oss,snd_seq_midi_event snd_seq_device 8876 2 snd_seq_oss,snd_seq snd_pcm_oss62784 0 snd_mixer_oss 21440 1 snd_pcm_oss snd_maestro3 24836 0 snd_ac97_codec 85432 1 snd_maestro3 snd_pcm 107012 3 snd_pcm_oss,snd_maestro3,snd_ac97_codec snd_timer 27972 2 snd_seq,snd_pcm snd_page_alloc 10564 1 snd_pcm snd61060 9 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_maestro3,snd_ac97_codec,snd_pcm,snd_timer soundcore 10272 1 snd ide_cd 44196 0 cdrom 42752 1 ide_cd pcmcia 28552 2 yenta_socket 23720 3 rsrc_nonstatic 13952 1
2.6.12 vs. /sbin/cardmgr
I've got a Mandrake 10.0 system with a 2.6.12 kernel presently. Somewhere between 2.6.11 and 2.6.12, /sbin/cardmgr from the pcmcia-cs-3.2.5-3mdk package decided it needs to consume incredible amounts of CPU time when invoked the first time following a boot. You can definitely notice the load on the system. Stopping cardmgr requires a "kill -9": softer kills are ignored. Restarting cardmgr produces the following output: cardmgr[3731]: watching 2 sockets cardmgr[3731]: could not adjust resource: IO ports 0xc00-0xcff: Device or resource busy cardmgr[3731]: could not adjust resource: IO ports 0x100-0x4ff: Device or resource busy cardmgr[3731]: could not adjust resource: memory 0xc-0xf: Input/output error cardmgr[3731]: could not adjust resource: memory 0x6000-0x60ff: Input/output error cardmgr[3731]: could not adjust resource: memory 0xa000-0xa0ff: Input/output error cardmgr[3731]: could not adjust resource: IO ports 0x1000-0x1fff: Device or resource busy cardmgr[3731]: could not adjust resource: IO ports 0xa00-0xaff: Device or resource busy But at least it doesn't seem to be running around in tight circles at this point :-). System is a Dell Latitude CPxJ notebook that continues to work fine with 2.6.11 and older kernels. Any idea what changed between 2.6.11 and 2.6.12 that might be causing this problem? I can probably provide more info on request. As usual, thanks in advance. -- --- Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org [EMAIL PROTECTED] --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.12 vs. /sbin/cardmgr
I've got a Mandrake 10.0 system with a 2.6.12 kernel presently. Somewhere between 2.6.11 and 2.6.12, /sbin/cardmgr from the pcmcia-cs-3.2.5-3mdk package decided it needs to consume incredible amounts of CPU time when invoked the first time following a boot. You can definitely notice the load on the system. Stopping cardmgr requires a kill -9: softer kills are ignored. Restarting cardmgr produces the following output: cardmgr[3731]: watching 2 sockets cardmgr[3731]: could not adjust resource: IO ports 0xc00-0xcff: Device or resource busy cardmgr[3731]: could not adjust resource: IO ports 0x100-0x4ff: Device or resource busy cardmgr[3731]: could not adjust resource: memory 0xc-0xf: Input/output error cardmgr[3731]: could not adjust resource: memory 0x6000-0x60ff: Input/output error cardmgr[3731]: could not adjust resource: memory 0xa000-0xa0ff: Input/output error cardmgr[3731]: could not adjust resource: IO ports 0x1000-0x1fff: Device or resource busy cardmgr[3731]: could not adjust resource: IO ports 0xa00-0xaff: Device or resource busy But at least it doesn't seem to be running around in tight circles at this point :-). System is a Dell Latitude CPxJ notebook that continues to work fine with 2.6.11 and older kernels. Any idea what changed between 2.6.11 and 2.6.12 that might be causing this problem? I can probably provide more info on request. As usual, thanks in advance. -- --- Bob Tracy WTO + WIPO = DMCA? http://www.anti-dmca.org [EMAIL PROTECTED] --- - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
