fixing recursive fault but reboot is needed! upon boot (always reproducible on battery only, but sometimes on AC too)

I also have the Y560 and can verify this is happening and I also get the same kernel panic message. Over at askubuntu.com there are a few other people experiencing the same problem:
http://askubuntu.com/questions/38612/lenovo-y560-wont-boot-unless-its-on-ac-power/39752#39752
http://askubuntu.com/questions/35112/lenovo-y460-wont-boot-most-of-the-time-unless-plugged-in/39766#39766

I also have a lenovo Y560 and confirm this. Exactely the same problem for me.

Problemappears in a fresh ubuntu 11.04 installation.

I have Lenovo IdeaPad U350 and the same problem happens. I didn't test while plugged in (so I was only on battery), but I need to restart several times before the panic doesn't occur!

Also: Are all of you using the proprietary Broadcom wireless drivers?

No iam not using the proprietary Broadcom driver.

The only proprietary driver i am using is the FGLRX driver.

What further information can I provide to help solving the bug?

I'm seeing the same thing with a Y450.

Happens to me even when on AC power with the battery in though - every other report I've seen says battery only. If I take the battery out and run on AC power only, everything works just fine. Battery + AC = panic.

ACPI=off as a boot parameter solves the problem for me. But as a consquence also power managment stops working properly.

I've the same problem with Y450. With the battery, it doesn't boot at all, on AC, it boots but with a noticeable lag. Occurs with Ubuntu 11.04 stock kernel, using older kernel for now.

@above: SRY, ITS Y560, NOT Y450

Same symptoms here with a Lenovo IdeaPad Z360.
Booting on battery only works about 33% of the time, but once it starts, everything is working fine.
On AC power it boots without any problems.

No proprietary drivers here; NVidia GPU disabled @ bios.

Seems like most of Lenovos recent IdeaPads are affected...

Hi i have the IdeaPad S10-3s and i think the same problem.

Same problem here...

Tried BIOS Update, didn't help

previous BIOS Version 30CN56WW
current BIOS Version 30CN77WW

Hardware information:
Lenovo IdeaPad Y560
Intel Core i3 350M
4GB RAM 1066

Software information:
Ubuntu 11.04 Natty Narwhal
Proprietary drivers: fglrx
switchable graphics turned off (BIOS)
working on discrete graphics (BIOS)

Hi All,

I have fairly old hardware - an Acer TravelMate 292LMi. It did fine with Ubuntu till this kernel release came around. I'm experiencing likewise and currently using an older kernel version.

Cheers

I am getting this error no matter whether AC is attached or not. Is there any resolution to it yet?

As some other users above, I also have a Y560 Lenovo and confirm this behavior.
1. Suspend when on AC.
2. Attempts to resume on battery -- fail with panic as reported above. Sadly, doesn't allow reboot.

Did anyone find a workaround?

Problem also occurs on my Lenovo IdeaPad Y450 with a fresh 11.04 installation, but like #5 sometimes the error doesn't appear and everything works fine after rebooting a few times.

On AC power without battery, I can boot without problems. In previous OS and kernel versions, no boot problems as well.

It should be noted, though, that my battery itself is considered "broken" by Ubuntu and Win7 and no longer reports accurate charge levels.

Kernel Panic on Boot with Ubuntu 11.04 and Battery Power affects me on the Lenovo Z360

I have the same problem, Lenovo IdeaPad Y460

I can confirm the bug on a Lenovo IdeaPad Z370 + 11.04.

The bug is 100% reproducible for me, if I shut down the laptop via reset (press power button for 6 seconds)

I'm using Lenovo Ideapad Z360 and reproducible on battery. But sometimes also on AC power.

To reproduce on AC power:
1. Power on the laptop on battery (without AC power)
2. Experience Ubuntu failed booting with "fixing recursive fault" (fan is also turning on highly)
3. Connect the AC power
4. Reboot the computer... Ubuntu still failed to boot.

If I turn off the laptop, while the AC power is connected, then power on again Ubuntu boots successfully.

My kernel is:

Linux annafi 2.6.38-9-generic #43+kamal~mjgbacklight4-Ubuntu SMP Fri Apr 29 04:33:59 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

My hardware info attached.

my lspci attached

my cpuinfo attached.

please let me know what else I can do to help.

not being able to power on my laptop on battery is critical issue.

This issue should be critical, seems to be affecting a lot of users in a very severe way (as many have mentioned - not being able to boot with battery power only is a big issue for anyone who is usually on the go)

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

I've confirmed this happens while using both fglrx and radeon X drivers. And while recovery (single) mode does occasionally work (for me), a majority of the time, it gives the same message.

This also happens on my Fujitsu Amilo PI 3560 laptop. I couldn't get it to work even with the AC plugged in.
The Ubuntu version that I installed using wubi is 11.04 amd64.

After getting this error with ubuntu 11.04, I've installed ubuntu 10.10-desktop-amd64 and it worked!

Also happens like this:
1. Turn on the laptop on AC
2. Suspend the laptop
3. Unplug from AC
4. Resume the laptop (on battery only)

Then the laptop will lock up (and in my Lenovo Ideapad Z360 the CPU fan is spinning very loud).
The laptop then needs to be powered off, losing all data and corrupting the filesystem in the process. :-(

This bug appears to be fixed in vanilla 2.6.39. I built and installed 2.6.39 loosely following the instructions on https://wiki.ubuntu.com/KernelTeam/GitKernelBuild and used Ubuntu-X ppa for updated fglrx drivers. Booting to that, I no longer have this issue, and am able to boot without any problems--AC or no.

Lenovo Y450, 11.04, 2.6.38-8-generic.
The HDD LED does not light when this bug appears.

I confirm that the bug appears to be fixed in Linux Kernel 2.6.39

I installed the Ubuntu mainline kernel v2.6.39-oneiric and you also need fgrlx 2:8.850 (you can use the Ubuntu-X ppa).

Tested on Lenovo Y560
Tested about 3 reboots without AC plugged in - it seams to work.

I have a Lenovo 460 with Ubuntu 11.04 on the machine. I am having similar issues where I am unable to boot into the new kernel, unless I am plugged in to the AC power adapter I have no issues booting into the OS. I have installed the latest graphics driver from AMD for my ATI switchable graphics.. Following this line-up to get the driver to properly install I had to Install the prerequisite packages:

$ sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 wget execstack libelfg0 dh-modaliases

If you are using the x86_64 architecture (64 bit), be sure to install "ia32-libs" on your machine, if you do not it will not function

$ sudo apt-get install ia32-libs

Download the latest Catalyst package.

This package contains both the 32-bit and 64-bit driver. Current Version is 11.6

$ cd ~/; mkdir catalyst11.6; cd catalyst11.6/
$ wget http://www2.ati.com/drivers/linux/ati-driver-installer-11-6-x86.x86_64.run
$ chmod +x ati-driver-installer-11-6-x86.x86_64.run

Create .deb packages.

$ sudo sh ./ati-driver-installer-11-6-x86.x86_64.run --buildpkg Ubuntu/natty

Install .debs.

$ sudo dpkg -i fglrx*.deb

Generate a new /etc/X11/xorg.conf file

Create the ATI version of the Xorg.conf file.
This is a Generic Configuration... This works great for my machine which is a Lenovo Y460

$ sudo aticonfig --initial -f

After just reboot your machine

After following this proceedure I am still unable to start Ubuntu without having to be plugged into the wall... I hope the fix will come soon...

I will confirm, after about 2 hours of configuring and tinkering with this relentless update of the new kernel. The new kernel installation was unable to boot on a switchable graphics BIOS setting, so I had to switch back to discrete display. However, the ATI device driver broke after installation, so after reverting to the default display driver everything went back to working order. I am am glad to say that my Lenovo Y460 laptop is able to successfully boot into the OS with or without a AC power adapter cord because of installing the 2.6.39.0 Kernel for Ubuntu 11.04.. Nice feature and all, but now the laptop runs hot and is unable to save on battery life because of the lack of a device driver to support the graphics card in the laptop. If anyone has a solution please let me know as soon as you can, for this is a huge disadvantage in a laptop having to have it plugged in because my battery drains from lack of driver support to the display card.

I have the same exact problem on a sony vaio with a fresh wubi installation of ubuntu. The AC power seems to play a critical role on the occurrence of the error but also experienced the error every time there was a first run for the kernel i.e. after wubi finished installing i got the error, then powered off and on again and it was fine, then i was prompted about updates and after i restarted again to load with a new kernel i got the message again.

I am happy to report that for the Y560 running the latest kernel update (2.6.38-10-generic) from the standard repo the problem seems to have been resolved. I can now boot up while on battery and I do not seem to be having any of the battery, heat, graphics issues others are reporting.

I hit the panic when install Ubuntu 11.04 on an OLD Lenovo laptop. I find a work around, that is, add "acpi=off noapic" to kernel options. I can countinue installing the system now.

Confirmed yet undecided? This has been three months.

I think I have the same problem but under slightly different circumstances. It happens whether on battery or not.

Was able to boot after adding 'acpi=off nomodeset xforcevesa' to the grub boot options. The acpi=off was definitely necessary. I think the xforcevesa was only necessary to fix a different, unrelated graphical problem.

By the way, this is in 11.10.

A friend just brought his Acer Travelmate 2350 notebook over asking me to remove WinXP and install a Linux OS. I tried to boot it with a Live DVD of Linux Mint 12, and Linux Mint 11, and in both instances got only as far as :
 Fixing recursive fault but reboot is needed!
Removing the battery resulted in the same.

It's getting to the point that I am reluctant to recommend a Linux OS to my friends as each upgrade seems to introduce problems which remain unresolved.

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, the next step is to find the specific commit that fixed this issue. Could you please do so following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Still having this, using 3.0.0-17-generic with a Sandy bridge CPU and graphics, so I am slightly reluctant to installing some foreign vendor graphics driver that isn't related to my hardware, even though it seems to have solved the issue for others using different GPU's.

Joakim B, please file a new bug via the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

Confirming that this issue occurrs on Acer Travelmate 2350.
Made a fresh install of Lubuntu 11.10. Didn't got the machine booting without setting kernel parameter "acpi=off".
kernel version 3.0.0-17-generic i686
..haven't touch the graphics settings yet.

Günter Dressel, please file a new bug via the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

In a Ubuntu-Precise server (3.2.0-27 kernel) i have this kernel panic in dmesg:

[ 131.459333] ------------[ cut here ]------------
[ 131.459344] WARNING: at /build/buildd/linux-3.2.0/mm/slub.c:3374 ksize+0xb5/0xc0()
[ 131.459347] Hardware name: ProLiant ML350 G6
[ 131.459349] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables bridge stp xen_gntdev xen_netback xen_blkback xen_evtchn xenfs microcode usbhid hid usb_storage uas xfs radeon ttm drm_kms_helper drm ipmi_si ipmi_msghandler i2c_algo_bit psmouse i7core_edac bonding edac_core hpilo serio_raw shpchp acpi_power_meter mac_hid lp parport tg3 hpsa
[ 131.459394] Pid: 1649, comm: sh Not tainted 3.2.0-27-generic #43-Ubuntu
[ 131.459396] Call Trace:
[ 131.459404] [<ffffffff8106729f>] warn_slowpath_common+0x7f/0xc0
[ 131.459410] [<ffffffff81659eae>] ? _raw_spin_unlock_irqrestore+0x1e/0x30
[ 131.459414] [<ffffffff810672fa>] warn_slowpath_null+0x1a/0x20
[ 131.459418] [<ffffffff81161f65>] ksize+0xb5/0xc0
[ 131.459423] [<ffffffff811329bc>] kzfree+0x1c/0x40
[ 131.459428] [<ffffffff812d6b9a>] apparmor_file_free_security+0x1a/0x20
[ 131.459434] [<ffffffff8129dbc6>] security_file_free+0x16/0x20
[ 131.459439] [<ffffffff81179436>] __fput+0xc6/0x210
[ 131.459442] [<ffffffff811795a5>] fput+0x25/0x30
[ 131.459446] [<ffffffff811761c6>] filp_close+0x66/0x90
[ 131.459450] [<ffffffff81069b7a>] put_files_struct.part.10+0x7a/0xe0
[ 131.459455] [<ffffffff8106b598>] put_files_struct+0x18/0x20
[ 131.459459] [<ffffffff8106b664>] exit_files+0x54/0x70
[ 131.459463] [<ffffffff8106bb45>] do_exit+0x195/0x420
[ 131.459467] [<ffffffff8106bf74>] do_group_exit+0x44/0xa0
[ 131.459470] [<ffffffff8106bfe7>] sys_exit_group+0x17/0x20
[ 131.459475] [<ffffffff81662282>] system_call_fastpath+0x16/0x1b
[ 131.459478] ---[ end trace 92e87a495e3a2e5a ]---
[ 131.459487] ------------[ cut here ]------------
[ 131.459564] kernel BUG at /build/buildd/linux-3.2.0/mm/slub.c:3430!
[ 131.459660] invalid opcode: 0000 [#1] SMP
[ 131.459738] CPU 5
[ 131.459771] Modules linked in: ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables bridge stp xen_gntdev xen_netback xen_blkback xen_evtchn xenfs microcode usbhid hid usb_storage uas xfs radeon ttm drm_kms_helper drm ipmi_si ipmi_msghandler i2c_algo_bit psmouse i7core_edac bonding edac_core hpilo serio_raw shpchp acpi_power_meter mac_hid lp parport tg3 hpsa
[ 131.460775]
[ 131.460802] Pid: 1649, comm: sh Tainted: G W 3.2.0-27-generic #43-Ubuntu HP ProLiant ML350 G6
[ 131.460996] RIP: e030:[<ffffffff81162505>] [<ffffffff81162505>] kfree+0x135/0x140
[ 131.461121] RSP: e02b:ffff88003126dd48 EFLAGS: 00010246
[ 131.461203] RAX: 0000000000000000 RBX: ffff880000000000 RCX: 0000000000000000
[ 131.461311] RDX: ffffffff7fffffff RSI: 0000000000000000 RDI: ffff880000000000
[ 131.465056] RBP: ffff88003126dd78 R08: ffffea0000000000 R09: ffff880000000000
[ 131.468879] R10: 0000000000000000 R11: 000...

Jesús Lara, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
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 Links:
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

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

This is affecting me on a fresh install on a TravelMate 5520.

The live CD works fine, but attempting to boot to the installed OS leads to the 'fixing recursive fault but reboot is needed' error during the boot sequence.

No combination of 'noapic', 'xforcevesa', 'acpi=off', 'nomodeset' helped.

I tried fresh installs of 12.04.02 and 13.04, with no luck.

MikeyB, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the official Ubuntu documentation:
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices
Ubuntu Community: https://wiki.ubuntu.com/ReportingBugs

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

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

This issue is also occurring on Dell Latitude 131L. Second time I installed 12.04 and the issue is definitely with the broadcom drivers. When I activated it and rebooted, that's when the issue started to occur.

I'm receiving the same errors as Jesus Lara @ comment #51
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/775950/comments/51

But same results as MikeyB @ comment #54
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/775950/comments/54

I tried editing the boot menu and adding

noapic xforcevesa acpi=off nomodeset

Resulted in the same recursive error, reboot required. Any suggestions? I'm thinking about downgrading to 10.04 or switching to BSD to boot up my old computer. There must have been some kind of regression if this used to work fine..

rbhatia, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report 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.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.