Gentoo Archives: gentoo-user-de

From: Sebastian van de Meer | Mobil <kernel-error-mobil@××××××××××××.de>
To: gentoo-user-de@l.g.o
Subject: Re: [gentoo-user-de] Seit Kernel 2.6.14 Probleme mit PCMCIA
Date: Mon, 30 Jan 2006 14:22:05
Message-Id: 200601301518.47942.kernel-error-mobil@kernel-error.de
In Reply to: [gentoo-user-de] Seit Kernel 2.6.14 Probleme mit PCMCIA by Sebastian van de Meer | Mobil
1 Hallo zusammen,
2
3 schieben ist ja so nicht meine Art. Nur stehe ich immer noch auf dem Schlauch.
4
5 Keine Ideen?
6
7 Beste Grüße und Dank.
8
9
10 S. van de Meer
11 Am Mittwoch, 14. Dezember 2005 17:48 schrieb Sebastian van de Meer | Mobil:
12 > Hallo zusammen,
13 >
14 > ich habe vor kurzem auf von Kernel 2.6.12 auf den 2.6.14 gewechselt.
15 >
16 > Den Kernel habe ich wie immer von Hand konfiguriert. Wirklich geändert habe
17 > ich an der Konfiguration aber nichts. Nur halt make oldconfig...
18 >
19 > Laufen tut alles auf einem Fujitsu-Siemens E7110.
20 >
21 > Alles klappt, bis zum einstecken eine PCMCIA-Karte, super. Stecke ich eine
22 > ein, egal welche und egal was, erbricht sich folgendes in meine Logs und
23 > die Konsole:
24 >
25 > ####################################################
26 >
27 > Dec 14 17:30:22 ErrorLap cs: memory probe 0x0c0000-0x0fffff: excluding
28 > 0xc0000-0xcffff 0xdc000-0xfffff
29 > Dec 14 17:30:22 ErrorLap cs: memory probe 0x60000000-0x60ffffff: clean.
30 > Dec 14 17:30:22 ErrorLap cs: memory probe 0xa0000000-0xa0ffffff: clean.
31 > Dec 14 17:30:22 ErrorLap cs: memory probe 0xe8200000-0xe82fffff: excluding
32 > 0xe8200000-0xe820ffff
33 > Dec 14 17:30:22 ErrorLap cs: memory probe 0xf8000000-0xf80fffff: excluding
34 > 0xf8000000-0xf80fffff
35 > Dec 14 17:30:22 ErrorLap cardmgr[7037]: socket 0: 3Com Bluetooth PC Card
36 > Dec 14 17:30:22 ErrorLap bt3c_interrupt: Call of irq 11 for unknown device
37 > Dec 14 17:30:22 ErrorLap bt3c_interrupt: Call of irq 11 for unknown device
38 > Dec 14 17:30:22 ErrorLap bt3c_interrupt: Call of irq 11 for unknown device
39 > Dec 14 17:30:22 ErrorLap bt3c_interrupt: Call of irq 11 for unknown device
40 > Dec 14 17:30:23 ErrorLap ------------[ cut here ]------------
41 > Dec 14 17:30:23 ErrorLap kernel BUG at fs/sysfs/symlink.c:87!
42 > Dec 14 17:30:23 ErrorLap invalid operand: 0000 [#1]
43 > Dec 14 17:30:23 ErrorLap PREEMPT
44 > Dec 14 17:30:23 ErrorLap Modules linked in: bt3c_cs firmware_class radeon
45 > drm vmnet parport_pc parport vmmon ipt_state ipt_LOG ipt_limit
46 > iptable_mangle iptable_nat ip_nat iptable_filter ip_conntrack_ftp
47 > ip_conntrack_irc ip_conntrack snd_pcm_oss snd_mixer_oss snd_seq_dummy
48 > snd_seq_oss
49 > snd_seq_midi_event snd_seq snd_seq_device ehci_hcd radeonfb i2c_algo_bit
50 > snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd soundcore
51 > snd_page_alloc i2c_i801 i2c_core eth1394 ide_scsi sbp2 raw1394 ohci1394
52 > ieee1394 sco rfcomm bnep l2cap hci_uart usblp usb_storage scsi_mod hci_usb
53 > bluetooth ohci_hcd uhci_hcd usbhid usbcore orinoco_pci orinoco hermes
54 > 8139too Dec 14 17:30:23 ErrorLap CPU: 0
55 > Dec 14 17:30:23 ErrorLap EIP: 0060:[<c019a709>] Tainted: P VLI
56 > Dec 14 17:30:23 ErrorLap EFLAGS: 00010202 (2.6.14-gentoo-r4)
57 > Dec 14 17:30:23 ErrorLap EIP is at sysfs_create_link+0x58/0x62
58 > Dec 14 17:30:23 ErrorLap eax: fddf6f01 ebx: 00000000 ecx: f5ab4fc0
59 > edx: f5c76b01
60 > Dec 14 17:30:23 ErrorLap esi: f5c76b80 edi: f91bec20 ebp: f5ab4fc0
61 > esp: f5cb58c0
62 > Dec 14 17:30:23 ErrorLap ds: 007b es: 007b ss: 0068
63 > Dec 14 17:30:23 ErrorLap Process modprobe (pid: 9625, threadinfo=f5cb4000
64 > task=f5c075a0)
65 > Dec 14 17:30:23 ErrorLap Stack: f4ce0c40 c041ffab f9190588 f9190520
66 > c0309f3e f9190588 f5c76b88 f5ab4fc0
67 > Dec 14 17:30:23 ErrorLap f5c76b88 00000000 f91bec20 f5c76c00 f5c76b80
68 > f9190520 f5cb593c f91bd60e
69 > Dec 14 17:30:23 ErrorLap f5c76b80 f91905bc 00000014 00000001 0050f9c8
70 > f7c3f800 e8210000 f5ab4fe0
71 > Dec 14 17:30:23 ErrorLap Call Trace:
72 > Dec 14 17:30:23 ErrorLap [<c0309f3e>] class_device_add+0x212/0x230
73 > Dec 14 17:30:23 ErrorLap [<f91bd60e>] fw_register_class_device+0x10e/0x182
74 > [firmware_class]
75 > Dec 14 17:30:23 ErrorLap [<f91bd6b7>] fw_setup_class_device+0x35/0x13d
76 > [firmware_class]
77 > Dec 14 17:30:23 ErrorLap [<f91bd82c>] _request_firmware+0x6d/0x17f
78 > [firmware_class]
79 > Dec 14 17:30:23 ErrorLap [<f91bd965>] request_firmware+0x27/0x2b
80 > [firmware_class]
81 > Dec 14 17:30:23 ErrorLap [<f918ed0d>] bt3c_open+0xc0/0x180 [bt3c_cs]
82 > Dec 14 17:30:23 ErrorLap [<f918f31a>] bt3c_config+0x24b/0x35e [bt3c_cs]
83 > Dec 14 17:30:23 ErrorLap [<c0316e52>] as_set_request+0x26/0x78
84 > Dec 14 17:30:23 ErrorLap [<c011b283>] activate_task+0x67/0x7a
85 > Dec 14 17:30:23 ErrorLap [<c011b3ad>] try_to_wake_up+0xd8/0xda
86 > Dec 14 17:30:23 ErrorLap [<c03d717c>] schedule+0x326/0x64f
87 > Dec 14 17:30:23 ErrorLap [<c012f35c>] queue_work+0x5e/0x60
88 > Dec 14 17:30:23 ErrorLap [<c03d00ea>] svc_authenticate+0x12e/0x130
89 > Dec 14 17:30:23 ErrorLap [<c0310e9a>] __make_request+0x4d2/0x522
90 > Dec 14 17:30:23 ErrorLap [<c03111fe>] generic_make_request+0x7a/0x1ff
91 > Dec 14 17:30:23 ErrorLap [<c0163100>] bio_alloc_bioset+0x88/0x1ab
92 > Dec 14 17:30:23 ErrorLap [<c0133d51>] autoremove_wake_function+0x0/0x57
93 > Dec 14 17:30:23 ErrorLap [<c0183625>] do_mpage_readpage+0x28e/0x3c7
94 > Dec 14 17:30:23 ErrorLap [<c03113dd>] submit_bio+0x5a/0xf5
95 > Dec 14 17:30:23 ErrorLap [<c028778c>] radix_tree_insert+0xde/0x12c
96 > Dec 14 17:30:23 ErrorLap [<c0148658>] __pagevec_lru_add+0xde/0x107
97 > Dec 14 17:30:23 ErrorLap [<c0183240>] mpage_bio_submit+0x2b/0x32
98 > Dec 14 17:30:23 ErrorLap [<c0183831>] mpage_readpages+0xd3/0x16c
99 > Dec 14 17:30:23 ErrorLap [<c01cee25>] ext3_get_block+0x0/0x8a
100 > Dec 14 17:30:23 ErrorLap [<c03d7c9e>] io_schedule+0xe/0x16
101 > Dec 14 17:30:23 ErrorLap [<c0142339>] prep_new_page+0x47/0x5f
102 > Dec 14 17:30:23 ErrorLap [<c0142339>] prep_new_page+0x47/0x5f
103 > Dec 14 17:30:23 ErrorLap [<c01428b8>] buffered_rmqueue+0x10e/0x211
104 > Dec 14 17:30:23 ErrorLap [<c0142d4d>] __alloc_pages+0x2c6/0x41c
105 > Dec 14 17:30:23 ErrorLap [<c033ee67>] pccard_get_next_tuple+0x1e0/0x2de
106 > Dec 14 17:30:23 ErrorLap [<c033e9d3>] pccard_get_first_tuple+0x82/0x141
107 > Dec 14 17:30:23 ErrorLap [<f918f54f>] bt3c_event+0xc9/0xce [bt3c_cs]
108 > Dec 14 17:30:23 ErrorLap [<c0342a2b>] pcmcia_register_client+0x1eb/0x299
109 > Dec 14 17:30:23 ErrorLap [<c03d74ea>] preempt_schedule+0x45/0x66
110 > Dec 14 17:30:23 ErrorLap [<c012f25d>] call_usermodehelper_keys+0xc1/0xcc
111 > Dec 14 17:30:23 ErrorLap [<f918eed3>] bt3c_attach+0xaf/0xea [bt3c_cs]
112 > Dec 14 17:30:23 ErrorLap [<c0341924>] pcmcia_device_probe+0xaf/0x13f
113 > Dec 14 17:30:23 ErrorLap [<c0308e0f>] driver_probe_device+0x38/0xc2
114 > Dec 14 17:30:23 ErrorLap [<c0308f02>] __driver_attach+0x0/0x43
115 > Dec 14 17:30:23 ErrorLap [<c0308f43>] __driver_attach+0x41/0x43
116 > Dec 14 17:30:23 ErrorLap [<c03083f7>] bus_for_each_dev+0x58/0x78
117 > Dec 14 17:30:23 ErrorLap [<c0308f6b>] driver_attach+0x26/0x2a
118 > Dec 14 17:30:23 ErrorLap [<c0308f02>] __driver_attach+0x0/0x43
119 > Dec 14 17:30:23 ErrorLap [<c0308910>] bus_add_driver+0x83/0xe9
120 > Dec 14 17:30:23 ErrorLap [<c0309395>] driver_register+0x3b/0x40
121 > Dec 14 17:30:23 ErrorLap [<c0309346>] klist_devices_get+0x0/0xa
122 > Dec 14 17:30:23 ErrorLap [<c0309350>] klist_devices_put+0x0/0xa
123 > Dec 14 17:30:23 ErrorLap [<c03417c8>] pcmcia_register_driver+0x14/0x52
124 > Dec 14 17:30:23 ErrorLap [<f913500f>] init_bt3c_cs+0xf/0x13 [bt3c_cs]
125 > Dec 14 17:30:23 ErrorLap [<c013a958>] sys_init_module+0x153/0x20e
126 > Dec 14 17:30:23 ErrorLap [<c0103031>] syscall_call+0x7/0xb
127 > Dec 14 17:30:23 ErrorLap Code: 00 00 8b 44 24 18 89 4c 24 04 89 1c 24 89 44
128 > 24 08 e8 cd fe ff ff 8b 53 08 89 c1 ff 42 70 0f 8e 75 02 00 00 83 c4 0c 89
129 > c8 5b c3 <0f> 0b 57 00 4b 4e 40 c0 eb c1 8b 44 24 04 8b 40 30 89 44 24 04
130 >
131 >
132 > ####################################################
133 >
134 >
135 > "Call of irq 11 for unknown device" habe ich dann auch gleich bewundert und
136 > mit einem cat /proc/ interrupt mal genauer nachgeschaut:
137 >
138 > ####################################################
139 >
140 >
141 > CPU0
142 > 0: 130617 XT-PIC timer
143 > 1: 525 XT-PIC i8042
144 > 2: 0 XT-PIC cascade
145 > 8: 2 XT-PIC rtc
146 > 9: 1 XT-PIC acpi
147 > 11: 75894 XT-PIC yenta, yenta, eth1, uhci_hcd:usb1,
148 > uhci_hcd:usb2, ohci1394, Intel 82801CA-ICH3, eth0, radeon@pci:0000:01:00.0,
149 > pcmcia0.0
150 > 12: 111 XT-PIC i8042
151 > 14: 19644 XT-PIC ide0
152 > 15: 4336 XT-PIC ide1
153 > NMI: 0
154 > LOC: 0
155 > ERR: 0
156 > MIS: 0
157 >
158 > ####################################################
159 >
160 >
161 > Liegt also fast alles auf der 11. Da es ein ACPI-System ist, kann das ja
162 > vorkommen....
163 >
164 > Ausprobiert habe ich nun schon so einiges (ja auch ACPI ausschalten über
165 > Bootoption)... Google bringt inzwischen auch keine Hilfe mehr. Vielleicht
166 > kann ja einer von euch Helfen. Wer mehr Infos braucht kann sie bekommen!
167 >
168 >
169 > Jetzt schon mal danke
170 >
171 >
172 >
173 > S. van de Meer
174
175 --
176 --
177 Ich widerspreche der Nutzung oder übermittlung meiner Daten
178 für Werbezwecke oder für die Markt- und Meinungsforschung
179 (§ 28 Absatz 3+4 Bundesdatenschutzgesetz).
180 VCard zum downloaden: http://www.kernel-error.de/kernel.vcf
181 #####################################################
182 # GPG-INFO                                          #
183 # Finger-Print                                      #
184 # AC4E 5829 62C9 9CE6 F3D0 C209 6BB8 FE16 5CD6 50F3 #
185 # Den oeffentlichen bekommt ihr unter:              #
186 # http://www.kernel-error.de/kernel-error-mobil.asc #
187 #####################################################

Replies

Subject Author
Re: [gentoo-user-de] Seit Kernel 2.6.14 Probleme mit PCMCIA Sebastian van de Meer | Mobil <kernel-error-mobil@××××××××××××.de>