WARNING: at /build/buildd/linux-2.6.31/fs/quota/dquot.c:964 dquot_claim_space+0x84/0x130()

Bug #442799 reported by Almas
56
This bug affects 12 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

x86 Ubuntu Jaunty 9.04 upgraded to Karmic 9.10 beta.

There is an attention: "Crash report detected" Then saying. And then said "Your system encountered a serious kernel problem".
I restarted few times. But problem still there.

Please fix this.

ProblemType: KernelOops
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices: aplay: device_list:223: no soundcards found...
Architecture: i386
ArecordDevices: arecord: device_list:223: no soundcards found...
Date: Mon Oct 5 02:08:43 2009
DistroRelease: Ubuntu 9.10
Failure: oops
MachineType: Kobian PI945GCM
Package: linux-image-2.6.31-11-generic 2.6.31-11.38
ProcCmdLine: root=UUID=13212a4c-b807-48be-82c4-5e540cf57224 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.31/fs/quota/dquot.c:964 dquot_claim_space+0x84/0x130()
Uname: Linux 2.6.31-11-generic i686
dmi.bios.date: 05/08/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080012
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: PI945GCM
dmi.board.vendor: Kobian
dmi.board.version: ECS
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Kobian
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd05/08/2007:svnKobian:pnPI945GCM:pvr1.X:rvnKobian:rnPI945GCM:rvrECS:cvnKobian:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: PI945GCM
dmi.product.version: 1.X
dmi.sys.vendor: Kobian

Revision history for this message
Almas (almasd) wrote :
Revision history for this message
Almas (almasd) wrote :

screenshot

Revision history for this message
Almas (almasd) wrote :

"Crash report detected"
"Your system encountered a serious kernel problem"

Didn't resolved yet. I think that it's related with Intel HDA Audio hardware (with sigmatel chip?) bug. On windows this is detected that named "HDT audio". It was OK on jaunty.

Changed in linux (Ubuntu):
assignee: nobody → Alex (kernelspanic)
assignee: Alex (kernelspanic) → darkrevival (kernel)
assignee: darkrevival (kernel) → Canonical Kernel Team (canonical-kernel-team)
Revision history for this message
Almas (almasd) wrote :

Didn't fixed yet on

Kernel Linux 2.6.31-13-generic
GNOME 2.28

Revision history for this message
Manus (manus) wrote :
Download full text (3.4 KiB)

Nov 18 23:16:26 ns***** kernel: ------------[ cut here ]------------
Nov 18 23:16:26 ns***** kernel: WARNING: at fs/quota/dquot.c:964 dquot_claim_space+0x151/0x180()
Nov 18 23:16:26 ns***** kernel: Hardware name:
Nov 18 23:16:26 ns***** kernel: Pid: 393, comm: pdflush Tainted: G W 2.6.31.5-grsec-xxxx-grs-ipv6-64 #2
Nov 18 23:16:26 ns***** kernel: Call Trace:
Nov 18 23:16:26 ns***** kernel: [<ffffffff818e499c>] ? __down_read+0x1c/0xbb
Nov 18 23:16:26 ns***** kernel: [<ffffffff8113d491>] ? dquot_claim_space+0x151/0x180
Nov 18 23:16:26 ns***** kernel: [<ffffffff8106a053>] warn_slowpath_common+0x73/0xc0
Nov 18 23:16:26 ns***** kernel: [<ffffffff8106a0af>] warn_slowpath_null+0xf/0x20
Nov 18 23:16:26 ns***** kernel: [<ffffffff8113d491>] dquot_claim_space+0x151/0x180
Nov 18 23:16:26 ns***** kernel: [<ffffffff811e062b>] ext4_mb_mark_diskspace_used+0x39b/0x3b0
Nov 18 23:16:26 ns***** kernel: [<ffffffff811dfafc>] ? ext4_mb_initialize_context+0x7c/0x170
Nov 18 23:16:26 ns***** kernel: [<ffffffff811e348d>] ext4_mb_new_blocks+0x2bd/0x440
Nov 18 23:16:26 ns***** kernel: [<ffffffff811d8aeb>] ? ext4_ext_find_extent+0x13b/0x2f0
Nov 18 23:16:26 ns***** kernel: [<ffffffff811da6c5>] ext4_ext_get_blocks+0x5b5/0xff0
Nov 18 23:16:26 ns***** kernel: [<ffffffff81469afa>] ? __make_request+0x25a/0x3e0
Nov 18 23:16:26 ns***** kernel: [<ffffffff81467cd7>] ? generic_make_request+0x207/0x320
Nov 18 23:16:26 ns***** kernel: [<ffffffff818e48cc>] ? __down_write_nested+0x1c/0xc0
Nov 18 23:16:26 ns***** kernel: [<ffffffff818e499c>] ? __down_read+0x1c/0xbb
Nov 18 23:16:26 ns***** kernel: [<ffffffff811c5419>] ext4_get_blocks+0x1f9/0x370
Nov 18 23:16:26 ns***** kernel: [<ffffffff811c5915>] mpage_da_map_blocks+0xc5/0x7e0
Nov 18 23:16:26 ns***** kernel: [<ffffffff810b8652>] ? pagevec_lookup_tag+0x22/0x30
Nov 18 23:16:26 ns***** kernel: [<ffffffff810b67a2>] ? write_cache_pages+0x132/0x470
Nov 18 23:16:26 ns***** kernel: [<ffffffff811c6590>] ? __mpage_da_writepage+0x0/0x190
Nov 18 23:16:26 ns***** kernel: [<ffffffff811f1317>] ? jbd2_journal_stop+0x217/0x290
Nov 18 23:16:26 ns***** kernel: [<ffffffff811c631d>] ext4_da_writepages+0x2ed/0x490
Nov 18 23:16:26 ns***** kernel: [<ffffffff810b6b38>] do_writepages+0x28/0x50
Nov 18 23:16:26 ns***** kernel: [<ffffffff8110ab1b>] writeback_single_inode+0x1db/0x480
Nov 18 23:16:26 ns***** kernel: [<ffffffff8105d298>] ? dequeue_entity+0x18/0x1a0
Nov 18 23:16:26 ns***** kernel: [<ffffffff8105e205>] ? dequeue_task_fair+0x45/0xb0
Nov 18 23:16:26 ns***** kernel: [<ffffffff8110b2e1>] generic_sync_sb_inodes+0x2e1/0x4c0
Nov 18 23:16:26 ns***** kernel: [<ffffffff8110b59f>] writeback_inodes+0x4f/0xf0
Nov 18 23:16:26 ns***** kernel: [<ffffffff810b6cec>] wb_kupdate+0xbc/0x140
Nov 18 23:16:26 ns***** kernel: [<ffffffff810b7ac0>] ? pdflush+0x0/0x250
Nov 18 23:16:26 ns***** kernel: [<ffffffff810b7c0c>] pdflush+0x14c/0x250
Nov 18 23:16:26 ns***** kernel: [<ffffffff810b6c30>] ? wb_kupdate+0x0/0x140
Nov 18 23:16:26 ns***** kernel: [<ffffffff81082f56>] kthread+0xa6/0xc0
Nov 18 23:16:26 ns***** kernel: [<ffffffff8102de3a>] child_rip+0xa/0x20
Nov 18 23:16:26 ns***** kernel: [<fffff...

Read more...

Revision history for this message
Kamilion (kamilion) wrote :

Disk quotas are on and you're using EXT4.

Disable quotas to stop the OOPS messages:

sudo quotaoff -a -f

Disable quotas in your /etc/fstab if you're not using them.

Example:

# / was on /dev/sda2 during installation
UUID=acee041c-a2a8-4ca4-9b51-19aa423f122e / ext4 errors=remount-ro,usrquota,grpquota 0 1

Remove usrquota and grpquota if they exist.

# / was on /dev/sda2 during installation
UUID=acee041c-a2a8-4ca4-9b51-19aa423f122e / ext4 errors=remount-ro 0 1

Revision history for this message
Almas (almasd) wrote :

Solved:

I parallel fresh installed ubuntu 9.10 on new partition without delete my old upgraded installation.
And then I rebooted and start with my old installation. There was surprise, kernel oops problem had gone away.
After that I deleted new installation and partition then I recover my grub2. Now my upgraded old Ubuntu installation is working charm :)

I think that its grub2 boot problem. Try to reinstall and recover grub2.

Revision history for this message
Almas (almasd) wrote :

Oh sorry I forgot I edited fstab like this:
/ ext4 relatime,errors=remount-ro,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 0 1

Revision history for this message
peraniy (info-balsoft) wrote :

Give FStab to this type:
/ Ext4 relatime, errors = remount-ro, usrquota, grpquota 0 1

And this error will disappear. This happens after upgrading the kernel.

Brad Figg (brad-figg)
tags: added: acpi-table-checksum
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Fix Releasing per OR indication that this issue is now resolved for them. Removed team assignment.

~JFo

Changed in linux (Ubuntu):
status: New → Fix Released
assignee: Canonical Kernel Team (canonical-kernel-team) → nobody
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.