[Solved for me]Kernel Panic not syncing fatal exception in interrupt-solved for me, firmware-b43-lpphy-installer instead of b43-firmware solves the panic

[Martin-knoflach]

I am running into troubles since 13.04 on my Dell Studio 1749. I get sudden kernel Panics on original x ati drivers and system freezes on fglrx-updates. fglrx states unsupported hardware

i did a screenir of my problem

http://s14.directupload.net/images/130517/3l2en6mw.jpg

Anything else u need, just let me know

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Brad Figg (brad-figg)]

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

apport-collect 1181392

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.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.10 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

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

[Martin-knoflach (martin-knoflach)]

I sure will try that. Think ill do resetup on friday evening. Just Fyi, im on Archlinux now on Kernel 3.9 without any trouble, so a failure of the hardware can be excluded from the run. Thank you for your support and any inconvenience

[Martin-knoflach (martin-knoflach)]

Ok i found the trouble:

Since Kernel 3.8.x the Broadcom drivers, that are recommended by additional drivers cause the kernel panics. Simce i have a 14e4 4315 chipset (Broadcom 4312) card, i needed to install firmware-b43-lpphy-installer by hand. This solved my crashes. Just waas a bit tricky as i never had that in 3.6 or 3.5 kernels, where i could use the shown proprietary drivers

Bug can be closed or marked as solved even though i dont know, what in the broadcom proprietary driver causes the panic

greetins
Martin

[Martin-knoflach (martin-knoflach)]

i add here a screenie of the panic for further investigation

http://s1.directupload.net/images/130530/pqrvetxb.jpg

[NoBugs! (luke32j)]

I had no problems with my broadcom card in the last year or two, but I just got this Kernel Panic not syncing fatal exception in interrupt error, this was awhile after running the updates.

Now it won't boot up Ubuntu - I managed to get it to boot Ubuntu 10 livecd, and checked memory to be ok. I booted the Mac OS partition that came with it, and the graphics were smaller resolution in the top left of the screen, and messed up.

I wonder if this is related to hardware failure, this was on an older macbook.

[penalvch (penalvch)]

NoBugs!, 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 Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team 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.

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

Thank you for your understanding.

[penalvch (penalvch)]

Martin-knoflach, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1181392/comments/5 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.