WARNING: at /build/buildd/linux-2.6.31/fs/buffer.c:1152 mark_buffer_dirty+0x70/0x90()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xdfef8000 irq 19'
Mixer name : 'Realtek ALC662 rev1'
Components : 'HDA:10ec0662,
Controls : 33
Simple ctrls : 17
Date: Tue Oct 27 15:47:19 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-14-generic i686
WpaSupplicantLog:
dmi.bios.date: 12/19/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0410
dmi.board.
dmi.board.name: P5GC-MX/1333
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 433365, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.