Re: RE: RE: RE: [Xen-devel] AGP problems with 2.0.5

[Kurt Garloff <kurt@xxxxxxxxxx>]

Hi Ian,

On Sun, Mar 13, 2005 at 09:07:29PM -0000, Ian Pratt wrote:
> One idea might be to disable writeable page tables so that faults get
> reported synchronously, and hence more likely to avoid the need to call
> domain_crash. The easiest way of doing this on the unstable tree right
> now is to enable SMP in the guest config. There's more chance of getting
> an oops message.

It produced an Oops, indeed.

Failed to execute MMU updates.
------------[ cut here ]------------
kernel BUG at <bad filename>:53227!
invalid operand: 0000 [#1]
PREEMPT SMP
Modules linked in: radeon drm netconsole usbserial parport_pc lp parport
edd sg st sr_mod nvram snd_seq_oss snd_seq_midi_event snd_seq
snd_seq_device snd_pcm_oss snd_mixer_oss radeonfb i2c_algo_bit
cfbcopyarea cfbimgblt cfbfillrect i2c_core snd_intel8x0 snd_ac97_codec
snd_pcm snd_timer snd soundcore snd_page_alloc intel_agp agpgart
uhci_hcd ehci_hcd evdev pcmcia yenta_socket rsrc_nonstatic pcmcia_core
usbcore ipt_MASQUERADE ipt_tos ipt_MARK ipt_length sch_htb ipt_TCPMSS
ipt_TOS ipt_state ipt_LOG ipt_REJECT iptable_mangle iptable_filter
ip_nat_ftp iptable_nat ip_conntrack_ftp ip_conntrack ip_tables e100
ppp_generic slhc rtc nls_cp437 vfat fat dm_mod serial_core
CPU:    0
EIP:    0061:[<c0116daa>]    Not tainted VLI
EFLAGS: 00010286   (2.6.11-xen0)
EIP is at xen_l1_entry_update+0xea/0xf0
eax: 00000022   ebx: c1387560   ecx: fbffc000   edx: d1c11e74
esi: 00ef3f60   edi: 00ef3f60   ebp: 00ef3f60   esp: d1c11e70
ds: 007b   es: 007b   ss: 0069
Process X (pid: 19601, threadinfo=d1c10000 task=d0ba5580)
Stack: c03b16dc 00000000 00ba1027 000d0008 00016000 d9895058 0010f000 c0149e77
       b5d0efff 0010f000 b5c00000 000cfff2 0000e000 d1ee3b5c 0010f000 b5c00000
       000cfff2 0000e000 d1ee3b5c d221fd40 000002d7 d221fd00 b5d0f000 b5d0f000
Call Trace:
 [<c0149e77>] remap_pfn_range+0x237/0x310
 [<dceb222a>] drm_mmap+0x20a/0x274 [drm]
 [<c014d51c>] get_unmapped_area+0x9c/0xd0
 [<c014ce4f>] do_mmap_pgoff+0x36f/0x770
 [<dceaa400>] drm_addmap+0x0/0x480 [drm]
 [<dceadf05>] drm_ioctl+0x115/0x206 [drm]
 [<c01124ae>] old_mmap+0xce/0x110
 [<c01099df>] syscall_call+0x7/0xb
Code: 24 04 b8 a8 90 3f c0 8b 5c 24 0c 8b 74 24 10 8b 7c 24 14 8b 6c 24
18 83 c4 1c e9 02 bf 27 00 c7 04 24 dc 16 3b c0 e8 66 81 00 00 <0f> 0b
eb cf 89 f6 83 ec 1c 89 5c 24 0c bb 08 36 49 c0 89 74 24
 <6>note: X[19601] exited with preempt_count 2
scheduling while atomic: X/0x00000002/19601
 [<c03913c5>] schedule+0x915/0xb60
 [<c010fe60>] do_IRQ+0x40/0x70
 [<c0105d8e>] evtchn_do_upcall+0x5e/0xb0
 [<c0109c09>] hypervisor_callback+0x31/0x3c
 [<c0392369>] rwsem_down_read_failed+0x99/0x190
 [<c0122950>] .text.lock.exit+0x27/0x87
 [<c01213b6>] do_exit+0x96/0x330
 [<c010a465>] die+0x185/0x190
 [<c010a535>] do_trap+0xc5/0xf0
 [<c010a780>] do_invalid_op+0x0/0xa0
 [<c010a813>] do_invalid_op+0x93/0xa0
 [<c0116daa>] xen_l1_entry_update+0xea/0xf0
 [<c013393b>] autoremove_wake_function+0x1b/0x50
 [<c011a727>] __wake_up_common+0x37/0x70
 [<c011a798>] __wake_up+0x38/0x50
 [<c0109bd3>] error_code+0x4b/0x50
 [<c0116daa>] xen_l1_entry_update+0xea/0xf0
 [<c0149e77>] remap_pfn_range+0x237/0x310
 [<dceb222a>] drm_mmap+0x20a/0x274 [drm]
 [<c014d51c>] get_unmapped_area+0x9c/0xd0
 [<c014ce4f>] do_mmap_pgoff+0x36f/0x770
 [<dceaa400>] drm_addmap+0x0/0x480 [drm]
 [<dceadf05>] drm_ioctl+0x115/0x206 [drm]
 [<c01124ae>] old_mmap+0xce/0x110
 [<c01099df>] syscall_call+0x7/0xb

Note that the radeonfb driver manages to mess up the display already,
which does not happen on xen-2.0-testing, where radeonfb works.

Regards,
-- 
Kurt Garloff                   <kurt@xxxxxxxxxx>             [Koeln, DE]
Physics:Plasma modeling <garloff@xxxxxxxxxxxxxxxxxxx> [TU Eindhoven, NL]
Linux: SUSE Labs (Director)    <garloff@xxxxxxx>            [Novell Inc]

pgply1WxBPRcz.pgp
Description: PGP signature