* [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
@ 2003-04-23 5:47 DevilKin
2003-04-23 11:12 ` Felipe Alfaro Solana
0 siblings, 1 reply; 17+ messages in thread
From: DevilKin @ 2003-04-23 5:47 UTC (permalink / raw)
To: linux-kernel, devilkin-ml
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
Kernels 2.5.6[78] hang when the pcmcia yenta_socket is initialised.
The last message I get is this:
Apr 23 06:54:22 laptop kernel: Linux Kernel Card Services 3.1.22
Apr 23 06:54:22 laptop kernel: options: [pci] [cardbus] [pm]
Apr 23 06:54:22 laptop kernel: Intel PCIC probe: not found.
Apr 23 06:54:22 laptop kernel: PCI: Found IRQ 11 for device 00:03.0
Apr 23 06:54:22 laptop kernel: PCI: Sharing IRQ 11 with 00:03.1
Apr 23 06:54:22 laptop kernel: PCI: Sharing IRQ 11 with 00:07.2
Apr 23 06:54:22 laptop kernel: Yenta IRQ list 0698, PCI irq11
Apr 23 06:54:22 laptop kernel: Socket status: 30000020
Apr 23 06:54:22 laptop kernel: PCI: Found IRQ 11 for device 00:03.1
Apr 23 06:54:22 laptop kernel: PCI: Sharing IRQ 11 with 00:03.0
Apr 23 06:54:22 laptop kernel: PCI: Sharing IRQ 11 with 00:07.2
Apr 23 06:54:22 laptop kernel: Yenta IRQ list 0698, PCI irq11
Apr 23 06:54:23 laptop kernel: Socket status: 30000010
After this, the system becomes unresponsive. Reboot is possible using the
SysRq keys.
System information:
System:
Dell Latitude CPx J 650MHz - Pentium 3 650
Distribution:
Debian Unstable (Sid)
Hardware:
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 10000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
Memory window 0: 10400000-107ff000 (prefetchable)
Memory window 1: 10800000-10bff000
I/O window 0: 00001000-000010ff
I/O window 1: 00001400-000014ff
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 10001000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=06, subordinate=09, sec-latency=176
Memory window 0: 10c00000-10fff000 (prefetchable)
Memory window 1: 11000000-113ff000
I/O window 0: 00001800-000018ff
I/O window 1: 00001c00-00001cff
16-bit legacy interface ports at 0001
To reproduce: boot with any 2.5.6[78] kernel with pcmcia as modules, and have
it loaded through pcmcia-cs at bootup
It works fine on kernel 2.5.66.
DK
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+pijspuyeqyCEh60RAl/7AJwOq6hubHFvffLFVO6RJ+yttCGoZgCfU4zS
fOYYQnc7w12OKOe50rx8WuE=
=Wuuf
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-04-23 5:47 [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation DevilKin
@ 2003-04-23 11:12 ` Felipe Alfaro Solana
2003-04-23 12:54 ` DevilKin
0 siblings, 1 reply; 17+ messages in thread
From: Felipe Alfaro Solana @ 2003-04-23 11:12 UTC (permalink / raw)
To: DevilKin; +Cc: LKML, devilkin-ml
On Wed, 2003-04-23 at 07:47, DevilKin wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> Kernels 2.5.6[78] hang when the pcmcia yenta_socket is initialised.
>
> The last message I get is this:
>
> Apr 23 06:54:22 laptop kernel: Linux Kernel Card Services 3.1.22
> Apr 23 06:54:22 laptop kernel: options: [pci] [cardbus] [pm]
> Apr 23 06:54:22 laptop kernel: Intel PCIC probe: not found.
> Apr 23 06:54:22 laptop kernel: PCI: Found IRQ 11 for device 00:03.0
> Apr 23 06:54:22 laptop kernel: PCI: Sharing IRQ 11 with 00:03.1
> Apr 23 06:54:22 laptop kernel: PCI: Sharing IRQ 11 with 00:07.2
> Apr 23 06:54:22 laptop kernel: Yenta IRQ list 0698, PCI irq11
> Apr 23 06:54:22 laptop kernel: Socket status: 30000020
> Apr 23 06:54:22 laptop kernel: PCI: Found IRQ 11 for device 00:03.1
> Apr 23 06:54:22 laptop kernel: PCI: Sharing IRQ 11 with 00:03.0
> Apr 23 06:54:22 laptop kernel: PCI: Sharing IRQ 11 with 00:07.2
> Apr 23 06:54:22 laptop kernel: Yenta IRQ list 0698, PCI irq11
> Apr 23 06:54:23 laptop kernel: Socket status: 30000010
Download and apply the following:
http://patches.arm.linux.org.uk/pcmcia/pcmcia-1.diff
Also, the -mm kernel series starting with 2.5.67-mm4 do include this
patch. You can download -mm patches from
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5
--
Please AVOID sending me WORD, EXCEL or POWERPOINT attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
Linux Registered User #287198
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-04-23 11:12 ` Felipe Alfaro Solana
@ 2003-04-23 12:54 ` DevilKin
2003-04-23 14:23 ` Felipe Alfaro Solana
0 siblings, 1 reply; 17+ messages in thread
From: DevilKin @ 2003-04-23 12:54 UTC (permalink / raw)
To: Felipe Alfaro Solana; +Cc: LKML, devilkin-lkml
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 23 April 2003 13:12, Felipe Alfaro Solana wrote:
> Download and apply the following:
>
> http://patches.arm.linux.org.uk/pcmcia/pcmcia-1.diff
>
> Also, the -mm kernel series starting with 2.5.67-mm4 do include this
> patch. You can download -mm patches from
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5
This results in the following oops:
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
Intel PCIC probe: not found.
PCI: Found IRQ 11 for device 00:03.0
PCI: Sharing IRQ 11 with 00:03.1
PCI: Sharing IRQ 11 with 00:07.2
Yenta IRQ list 0698, PCI irq11
Socket status: 30000020
PCI: Found IRQ 11 for device 00:03.1
PCI: Sharing IRQ 11 with 00:03.0
PCI: Sharing IRQ 11 with 00:07.2
Yenta IRQ list 0698, PCI irq11
Socket status: 30000010
cs: sock ce519800 old smfunc d116d1a0 mask 0x0000004a pending 0x00000002
sockstate 0x00000000 status 0x00001880 delivering 0x00000002
cs: sock ce519800 new smfunc d116d280 mask 0x00000001 pending 0x00000002
sockstate 0x00000010
cs: sock ce519800 old smfunc d116d280 mask 0x00000001 pending 0x00000003
sockstate 0x00000010 status 0x00001880 delivering 0x00000001
cs: sock ce519800 new smfunc d116d480 mask 0x00000001 pending 0x00000002
sockstate 0x00008018
cs: sock ce519000 old smfunc d116d1a0 mask 0x0000004a pending 0x00000002
sockstate 0x00000000 status 0x000000b0 delivering 0x00000002
cs: sock ce519000 new smfunc d116d280 mask 0x00000001 pending 0x00000002
sockstate 0x00000010
cs: sock ce519000 old smfunc d116d280 mask 0x00000001 pending 0x00000003
sockstate 0x00000010 status 0x000000b0 delivering 0x00000001
cs: sock ce519000 new smfunc d116d480 mask 0x00000001 pending 0x00000002
sockstate 0x00000018
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x84f 0x868-0x86f
cs: IO port probe 0x0100-0x04ff: excluding 0x280-0x287 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: sock ce519800 old smfunc d116d480 mask 0x00000001 pending 0x00000023
sockstate 0x00008018 status 0x000019c0 delivering 0x00000001
cs: sock ce519800 new smfunc d116d580 mask 0x00000001 pending 0x00000022
sockstate 0x00008018
cs: sock ce519800 old smfunc d116d580 mask 0x00000001 pending 0x00000023
sockstate 0x00008018 status 0x000019c0 delivering 0x00000001
Unable to handle kernel paging request at virtual address d10545c0
printing eip:
c01b0368
*pde = 0fb66067
*pte = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c01b0368>] Not tainted
EFLAGS: 00010286
EIP is at pci_bus_match+0x18/0xb0
eax: 00000000 ebx: cef4dc00 ecx: d10545c0 edx: 00000000
esi: cef4dc4c edi: ffffffed ebp: c12d284c esp: ce479e74
ds: 007b es: 007b ss: 0068
Process pcmcia/0 (pid: 2203, threadinfo=ce478000 task=ce4df300)
Stack: d109edc8 c01d1abf cef4dc4c d109edc8 d109edf8 cef4dc4c c02d7ff8 c01d1b5f
cef4dc4c d109edc8 cef4dc4c c02d7fa0 cef4dc88 c01d1d24 cef4dc4c c0282ddf
c02de000 cef4dc4c 00000000 cef4dc88 c01d0ef0 cef4dc4c cef4dc00 cffd08b4
Call Trace:
[<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
[<c01d1abf>] bus_match+0x2f/0x80
[<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
[<d109edf8>] m3_pci_driver+0x58/0xa0 [maestro3]
[<c01d1b5f>] device_attach+0x4f/0x90
[<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
[<c01d1d24>] bus_add_device+0x64/0xb0
[<c01d0ef0>] device_add+0xd0/0x110
[<c01aca6b>] pci_bus_add_devices+0x4b/0xb0
[<d1170e2d>] cb_alloc+0xad/0xf0 [pcmcia_core]
[<c011a608>] printk+0x118/0x180
[<d116d6d1>] state_wait_ready+0x151/0x260 [pcmcia_core]
[<d116dbf1>] sm_do_work+0xa1/0xf0 [pcmcia_core]
[<c012867f>] worker_thread+0x1ff/0x2e0
[<d116db50>] sm_do_work+0x0/0xf0 [pcmcia_core]
[<c01168f0>] default_wake_function+0x0/0x20
[<c01091c2>] ret_from_fork+0x6/0x14
[<c01168f0>] default_wake_function+0x0/0x20
[<c0128480>] worker_thread+0x0/0x2e0
[<c01071dd>] kernel_thread_helper+0x5/0x18
Code: 8b 11 85 d2 74 7a 89 f6 83 fa ff 74 2b 0f b7 43 24 39 c2 74
DK
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+poz3puyeqyCEh60RAmgoAJ40zorNV1oRGbmy6hngz6LE29T/sACfbiro
+tUYPVecqFk8PBWN6njOBDI=
=ubew
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-04-23 12:54 ` DevilKin
@ 2003-04-23 14:23 ` Felipe Alfaro Solana
2003-04-23 18:50 ` DevilKin-LKML
0 siblings, 1 reply; 17+ messages in thread
From: Felipe Alfaro Solana @ 2003-04-23 14:23 UTC (permalink / raw)
To: DevilKin; +Cc: LKML
On Wed, 2003-04-23 at 14:54, DevilKin wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wednesday 23 April 2003 13:12, Felipe Alfaro Solana wrote:
> > Download and apply the following:
> >
> > http://patches.arm.linux.org.uk/pcmcia/pcmcia-1.diff
> >
> > Also, the -mm kernel series starting with 2.5.67-mm4 do include this
> > patch. You can download -mm patches from
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5
>
> This results in the following oops:
>
> Linux Kernel Card Services 3.1.22
> options: [pci] [cardbus] [pm]
> Intel PCIC probe: not found.
> PCI: Found IRQ 11 for device 00:03.0
> PCI: Sharing IRQ 11 with 00:03.1
> PCI: Sharing IRQ 11 with 00:07.2
> Yenta IRQ list 0698, PCI irq11
> Socket status: 30000020
> PCI: Found IRQ 11 for device 00:03.1
> PCI: Sharing IRQ 11 with 00:03.0
> PCI: Sharing IRQ 11 with 00:07.2
> Yenta IRQ list 0698, PCI irq11
> Socket status: 30000010
> cs: sock ce519800 old smfunc d116d1a0 mask 0x0000004a pending 0x00000002
> sockstate 0x00000000 status 0x00001880 delivering 0x00000002
> cs: sock ce519800 new smfunc d116d280 mask 0x00000001 pending 0x00000002
> sockstate 0x00000010
> cs: sock ce519800 old smfunc d116d280 mask 0x00000001 pending 0x00000003
> sockstate 0x00000010 status 0x00001880 delivering 0x00000001
> cs: sock ce519800 new smfunc d116d480 mask 0x00000001 pending 0x00000002
> sockstate 0x00008018
> cs: sock ce519000 old smfunc d116d1a0 mask 0x0000004a pending 0x00000002
> sockstate 0x00000000 status 0x000000b0 delivering 0x00000002
> cs: sock ce519000 new smfunc d116d280 mask 0x00000001 pending 0x00000002
> sockstate 0x00000010
> cs: sock ce519000 old smfunc d116d280 mask 0x00000001 pending 0x00000003
> sockstate 0x00000010 status 0x000000b0 delivering 0x00000001
> cs: sock ce519000 new smfunc d116d480 mask 0x00000001 pending 0x00000002
> sockstate 0x00000018
> cs: IO port probe 0x0c00-0x0cff: clean.
> cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x84f 0x868-0x86f
> cs: IO port probe 0x0100-0x04ff: excluding 0x280-0x287 0x4d0-0x4d7
> cs: IO port probe 0x0a00-0x0aff: clean.
> cs: sock ce519800 old smfunc d116d480 mask 0x00000001 pending 0x00000023
> sockstate 0x00008018 status 0x000019c0 delivering 0x00000001
> cs: sock ce519800 new smfunc d116d580 mask 0x00000001 pending 0x00000022
> sockstate 0x00008018
> cs: sock ce519800 old smfunc d116d580 mask 0x00000001 pending 0x00000023
> sockstate 0x00008018 status 0x000019c0 delivering 0x00000001
> Unable to handle kernel paging request at virtual address d10545c0
> printing eip:
> c01b0368
> *pde = 0fb66067
> *pte = 00000000
> Oops: 0000 [#1]
> CPU: 0
> EIP: 0060:[<c01b0368>] Not tainted
> EFLAGS: 00010286
> EIP is at pci_bus_match+0x18/0xb0
> eax: 00000000 ebx: cef4dc00 ecx: d10545c0 edx: 00000000
> esi: cef4dc4c edi: ffffffed ebp: c12d284c esp: ce479e74
> ds: 007b es: 007b ss: 0068
> Process pcmcia/0 (pid: 2203, threadinfo=ce478000 task=ce4df300)
> Stack: d109edc8 c01d1abf cef4dc4c d109edc8 d109edf8 cef4dc4c c02d7ff8 c01d1b5f
> cef4dc4c d109edc8 cef4dc4c c02d7fa0 cef4dc88 c01d1d24 cef4dc4c c0282ddf
> c02de000 cef4dc4c 00000000 cef4dc88 c01d0ef0 cef4dc4c cef4dc00 cffd08b4
> Call Trace:
> [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
> [<c01d1abf>] bus_match+0x2f/0x80
> [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
> [<d109edf8>] m3_pci_driver+0x58/0xa0 [maestro3]
> [<c01d1b5f>] device_attach+0x4f/0x90
> [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
> [<c01d1d24>] bus_add_device+0x64/0xb0
> [<c01d0ef0>] device_add+0xd0/0x110
> [<c01aca6b>] pci_bus_add_devices+0x4b/0xb0
> [<d1170e2d>] cb_alloc+0xad/0xf0 [pcmcia_core]
> [<c011a608>] printk+0x118/0x180
> [<d116d6d1>] state_wait_ready+0x151/0x260 [pcmcia_core]
> [<d116dbf1>] sm_do_work+0xa1/0xf0 [pcmcia_core]
> [<c012867f>] worker_thread+0x1ff/0x2e0
> [<d116db50>] sm_do_work+0x0/0xf0 [pcmcia_core]
> [<c01168f0>] default_wake_function+0x0/0x20
> [<c01091c2>] ret_from_fork+0x6/0x14
> [<c01168f0>] default_wake_function+0x0/0x20
> [<c0128480>] worker_thread+0x0/0x2e0
> [<c01071dd>] kernel_thread_helper+0x5/0x18
>
> Code: 8b 11 85 d2 74 7a 89 f6 83 fa ff 74 2b 0f b7 43 24 39 c2 74
>
> DK
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQE+poz3puyeqyCEh60RAmgoAJ40zorNV1oRGbmy6hngz6LE29T/sACfbiro
> +tUYPVecqFk8PBWN6njOBDI=
> =ubew
> -----END PGP SIGNATURE-----
Could you please try again with this individual and newer PCMCIA patch
at http://patches.arm.linux.org.uk/pcmcia-20030421.diff? If you prefer,
you can also try with 2.5.68-mm2 which includes the mentioned patch.
--
Please AVOID sending me WORD, EXCEL or POWERPOINT attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
Linux Registered User #287198
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-04-23 14:23 ` Felipe Alfaro Solana
@ 2003-04-23 18:50 ` DevilKin-LKML
2003-04-23 19:43 ` Russell King
2003-04-23 22:14 ` Felipe Alfaro Solana
0 siblings, 2 replies; 17+ messages in thread
From: DevilKin-LKML @ 2003-04-23 18:50 UTC (permalink / raw)
To: Felipe Alfaro Solana; +Cc: LKML, devilkin-lkml
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 23 April 2003 16:23, Felipe Alfaro Solana wrote:
> Could you please try again with this individual and newer PCMCIA patch
> at http://patches.arm.linux.org.uk/pcmcia-20030421.diff? If you prefer,
> you can also try with 2.5.68-mm2 which includes the mentioned patch.
Tried the patch against vanilla 2.5.68, gives me this oops:
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
Intel PCIC probe: not found.
PCI: Found IRQ 11 for device 00:03.0
PCI: Sharing IRQ 11 with 00:03.1
PCI: Sharing IRQ 11 with 00:07.2
Yenta IRQ list 0698, PCI irq11
Socket status: 30000020
PCI: Found IRQ 11 for device 00:03.1
PCI: Sharing IRQ 11 with 00:03.0
PCI: Sharing IRQ 11 with 00:07.2
Yenta IRQ list 0698, PCI irq11
Socket status: 30000010
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x84f 0x868-0x86f
cs: IO port probe 0x0100-0x04ff: excluding 0x280-0x287 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
Unable to handle kernel paging request at virtual address d10545c0
printing eip:
c01b0368
*pde = 0fb66067
*pte = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c01b0368>] Not tainted
EFLAGS: 00010286
EIP is at pci_bus_match+0x18/0xb0
eax: 00000000 ebx: cf2a8800 ecx: d10545c0 edx: 00000000
esi: cf2a884c edi: ffffffed ebp: c12d284c esp: ce591e88
ds: 007b es: 007b ss: 0068
Process pcmcia/0 (pid: 388, threadinfo=ce590000 task=ce6f7300)
Stack: d109edc8 c01d1abf cf2a884c d109edc8 d109edf8 cf2a884c c02d7ff8 c01d1b5f
cf2a884c d109edc8 cf2a884c c02d7fa0 cf2a8888 c01d1d24 cf2a884c c0282ddf
c02de000 cf2a884c 00000000 cf2a8888 c01d0ef0 cf2a884c cf2a8800 cffd08b4
Call Trace:
[<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
[<c01d1abf>] bus_match+0x2f/0x80
[<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
[<d109edf8>] m3_pci_driver+0x58/0xa0 [maestro3]
[<c01d1b5f>] device_attach+0x4f/0x90
[<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
[<c01d1d24>] bus_add_device+0x64/0xb0
[<c01d0ef0>] device_add+0xd0/0x110
[<c01aca6b>] pci_bus_add_devices+0x4b/0xb0
[<d116fdad>] cb_alloc+0xad/0xf0 [pcmcia_core]
[<d115a17e>] pci_set_socket+0x3e/0x40 [yenta_socket]
[<d115d140>] +0x0/0x5a0 [yenta_socket]
[<d116c6d1>] state_wait_ready+0x151/0x260 [pcmcia_core]
[<d116b9fa>] get_socket_status+0x1a/0x20 [pcmcia_core]
[<d116cbae>] sm_do_work+0x5e/0x70 [pcmcia_core]
[<c012867f>] worker_thread+0x1ff/0x2e0
[<d116cb50>] sm_do_work+0x0/0x70 [pcmcia_core]
[<c01168f0>] default_wake_function+0x0/0x20
[<c01091c2>] ret_from_fork+0x6/0x14
[<c01168f0>] default_wake_function+0x0/0x20
[<c0128480>] worker_thread+0x0/0x2e0
[<c01071dd>] kernel_thread_helper+0x5/0x18
Code: 8b 11 85 d2 74 7a 89 f6 83 fa ff 74 2b 0f b7 43 24 39 c2 74
DK
- --
San Francisco isn't what it used to be, and it never was.
-- Herb Caen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+puCBpuyeqyCEh60RAoj+AJ97jlGV25k0tMzJFx7SIhRmhVjyKgCeMBRr
1QyJMJciTYIcNm6odgu+CZk=
=HVXA
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-04-23 18:50 ` DevilKin-LKML
@ 2003-04-23 19:43 ` Russell King
2003-04-24 7:40 ` DevilKin-LKML
2003-04-23 22:14 ` Felipe Alfaro Solana
1 sibling, 1 reply; 17+ messages in thread
From: Russell King @ 2003-04-23 19:43 UTC (permalink / raw)
To: DevilKin-LKML; +Cc: Felipe Alfaro Solana, LKML
On Wed, Apr 23, 2003 at 08:50:39PM +0200, DevilKin-LKML wrote:
> Unable to handle kernel paging request at virtual address d10545c0
> printing eip:
> c01b0368
> *pde = 0fb66067
> *pte = 00000000
> Oops: 0000 [#1]
> CPU: 0
> EIP: 0060:[<c01b0368>] Not tainted
> EFLAGS: 00010286
> EIP is at pci_bus_match+0x18/0xb0
> eax: 00000000 ebx: cf2a8800 ecx: d10545c0 edx: 00000000
> esi: cf2a884c edi: ffffffed ebp: c12d284c esp: ce591e88
> ds: 007b es: 007b ss: 0068
> Process pcmcia/0 (pid: 388, threadinfo=ce590000 task=ce6f7300)
> Stack: d109edc8 c01d1abf cf2a884c d109edc8 d109edf8 cf2a884c c02d7ff8 c01d1b5f
> cf2a884c d109edc8 cf2a884c c02d7fa0 cf2a8888 c01d1d24 cf2a884c c0282ddf
> c02de000 cf2a884c 00000000 cf2a8888 c01d0ef0 cf2a884c cf2a8800 cffd08b4
> Call Trace:
> [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
> [<c01d1abf>] bus_match+0x2f/0x80
> [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
> [<d109edf8>] m3_pci_driver+0x58/0xa0 [maestro3]
> [<c01d1b5f>] device_attach+0x4f/0x90
> [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
I don't think this is PCMCIA related - something else is going on here.
My guess is we're trying to locate a driver for the card, and we get to
maestro3. This works as expected, but the next driver on the chain
seems to be a module which was may have been removed but which left
its pci_driver structure behind (at 0xd10545c0.)
Decoding the attached x86 opcodes didn't reveal anything interesting to
me.
Anyone else?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-04-23 19:43 ` Russell King
@ 2003-04-24 7:40 ` DevilKin-LKML
2003-04-24 7:57 ` Russell King
0 siblings, 1 reply; 17+ messages in thread
From: DevilKin-LKML @ 2003-04-24 7:40 UTC (permalink / raw)
To: Russell King; +Cc: Felipe Alfaro Solana, LKML, devilkin-lkml
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 23 April 2003 21:43, Russell King wrote:
> On Wed, Apr 23, 2003 at 08:50:39PM +0200, DevilKin-LKML wrote:
> > Unable to handle kernel paging request at virtual address d10545c0
> > printing eip:
> > c01b0368
> > *pde = 0fb66067
> > *pte = 00000000
> > Oops: 0000 [#1]
> > CPU: 0
> > EIP: 0060:[<c01b0368>] Not tainted
> > EFLAGS: 00010286
> > EIP is at pci_bus_match+0x18/0xb0
> > eax: 00000000 ebx: cf2a8800 ecx: d10545c0 edx: 00000000
> > esi: cf2a884c edi: ffffffed ebp: c12d284c esp: ce591e88
> > ds: 007b es: 007b ss: 0068
> > Process pcmcia/0 (pid: 388, threadinfo=ce590000 task=ce6f7300)
> > Stack: d109edc8 c01d1abf cf2a884c d109edc8 d109edf8 cf2a884c c02d7ff8
> > c01d1b5f cf2a884c d109edc8 cf2a884c c02d7fa0 cf2a8888 c01d1d24 cf2a884c
> > c0282ddf c02de000 cf2a884c 00000000 cf2a8888 c01d0ef0 cf2a884c cf2a8800
> > cffd08b4 Call Trace:
> > [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
> > [<c01d1abf>] bus_match+0x2f/0x80
> > [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
> > [<d109edf8>] m3_pci_driver+0x58/0xa0 [maestro3]
> > [<c01d1b5f>] device_attach+0x4f/0x90
> > [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
>
> I don't think this is PCMCIA related - something else is going on here.
>
> My guess is we're trying to locate a driver for the card, and we get to
> maestro3. This works as expected, but the next driver on the chain
> seems to be a module which was may have been removed but which left
> its pci_driver structure behind (at 0xd10545c0.)
I have a Maestro3 in the laptop (which is also why the module is loaded), but
I never unload it once it's loaded at bootup...
Anything else I can try?
Jan
- --
To be sure of hitting the target, shoot first and, whatever you hit,
call it the target.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+p5TlpuyeqyCEh60RAuAuAJ9WByWWm+pwMNT3HrarHxiW/6HfKACeMOPZ
2d2+dnUbdZhDG2A3vfVNHoI=
=rw/c
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-04-24 7:40 ` DevilKin-LKML
@ 2003-04-24 7:57 ` Russell King
2003-04-24 10:06 ` DevilKin
2003-05-05 8:51 ` [FIXED 2.5.69] " DevilKin
0 siblings, 2 replies; 17+ messages in thread
From: Russell King @ 2003-04-24 7:57 UTC (permalink / raw)
To: DevilKin-LKML; +Cc: Felipe Alfaro Solana, LKML
On Thu, Apr 24, 2003 at 09:40:18AM +0200, DevilKin-LKML wrote:
> I have a Maestro3 in the laptop (which is also why the module is loaded), but
> I never unload it once it's loaded at bootup...
>
> Anything else I can try?
Maybe looking in /sysfs/bus/pci/drivers before inserting the card
(this may cause an oops as well - if so, it confirms my suspicion.)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-04-24 7:57 ` Russell King
@ 2003-04-24 10:06 ` DevilKin
2003-04-24 10:11 ` Russell King
2003-04-24 10:13 ` DevilKin
2003-05-05 8:51 ` [FIXED 2.5.69] " DevilKin
1 sibling, 2 replies; 17+ messages in thread
From: DevilKin @ 2003-04-24 10:06 UTC (permalink / raw)
To: Russell King, devilkin-lkml; +Cc: Felipe Alfaro Solana, LKML
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 24 April 2003 09:57, Russell King wrote:
> On Thu, Apr 24, 2003 at 09:40:18AM +0200, DevilKin-LKML wrote:
> > I have a Maestro3 in the laptop (which is also why the module is loaded),
> > but I never unload it once it's loaded at bootup...
> >
> > Anything else I can try?
>
> Maybe looking in /sysfs/bus/pci/drivers before inserting the card
> (this may cause an oops as well - if so, it confirms my suspicion.)
Uh... The Maestro3 is integrated on the motherboard, so that's kinda hard.
I have 1 pcmcia card and 1 cardbus card in the system (see below).
I have tested the booting with no cards, than it boots fine. Booting with only
the pcmcia card also works fine, so It's really the cardbus card that seems to
throw the system into an unstable state.
laptop:/home/devilkin# cardctl ident
Socket 0:
product info: "3Com Corporation", "3CCFE575BT", "LAN Cardbus Card", "001"
manfid: 0x0101, 0x5157
function: 6 (network)
Socket 1:
product info: "Psion Dacom", "Gold Card Global 56K+Fax", "56K+Fax", "V8.25"
manfid: 0x016c, 0x0005
function: 2 (serial)
Jan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+p7cvpuyeqyCEh60RAtLVAJwOVfwwZ0RyTG5UwqprhYK2yibtlgCfbWRP
v0glplXaF6gJbQ+83/bqS/k=
=Au0c
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-04-24 10:06 ` DevilKin
@ 2003-04-24 10:11 ` Russell King
2003-04-24 10:16 ` DevilKin
2003-04-24 10:13 ` DevilKin
1 sibling, 1 reply; 17+ messages in thread
From: Russell King @ 2003-04-24 10:11 UTC (permalink / raw)
To: DevilKin; +Cc: Felipe Alfaro Solana, LKML
On Thu, Apr 24, 2003 at 12:06:37PM +0200, DevilKin wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thursday 24 April 2003 09:57, Russell King wrote:
> > Maybe looking in /sysfs/bus/pci/drivers before inserting the card
> > (this may cause an oops as well - if so, it confirms my suspicion.)
>
> Uh... The Maestro3 is integrated on the motherboard, so that's kinda hard.
Sorry, I meant booting without the cardbus card inserted, then looking
at /sysfs/bus/pci/drivers.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-04-24 10:11 ` Russell King
@ 2003-04-24 10:16 ` DevilKin
0 siblings, 0 replies; 17+ messages in thread
From: DevilKin @ 2003-04-24 10:16 UTC (permalink / raw)
To: Russell King, devilkin-lkml; +Cc: Felipe Alfaro Solana, LKML
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 24 April 2003 12:11, Russell King wrote:
> On Thu, Apr 24, 2003 at 12:06:37PM +0200, DevilKin wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Thursday 24 April 2003 09:57, Russell King wrote:
> > > Maybe looking in /sysfs/bus/pci/drivers before inserting the card
> > > (this may cause an oops as well - if so, it confirms my suspicion.)
> >
> > Uh... The Maestro3 is integrated on the motherboard, so that's kinda
> > hard.
>
> Sorry, I meant booting without the cardbus card inserted, then looking
> at /sysfs/bus/pci/drivers.
devilkin@laptop:~$ tree /sys/bus/pci/drivers/
/sys/bus/pci/drivers/
|-- PIIX IDE
| `-- 00:07.1 -> ../../../../devices/pci0/00:07.1
|-- cardbus
| |-- 00:03.0 -> ../../../../devices/pci0/00:03.0
| `-- 00:03.1 -> ../../../../devices/pci0/00:03.1
|-- ess_m3_audio
| `-- 00:08.0 -> ../../../../devices/pci0/00:08.0
|-- parport_pc
|-- serial
`-- uhci-hcd
`-- 00:07.2 -> ../../../../devices/pci0/00:07.2
Jan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+p7l1puyeqyCEh60RAkK0AJ48w7l9nl93DpKbQAldI7Q1nsMfkgCghNiP
IzwpmcKOxgGytMG+OQP20RI=
=SnTJ
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-04-24 10:06 ` DevilKin
2003-04-24 10:11 ` Russell King
@ 2003-04-24 10:13 ` DevilKin
1 sibling, 0 replies; 17+ messages in thread
From: DevilKin @ 2003-04-24 10:13 UTC (permalink / raw)
To: Russell King, devilkin-lkml; +Cc: Felipe Alfaro Solana, LKML
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 24 April 2003 12:06, DevilKin wrote:
> Uh... The Maestro3 is integrated on the motherboard, so that's kinda hard.
>
> I have 1 pcmcia card and 1 cardbus card in the system (see below).
> I have tested the booting with no cards, than it boots fine. Booting with
> only the pcmcia card also works fine, so It's really the cardbus card that
> seems to throw the system into an unstable state.
>
Forgot to mention that inserting the cardbus card afterwards and modprobe'ing
the module then (3c59x) works ok too. Its only during the detection that
something seems to go wrong.
Jan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+p7i+puyeqyCEh60RAvpqAJ4nT5C26gAzEKmp18wqArh7cIjf4gCeP116
mir+3C9x7idsfJpnbDdrDpI=
=5vOg
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 17+ messages in thread
* [FIXED 2.5.69] Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-04-24 7:57 ` Russell King
2003-04-24 10:06 ` DevilKin
@ 2003-05-05 8:51 ` DevilKin
2003-05-06 23:48 ` Matthew Harrell
1 sibling, 1 reply; 17+ messages in thread
From: DevilKin @ 2003-05-05 8:51 UTC (permalink / raw)
To: LKML
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Just reporting that this now works fine under 2.5.69. Whatever the problem,
it's definitely gone now.
DK
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+tiX5puyeqyCEh60RAvk1AJ9Qvygxk+70PFSKSSLKTgUi2mWmJwCaAjf0
5AR6Cz0LF6fC9g6Nd5t2eP8=
=o4WM
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [FIXED 2.5.69] Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-05-05 8:51 ` [FIXED 2.5.69] " DevilKin
@ 2003-05-06 23:48 ` Matthew Harrell
2003-05-07 5:19 ` DevilKin
0 siblings, 1 reply; 17+ messages in thread
From: Matthew Harrell @ 2003-05-06 23:48 UTC (permalink / raw)
To: DevilKin; +Cc: Kernel List
Was this one you reported - I didn't see this one.
I still get a hang on any 2.5.50+ kernel when I load yenta and have ACPI
turned on. It locks solid about three seconds after loading the module
>
> Just reporting that this now works fine under 2.5.69. Whatever the problem,
> it's definitely gone now.
>
--
Matthew Harrell Preserve wildlife --
Bit Twiddlers, Inc. pickle a squirrel today!
mharrell@bittwiddlers.com
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [FIXED 2.5.69] Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-05-06 23:48 ` Matthew Harrell
@ 2003-05-07 5:19 ` DevilKin
0 siblings, 0 replies; 17+ messages in thread
From: DevilKin @ 2003-05-07 5:19 UTC (permalink / raw)
To: Matthew Harrell, Matthew Harrell; +Cc: Kernel List
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 07 May 2003 01:48, Matthew Harrell wrote:
> Was this one you reported - I didn't see this one.
It was the fact that when I booted my system with my 3com cardbus NIC inserted
in the slot it would oops, giving me a non-working pcmcia/cardbus system.
Booting without the card worked fine, and inserting the card afterwards also
worked great.
thread is here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=105107713129722&w=2
>
> I still get a hang on any 2.5.50+ kernel when I load yenta and have ACPI
> turned on. It locks solid about three seconds after loading the module
>
Ah. I don't use ACPI, because well... it caused me more pain than it helped me
in the past, in both OS' on my system (being Linux and win2k)
Jan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+uJdQpuyeqyCEh60RAv/oAKCAUsots5uqvrL0O3dsrBGVXJ9icwCfQS/c
H6BRfG+uFkYWWsFQL8SJsSs=
=cGpw
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
2003-04-23 18:50 ` DevilKin-LKML
2003-04-23 19:43 ` Russell King
@ 2003-04-23 22:14 ` Felipe Alfaro Solana
1 sibling, 0 replies; 17+ messages in thread
From: Felipe Alfaro Solana @ 2003-04-23 22:14 UTC (permalink / raw)
To: DevilKin-LKML; +Cc: LKML
On Wed, 2003-04-23 at 20:50, DevilKin-LKML wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wednesday 23 April 2003 16:23, Felipe Alfaro Solana wrote:
> > Could you please try again with this individual and newer PCMCIA patch
> > at http://patches.arm.linux.org.uk/pcmcia-20030421.diff? If you prefer,
> > you can also try with 2.5.68-mm2 which includes the mentioned patch.
>
> Tried the patch against vanilla 2.5.68, gives me this oops
>
> Linux Kernel Card Services 3.1.22
> options: [pci] [cardbus] [pm]
> Intel PCIC probe: not found.
> PCI: Found IRQ 11 for device 00:03.0
> PCI: Sharing IRQ 11 with 00:03.1
> PCI: Sharing IRQ 11 with 00:07.2
> Yenta IRQ list 0698, PCI irq11
> Socket status: 30000020
> PCI: Found IRQ 11 for device 00:03.1
> PCI: Sharing IRQ 11 with 00:03.0
> PCI: Sharing IRQ 11 with 00:07.2
> Yenta IRQ list 0698, PCI irq11
> Socket status: 30000010
> cs: IO port probe 0x0c00-0x0cff: clean.
> cs: IO port probe 0x0800-0x08ff: excluding 0x800-0x84f 0x868-0x86f
> cs: IO port probe 0x0100-0x04ff: excluding 0x280-0x287 0x4d0-0x4d7
> cs: IO port probe 0x0a00-0x0aff: clean.
> Unable to handle kernel paging request at virtual address d10545c0
> printing eip:
> c01b0368
> *pde = 0fb66067
> *pte = 00000000
> Oops: 0000 [#1]
> CPU: 0
> EIP: 0060:[<c01b0368>] Not tainted
> EFLAGS: 00010286
> EIP is at pci_bus_match+0x18/0xb0
> eax: 00000000 ebx: cf2a8800 ecx: d10545c0 edx: 00000000
> esi: cf2a884c edi: ffffffed ebp: c12d284c esp: ce591e88
> ds: 007b es: 007b ss: 0068
> Process pcmcia/0 (pid: 388, threadinfo=ce590000 task=ce6f7300)
> Stack: d109edc8 c01d1abf cf2a884c d109edc8 d109edf8 cf2a884c c02d7ff8 c01d1b5f
> cf2a884c d109edc8 cf2a884c c02d7fa0 cf2a8888 c01d1d24 cf2a884c c0282ddf
> c02de000 cf2a884c 00000000 cf2a8888 c01d0ef0 cf2a884c cf2a8800 cffd08b4
> Call Trace:
> [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
> [<c01d1abf>] bus_match+0x2f/0x80
> [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
> [<d109edf8>] m3_pci_driver+0x58/0xa0 [maestro3]
> [<c01d1b5f>] device_attach+0x4f/0x90
> [<d109edc8>] m3_pci_driver+0x28/0xa0 [maestro3]
> [<c01d1d24>] bus_add_device+0x64/0xb0
> [<c01d0ef0>] device_add+0xd0/0x110
> [<c01aca6b>] pci_bus_add_devices+0x4b/0xb0
> [<d116fdad>] cb_alloc+0xad/0xf0 [pcmcia_core]
> [<d115a17e>] pci_set_socket+0x3e/0x40 [yenta_socket]
> [<d115d140>] +0x0/0x5a0 [yenta_socket]
> [<d116c6d1>] state_wait_ready+0x151/0x260 [pcmcia_core]
> [<d116b9fa>] get_socket_status+0x1a/0x20 [pcmcia_core]
> [<d116cbae>] sm_do_work+0x5e/0x70 [pcmcia_core]
> [<c012867f>] worker_thread+0x1ff/0x2e0
> [<d116cb50>] sm_do_work+0x0/0x70 [pcmcia_core]
> [<c01168f0>] default_wake_function+0x0/0x20
> [<c01091c2>] ret_from_fork+0x6/0x14
> [<c01168f0>] default_wake_function+0x0/0x20
> [<c0128480>] worker_thread+0x0/0x2e0
> [<c01071dd>] kernel_thread_helper+0x5/0x18
>
> Code: 8b 11 85 d2 74 7a 89 f6 83 fa ff 74 2b 0f b7 43 24 39 c2 74
>
Don't know what the device "M3" is. This falls out of my knowledge...
Russell, Andrew, someone?
--
Please AVOID sending me WORD, EXCEL or POWERPOINT attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
Linux Registered User #287198
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [FIXED 2.5.69] Re: [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation
@ 2003-05-07 12:34 Matthew Harrell
0 siblings, 0 replies; 17+ messages in thread
From: Matthew Harrell @ 2003-05-07 12:34 UTC (permalink / raw)
To: Kernel List
: It was the fact that when I booted my system with my 3com cardbus NIC inserted
: in the slot it would oops, giving me a non-working pcmcia/cardbus system.
:
: Booting without the card worked fine, and inserting the card afterwards also
: worked great.
:
: thread is here:
:
: http://marc.theaimsgroup.com/?l=linux-kernel&m=105107713129722&w=2
Oh, mine's different. Total lockup with no messages. Starts a few seconds
after the yenta module is loaded. I think it occurs during the yenta probe
but I haven't been able to prove that yet.
: Ah. I don't use ACPI, because well... it caused me more pain than it helped me
: in the past, in both OS' on my system (being Linux and win2k)
Yeah, it's a pain but this laptop no longer has APM so I need some way to read
my batteries and soft power the system off. But, if it weren't for the
batteries I wouldn't bother because it is a real pain to deal with
--
Matthew Harrell I love defenseless animals,
Bit Twiddlers, Inc. especially in a good gravy.
mharrell@bittwiddlers.com
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2003-05-07 12:23 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-23 5:47 [2.5.67 - 2.5.68] Hangs on pcmcia yenta_socket initialisation DevilKin
2003-04-23 11:12 ` Felipe Alfaro Solana
2003-04-23 12:54 ` DevilKin
2003-04-23 14:23 ` Felipe Alfaro Solana
2003-04-23 18:50 ` DevilKin-LKML
2003-04-23 19:43 ` Russell King
2003-04-24 7:40 ` DevilKin-LKML
2003-04-24 7:57 ` Russell King
2003-04-24 10:06 ` DevilKin
2003-04-24 10:11 ` Russell King
2003-04-24 10:16 ` DevilKin
2003-04-24 10:13 ` DevilKin
2003-05-05 8:51 ` [FIXED 2.5.69] " DevilKin
2003-05-06 23:48 ` Matthew Harrell
2003-05-07 5:19 ` DevilKin
2003-04-23 22:14 ` Felipe Alfaro Solana
2003-05-07 12:34 [FIXED 2.5.69] " Matthew Harrell
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).