public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivan Gyurdiev <ivg2@cornell.edu>
To: linux-kernel@vger.kernel.org
Cc: arjanv@redhat.com
Subject: Invalid paging request (cfq_get_queue)
Date: Fri, 09 Jul 2004 10:42:30 -0600	[thread overview]
Message-ID: <1089391350.7132.5.camel@localhost.bluenet> (raw)

[-- Attachment #1: Type: text/plain, Size: 2712 bytes --]

Rawhide, 2.6.7-1.476 (and I was just trying to get to 478, but here's
what happened instead)

Unable to handle kernel paging request at virtual address 6b6b6b6b
 printing eip:
022387e1
*pde = 00000000
Oops: 0000 [#1]
Modules linked in: snd_mixer_oss nvidia snd_seq_midi snd_seq_midi_event
snd_seq snd_via82xx snd_ac97_codec snd_pcm snd_timer snd_page_alloc
gameport snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore ipv6
usbserial parport_pc lp parport iptable_filter ip_tables via_rhine mii
floppy sg scsi_mod nls_ascii vfat fat ext3 jbd dm_mod usblp uhci_hcd
button battery asus_acpi ac xfs
CPU:    0
EIP:    0060:[<022387e1>]    Tainted: P
EFLAGS: 00210202   (2.6.7-1.476)
EIP is at cfq_get_queue+0x28/0x98
eax: 6b6b6b6b   ebx: 0000000b   ecx: 09e901a4   edx: 6b6b6b6b
esi: 00001b58   edi: 00000220   ebp: 09e0f1b4   esp: 08fa9ba8
ds: 007b   es: 007b   ss: 0068
Process yum (pid: 7000, threadinfo=08fa9000 task=02ab8d90)
Stack: 09e0f1b4 00000220 090e2f14 09eccb0c 02238ae1 02238ac1 090e2f14
00000000
       0222fb5b 09ea291c 02231610 09ea29a8 00000220 00000020 00000000
09ea291c
       00000020 00000008 0223250e 013fa477 00000000 00000000 00000000
00000000
Call Trace:
 [<02238ae1>] cfq_set_request+0x20/0x63
 [<02238ac1>] cfq_set_request+0x0/0x63
 [<0222fb5b>] elv_set_request+0xa/0x17
 [<02231610>] get_request+0x281/0x44e
 [<0223250e>] __make_request+0x382/0x5c3
 [<02188ff0>] mpage_end_io_read+0x0/0x5e
 [<022328dd>] generic_make_request+0x18e/0x19e
 [<02188ff0>] mpage_end_io_read+0x0/0x5e
 [<02232991>] submit_bio+0xa4/0xac
 [<0a911d23>] linvfs_get_block+0x13/0x17 [xfs]
 [<02188ff0>] mpage_end_io_read+0x0/0x5e
 [<021890bb>] mpage_bio_submit+0x19/0x1d
 [<02189408>] do_mpage_readpage+0x259/0x342
 [<022328dd>] generic_make_request+0x18e/0x19e
 [<0a910b86>] kmem_zone_alloc+0x3b/0x70 [xfs]
 [<0a8c5095>] xfs_attr_leaf_get+0x24/0x82 [xfs]
 [<02188ff0>] mpage_end_io_read+0x0/0x5e
 [<02232991>] submit_bio+0xa4/0xac
 [<02189582>] mpage_readpages+0x91/0xf9
 [<0a911d10>] linvfs_get_block+0x0/0x17 [xfs]
 [<02142180>] __rmqueue+0xbb/0x106
 [<0a911e69>] linvfs_readpages+0x12/0x14 [xfs]
 [<0a911d10>] linvfs_get_block+0x0/0x17 [xfs]
 [<0214554d>] read_pages+0x2d/0xd0
 [<0214279c>] buffered_rmqueue+0x1dd/0x200
 [<02142861>] __alloc_pages+0xa2/0x283
 [<02145b8d>] do_page_cache_readahead+0x29a/0x2ba
 [<0213f553>] filemap_nopage+0x10e/0x287
 [<0215039d>] do_no_page+0xfd/0x434
 [<021bf461>] inode_has_perm+0x57/0x5f
 [<021508c9>] handle_mm_fault+0xe4/0x21e
 [<021191f4>] do_page_fault+0x16e/0x49c
 [<02161451>] vfs_read+0xda/0xe2
 [<02119086>] do_page_fault+0x0/0x49c
Code: 8b 02 0f 18 00 90 39 ca 74 0d 39 72 14 75 04 89 d0 eb 06 8b


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2004-07-09 16:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1089391350.7132.5.camel@localhost.bluenet \
    --to=ivg2@cornell.edu \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox