pcmcia detection locks up my laptop [also dapper flight 5]

Have you tried the Breezy preview release and does this still happen to you?

(In reply to comment #1)
> Have you tried the Breezy preview release and does this still happen to you?

No, not yet. I will download it when I'm at school again on monday.

Any update with regard to breezy release testing?

I have the same problem with a Toshiba A100-512 (see lspci & dmesg for further details). Booting from live/install cd (flight5) hangs (hard reset required) both times while configuring the cardbus bridge.

I installed dapper throug installing breezy, updating to dapper and uninstalling ubuntu-desktop, bluez-pcmcia-support and pcmcia-cs _before_ rebooting the system. After removing this packages, the lockup doesn't occur anymore. lspci and dmesg output originates from that system.

Since i am too lazy to c&p a complete screen of kernel output with pencil & paper :-) i will attach two screenshots from hung flight live and install cds.

HTH
tenco

Toshiba A100-512 dmesg output

Toshiba A100-512 "lspci -vv" output

Toshiba A100-512 screenshot Flight 5 live-cd

Toshiba A100-512 screenshot Flight 5 install-cd

Can anyone get a backtrace from the crash? https://wiki.ubuntu.com/DebuggingSystemCrash

Ben, surely a hang is indicative of a kernel issue rather than pcmcia-cs itself?

I think I'm having same problem, though with Flight 6 live cd. Hangs requiring reboot during gdm load -- I get a mouse cursor and a background, but nothing else. System is an Averatec 3250HX laptop w/ 1GB ram, mobile athlonxp proc.

This isn't a problem specific to laptops. My desktop computer hanged with the same bug. A friend of mine had the same bug.

The instalation hangs while trying to configure the package pcmcia-cs and then hangs on startup while trying to init the module. I had to reinstall Ubuntu, but my friend found a way around. He just started the machine using an i386 kernel instead of the 686-smp (the 686-smp is the only kernel I had configured).

I was wondering since I'm not familiar to the bug resolving process, if this bug gets patched will it be patched in the main repositories? or will every update have this issue?

dapper live-cd pcmcia detection and pcmcia detection of an installed dapper system works flawlessly.

Looks like this was last confirmed against a flight release. Can anyone reproduce it on a final dapper, or on edgy?

Did you look at the known problems here:

http://kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html#knownproblems

Maybe the kernel-option "pci=assign-busses" helps.

The lock up does not occur on the Dapper live-cd on my laptop anymore.

Based on comments from tenco and bitrain, marking this as "fix released", since code changes between Dapper's last "flight" and final release appear to have fixed this.