Sometimes I get a Kernel panic during system startup

Bug #706032 reported by Lucazade
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Sometimes I get a Kernel panic during system startup.
It hangs after grub or when plymouth appears.
This issue happens only with Natty, never experienced before (from feisty fawn)

Looks similiar to this forum post:
http://ubuntuforums.org/showpost.php?p=10383469&postcount=4

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.37-12-generic 2.6.37-12.26
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: luca 1242 F.... pulseaudio
CRDA: Error: [Errno 2] File o directory non esistente
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xf7f78000 irq 21'
   Mixer name : 'Realtek ALC662 rev1'
   Components : 'HDA:10ec0662,10438290,00100101'
   Controls : 34
   Simple ctrls : 18
Date: Fri Jan 21 20:03:32 2011
Frequency: Once every few days.
HibernationDevice: RESUME=UUID=d1912aa1-c543-4653-aa5c-0ac1eb40a1c3
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110121)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=it_IT.UTF-8:it:en_GB:en
 LANG=it_IT.UTF-8
 LC_MESSAGES=it_CH.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.37-12-generic root=UUID=102112c2-b0dc-42eb-a81f-60717504dd6f ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.37-12-generic N/A
 linux-backports-modules-2.6.37-12-generic N/A
 linux-firmware 1.45
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 05/07/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1401
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4N78 SE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd05/07/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78SE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Lucazade (lucazade) wrote :
Revision history for this message
Lucazade (lucazade) wrote :
Revision history for this message
Lucazade (lucazade) wrote :
Revision history for this message
Lucazade (lucazade) wrote :
Revision history for this message
Lucazade (lucazade) wrote :
Revision history for this message
Lucazade (lucazade) wrote :
Revision history for this message
Lucazade (lucazade) wrote :
Revision history for this message
Lucazade (lucazade) wrote :

this kernel panic is present also using 2.6.38rc from kernel ppa

Revision history for this message
Lucazade (lucazade) wrote :
Revision history for this message
zeruke (oninekoze) wrote :

im having the same problem and this seems to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/693828

Revision history for this message
Lucazade (lucazade) wrote :

@zeruke
thanks for pointing this out! subscribed.

Revision history for this message
Lucazade (lucazade) wrote :

I don't have this issue anymore.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/706032/comments/12
"I don't have this issue anymore."
linux (Ubuntu) -> Invalid

Changed in linux (Ubuntu):
status: Confirmed → Invalid
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.