Attachment 4335 Details for Bug 5569 – output of /var/log/messages

output of /var/log/messages

messages.log (text/x-log), 1.54 KB, created by Steffen Schwientek on 2006-01-13 09:35:35 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Steffen Schwientek

Created: 2006-01-13 09:35:35 UTC

Size: 1.54 KB

patch

obsolete

>Jan 12 23:21:45 thinkpad kernel: ACPI: PCI interrupt for device 0000:02:00.0 disabled
>Jan 12 23:21:52 thinkpad kernel: [drm] Initialized drm 1.0.1 20051102
>Jan 12 23:21:52 thinkpad kernel: ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
>Jan 12 23:21:52 thinkpad kernel: [drm] Initialized savage 2.4.1 20050313 on minor 0: 
>Jan 12 23:21:52 thinkpad kernel: mtrr: base(0xf2000000) is not aligned on a size(0x5000000) boundary
>Jan 12 23:21:52 thinkpad kernel: agpgart: Found an AGP 1.0 compliant device at 0000:00:00.0.
>Jan 12 23:21:52 thinkpad kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 2x mode
>Jan 12 23:21:52 thinkpad kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 2x mode
>Jan 12 23:23:01 thinkpad kernel: [drm]    status=0x00010407, e=0x041d
>Jan 12 23:23:02 thinkpad kernel:  [<c0133c87>] bad_page+0x5c/0x92
>Jan 12 23:23:02 thinkpad kernel:  [<c013436d>] free_hot_cold_page+0x5a/0xe9
>Jan 12 23:23:02 thinkpad kernel:  [<c013c53b>] zap_pte_range+0x164/0x1ea
>Jan 12 23:23:02 thinkpad kernel:  [<c013c660>] unmap_page_range+0x9f/0xed
>Jan 12 23:23:02 thinkpad kernel:  [<c013c775>] unmap_vmas+0xc7/0x18c
>Jan 12 23:23:02 thinkpad kernel:  [<c01402a1>] exit_mmap+0x5b/0xd1
>Jan 12 23:23:02 thinkpad kernel:  [<c0114631>] mmput+0x20/0x7d
>Jan 12 23:23:02 thinkpad kernel:  [<c011844e>] do_exit+0x16c/0x368
>Jan 12 23:23:02 thinkpad kernel:  [<c0118706>] sys_exit_group+0x0/0x11
>Jan 12 23:23:02 thinkpad kernel:  [<c011fecc>] get_signal_to_deliver+0x287/0x2ac
>Jan 12 23:23:02 thinkpad kernel:  [<c01029ca>] do_signal+0x4f/0xcc

Actions: View

Attachments on bug 5569: 4334 | 4335

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.