[Acer Extensa 5230] linux-image-3.11.0-12-generic doesn't boot

Boot process with kernel 3.11 when hanging (the disk led is on all the time)

Boot process on the same machine with the 3.8 kernel from quantal. It succeeeds.
Incidentially, the machine is fsck-ing the disk, due to the sheer number of reboots I did...

It's 3.8 from raring ringtail, not quantal (sorry about that)

I tried disabling swap, but that doesn't change a thing. So it must be something after swapon.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1237336

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Falling back to linux-image-3.11.0-11-generic makes things work again.
So it's a change between -11 and -12...

3.11.0-11.17: working
3.11.0-12.18: not working

Hm, looking at the changelog it's maybe due to the apparmor changes?
Don't have the calxedaxgmac at all, and the Upstream Kernel Change seems to refer to an apple trackpad.

Adding apparmor=0 to the kernel boot parameters doesn't change a thing

So, I even updated the BIOS to the most recent version, no change.

Turns out that it's a driver in the extra package. PCMCIA is being probed and the kernel freezes; this happens for the mainline kernel as well.

Blacklisting yenta_socket makes the machine boot OK!
If I modprobe yenta_socket after booting up, the machine locks up.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

On 3.8, modprobe'ing yenta_socket works ok and gives:

# sync && modprobe yenta_socket
Oct 9 14:46:46 ishtar kernel: [ 68.809008] yenta_cardbus 0000:0d:06.0: CardBus bridge found [1025:013c]
Oct 9 14:46:46 ishtar kernel: [ 68.809031] yenta_cardbus 0000:0d:06.0: O2: enabling read prefetch/write burst. If you experience problems or performance issues, use the yenta_socket parameter 'o2_speedup=off'
Oct 9 14:46:46 ishtar kernel: [ 68.936933] yenta_cardbus 0000:0d:06.0: ISA IRQ mask 0x0cb8, PCI irq 22
Oct 9 14:46:46 ishtar kernel: [ 68.936938] yenta_cardbus 0000:0d:06.0: Socket status: 30000006
Oct 9 14:46:46 ishtar kernel: [ 68.936942] pci_bus 0000:0d: Raising subordinate bus# of parent bus (#0d) from #0e to #11
Oct 9 14:46:46 ishtar kernel: [ 68.936957] yenta_cardbus 0000:0d:06.0: pcmcia: parent PCI bridge window: [io 0x5000-0x5fff]
Oct 9 14:46:46 ishtar kernel: [ 68.936960] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x5000-0x5fff:
Oct 9 14:46:46 ishtar kernel: [ 68.937914] excluding 0x5000-0x50ff 0x5400-0x54ff
Oct 9 14:46:46 ishtar kernel: [ 68.942008] yenta_cardbus 0000:0d:06.0: pcmcia: parent PCI bridge window: [mem 0xf4700000-0xf47fffff]
Oct 9 14:46:46 ishtar kernel: [ 68.942013] pcmcia_socket pcmcia_socket0: cs: memory probe 0xf4700000-0xf47fffff:
Oct 9 14:46:46 ishtar kernel: [ 68.942015] excluding 0xf4700000-0xf470ffff
Oct 9 14:46:46 ishtar kernel: [ 68.942025] yenta_cardbus 0000:0d:06.0: pcmcia: parent PCI bridge window: [mem 0x80000000-0x83ffffff pref]
Oct 9 14:46:46 ishtar kernel: [ 68.942028] pcmcia_socket pcmcia_socket0: cs: memory probe 0x80000000-0x83ffffff:
Oct 9 14:46:46 ishtar kernel: [ 68.942042] excluding 0x80000000-0x83ffffff
root@ishtar:~# Oct 9 14:46:46 ishtar kernel: [ 69.055044] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af:
Oct 9 14:46:46 ishtar kernel: [ 69.056776] clean.
Oct 9 14:46:46 ishtar kernel: [ 69.056814] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff:
Oct 9 14:46:46 ishtar kernel: [ 69.057000] excluding 0x400-0x48f 0x4d0-0x4d7
Oct 9 14:46:46 ishtar kernel: [ 69.057122] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff:
Oct 9 14:46:46 ishtar kernel: [ 69.057546] clean.
Oct 9 14:46:46 ishtar kernel: [ 69.057560] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7:
Oct 9 14:46:46 ishtar kernel: [ 69.058029] clean.
Oct 9 14:46:46 ishtar kernel: [ 69.058049] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff:
Oct 9 14:46:46 ishtar kernel: [ 69.058055] excluding 0xc0000-0xd3fff 0xe4000-0xfffff
Oct 9 14:46:46 ishtar kernel: [ 69.058080] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff:
Oct 9 14:46:46 ishtar kernel: [ 69.058097] clean.
Oct 9 14:46:46 ishtar kernel: [ 69.058111] pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff:
Oct 9 14:46:46 ishtar kernel: [ 69.058126] excluding 0x60000000-0x60ffffff
Oct 9 14:46:46 ishtar kernel: [ 69.058141] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff:
Oct 9 14:46:46 ishtar kernel: [ 69.058675] clean.

On 3.11 I got:

# sync && modprobe yenta_socket o2_speedup=off
Oct 9 14:50:18 ishtar kernel: [ 62.095581] yenta_cardbus 0000:0d:06.0: CardBus bridge found [1025:013c]
Oct 9 14:50:18 ishtar kernel: [ 62.095607] yenta_cardbus 0000:0d:06.0: O2: disabling read prefetch/write burst. If you experience problems or performance issues, use the yenta_socket parameter 'o2_speedup=on'
Oct 9 14:50:18 ishtar kernel: [ 62.221015] yenta_cardbus 0000:0d:06.0: ISA IRQ mask 0x0cb8, PCI irq 22
Oct 9 14:50:18 ishtar kernel: [ 62.221021] yenta_cardbus 0000:0d:06.0: Socket status: 30000006
Oct 9 14:50:18 ishtar kernel: [ 62.221025] pci_bus 0000:0d: Raising subordinate bus# of parent bus (#0d) from #0e to #11
Oct 9 14:50:18 ishtar kernel: [ 62.221035] yenta_cardbus 0000:0d:06.0: pcmcia: parent PCI bridge window: [io 0x5000-0x5fff]
Oct 9 14:50:18 ishtar kernel: [ 62.221039] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x5000-0x5fff:
Oct 9 14:50:18 ishtar kernel: [ 62.221995] excluding 0x5000-0x50ff 0x5400-0x54ff
Oct 9 14:50:18 ishtar kernel: [ 62.226329] yenta_cardbus 0000:0d:06.0: pcmcia: parent PCI bridge window: [mem 0xf4700000-0xf47fffff]
Oct 9 14:50:18 ishtar kernel: [ 62.226334] pcmcia_socket pcmcia_socket0: cs: memory probe 0xf4700000-0xf47fffff:
Oct 9 14:50:18 ishtar kernel: [ 62.226337] excluding 0xf4700000-0xf470ffff
Oct 9 14:50:18 ishtar kernel: [ 62.226347] yenta_cardbus 0000:0d:06.0: pcmcia: parent PCI bridge window: [mem 0x80000000-0x83ffffff pref]
Oct 9 14:50:18 ishtar kernel: [ 62.226350] pcmcia_socket pcmcia_socket0: cs: memory probe 0x80000000-0x83ffffff:
Oct 9 14:50:18 ishtar kernel: [ 62.226364] excluding 0x80000000-0x83ffffff

and it freezes

Leaving o2_speedup at i's default "on" doesn't change the picture on 3.11:

# sync && modprobe yenta_socket
Oct 9 14:52:55 ishtar kernel: [ 57.637446] yenta_cardbus 0000:0d:06.0: CardBus bridge found [1025:013c]
Oct 9 14:52:55 ishtar kernel: [ 57.637472] yenta_cardbus 0000:0d:06.0: O2: enabling read prefetch/write burst. If you experience problems or performance issues, use the yenta_socket parameter 'o2_speedup=off'
Oct 9 14:52:55 ishtar kernel: [ 57.764939] yenta_cardbus 0000:0d:06.0: ISA IRQ mask 0x0cb8, PCI irq 22
Oct 9 14:52:55 ishtar kernel: [ 57.764945] yenta_cardbus 0000:0d:06.0: Socket status: 30000006
Oct 9 14:52:55 ishtar kernel: [ 57.764949] pci_bus 0000:0d: Raising subordinate bus# of parent bus (#0d) from #0e to #11
Oct 9 14:52:55 ishtar kernel: [ 57.764959] yenta_cardbus 0000:0d:06.0: pcmcia: parent PCI bridge window: [io 0x5000-0x5fff]
Oct 9 14:52:55 ishtar kernel: [ 57.764962] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x5000-0x5fff:
Oct 9 14:52:55 ishtar kernel: [ 57.765918] excluding 0x5000-0x50ff 0x5400-0x54ff
Oct 9 14:52:55 ishtar kernel: [ 57.770077] yenta_cardbus 0000:0d:06.0: pcmcia: parent PCI bridge window: [mem 0xf4700000-0xf47fffff]
Oct 9 14:52:55 ishtar kernel: [ 57.770081] pcmcia_socket pcmcia_socket0: cs: memory probe 0xf4700000-0xf47fffff:
Oct 9 14:52:55 ishtar kernel: [ 57.770084] excluding 0xf4700000-0xf470ffff
Oct 9 14:52:55 ishtar kernel: [ 57.770094] yenta_cardbus 0000:0d:06.0: pcmcia: parent PCI bridge window: [mem 0x80000000-0x83ffffff pref]
Oct 9 14:52:55 ishtar kernel: [ 57.770097] pcmcia_socket pcmcia_socket0: cs: memory probe 0x80000000-0x83ffffff:
Oct 9 14:52:55 ishtar kernel: [ 57.770111] excluding 0x80000000-0x83ffffff

So I'm digging through the CHANGELOGS between the mainline kernels 3.8.13.8 and 3.11.3 (which correspond to the mainline kernels for the working and broken kernel).

There's only two kernels with changes to PCMCIA (which strikes me as odd, but hey), and both contain the SAME change:

https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.9.11

commit 22b8276166bdb3daf7858f6cca7d315fdcced175
Author: Joachim Eastwood <email address hidden>
Date: Thu Jun 6 10:24:14 2013 +0200

    pcmcia: at91_cf: fix gpio_get_value in at91_cf_get_status

    commit e39506b466edcda2a7e9d0174d7987ae654137b7 upstream.

    Commit 80af9e6d (pcmcia at91_cf: fix raw gpio number usage) forgot
    to change the parameter in gpio_get_value after adding gpio
    validation.

https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.2

commit 5eb2698932989f855e3427b0860771611f831a69
Author: Joachim Eastwood <email address hidden>
Date: Thu Jun 6 10:24:14 2013 +0200

    pcmcia: at91_cf: fix gpio_get_value in at91_cf_get_status

    commit e39506b466edcda2a7e9d0174d7987ae654137b7 upstream.

    Commit 80af9e6d (pcmcia at91_cf: fix raw gpio number usage) forgot
    to change the parameter in gpio_get_value after adding gpio
    validation.

3.11.0-11.17 was rebased to upstream 3.11.3, so it has all 3.11.3 changes. 3.11.0-12.18 is still based off of upstream 3.11.3, so the bug may have been introduced by a SAUCE patch between 3.11.0-11.17 and 3.11.0-12.18.

Can you first test the mainline 3.11.3 kernel to confirm the bug does not exist:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.3-saucy/

If the bug does not exist in upstream 3.11.3, we can bisect between 3.11.0-11.17 and 3.11.0-12.18 to find the commit that introduced this. As you already saw, there are only a few changes between these two Ubuntu versions, so a bisect should be fairly quick.

* Joseph Salisbury <email address hidden>:
> 3.11.0-11.17 was rebased to upstream 3.11.3, so it has all 3.11.3
> changes. 3.11.0-12.18 is still based off of upstream 3.11.3, so the bug
> may have been introduced by a SAUCE patch between 3.11.0-11.17 and
> 3.11.0-12.18.
>
> Can you first test the mainline 3.11.3 kernel to confirm the bug does not exist:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.3-saucy/

It's in mainline 3.11.3 as well. Turns out that 3.11.0-11.17 was ONLY
working since I forgot to install the -extras package which contains
the PCMCIA drivers.

So: 3.11.0-11.17 && 3.11.0-12.18 && mainline 3.11.3 ALL crash, at the
very same stage (when initializing the PCMCIA adapter)

As a quick test, I built a saucy test kernel with commit e39506b reverted. This test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1237336/

Can you test this kernel and see if it still exhibits the bug? If it still has the bug, we can start a kernel bisect to identify the commit that introduced this regression.

This test kernel also requires installation of both the linux-image and linux-image-extra .deb packages.

Hi! I upgraded from 13.04 to 13.10 and have the same problem. I launch linux-image-3.11.0-12-generic in safe mode and it freezes by "pcmcia_socket: cs: I0 port probe excluding".
I have to boot with linux-image-3.8.0-31-generic
I am willing to help to solve the issue but I don't really know what to do next.

@Ralf, @naphta,

Can you test the kernel posted in comment #33?

* Joseph Salisbury <email address hidden>:
> @Ralf, @naphta,
>
> Can you test the kernel posted in comment #33?

I hope @naphta can, since I don't have access to the machine in
question.

@Joseph,

My computer is 32 bits, may the test work if I install linux-image-3.11.0-12-generic_3.11.0-12.19~lp1237336v1_amd64.deb ?

@naphta,

I'll build a 32 bit kernel for you.

There is now a 32 bit version of the test kernel available at:
http://kernel.ubuntu.com/~jsalisbury/lp1237336/

Hi! I have the same problem. I upgraded from 13.04 to 13.10 today. I can boot with kernel 3.8.0-31-generic but kernel 3.11.0-12 freezes before the login screen.

The last test kernel has the bug.

I have exactly the same problem on an Acer Extensa 5630Z

I built the next test kernel, up to the following commit:
e2ff39400d81233374e780b133496a2296643d7d

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1237336

Can you test that kernel and report back if it has the bug or not. I will build the next test kernel based on your test results.

Thanks in advance

On a Lenovo Thinkpad X230, 3.11.0-12-generic does not get past the Ubuntu boot logo, whereas 3.11.0-11-generic works fine.

@Joseph,

the last test kernel exhibits the bug.

I built the next test kernel, up to the following commit:
0902a9044fa5b7a0456ea4daacec2c2b3189ba8c

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1237336

Can you test that kernel and report back if it has the bug or not. I will build the next test kernel based on your test results.

Thanks in advance

The last one doesn't have the bug.

I built the next test kernel, up to the following commit:
ac212b6980d8d5eda705864fc5a8ecddc6d6eacc

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1237336

Can you test that kernel and report back if it has the bug or not. I will build the next test kernel based on your test results.

Thanks in advance

The last one presents the bug.

I built the next test kernel, up to the following commit:
683058e315f00a216fd6c79df4f63bc9945ca434

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1237336

Can you test that kernel and report back if it has the bug or not.

This should be one of the last kernels to identify the commit that introduced this bug.

The last kernel does not exhibit the bug.

The bisect indicated the following commit as the source of the regression:

commit ac212b6980d8d5eda705864fc5a8ecddc6d6eacc
Author: Rafael J. Wysocki <email address hidden>
Date: Fri May 3 00:26:22 2013 +0200

    ACPI / processor: Use common hotplug infrastructure

This seems like a fairly big commit to easily revert, but I'll investigate it.

Just to confirm this isn't already fixed in mainline, could you test the v3.12 final kernel, which can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/

It isn't fixed, the bug still appears in mainline.

Any update on this? My current workaround consists of booting 3.11.0-11-generic x84_64 and setting

   GRUB_DEFAULT="saved"

in /etc/default/grub.

@jnns, per your previous comments, it seems you may be hitting a different bug. Can you test the v3.11-rc1[0] kernel, as was also tested in comment #45. You should hit the bug in 3.11-rc1, but you mention in comment #70 that 3.11.0-11 boots fine.

If you don't hit the bug in v3.11-rc1, then you should open a new bug for your issue.

[0] v3.11-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/

@naphta, We recieved a request from upstream[0]. Can you try booting your system without PCMCIA?

[0] https://lkml.org/lkml/2013/11/15/442

I do not really know how to do that. I have never used a PCMCIA card and my computer is a laptop, so I cannot phisically uninstall the PCMCIA slot. Maybe I can configure it on the BIOS? I have not been able to find any information about booting without PCMCIA.

@jsalisbury, you're right; it seems as if I'm hitting a different bug.

A quick summary for a Lenovo Thinkpad X230:
 - v3.11-rc1 works
 - v3.11.0-11 works
 - v3.11.0.12 does not work
 - v3.11.0.13 works

You can boot with the hw-detect/start_pcmcia=false boot parameter. This can be done by entering the letter 'e' at the GRUB menu, then adding hw-detect/start_pcmcia=false to the boot cmd line.

Another thing you can do is to edit the /etc/default/grub line and add that parameter to:

GRUB_CMDLINE_LINUX_DEFAULT

The line could then look like:
GRUB_CMDLINE_LINUX_DEFAULT=" hw-detect/start_pcmcia=false"

After editing the /etc/default/grub file, you need to run: 'sudo update-grub' then reboot.

I tried both ways but the problem remains the same.

Thanks for testing. I'll let upstream know and see if there are other things to test.

Could you also give the v3.13-rc2 kernel a test:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc2-trusty/

The v3.13-rc2 kernel presents the bug, as well.

Do you see a different error when you have PCMCIA disabled? Can you take a digital picture of where the system hangs?

naphta /jnns, thank you for your comment. So your underlying hardware may be tracked and reviewed, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

Hello,

I'm having exactly the same problem on a Fujitsu M2010.
Here attached some logs. It is reproductible exactly the same way and hangs at the same point.

Best regards

Lsusb?field.comment=Lsusb

Aureliano, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Good evening,

executing ubuntu-bug linux (even with sudo), it tells me that the kernel is not "officially supported by Ubuntu".
May be because it is a kernel from the previous release that is not in saucy ?

Uname -a returns:
Linux PAS 3.8.0-33-generic #48-Ubuntu SMP Wed Oct 23 17:26:34 UTC 2013 i686 i686 i686 GNU/Linux

Aureliano, please just open a report via https://bugs.launchpad.net/ubuntu/+source/linux/+filebug and we can take it from there.

I nave the same laptop and the same problem with saucy, I had to install Ubuntu 12.04 for now 'cause I needed a fully functional PC' anyway my Acer would boot if acpi=off parameter was set in the grub, don't know if that's useful

Samir Boumsik, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Hi,

I just want to say that I've hit that bug on much more older kernels than you guys...

After installing Linux Mint 13 Xfce (32bits) on a HP Pavilion ZV5000 [with TI PCI1620 PC card controller (rev 01)], I could only boot 1 of 5 times without a total freeze, needing a hard reset (neither Ctrl+Alt+Del nor MagicKeys are working in this case) !
And that with stock kernel 3.2.0-23 or it's update 3.2.0-58.
Even the live CD of PartedMagic only boots 3 of 5 times without freezes, with it's 3.5.6 kernel fom october 2012.

In both cases (LM13 + PartedMagic) , adding the boot option "modprobe.blacklist=yenta_socket" solves the issue all the time...

But also in both cases, modprobing yenta_socket once booted doesn't brings a lock up !
Just a lot of "memory probe / IO port probe: excluding nothing: probe failed"...
Hope this helps.

fvj, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Same issue on Fujitsu M2010.

Ubuntu 12.04 with saucy lts (3.11) kernet does not boot.

Kernels 3.2, 3.5, 3.8 boots ok.

@ penalvch
Thank your for your reply.
Sadly, the HP Pavilion was not mine.
As its owner doesn't use PCMCIA cards, I added the boot option and had to give it back to him this week-end...

eros2, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

same Problem with XUBUNT 14.04-1 and ACER 5230 and latest Updateas

Same problem with DEBIAN 8 (Jessie) and kernel 3.16.0-4.
This bug affect only i386 kernel, 64 bits install works perfectly.