Installed 9.10, system hung when I tried to install Broadcom driver.

Bug #468422 reported by Mik
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

1st attempt installing 9.10 Karmic Koala on a Vista Home Premium laptop (Acer 2920z), I load up Ubuntu, do a search for hardware drivers to install. 2 entries for Broadcom appear. Installing the first (the one that mentions Firmware something or other) causes a kernel panic, and I'm locked out of the OS.

Can't get back into Ubuntu, even in safe mode, do a fresh install, try installing the 2nd Broadcom driver this time, nothing happens, the "downloading and installing" progress bar continues to move, but there's no disk movement. Stays the same for a further 10+ minutes, I click the Crash Report logo icon that has now appeared, and end up typing this.

Disappointed, previously used 8.1 on this laptop, and was hoping 9.1 would finally be the answer. Seems I'm back to using Vista now, until I can have a stable and wireless enabled laptop running linux : (

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mik 1767 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc200000 irq 22'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,10250135,00100003 HDA:11c11040,10250100,00100200'
   Controls : 21
   Simple ctrls : 12
Date: Sun Nov 1 11:50:14 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=edbce27a-1368-4fbd-96b6-0bd6e12ac3a0
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Acer Aspire 2920
NonfreeKernelModules: wl
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=4bbcd93e-c6d6-454b-a242-ea9bfe27cee3 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
SourcePackage: linux
Tags: kernel-oops
Title: BUG: unable to handle kernel NULL pointer dereference at (null)
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 02/14/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.13
dmi.board.name: Calado
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.asset.tag: None
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.13:bd02/14/2008:svnAcer:pnAspire2920:pvr0100:rvnAcer:rnCalado:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 2920
dmi.product.version: 0100
dmi.sys.vendor: Acer

Revision history for this message
Mik (mik395) wrote :
Revision history for this message
Norbert Schultz (zaiib) wrote :

On my Macbook 3,1 I also had a hard lockup after installing the broadcom STA driver. Although rebooting seems to work and I can use wifi right now.

Tested it two times; hard lock during installation, hard lock during LiveCD usage.

Revision history for this message
dhaus (dhaus111) wrote :

I'm having a similar problem. I'm using broadcom 4328 rev 03 (14e4:4328) on a fresh install on my dell m1530. After manually installing b43-fwcutter i managed to get Hardware Drivers to cooperate and acknowledge the install and activate the driver. I get a listing of wireless networks but soon after I get a kernel panic and a hard lockup. On my first attempted fresh install after a few of those kernel panics, it actually stopped booting. It gave me a VFS something-rather kernel panic that I mistook for filesystem damage and just resorted to a reformat. I've installed the bcmwl-kernel-source package and reinstalled it several times, rebooted. Might be resorting to Ndiswrapper here soon, but I really don't want to have to do that. I'm open to suggestions, but at least wanted to speak up about this problem.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Mik,

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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 468422

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.