More weird behavior after last round of updates.

[Hans Engelen]

So after tinkering for day installing a whole range of stuff miniset per 
miniset I managed to catch up to almost all my updates pending in up2date.

My setup is as follows :
Dell C600, which has an internal 3c59x network card and around the house is 
used with a lucent orinoco gold card (all of which worked fine up till now). 
When using the laptop at my desk it is inserted into a Dell docking station 
which adds an adaptec controler (nothing attached) another 3c59x and usually 
houses my floppy module in the module slot. It also adds 2 pci slots, some 
usb ports and the common parallel, serial, keyb/mouse and vga connectors all 
of which are unused.

Up to now (including FC2T1) this usually led to kudzu asking for instructions 
with regards to the adaptec and second 3com adapter when changing from docked 
to undocked booting or vice-versa.

Since the last batch of updates (and it was a lot, nearly 1200 if memory 
serves) the system works semi stable in docked mode (cyrus-imapd seems to be 
running amok and spawning an abnormal amount of child instances but thats 
probably unrelated). Pcmcia seemed to be acting up slightly initially but 
that most likely was due to some odd moprobe.conf setting that managed to 
load modules like hermes and orinoco (not orinoco_cs) before pcmcia was 
started. This oddly resulted in pcmcia not detecting any of the pcmcia 
sockets or sometimes just one (C600 has 2, yenta type).

Starting the laptop in undocked mode however is a disaster. Kudzu hangs and 
does not seem to recover. Pcmcia refuses to find any sockets flat out no 
matter what and often hangs too. Checking the running processes reveals one 
or more modprobe command that seem to be hanging and dmesg spits out fun 
tidbits like this (they vary) :

kernel: Unable to handle kernel paging request at virtual address 228ba770
kernel:  printing eip:
kernel: 021cbb01
kernel: *pde = 0154f067
kernel: Oops: 0002 [#1]
kernel: CPU:    0
kernel: EIP:    0060:[<021cbb01>]    Not tainted
kernel: EFLAGS: 00010206   (2.6.4-1.305)
kernel: EIP is at kobject_add+0x7c/0xd0
kernel: eax: 02339d78   ebx: 02339d04   ecx: 228ba770   edx: 2288d630
kernel: esi: 02339d4c   edi: 2288d614   ebp: 02339d80   esp: 1ed93f24
kernel: ds: 007b   es: 007b   ss: 0068
kernel: Process modprobe (pid: 765, threadinfo=1ed93000 task=21665980)
kernel: Stack: 2288d614 ffffffea 2288d5e4 00000000 021cbb6e 2288d614 02339d00 
0222170f
kernel:        2288d614 2288a3d5 2288d5f4 1ed93f78 2288d60c 00000006 02221a57 
1d244b3c
kernel:        00000000 0000000a 022f314d 00000000 00000000 00000000 00000000 
2288d5c0
kernel: Call Trace:
kernel:  [<021cbb6e>] kobject_register+0x19/0x39
kernel:  [<0222170f>] bus_add_driver+0x2e/0x81
kernel:  [<02221a57>] driver_register+0x48/0x50
kernel:  [<021d4188>] pci_register_driver+0x84/0x9f
kernel:  [<2283b046>] vortex_init+0xe/0x4d [3c59x]
kernel:  [<0213b708>] sys_init_module+0x1ef/0x2c6
kernel: Code: 89 11 89 4a 04 8b 47 28 8b 18 8d 4b 48 89 c8 ba ff ff 00 00

At this point I am a little at a loss as to what might be going wrong. Anybody 
have any suggestions where to start? I scanned through Bugzilla and recent 
posts on the list but didn't find anything that resembled my findings.

Cheers.