* Linux 3.8-rc4
@ 2013-01-18 3:51 Linus Torvalds
2013-01-18 17:51 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Linus Torvalds @ 2013-01-18 3:51 UTC (permalink / raw)
To: Linux Kernel Mailing List
Hey, it's been another week already! In fact, it took me so much by
surprise that it's been an extra day. The whole "release in the middle
of the week" thing feels odd to me.
[ That actually got me to wonder what the most common day was, and
statistically I definitely do most releases on Sunday. The "git tip of
the week" looks like this:
git log --no-walk --pretty="%ad" $(git tag -l)
which can then be piped into
cut -d' ' -f1 | sort | uniq -c | sort -n
to see the full git tagging statistics ]
Anyway, with that digression, I can happily report that -rc4 is
smaller than -rc3 despite the extra day, although not by much. There's
not really a whole lot that stands out: apart from one new wireless
driver (the Atheros Wilocity driver) and some OMAP drm changes, the
diffstat looks pretty flat and spread out. Which just means lots of
small changes all over.
The ShortLog is appended, but it's basically 85% drivers, with over
half the patch being to the aforementioned new wireless one and the
OMAP drm changes. There's some other stuff there too, but it's largely
in the noise - small ARM and s390 updates (and a smattering of SuperH
and x86), a few tiny filesystem fixes, things like that.
Go forth and test. My gut feel is that things really are calming down.
And I'd hate to be proven wrong.
Linus
---
Afzal Mohammed (1):
usb: musb: dsps: header movement build error fix
Alan Stern (1):
USB: usbtest: fix test number in log message
Aleksi Torhamo (2):
drm/nouveau/clock: fix support for more than 2 monitors on nve0
drm/nvc0/fb: fix crash when different mutex is used to protect same list
Alexander Holler (1):
iio: hid-sensors: respect CONFIG_IIO_TRIGGER
Alexey Khoroshilov (1):
mei: fix mismatch in mutex unlock-lock in mei_amthif_read()
Amerigo Wang (1):
qlge: remove NETIF_F_TSO6 flag
Amitkumar Karwar (1):
mwifiex: fix typo in setting up ibss network parameters
Anatolij Gustschin (3):
USB: fix fsl_otg config dependency
USB: fsl-mph-dr-of: fix regression on mpc5121e
USB: ehci-fsl: fix regression on mpc5121e
Andre Schramm (1):
ALSA: hdspm - Fix wordclock status on AES32
Andreas Fleig (1):
USB: Add device quirk for Microsoft VX700 webcam
Andreas Schwab (1):
KVM: PPC: Book3S HV: Fix compilation without CONFIG_PPC_POWERNV
Andrew Morton (3):
drivers/rtc/rtc-da9055.c: fix cross-section reference
arch/mn10300/Kconfig: select CONFIG_GENERIC_ATOMIC64
kernel/audit.c: avoid negative sleep durations
Axel Lin (17):
ASoC: sta529: Fix update register bits in sta529_set_dai_fmt
ASoC: wm2200: Fix setting dai format in wm2200_set_fmt
ASoC: lm49453: Fix mask for setting mode bit in lm49453_set_dai_fmt()
ASoC: arizona: Do proper shift for setting AIF rate
ASoC: cs42l52: Catch no-match case in cs42l52_get_clk
regulator: core: Fix continuous_voltage_range case in
regulator_can_change_voltage
iio: adc: ad7266: Don't set error code to st->vref_uv
iio: dac: ad5380: Don't set error code to st->vref
iio: dac: ad5791: Don't set error code to [pos|neg]_voltage_uv
iio: dac: ad5504: Don't set error code to voltage_uv
iio: dac: ad5624r_spi: Don't set error code to voltage_uv
iio: dac: ad5686: Don't set error code to voltage_uv
iio: dac: ad5446: Don't set error code to voltage_uv
regulator: core: Fix comment for regulator_register()
regulator: max8997: Use uV in voltage_map_desc
regulator: max8998: Use uV in voltage_map_desc
regulator: max8998: Ensure enough delay time for
max8998_set_voltage_buck_time_sel
Barak Witkowski (1):
bnx2x: Allow management traffic after boot from SAN
Ben Hutchings (1):
asus-laptop: Do not call HWRS on init
Ben Skeggs (2):
drm/nouveau/devinit: ensure legacy vga control is enabled during post
drm/nouveau: do not forcibly power on lvds panels
Bharat Bhushan (1):
powerpc: Corrected include header path in kvm_para.h
Bing Zhao (1):
mwifiex: check wait_event_interruptible return value
Bjørn Mork (2):
USB: option: blacklist network interface on ZTE MF880
USB: option: add Telekom Speedstick LTE II
Bo Shen (2):
ARM: at91/dts: add pinctrl support for SSC peripheral
ASoC: atmel-ssc: add pinctrl selection to driver
Brian Foster (1):
xfs: remove int casts from debug dquot soft limit timer asserts
Chaitanya (1):
mac80211: fix maximum MTU
Chao Xie (3):
usb: gadget: mv_udc: fix the clk APIs
usb: host: ehci-mv: fix clk APIs
usb: otg: mv_otg: fix the clk APIs
Chen Gang (2):
drivers/net/wireless/iwlegacy: use strlcpy instead of strncpy
MAINTAINERS: Omar had moved
Chris Wilson (6):
drm/i915; Only increment the user-pin-count after successfully
pinning the bo
drm/i915: Treat crtc->mode.clock == 0 as disabled
drm: Only evict the blocks required to create the requested hole
drm/i915: The sprite scaler on Ironlake also support YUV planes
drm/i915: Add DEBUG messages to all
intel_create_user_framebuffer error paths
drm/i915: Use pixel size for computing linear offsets into a sprite
Christian Borntraeger (1):
s390/kvm: Fix BUG in include/linux/kvm_host.h:745
Chuansheng Liu (3):
ASoC: core: fix the memory leak in case of device_add() failure
ASoC: core: fix the memory leak in case of remove_aux_dev()
mfd, TWL4030: TWL4030 need select REGMAP_I2C
Cong Wang (1):
net: prevent setting ttl=0 via IP_TTL
Dan Carpenter (1):
bnx2x: move debugging code before the return
Daniel Lezcano (1):
cpuidle: remove the power_specified field in the driver
Daniel Mack (2):
ASoC: cs4271: fix sparse warning
ASoC: cs4271: fix property check
Daniel Vetter (2):
Revert "drm/i915: no lvds quirk for Zotac ZDBOX SD ID12/ID13"
drm/i915: Revert shrinker changes from "Track unbound pages"
Dave Reisner (1):
debugfs: convert gid= argument from decimal, not octal
David Decotigny (1):
lib: cpu_rmap: avoid flushing all workqueues
David Henningsson (2):
Revert "ALSA: hda - Shut up pins at power-saving mode with
Conexnat codecs"
ALSA: usb - fix race in creation of M-Audio Fast track pro driver
David S. Miller (1):
sparc: Hook up finit_module syscall.
Denis N Ladin (1):
USB: cdc-acm: Add support for "PSC Scanning, Magellan 800i"
Dzianis Kahanovich (1):
USB: option: add Nexpring NP10T terminal id
Eldad Zack (3):
ALSA: usb-audio: correct M-Audio C400 clock source quirk
ALSA: usb-audio: M-Audio FT C400 skip packet quirk
ALSA: usb-audio: selector map for M-Audio FT C400
Emil Goode (1):
Staging: wlan-ng: Add missing argument
Emmanuel Grumbach (1):
iwlwifi: fix the reclaimed packet tracking upon flush queue
Enric Balletbo i Serra (1):
staging: tidspbridge: Fix build breakage due to splitting CM functions.
Eric Dumazet (3):
tcp: splice: fix an infinite loop in tcp_read_sock()
tcp: fix splice() and tcp collapsing interaction
tcp: accept RST without ACK flag
Éric Piel (1):
staging: comedi: fix minimum AO period for NI 625x and NI 628x
Eric Sandeen (2):
jbd: don't wake kjournald unnecessarily
xfs: recalculate leaf entry pointer after compacting a dir2 block
Fabio Estevam (4):
ASoC: soc-core: Remove unused 'ret' variable
ASoC: sgtl5000: Fix maximum value for microphone gain
usb: imx21-hcd: Include missing linux/module.h
usb: chipidea: Allow disabling streaming not only in udc mode
Felipe Balbi (1):
usb: host: ohci-tmio: fix compile warning
Felix Fietkau (1):
mac80211: flush AP_VLAN stations when tearing down the BSS AP
Gerald Schaefer (1):
s390/mm: fix pmd_pfn() for thp
Greg Kroah-Hartman (1):
Remove __dev* markings from init.h
Guenter Roeck (2):
iio: (max1363) Fix probe error path
hwmon: (vexpress) Fix build error seen if CONFIG_OF_DEVICE is not set
H. Peter Anvin (2):
x86/Sandy Bridge: mark arrays in __init functions as __initconst
x86/Sandy Bridge: Sandy Bridge workaround depends on CONFIG_PCI
Haipeng YU (1):
usb: gadget: u_serial: fix switch off blocked
Hannes Reinecke (3):
target: use correct sense code for LUN communication failure
target: Introduce TCM_NO_SENSE
target: Use TCM_NO_SENSE for initialisation
Hans de Goede (3):
udldrmfb: Fix EDID not working with monitors with EDID extension blocks
udldrmfb: udl_get_edid: usb_control_msg buffer must not be on the stack
udldrmfb: udl_get_edid: drop unneeded i--
Heiko Carstens (12):
s390/smp: fix section mismatch for smp_add_present_cpu()
s390/pci: remove dead code
s390/syscalls: wire up finit_module syscall
s390/irq: enable irq sum accounting for /proc/stat again
s390/irq: remove split irq fields from /proc/stat
s390/irq: count cpu restart events
s390/3215: partially revert tty close handling fix
s390/pci: define isa_dma_bridge_buggy
s390/pm: export pm_power_off
s390/topology: export cpu_topology
s390/pci: define read*_relaxed functions
s390/time: fix sched_clock() overflow
Ian Abbott (3):
staging: comedi: prevent auto-unconfig of manually configured devices
staging: comedi: Kconfig: COMEDI_NI_AT_A2150 should select COMEDI_FC
staging: comedi: comedi_test: fix race when cancelling command
Ilija Hadzic (3):
drm/radeon: fix NULL pointer dereference in UMS mode
drm/radeon: fix a bogus kfree
drm/radeon: fix error path in kpage allocation
Inderpal Singh (1):
regulator: s5m8767: Fix probe failure due to stack corruption
Jack Pham (1):
usb: dwc3: debugfs: fix regdump offset
Jan Beulich (1):
USB: ehci: make debug port in-use detection functional again
Jason Liu (1):
mm: compaction: fix echo 1 > compact_memory return error issue
Jason Wang (3):
tuntap: switch to use rtnl_dereference()
tuntap: forbid calling TUNSETIFF when detached
tuntap: fix leaking reference count
Jean-Christophe PLAGNIOL-VILLARD (1):
iio: at91: fix dev var name in at91_adc_trigger_handler
Jerome Glisse (2):
radeon/kms: force rn50 chip to always report connected on analog output
radeon/kms: fix dma relocation checking
Jesse Barnes (1):
x86/Sandy Bridge: reserve pages when integrated graphics is present
Jiri Kosina (3):
lockdep, rwsem: provide down_write_nest_lock()
mm: mmap: annotate vm_lock_anon_vma locking properly for lockdep
lockdep, rwsem: fix down_write_nest_lock() if !CONFIG_DEBUG_LOCK_ALLOC
Johannes Berg (5):
mac80211: assign VLAN channel contexts
mac80211: fix station destruction in AP/mesh modes
mac80211: use del_timer_sync for final sta cleanup timer deletion
mac80211: fix dtim_period in hidden SSID AP association
iwlwifi: fix PCIe interrupt handle return value
Julian Wollrath (1):
rtlwifi: Fix typo in debug output of rtl8192c and rtl8723ae
Kailang Yang (1):
ALSA: hda - Add support of new codec ALC284
Kees Cook (2):
audit: create explicit AUDIT_SECCOMP event type
audit: catch possible NULL audit buffers
Kirill Smelkov (1):
Tell the world we gave up on pushing CC_OPTIMIZE_FOR_SIZE
Konstantin Khlebnikov (1):
staging: vme_pio2: fix oops on module unloading
Krzysztof Mazur (1):
cpuidle: fix number of initialized/destroyed states
Kuninori Morimoto (6):
usb: renesas_usbhs: gadget: remove usbhsg_uep_init()
usb: renesas_usbhs: gadget: usbhsg_ep_disable() care pipe settings
usb: renesas_usbhs: mod_host: fixup usbhsh_ureq_free() timing
sh: define TASK_UNMAPPED_BASE as a page aligned constant
sh: clkfwk: bugfix: sh_clk_div_enable() care sh_clk_div_set_rate() if div6
sh: ecovec: add sample amixer settings
Larry Finger (4):
staging: r8712u: Add new device ID
b43: Fix firmware loading when driver is built into the kernel
staging: rtl8187se: Fix failure to check pci_map_single()
staging: rtl8192e: Fix failure to check pci_map_single()
Lars-Peter Clausen (2):
staging:iio:adis16260: Select adislib
bfin_mac: Restore hardware time-stamping dependency on BF518
Laura Abbott (1):
mm: use aligned zone start for pfn_to_bitidx calculation
Lee, Chun-Yi (3):
MAINTAINERS: change the mail address of acer-wmi/msi-laptop maintainer
acer-wmi: fix obj is NULL but dereferenced
acer-wmi: change to emit touchpad on off key
Li Zhong (1):
Add rcu user eqs exception hooks for async page fault
Lin Feng (1):
mm: memblock: fix wrong memmove size in memblock_merge_regions()
Linus Torvalds (2):
vfs: add missing virtual cache flush after editing partial pages
Linux 3.8-rc4
Liu Bo (1):
tracing: Fix regression of trace_pipe
Lothar Waßmann (3):
staging: drm/imx: check return value of ipu_reset()
staging: drm/imx: several bug fixes
staging: drm/imx: fix double free bug in error path
Luciano Coelho (1):
firmware: make sure the fw file size is not 0
MR.Swami.Reddy@ti.com (2):
ASoC: lm49453: Fix adc, mic and sidetone volume ranges
ASoC: lm49453: Update lm49453_reg_defs values as per LM49453 HW revision-B
Marcelo Tosatti (1):
KVM: x86: use dynamic percpu allocations for shared msrs area
Marcin Slusarz (7):
drm/nouveau: add locking around instobj list operations
drm/nouveau/vm: fix memory corruption when pgt allocation fails
drm/nouveau: don't return freed object from nouveau_handle_create
drm/nouveau: fix nouveau_client allocation failure path
drm/nouveau: fix blank LVDS screen regression on pre-nv50 cards
drm/nv17-50: restore fence buffer on resume
drm/nv50/disp: fix selection of bios script for analog outputs
Mark Brown (13):
ASoC: core: Fix SOC_DOUBLE_RANGE() macros
ASoC: arizona: Correct FLL source definitions
ASoC: wm5102: Improve speaker enable performance
ASoC: wm2200: Remove DSP B and left justified AIF modes
ASoC: arizona: Remove DSP B and left justified AIF modes
ASoC: wm5100: Remove DSP B and left justified formats
ASoC: wm2000: Fix sense of speech clarity enable
ASoC: wm_adsp: Ensure that block writes are from DMA aligned addresses
regmap: debugfs: Fix attempts to read nonexistant register blocks
regmap: debugfs: Fix check for block start in cached seeks
regmap: debugfs: Discard the cache if we fail to allocate an entry
regmap: debugfs: Ensure a correct return value for empty caches
regmap: debugfs: Make sure we store the last entry in the offset cache
Mark Rustad (2):
tcm_fc: Do not indicate retry capability to initiators
tcm_fc: Do not report target role when target is not defined
Mark Tinguely (4):
xfs: use b_maps[] for discontiguous buffers
xfs: rename bli_format to avoid confusion with bli_formats
xfs: fix segment in xfs_buf_item_format_segment
xfs: fix the multi-segment log buffer format
Martin Schwidefsky (1):
s390: use -fPIC for module compile
Matthew Garrett (2):
Update MAINTAINERS entry
asus-laptop: Fix potential invalid pointer dereference
Mattia Dongili (1):
sony-laptop: fix SNC buffer calls when SN06 returns Integers
Max Filippov (1):
mm: bootmem: fix free_all_bootmem_core() with odd bitmap alignment
Maxime Ripard (2):
drivers/video/ssd1307fb.c: fix bit order bug in the byte
translation function
USB: select USB_ARCH_HAS_EHCI for MXS
Mel Gorman (4):
mm: compaction: Partially revert capture of suitable high-order page
mm: migrate: check page_count of THP before migrating
mm: thp: acquire the anon_vma rwsem for write during split
mm: compaction: partially revert capture of suitable high-order page
Michael Hennerich (1):
iio:adf4350: Fix typo
Michael Holzheu (1):
s390/debug: Fix s390dbf lockdep problem in debug_(un)register_view()
Michael S. Tsirkin (1):
tun: avoid owner checks on IFF_ATTACH_QUEUE
Michal Simek (2):
net: ethernet: xilinx: Do not use axienet on PPC
net: ethernet: xilinx: Do not use NO_IRQ in axienet
Michel Lespinasse (1):
lib/rbtree.c: avoid the use of non-static __always_inline
Mike Dunn (2):
ALSA: pxa27x: fix ac97 cold reset
ALSA: pxa27x: fix ac97 warm reset
Mike Frysinger (1):
linux/audit.h: move ptrace.h include to kernel header
Namjae Jeon (1):
UDF: Fix a null pointer dereference in udf_sb_free_partitions
Nickolai Zeldovich (2):
drivers/net/wireless/mwl8k.c: avoid use-after-free
staging: speakup: avoid out-of-range access in synth_init()
Nitin Gupta (1):
staging: zram: fix invalid memory references during disk write
Oliver Neukum (1):
USB: hub: handle claim of enabled remote wakeup after reset
Omar Ramirez Luna (1):
staging: tidspbridge: use prepare/unprepare on dsp clocks
Patrick Lai (1):
ASoC: pcm: allow backend hardware to be freed in pause state
Paul Mundt (2):
sh: wire up finit_module syscall.
sh: Fix up stack debugging build.
Peter Hurley (3):
staging/fwserial: Refine Kconfig help text
staging/fwserial: Limit tx/rx to 1394-2008 spec maximum
staging/fwserial: Update TODO file per reviewer comments
Quentin.Li (1):
USB: option: Add new MEDIATEK PID support
Ralf Baechle (1):
drivers/base/cpu.c: Fix typo in comment
Randy Dunlap (4):
nfs: fix sunrpc/clnt.c kernel-doc warnings
audit: fix auditfilter.c kernel-doc warnings
pci: fix iov.c kernel-doc warnings
seq_file: fix new kernel-doc warnings
Rob Clark (2):
staging: drm/omap: use omapdss low level API
staging: drm/omap: fix flags in dma buf exporting
Roland Dreier (4):
target: Fix missing CMD_T_ACTIVE bit regression for pending WRITEs
target: Fix use-after-free in LUN RESET handling
target: Release se_cmd when LUN lookup fails for TMR
iscsi-target: Fix CmdSN comparison (use cmd->cmd_sn instead of
cmd->stat_sn)
Romain Kuntz (2):
ipv6: fix the noflags test in addrconf_get_prefix_route
ipv6: use addrconf_get_prefix_route for prefix route lookup [v2]
Sachin Kamat (1):
ALSA: usb-audio: Make ebox44_table static
Sam Ravnborg (1):
sparc: remove __devinit, __devexit annotations
Samuel Thibault (1):
staging: speakup: avoid out-of-range access in synth_add()
Sarah Sharp (8):
xhci: Handle HS bulk/ctrl endpoints that don't NAK.
USB: Handle auto-transition from hot to warm reset.
USB: Ignore xHCI Reset Device status.
USB: Allow USB 3.0 ports to be disabled.
USB: Increase reset timeout.
USB: Ignore port state until reset completes.
USB: Handle warm reset failure on empty port.
xhci: Avoid "dead ports", add roothub port polling.
Sasha Levin (1):
x86, efi: correct precedence of operators in setup_efi_pci
Sathya Perla (1):
be2net: fix unconditionally returning IRQ_HANDLED in INTx
Sebastian Andrzej Siewior (1):
usb: gadget: dummy: fix enumeration with g_multi
Sebastian Ott (1):
s390/chsc: fix SEI usage
Sergei Shtylyov (1):
usb: musb: core: print new line in the driver banner again
Sergey Senozhatsky (1):
acer-wmi: add Aspire 5741G touchpad toggle key
Seth Forshee (1):
samsung-laptop: Add quirk for broken acpi_video backlight on N250P
Stanislaw Gruszka (2):
mac80211: fix ibss scanning
net, wireless: overwrite default_ethtool_ops
Stefan Hajnoczi (1):
tuntap: refuse to re-attach to different tun_struct
Stephen Warren (2):
arm64: dts: prevent *.dtb from always being rebuilt
ARM: dts: prevent *.dtb from always being rebuilt
Steven Rostedt (4):
staging: Make SystemBase PCI Multiport UART only for x86
staging: Enable parport sb105x drivers if parport is configured
tracing: Fix regression of trace_options file setting
tracing: Fix regression with irqsoff tracer and tracing_on file
Takashi Iwai (3):
ALSA: hda - Disable runtime D3 for Intel CPT & co
ALSA: usb-audio: Fix NULL dereference by access to non-existing substream
ALSA: hda/hdmi - Work around "alsactl restore" errors
Tejun Heo (1):
module, async: async_synchronize_full() on module init iff async is used
Thomas Pedersen (1):
mac80211: RMC buckets are just list heads
Thomas Schwinge (1):
sh: Fix FDPIC binary loader
Timur Tabi (1):
MAINTAINERS: update email address for Timur Tabi
Tomasz Mloduchowski (1):
usb: ftdi_sio: Crucible Technologies COMET Caller ID - pid added
Trond Myklebust (1):
SUNRPC: Ensure we release the socket write lock if the rpc_task
exits early
Tushar Behera (1):
usb: gadget: s3c-hsotg: Fix invalid free of devm_ allocated data
Vladimir Kondratiev (1):
wireless: add new wil6210 802.11ad 60GHz driver
Wei Yongjun (1):
usb: gadget: tcm_usb_gadge: fix to return error or 0 in
tcm_usbg_drop_nexus()
Will Deacon (4):
arm64: vdso: remove broken, redundant sequence counting for timezones
arm64: mm: only wrprotect clean ptes if they are present
arm64: mm: introduce present, faulting entries for PAGE_NONE
arm64: compat: add syscall table entries for new syscalls
Xi Wang (2):
usb: gadget: amd5536udc: avoid NULL pointer dereference in udc_pci_probe()
fs/exec.c: work around icc miscompilation
Yinghai Lu (1):
ACPI / glue: Fix build with ACPI_GLUE_DEBUG set
Yuval Mintz (1):
bnx2x: Fix fastpath structures when memory allocation fails
Zhang Yanfei (2):
MAINTAINERS: fix arch/arm/plat-omap/include/plat/omap_hwmod.h
MAINTAINERS: fix a status pattern
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-18 3:51 Linux 3.8-rc4 Linus Torvalds
@ 2013-01-18 17:51 ` Shuah Khan
2013-01-18 22:37 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-18 17:51 UTC (permalink / raw)
To: Linus Torvalds; +Cc: Linux Kernel Mailing List
On Thu, Jan 17, 2013 at 8:51 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> Hey, it's been another week already! In fact, it took me so much by
> surprise that it's been an extra day. The whole "release in the middle
> of the week" thing feels odd to me.
>
> [ That actually got me to wonder what the most common day was, and
> statistically I definitely do most releases on Sunday. The "git tip of
> the week" looks like this:
>
> git log --no-walk --pretty="%ad" $(git tag -l)
>
> which can then be piped into
>
> cut -d' ' -f1 | sort | uniq -c | sort -n
>
> to see the full git tagging statistics ]
>
> Anyway, with that digression, I can happily report that -rc4 is
> smaller than -rc3 despite the extra day, although not by much. There's
> not really a whole lot that stands out: apart from one new wireless
> driver (the Atheros Wilocity driver) and some OMAP drm changes, the
> diffstat looks pretty flat and spread out. Which just means lots of
> small changes all over.
>
> The ShortLog is appended, but it's basically 85% drivers, with over
> half the patch being to the aforementioned new wireless one and the
> OMAP drm changes. There's some other stuff there too, but it's largely
> in the noise - small ARM and s390 updates (and a smattering of SuperH
> and x86), a few tiny filesystem fixes, things like that.
>
> Go forth and test. My gut feel is that things really are calming down.
> And I'd hate to be proven wrong.
>
> Linus
>
reboot/shutdown hang in 3.8-rc3 due to
71e3d1578c954cf29f1f4db1c8930d3574025eb0 went away in this rc. But I
am still seeing
[ 22.890240] DMAR:[fault reason 06] PTE Read access is not set
[ 22.890268] dmar: DRHD: handling fault status reg 3
[ 22.890272] dmar: DMAR:[DMA Read] Request device [01:00.0] fault
addr 80004000
on ATI radeon VGA. Running bisect and will update.
-- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-18 17:51 ` Shuah Khan
@ 2013-01-18 22:37 ` Shuah Khan
2013-01-19 0:40 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-18 22:37 UTC (permalink / raw)
To: Linus Torvalds, alexander.deucher; +Cc: Linux Kernel Mailing List
On Fri, Jan 18, 2013 at 10:51 AM, Shuah Khan <shuahkhan@gmail.com> wrote:
> On Thu, Jan 17, 2013 at 8:51 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>> Hey, it's been another week already! In fact, it took me so much by
>> surprise that it's been an extra day. The whole "release in the middle
>> of the week" thing feels odd to me.
>>
>> [ That actually got me to wonder what the most common day was, and
>> statistically I definitely do most releases on Sunday. The "git tip of
>> the week" looks like this:
>>
>> git log --no-walk --pretty="%ad" $(git tag -l)
>>
>> which can then be piped into
>>
>> cut -d' ' -f1 | sort | uniq -c | sort -n
>>
>> to see the full git tagging statistics ]
>>
>> Anyway, with that digression, I can happily report that -rc4 is
>> smaller than -rc3 despite the extra day, although not by much. There's
>> not really a whole lot that stands out: apart from one new wireless
>> driver (the Atheros Wilocity driver) and some OMAP drm changes, the
>> diffstat looks pretty flat and spread out. Which just means lots of
>> small changes all over.
>>
>> The ShortLog is appended, but it's basically 85% drivers, with over
>> half the patch being to the aforementioned new wireless one and the
>> OMAP drm changes. There's some other stuff there too, but it's largely
>> in the noise - small ARM and s390 updates (and a smattering of SuperH
>> and x86), a few tiny filesystem fixes, things like that.
>>
>> Go forth and test. My gut feel is that things really are calming down.
>> And I'd hate to be proven wrong.
>>
>> Linus
>>
>
> reboot/shutdown hang in 3.8-rc3 due to
> 71e3d1578c954cf29f1f4db1c8930d3574025eb0 went away in this rc. But I
> am still seeing
>
> [ 22.890240] DMAR:[fault reason 06] PTE Read access is not set
> [ 22.890268] dmar: DRHD: handling fault status reg 3
> [ 22.890272] dmar: DMAR:[DMA Read] Request device [01:00.0] fault
> addr 80004000
>
> on ATI radeon VGA. Running bisect and will update.
>
> -- Shuah
ok. I bisected the DMAR faults and it points to the following commit:
909d9eb67f1e4e39f2ea88e96bde03d560cde3eb
This commit as I recall, fixed the crash problem I was seeing back in
3.8-rc1. Reverting to see if crash problem reappears.
Here is the git bisect log:
git bisect start '--' 'drivers/gpu/drm/radeon'
# bad: [9931faca02c604c22335f5a935a501bb2ace6e20] Linux 3.8-rc3
git bisect bad 9931faca02c604c22335f5a935a501bb2ace6e20
# good: [d1c3ed669a2d452cacfb48c2d171a1f364dae2ed] Linux 3.8-rc2
git bisect good d1c3ed669a2d452cacfb48c2d171a1f364dae2ed
# bad: [71e3d1578c954cf29f1f4db1c8930d3574025eb0] drm/radeon: switch
to a finer grained reset for r6xx/7xx
git bisect bad 71e3d1578c954cf29f1f4db1c8930d3574025eb0
# bad: [eaaa6983ab2ccdf826c90838eb584211e0cadb76] drm/radeon: print
dma status reg on lockup (v2)
git bisect bad eaaa6983ab2ccdf826c90838eb584211e0cadb76
# bad: [909d9eb67f1e4e39f2ea88e96bde03d560cde3eb] drm/radeon/r6xx: fix
DMA engine for ttm bo transfers
git bisect bad 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb
# good: [cafa59b9011a7790be4ddd5979419259844a165d] drm/radeon: add
connector table for Mac G4 Silver
git bisect good cafa59b9011a7790be4ddd5979419259844a165d
bad commit:
909d9eb67f1e4e39f2ea88e96bde03d560cde3eb is the first bad commit
commit 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb
Author: Alex Deucher <alexander.deucher@amd.com>
Date: Wed Jan 2 18:30:21 2013 -0500
drm/radeon/r6xx: fix DMA engine for ttm bo transfers
count must be a multiple of 2. Fixes crashes on
R6xx chips reported by a number of people.
Cc: Borislav Petkov <bp@alien8.de>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>
Reviewed-by: Jerome Glisse <jglisse@redhat.com>
Tested-by: Jerome Glisse <jglisse@redhat.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
:040000 040000 f641a4e6cb7ac7426a8a80f3a4cf51a6320f95d4
e974cd1737fafb82c6dc8f85dbcdf6cacfea893a M drivers
-- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-18 22:37 ` Shuah Khan
@ 2013-01-19 0:40 ` Shuah Khan
2013-01-19 16:44 ` Deucher, Alexander
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-19 0:40 UTC (permalink / raw)
To: Linus Torvalds, alexander.deucher; +Cc: Linux Kernel Mailing List
On Fri, Jan 18, 2013 at 3:37 PM, Shuah Khan <shuahkhan@gmail.com> wrote:
> On Fri, Jan 18, 2013 at 10:51 AM, Shuah Khan <shuahkhan@gmail.com> wrote:
>
> ok. I bisected the DMAR faults and it points to the following commit:
>
> 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb
>
> This commit as I recall, fixed the crash problem I was seeing back in
> 3.8-rc1. Reverting to see if crash problem reappears.
Confirming that with this commit reverted crash problem re-appeared.
With this commit, DMAR faults show up.
-- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: Linux 3.8-rc4
2013-01-19 0:40 ` Shuah Khan
@ 2013-01-19 16:44 ` Deucher, Alexander
2013-01-22 16:14 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Deucher, Alexander @ 2013-01-19 16:44 UTC (permalink / raw)
To: Shuah Khan, Linus Torvalds; +Cc: Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
> -----Original Message-----
> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> Sent: Friday, January 18, 2013 7:40 PM
> To: Linus Torvalds; Deucher, Alexander
> Cc: Linux Kernel Mailing List
> Subject: Re: Linux 3.8-rc4
>
> On Fri, Jan 18, 2013 at 3:37 PM, Shuah Khan <shuahkhan@gmail.com> wrote:
> > On Fri, Jan 18, 2013 at 10:51 AM, Shuah Khan <shuahkhan@gmail.com>
> wrote:
>
> >
> > ok. I bisected the DMAR faults and it points to the following commit:
> >
> > 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb
> >
> > This commit as I recall, fixed the crash problem I was seeing back in
> > 3.8-rc1. Reverting to see if crash problem reappears.
>
> Confirming that with this commit reverted crash problem re-appeared.
> With this commit, DMAR faults show up.
I'm not quite sure what's going on with your system. At this point it's probably best to just disable the DMA ring on these cards until we sort out what's going on. The attached patch disables the use of the DMA ring. Let me know if it fixes the issues you are seeing.
Alex
[-- Attachment #2: disable_dma_ring_on_6xx.diff --]
[-- Type: application/octet-stream, Size: 1549 bytes --]
diff --git a/drivers/gpu/drm/radeon/radeon_asic.c b/drivers/gpu/drm/radeon/radeon_asic.c
index 9056faf..b0cc46d 100644
--- a/drivers/gpu/drm/radeon/radeon_asic.c
+++ b/drivers/gpu/drm/radeon/radeon_asic.c
@@ -974,8 +974,8 @@ static struct radeon_asic r600_asic = {
.blit_ring_index = RADEON_RING_TYPE_GFX_INDEX,
.dma = &r600_copy_dma,
.dma_ring_index = R600_RING_TYPE_DMA_INDEX,
- .copy = &r600_copy_dma,
- .copy_ring_index = R600_RING_TYPE_DMA_INDEX,
+ .copy = &r600_copy_blit,
+ .copy_ring_index = RADEON_RING_TYPE_GFX_INDEX,
},
.surface = {
.set_reg = r600_set_surface_reg,
@@ -1058,8 +1058,8 @@ static struct radeon_asic rs780_asic = {
.blit_ring_index = RADEON_RING_TYPE_GFX_INDEX,
.dma = &r600_copy_dma,
.dma_ring_index = R600_RING_TYPE_DMA_INDEX,
- .copy = &r600_copy_dma,
- .copy_ring_index = R600_RING_TYPE_DMA_INDEX,
+ .copy = &r600_copy_blit,
+ .copy_ring_index = RADEON_RING_TYPE_GFX_INDEX,
},
.surface = {
.set_reg = r600_set_surface_reg,
diff --git a/drivers/gpu/drm/radeon/radeon_cs.c b/drivers/gpu/drm/radeon/radeon_cs.c
index 469661f..fa7f375 100644
--- a/drivers/gpu/drm/radeon/radeon_cs.c
+++ b/drivers/gpu/drm/radeon/radeon_cs.c
@@ -118,7 +118,7 @@ static int radeon_cs_get_ring(struct radeon_cs_parser *p, u32 ring, s32 priority
p->ring = R600_RING_TYPE_DMA_INDEX;
else
p->ring = CAYMAN_RING_TYPE_DMA1_INDEX;
- } else if (p->rdev->family >= CHIP_R600) {
+ } else if (p->rdev->family >= CHIP_RV770) {
p->ring = R600_RING_TYPE_DMA_INDEX;
} else {
return -EINVAL;
^ permalink raw reply related [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-19 16:44 ` Deucher, Alexander
@ 2013-01-22 16:14 ` Shuah Khan
2013-01-22 16:36 ` Deucher, Alexander
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-22 16:14 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
On Sat, Jan 19, 2013 at 9:44 AM, Deucher, Alexander
<Alexander.Deucher@amd.com> wrote:
>> -----Original Message-----
>> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> Sent: Friday, January 18, 2013 7:40 PM
>> To: Linus Torvalds; Deucher, Alexander
>> Cc: Linux Kernel Mailing List
>> Subject: Re: Linux 3.8-rc4
>>
>> On Fri, Jan 18, 2013 at 3:37 PM, Shuah Khan <shuahkhan@gmail.com> wrote:
>> > On Fri, Jan 18, 2013 at 10:51 AM, Shuah Khan <shuahkhan@gmail.com>
>> wrote:
>>
>> >
>> > ok. I bisected the DMAR faults and it points to the following commit:
>> >
>> > 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb
>> >
>> > This commit as I recall, fixed the crash problem I was seeing back in
>> > 3.8-rc1. Reverting to see if crash problem reappears.
>>
>> Confirming that with this commit reverted crash problem re-appeared.
>> With this commit, DMAR faults show up.
>
> I'm not quite sure what's going on with your system. At this point it's probably best to just disable the DMA ring on these cards until we sort out what's going on. The attached patch disables the use of the DMA ring. Let me know if it fixes the issues you are seeing.
>
I applied this patch to 3.8-rc4 and didn't fix the DMAR faults.
-- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: Linux 3.8-rc4
2013-01-22 16:14 ` Shuah Khan
@ 2013-01-22 16:36 ` Deucher, Alexander
2013-01-22 18:05 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Deucher, Alexander @ 2013-01-22 16:36 UTC (permalink / raw)
To: Shuah Khan; +Cc: Linus Torvalds, Linux Kernel Mailing List
> -----Original Message-----
> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> Sent: Tuesday, January 22, 2013 11:15 AM
> To: Deucher, Alexander
> Cc: Linus Torvalds; Linux Kernel Mailing List
> Subject: Re: Linux 3.8-rc4
>
> On Sat, Jan 19, 2013 at 9:44 AM, Deucher, Alexander
> <Alexander.Deucher@amd.com> wrote:
> >> -----Original Message-----
> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> >> Sent: Friday, January 18, 2013 7:40 PM
> >> To: Linus Torvalds; Deucher, Alexander
> >> Cc: Linux Kernel Mailing List
> >> Subject: Re: Linux 3.8-rc4
> >>
> >> On Fri, Jan 18, 2013 at 3:37 PM, Shuah Khan <shuahkhan@gmail.com>
> wrote:
> >> > On Fri, Jan 18, 2013 at 10:51 AM, Shuah Khan <shuahkhan@gmail.com>
> >> wrote:
> >>
> >> >
> >> > ok. I bisected the DMAR faults and it points to the following commit:
> >> >
> >> > 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb
> >> >
> >> > This commit as I recall, fixed the crash problem I was seeing back in
> >> > 3.8-rc1. Reverting to see if crash problem reappears.
> >>
> >> Confirming that with this commit reverted crash problem re-appeared.
> >> With this commit, DMAR faults show up.
> >
> > I'm not quite sure what's going on with your system. At this point it's
> probably best to just disable the DMA ring on these cards until we sort out
> what's going on. The attached patch disables the use of the DMA ring. Let
> me know if it fixes the issues you are seeing.
> >
>
> I applied this patch to 3.8-rc4 and didn't fix the DMAR faults.
Are you getting continuous DMAR faults or just when while the module is being loaded?
Alex
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-22 16:36 ` Deucher, Alexander
@ 2013-01-22 18:05 ` Shuah Khan
2013-01-22 18:29 ` Shuah Khan
2013-01-22 18:40 ` Deucher, Alexander
0 siblings, 2 replies; 30+ messages in thread
From: Shuah Khan @ 2013-01-22 18:05 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 6151 bytes --]
On Tue, Jan 22, 2013 at 9:36 AM, Deucher, Alexander
<Alexander.Deucher@amd.com> wrote:
>> -----Original Message-----
>> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> Sent: Tuesday, January 22, 2013 11:15 AM
>> To: Deucher, Alexander
>> Cc: Linus Torvalds; Linux Kernel Mailing List
>> Subject: Re: Linux 3.8-rc4
>>
>> On Sat, Jan 19, 2013 at 9:44 AM, Deucher, Alexander
>> <Alexander.Deucher@amd.com> wrote:
>> >> -----Original Message-----
>> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> >> Sent: Friday, January 18, 2013 7:40 PM
>> >> To: Linus Torvalds; Deucher, Alexander
>> >> Cc: Linux Kernel Mailing List
>> >> Subject: Re: Linux 3.8-rc4
>> >>
>> >> On Fri, Jan 18, 2013 at 3:37 PM, Shuah Khan <shuahkhan@gmail.com>
>> wrote:
>> >> > On Fri, Jan 18, 2013 at 10:51 AM, Shuah Khan <shuahkhan@gmail.com>
>> >> wrote:
>> >>
>> >> >
>> >> > ok. I bisected the DMAR faults and it points to the following commit:
>> >> >
>> >> > 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb
>> >> >
>> >> > This commit as I recall, fixed the crash problem I was seeing back in
>> >> > 3.8-rc1. Reverting to see if crash problem reappears.
>> >>
>> >> Confirming that with this commit reverted crash problem re-appeared.
>> >> With this commit, DMAR faults show up.
>> >
>> > I'm not quite sure what's going on with your system. At this point it's
>> probably best to just disable the DMA ring on these cards until we sort out
>> what's going on. The attached patch disables the use of the DMA ring. Let
>> me know if it fixes the issues you are seeing.
>> >
>>
>> I applied this patch to 3.8-rc4 and didn't fix the DMAR faults.
>
> Are you getting continuous DMAR faults or just when while the module is being loaded?
>
> Alex
During module initialization, I think might be actually right after
RV620 Microcode loading attempt: dmesg excerpts starting from radeoan
init:
[ 22.150520] [drm] radeon defaulting to kernel modesetting.
[ 22.150524] [drm] radeon kernel modesetting enabled.
[ 22.150793] [drm] initializing kernel modesetting (RV620 0x1002:0x95C4 0x103C
:0x30DC).
[ 22.150815] [drm] register mmio base: 0x90300000
[ 22.150817] [drm] register mmio size: 65536
[ 22.150918] ATOM BIOS: HP
[ 22.150941] radeon 0000:01:00.0: VRAM: 128M 0x0000000000000000 - 0x0000000007
FFFFFF (128M used)
[ 22.150943] radeon 0000:01:00.0: GTT: 512M 0x0000000008000000 - 0x0000000027F
FFFFF
[ 22.153790] [drm] Detected VRAM RAM=128M, BAR=128M
[ 22.153793] [drm] RAM width 64bits DDR
[ 22.153850] [TTM] Zone kernel: Available graphics memory: 989986 kiB
[ 22.153852] [TTM] Initializing pool allocator
[ 22.153857] [TTM] Initializing DMA pool allocator
[ 22.153884] [drm] radeon: 128M of VRAM memory ready
[ 22.153885] [drm] radeon: 512M of GTT memory ready.
[ 22.153902] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 22.153903] [drm] Driver supports precise vblank timestamp query.
[ 22.153947] radeon 0000:01:00.0: irq 51 for MSI/MSI-X
[ 22.153958] radeon 0000:01:00.0: radeon: using MSI.
[ 22.153988] [drm] radeon: irq initialized.
[ 22.154034] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 22.154796] [drm] probing gen 2 caps for device 8086:2a41 = 1/0
[ 22.154969] [drm] Loading RV620 Microcode
[ 22.218044] dmar: DRHD: handling fault status reg 3
[ 22.218054] dmar: DMAR:[DMA Read] Request device [01:00.0] fault
addr 80000000
[ 22.218054] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218083] dmar: DRHD: handling fault status reg 3
[ 22.218089] dmar: DMAR:[DMA Read] Request device [01:00.0] fault
addr 80002000
[ 22.218089] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218123] dmar: DRHD: handling fault status reg 3
[ 22.218128] dmar: DMAR:[DMA Read] Request device [01:00.0] fault
addr 80004000
[ 22.218128] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218155] dmar: DRHD: handling fault status reg 3
[ 22.218159] dmar: DMAR:[DMA Read] Request device [01:00.0] fault
addr 80006000
[ 22.218159] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218169] dmar: DRHD: handling fault status reg 3
[ 22.218173] dmar: DMAR:[DMA Read] Request device [01:00.0] fault
addr 80007000
[ 22.218173] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218191] dmar: DRHD: handling fault status reg 3
tons of these and then:
[ 22.236419] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 22.236479] radeon 0000:01:00.0: WB enabled
[ 22.236483] radeon 0000:01:00.0: fence driver on ring 0 use gpu
addr 0x0000000008
000c00 and cpu addr 0xffff88002f436c00
[ 22.236485] radeon 0000:01:00.0: fence driver on ring 3 use gpu
addr 0x0000000008
000c0c and cpu addr 0xffff88002f436c0c
[ 22.270041] [drm] ring test on 0 succeeded in 1 usecs
[ 22.270099] [drm] ring test on 3 succeeded in 1 usecs
[ 22.272156] [drm] ib test on ring 0 succeeded in 0 usecs
[ 22.272170] [drm] ib test on ring 3 succeeded in 0 usecs
[ 22.272705] [drm] radeon atom DIG backlight initialized
[ 22.272707] [drm] Radeon Display Connectors
[ 22.272708] [drm] Connector 0:
[ 22.272710] [drm] LVDS-1
[ 22.272711] [drm] Encoders:
[ 22.272712] [drm] LCD1: INTERNAL_KLDSCP_LVTMA
[ 22.272713] [drm] Connector 1:
[ 22.272714] [drm] VGA-1
[ 22.272716] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48
0x7e4c 0x7e4c
[ 22.272717] [drm] Encoders:
[ 22.272718] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 22.272719] [drm] Connector 2:
[ 22.272720] [drm] DVI-D-1
[ 22.272721] [drm] HPD1
[ 22.272723] [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68
0x7e6c 0x7e6c
[ 22.272724] [drm] Encoders:
[ 22.272725] [drm] DFP1: INTERNAL_UNIPHY
[ 22.272758] [drm] radeon: power management initialized
[ 23.232093] fbcon: radeondrmfb (fb0) is primary device
[ 23.496217] Console: switching to colour frame buffer device 180x56
[ 23.499083] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[ 23.499085] radeon 0000:01:00.0: registered panic notifier
[ 23.499100] [drm] Initialized radeon 2.28.0 20080528 for
0000:01:00.0 on minor 0
Attaching entire dmesg as well:
-- Shuah
[-- Attachment #2: dmesg_3.8-rc4_radeaon --]
[-- Type: application/octet-stream, Size: 202682 bytes --]
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.8.0-rc4+ (shuah@lorien) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #8 SMP Sat Jan 19 11:59:29 MST 2013
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.8.0-rc4+ root=UUID=89758757-2419-42dd-b137-747a1070d1f9 ro earlyprintk=vga intel_iommu=on loglvl=info crashkernel=384M-2G:64M,2G-:128M
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] Disabled fast string operations
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000ef000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000007ad45fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007ad46000-0x000000007ad47fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000007ad48000-0x000000007bb6ffff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007bb70000-0x000000007bb7ffff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000007bb80000-0x000000007e2c0fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007e2c1000-0x000000007e4c0fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000007e4c1000-0x000000007fc91fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007fc92000-0x000000007fc99fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000007fc9a000-0x000000007fcbefff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007fcbf000-0x000000007fccefff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000007fccf000-0x000000007fdcefff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000007fdcf000-0x000000007fdfefff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x000000007fdff000-0x000000007fdfffff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007fe00000-0x000000007fffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed13fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed18000-0x00000000fed19fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ffe80000-0x00000000ffffffff] reserved
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.4 present.
[ 0.000000] DMI: Hewlett-Packard HP EliteBook 6930p/30DC, BIOS 68PCD Ver. F.10 06/24/2009
[ 0.000000] e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] No AGP bridge found
[ 0.000000] e820: last_pfn = 0x7fe00 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0FFE00000 mask FFFE00000 write-protect
[ 0.000000] 1 base 000000000 mask F80000000 write-back
[ 0.000000] 2 base 07BB70000 mask FFFFF0000 uncachable
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] initial memory mapped: [mem 0x00000000-0x1fffffff]
[ 0.000000] Base memory trampoline at [ffff880000099000] 99000 size 24576
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x7fdfffff]
[ 0.000000] [mem 0x00000000-0x7fdfffff] page 2M
[ 0.000000] kernel direct mapping tables up to 0x7fdfffff @ [mem 0x1fffd000-0x1fffffff]
[ 0.000000] RAMDISK: [mem 0x294a4000-0x30a49fff]
[ 0.000000] Reserving 64MB of memory at 832MB for crashkernel (System RAM: 2042MB)
[ 0.000000] ACPI: RSDP 00000000000f6810 00024 (v02 HPQOEM)
[ 0.000000] ACPI: XSDT 000000007fdfe120 00084 (v01 HPQOEM SLIC-MPC 0000000F 01000013)
[ 0.000000] ACPI: FACP 000000007fdfc000 000F4 (v03 HPQOEM 30DC 0000000F HP 00000001)
[ 0.000000] ACPI: DSDT 000000007fdde000 18ADC (v01 HPQOEM 30DC 00000001 INTL 20060912)
[ 0.000000] ACPI: FACS 000000007fd9c000 00040
[ 0.000000] ACPI: HPET 000000007fdfb000 00038 (v01 HPQOEM 30DC 00000001 HP 00000001)
[ 0.000000] ACPI: APIC 000000007fdfa000 00084 (v01 HPQOEM 30DC 00000001 HP 00000001)
[ 0.000000] ACPI: MCFG 000000007fdf9000 0003C (v01 HPQOEM 30DC 00000001 HP 00000001)
[ 0.000000] ACPI: ASF! 000000007fdf8000 00095 (v32 HPQOEM 30DC 00000001 HP 00000001)
[ 0.000000] ACPI: TCPA 000000007fdf7000 00032 (v02 HPQOEM 30DC 00000000 HP 00000001)
[ 0.000000] ACPI: SSDT 000000007fddb000 002DD (v01 HPQOEM SataAhci 00001000 INTL 20060912)
[ 0.000000] ACPI: SLIC 000000007fdd9000 00176 (v01 HPQOEM SLIC-MPC 00000001 HP 00000001)
[ 0.000000] ACPI: DMAR 000000007fdd8000 000B0 (v01 ? 00000001 00000000)
[ 0.000000] ACPI: SSDT 000000007fdd7000 0066C (v01 PmRef CpuPm 00003000 INTL 20060912)
[ 0.000000] ACPI: SSDT 000000007fdd6000 00288 (v01 PmRef Cpu0Tst 00003000 INTL 20060912)
[ 0.000000] ACPI: SSDT 000000007fdd5000 00225 (v01 PmRef ApTst 00003000 INTL 20060912)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000007fdfffff]
[ 0.000000] Initmem setup node 0 [mem 0x00000000-0x7fdfffff]
[ 0.000000] NODE_DATA [mem 0x7fcbb000-0x7fcbefff]
[ 0.000000] [ffffea0000000000-ffffea0001ffffff] PMD -> [ffff88007c200000-ffff88007e1fffff] on node 0
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00010000-0x00ffffff]
[ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00010000-0x0009efff]
[ 0.000000] node 0: [mem 0x00100000-0x7ad45fff]
[ 0.000000] node 0: [mem 0x7ad48000-0x7bb6ffff]
[ 0.000000] node 0: [mem 0x7bb80000-0x7e2c0fff]
[ 0.000000] node 0: [mem 0x7e4c1000-0x7fc91fff]
[ 0.000000] node 0: [mem 0x7fc9a000-0x7fcbefff]
[ 0.000000] node 0: [mem 0x7fdff000-0x7fdfffff]
[ 0.000000] On node 0 totalpages: 522805
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 6 pages reserved
[ 0.000000] DMA zone: 3913 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 8120 pages used for memmap
[ 0.000000] DMA32 zone: 510702 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x408
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x00] disabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x00] disabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 1, version 32, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.000000] smpboot: Allowing 4 CPUs, 2 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 40
[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000
[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000ef000
[ 0.000000] PM: Registered nosave memory: 00000000000ef000 - 0000000000100000
[ 0.000000] PM: Registered nosave memory: 000000007ad46000 - 000000007ad48000
[ 0.000000] PM: Registered nosave memory: 000000007bb70000 - 000000007bb80000
[ 0.000000] PM: Registered nosave memory: 000000007e2c1000 - 000000007e4c1000
[ 0.000000] PM: Registered nosave memory: 000000007fc92000 - 000000007fc9a000
[ 0.000000] PM: Registered nosave memory: 000000007fcbf000 - 000000007fccf000
[ 0.000000] PM: Registered nosave memory: 000000007fccf000 - 000000007fdcf000
[ 0.000000] PM: Registered nosave memory: 000000007fdcf000 - 000000007fdff000
[ 0.000000] e820: [mem 0x80000000-0xdfffffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:4 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 28 pages/cpu @ffff88007fa00000 s84800 r8192 d21696 u524288
[ 0.000000] pcpu-alloc: s84800 r8192 d21696 u524288 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0 1 2 3
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 514615
[ 0.000000] Policy zone: DMA32
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.8.0-rc4+ root=UUID=89758757-2419-42dd-b137-747a1070d1f9 ro earlyprintk=vga intel_iommu=on loglvl=info crashkernel=384M-2G:64M,2G-:128M
[ 0.000000] Intel-IOMMU: enabled
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] __ex_table already sorted, skipping sort
[ 0.000000] xsave: enabled xstate_bv 0x3, cntxt size 0x240
[ 0.000000] Checking aperture...
[ 0.000000] No AGP bridge found
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[ 0.000000] Memory: 1856092k/2095104k available (6875k kernel code, 3884k absent, 235128k reserved, 6327k data, 964k init)
[ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[ 0.000000] NR_IRQS:16640 nr_irqs:712 16
[ 0.000000] Extended CMOS year: 2000
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] hpet clockevent registered
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 2527.029 MHz processor
[ 0.004004] Calibrating delay loop (skipped), value calculated using timer frequency.. 5054.05 BogoMIPS (lpj=10108116)
[ 0.004010] pid_max: default: 32768 minimum: 301
[ 0.004036] Security Framework initialized
[ 0.004053] AppArmor: AppArmor initialized
[ 0.004230] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes)
[ 0.005448] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.006011] Mount-cache hash table entries: 256
[ 0.006210] Initializing cgroup subsys cpuacct
[ 0.006214] Initializing cgroup subsys devices
[ 0.006217] Initializing cgroup subsys freezer
[ 0.006220] Initializing cgroup subsys blkio
[ 0.006223] Initializing cgroup subsys perf_event
[ 0.006248] Disabled fast string operations
[ 0.006255] CPU: Physical Processor ID: 0
[ 0.006258] CPU: Processor Core ID: 0
[ 0.006261] mce: CPU supports 6 MCE banks
[ 0.006269] CPU0: Thermal monitoring handled by SMI
[ 0.006272] process: using mwait in idle threads
[ 0.006278] Last level iTLB entries: 4KB 128, 2MB 4, 4MB 4
[ 0.006278] Last level dTLB entries: 4KB 256, 2MB 0, 4MB 32
[ 0.006278] tlb_flushall_shift: -1
[ 0.006369] Freeing SMP alternatives: 24k freed
[ 0.008545] ACPI: Core revision 20121018
[ 0.016016] ftrace: allocating 25776 entries in 101 pages
[ 0.024092] dmar: Host address width 36
[ 0.024097] dmar: DRHD base: 0x000000feb03000 flags: 0x0
[ 0.024103] dmar: IOMMU 0: reg_base_addr feb03000 ver 1:0 cap c9008020e30260 ecap 1000
[ 0.024107] dmar: DRHD base: 0x000000feb02000 flags: 0x1
[ 0.024112] dmar: IOMMU 1: reg_base_addr feb02000 ver 1:0 cap c9008020630260 ecap 1000
[ 0.024116] dmar: RMRR base: 0x0000007bb70000 end: 0x0000007bb7ffff
[ 0.024561] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.064322] smpboot: CPU0: Intel(R) Core(TM)2 Duo CPU T9400 @ 2.53GHz (fam: 06, model: 17, stepping: 0a)
[ 0.068000] Performance Events: PEBS fmt0+, 4-deep LBR, Core2 events, Intel PMU driver.
[ 0.068000] ... version: 2
[ 0.068000] ... bit width: 40
[ 0.068000] ... generic registers: 2
[ 0.068000] ... value mask: 000000ffffffffff
[ 0.068000] ... max period: 000000007fffffff
[ 0.068000] ... fixed-purpose events: 3
[ 0.068000] ... event mask: 0000000700000003
[ 0.008000] CPU1: Thermal monitoring handled by SMI
[ 0.068000] smpboot: Booting Node 0, Processors #1
[ 0.076022] Brought up 2 CPUs
[ 0.076031] smpboot: Total of 2 processors activated (10108.11 BogoMIPS)
[ 0.076155] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.080094] devtmpfs: initialized
[ 0.080931] EVM: security.selinux
[ 0.080934] EVM: security.SMACK64
[ 0.080936] EVM: security.capability
[ 0.080951] PM: Registering ACPI NVS region [mem 0x7bb70000-0x7bb7ffff] (65536 bytes)
[ 0.080951] PM: Registering ACPI NVS region [mem 0x7e2c1000-0x7e4c0fff] (2097152 bytes)
[ 0.080951] PM: Registering ACPI NVS region [mem 0x7fccf000-0x7fdcefff] (1048576 bytes)
[ 0.080951] regulator-dummy: no parameters
[ 0.080980] RTC time: 16:07:15, date: 01/22/13
[ 0.081020] NET: Registered protocol family 16
[ 0.081173] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[ 0.081178] ACPI: bus type pci registered
[ 0.081219] dca service started, version 1.12.1
[ 0.081250] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 0.081255] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820
[ 0.109130] PCI: Using configuration type 1 for base access
[ 0.109942] bio: create slab <bio-0> at 0
[ 0.112043] ACPI: Added _OSI(Module Device)
[ 0.112047] ACPI: Added _OSI(Processor Device)
[ 0.112049] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.112052] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.113687] ACPI: EC: Look up EC in DSDT
[ 0.117979] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 0.125313] ACPI: SSDT 000000007fcc7c18 00275 (v01 PmRef Cpu0Ist 00003000 INTL 20060912)
[ 0.125707] ACPI: Dynamic OEM Table Load:
[ 0.125711] ACPI: SSDT (null) 00275 (v01 PmRef Cpu0Ist 00003000 INTL 20060912)
[ 0.125816] ACPI: SSDT 000000007fcc5618 0057B (v01 PmRef Cpu0Cst 00003001 INTL 20060912)
[ 0.126197] ACPI: Dynamic OEM Table Load:
[ 0.126201] ACPI: SSDT (null) 0057B (v01 PmRef Cpu0Cst 00003001 INTL 20060912)
[ 0.128189] ACPI: SSDT 000000007fcc6e18 001D7 (v01 PmRef ApIst 00003000 INTL 20060912)
[ 0.128595] ACPI: Dynamic OEM Table Load:
[ 0.128599] ACPI: SSDT (null) 001D7 (v01 PmRef ApIst 00003000 INTL 20060912)
[ 0.128609] ACPI: SSDT 000000007fcc7f18 0008D (v01 PmRef ApCst 00003000 INTL 20060912)
[ 0.128609] ACPI: Dynamic OEM Table Load:
[ 0.128609] ACPI: SSDT (null) 0008D (v01 PmRef ApCst 00003000 INTL 20060912)
[ 0.372060] ACPI: Interpreter enabled
[ 0.372066] ACPI: (supports S0 S3 S4 S5)
[ 0.372082] ACPI: Using IOAPIC for interrupt routing
[ 0.372718] ACPI: Power Resource [APPR] (off)
[ 0.377826] ACPI: Power Resource [LPP] (on)
[ 0.377826] ACPI: Power Resource [PGF0] (off)
[ 0.377826] ACPI: EC: GPE = 0x16, I/O: command/status = 0x66, data = 0x62
[ 0.377891] ACPI: No dock devices found.
[ 0.377896] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.380103] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.380108] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
[ 0.380882] pci_root PNP0A08:00: Requesting ACPI _OSC control (0x1d)
[ 0.381767] pci_root PNP0A08:00: ACPI _OSC control (0x1d) granted
[ 0.382250] PCI host bridge to bus 0000:00
[ 0.382255] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.382259] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[ 0.382262] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
[ 0.382265] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 0.382269] pci_bus 0000:00: root bus resource [mem 0x80000000-0xdfffffff]
[ 0.382272] pci_bus 0000:00: root bus resource [mem 0xf0000000-0xfedfffff]
[ 0.382275] pci_bus 0000:00: root bus resource [mem 0xfee01000-0xffffffff]
[ 0.382286] pci 0000:00:00.0: [8086:2a40] type 00 class 0x060000
[ 0.382305] DMAR: Forcing write-buffer flush capability
[ 0.382307] DMAR: Disabling IOMMU for graphics on this chipset
[ 0.382334] pci 0000:00:01.0: [8086:2a41] type 01 class 0x060400
[ 0.382372] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.382412] pci 0000:00:19.0: [8086:10f5] type 00 class 0x020000
[ 0.382430] pci 0000:00:19.0: reg 10: [mem 0x90400000-0x9041ffff]
[ 0.382438] pci 0000:00:19.0: reg 14: [mem 0x90424000-0x90424fff]
[ 0.382446] pci 0000:00:19.0: reg 18: [io 0x80e0-0x80ff]
[ 0.382506] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
[ 0.382525] pci 0000:00:1a.0: [8086:2937] type 00 class 0x0c0300
[ 0.382565] pci 0000:00:1a.0: reg 20: [io 0x80c0-0x80df]
[ 0.382615] pci 0000:00:1a.1: [8086:2938] type 00 class 0x0c0300
[ 0.382655] pci 0000:00:1a.1: reg 20: [io 0x80a0-0x80bf]
[ 0.382704] pci 0000:00:1a.2: [8086:2939] type 00 class 0x0c0300
[ 0.382744] pci 0000:00:1a.2: reg 20: [io 0x8080-0x809f]
[ 0.382802] pci 0000:00:1a.7: [8086:293c] type 00 class 0x0c0320
[ 0.382822] pci 0000:00:1a.7: reg 10: [mem 0x90425c00-0x90425fff]
[ 0.382908] pci 0000:00:1a.7: PME# supported from D0 D3hot D3cold
[ 0.382935] pci 0000:00:1b.0: [8086:293e] type 00 class 0x040300
[ 0.382950] pci 0000:00:1b.0: reg 10: [mem 0x90420000-0x90423fff 64bit]
[ 0.383014] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.383036] pci 0000:00:1c.0: [8086:2940] type 01 class 0x060400
[ 0.383101] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.383124] pci 0000:00:1c.1: [8086:2942] type 01 class 0x060400
[ 0.383189] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 0.383212] pci 0000:00:1c.2: [8086:2944] type 01 class 0x060400
[ 0.383277] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
[ 0.383301] pci 0000:00:1c.4: [8086:2948] type 01 class 0x060400
[ 0.383366] pci 0000:00:1c.4: PME# supported from D0 D3hot D3cold
[ 0.383392] pci 0000:00:1d.0: [8086:2934] type 00 class 0x0c0300
[ 0.383432] pci 0000:00:1d.0: reg 20: [io 0x8060-0x807f]
[ 0.383482] pci 0000:00:1d.1: [8086:2935] type 00 class 0x0c0300
[ 0.383522] pci 0000:00:1d.1: reg 20: [io 0x8040-0x805f]
[ 0.383571] pci 0000:00:1d.2: [8086:2936] type 00 class 0x0c0300
[ 0.383611] pci 0000:00:1d.2: reg 20: [io 0x8020-0x803f]
[ 0.383670] pci 0000:00:1d.7: [8086:293a] type 00 class 0x0c0320
[ 0.383690] pci 0000:00:1d.7: reg 10: [mem 0x90425800-0x90425bff]
[ 0.383776] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 0.383797] pci 0000:00:1e.0: [8086:2448] type 01 class 0x060401
[ 0.383857] pci 0000:00:1f.0: [8086:2917] type 00 class 0x060100
[ 0.383971] pci 0000:00:1f.2: [8086:2929] type 00 class 0x010601
[ 0.383989] pci 0000:00:1f.2: reg 10: [io 0x8108-0x810f]
[ 0.383996] pci 0000:00:1f.2: reg 14: [io 0x8114-0x8117]
[ 0.384008] pci 0000:00:1f.2: reg 18: [io 0x8100-0x8107]
[ 0.384015] pci 0000:00:1f.2: reg 1c: [io 0x8110-0x8113]
[ 0.384023] pci 0000:00:1f.2: reg 20: [io 0x8000-0x801f]
[ 0.384030] pci 0000:00:1f.2: reg 24: [mem 0x90425000-0x904257ff]
[ 0.384074] pci 0000:00:1f.2: PME# supported from D3hot
[ 0.384131] pci 0000:01:00.0: [1002:95c4] type 00 class 0x030000
[ 0.384146] pci 0000:01:00.0: reg 10: [mem 0x80000000-0x87ffffff pref]
[ 0.384156] pci 0000:01:00.0: reg 14: [io 0x7000-0x70ff]
[ 0.384167] pci 0000:01:00.0: reg 18: [mem 0x90300000-0x9030ffff]
[ 0.384204] pci 0000:01:00.0: reg 30: [mem 0xfffe0000-0xffffffff pref]
[ 0.384253] pci 0000:01:00.0: supports D1 D2
[ 0.392011] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.392016] pci 0000:00:01.0: bridge window [io 0x7000-0x7fff]
[ 0.392019] pci 0000:00:01.0: bridge window [mem 0x90300000-0x903fffff]
[ 0.392023] pci 0000:00:01.0: bridge window [mem 0x80000000-0x87ffffff 64bit pref]
[ 0.392060] pci 0000:00:1c.0: PCI bridge to [bus 02]
[ 0.392066] pci 0000:00:1c.0: bridge window [mem 0x90200000-0x902fffff]
[ 0.392154] pci 0000:03:00.0: [8086:4236] type 00 class 0x028000
[ 0.392186] pci 0000:03:00.0: reg 10: [mem 0x90100000-0x90101fff 64bit]
[ 0.392351] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
[ 0.400039] pci 0000:00:1c.1: PCI bridge to [bus 03]
[ 0.400046] pci 0000:00:1c.1: bridge window [mem 0x90100000-0x901fffff]
[ 0.400087] pci 0000:00:1c.2: PCI bridge to [bus 04-44]
[ 0.400091] pci 0000:00:1c.2: bridge window [io 0x5000-0x6fff]
[ 0.400095] pci 0000:00:1c.2: bridge window [mem 0x8c100000-0x900fffff]
[ 0.400135] pci 0000:00:1c.4: PCI bridge to [bus 45-85]
[ 0.400140] pci 0000:00:1c.4: bridge window [io 0x3000-0x4fff]
[ 0.400143] pci 0000:00:1c.4: bridge window [mem 0x88100000-0x8c0fffff]
[ 0.400187] pci 0000:86:09.0: [1180:0832] type 00 class 0x0c0010
[ 0.400199] pci 0000:86:09.0: proprietary Ricoh MMC controller disabled (via firewire function)
[ 0.400203] pci 0000:86:09.0: MMC cards are now supported by standard SDHCI controller
[ 0.400217] pci 0000:86:09.0: reg 10: [mem 0x88001000-0x880017ff]
[ 0.400288] pci 0000:86:09.0: supports D1 D2
[ 0.400290] pci 0000:86:09.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.400309] pci 0000:86:09.1: [1180:0822] type 00 class 0x080500
[ 0.400325] pci 0000:86:09.1: reg 10: [mem 0x88001900-0x880019ff]
[ 0.400396] pci 0000:86:09.1: supports D1 D2
[ 0.400398] pci 0000:86:09.1: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.400418] pci 0000:86:09.2: [1180:0476] type 02 class 0x060700
[ 0.400434] pci 0000:86:09.2: reg 10: [mem 0x88000000-0x88000fff]
[ 0.400461] pci 0000:86:09.2: supports D1 D2
[ 0.400463] pci 0000:86:09.2: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.400504] pci 0000:00:1e.0: PCI bridge to [bus 86-87] (subtractive decode)
[ 0.400509] pci 0000:00:1e.0: bridge window [io 0x2000-0x2fff]
[ 0.400513] pci 0000:00:1e.0: bridge window [mem 0x88000000-0x880fffff]
[ 0.400518] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
[ 0.400520] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
[ 0.400522] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
[ 0.400524] pci 0000:00:1e.0: bridge window [mem 0x80000000-0xdfffffff] (subtractive decode)
[ 0.400526] pci 0000:00:1e.0: bridge window [mem 0xf0000000-0xfedfffff] (subtractive decode)
[ 0.400528] pci 0000:00:1e.0: bridge window [mem 0xfee01000-0xffffffff] (subtractive decode)
[ 0.400557] pci_bus 0000:87: busn_res: can not insert [bus 87-ff] under [bus 86-87] (conflicts with (null) [bus 86-87])
[ 0.400562] pci_bus 0000:87: busn_res: [bus 87-ff] end is updated to 8a
[ 0.400564] pci_bus 0000:87: busn_res: can not insert [bus 87-8a] under [bus 86-87] (conflicts with (null) [bus 86-87])
[ 0.400568] pci_bus 0000:87: [bus 87-8a] partially hidden behind transparent bridge 0000:86 [bus 86-87]
[ 0.400601] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PEGP._PRT]
[ 0.400645] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP01._PRT]
[ 0.400674] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP02._PRT]
[ 0.400706] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP03._PRT]
[ 0.400757] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.RP05._PRT]
[ 0.400829] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
[ 0.406697] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 *10 12 14 15)
[ 0.406738] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
[ 0.406779] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 *10 12 14 15)
[ 0.406817] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
[ 0.406856] ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 *10 12 14 15)
[ 0.406895] ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
[ 0.406935] ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
[ 0.406974] ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
[ 0.407034] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.407034] vgaarb: loaded
[ 0.407034] vgaarb: bridge control possible 0000:01:00.0
[ 0.407034] SCSI subsystem initialized
[ 0.407034] ACPI: bus type scsi registered
[ 0.407034] libata version 3.00 loaded.
[ 0.407034] ACPI: bus type usb registered
[ 0.407034] usbcore: registered new interface driver usbfs
[ 0.407034] usbcore: registered new interface driver hub
[ 0.407034] usbcore: registered new device driver usb
[ 0.407034] PCI: Using ACPI for IRQ routing
[ 0.413247] PCI: pci_cache_line_size set to 64 bytes
[ 0.413315] e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
[ 0.413317] e820: reserve RAM buffer [mem 0x7ad46000-0x7bffffff]
[ 0.413318] e820: reserve RAM buffer [mem 0x7bb70000-0x7bffffff]
[ 0.413319] e820: reserve RAM buffer [mem 0x7e2c1000-0x7fffffff]
[ 0.413321] e820: reserve RAM buffer [mem 0x7fc92000-0x7fffffff]
[ 0.413323] e820: reserve RAM buffer [mem 0x7fcbf000-0x7fffffff]
[ 0.413324] e820: reserve RAM buffer [mem 0x7fe00000-0x7fffffff]
[ 0.413403] NetLabel: Initializing
[ 0.413406] NetLabel: domain hash size = 128
[ 0.413408] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.413419] NetLabel: unlabeled traffic allowed by default
[ 0.413431] HPET: 4 timers in total, 0 timers will be used for per-cpu timer
[ 0.413431] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0
[ 0.413431] hpet0: 4 comparators, 64-bit 14.318180 MHz counter
[ 0.414058] Switching to clocksource hpet
[ 0.417465] AppArmor: AppArmor Filesystem Enabled
[ 0.417488] pnp: PnP ACPI init
[ 0.417505] ACPI: bus type pnp registered
[ 0.417641] system 00:00: [mem 0xfed1c000-0xfed1ffff] has been reserved
[ 0.417646] system 00:00: [mem 0xfed10000-0xfed13fff] has been reserved
[ 0.417650] system 00:00: [mem 0xfed18000-0xfed18fff] has been reserved
[ 0.417653] system 00:00: [mem 0xfed19000-0xfed19fff] has been reserved
[ 0.417657] system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
[ 0.417661] system 00:00: [mem 0xfec00000-0xfec00fff] could not be reserved
[ 0.417664] system 00:00: [mem 0xfed20000-0xfed3ffff] has been reserved
[ 0.417668] system 00:00: [mem 0xfed45000-0xfed8ffff] has been reserved
[ 0.417673] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.417968] pnp 00:01: [dma 4]
[ 0.418002] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
[ 0.418031] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
[ 0.418097] pnp 00:03: Plug and Play ACPI device, IDs IFX0102 PNP0c31 (active)
[ 0.418189] system 00:04: [mem 0xfed00000-0xfed003ff] has been reserved
[ 0.418195] system 00:04: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
[ 0.418239] pnp 00:05: Plug and Play ACPI device, IDs PNP0c04 (active)
[ 0.418295] system 00:06: [io 0x0200-0x027f] has been reserved
[ 0.418299] system 00:06: [io 0x1000-0x1003] has been reserved
[ 0.418303] system 00:06: [io 0x1010-0x101f] has been reserved
[ 0.418306] system 00:06: [io 0xffff] has been reserved
[ 0.418309] system 00:06: [io 0x0400-0x047f] has been reserved
[ 0.418313] system 00:06: [io 0x0500-0x057f] has been reserved
[ 0.418316] system 00:06: [io 0xef80-0xef9f] has been reserved
[ 0.418320] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.418356] pnp 00:07: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.418687] pnp 00:08: [dma 0 disabled]
[ 0.418764] pnp 00:08: Plug and Play ACPI device, IDs PNP0401 (active)
[ 0.418799] pnp 00:09: Plug and Play ACPI device, IDs PNP0303 (active)
[ 0.418835] pnp 00:0a: Plug and Play ACPI device, IDs SYN0147 SYN0100 SYN0002 PNP0f13 (active)
[ 0.418888] pnp 00:0b: Plug and Play ACPI device, IDs HPQ0004 (active)
[ 0.418996] pnp: PnP ACPI: found 12 devices
[ 0.418999] ACPI: ACPI bus type pnp unregistered
[ 0.425241] pci 0000:01:00.0: no compatible bridge window for [mem 0xfffe0000-0xffffffff pref]
[ 0.425260] pci 0000:00:1c.0: bridge window [io 0x1000-0x0fff] to [bus 02] add_size 1000
[ 0.425263] pci 0000:00:1c.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000
[ 0.425271] pci 0000:00:1c.1: bridge window [io 0x1000-0x0fff] to [bus 03] add_size 1000
[ 0.425274] pci 0000:00:1c.1: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000
[ 0.425282] pci 0000:00:1c.2: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 04-44] add_size 200000
[ 0.425290] pci 0000:00:1c.4: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 45-85] add_size 200000
[ 0.425303] pci 0000:86:09.2: res[15]=[mem 0x04000000-0x03ffffff pref] get_res_add_size add_size 4000000
[ 0.425306] pci 0000:00:1e.0: bridge window [mem 0x04000000-0x03ffffff pref] to [bus 86-87] add_size 4000000
[ 0.425314] pci 0000:00:1e.0: res[15]=[mem 0x04000000-0x03ffffff pref] get_res_add_size add_size 4000000
[ 0.425317] pci 0000:00:1c.0: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
[ 0.425319] pci 0000:00:1c.1: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
[ 0.425321] pci 0000:00:1c.2: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
[ 0.425323] pci 0000:00:1c.4: res[15]=[mem 0x00100000-0x000fffff 64bit pref] get_res_add_size add_size 200000
[ 0.425325] pci 0000:00:1c.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
[ 0.425327] pci 0000:00:1c.1: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
[ 0.425332] pci 0000:00:1e.0: BAR 15: assigned [mem 0x94000000-0x97ffffff pref]
[ 0.425337] pci 0000:00:1c.0: BAR 15: assigned [mem 0x90500000-0x906fffff 64bit pref]
[ 0.425342] pci 0000:00:1c.1: BAR 15: assigned [mem 0x90700000-0x908fffff 64bit pref]
[ 0.425347] pci 0000:00:1c.2: BAR 15: assigned [mem 0x90900000-0x90afffff 64bit pref]
[ 0.425351] pci 0000:00:1c.4: BAR 15: assigned [mem 0x90b00000-0x90cfffff 64bit pref]
[ 0.425356] pci 0000:00:1c.0: BAR 13: assigned [io 0x9000-0x9fff]
[ 0.425360] pci 0000:00:1c.1: BAR 13: assigned [io 0xa000-0xafff]
[ 0.425366] pci 0000:01:00.0: BAR 6: assigned [mem 0x90320000-0x9033ffff pref]
[ 0.425370] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.425374] pci 0000:00:01.0: bridge window [io 0x7000-0x7fff]
[ 0.425379] pci 0000:00:01.0: bridge window [mem 0x90300000-0x903fffff]
[ 0.425383] pci 0000:00:01.0: bridge window [mem 0x80000000-0x87ffffff 64bit pref]
[ 0.425389] pci 0000:00:1c.0: PCI bridge to [bus 02]
[ 0.425393] pci 0000:00:1c.0: bridge window [io 0x9000-0x9fff]
[ 0.425399] pci 0000:00:1c.0: bridge window [mem 0x90200000-0x902fffff]
[ 0.425404] pci 0000:00:1c.0: bridge window [mem 0x90500000-0x906fffff 64bit pref]
[ 0.425411] pci 0000:00:1c.1: PCI bridge to [bus 03]
[ 0.425415] pci 0000:00:1c.1: bridge window [io 0xa000-0xafff]
[ 0.425420] pci 0000:00:1c.1: bridge window [mem 0x90100000-0x901fffff]
[ 0.425425] pci 0000:00:1c.1: bridge window [mem 0x90700000-0x908fffff 64bit pref]
[ 0.425432] pci 0000:00:1c.2: PCI bridge to [bus 04-44]
[ 0.425436] pci 0000:00:1c.2: bridge window [io 0x5000-0x6fff]
[ 0.425442] pci 0000:00:1c.2: bridge window [mem 0x8c100000-0x900fffff]
[ 0.425447] pci 0000:00:1c.2: bridge window [mem 0x90900000-0x90afffff 64bit pref]
[ 0.425454] pci 0000:00:1c.4: PCI bridge to [bus 45-85]
[ 0.425458] pci 0000:00:1c.4: bridge window [io 0x3000-0x4fff]
[ 0.425464] pci 0000:00:1c.4: bridge window [mem 0x88100000-0x8c0fffff]
[ 0.425469] pci 0000:00:1c.4: bridge window [mem 0x90b00000-0x90cfffff 64bit pref]
[ 0.425477] pci 0000:86:09.2: res[15]=[mem 0x04000000-0x03ffffff pref] get_res_add_size add_size 4000000
[ 0.425479] pci 0000:86:09.2: res[16]=[mem 0x04000000-0x03ffffff] get_res_add_size add_size 4000000
[ 0.425481] pci 0000:86:09.2: res[13]=[io 0x0100-0x00ff] get_res_add_size add_size 100
[ 0.425483] pci 0000:86:09.2: res[14]=[io 0x0100-0x00ff] get_res_add_size add_size 100
[ 0.425486] pci 0000:86:09.2: BAR 15: assigned [mem 0x94000000-0x97ffffff pref]
[ 0.425491] pci 0000:86:09.2: BAR 16: assigned [mem 0x98000000-0x9bffffff]
[ 0.425495] pci 0000:86:09.2: BAR 13: assigned [io 0x2000-0x20ff]
[ 0.425498] pci 0000:86:09.2: BAR 14: assigned [io 0x2400-0x24ff]
[ 0.425502] pci 0000:86:09.2: CardBus bridge to [bus 87-8a]
[ 0.425505] pci 0000:86:09.2: bridge window [io 0x2000-0x20ff]
[ 0.425511] pci 0000:86:09.2: bridge window [io 0x2400-0x24ff]
[ 0.425516] pci 0000:86:09.2: bridge window [mem 0x94000000-0x97ffffff pref]
[ 0.425522] pci 0000:86:09.2: bridge window [mem 0x98000000-0x9bffffff]
[ 0.425527] pci 0000:00:1e.0: PCI bridge to [bus 86-87]
[ 0.425531] pci 0000:00:1e.0: bridge window [io 0x2000-0x2fff]
[ 0.425537] pci 0000:00:1e.0: bridge window [mem 0x88000000-0x880fffff]
[ 0.425542] pci 0000:00:1e.0: bridge window [mem 0x94000000-0x97ffffff pref]
[ 0.425578] pci 0000:00:1e.0: setting latency timer to 64
[ 0.425589] pci 0000:86:09.2: setting latency timer to 64
[ 0.425593] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
[ 0.425595] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
[ 0.425596] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
[ 0.425598] pci_bus 0000:00: resource 7 [mem 0x80000000-0xdfffffff]
[ 0.425600] pci_bus 0000:00: resource 8 [mem 0xf0000000-0xfedfffff]
[ 0.425602] pci_bus 0000:00: resource 9 [mem 0xfee01000-0xffffffff]
[ 0.425604] pci_bus 0000:01: resource 0 [io 0x7000-0x7fff]
[ 0.425605] pci_bus 0000:01: resource 1 [mem 0x90300000-0x903fffff]
[ 0.425607] pci_bus 0000:01: resource 2 [mem 0x80000000-0x87ffffff 64bit pref]
[ 0.425609] pci_bus 0000:02: resource 0 [io 0x9000-0x9fff]
[ 0.425611] pci_bus 0000:02: resource 1 [mem 0x90200000-0x902fffff]
[ 0.425613] pci_bus 0000:02: resource 2 [mem 0x90500000-0x906fffff 64bit pref]
[ 0.425615] pci_bus 0000:03: resource 0 [io 0xa000-0xafff]
[ 0.425617] pci_bus 0000:03: resource 1 [mem 0x90100000-0x901fffff]
[ 0.425619] pci_bus 0000:03: resource 2 [mem 0x90700000-0x908fffff 64bit pref]
[ 0.425621] pci_bus 0000:04: resource 0 [io 0x5000-0x6fff]
[ 0.425622] pci_bus 0000:04: resource 1 [mem 0x8c100000-0x900fffff]
[ 0.425624] pci_bus 0000:04: resource 2 [mem 0x90900000-0x90afffff 64bit pref]
[ 0.425626] pci_bus 0000:45: resource 0 [io 0x3000-0x4fff]
[ 0.425628] pci_bus 0000:45: resource 1 [mem 0x88100000-0x8c0fffff]
[ 0.425630] pci_bus 0000:45: resource 2 [mem 0x90b00000-0x90cfffff 64bit pref]
[ 0.425631] pci_bus 0000:86: resource 0 [io 0x2000-0x2fff]
[ 0.425633] pci_bus 0000:86: resource 1 [mem 0x88000000-0x880fffff]
[ 0.425635] pci_bus 0000:86: resource 2 [mem 0x94000000-0x97ffffff pref]
[ 0.425637] pci_bus 0000:86: resource 4 [io 0x0000-0x0cf7]
[ 0.425639] pci_bus 0000:86: resource 5 [io 0x0d00-0xffff]
[ 0.425640] pci_bus 0000:86: resource 6 [mem 0x000a0000-0x000bffff]
[ 0.425642] pci_bus 0000:86: resource 7 [mem 0x80000000-0xdfffffff]
[ 0.425644] pci_bus 0000:86: resource 8 [mem 0xf0000000-0xfedfffff]
[ 0.425646] pci_bus 0000:86: resource 9 [mem 0xfee01000-0xffffffff]
[ 0.425648] pci_bus 0000:87: resource 0 [io 0x2000-0x20ff]
[ 0.425649] pci_bus 0000:87: resource 1 [io 0x2400-0x24ff]
[ 0.425651] pci_bus 0000:87: resource 2 [mem 0x94000000-0x97ffffff pref]
[ 0.425653] pci_bus 0000:87: resource 3 [mem 0x98000000-0x9bffffff]
[ 0.425683] NET: Registered protocol family 2
[ 0.425835] TCP established hash table entries: 16384 (order: 6, 262144 bytes)
[ 0.425973] TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
[ 0.426096] TCP: Hash tables configured (established 16384 bind 16384)
[ 0.426164] TCP: reno registered
[ 0.426170] UDP hash table entries: 1024 (order: 3, 32768 bytes)
[ 0.426192] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes)
[ 0.426257] NET: Registered protocol family 1
[ 0.426437] pci 0000:01:00.0: Boot video device
[ 0.426450] PCI: CLS 64 bytes, default 64
[ 0.426493] Trying to unpack rootfs image as initramfs...
[ 2.703404] Freeing initrd memory: 120472k freed
[ 2.777176] DMA-API: preallocated 32768 debug entries
[ 2.777187] DMA-API: debugging enabled by kernel config
[ 2.777213] DMAR: No ATSR found
[ 2.777269] IOMMU 0 0xfeb03000: using Register based invalidation
[ 2.777272] IOMMU 1 0xfeb02000: using Register based invalidation
[ 2.777276] IOMMU: Setting RMRR:
[ 2.777289] IOMMU: Setting identity map for device 0000:00:1d.0 [0x7bb70000 - 0x7bb7ffff]
[ 2.777319] IOMMU: Setting identity map for device 0000:00:1d.1 [0x7bb70000 - 0x7bb7ffff]
[ 2.777343] IOMMU: Setting identity map for device 0000:00:1d.2 [0x7bb70000 - 0x7bb7ffff]
[ 2.777365] IOMMU: Setting identity map for device 0000:00:1d.7 [0x7bb70000 - 0x7bb7ffff]
[ 2.777388] IOMMU: Setting identity map for device 0000:00:1a.0 [0x7bb70000 - 0x7bb7ffff]
[ 2.777410] IOMMU: Setting identity map for device 0000:00:1a.1 [0x7bb70000 - 0x7bb7ffff]
[ 2.777434] IOMMU: Setting identity map for device 0000:00:1a.2 [0x7bb70000 - 0x7bb7ffff]
[ 2.777460] IOMMU: Setting identity map for device 0000:00:1a.7 [0x7bb70000 - 0x7bb7ffff]
[ 2.777475] IOMMU: Prepare 0-16MiB unity mapping for LPC
[ 2.777486] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff]
[ 2.777631] PCI-DMA: Intel(R) Virtualization Technology for Directed I/O
[ 2.778074] audit: initializing netlink socket (disabled)
[ 2.778091] type=2000 audit(1358870837.772:1): initialized
[ 2.803265] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 2.804707] VFS: Disk quotas dquot_6.5.2
[ 2.804748] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 2.805168] fuse init (API version 7.20)
[ 2.805241] msgmni has been set to 3860
[ 2.805559] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 2.805590] io scheduler noop registered
[ 2.805594] io scheduler deadline registered
[ 2.805600] io scheduler cfq registered (default)
[ 2.805710] pcieport 0000:00:01.0: irq 42 for MSI/MSI-X
[ 2.805805] pcieport 0000:00:1c.0: irq 43 for MSI/MSI-X
[ 2.805912] pcieport 0000:00:1c.1: irq 44 for MSI/MSI-X
[ 2.806016] pcieport 0000:00:1c.2: irq 45 for MSI/MSI-X
[ 2.806120] pcieport 0000:00:1c.4: irq 46 for MSI/MSI-X
[ 2.806214] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
[ 2.806218] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[ 2.806222] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
[ 2.806238] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
[ 2.806243] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
[ 2.806258] pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt
[ 2.806261] pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
[ 2.806266] pcie_pme 0000:00:1c.1:pcie01: service driver pcie_pme loaded
[ 2.806283] pcieport 0000:00:1c.2: Signaling PME through PCIe PME interrupt
[ 2.806288] pcie_pme 0000:00:1c.2:pcie01: service driver pcie_pme loaded
[ 2.806303] pcieport 0000:00:1c.4: Signaling PME through PCIe PME interrupt
[ 2.806308] pcie_pme 0000:00:1c.4:pcie01: service driver pcie_pme loaded
[ 2.806321] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 2.806389] pciehp: Using ACPI for slot detection.
[ 2.806420] pciehp 0000:00:1c.2:pcie04: HPC vendor_id 8086 device_id 2944 ss_vid 0 ss_did 0
[ 2.806439] pciehp 0000:00:1c.2:pcie04: service driver pciehp loaded
[ 2.806456] pciehp 0000:00:1c.4:pcie04: HPC vendor_id 8086 device_id 2948 ss_vid 0 ss_did 0
[ 2.806472] pciehp 0000:00:1c.4:pcie04: service driver pciehp loaded
[ 2.806477] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 2.806526] intel_idle: does not run on family 6 model 23
[ 2.806664] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
[ 2.806749] ACPI: AC Adapter [AC] (on-line)
[ 2.806818] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
[ 2.806827] ACPI: Sleep Button [SLPB]
[ 2.806861] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
[ 2.806899] ACPI: Lid Switch [LID]
[ 2.806935] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[ 2.806940] ACPI: Power Button [PWRF]
[ 2.806999] ACPI: Fan [FANG] (off)
[ 2.807040] ACPI: Requesting acpi_cpufreq
[ 2.808434] Monitor-Mwait will be used to enter C-1 state
[ 2.808439] Monitor-Mwait will be used to enter C-2 state
[ 2.808442] tsc: Marking TSC unstable due to TSC halts in idle
[ 2.808448] ACPI: acpi_idle registered with cpuidle
[ 2.812370] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x0000000000000006) is beyond end of object (20121018/exoparg2-418)
[ 2.812379] ACPI Error: Method parse/execution failed [\_TZ_.GETP] (Node ffff88007f735cd0), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
[ 2.812388] ACPI Error: Method parse/execution failed [\_TZ_.GFXZ._CRT] (Node ffff88007f735a78), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
[ 2.812485] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x0000000000000005) is beyond end of object (20121018/exoparg2-418)
[ 2.812492] ACPI Error: Method parse/execution failed [\_TZ_.GETP] (Node ffff88007f735cd0), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
[ 2.812500] ACPI Error: Method parse/execution failed [\_TZ_.GFXZ._AC0] (Node ffff88007f735a50), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
[ 2.812726] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x0000000000000001) is beyond end of object (20121018/exoparg2-418)
[ 2.812736] ACPI Error: Method parse/execution failed [\_TZ_.PSWT] (Node ffff88007f735e10), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
[ 2.812744] ACPI Error: Method parse/execution failed [\_TZ_.GTTP] (Node ffff88007f735dc0), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
[ 2.812752] ACPI Error: Method parse/execution failed [\_TZ_.GFXZ._TMP] (Node ffff88007f735aa0), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
[ 2.812844] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x0000000000000006) is beyond end of object (20121018/exoparg2-418)
[ 2.812851] ACPI Error: Method parse/execution failed [\_TZ_.GETP] (Node ffff88007f735cd0), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
[ 2.812859] ACPI Error: Method parse/execution failed [\_TZ_.GFXZ._CRT] (Node ffff88007f735a78), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
[ 2.812951] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x0000000000000005) is beyond end of object (20121018/exoparg2-418)
[ 2.812959] ACPI Error: Method parse/execution failed [\_TZ_.GETP] (Node ffff88007f735cd0), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
[ 2.812967] ACPI Error: Method parse/execution failed [\_TZ_.GFXZ._AC0] (Node ffff88007f735a50), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
[ 2.812976] [Firmware Bug]: No valid trip found
[ 2.815397] ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x0000000000000001) is beyond end of object (20121018/exoparg2-418)
[ 2.815407] ACPI Error: Method parse/execution failed [\_TZ_.PSWT] (Node ffff88007f735e10), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
[ 2.815415] ACPI Error: Method parse/execution failed [\_TZ_.GTTP] (Node ffff88007f735dc0), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
[ 2.815423] ACPI Error: Method parse/execution failed [\_TZ_.DTSZ._TMP] (Node ffff88007f735fa0), AE_AML_PACKAGE_LIMIT (20121018/psparse-537)
[ 2.815963] thermal LNXTHERM:01: registered as thermal_zone0
[ 2.815968] ACPI: Thermal Zone [DTSZ] (43 C)
[ 2.828006] thermal LNXTHERM:02: registered as thermal_zone1
[ 2.828011] ACPI: Thermal Zone [BATZ] (21 C)
[ 2.831488] thermal LNXTHERM:03: registered as thermal_zone2
[ 2.831492] ACPI: Thermal Zone [CPUZ] (50 C)
[ 2.834852] thermal LNXTHERM:04: registered as thermal_zone3
[ 2.834856] ACPI: Thermal Zone [LOCZ] (29 C)
[ 2.838262] thermal LNXTHERM:05: registered as thermal_zone4
[ 2.838266] ACPI: Thermal Zone [VGAZ] (42 C)
[ 2.838302] GHES: HEST is not enabled!
[ 2.838305] ioatdma: Intel(R) QuickData Technology Driver 4.00
[ 2.838378] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 2.839657] Linux agpgart interface v0.103
[ 2.840959] brd: module loaded
[ 2.841589] loop: module loaded
[ 2.841703] ahci 0000:00:1f.2: version 3.0
[ 2.841746] ahci 0000:00:1f.2: irq 47 for MSI/MSI-X
[ 2.841797] ahci: SSS flag set, parallel bus scan disabled
[ 2.841823] ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 4 ports 3 Gbps 0x23 impl SATA mode
[ 2.841828] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pio slum part ccc ems sxs
[ 2.841834] ahci 0000:00:1f.2: setting latency timer to 64
[ 2.856410] scsi0 : ahci
[ 2.856474] scsi1 : ahci
[ 2.856531] scsi2 : ahci
[ 2.856590] scsi3 : ahci
[ 2.856646] scsi4 : ahci
[ 2.856701] scsi5 : ahci
[ 2.856735] ata1: SATA max UDMA/133 abar m2048@0x90425000 port 0x90425100 irq 47
[ 2.856740] ata2: SATA max UDMA/133 abar m2048@0x90425000 port 0x90425180 irq 47
[ 2.856743] ata3: DUMMY
[ 2.856745] ata4: DUMMY
[ 2.856746] ata5: DUMMY
[ 2.856749] ata6: SATA max UDMA/133 abar m2048@0x90425000 port 0x90425380 irq 47
[ 2.857037] libphy: Fixed MDIO Bus: probed
[ 2.857051] tun: Universal TUN/TAP device driver, 1.6
[ 2.857054] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 2.857092] PPP generic driver version 2.4.2
[ 2.857161] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.857165] ehci-pci: EHCI PCI platform driver
[ 2.857186] ehci-pci 0000:00:1a.7: setting latency timer to 64
[ 2.857189] ehci-pci 0000:00:1a.7: EHCI Host Controller
[ 2.857225] ehci-pci 0000:00:1a.7: new USB bus registered, assigned bus number 1
[ 2.857240] ehci-pci 0000:00:1a.7: debug port 1
[ 2.861172] ehci-pci 0000:00:1a.7: cache line size of 64 is not supported
[ 2.861184] ehci-pci 0000:00:1a.7: irq 19, io mem 0x90425c00
[ 2.872013] ehci-pci 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[ 2.872125] hub 1-0:1.0: USB hub found
[ 2.872130] hub 1-0:1.0: 6 ports detected
[ 2.872531] ehci-pci 0000:00:1d.7: setting latency timer to 64
[ 2.872534] ehci-pci 0000:00:1d.7: EHCI Host Controller
[ 2.872570] ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 2
[ 2.872584] ehci-pci 0000:00:1d.7: debug port 1
[ 2.876492] ehci-pci 0000:00:1d.7: cache line size of 64 is not supported
[ 2.876503] ehci-pci 0000:00:1d.7: irq 20, io mem 0x90425800
[ 2.882065] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
[ 2.882074] ACPI: Battery Slot [BAT0] (battery present)
[ 2.882120] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
[ 2.882128] ACPI: Battery Slot [BAT1] (battery absent)
[ 2.888013] ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 2.888109] hub 2-0:1.0: USB hub found
[ 2.888114] hub 2-0:1.0: 6 ports detected
[ 2.888442] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 2.888453] uhci_hcd: USB Universal Host Controller Interface driver
[ 2.888469] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[ 2.888472] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[ 2.888511] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
[ 2.888542] uhci_hcd 0000:00:1a.0: irq 16, io base 0x000080c0
[ 2.888678] hub 3-0:1.0: USB hub found
[ 2.888683] hub 3-0:1.0: 2 ports detected
[ 2.888823] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[ 2.888826] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[ 2.888861] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
[ 2.888891] uhci_hcd 0000:00:1a.1: irq 17, io base 0x000080a0
[ 2.889017] hub 4-0:1.0: USB hub found
[ 2.889027] hub 4-0:1.0: 2 ports detected
[ 2.889142] uhci_hcd 0000:00:1a.2: setting latency timer to 64
[ 2.889145] uhci_hcd 0000:00:1a.2: UHCI Host Controller
[ 2.889184] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
[ 2.889216] uhci_hcd 0000:00:1a.2: irq 18, io base 0x00008080
[ 2.889345] hub 5-0:1.0: USB hub found
[ 2.889350] hub 5-0:1.0: 2 ports detected
[ 2.889467] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[ 2.889470] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 2.889501] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
[ 2.889524] uhci_hcd 0000:00:1d.0: irq 20, io base 0x00008060
[ 2.889652] hub 6-0:1.0: USB hub found
[ 2.889657] hub 6-0:1.0: 2 ports detected
[ 2.889755] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[ 2.889758] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 2.889792] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
[ 2.889824] uhci_hcd 0000:00:1d.1: irq 22, io base 0x00008040
[ 2.889950] hub 7-0:1.0: USB hub found
[ 2.889955] hub 7-0:1.0: 2 ports detected
[ 2.890070] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[ 2.890073] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 2.890107] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
[ 2.890130] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00008020
[ 2.890254] hub 8-0:1.0: USB hub found
[ 2.890259] hub 8-0:1.0: 2 ports detected
[ 2.890396] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[ 2.892070] i8042: Detected active multiplexing controller, rev 1.1
[ 2.892802] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 2.892809] serio: i8042 AUX0 port at 0x60,0x64 irq 12
[ 2.892833] serio: i8042 AUX1 port at 0x60,0x64 irq 12
[ 2.892855] serio: i8042 AUX2 port at 0x60,0x64 irq 12
[ 2.892873] serio: i8042 AUX3 port at 0x60,0x64 irq 12
[ 2.892970] mousedev: PS/2 mouse device common for all mice
[ 2.893101] rtc_cmos 00:07: RTC can wake from S4
[ 2.893204] rtc_cmos 00:07: rtc core: registered rtc_cmos as rtc0
[ 2.893228] rtc0: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[ 2.893306] device-mapper: uevent: version 1.0.3
[ 2.893365] device-mapper: ioctl: 4.23.1-ioctl (2012-12-18) initialised: dm-devel@redhat.com
[ 2.893395] cpuidle: using governor ladder
[ 2.893427] cpuidle: using governor menu
[ 2.893431] EFI Variables Facility v0.08 2004-May-17
[ 2.893502] TCP: cubic registered
[ 2.893595] NET: Registered protocol family 10
[ 2.893756] NET: Registered protocol family 17
[ 2.893774] Key type dns_resolver registered
[ 2.893985] PM: Hibernation image not present or could not be loaded.
[ 2.893995] registered taskstats version 1
[ 2.895741] Key type trusted registered
[ 2.897232] Key type encrypted registered
[ 2.898991] Magic number: 13:383:136
[ 2.899010] block ram1: hash matches
[ 2.899102] rtc_cmos 00:07: setting system clock to 2013-01-22 16:07:18 UTC (1358870838)
[ 2.899538] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 2.899542] EDD information not available.
[ 2.915000] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[ 3.176097] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3.177077] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 3.177260] ata1.00: ATA-8: ST9160412AS, 0003HPM1, max UDMA/100
[ 3.177267] ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[ 3.218663] ata1.00: failed to get Identify Device Data, Emask 0x1
[ 3.220770] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 3.221488] ata1.00: failed to get Identify Device Data, Emask 0x1
[ 3.221493] ata1.00: configured for UDMA/100
[ 3.221674] scsi 0:0:0:0: Direct-Access ATA ST9160412AS 0003 PQ: 0 ANSI: 5
[ 3.221812] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 3.221822] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
[ 3.221867] sd 0:0:0:0: [sda] Write Protect is off
[ 3.221871] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 3.221890] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.252772] sda: sda1 sda2 < sda5 >
[ 3.253198] sd 0:0:0:0: [sda] Attached SCSI disk
[ 3.424124] usb 4-1: new full-speed USB device number 2 using uhci_hcd
[ 3.540136] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 3.553073] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 3.553078] ata2.00: ATAPI: Optiarc DVD RW AD-7561S, AH03, max UDMA/100
[ 3.566900] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[ 3.566906] ata2.00: configured for UDMA/100
[ 3.568321] scsi 1:0:0:0: CD-ROM Optiarc DVD RW AD-7561S AH03 PQ: 0 ANSI: 5
[ 3.572147] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[ 3.572155] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 3.572285] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 3.572349] sr 1:0:0:0: Attached scsi generic sg1 type 5
[ 3.892146] ata6: SATA link down (SStatus 0 SControl 300)
[ 3.893574] Freeing unused kernel memory: 964k freed
[ 3.893931] Write protecting the kernel read-only data: 12288k
[ 3.897539] Freeing unused kernel memory: 1304k freed
[ 3.900980] Freeing unused kernel memory: 1116k freed
[ 3.914593] udevd[104]: starting version 175
[ 3.960986] e1000e: Intel(R) PRO/1000 Network Driver - 2.1.4-k
[ 3.960994] e1000e: Copyright(c) 1999 - 2012 Intel Corporation.
[ 3.961030] e1000e 0000:00:19.0: setting latency timer to 64
[ 3.961095] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 3.961132] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 4.002006] firewire_ohci 0000:86:09.0: setting latency timer to 64
[ 4.002776] sdhci: Secure Digital Host Controller Interface driver
[ 4.002782] sdhci: Copyright(c) Pierre Ossman
[ 4.064057] firewire_ohci 0000:86:09.0: added OHCI v1.10 device as card 0, 4 IR + 4 IT contexts, quirks 0x11
[ 4.064137] sdhci-pci 0000:86:09.1: SDHCI controller found [1180:0822] (rev 25)
[ 4.065167] sdhci-pci 0000:86:09.1: Will use DMA mode even though HW doesn't fully claim to support it.
[ 4.065175] sdhci-pci 0000:86:09.1: setting latency timer to 64
[ 4.065179] mmc0: no vqmmc regulator found
[ 4.065181] mmc0: no vmmc regulator found
[ 4.066181] sdhci-pci 0000:86:09.1: Will use DMA mode even though HW doesn't fully claim to support it.
[ 4.096039] mmc0: SDHCI controller on PCI [0000:86:09.1] using DMA
[ 4.126235] sdhci-pci 0000:86:09.1: Will use DMA mode even though HW doesn't fully claim to support it.
[ 4.154046] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:26:55:11:f1:6f
[ 4.154052] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 4.154075] e1000e 0000:00:19.0 eth0: MAC: 7, PHY: 8, PBA No: 1052FF-0FF
[ 4.186280] sdhci-pci 0000:86:09.1: Will use DMA mode even though HW doesn't fully claim to support it.
[ 4.246726] sdhci-pci 0000:86:09.1: Will use DMA mode even though HW doesn't fully claim to support it.
[ 4.251840] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[ 4.251844] EXT4-fs (sda1): write access will be enabled during recovery
[ 4.306201] sdhci-pci 0000:86:09.1: Will use DMA mode even though HW doesn't fully claim to support it.
[ 4.564107] firewire_core 0000:86:09.0: created device fw0: GUID 5566778811223344, S400
[ 6.253913] EXT4-fs (sda1): recovery complete
[ 6.261748] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 8.153870] init: ureadahead main process (268) terminated with status 5
[ 10.418750] Adding 2089980k swap on /dev/sda5. Priority:-1 extents:1 across:2089980k
[ 10.433358] udevd[363]: starting version 175
[ 11.601401] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ 11.910214] lp: driver loaded but no devices found
[ 13.528437] parport_pc 00:08: reported by Plug and Play ACPI
[ 13.528497] parport0: PC-style at 0x378 (0x778), irq 5, using FIFO [PCSPP,TRISTATE,COMPAT,ECP]
[ 13.624185] lp0: using parport0 (interrupt-driven).
[ 13.703745] microcode: CPU0 sig=0x1067a, pf=0x80, revision=0xa07
[ 13.974550] ppdev: user-space parallel port driver
[ 13.982263] tpm_tis 00:03: 1.2 TPM (device-id 0xB, rev-id 16)
[ 14.112069] tpm_tis 00:03: Adjusting TPM timeout parameters.
[ 14.263445] wmi: Mapper loaded
[ 14.388883] acpi device:02: registered as cooling_device3
[ 14.389030] ACPI: Video Device [DGFX] (multi-head: yes rom: no post: no)
[ 14.389127] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/LNXVIDEO:00/input/input4
[ 14.690489] device-mapper: multipath: version 1.5.0 loaded
[ 14.808864] microcode: CPU1 sig=0x1067a, pf=0x80, revision=0xa07
[ 14.810130] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 14.832213] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20121018/utaddress-251)
[ 14.832219] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 14.832222] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
[ 14.832225] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 14.832227] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251)
[ 14.832229] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 14.832231] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 15.000409] hp_accel: hardware type NC693xx found
[ 15.004707] lis3lv02d: 8 bits sensor found
[ 15.004860] input: HP WMI hotkeys as /devices/virtual/input/input5
[ 15.060215] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input6
[ 15.300047] tpm_tis 00:03: TPM is disabled/deactivated (0x7)
[ 15.433708] yenta_cardbus 0000:86:09.2: CardBus bridge found [103c:30dc]
[ 15.560678] yenta_cardbus 0000:86:09.2: ISA IRQ mask 0x0c98, PCI irq 22
[ 15.560682] yenta_cardbus 0000:86:09.2: Socket status: 30000810
[ 15.560685] pci_bus 0000:86: Raising subordinate bus# of parent bus (#86) from #87 to #8a
[ 15.560692] yenta_cardbus 0000:86:09.2: pcmcia: parent PCI bridge window: [io 0x2000-0x2fff]
[ 15.560695] yenta_cardbus 0000:86:09.2: pcmcia: parent PCI bridge window: [mem 0x88000000-0x880fffff]
[ 15.560697] pcmcia_socket pcmcia_socket0: cs: memory probe 0x88000000-0x880fffff:
[ 15.560701] excluding 0x88000000-0x8800ffff
[ 15.560708] yenta_cardbus 0000:86:09.2: pcmcia: parent PCI bridge window: [mem 0x94000000-0x97ffffff pref]
[ 15.560710] pcmcia_socket pcmcia_socket0: cs: memory probe 0x94000000-0x97ffffff:
[ 15.560718] excluding 0x94000000-0x97ffffff
[ 16.452019] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 16.473316] pcmcia_socket pcmcia_socket0: cs: memory probe 0x88010000-0x880fffff:
[ 16.476961] excluding 0x880fe000-0x8810bfff
[ 16.477072] pcmcia 0.0: pcmcia: registering new device pcmcia0.0 (IRQ: 22)
[ 17.055145] psmouse serio4: synaptics: Touchpad model: 1, fw: 7.0, id: 0x1c0b1, caps: 0xd04791/0xb00000/0x20000, board id: 71, fw id: 504136
[ 17.055151] psmouse serio4: synaptics: serio: Synaptics pass-through port at isa0060/serio4/input0
[ 17.094977] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input7
[ 17.430521] [drm] Initialized drm 1.1.0 20060810
[ 17.479217] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff:
[ 17.479226] excluding 0xc0000-0xfffff
[ 17.479241] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff:
[ 17.479254] clean.
[ 17.479267] pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff:
[ 17.479273] excluding 0x60000000-0x60ffffff
[ 18.109569] cfg80211: Calling CRDA to update world regulatory domain
[ 18.213077] scsi6 : pata_pcmcia
[ 18.213124] ata7: PATA max PIO0 cmd 0x2100 ctl 0x210e irq 22
[ 18.961829] Intel(R) Wireless WiFi driver for Linux, in-tree:
[ 18.961833] Copyright(c) 2003-2012 Intel Corporation
[ 18.961966] iwlwifi 0000:03:00.0: irq 49 for MSI/MSI-X
[ 19.211082] iwlwifi 0000:03:00.0: loaded firmware version 8.83.5.1 build 33692
[ 19.547910] cfg80211: World regulatory domain updated:
[ 19.547914] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 19.547917] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 19.547918] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 19.547920] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 19.547921] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 19.547923] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 20.656451] type=1400 audit(1358870856.253:2): apparmor="STATUS" operation="profile_load" name="/sbin/dhclient" pid=810 comm="apparmor_parser"
[ 20.656461] type=1400 audit(1358870856.253:3): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=811 comm="apparmor_parser"
[ 20.656793] type=1400 audit(1358870856.253:4): apparmor="STATUS" operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=810 comm="apparmor_parser"
[ 20.656801] type=1400 audit(1358870856.253:5): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=811 comm="apparmor_parser"
[ 20.656988] type=1400 audit(1358870856.253:6): apparmor="STATUS" operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" pid=810 comm="apparmor_parser"
[ 20.656997] type=1400 audit(1358870856.253:7): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=811 comm="apparmor_parser"
[ 21.883383] snd_hda_intel 0000:00:1b.0: irq 50 for MSI/MSI-X
[ 22.046982] input: PS/2 Generic Mouse as /devices/platform/i8042/serio4/serio5/input/input8
[ 22.150520] [drm] radeon defaulting to kernel modesetting.
[ 22.150524] [drm] radeon kernel modesetting enabled.
[ 22.150793] [drm] initializing kernel modesetting (RV620 0x1002:0x95C4 0x103C:0x30DC).
[ 22.150815] [drm] register mmio base: 0x90300000
[ 22.150817] [drm] register mmio size: 65536
[ 22.150918] ATOM BIOS: HP
[ 22.150941] radeon 0000:01:00.0: VRAM: 128M 0x0000000000000000 - 0x0000000007FFFFFF (128M used)
[ 22.150943] radeon 0000:01:00.0: GTT: 512M 0x0000000008000000 - 0x0000000027FFFFFF
[ 22.153790] [drm] Detected VRAM RAM=128M, BAR=128M
[ 22.153793] [drm] RAM width 64bits DDR
[ 22.153850] [TTM] Zone kernel: Available graphics memory: 989986 kiB
[ 22.153852] [TTM] Initializing pool allocator
[ 22.153857] [TTM] Initializing DMA pool allocator
[ 22.153884] [drm] radeon: 128M of VRAM memory ready
[ 22.153885] [drm] radeon: 512M of GTT memory ready.
[ 22.153902] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 22.153903] [drm] Driver supports precise vblank timestamp query.
[ 22.153947] radeon 0000:01:00.0: irq 51 for MSI/MSI-X
[ 22.153958] radeon 0000:01:00.0: radeon: using MSI.
[ 22.153988] [drm] radeon: irq initialized.
[ 22.154034] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 22.154796] [drm] probing gen 2 caps for device 8086:2a41 = 1/0
[ 22.154969] [drm] Loading RV620 Microcode
[ 22.218044] dmar: DRHD: handling fault status reg 3
[ 22.218054] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80000000
[ 22.218054] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218083] dmar: DRHD: handling fault status reg 3
[ 22.218089] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80002000
[ 22.218089] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218123] dmar: DRHD: handling fault status reg 3
[ 22.218128] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80004000
[ 22.218128] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218155] dmar: DRHD: handling fault status reg 3
[ 22.218159] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80006000
[ 22.218159] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218169] dmar: DRHD: handling fault status reg 3
[ 22.218173] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80007000
[ 22.218173] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218191] dmar: DRHD: handling fault status reg 3
[ 22.218195] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80009000
[ 22.218195] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218205] dmar: DRHD: handling fault status reg 3
[ 22.218209] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8000a000
[ 22.218209] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218228] dmar: DRHD: handling fault status reg 3
[ 22.218232] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8000b000
[ 22.218232] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218242] dmar: DRHD: handling fault status reg 3
[ 22.218246] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8000c000
[ 22.218246] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218264] dmar: DRHD: handling fault status reg 3
[ 22.218268] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8000d000
[ 22.218268] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218278] dmar: DRHD: handling fault status reg 3
[ 22.218282] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8000e000
[ 22.218282] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218301] dmar: DRHD: handling fault status reg 3
[ 22.218305] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8000f000
[ 22.218305] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218315] dmar: DRHD: handling fault status reg 3
[ 22.218319] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80010000
[ 22.218319] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218337] dmar: DRHD: handling fault status reg 3
[ 22.218341] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80012000
[ 22.218341] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218352] dmar: DRHD: handling fault status reg 3
[ 22.218356] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80013000
[ 22.218356] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218374] dmar: DRHD: handling fault status reg 3
[ 22.218378] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80014000
[ 22.218378] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218388] dmar: DRHD: handling fault status reg 3
[ 22.218392] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80015000
[ 22.218392] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218411] dmar: DRHD: handling fault status reg 3
[ 22.218415] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80016000
[ 22.218415] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218451] dmar: DRHD: handling fault status reg 3
[ 22.218455] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80018000
[ 22.218455] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218484] dmar: DRHD: handling fault status reg 3
[ 22.218488] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8001b000
[ 22.218488] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218497] dmar: DRHD: handling fault status reg 3
[ 22.218502] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8001c000
[ 22.218502] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218538] dmar: DRHD: handling fault status reg 3
[ 22.218542] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8001d000
[ 22.218542] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218552] dmar: DRHD: handling fault status reg 3
[ 22.218557] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8001e000
[ 22.218557] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218574] dmar: DRHD: handling fault status reg 3
[ 22.218579] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8001f000
[ 22.218579] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218589] dmar: DRHD: handling fault status reg 3
[ 22.218593] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80020000
[ 22.218593] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218611] dmar: DRHD: handling fault status reg 3
[ 22.218615] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80021000
[ 22.218615] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218625] dmar: DRHD: handling fault status reg 3
[ 22.218630] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80022000
[ 22.218630] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218648] dmar: DRHD: handling fault status reg 3
[ 22.218652] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80024000
[ 22.218652] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218662] dmar: DRHD: handling fault status reg 3
[ 22.218666] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80025000
[ 22.218666] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218684] dmar: DRHD: handling fault status reg 3
[ 22.218688] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80026000
[ 22.218688] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218698] dmar: DRHD: handling fault status reg 3
[ 22.218703] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80027000
[ 22.218703] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218721] dmar: DRHD: handling fault status reg 3
[ 22.218725] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80028000
[ 22.218725] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218735] dmar: DRHD: handling fault status reg 3
[ 22.218739] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80029000
[ 22.218739] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218757] dmar: DRHD: handling fault status reg 3
[ 22.218761] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8002a000
[ 22.218761] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218772] dmar: DRHD: handling fault status reg 3
[ 22.218776] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8002b000
[ 22.218776] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218794] dmar: DRHD: handling fault status reg 3
[ 22.218798] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8002d000
[ 22.218798] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218808] dmar: DRHD: handling fault status reg 3
[ 22.218812] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8002e000
[ 22.218812] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218830] dmar: DRHD: handling fault status reg 3
[ 22.218834] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8002f000
[ 22.218834] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218845] dmar: DRHD: handling fault status reg 3
[ 22.218849] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80030000
[ 22.218849] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218867] dmar: DRHD: handling fault status reg 3
[ 22.218871] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80031000
[ 22.218871] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218881] dmar: DRHD: handling fault status reg 3
[ 22.218886] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80032000
[ 22.218886] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218903] dmar: DRHD: handling fault status reg 3
[ 22.218907] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80033000
[ 22.218907] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218918] dmar: DRHD: handling fault status reg 3
[ 22.218922] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80035000
[ 22.218922] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218940] dmar: DRHD: handling fault status reg 3
[ 22.218944] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80036000
[ 22.218944] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218954] dmar: DRHD: handling fault status reg 3
[ 22.218958] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80037000
[ 22.218958] DMAR:[fault reason 06] PTE Read access is not set
[ 22.218994] dmar: DRHD: handling fault status reg 3
[ 22.218998] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80038000
[ 22.218998] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219009] dmar: DRHD: handling fault status reg 3
[ 22.219013] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80039000
[ 22.219013] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219031] dmar: DRHD: handling fault status reg 3
[ 22.219035] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8003a000
[ 22.219035] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219046] dmar: DRHD: handling fault status reg 3
[ 22.219050] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8003b000
[ 22.219050] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219067] dmar: DRHD: handling fault status reg 3
[ 22.219071] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8003c000
[ 22.219071] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219082] dmar: DRHD: handling fault status reg 3
[ 22.219087] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8003d000
[ 22.219087] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219104] dmar: DRHD: handling fault status reg 3
[ 22.219108] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8003f000
[ 22.219108] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219119] dmar: DRHD: handling fault status reg 3
[ 22.219123] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80040000
[ 22.219123] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219140] dmar: DRHD: handling fault status reg 3
[ 22.219144] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80041000
[ 22.219144] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219155] dmar: DRHD: handling fault status reg 3
[ 22.219159] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80042000
[ 22.219159] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219177] dmar: DRHD: handling fault status reg 3
[ 22.219181] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80043000
[ 22.219181] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219192] dmar: DRHD: handling fault status reg 3
[ 22.219196] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80044000
[ 22.219196] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219213] dmar: DRHD: handling fault status reg 3
[ 22.219217] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80045000
[ 22.219217] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219228] dmar: DRHD: handling fault status reg 3
[ 22.219233] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80046000
[ 22.219233] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219250] dmar: DRHD: handling fault status reg 3
[ 22.219254] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80048000
[ 22.219254] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219265] dmar: DRHD: handling fault status reg 3
[ 22.219269] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80049000
[ 22.219269] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219286] dmar: DRHD: handling fault status reg 3
[ 22.219290] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8004a000
[ 22.219290] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219301] dmar: DRHD: handling fault status reg 3
[ 22.219306] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8004b000
[ 22.219306] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219323] dmar: DRHD: handling fault status reg 3
[ 22.219327] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8004c000
[ 22.219327] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219337] dmar: DRHD: handling fault status reg 3
[ 22.219342] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8004d000
[ 22.219342] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219359] dmar: DRHD: handling fault status reg 3
[ 22.219363] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8004e000
[ 22.219363] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219374] dmar: DRHD: handling fault status reg 3
[ 22.219378] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8004f000
[ 22.219378] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219396] dmar: DRHD: handling fault status reg 3
[ 22.219400] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80051000
[ 22.219400] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219411] dmar: DRHD: handling fault status reg 3
[ 22.219415] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80052000
[ 22.219415] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219451] dmar: DRHD: handling fault status reg 3
[ 22.219455] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80053000
[ 22.219455] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219465] dmar: DRHD: handling fault status reg 3
[ 22.219470] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80054000
[ 22.219470] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219487] dmar: DRHD: handling fault status reg 3
[ 22.219491] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80055000
[ 22.219491] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219502] dmar: DRHD: handling fault status reg 3
[ 22.219506] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80056000
[ 22.219506] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219524] dmar: DRHD: handling fault status reg 3
[ 22.219528] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80057000
[ 22.219528] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219539] dmar: DRHD: handling fault status reg 3
[ 22.219543] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80058000
[ 22.219543] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219561] dmar: DRHD: handling fault status reg 3
[ 22.219565] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8005a000
[ 22.219565] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219601] dmar: DRHD: handling fault status reg 3
[ 22.219606] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8005c000
[ 22.219606] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219633] dmar: DRHD: handling fault status reg 3
[ 22.219637] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8005e000
[ 22.219637] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219648] dmar: DRHD: handling fault status reg 3
[ 22.219652] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8005f000
[ 22.219652] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219670] dmar: DRHD: handling fault status reg 3
[ 22.219674] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80060000
[ 22.219674] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219685] dmar: DRHD: handling fault status reg 3
[ 22.219689] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80061000
[ 22.219689] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219707] dmar: DRHD: handling fault status reg 3
[ 22.219711] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80063000
[ 22.219711] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219747] dmar: DRHD: handling fault status reg 3
[ 22.219752] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80065000
[ 22.219752] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219779] dmar: DRHD: handling fault status reg 3
[ 22.219783] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80067000
[ 22.219783] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219794] dmar: DRHD: handling fault status reg 3
[ 22.219798] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80068000
[ 22.219798] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219816] dmar: DRHD: handling fault status reg 3
[ 22.219820] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80069000
[ 22.219820] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219831] dmar: DRHD: handling fault status reg 3
[ 22.219836] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8006a000
[ 22.219836] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219852] dmar: DRHD: handling fault status reg 3
[ 22.219856] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8006c000
[ 22.219856] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219867] dmar: DRHD: handling fault status reg 3
[ 22.219872] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8006d000
[ 22.219872] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219907] dmar: DRHD: handling fault status reg 3
[ 22.219911] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8006e000
[ 22.219911] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219922] dmar: DRHD: handling fault status reg 3
[ 22.219926] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8006f000
[ 22.219926] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219943] dmar: DRHD: handling fault status reg 3
[ 22.219948] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80070000
[ 22.219948] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219959] dmar: DRHD: handling fault status reg 3
[ 22.219963] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80071000
[ 22.219963] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219981] dmar: DRHD: handling fault status reg 3
[ 22.219985] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80072000
[ 22.219985] DMAR:[fault reason 06] PTE Read access is not set
[ 22.219995] dmar: DRHD: handling fault status reg 3
[ 22.219999] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80073000
[ 22.219999] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220019] dmar: DRHD: handling fault status reg 3
[ 22.220025] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80075000
[ 22.220025] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220055] dmar: DRHD: handling fault status reg 3
[ 22.220060] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80077000
[ 22.220060] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220092] dmar: DRHD: handling fault status reg 3
[ 22.220096] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80079000
[ 22.220096] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220130] dmar: DRHD: handling fault status reg 3
[ 22.220135] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8007b000
[ 22.220135] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220165] dmar: DRHD: handling fault status reg 3
[ 22.220169] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8007e000
[ 22.220169] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220201] dmar: DRHD: handling fault status reg 3
[ 22.220206] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80080000
[ 22.220206] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220211] dmar: DRHD: handling fault status reg 3
[ 22.220216] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80082000
[ 22.220216] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220238] dmar: DRHD: handling fault status reg 3
[ 22.220242] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80082000
[ 22.220242] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220249] dmar: DRHD: handling fault status reg 3
[ 22.220257] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80083000
[ 22.220257] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220275] dmar: DRHD: handling fault status reg 3
[ 22.220279] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80084000
[ 22.220279] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220311] dmar: DRHD: handling fault status reg 3
[ 22.220315] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80087000
[ 22.220315] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220366] dmar: DRHD: handling fault status reg 3
[ 22.220370] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80089000
[ 22.220370] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220376] dmar: DRHD: handling fault status reg 3
[ 22.220380] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8008a000
[ 22.220380] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220403] dmar: DRHD: handling fault status reg 3
[ 22.220407] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8008b000
[ 22.220407] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220439] dmar: DRHD: handling fault status reg 3
[ 22.220444] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8008d000
[ 22.220444] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220476] dmar: DRHD: handling fault status reg 3
[ 22.220480] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80090000
[ 22.220480] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220511] dmar: DRHD: handling fault status reg 3
[ 22.220516] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80092000
[ 22.220516] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220522] dmar: DRHD: handling fault status reg 3
[ 22.220526] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80093000
[ 22.220526] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220549] dmar: DRHD: handling fault status reg 3
[ 22.220553] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80094000
[ 22.220553] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220559] dmar: DRHD: handling fault status reg 3
[ 22.220564] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80096000
[ 22.220564] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220585] dmar: DRHD: handling fault status reg 3
[ 22.220592] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80096000
[ 22.220592] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220622] dmar: DRHD: handling fault status reg 3
[ 22.220626] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80099000
[ 22.220626] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220659] dmar: DRHD: handling fault status reg 3
[ 22.220663] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8009b000
[ 22.220663] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220694] dmar: DRHD: handling fault status reg 3
[ 22.220699] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8009d000
[ 22.220699] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220731] dmar: DRHD: handling fault status reg 3
[ 22.220735] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8009f000
[ 22.220735] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220768] dmar: DRHD: handling fault status reg 3
[ 22.220773] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800a2000
[ 22.220773] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220822] dmar: DRHD: handling fault status reg 3
[ 22.220826] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800a4000
[ 22.220826] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220832] dmar: DRHD: handling fault status reg 3
[ 22.220837] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800a5000
[ 22.220837] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220859] dmar: DRHD: handling fault status reg 3
[ 22.220863] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800a6000
[ 22.220863] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220869] dmar: DRHD: handling fault status reg 3
[ 22.220873] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800a7000
[ 22.220873] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220895] dmar: DRHD: handling fault status reg 3
[ 22.220899] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800a8000
[ 22.220899] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220905] dmar: DRHD: handling fault status reg 3
[ 22.220909] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800aa000
[ 22.220909] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220932] dmar: DRHD: handling fault status reg 3
[ 22.220937] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800ab000
[ 22.220937] DMAR:[fault reason 06] PTE Read access is not set
[ 22.220968] dmar: DRHD: handling fault status reg 3
[ 22.220973] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800ad000
[ 22.220973] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221004] dmar: DRHD: handling fault status reg 3
[ 22.221009] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800af000
[ 22.221009] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221041] dmar: DRHD: handling fault status reg 3
[ 22.221045] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800b1000
[ 22.221045] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221051] dmar: DRHD: handling fault status reg 3
[ 22.221055] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800b2000
[ 22.221055] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221078] dmar: DRHD: handling fault status reg 3
[ 22.221083] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800b4000
[ 22.221083] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221115] dmar: DRHD: handling fault status reg 3
[ 22.221119] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800b6000
[ 22.221119] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221151] dmar: DRHD: handling fault status reg 3
[ 22.221156] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800b8000
[ 22.221156] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221188] dmar: DRHD: handling fault status reg 3
[ 22.221192] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800ba000
[ 22.221192] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221223] dmar: DRHD: handling fault status reg 3
[ 22.221228] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800bd000
[ 22.221228] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221279] dmar: DRHD: handling fault status reg 3
[ 22.221283] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800bf000
[ 22.221283] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221315] dmar: DRHD: handling fault status reg 3
[ 22.221319] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800c1000
[ 22.221319] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221325] dmar: DRHD: handling fault status reg 3
[ 22.221329] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800c2000
[ 22.221329] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221351] dmar: DRHD: handling fault status reg 3
[ 22.221356] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800c3000
[ 22.221356] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221388] dmar: DRHD: handling fault status reg 3
[ 22.221392] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800c6000
[ 22.221392] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221399] dmar: DRHD: handling fault status reg 3
[ 22.221404] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800c8000
[ 22.221404] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221424] dmar: DRHD: handling fault status reg 3
[ 22.221428] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800c8000
[ 22.221428] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221435] dmar: DRHD: handling fault status reg 3
[ 22.221439] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800c9000
[ 22.221439] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221461] dmar: DRHD: handling fault status reg 3
[ 22.221465] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800ca000
[ 22.221465] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221471] dmar: DRHD: handling fault status reg 3
[ 22.221476] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800cb000
[ 22.221476] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221497] dmar: DRHD: handling fault status reg 3
[ 22.221501] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800cc000
[ 22.221501] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221508] dmar: DRHD: handling fault status reg 3
[ 22.221513] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800cd000
[ 22.221513] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221534] dmar: DRHD: handling fault status reg 3
[ 22.221538] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800cf000
[ 22.221538] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221571] dmar: DRHD: handling fault status reg 3
[ 22.221576] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800d1000
[ 22.221576] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221607] dmar: DRHD: handling fault status reg 3
[ 22.221611] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800d3000
[ 22.221611] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221618] dmar: DRHD: handling fault status reg 3
[ 22.221622] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800d4000
[ 22.221622] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221643] dmar: DRHD: handling fault status reg 3
[ 22.221647] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800d5000
[ 22.221647] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221654] dmar: DRHD: handling fault status reg 3
[ 22.221658] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800d6000
[ 22.221658] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221680] dmar: DRHD: handling fault status reg 3
[ 22.221684] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800d8000
[ 22.221684] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221735] dmar: DRHD: handling fault status reg 3
[ 22.221740] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800da000
[ 22.221740] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221771] dmar: DRHD: handling fault status reg 3
[ 22.221775] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800dc000
[ 22.221775] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221782] dmar: DRHD: handling fault status reg 3
[ 22.221787] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800dd000
[ 22.221787] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221808] dmar: DRHD: handling fault status reg 3
[ 22.221812] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800de000
[ 22.221812] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221844] dmar: DRHD: handling fault status reg 3
[ 22.221849] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800e1000
[ 22.221849] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221854] dmar: DRHD: handling fault status reg 3
[ 22.221859] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800e2000
[ 22.221859] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221881] dmar: DRHD: handling fault status reg 3
[ 22.221886] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800e3000
[ 22.221886] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221917] dmar: DRHD: handling fault status reg 3
[ 22.221921] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800e5000
[ 22.221921] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221928] dmar: DRHD: handling fault status reg 3
[ 22.221932] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800e6000
[ 22.221932] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221954] dmar: DRHD: handling fault status reg 3
[ 22.221958] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800e7000
[ 22.221958] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221964] dmar: DRHD: handling fault status reg 3
[ 22.221969] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800e8000
[ 22.221969] DMAR:[fault reason 06] PTE Read access is not set
[ 22.221991] dmar: DRHD: handling fault status reg 3
[ 22.221995] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800ea000
[ 22.221995] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222027] dmar: DRHD: handling fault status reg 3
[ 22.222032] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800ec000
[ 22.222032] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222064] dmar: DRHD: handling fault status reg 3
[ 22.222068] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800ee000
[ 22.222068] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222101] dmar: DRHD: handling fault status reg 3
[ 22.222106] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800f0000
[ 22.222106] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222136] dmar: DRHD: handling fault status reg 3
[ 22.222140] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800f3000
[ 22.222140] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222147] dmar: DRHD: handling fault status reg 3
[ 22.222151] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800f4000
[ 22.222151] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222191] dmar: DRHD: handling fault status reg 3
[ 22.222195] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800f5000
[ 22.222195] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222201] dmar: DRHD: handling fault status reg 3
[ 22.222207] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800f6000
[ 22.222207] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222228] dmar: DRHD: handling fault status reg 3
[ 22.222233] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800f7000
[ 22.222233] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222264] dmar: DRHD: handling fault status reg 3
[ 22.222269] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800f9000
[ 22.222269] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222300] dmar: DRHD: handling fault status reg 3
[ 22.222304] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800fc000
[ 22.222304] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222311] dmar: DRHD: handling fault status reg 3
[ 22.222316] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800fd000
[ 22.222316] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222338] dmar: DRHD: handling fault status reg 3
[ 22.222342] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 800fe000
[ 22.222342] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222374] dmar: DRHD: handling fault status reg 3
[ 22.222378] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80100000
[ 22.222378] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222411] dmar: DRHD: handling fault status reg 3
[ 22.222415] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80102000
[ 22.222415] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222447] dmar: DRHD: handling fault status reg 3
[ 22.222451] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80105000
[ 22.222451] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222484] dmar: DRHD: handling fault status reg 3
[ 22.222488] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80107000
[ 22.222488] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222520] dmar: DRHD: handling fault status reg 3
[ 22.222524] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80109000
[ 22.222524] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222556] dmar: DRHD: handling fault status reg 3
[ 22.222560] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8010b000
[ 22.222560] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222567] dmar: DRHD: handling fault status reg 3
[ 22.222571] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8010c000
[ 22.222571] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222593] dmar: DRHD: handling fault status reg 3
[ 22.222597] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8010e000
[ 22.222597] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222647] dmar: DRHD: handling fault status reg 3
[ 22.222652] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80110000
[ 22.222652] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222684] dmar: DRHD: handling fault status reg 3
[ 22.222688] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80112000
[ 22.222688] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222721] dmar: DRHD: handling fault status reg 3
[ 22.222725] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80114000
[ 22.222725] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222757] dmar: DRHD: handling fault status reg 3
[ 22.222761] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80117000
[ 22.222761] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222767] dmar: DRHD: handling fault status reg 3
[ 22.222773] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80118000
[ 22.222773] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222794] dmar: DRHD: handling fault status reg 3
[ 22.222798] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80119000
[ 22.222798] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222830] dmar: DRHD: handling fault status reg 3
[ 22.222834] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8011b000
[ 22.222834] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222867] dmar: DRHD: handling fault status reg 3
[ 22.222871] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8011d000
[ 22.222871] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222877] dmar: DRHD: handling fault status reg 3
[ 22.222882] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8011f000
[ 22.222882] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222903] dmar: DRHD: handling fault status reg 3
[ 22.222907] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80120000
[ 22.222907] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222913] dmar: DRHD: handling fault status reg 3
[ 22.222918] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80121000
[ 22.222918] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222939] dmar: DRHD: handling fault status reg 3
[ 22.222943] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80122000
[ 22.222943] DMAR:[fault reason 06] PTE Read access is not set
[ 22.222976] dmar: DRHD: handling fault status reg 3
[ 22.222981] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80124000
[ 22.222981] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223013] dmar: DRHD: handling fault status reg 3
[ 22.223017] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80126000
[ 22.223017] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223050] dmar: DRHD: handling fault status reg 3
[ 22.223056] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80129000
[ 22.223056] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223103] dmar: DRHD: handling fault status reg 3
[ 22.223107] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8012b000
[ 22.223107] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223114] dmar: DRHD: handling fault status reg 3
[ 22.223119] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8012c000
[ 22.223119] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223140] dmar: DRHD: handling fault status reg 3
[ 22.223144] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8012d000
[ 22.223144] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223151] dmar: DRHD: handling fault status reg 3
[ 22.223156] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8012e000
[ 22.223156] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223177] dmar: DRHD: handling fault status reg 3
[ 22.223181] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8012f000
[ 22.223181] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223188] dmar: DRHD: handling fault status reg 2
[ 22.223192] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80131000
[ 22.223192] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223213] dmar: DRHD: handling fault status reg 3
[ 22.223217] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80132000
[ 22.223217] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223224] dmar: DRHD: handling fault status reg 3
[ 22.223229] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80133000
[ 22.223229] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223250] dmar: DRHD: handling fault status reg 3
[ 22.223254] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80134000
[ 22.223254] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223287] dmar: DRHD: handling fault status reg 3
[ 22.223293] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80136000
[ 22.223293] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223323] dmar: DRHD: handling fault status reg 3
[ 22.223327] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80138000
[ 22.223327] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223333] dmar: DRHD: handling fault status reg 3
[ 22.223338] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8013a000
[ 22.223338] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223359] dmar: DRHD: handling fault status reg 3
[ 22.223363] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8013b000
[ 22.223363] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223396] dmar: DRHD: handling fault status reg 3
[ 22.223401] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8013d000
[ 22.223401] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223433] dmar: DRHD: handling fault status reg 3
[ 22.223437] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8013f000
[ 22.223437] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223469] dmar: DRHD: handling fault status reg 3
[ 22.223474] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80141000
[ 22.223474] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223505] dmar: DRHD: handling fault status reg 3
[ 22.223509] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80144000
[ 22.223509] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223516] dmar: DRHD: handling fault status reg 3
[ 22.223521] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80145000
[ 22.223521] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223560] dmar: DRHD: handling fault status reg 3
[ 22.223565] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80146000
[ 22.223565] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223597] dmar: DRHD: handling fault status reg 3
[ 22.223602] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80148000
[ 22.223602] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223633] dmar: DRHD: handling fault status reg 3
[ 22.223637] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8014a000
[ 22.223637] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223644] dmar: DRHD: handling fault status reg 3
[ 22.223649] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8014b000
[ 22.223649] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223670] dmar: DRHD: handling fault status reg 3
[ 22.223674] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8014d000
[ 22.223674] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223706] dmar: DRHD: handling fault status reg 3
[ 22.223711] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8014f000
[ 22.223711] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223742] dmar: DRHD: handling fault status reg 3
[ 22.223746] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80151000
[ 22.223746] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223753] dmar: DRHD: handling fault status reg 3
[ 22.223758] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80152000
[ 22.223758] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223779] dmar: DRHD: handling fault status reg 3
[ 22.223783] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80153000
[ 22.223783] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223789] dmar: DRHD: handling fault status reg 3
[ 22.223795] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80154000
[ 22.223795] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223816] dmar: DRHD: handling fault status reg 3
[ 22.223820] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80156000
[ 22.223820] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223852] dmar: DRHD: handling fault status reg 3
[ 22.223857] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80158000
[ 22.223857] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223888] dmar: DRHD: handling fault status reg 3
[ 22.223892] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8015a000
[ 22.223892] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223926] dmar: DRHD: handling fault status reg 3
[ 22.223930] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8015c000
[ 22.223930] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223962] dmar: DRHD: handling fault status reg 3
[ 22.223966] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8015f000
[ 22.223966] DMAR:[fault reason 06] PTE Read access is not set
[ 22.223972] dmar: DRHD: handling fault status reg 3
[ 22.223977] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80161000
[ 22.223977] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224019] dmar: DRHD: handling fault status reg 3
[ 22.224027] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80161000
[ 22.224027] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224055] dmar: DRHD: handling fault status reg 3
[ 22.224060] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80163000
[ 22.224060] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224092] dmar: DRHD: handling fault status reg 3
[ 22.224096] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80165000
[ 22.224096] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224102] dmar: DRHD: handling fault status reg 3
[ 22.224106] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80166000
[ 22.224106] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224128] dmar: DRHD: handling fault status reg 3
[ 22.224132] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80168000
[ 22.224132] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224139] dmar: DRHD: handling fault status reg 3
[ 22.224143] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80169000
[ 22.224143] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224164] dmar: DRHD: handling fault status reg 3
[ 22.224169] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8016a000
[ 22.224169] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224175] dmar: DRHD: handling fault status reg 3
[ 22.224179] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8016b000
[ 22.224179] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224201] dmar: DRHD: handling fault status reg 3
[ 22.224205] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8016c000
[ 22.224205] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224238] dmar: DRHD: handling fault status reg 3
[ 22.224242] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8016e000
[ 22.224242] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224274] dmar: DRHD: handling fault status reg 3
[ 22.224279] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80171000
[ 22.224279] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224311] dmar: DRHD: handling fault status reg 3
[ 22.224316] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80173000
[ 22.224316] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224348] dmar: DRHD: handling fault status reg 3
[ 22.224352] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80175000
[ 22.224352] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224384] dmar: DRHD: handling fault status reg 3
[ 22.224389] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80177000
[ 22.224389] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224421] dmar: DRHD: handling fault status reg 3
[ 22.224425] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8017a000
[ 22.224425] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224475] dmar: DRHD: handling fault status reg 3
[ 22.224479] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8017c000
[ 22.224479] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224485] dmar: DRHD: handling fault status reg 3
[ 22.224489] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8017d000
[ 22.224489] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224511] dmar: DRHD: handling fault status reg 3
[ 22.224516] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8017e000
[ 22.224516] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224522] dmar: DRHD: handling fault status reg 3
[ 22.224526] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8017f000
[ 22.224526] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224548] dmar: DRHD: handling fault status reg 3
[ 22.224552] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80180000
[ 22.224552] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224559] dmar: DRHD: handling fault status reg 3
[ 22.224566] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80181000
[ 22.224566] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224584] dmar: DRHD: handling fault status reg 3
[ 22.224589] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80183000
[ 22.224589] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224594] dmar: DRHD: handling fault status reg 3
[ 22.224599] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80184000
[ 22.224599] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224621] dmar: DRHD: handling fault status reg 3
[ 22.224625] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80185000
[ 22.224625] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224631] dmar: DRHD: handling fault status reg 3
[ 22.224635] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80186000
[ 22.224635] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224657] dmar: DRHD: handling fault status reg 3
[ 22.224662] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80187000
[ 22.224662] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224667] dmar: DRHD: handling fault status reg 3
[ 22.224672] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80188000
[ 22.224672] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224694] dmar: DRHD: handling fault status reg 3
[ 22.224698] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80189000
[ 22.224698] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224704] dmar: DRHD: handling fault status reg 3
[ 22.224709] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8018a000
[ 22.224709] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224731] dmar: DRHD: handling fault status reg 3
[ 22.224736] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8018c000
[ 22.224736] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224768] dmar: DRHD: handling fault status reg 3
[ 22.224772] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8018e000
[ 22.224772] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224803] dmar: DRHD: handling fault status reg 3
[ 22.224808] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80190000
[ 22.224808] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224840] dmar: DRHD: handling fault status reg 3
[ 22.224844] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80192000
[ 22.224844] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224850] dmar: DRHD: handling fault status reg 3
[ 22.224855] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80193000
[ 22.224855] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224877] dmar: DRHD: handling fault status reg 3
[ 22.224881] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80195000
[ 22.224881] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224887] dmar: DRHD: handling fault status reg 3
[ 22.224891] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80197000
[ 22.224891] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224931] dmar: DRHD: handling fault status reg 3
[ 22.224938] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80197000
[ 22.224938] DMAR:[fault reason 06] PTE Read access is not set
[ 22.224968] dmar: DRHD: handling fault status reg 3
[ 22.224973] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80199000
[ 22.224973] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225005] dmar: DRHD: handling fault status reg 3
[ 22.225009] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8019b000
[ 22.225009] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225041] dmar: DRHD: handling fault status reg 3
[ 22.225045] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8019e000
[ 22.225045] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225078] dmar: DRHD: handling fault status reg 3
[ 22.225086] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801a0000
[ 22.225086] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225114] dmar: DRHD: handling fault status reg 3
[ 22.225119] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801a2000
[ 22.225119] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225151] dmar: DRHD: handling fault status reg 3
[ 22.225155] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801a4000
[ 22.225155] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225187] dmar: DRHD: handling fault status reg 3
[ 22.225191] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801a7000
[ 22.225191] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225197] dmar: DRHD: handling fault status reg 2
[ 22.225202] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801a9000
[ 22.225202] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225223] dmar: DRHD: handling fault status reg 3
[ 22.225228] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801a9000
[ 22.225228] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225260] dmar: DRHD: handling fault status reg 3
[ 22.225267] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801ab000
[ 22.225267] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225296] dmar: DRHD: handling fault status reg 3
[ 22.225300] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801ad000
[ 22.225300] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225306] dmar: DRHD: handling fault status reg 3
[ 22.225310] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801ae000
[ 22.225310] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225333] dmar: DRHD: handling fault status reg 3
[ 22.225338] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801b0000
[ 22.225338] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225388] dmar: DRHD: handling fault status reg 3
[ 22.225391] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801b2000
[ 22.225391] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225398] dmar: DRHD: handling fault status reg 3
[ 22.225403] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801b3000
[ 22.225403] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225424] dmar: DRHD: handling fault status reg 3
[ 22.225428] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801b4000
[ 22.225428] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225435] dmar: DRHD: handling fault status reg 3
[ 22.225439] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801b5000
[ 22.225439] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225461] dmar: DRHD: handling fault status reg 3
[ 22.225465] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801b6000
[ 22.225465] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225497] dmar: DRHD: handling fault status reg 3
[ 22.225501] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801b9000
[ 22.225501] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225508] dmar: DRHD: handling fault status reg 3
[ 22.225513] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801bb000
[ 22.225513] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225533] dmar: DRHD: handling fault status reg 3
[ 22.225538] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801bb000
[ 22.225538] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225571] dmar: DRHD: handling fault status reg 3
[ 22.225577] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801bd000
[ 22.225577] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225606] dmar: DRHD: handling fault status reg 3
[ 22.225610] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801bf000
[ 22.225610] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225617] dmar: DRHD: handling fault status reg 3
[ 22.225622] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801c0000
[ 22.225622] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225643] dmar: DRHD: handling fault status reg 3
[ 22.225647] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801c2000
[ 22.225647] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225654] dmar: DRHD: handling fault status reg 2
[ 22.225659] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801c4000
[ 22.225659] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225680] dmar: DRHD: handling fault status reg 3
[ 22.225684] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801c4000
[ 22.225684] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225716] dmar: DRHD: handling fault status reg 3
[ 22.225721] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801c6000
[ 22.225721] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225753] dmar: DRHD: handling fault status reg 3
[ 22.225757] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801c8000
[ 22.225757] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225789] dmar: DRHD: handling fault status reg 3
[ 22.225794] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801cb000
[ 22.225794] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225844] dmar: DRHD: handling fault status reg 3
[ 22.225848] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801cd000
[ 22.225848] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225881] dmar: DRHD: handling fault status reg 3
[ 22.225885] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801cf000
[ 22.225885] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225918] dmar: DRHD: handling fault status reg 3
[ 22.225922] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801d1000
[ 22.225922] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225954] dmar: DRHD: handling fault status reg 3
[ 22.225958] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801d4000
[ 22.225958] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225964] dmar: DRHD: handling fault status reg 3
[ 22.225969] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801d5000
[ 22.225969] DMAR:[fault reason 06] PTE Read access is not set
[ 22.225991] dmar: DRHD: handling fault status reg 3
[ 22.225995] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801d6000
[ 22.225995] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226027] dmar: DRHD: handling fault status reg 3
[ 22.226031] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801d8000
[ 22.226031] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226063] dmar: DRHD: handling fault status reg 3
[ 22.226068] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801da000
[ 22.226068] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226100] dmar: DRHD: handling fault status reg 3
[ 22.226104] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801dd000
[ 22.226104] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226136] dmar: DRHD: handling fault status reg 3
[ 22.226141] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801df000
[ 22.226141] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226172] dmar: DRHD: handling fault status reg 3
[ 22.226176] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801e1000
[ 22.226176] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226183] dmar: DRHD: handling fault status reg 3
[ 22.226188] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801e2000
[ 22.226188] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226209] dmar: DRHD: handling fault status reg 3
[ 22.226214] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801e3000
[ 22.226214] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226246] dmar: DRHD: handling fault status reg 3
[ 22.226251] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801e6000
[ 22.226251] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226300] dmar: DRHD: handling fault status reg 3
[ 22.226304] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801e8000
[ 22.226304] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226310] dmar: DRHD: handling fault status reg 3
[ 22.226316] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801e9000
[ 22.226316] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226337] dmar: DRHD: handling fault status reg 3
[ 22.226342] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801ea000
[ 22.226342] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226373] dmar: DRHD: handling fault status reg 3
[ 22.226378] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801ec000
[ 22.226378] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226410] dmar: DRHD: handling fault status reg 3
[ 22.226414] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801ef000
[ 22.226414] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226420] dmar: DRHD: handling fault status reg 3
[ 22.226425] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801f0000
[ 22.226425] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226446] dmar: DRHD: handling fault status reg 3
[ 22.226450] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801f1000
[ 22.226450] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226457] dmar: DRHD: handling fault status reg 3
[ 22.226462] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801f2000
[ 22.226462] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226483] dmar: DRHD: handling fault status reg 3
[ 22.226487] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801f3000
[ 22.226487] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226493] dmar: DRHD: handling fault status reg 3
[ 22.226498] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801f4000
[ 22.226498] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226519] dmar: DRHD: handling fault status reg 3
[ 22.226524] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801f5000
[ 22.226524] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226530] dmar: DRHD: handling fault status reg 3
[ 22.226535] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801f6000
[ 22.226535] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226556] dmar: DRHD: handling fault status reg 3
[ 22.226560] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801f8000
[ 22.226560] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226566] dmar: DRHD: handling fault status reg 3
[ 22.226571] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801f9000
[ 22.226571] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226593] dmar: DRHD: handling fault status reg 3
[ 22.226597] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801fa000
[ 22.226597] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226629] dmar: DRHD: handling fault status reg 3
[ 22.226634] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801fc000
[ 22.226634] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226666] dmar: DRHD: handling fault status reg 3
[ 22.226670] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801fe000
[ 22.226670] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226676] dmar: DRHD: handling fault status reg 3
[ 22.226681] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 801ff000
[ 22.226681] DMAR:[fault reason 06] PTE Read access is not set
[ 22.226701] dmar: DRHD: handling fault status reg 3
[ 22.226705] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80201000
[ 22.226705] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.226712] dmar: DRHD: handling fault status reg 3
[ 22.226717] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80202000
[ 22.226717] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.226756] dmar: DRHD: handling fault status reg 3
[ 22.226760] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80203000
[ 22.226760] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.226767] dmar: DRHD: handling fault status reg 3
[ 22.226772] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80204000
[ 22.226772] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.226792] dmar: DRHD: handling fault status reg 3
[ 22.226797] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80205000
[ 22.226797] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.226804] dmar: DRHD: handling fault status reg 3
[ 22.226808] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80206000
[ 22.226808] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.226829] dmar: DRHD: handling fault status reg 3
[ 22.226833] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80207000
[ 22.226833] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.226840] dmar: DRHD: handling fault status reg 3
[ 22.226845] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80208000
[ 22.226845] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.226865] dmar: DRHD: handling fault status reg 3
[ 22.226870] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8020a000
[ 22.226870] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.226876] dmar: DRHD: handling fault status reg 3
[ 22.226881] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8020b000
[ 22.226881] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.226902] dmar: DRHD: handling fault status reg 3
[ 22.226906] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8020c000
[ 22.226906] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.226913] dmar: DRHD: handling fault status reg 3
[ 22.226918] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8020d000
[ 22.226918] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.226940] dmar: DRHD: handling fault status reg 3
[ 22.226944] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8020e000
[ 22.226944] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.226976] dmar: DRHD: handling fault status reg 3
[ 22.226981] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80210000
[ 22.226981] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227011] dmar: DRHD: handling fault status reg 3
[ 22.227016] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80213000
[ 22.227016] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227022] dmar: DRHD: handling fault status reg 3
[ 22.227027] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80214000
[ 22.227027] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227048] dmar: DRHD: handling fault status reg 3
[ 22.227052] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80215000
[ 22.227052] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227059] dmar: DRHD: handling fault status reg 3
[ 22.227064] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80216000
[ 22.227064] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227086] dmar: DRHD: handling fault status reg 3
[ 22.227090] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80217000
[ 22.227090] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227121] dmar: DRHD: handling fault status reg 3
[ 22.227126] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80219000
[ 22.227126] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227158] dmar: DRHD: handling fault status reg 3
[ 22.227162] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8021c000
[ 22.227162] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227169] dmar: DRHD: handling fault status reg 3
[ 22.227174] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8021d000
[ 22.227174] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227214] dmar: DRHD: handling fault status reg 3
[ 22.227217] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8021e000
[ 22.227217] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227249] dmar: DRHD: handling fault status reg 3
[ 22.227254] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80220000
[ 22.227254] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227285] dmar: DRHD: handling fault status reg 3
[ 22.227289] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80222000
[ 22.227289] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227296] dmar: DRHD: handling fault status reg 3
[ 22.227301] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80223000
[ 22.227301] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227322] dmar: DRHD: handling fault status reg 3
[ 22.227326] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80225000
[ 22.227326] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227333] dmar: DRHD: handling fault status reg 3
[ 22.227338] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80226000
[ 22.227338] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227359] dmar: DRHD: handling fault status reg 3
[ 22.227363] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80227000
[ 22.227363] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227369] dmar: DRHD: handling fault status reg 3
[ 22.227374] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80228000
[ 22.227374] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227395] dmar: DRHD: handling fault status reg 3
[ 22.227399] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80229000
[ 22.227399] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227406] dmar: DRHD: handling fault status reg 3
[ 22.227410] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8022a000
[ 22.227410] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227431] dmar: DRHD: handling fault status reg 3
[ 22.227436] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8022b000
[ 22.227436] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227442] dmar: DRHD: handling fault status reg 3
[ 22.227447] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8022c000
[ 22.227447] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227468] dmar: DRHD: handling fault status reg 3
[ 22.227473] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8022e000
[ 22.227473] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227506] dmar: DRHD: handling fault status reg 3
[ 22.227510] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80230000
[ 22.227510] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227541] dmar: DRHD: handling fault status reg 3
[ 22.227545] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80232000
[ 22.227545] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227578] dmar: DRHD: handling fault status reg 3
[ 22.227582] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80234000
[ 22.227582] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227614] dmar: DRHD: handling fault status reg 3
[ 22.227619] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80237000
[ 22.227619] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227625] dmar: DRHD: handling fault status reg 3
[ 22.227630] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80238000
[ 22.227630] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227669] dmar: DRHD: handling fault status reg 3
[ 22.227673] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80239000
[ 22.227673] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227706] dmar: DRHD: handling fault status reg 3
[ 22.227710] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8023b000
[ 22.227710] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227743] dmar: DRHD: handling fault status reg 3
[ 22.227747] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8023d000
[ 22.227747] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227779] dmar: DRHD: handling fault status reg 3
[ 22.227784] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80240000
[ 22.227784] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227815] dmar: DRHD: handling fault status reg 3
[ 22.227819] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80242000
[ 22.227819] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227826] dmar: DRHD: handling fault status reg 3
[ 22.227830] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80243000
[ 22.227830] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227852] dmar: DRHD: handling fault status reg 3
[ 22.227856] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80244000
[ 22.227856] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227888] dmar: DRHD: handling fault status reg 3
[ 22.227893] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80246000
[ 22.227893] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227924] dmar: DRHD: handling fault status reg 3
[ 22.227928] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80249000
[ 22.227928] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227935] dmar: DRHD: handling fault status reg 3
[ 22.227940] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8024a000
[ 22.227940] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227961] dmar: DRHD: handling fault status reg 3
[ 22.227966] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8024b000
[ 22.227966] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227972] dmar: DRHD: handling fault status reg 2
[ 22.227977] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8024c000
[ 22.227977] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.227997] dmar: DRHD: handling fault status reg 3
[ 22.228001] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8024d000
[ 22.228001] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228037] dmar: DRHD: handling fault status reg 3
[ 22.228042] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8024f000
[ 22.228042] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228073] dmar: DRHD: handling fault status reg 3
[ 22.228078] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80252000
[ 22.228078] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228128] dmar: DRHD: handling fault status reg 3
[ 22.228132] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80254000
[ 22.228132] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228164] dmar: DRHD: handling fault status reg 3
[ 22.228169] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80256000
[ 22.228169] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228201] dmar: DRHD: handling fault status reg 3
[ 22.228205] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80258000
[ 22.228205] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228237] dmar: DRHD: handling fault status reg 3
[ 22.228241] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8025b000
[ 22.228241] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228248] dmar: DRHD: handling fault status reg 3
[ 22.228252] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8025c000
[ 22.228252] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228273] dmar: DRHD: handling fault status reg 3
[ 22.228278] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8025d000
[ 22.228278] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228284] dmar: DRHD: handling fault status reg 3
[ 22.228289] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8025e000
[ 22.228289] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228310] dmar: DRHD: handling fault status reg 3
[ 22.228315] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8025f000
[ 22.228315] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228321] dmar: DRHD: handling fault status reg 3
[ 22.228325] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80260000
[ 22.228325] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228347] dmar: DRHD: handling fault status reg 3
[ 22.228352] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80261000
[ 22.228352] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228383] dmar: DRHD: handling fault status reg 3
[ 22.228387] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80264000
[ 22.228387] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228395] dmar: DRHD: handling fault status reg 3
[ 22.228401] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80265000
[ 22.228401] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228419] dmar: DRHD: handling fault status reg 3
[ 22.228424] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80266000
[ 22.228424] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228430] dmar: DRHD: handling fault status reg 3
[ 22.228434] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80267000
[ 22.228434] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228456] dmar: DRHD: handling fault status reg 3
[ 22.228460] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80268000
[ 22.228460] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228467] dmar: DRHD: handling fault status reg 3
[ 22.228472] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80269000
[ 22.228472] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228492] dmar: DRHD: handling fault status reg 3
[ 22.228497] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8026a000
[ 22.228497] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228503] dmar: DRHD: handling fault status reg 3
[ 22.228507] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8026b000
[ 22.228507] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228529] dmar: DRHD: handling fault status reg 3
[ 22.228534] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8026d000
[ 22.228534] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228540] dmar: DRHD: handling fault status reg 3
[ 22.228546] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8026e000
[ 22.228546] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228584] dmar: DRHD: handling fault status reg 3
[ 22.228588] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8026f000
[ 22.228588] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228594] dmar: DRHD: handling fault status reg 3
[ 22.228598] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80270000
[ 22.228598] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228620] dmar: DRHD: handling fault status reg 3
[ 22.228625] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80271000
[ 22.228625] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228630] dmar: DRHD: handling fault status reg 3
[ 22.228635] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80272000
[ 22.228635] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228657] dmar: DRHD: handling fault status reg 3
[ 22.228661] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80273000
[ 22.228661] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228667] dmar: DRHD: handling fault status reg 3
[ 22.228671] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80274000
[ 22.228671] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228693] dmar: DRHD: handling fault status reg 3
[ 22.228698] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80276000
[ 22.228698] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228730] dmar: DRHD: handling fault status reg 3
[ 22.228738] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80278000
[ 22.228738] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228766] dmar: DRHD: handling fault status reg 3
[ 22.228771] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8027a000
[ 22.228771] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228777] dmar: DRHD: handling fault status reg 3
[ 22.228781] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8027b000
[ 22.228781] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228804] dmar: DRHD: handling fault status reg 3
[ 22.228808] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8027c000
[ 22.228808] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228839] dmar: DRHD: handling fault status reg 3
[ 22.228844] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8027f000
[ 22.228844] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228876] dmar: DRHD: handling fault status reg 3
[ 22.228881] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80281000
[ 22.228881] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228912] dmar: DRHD: handling fault status reg 3
[ 22.228920] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80283000
[ 22.228920] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228950] dmar: DRHD: handling fault status reg 3
[ 22.228954] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80285000
[ 22.228954] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.228986] dmar: DRHD: handling fault status reg 3
[ 22.228991] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80288000
[ 22.228991] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229041] dmar: DRHD: handling fault status reg 3
[ 22.229045] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8028a000
[ 22.229045] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229077] dmar: DRHD: handling fault status reg 3
[ 22.229086] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8028c000
[ 22.229086] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229113] dmar: DRHD: handling fault status reg 3
[ 22.229117] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8028e000
[ 22.229117] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229123] dmar: DRHD: handling fault status reg 3
[ 22.229127] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8028f000
[ 22.229127] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229150] dmar: DRHD: handling fault status reg 3
[ 22.229154] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80291000
[ 22.229154] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229160] dmar: DRHD: handling fault status reg 3
[ 22.229165] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80292000
[ 22.229165] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229187] dmar: DRHD: handling fault status reg 3
[ 22.229192] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80293000
[ 22.229192] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229223] dmar: DRHD: handling fault status reg 3
[ 22.229227] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80295000
[ 22.229227] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229259] dmar: DRHD: handling fault status reg 3
[ 22.229264] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80297000
[ 22.229264] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229296] dmar: DRHD: handling fault status reg 3
[ 22.229300] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8029a000
[ 22.229300] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229307] dmar: DRHD: handling fault status reg 3
[ 22.229312] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8029b000
[ 22.229312] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229332] dmar: DRHD: handling fault status reg 3
[ 22.229336] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8029c000
[ 22.229336] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229343] dmar: DRHD: handling fault status reg 3
[ 22.229347] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8029e000
[ 22.229347] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229369] dmar: DRHD: handling fault status reg 3
[ 22.229374] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8029e000
[ 22.229374] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229406] dmar: DRHD: handling fault status reg 3
[ 22.229411] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802a0000
[ 22.229411] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229443] dmar: DRHD: handling fault status reg 3
[ 22.229449] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802a3000
[ 22.229449] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229497] dmar: DRHD: handling fault status reg 3
[ 22.229502] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802a5000
[ 22.229502] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229533] dmar: DRHD: handling fault status reg 3
[ 22.229537] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802a7000
[ 22.229537] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229544] dmar: DRHD: handling fault status reg 3
[ 22.229549] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802a9000
[ 22.229549] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229570] dmar: DRHD: handling fault status reg 3
[ 22.229574] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802a9000
[ 22.229574] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229581] dmar: DRHD: handling fault status reg 2
[ 22.229586] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802aa000
[ 22.229586] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229606] dmar: DRHD: handling fault status reg 3
[ 22.229611] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802ac000
[ 22.229611] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229643] dmar: DRHD: handling fault status reg 3
[ 22.229648] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802ae000
[ 22.229648] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229679] dmar: DRHD: handling fault status reg 3
[ 22.229684] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802b0000
[ 22.229684] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229717] dmar: DRHD: handling fault status reg 3
[ 22.229721] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802b2000
[ 22.229721] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229752] dmar: DRHD: handling fault status reg 3
[ 22.229756] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802b5000
[ 22.229756] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229763] dmar: DRHD: handling fault status reg 3
[ 22.229767] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802b6000
[ 22.229767] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229788] dmar: DRHD: handling fault status reg 3
[ 22.229792] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802b7000
[ 22.229792] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229799] dmar: DRHD: handling fault status reg 3
[ 22.229804] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802b8000
[ 22.229804] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229826] dmar: DRHD: handling fault status reg 3
[ 22.229830] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802b9000
[ 22.229830] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229862] dmar: DRHD: handling fault status reg 3
[ 22.229867] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802bb000
[ 22.229867] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229898] dmar: DRHD: handling fault status reg 3
[ 22.229902] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802be000
[ 22.229902] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229908] dmar: DRHD: handling fault status reg 3
[ 22.229913] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802be000
[ 22.229913] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229954] dmar: DRHD: handling fault status reg 3
[ 22.229958] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802c0000
[ 22.229958] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.229990] dmar: DRHD: handling fault status reg 3
[ 22.229995] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802c2000
[ 22.229995] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230026] dmar: DRHD: handling fault status reg 3
[ 22.230030] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802c4000
[ 22.230030] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230063] dmar: DRHD: handling fault status reg 3
[ 22.230068] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802c7000
[ 22.230068] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230099] dmar: DRHD: handling fault status reg 3
[ 22.230103] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802c9000
[ 22.230103] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230110] dmar: DRHD: handling fault status reg 3
[ 22.230115] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802ca000
[ 22.230115] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230135] dmar: DRHD: handling fault status reg 3
[ 22.230139] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802cb000
[ 22.230139] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230146] dmar: DRHD: handling fault status reg 3
[ 22.230151] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802cc000
[ 22.230151] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230172] dmar: DRHD: handling fault status reg 3
[ 22.230177] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802cd000
[ 22.230177] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230209] dmar: DRHD: handling fault status reg 3
[ 22.230214] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802d0000
[ 22.230214] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230245] dmar: DRHD: handling fault status reg 3
[ 22.230249] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802d2000
[ 22.230249] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230255] dmar: DRHD: handling fault status reg 3
[ 22.230260] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802d4000
[ 22.230260] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230282] dmar: DRHD: handling fault status reg 3
[ 22.230286] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802d4000
[ 22.230286] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230318] dmar: DRHD: handling fault status reg 3
[ 22.230323] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802d6000
[ 22.230323] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230354] dmar: DRHD: handling fault status reg 3
[ 22.230358] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802d9000
[ 22.230358] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230365] dmar: DRHD: handling fault status reg 3
[ 22.230369] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802da000
[ 22.230369] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230409] dmar: DRHD: handling fault status reg 3
[ 22.230413] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802db000
[ 22.230413] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230420] dmar: DRHD: handling fault status reg 3
[ 22.230424] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802dc000
[ 22.230424] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230446] dmar: DRHD: handling fault status reg 3
[ 22.230450] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802dd000
[ 22.230450] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230482] dmar: DRHD: handling fault status reg 3
[ 22.230487] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802df000
[ 22.230487] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230493] dmar: DRHD: handling fault status reg 2
[ 22.230497] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802e0000
[ 22.230497] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230519] dmar: DRHD: handling fault status reg 3
[ 22.230524] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802e2000
[ 22.230524] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230555] dmar: DRHD: handling fault status reg 3
[ 22.230559] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802e4000
[ 22.230559] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230566] dmar: DRHD: handling fault status reg 3
[ 22.230570] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802e5000
[ 22.230570] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230591] dmar: DRHD: handling fault status reg 3
[ 22.230595] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802e6000
[ 22.230595] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230602] dmar: DRHD: handling fault status reg 3
[ 22.230607] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802e7000
[ 22.230607] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230629] dmar: DRHD: handling fault status reg 3
[ 22.230633] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802e8000
[ 22.230633] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230665] dmar: DRHD: handling fault status reg 3
[ 22.230669] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802eb000
[ 22.230669] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230675] dmar: DRHD: handling fault status reg 3
[ 22.230679] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802ec000
[ 22.230679] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230702] dmar: DRHD: handling fault status reg 3
[ 22.230706] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802ed000
[ 22.230706] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230738] dmar: DRHD: handling fault status reg 3
[ 22.230742] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802ef000
[ 22.230742] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230775] dmar: DRHD: handling fault status reg 3
[ 22.230779] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802f1000
[ 22.230779] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230811] dmar: DRHD: handling fault status reg 3
[ 22.230816] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802f4000
[ 22.230816] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230866] dmar: DRHD: handling fault status reg 3
[ 22.230870] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802f6000
[ 22.230870] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230903] dmar: DRHD: handling fault status reg 3
[ 22.230906] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802f8000
[ 22.230906] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230939] dmar: DRHD: handling fault status reg 3
[ 22.230944] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802fa000
[ 22.230944] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230975] dmar: DRHD: handling fault status reg 3
[ 22.230979] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802fd000
[ 22.230979] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.230985] dmar: DRHD: handling fault status reg 3
[ 22.230990] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802fd000
[ 22.230990] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231011] dmar: DRHD: handling fault status reg 3
[ 22.231016] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 802ff000
[ 22.231016] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231023] dmar: DRHD: handling fault status reg 3
[ 22.231027] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80300000
[ 22.231027] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231048] dmar: DRHD: handling fault status reg 3
[ 22.231052] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80301000
[ 22.231052] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231059] dmar: DRHD: handling fault status reg 3
[ 22.231063] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80302000
[ 22.231063] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231084] dmar: DRHD: handling fault status reg 3
[ 22.231088] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80303000
[ 22.231088] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231095] dmar: DRHD: handling fault status reg 3
[ 22.231100] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80304000
[ 22.231100] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231122] dmar: DRHD: handling fault status reg 3
[ 22.231126] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80306000
[ 22.231126] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231158] dmar: DRHD: handling fault status reg 3
[ 22.231163] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80308000
[ 22.231163] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231194] dmar: DRHD: handling fault status reg 3
[ 22.231198] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8030a000
[ 22.231198] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231205] dmar: DRHD: handling fault status reg 3
[ 22.231209] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8030b000
[ 22.231209] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231231] dmar: DRHD: handling fault status reg 3
[ 22.231235] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8030c000
[ 22.231235] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231268] dmar: DRHD: handling fault status reg 3
[ 22.231273] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8030f000
[ 22.231273] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231322] dmar: DRHD: handling fault status reg 3
[ 22.231326] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80311000
[ 22.231326] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231333] dmar: DRHD: handling fault status reg 3
[ 22.231337] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80312000
[ 22.231337] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231359] dmar: DRHD: handling fault status reg 3
[ 22.231363] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80313000
[ 22.231363] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231369] dmar: DRHD: handling fault status reg 3
[ 22.231373] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80314000
[ 22.231373] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231395] dmar: DRHD: handling fault status reg 3
[ 22.231399] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80315000
[ 22.231399] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231406] dmar: DRHD: handling fault status reg 3
[ 22.231410] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80316000
[ 22.231410] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231432] dmar: DRHD: handling fault status reg 3
[ 22.231436] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80318000
[ 22.231436] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231442] dmar: DRHD: handling fault status reg 3
[ 22.231447] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80319000
[ 22.231447] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231468] dmar: DRHD: handling fault status reg 3
[ 22.231472] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8031a000
[ 22.231472] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231478] dmar: DRHD: handling fault status reg 3
[ 22.231483] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8031b000
[ 22.231483] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231505] dmar: DRHD: handling fault status reg 3
[ 22.231509] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8031c000
[ 22.231509] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231541] dmar: DRHD: handling fault status reg 3
[ 22.231546] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8031e000
[ 22.231546] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231578] dmar: DRHD: handling fault status reg 3
[ 22.231582] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80321000
[ 22.231582] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231615] dmar: DRHD: handling fault status reg 3
[ 22.231619] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80323000
[ 22.231619] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231651] dmar: DRHD: handling fault status reg 3
[ 22.231656] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80325000
[ 22.231656] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231688] dmar: DRHD: handling fault status reg 3
[ 22.231692] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80327000
[ 22.231692] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231723] dmar: DRHD: handling fault status reg 3
[ 22.231727] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8032a000
[ 22.231727] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231734] dmar: DRHD: handling fault status reg 3
[ 22.231739] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8032b000
[ 22.231739] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231778] dmar: DRHD: handling fault status reg 3
[ 22.231782] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8032c000
[ 22.231782] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231789] dmar: DRHD: handling fault status reg 3
[ 22.231793] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8032d000
[ 22.231793] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231815] dmar: DRHD: handling fault status reg 3
[ 22.231819] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8032e000
[ 22.231819] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231852] dmar: DRHD: handling fault status reg 3
[ 22.231856] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80330000
[ 22.231856] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231887] dmar: DRHD: handling fault status reg 3
[ 22.231891] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80333000
[ 22.231891] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231898] dmar: DRHD: handling fault status reg 3
[ 22.231903] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80334000
[ 22.231903] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231924] dmar: DRHD: handling fault status reg 3
[ 22.231928] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80335000
[ 22.231928] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231935] dmar: DRHD: handling fault status reg 3
[ 22.231940] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80336000
[ 22.231940] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231960] dmar: DRHD: handling fault status reg 3
[ 22.231964] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80337000
[ 22.231964] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231971] dmar: DRHD: handling fault status reg 3
[ 22.231976] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80338000
[ 22.231976] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.231998] dmar: DRHD: handling fault status reg 3
[ 22.232002] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80339000
[ 22.232002] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232036] dmar: DRHD: handling fault status reg 3
[ 22.232040] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8033c000
[ 22.232040] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232073] dmar: DRHD: handling fault status reg 3
[ 22.232078] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8033e000
[ 22.232078] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232109] dmar: DRHD: handling fault status reg 3
[ 22.232113] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80340000
[ 22.232113] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232119] dmar: DRHD: handling fault status reg 3
[ 22.232123] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80341000
[ 22.232123] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232145] dmar: DRHD: handling fault status reg 3
[ 22.232150] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80342000
[ 22.232150] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232156] dmar: DRHD: handling fault status reg 3
[ 22.232160] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80343000
[ 22.232160] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232182] dmar: DRHD: handling fault status reg 3
[ 22.232187] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80345000
[ 22.232187] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232237] dmar: DRHD: handling fault status reg 3
[ 22.232242] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80347000
[ 22.232242] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232275] dmar: DRHD: handling fault status reg 3
[ 22.232284] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80349000
[ 22.232284] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232310] dmar: DRHD: handling fault status reg 3
[ 22.232315] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8034b000
[ 22.232315] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232346] dmar: DRHD: handling fault status reg 3
[ 22.232351] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8034e000
[ 22.232351] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232357] dmar: DRHD: handling fault status reg 3
[ 22.232362] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8034f000
[ 22.232362] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232383] dmar: DRHD: handling fault status reg 3
[ 22.232388] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80350000
[ 22.232388] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232420] dmar: DRHD: handling fault status reg 3
[ 22.232425] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80352000
[ 22.232425] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232456] dmar: DRHD: handling fault status reg 3
[ 22.232462] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80354000
[ 22.232462] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232492] dmar: DRHD: handling fault status reg 3
[ 22.232496] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80357000
[ 22.232496] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232503] dmar: DRHD: handling fault status reg 3
[ 22.232507] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80358000
[ 22.232507] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232529] dmar: DRHD: handling fault status reg 3
[ 22.232534] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80359000
[ 22.232534] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232565] dmar: DRHD: handling fault status reg 3
[ 22.232570] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8035b000
[ 22.232570] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232576] dmar: DRHD: handling fault status reg 2
[ 22.232580] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8035c000
[ 22.232580] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232602] dmar: DRHD: handling fault status reg 3
[ 22.232610] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8035d000
[ 22.232610] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232639] dmar: DRHD: handling fault status reg 3
[ 22.232643] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80360000
[ 22.232643] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232693] dmar: DRHD: handling fault status reg 3
[ 22.232697] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80362000
[ 22.232697] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232704] dmar: DRHD: handling fault status reg 3
[ 22.232708] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80363000
[ 22.232708] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232729] dmar: DRHD: handling fault status reg 3
[ 22.232734] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80364000
[ 22.232734] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232740] dmar: DRHD: handling fault status reg 3
[ 22.232745] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80365000
[ 22.232745] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232767] dmar: DRHD: handling fault status reg 3
[ 22.232775] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80366000
[ 22.232775] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232803] dmar: DRHD: handling fault status reg 3
[ 22.232807] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80369000
[ 22.232807] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232840] dmar: DRHD: handling fault status reg 3
[ 22.232844] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8036b000
[ 22.232844] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232876] dmar: DRHD: handling fault status reg 3
[ 22.232881] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8036d000
[ 22.232881] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232912] dmar: DRHD: handling fault status reg 3
[ 22.232917] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8036f000
[ 22.232917] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232949] dmar: DRHD: handling fault status reg 3
[ 22.232954] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80372000
[ 22.232954] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.232986] dmar: DRHD: handling fault status reg 3
[ 22.232990] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80374000
[ 22.232990] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233022] dmar: DRHD: handling fault status reg 3
[ 22.233026] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80376000
[ 22.233026] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233059] dmar: DRHD: handling fault status reg 3
[ 22.233063] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80378000
[ 22.233063] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233069] dmar: DRHD: handling fault status reg 3
[ 22.233074] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80379000
[ 22.233074] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233095] dmar: DRHD: handling fault status reg 3
[ 22.233099] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8037b000
[ 22.233099] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233150] dmar: DRHD: handling fault status reg 3
[ 22.233154] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8037d000
[ 22.233154] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233160] dmar: DRHD: handling fault status reg 3
[ 22.233164] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8037e000
[ 22.233164] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233186] dmar: DRHD: handling fault status reg 3
[ 22.233191] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8037f000
[ 22.233191] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233223] dmar: DRHD: handling fault status reg 3
[ 22.233227] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80381000
[ 22.233227] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233233] dmar: DRHD: handling fault status reg 2
[ 22.233238] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80382000
[ 22.233238] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233260] dmar: DRHD: handling fault status reg 3
[ 22.233263] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80384000
[ 22.233263] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233296] dmar: DRHD: handling fault status reg 3
[ 22.233300] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80386000
[ 22.233300] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233306] dmar: DRHD: handling fault status reg 3
[ 22.233310] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80387000
[ 22.233310] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233333] dmar: DRHD: handling fault status reg 3
[ 22.233338] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80388000
[ 22.233338] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233368] dmar: DRHD: handling fault status reg 3
[ 22.233373] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8038a000
[ 22.233373] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233379] dmar: DRHD: handling fault status reg 3
[ 22.233384] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8038b000
[ 22.233384] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233406] dmar: DRHD: handling fault status reg 3
[ 22.233410] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8038d000
[ 22.233410] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233442] dmar: DRHD: handling fault status reg 3
[ 22.233446] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8038f000
[ 22.233446] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233452] dmar: DRHD: handling fault status reg 2
[ 22.233456] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80391000
[ 22.233456] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233479] dmar: DRHD: handling fault status reg 3
[ 22.233484] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80391000
[ 22.233484] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233515] dmar: DRHD: handling fault status reg 3
[ 22.233520] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80393000
[ 22.233520] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233552] dmar: DRHD: handling fault status reg 3
[ 22.233557] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80396000
[ 22.233557] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233606] dmar: DRHD: handling fault status reg 3
[ 22.233610] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80398000
[ 22.233610] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233617] dmar: DRHD: handling fault status reg 2
[ 22.233622] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 80399000
[ 22.233622] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233642] dmar: DRHD: handling fault status reg 3
[ 22.233647] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8039a000
[ 22.233647] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233653] dmar: DRHD: handling fault status reg 3
[ 22.233657] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8039b000
[ 22.233657] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233679] dmar: DRHD: handling fault status reg 3
[ 22.233683] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8039c000
[ 22.233683] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233690] dmar: DRHD: handling fault status reg 3
[ 22.233694] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8039d000
[ 22.233694] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233716] dmar: DRHD: handling fault status reg 3
[ 22.233720] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 8039f000
[ 22.233720] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233752] dmar: DRHD: handling fault status reg 3
[ 22.233757] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803a1000
[ 22.233757] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233789] dmar: DRHD: handling fault status reg 3
[ 22.233793] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803a3000
[ 22.233793] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233825] dmar: DRHD: handling fault status reg 3
[ 22.233830] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803a5000
[ 22.233830] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233861] dmar: DRHD: handling fault status reg 3
[ 22.233865] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803a8000
[ 22.233865] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233872] dmar: DRHD: handling fault status reg 3
[ 22.233877] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803a9000
[ 22.233877] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233898] dmar: DRHD: handling fault status reg 3
[ 22.233902] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803aa000
[ 22.233902] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233934] dmar: DRHD: handling fault status reg 3
[ 22.233940] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803ac000
[ 22.233940] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233971] dmar: DRHD: handling fault status reg 3
[ 22.233975] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803ae000
[ 22.233975] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.233981] dmar: DRHD: handling fault status reg 3
[ 22.233986] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803b0000
[ 22.233986] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234008] dmar: DRHD: handling fault status reg 3
[ 22.234012] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803b1000
[ 22.234012] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234063] dmar: DRHD: handling fault status reg 3
[ 22.234068] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803b3000
[ 22.234068] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234100] dmar: DRHD: handling fault status reg 3
[ 22.234104] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803b5000
[ 22.234104] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234135] dmar: DRHD: handling fault status reg 3
[ 22.234140] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803b7000
[ 22.234140] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234171] dmar: DRHD: handling fault status reg 3
[ 22.234175] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803ba000
[ 22.234175] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234182] dmar: DRHD: handling fault status reg 3
[ 22.234187] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803bb000
[ 22.234187] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234208] dmar: DRHD: handling fault status reg 3
[ 22.234212] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803bc000
[ 22.234212] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234219] dmar: DRHD: handling fault status reg 3
[ 22.234223] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803bd000
[ 22.234223] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234244] dmar: DRHD: handling fault status reg 3
[ 22.234248] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803be000
[ 22.234248] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234255] dmar: DRHD: handling fault status reg 3
[ 22.234260] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803bf000
[ 22.234260] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234281] dmar: DRHD: handling fault status reg 3
[ 22.234285] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803c0000
[ 22.234285] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234292] dmar: DRHD: handling fault status reg 3
[ 22.234296] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803c1000
[ 22.234296] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234317] dmar: DRHD: handling fault status reg 3
[ 22.234322] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803c3000
[ 22.234322] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234329] dmar: DRHD: handling fault status reg 3
[ 22.234333] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803c4000
[ 22.234333] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234355] dmar: DRHD: handling fault status reg 3
[ 22.234359] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803c5000
[ 22.234359] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234391] dmar: DRHD: handling fault status reg 3
[ 22.234395] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803c7000
[ 22.234395] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234427] dmar: DRHD: handling fault status reg 3
[ 22.234431] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803c9000
[ 22.234431] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.234438] dmar: DRHD: handling fault status reg 3
[ 22.234443] dmar: DMAR:[DMA Read] Request device [01:00.0] fault addr 803ca000
[ 22.234443] DMAR:[fault reason 07] Next page table ptr is invalid
[ 22.236419] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 22.236479] radeon 0000:01:00.0: WB enabled
[ 22.236483] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000008000c00 and cpu addr 0xffff88002f436c00
[ 22.236485] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000008000c0c and cpu addr 0xffff88002f436c0c
[ 22.270041] [drm] ring test on 0 succeeded in 1 usecs
[ 22.270099] [drm] ring test on 3 succeeded in 1 usecs
[ 22.272156] [drm] ib test on ring 0 succeeded in 0 usecs
[ 22.272170] [drm] ib test on ring 3 succeeded in 0 usecs
[ 22.272705] [drm] radeon atom DIG backlight initialized
[ 22.272707] [drm] Radeon Display Connectors
[ 22.272708] [drm] Connector 0:
[ 22.272710] [drm] LVDS-1
[ 22.272711] [drm] Encoders:
[ 22.272712] [drm] LCD1: INTERNAL_KLDSCP_LVTMA
[ 22.272713] [drm] Connector 1:
[ 22.272714] [drm] VGA-1
[ 22.272716] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[ 22.272717] [drm] Encoders:
[ 22.272718] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 22.272719] [drm] Connector 2:
[ 22.272720] [drm] DVI-D-1
[ 22.272721] [drm] HPD1
[ 22.272723] [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c
[ 22.272724] [drm] Encoders:
[ 22.272725] [drm] DFP1: INTERNAL_UNIPHY
[ 22.272758] [drm] radeon: power management initialized
[ 23.130338] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUG disabled
[ 23.130342] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEBUGFS enabled
[ 23.130344] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TRACING enabled
[ 23.130346] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_DEVICE_TESTMODE enabled
[ 23.130347] iwlwifi 0000:03:00.0: CONFIG_IWLWIFI_P2P disabled
[ 23.130350] iwlwifi 0000:03:00.0: Detected Intel(R) Ultimate N WiFi Link 5300 AGN, REV=0x24
[ 23.130434] iwlwifi 0000:03:00.0: L1 Disabled; Enabling L0S
[ 23.130809] iwlwifi 0000:03:00.0: RF_KILL bit toggled to disable radio.
[ 23.148559] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain
[ 23.231949] [drm] fb mappable at 0x80142000
[ 23.231952] [drm] vram apper at 0x80000000
[ 23.231953] [drm] size 5324800
[ 23.231954] [drm] fb depth is 24
[ 23.231955] [drm] pitch is 5888
[ 23.232093] fbcon: radeondrmfb (fb0) is primary device
[ 23.496217] Console: switching to colour frame buffer device 180x56
[ 23.499083] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[ 23.499085] radeon 0000:01:00.0: registered panic notifier
[ 23.499100] [drm] Initialized radeon 2.28.0 20080528 for 0000:01:00.0 on minor 0
[ 23.685147] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[ 23.942588] init: udev-fallback-graphics main process (999) terminated with status 1
[ 24.211397] init: failsafe main process (901) killed by TERM signal
[ 24.770021] type=1400 audit(1358870860.370:8): apparmor="STATUS" operation="profile_load" name="/usr/lib/cups/backend/cups-pdf" pid=1020 comm="apparmor_parser"
[ 24.770411] type=1400 audit(1358870860.370:9): apparmor="STATUS" operation="profile_load" name="/usr/sbin/cupsd" pid=1020 comm="apparmor_parser"
[ 26.401945] Bluetooth: Core ver 2.16
[ 26.401964] NET: Registered protocol family 31
[ 26.401966] Bluetooth: HCI device and connection manager initialized
[ 26.401975] Bluetooth: HCI socket layer initialized
[ 26.401977] Bluetooth: L2CAP socket layer initialized
[ 26.401982] Bluetooth: SCO socket layer initialized
[ 26.472275] Bluetooth: RFCOMM TTY layer initialized
[ 26.472287] Bluetooth: RFCOMM socket layer initialized
[ 26.472288] Bluetooth: RFCOMM ver 1.11
[ 26.656803] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 26.656805] Bluetooth: BNEP filters: protocol multicast
[ 26.656815] Bluetooth: BNEP socket layer initialized
[ 27.144233] type=1400 audit(1358870862.742:10): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=1082 comm="apparmor_parser"
[ 27.144574] type=1400 audit(1358870862.742:11): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1082 comm="apparmor_parser"
[ 27.144769] type=1400 audit(1358870862.742:12): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=1082 comm="apparmor_parser"
[ 27.183200] type=1400 audit(1358870862.782:13): apparmor="STATUS" operation="profile_load" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=1081 comm="apparmor_parser"
[ 27.312368] type=1400 audit(1358870862.910:14): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince" pid=1083 comm="apparmor_parser"
[ 27.315982] type=1400 audit(1358870862.910:15): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince//launchpad_integration" pid=1083 comm="apparmor_parser"
[ 27.316783] type=1400 audit(1358870862.914:16): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince//sanitized_helper" pid=1083 comm="apparmor_parser"
[ 27.317545] type=1400 audit(1358870862.914:17): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince-previewer" pid=1083 comm="apparmor_parser"
[ 27.319749] type=1400 audit(1358870862.914:18): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince-previewer//launchpad_integration" pid=1083 comm="apparmor_parser"
[ 27.320456] type=1400 audit(1358870862.918:19): apparmor="STATUS" operation="profile_load" name="/usr/bin/evince-previewer//sanitized_helper" pid=1083 comm="apparmor_parser"
[ 27.360498] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 27.464074] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
[ 27.464196] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 29.068829] init: isc-dhcp-server main process (1207) terminated with status 1
[ 29.068854] init: isc-dhcp-server main process ended, respawning
[ 29.383580] init: isc-dhcp-server main process (1225) terminated with status 1
[ 29.383603] init: isc-dhcp-server main process ended, respawning
[ 29.830677] init: isc-dhcp-server main process (1234) terminated with status 1
[ 29.830701] init: isc-dhcp-server main process ended, respawning
[ 29.995991] init: isc-dhcp-server main process (1243) terminated with status 1
[ 29.996031] init: isc-dhcp-server main process ended, respawning
[ 30.095252] init: isc-dhcp-server main process (1250) terminated with status 1
[ 30.095274] init: isc-dhcp-server main process ended, respawning
[ 30.244882] init: isc-dhcp-server main process (1257) terminated with status 1
[ 30.244902] init: isc-dhcp-server main process ended, respawning
[ 30.400864] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 30.400895] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 30.447708] init: isc-dhcp-server main process (1264) terminated with status 1
[ 30.447744] init: isc-dhcp-server main process ended, respawning
[ 30.817215] init: isc-dhcp-server main process (1272) terminated with status 1
[ 30.817237] init: isc-dhcp-server main process ended, respawning
[ 31.462225] init: isc-dhcp-server main process (1293) terminated with status 1
[ 31.462247] init: isc-dhcp-server main process ended, respawning
[ 31.570152] init: isc-dhcp-server main process (1304) terminated with status 1
[ 31.570174] init: isc-dhcp-server main process ended, respawning
[ 31.677995] init: isc-dhcp-server main process (1311) terminated with status 1
[ 31.678018] init: isc-dhcp-server respawning too fast, stopped
[ 32.728505] Bridge firewalling registered
[ 33.198212] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 34.604029] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 35.926614] init: plymouth-upstart-bridge main process (959) killed by TERM signal
[ 36.152772] Ebtables v2.0 registered
[ 36.198962] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 36.983657] cgroup: libvirtd (1298) created nested cgroup for controller "devices" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
[ 36.983703] cgroup: libvirtd (1298) created nested cgroup for controller "blkio" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
[ 39.031571] init: plymouth-stop pre-start process (1756) terminated with status 1
[ 189.629891] audit_printk_skb: 30 callbacks suppressed
[ 189.629896] type=1400 audit(1358871022.457:30): apparmor="DENIED" operation="capable" parent=1 profile="/usr/sbin/cupsd" pid=1032 comm="cupsd" pid=1032 comm="cupsd" capability=36 capname="block_suspend"
[ 200.640490] radeon 0000:01:00.0: texture bo too small ((200 200) (64 1) 1 26 0 -> 204800 have 143360)
[ 200.640494] radeon 0000:01:00.0: alignments 1472 64 1 256
[ 200.640496] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
[ 200.641800] radeon 0000:01:00.0: texture bo too small ((200 200) (64 1) 1 26 0 -> 204800 have 143360)
[ 200.641803] radeon 0000:01:00.0: alignments 1472 64 1 256
[ 200.641804] [drm:radeon_cs_ib_chunk] *ERROR* Invalid command stream !
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-22 18:05 ` Shuah Khan
@ 2013-01-22 18:29 ` Shuah Khan
2013-01-22 18:40 ` Deucher, Alexander
1 sibling, 0 replies; 30+ messages in thread
From: Shuah Khan @ 2013-01-22 18:29 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 2738 bytes --]
On Tue, Jan 22, 2013 at 11:05 AM, Shuah Khan <shuahkhan@gmail.com> wrote:
> On Tue, Jan 22, 2013 at 9:36 AM, Deucher, Alexander
> <Alexander.Deucher@amd.com> wrote:
>>> -----Original Message-----
>>> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>>> Sent: Tuesday, January 22, 2013 11:15 AM
>>> To: Deucher, Alexander
>>> Cc: Linus Torvalds; Linux Kernel Mailing List
>>> Subject: Re: Linux 3.8-rc4
>>>
>>> On Sat, Jan 19, 2013 at 9:44 AM, Deucher, Alexander
>>> <Alexander.Deucher@amd.com> wrote:
>>> >> -----Original Message-----
>>> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>>> >> Sent: Friday, January 18, 2013 7:40 PM
>>> >> To: Linus Torvalds; Deucher, Alexander
>>> >> Cc: Linux Kernel Mailing List
>>> >> Subject: Re: Linux 3.8-rc4
>>> >>
>>> >> On Fri, Jan 18, 2013 at 3:37 PM, Shuah Khan <shuahkhan@gmail.com>
>>> wrote:
>>> >> > On Fri, Jan 18, 2013 at 10:51 AM, Shuah Khan <shuahkhan@gmail.com>
>>> >> wrote:
>>> >>
>>> >> >
>>> >> > ok. I bisected the DMAR faults and it points to the following commit:
>>> >> >
>>> >> > 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb
>>> >> >
>>> >> > This commit as I recall, fixed the crash problem I was seeing back in
>>> >> > 3.8-rc1. Reverting to see if crash problem reappears.
>>> >>
>>> >> Confirming that with this commit reverted crash problem re-appeared.
>>> >> With this commit, DMAR faults show up.
>>> >
>>> > I'm not quite sure what's going on with your system. At this point it's
>>> probably best to just disable the DMA ring on these cards until we sort out
>>> what's going on. The attached patch disables the use of the DMA ring. Let
>>> me know if it fixes the issues you are seeing.
>>> >
>>>
>>> I applied this patch to 3.8-rc4 and didn't fix the DMAR faults.
>>
>> Are you getting continuous DMAR faults or just when while the module is being loaded?
>>
>> Alex
>
> During module initialization, I think might be actually right after
> RV620 Microcode loading attempt: dmesg excerpts starting from radeoan
Here is the log from 3.7.4-rc4 without this problem. These faults
definitely are showing up during Microcode loading process if I am
reading the dmesg correctly.
[ 20.560517] [drm] Loading RV620 Microcode
[ 20.639618] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 20.639670] radeon 0000:01:00.0: WB enabled
[ 20.639674] radeon 0000:01:00.0: fence driver on ring 0 use gpu
addr 0x0000000008000c00 and cpu addr 0xffff88006d5b3c00
[ 20.672797] [drm] ring test on 0 succeeded in 1 usecs
[ 20.674597] [drm] ib test on ring 0 succeeded in 0 usecs
[ 20.675083] [drm] radeon atom DIG backlight initialized
[ 20.675085] [drm] Radeon Display Connectors
Attaching compressed dmesg from 3.7.4-rc1 boot on this system
-- Shuah
[-- Attachment #2: dmesg_3.7.4-rc1_radeon.gz --]
[-- Type: application/x-gzip, Size: 18734 bytes --]
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: Linux 3.8-rc4
2013-01-22 18:05 ` Shuah Khan
2013-01-22 18:29 ` Shuah Khan
@ 2013-01-22 18:40 ` Deucher, Alexander
2013-01-22 18:55 ` Shuah Khan
1 sibling, 1 reply; 30+ messages in thread
From: Deucher, Alexander @ 2013-01-22 18:40 UTC (permalink / raw)
To: Shuah Khan; +Cc: Linus Torvalds, Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 7365 bytes --]
> -----Original Message-----
> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> Sent: Tuesday, January 22, 2013 1:06 PM
> To: Deucher, Alexander
> Cc: Linus Torvalds; Linux Kernel Mailing List
> Subject: Re: Linux 3.8-rc4
>
> On Tue, Jan 22, 2013 at 9:36 AM, Deucher, Alexander
> <Alexander.Deucher@amd.com> wrote:
> >> -----Original Message-----
> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> >> Sent: Tuesday, January 22, 2013 11:15 AM
> >> To: Deucher, Alexander
> >> Cc: Linus Torvalds; Linux Kernel Mailing List
> >> Subject: Re: Linux 3.8-rc4
> >>
> >> On Sat, Jan 19, 2013 at 9:44 AM, Deucher, Alexander
> >> <Alexander.Deucher@amd.com> wrote:
> >> >> -----Original Message-----
> >> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> >> >> Sent: Friday, January 18, 2013 7:40 PM
> >> >> To: Linus Torvalds; Deucher, Alexander
> >> >> Cc: Linux Kernel Mailing List
> >> >> Subject: Re: Linux 3.8-rc4
> >> >>
> >> >> On Fri, Jan 18, 2013 at 3:37 PM, Shuah Khan <shuahkhan@gmail.com>
> >> wrote:
> >> >> > On Fri, Jan 18, 2013 at 10:51 AM, Shuah Khan
> <shuahkhan@gmail.com>
> >> >> wrote:
> >> >>
> >> >> >
> >> >> > ok. I bisected the DMAR faults and it points to the following commit:
> >> >> >
> >> >> > 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb
> >> >> >
> >> >> > This commit as I recall, fixed the crash problem I was seeing back in
> >> >> > 3.8-rc1. Reverting to see if crash problem reappears.
> >> >>
> >> >> Confirming that with this commit reverted crash problem re-appeared.
> >> >> With this commit, DMAR faults show up.
> >> >
> >> > I'm not quite sure what's going on with your system. At this point it's
> >> probably best to just disable the DMA ring on these cards until we sort out
> >> what's going on. The attached patch disables the use of the DMA ring.
> Let
> >> me know if it fixes the issues you are seeing.
> >> >
> >>
> >> I applied this patch to 3.8-rc4 and didn't fix the DMAR faults.
> >
> > Are you getting continuous DMAR faults or just when while the module is
> being loaded?
> >
> > Alex
>
> During module initialization, I think might be actually right after
> RV620 Microcode loading attempt: dmesg excerpts starting from radeoan
> init:
Does the attached patch stop them? It basically skips all initialization of the DMA ring on your system. What I don't understand is why you still get them with the previous patch, but not with 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb reverted. 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb only affects the use of the DMA ring for buffer migration and the patch I previously attached disables the use of the DMA ring for buffer migration. Does the latest batch of drm-fixes from Dave that Linus just merged help?
Alex
>
> [ 22.150520] [drm] radeon defaulting to kernel modesetting.
> [ 22.150524] [drm] radeon kernel modesetting enabled.
> [ 22.150793] [drm] initializing kernel modesetting (RV620 0x1002:0x95C4
> 0x103C
> :0x30DC).
> [ 22.150815] [drm] register mmio base: 0x90300000
> [ 22.150817] [drm] register mmio size: 65536
> [ 22.150918] ATOM BIOS: HP
> [ 22.150941] radeon 0000:01:00.0: VRAM: 128M 0x0000000000000000 -
> 0x0000000007
> FFFFFF (128M used)
> [ 22.150943] radeon 0000:01:00.0: GTT: 512M 0x0000000008000000 -
> 0x0000000027F
> FFFFF
> [ 22.153790] [drm] Detected VRAM RAM=128M, BAR=128M
> [ 22.153793] [drm] RAM width 64bits DDR
> [ 22.153850] [TTM] Zone kernel: Available graphics memory: 989986 kiB
> [ 22.153852] [TTM] Initializing pool allocator
> [ 22.153857] [TTM] Initializing DMA pool allocator
> [ 22.153884] [drm] radeon: 128M of VRAM memory ready
> [ 22.153885] [drm] radeon: 512M of GTT memory ready.
> [ 22.153902] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
> [ 22.153903] [drm] Driver supports precise vblank timestamp query.
> [ 22.153947] radeon 0000:01:00.0: irq 51 for MSI/MSI-X
> [ 22.153958] radeon 0000:01:00.0: radeon: using MSI.
> [ 22.153988] [drm] radeon: irq initialized.
> [ 22.154034] [drm] GART: num cpu pages 131072, num gpu pages 131072
> [ 22.154796] [drm] probing gen 2 caps for device 8086:2a41 = 1/0
>
> [ 22.154969] [drm] Loading RV620 Microcode
>
> [ 22.218044] dmar: DRHD: handling fault status reg 3
> [ 22.218054] dmar: DMAR:[DMA Read] Request device [01:00.0] fault
> addr 80000000
> [ 22.218054] DMAR:[fault reason 06] PTE Read access is not set
> [ 22.218083] dmar: DRHD: handling fault status reg 3
> [ 22.218089] dmar: DMAR:[DMA Read] Request device [01:00.0] fault
> addr 80002000
> [ 22.218089] DMAR:[fault reason 06] PTE Read access is not set
> [ 22.218123] dmar: DRHD: handling fault status reg 3
> [ 22.218128] dmar: DMAR:[DMA Read] Request device [01:00.0] fault
> addr 80004000
> [ 22.218128] DMAR:[fault reason 06] PTE Read access is not set
> [ 22.218155] dmar: DRHD: handling fault status reg 3
> [ 22.218159] dmar: DMAR:[DMA Read] Request device [01:00.0] fault
> addr 80006000
> [ 22.218159] DMAR:[fault reason 06] PTE Read access is not set
> [ 22.218169] dmar: DRHD: handling fault status reg 3
> [ 22.218173] dmar: DMAR:[DMA Read] Request device [01:00.0] fault
> addr 80007000
> [ 22.218173] DMAR:[fault reason 06] PTE Read access is not set
> [ 22.218191] dmar: DRHD: handling fault status reg 3
>
> tons of these and then:
>
>
> [ 22.236419] [drm] PCIE GART of 512M enabled (table at
> 0x0000000000040000).
> [ 22.236479] radeon 0000:01:00.0: WB enabled
> [ 22.236483] radeon 0000:01:00.0: fence driver on ring 0 use gpu
> addr 0x0000000008
> 000c00 and cpu addr 0xffff88002f436c00
> [ 22.236485] radeon 0000:01:00.0: fence driver on ring 3 use gpu
> addr 0x0000000008
> 000c0c and cpu addr 0xffff88002f436c0c
> [ 22.270041] [drm] ring test on 0 succeeded in 1 usecs
> [ 22.270099] [drm] ring test on 3 succeeded in 1 usecs
> [ 22.272156] [drm] ib test on ring 0 succeeded in 0 usecs
> [ 22.272170] [drm] ib test on ring 3 succeeded in 0 usecs
> [ 22.272705] [drm] radeon atom DIG backlight initialized
> [ 22.272707] [drm] Radeon Display Connectors
> [ 22.272708] [drm] Connector 0:
> [ 22.272710] [drm] LVDS-1
> [ 22.272711] [drm] Encoders:
> [ 22.272712] [drm] LCD1: INTERNAL_KLDSCP_LVTMA
> [ 22.272713] [drm] Connector 1:
> [ 22.272714] [drm] VGA-1
> [ 22.272716] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48
> 0x7e4c 0x7e4c
> [ 22.272717] [drm] Encoders:
> [ 22.272718] [drm] CRT1: INTERNAL_KLDSCP_DAC1
> [ 22.272719] [drm] Connector 2:
> [ 22.272720] [drm] DVI-D-1
> [ 22.272721] [drm] HPD1
> [ 22.272723] [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68
> 0x7e6c 0x7e6c
> [ 22.272724] [drm] Encoders:
> [ 22.272725] [drm] DFP1: INTERNAL_UNIPHY
> [ 22.272758] [drm] radeon: power management initialized
> [ 23.232093] fbcon: radeondrmfb (fb0) is primary device
> [ 23.496217] Console: switching to colour frame buffer device 180x56
> [ 23.499083] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
> [ 23.499085] radeon 0000:01:00.0: registered panic notifier
> [ 23.499100] [drm] Initialized radeon 2.28.0 20080528 for
> 0000:01:00.0 on minor 0
>
>
> Attaching entire dmesg as well:
>
> -- Shuah
[-- Attachment #2: disable_dma_ring_on_6xx-2.diff --]
[-- Type: application/octet-stream, Size: 3841 bytes --]
diff --git a/drivers/gpu/drm/radeon/r600.c b/drivers/gpu/drm/radeon/r600.c
index 04f3745..75625f6 100644
--- a/drivers/gpu/drm/radeon/r600.c
+++ b/drivers/gpu/drm/radeon/r600.c
@@ -2900,11 +2900,13 @@ static int r600_startup(struct radeon_device *rdev)
return r;
}
+#if 0
r = radeon_fence_driver_start_ring(rdev, R600_RING_TYPE_DMA_INDEX);
if (r) {
dev_err(rdev->dev, "failed initializing DMA fences (%d).\n", r);
return r;
}
+#endif
/* Enable IRQ */
r = r600_irq_init(rdev);
@@ -2922,12 +2924,14 @@ static int r600_startup(struct radeon_device *rdev)
if (r)
return r;
+#if 0
ring = &rdev->ring[R600_RING_TYPE_DMA_INDEX];
r = radeon_ring_init(rdev, ring, ring->ring_size, R600_WB_DMA_RPTR_OFFSET,
DMA_RB_RPTR, DMA_RB_WPTR,
2, 0x3fffc, DMA_PACKET(DMA_PACKET_NOP, 0, 0, 0));
if (r)
return r;
+#endif
r = r600_cp_load_microcode(rdev);
if (r)
@@ -2936,9 +2940,11 @@ static int r600_startup(struct radeon_device *rdev)
if (r)
return r;
+#if 0
r = r600_dma_resume(rdev);
if (r)
return r;
+#endif
r = radeon_ib_pool_init(rdev);
if (r) {
@@ -2995,7 +3001,9 @@ int r600_suspend(struct radeon_device *rdev)
{
r600_audio_fini(rdev);
r600_cp_stop(rdev);
+#if 0
r600_dma_stop(rdev);
+#endif
r600_irq_suspend(rdev);
radeon_wb_disable(rdev);
r600_pcie_gart_disable(rdev);
@@ -3068,8 +3076,10 @@ int r600_init(struct radeon_device *rdev)
rdev->ring[RADEON_RING_TYPE_GFX_INDEX].ring_obj = NULL;
r600_ring_init(rdev, &rdev->ring[RADEON_RING_TYPE_GFX_INDEX], 1024 * 1024);
+#if 0
rdev->ring[R600_RING_TYPE_DMA_INDEX].ring_obj = NULL;
r600_ring_init(rdev, &rdev->ring[R600_RING_TYPE_DMA_INDEX], 64 * 1024);
+#endif
rdev->ih.ring_obj = NULL;
r600_ih_ring_init(rdev, 64 * 1024);
@@ -3083,7 +3093,9 @@ int r600_init(struct radeon_device *rdev)
if (r) {
dev_err(rdev->dev, "disabling GPU acceleration\n");
r600_cp_fini(rdev);
+#if 0
r600_dma_fini(rdev);
+#endif
r600_irq_fini(rdev);
radeon_wb_fini(rdev);
radeon_ib_pool_fini(rdev);
@@ -3100,7 +3112,9 @@ void r600_fini(struct radeon_device *rdev)
r600_audio_fini(rdev);
r600_blit_fini(rdev);
r600_cp_fini(rdev);
+#if 0
r600_dma_fini(rdev);
+#endif
r600_irq_fini(rdev);
radeon_wb_fini(rdev);
radeon_ib_pool_fini(rdev);
diff --git a/drivers/gpu/drm/radeon/radeon_asic.c b/drivers/gpu/drm/radeon/radeon_asic.c
index 9056faf..b0cc46d 100644
--- a/drivers/gpu/drm/radeon/radeon_asic.c
+++ b/drivers/gpu/drm/radeon/radeon_asic.c
@@ -974,8 +974,8 @@ static struct radeon_asic r600_asic = {
.blit_ring_index = RADEON_RING_TYPE_GFX_INDEX,
.dma = &r600_copy_dma,
.dma_ring_index = R600_RING_TYPE_DMA_INDEX,
- .copy = &r600_copy_dma,
- .copy_ring_index = R600_RING_TYPE_DMA_INDEX,
+ .copy = &r600_copy_blit,
+ .copy_ring_index = RADEON_RING_TYPE_GFX_INDEX,
},
.surface = {
.set_reg = r600_set_surface_reg,
@@ -1058,8 +1058,8 @@ static struct radeon_asic rs780_asic = {
.blit_ring_index = RADEON_RING_TYPE_GFX_INDEX,
.dma = &r600_copy_dma,
.dma_ring_index = R600_RING_TYPE_DMA_INDEX,
- .copy = &r600_copy_dma,
- .copy_ring_index = R600_RING_TYPE_DMA_INDEX,
+ .copy = &r600_copy_blit,
+ .copy_ring_index = RADEON_RING_TYPE_GFX_INDEX,
},
.surface = {
.set_reg = r600_set_surface_reg,
diff --git a/drivers/gpu/drm/radeon/radeon_cs.c b/drivers/gpu/drm/radeon/radeon_cs.c
index 312cd91..a4364e4 100644
--- a/drivers/gpu/drm/radeon/radeon_cs.c
+++ b/drivers/gpu/drm/radeon/radeon_cs.c
@@ -115,7 +115,7 @@ static int radeon_cs_get_ring(struct radeon_cs_parser *p, u32 ring, s32 priority
p->ring = R600_RING_TYPE_DMA_INDEX;
else
p->ring = CAYMAN_RING_TYPE_DMA1_INDEX;
- } else if (p->rdev->family >= CHIP_R600) {
+ } else if (p->rdev->family >= CHIP_RV770) {
p->ring = R600_RING_TYPE_DMA_INDEX;
} else {
return -EINVAL;
^ permalink raw reply related [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-22 18:40 ` Deucher, Alexander
@ 2013-01-22 18:55 ` Shuah Khan
2013-01-22 23:57 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-22 18:55 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
On Tue, Jan 22, 2013 at 11:40 AM, Deucher, Alexander
<Alexander.Deucher@amd.com> wrote:
>> -----Original Message-----
>> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> Sent: Tuesday, January 22, 2013 1:06 PM
>> To: Deucher, Alexander
>> Cc: Linus Torvalds; Linux Kernel Mailing List
>> Subject: Re: Linux 3.8-rc4
>>
>> On Tue, Jan 22, 2013 at 9:36 AM, Deucher, Alexander
>> <Alexander.Deucher@amd.com> wrote:
>> >> -----Original Message-----
>> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> >> Sent: Tuesday, January 22, 2013 11:15 AM
>> >> To: Deucher, Alexander
>> >> Cc: Linus Torvalds; Linux Kernel Mailing List
>> >> Subject: Re: Linux 3.8-rc4
>> >>
>> >> On Sat, Jan 19, 2013 at 9:44 AM, Deucher, Alexander
>> >> <Alexander.Deucher@amd.com> wrote:
>> >> >> -----Original Message-----
>> >> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> >> >> Sent: Friday, January 18, 2013 7:40 PM
>> >> >> To: Linus Torvalds; Deucher, Alexander
>> >> >> Cc: Linux Kernel Mailing List
>> >> >> Subject: Re: Linux 3.8-rc4
>> >> >>
>> >> >> On Fri, Jan 18, 2013 at 3:37 PM, Shuah Khan <shuahkhan@gmail.com>
>> >> wrote:
>> >> >> > On Fri, Jan 18, 2013 at 10:51 AM, Shuah Khan
>> <shuahkhan@gmail.com>
>> >> >> wrote:
>> >> >>
>> >> >> >
>> >> >> > ok. I bisected the DMAR faults and it points to the following commit:
>> >> >> >
>> >> >> > 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb
>> >> >> >
>> >> >> > This commit as I recall, fixed the crash problem I was seeing back in
>> >> >> > 3.8-rc1. Reverting to see if crash problem reappears.
>> >> >>
>> >> >> Confirming that with this commit reverted crash problem re-appeared.
>> >> >> With this commit, DMAR faults show up.
>> >> >
>> >> > I'm not quite sure what's going on with your system. At this point it's
>> >> probably best to just disable the DMA ring on these cards until we sort out
>> >> what's going on. The attached patch disables the use of the DMA ring.
>> Let
>> >> me know if it fixes the issues you are seeing.
>> >> >
>> >>
>> >> I applied this patch to 3.8-rc4 and didn't fix the DMAR faults.
>> >
>> > Are you getting continuous DMAR faults or just when while the module is
>> being loaded?
>> >
>> > Alex
>>
>> During module initialization, I think might be actually right after
>> RV620 Microcode loading attempt: dmesg excerpts starting from radeoan
>> init:
>
> Does the attached patch stop them? It basically skips all initialization of the DMA ring on your system. What I don't understand is why you still get them with the previous patch, but not with 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb reverted. 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb only affects the use of the DMA ring for buffer migration and the patch I previously attached disables the use of the DMA ring for buffer migration. Does the latest batch of drm-fixes from Dave that Linus just merged help?
>
> Alex
Will try your latest patch. Will also try the latest git - I am
currently on Jan 17th. However, in the meantime, I found that these
messages might not be new and getting printed now with the
eaaa6983ab2ccdf826c90838eb584211e0cadb76 [PATCH] drm/radeon: print dma
status reg on lockup (v2) commit that introduced debug messages in
r600_gpu_soft_reset(). I couldn't revert this commit, but doing a
compile with these messages commented out. Will update you on the
results and then test the new git
-- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-22 18:55 ` Shuah Khan
@ 2013-01-22 23:57 ` Shuah Khan
2013-01-23 13:40 ` Deucher, Alexander
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-22 23:57 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
On Tue, Jan 22, 2013 at 11:55 AM, Shuah Khan <shuahkhan@gmail.com> wrote:
>>> init:
>>
>> Does the attached patch stop them? It basically skips all initialization of the DMA ring on your system. What I don't understand is why you still get them with the previous patch, but not with 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb reverted. 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb only affects the use of the DMA ring for buffer migration and the patch I previously attached disables the use of the DMA ring for buffer migration. Does the latest batch of drm-fixes from Dave that Linus just merged help?
>>
>> Alex
>
> Will try your latest patch. Will also try the latest git - I am
> currently on Jan 17th. However, in the meantime, I found that these
> messages might not be new and getting printed now with the
> eaaa6983ab2ccdf826c90838eb584211e0cadb76 [PATCH] drm/radeon: print dma
> status reg on lockup (v2) commit that introduced debug messages in
> r600_gpu_soft_reset(). I couldn't revert this commit, but doing a
> compile with these messages commented out. Will update you on the
> results and then test the new git
>
> -- Shuah
Here is what I tried:
1. Applied your latest disable_dma_ring_on_6xx-2.diff and still see messages.
2. Tried intel_iommu=igfx_off to see if that changes anything. The
reason for trying this option is, I noticed this message: (this is not
a new message, I see this all the time)
[ 1.337112] DMAR: Disabling IOMMU for graphics on this chipset
No change with or without option - still see the same messages.
Next steps:
1. One big difference between 3.7 and 3.8 is in the
r600_gpu_soft_reset() - I started with 3.7 to see the differences if
any of these differences is causing this to be logged. In 3.7
r600_gpu_soft_reset() is called with no reset_mask. I am going to
first verify if softreset happens on 3.7. Does this give you any ideas
of whether this could cause a problem?
2. Another angle I am looking at is the newly added
dev_info(rdev->dev, " R_00D034_DMA_STATUS_REG = 0x%08X\n",
RREG32(DMA_STATUS_REG));
messages in r600_gpu_soft_reset_dma().
Could it be that these newly added debug messages are now showing this
old condition that always existed on my test system. From what I have
observed so far, this is very likely.
Please let me know if you want to me try anything else or if you don't
think these steps won't help.
-- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: Linux 3.8-rc4
2013-01-22 23:57 ` Shuah Khan
@ 2013-01-23 13:40 ` Deucher, Alexander
2013-01-23 18:44 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Deucher, Alexander @ 2013-01-23 13:40 UTC (permalink / raw)
To: Shuah Khan; +Cc: Linus Torvalds, Linux Kernel Mailing List
> -----Original Message-----
> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> Sent: Tuesday, January 22, 2013 6:57 PM
> To: Deucher, Alexander
> Cc: Linus Torvalds; Linux Kernel Mailing List
> Subject: Re: Linux 3.8-rc4
>
> On Tue, Jan 22, 2013 at 11:55 AM, Shuah Khan <shuahkhan@gmail.com>
> wrote:
>
> >>> init:
> >>
> >> Does the attached patch stop them? It basically skips all initialization of
> the DMA ring on your system. What I don't understand is why you still get
> them with the previous patch, but not with
> 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb reverted.
> 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb only affects the use of the
> DMA ring for buffer migration and the patch I previously attached disables
> the use of the DMA ring for buffer migration. Does the latest batch of drm-
> fixes from Dave that Linus just merged help?
> >>
> >> Alex
> >
> > Will try your latest patch. Will also try the latest git - I am
> > currently on Jan 17th. However, in the meantime, I found that these
> > messages might not be new and getting printed now with the
> > eaaa6983ab2ccdf826c90838eb584211e0cadb76 [PATCH] drm/radeon: print
> dma
> > status reg on lockup (v2) commit that introduced debug messages in
> > r600_gpu_soft_reset(). I couldn't revert this commit, but doing a
> > compile with these messages commented out. Will update you on the
> > results and then test the new git
> >
> > -- Shuah
>
> Here is what I tried:
>
> 1. Applied your latest disable_dma_ring_on_6xx-2.diff and still see
> messages.
If that is the case, I'm beginning to think the bug is elsewhere. Support for the DMA ring was the only major feature we added in this cycle. If you are still getting errors even with the ring completely disabled, it's probably not the DMA ring.
Make sure your kernel has this patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=20707874fd4fd37e09513f508e642fa8bd06365a
That's the only thing I can think of that may cause the DMAR errors if the DMA ring is disabled.
> 2. Tried intel_iommu=igfx_off to see if that changes anything. The
> reason for trying this option is, I noticed this message: (this is not
> a new message, I see this all the time)
>
> [ 1.337112] DMAR: Disabling IOMMU for graphics on this chipset
>
> No change with or without option - still see the same messages.
>
> Next steps:
>
> 1. One big difference between 3.7 and 3.8 is in the
> r600_gpu_soft_reset() - I started with 3.7 to see the differences if
> any of these differences is causing this to be logged. In 3.7
> r600_gpu_soft_reset() is called with no reset_mask. I am going to
> first verify if softreset happens on 3.7. Does this give you any ideas
> of whether this could cause a problem?
I don't think the problem is related to GPU reset. That's for resetting the GPU when it hangs. It changed slightly in 3.8 to accommodate the new DMA engine that we added support for in 3.8. Previously we just reset the graphics engine.
>
> 2. Another angle I am looking at is the newly added
>
> dev_info(rdev->dev, " R_00D034_DMA_STATUS_REG = 0x%08X\n",
> RREG32(DMA_STATUS_REG));
>
> messages in r600_gpu_soft_reset_dma().
>
> Could it be that these newly added debug messages are now showing this
> old condition that always existed on my test system. From what I have
> observed so far, this is very likely.
I'm not following. That just prints the DMA status register when we attempt to reset the GPU. It's purely for debugging.
Alex
>
> Please let me know if you want to me try anything else or if you don't
> think these steps won't help.
>
> -- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-23 13:40 ` Deucher, Alexander
@ 2013-01-23 18:44 ` Shuah Khan
2013-01-29 3:19 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-23 18:44 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
On Wed, Jan 23, 2013 at 6:40 AM, Deucher, Alexander
<Alexander.Deucher@amd.com> wrote:
>> -----Original Message-----
>> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> Sent: Tuesday, January 22, 2013 6:57 PM
>> To: Deucher, Alexander
>> Cc: Linus Torvalds; Linux Kernel Mailing List
>> Subject: Re: Linux 3.8-rc4
>>
>> On Tue, Jan 22, 2013 at 11:55 AM, Shuah Khan <shuahkhan@gmail.com>
>> wrote:
>>
>> >>> init:
>> >>
>> >> Does the attached patch stop them? It basically skips all initialization of
>> the DMA ring on your system. What I don't understand is why you still get
>> them with the previous patch, but not with
>> 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb reverted.
>> 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb only affects the use of the
>> DMA ring for buffer migration and the patch I previously attached disables
>> the use of the DMA ring for buffer migration. Does the latest batch of drm-
>> fixes from Dave that Linus just merged help?
>> >>
>> >> Alex
>> >
>> > Will try your latest patch. Will also try the latest git - I am
>> > currently on Jan 17th. However, in the meantime, I found that these
>> > messages might not be new and getting printed now with the
>> > eaaa6983ab2ccdf826c90838eb584211e0cadb76 [PATCH] drm/radeon: print
>> dma
>> > status reg on lockup (v2) commit that introduced debug messages in
>> > r600_gpu_soft_reset(). I couldn't revert this commit, but doing a
>> > compile with these messages commented out. Will update you on the
>> > results and then test the new git
>> >
>> > -- Shuah
>>
>> Here is what I tried:
>>
>> 1. Applied your latest disable_dma_ring_on_6xx-2.diff and still see
>> messages.
>
> If that is the case, I'm beginning to think the bug is elsewhere. Support for the DMA ring was the only major feature we added in this cycle. If you are still getting errors even with the ring completely disabled, it's probably not the DMA ring.
>
> Make sure your kernel has this patch:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=20707874fd4fd37e09513f508e642fa8bd06365a
> That's the only thing I can think of that may cause the DMAR errors if the DMA ring is disabled.
>
I verified I have this commit. ok maybe the bug is elsewhere. So far
all my bisects are on drivers/gpu/drm/radeon - I am going go one more
level up and start at drivers/gpu/drm and see what I can isolate it
that way. I do know that I don't see this problem on 3.7.4
-- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-23 18:44 ` Shuah Khan
@ 2013-01-29 3:19 ` Shuah Khan
2013-01-29 13:05 ` Deucher, Alexander
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-29 3:19 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 3333 bytes --]
On Wed, Jan 23, 2013 at 11:44 AM, Shuah Khan <shuahkhan@gmail.com> wrote:
> On Wed, Jan 23, 2013 at 6:40 AM, Deucher, Alexander
> <Alexander.Deucher@amd.com> wrote:
>>> -----Original Message-----
>>> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>>> Sent: Tuesday, January 22, 2013 6:57 PM
>>> To: Deucher, Alexander
>>> Cc: Linus Torvalds; Linux Kernel Mailing List
>>> Subject: Re: Linux 3.8-rc4
>>>
>>> On Tue, Jan 22, 2013 at 11:55 AM, Shuah Khan <shuahkhan@gmail.com>
>>> wrote:
>>>
>>> >>> init:
>>> >>
>>> >> Does the attached patch stop them? It basically skips all initialization of
>>> the DMA ring on your system. What I don't understand is why you still get
>>> them with the previous patch, but not with
>>> 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb reverted.
>>> 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb only affects the use of the
>>> DMA ring for buffer migration and the patch I previously attached disables
>>> the use of the DMA ring for buffer migration. Does the latest batch of drm-
>>> fixes from Dave that Linus just merged help?
>>> >>
>>> >> Alex
>>> >
>>> > Will try your latest patch. Will also try the latest git - I am
>>> > currently on Jan 17th. However, in the meantime, I found that these
>>> > messages might not be new and getting printed now with the
>>> > eaaa6983ab2ccdf826c90838eb584211e0cadb76 [PATCH] drm/radeon: print
>>> dma
>>> > status reg on lockup (v2) commit that introduced debug messages in
>>> > r600_gpu_soft_reset(). I couldn't revert this commit, but doing a
>>> > compile with these messages commented out. Will update you on the
>>> > results and then test the new git
>>> >
>>> > -- Shuah
>>>
>>> Here is what I tried:
>>>
>>> 1. Applied your latest disable_dma_ring_on_6xx-2.diff and still see
>>> messages.
>>
>> If that is the case, I'm beginning to think the bug is elsewhere. Support for the DMA ring was the only major feature we added in this cycle. If you are still getting errors even with the ring completely disabled, it's probably not the DMA ring.
>>
>> Make sure your kernel has this patch:
>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=20707874fd4fd37e09513f508e642fa8bd06365a
>> That's the only thing I can think of that may cause the DMAR errors if the DMA ring is disabled.
>>
>
> I verified I have this commit. ok maybe the bug is elsewhere. So far
> all my bisects are on drivers/gpu/drm/radeon - I am going go one more
> level up and start at drivers/gpu/drm and see what I can isolate it
> that way. I do know that I don't see this problem on 3.7.4
>
> -- Shuah
Alex,
I was out sick for a few days and finally picked this bisect backup
again. I started at 3.7 tag instead of 3.8-rc1 that I did in the past
and also did bisect at drivers/gpu/drm/radeon instead. Here are the
results:
6253e4c75d96006c06b9ac8f417eba873de2497b is the first bad commit
commit 6253e4c75d96006c06b9ac8f417eba873de2497b
Author: Alex Deucher <alexander.deucher@amd.com>
Date: Wed Dec 12 14:30:32 2012 -0500
drm/radeon: improve mc_stop/mc_resume on r5xx-r7xx
Along the same lines of what was done for evergreen+
in the last kernel.
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
git bisect log attached.
I am going to try doing a revert on this commit tomorrow and see if
that clears the problem.
-- Shuah
[-- Attachment #2: git_bisect_log_jan28 --]
[-- Type: application/octet-stream, Size: 4921 bytes --]
git bisect start '--' 'drivers/gpu/drm'
# good: [29594404d7fe73cd80eaa4ee8c43dcc53970c60e] Linux 3.7
git bisect good 29594404d7fe73cd80eaa4ee8c43dcc53970c60e
# bad: [8f0d8163b50e01f398b14bcd4dc039ac5ab18d64] Linux 3.7-rc3
git bisect bad 8f0d8163b50e01f398b14bcd4dc039ac5ab18d64
# bad: [9931faca02c604c22335f5a935a501bb2ace6e20] Linux 3.8-rc3
git bisect bad 9931faca02c604c22335f5a935a501bb2ace6e20
# skip: [944234d6a2c46a4666533904b7ea8c79807e9072] drm/nv50/disp: allow PCI_US pushbuf binding
git bisect skip 944234d6a2c46a4666533904b7ea8c79807e9072
# skip: [e5e454f918051e4ff4be98777ee25437d48c3a1e] drm/nvc0/copy: share interrupt handler with nva3
git bisect skip e5e454f918051e4ff4be98777ee25437d48c3a1e
# skip: [76e438303403f301f3509479b544e41518edd059] drm/i915: move hpd handling to (ibx|cpt)_irq_handler
git bisect skip 76e438303403f301f3509479b544e41518edd059
# skip: [be7cb6347e0c3aa1956748a860a2465a7ea128c4] drm/i915: Remove bogus test for a present execbuffer
git bisect skip be7cb6347e0c3aa1956748a860a2465a7ea128c4
# bad: [8be0e5c427c18a59ce261c496ae2193cbcbafffd] Merge branch 'drm-intel-fixes' of git://people.freedesktop.org/~danvet/drm-intel into drm-next
git bisect bad 8be0e5c427c18a59ce261c496ae2193cbcbafffd
# skip: [5f8e256704e86df795037b18395fdf102b75199e] drm/nv40/fb: start bashing zcomp registers on relevant chipsets
git bisect skip 5f8e256704e86df795037b18395fdf102b75199e
# skip: [f4c956adc79f852e1f064679c2847b8ece2cd16f] drm/i915: move the suspend/resume register file out of dev_priv
git bisect skip f4c956adc79f852e1f064679c2847b8ece2cd16f
# skip: [b5c621584ba57e6112864dcd79b71020c9525f6a] drm/i915: Use pci_resource functions for BARs.
git bisect skip b5c621584ba57e6112864dcd79b71020c9525f6a
# skip: [3f69e7605d6b072b9890845bb6d9f982bcd879ec] drm/nouveau: remove misleading comment from nouveau_prime_new
git bisect skip 3f69e7605d6b072b9890845bb6d9f982bcd879ec
# skip: [5774506f157a91400c587b85d1ce4de56f0d32f6] drm/i915: Borrow our struct_mutex for the direct reclaim
git bisect skip 5774506f157a91400c587b85d1ce4de56f0d32f6
# skip: [d640c4b09a5d83a8167eb09d22bd89d9fa7e3b91] drm/i915: Report amount of usable graphics memory in MiB
git bisect skip d640c4b09a5d83a8167eb09d22bd89d9fa7e3b91
# good: [b180b5d1c7ac930387734664802fc26fa788e26f] drm: Be more paranoid with integer overflows
git bisect good b180b5d1c7ac930387734664802fc26fa788e26f
# skip: [96081cdfae35c1e332be42d89dee278c72d8915d] drm/drm_fb_helper: Remove unnecessary braces
git bisect skip 96081cdfae35c1e332be42d89dee278c72d8915d
# skip: [71bfe916ebe6d026cd3d0e41c398574fc1228e03] drm/radeon: bump driver version for new info ioctl requests
git bisect skip 71bfe916ebe6d026cd3d0e41c398574fc1228e03
# skip: [d8f4a9eda006788d8054b8500d9eb5b6efcd8755] drm: Add NVIDIA Tegra20 support
git bisect skip d8f4a9eda006788d8054b8500d9eb5b6efcd8755
# skip: [5ddf4d4a543dd3303b20d7e9a4b3549589c5f095] drm/nouveau/bios: cache ramcfg strap on later chipsets
git bisect skip 5ddf4d4a543dd3303b20d7e9a4b3549589c5f095
# good: [e62f2f5acba1d466da047983ae16f6b96b68b310] drm: use monotonic time in drm_calc_vbltimestamp_from_scanoutpos
git bisect good e62f2f5acba1d466da047983ae16f6b96b68b310
# good: [7136470d4b37b46565b29b8b9425a8361421483b] Merge branch 'for-airlied' of git://people.freedesktop.org/~danvet/drm-intel into drm-next
git bisect good 7136470d4b37b46565b29b8b9425a8361421483b
# skip: [a0e41b562b3e302b47f887056d89189b816ce219] drm/exynos/iommu: fix return value check in drm_create_iommu_mapping()
git bisect skip a0e41b562b3e302b47f887056d89189b816ce219
# good: [97a875cbdf89a4638eea57c2b456c7cc4e3e8b21] drm/ttm: remove no_wait_reserve, v3
git bisect good 97a875cbdf89a4638eea57c2b456c7cc4e3e8b21
# skip: [2f3f24061c5c489074ad492bf694a5a76ebd8fc5] Merge branch 'exynos-drm-next' of git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos into drm-next
git bisect skip 2f3f24061c5c489074ad492bf694a5a76ebd8fc5
# skip: [60a705a9f97b83b1daf03295bf123af84a46116a] drm/exynos: fix fb offset calculation for plane
git bisect skip 60a705a9f97b83b1daf03295bf123af84a46116a
# bad: [9af20792124850369e764965690b99b20623dfc4] drm/radeon: fix fence locking in the pageflip callback
git bisect bad 9af20792124850369e764965690b99b20623dfc4
# good: [a636a9829175987e74ddd28a2e87ed17ff7adfdc] Merge branch 'drm-next-3.8' of git://people.freedesktop.org/~agd5f/linux into drm-next
git bisect good a636a9829175987e74ddd28a2e87ed17ff7adfdc
# bad: [8770b86b3e02c3e30f2ffc42753ff9d62bc428bf] drm/radeon: add support for CP DMA packet to evergreen CS checker
git bisect bad 8770b86b3e02c3e30f2ffc42753ff9d62bc428bf
# bad: [6253e4c75d96006c06b9ac8f417eba873de2497b] drm/radeon: improve mc_stop/mc_resume on r5xx-r7xx
git bisect bad 6253e4c75d96006c06b9ac8f417eba873de2497b
# good: [bd25f0783dc3fb72e1e2779c2b99b2d34b67fa8a] drm/radeon: fix amd afusion gpu setup aka sumo v2
git bisect good bd25f0783dc3fb72e1e2779c2b99b2d34b67fa8a
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: Linux 3.8-rc4
2013-01-29 3:19 ` Shuah Khan
@ 2013-01-29 13:05 ` Deucher, Alexander
2013-01-29 19:11 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Deucher, Alexander @ 2013-01-29 13:05 UTC (permalink / raw)
To: Shuah Khan; +Cc: Linus Torvalds, Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 3855 bytes --]
> -----Original Message-----
> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> Sent: Monday, January 28, 2013 10:20 PM
> To: Deucher, Alexander
> Cc: Linus Torvalds; Linux Kernel Mailing List
> Subject: Re: Linux 3.8-rc4
>
> On Wed, Jan 23, 2013 at 11:44 AM, Shuah Khan <shuahkhan@gmail.com>
> wrote:
> > On Wed, Jan 23, 2013 at 6:40 AM, Deucher, Alexander
> > <Alexander.Deucher@amd.com> wrote:
> >>> -----Original Message-----
> >>> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> >>> Sent: Tuesday, January 22, 2013 6:57 PM
> >>> To: Deucher, Alexander
> >>> Cc: Linus Torvalds; Linux Kernel Mailing List
> >>> Subject: Re: Linux 3.8-rc4
> >>>
> >>> On Tue, Jan 22, 2013 at 11:55 AM, Shuah Khan <shuahkhan@gmail.com>
> >>> wrote:
> >>>
> >>> >>> init:
> >>> >>
> >>> >> Does the attached patch stop them? It basically skips all initialization
> of
> >>> the DMA ring on your system. What I don't understand is why you still
> get
> >>> them with the previous patch, but not with
> >>> 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb reverted.
> >>> 909d9eb67f1e4e39f2ea88e96bde03d560cde3eb only affects the use of
> the
> >>> DMA ring for buffer migration and the patch I previously attached
> disables
> >>> the use of the DMA ring for buffer migration. Does the latest batch of
> drm-
> >>> fixes from Dave that Linus just merged help?
> >>> >>
> >>> >> Alex
> >>> >
> >>> > Will try your latest patch. Will also try the latest git - I am
> >>> > currently on Jan 17th. However, in the meantime, I found that these
> >>> > messages might not be new and getting printed now with the
> >>> > eaaa6983ab2ccdf826c90838eb584211e0cadb76 [PATCH] drm/radeon:
> print
> >>> dma
> >>> > status reg on lockup (v2) commit that introduced debug messages in
> >>> > r600_gpu_soft_reset(). I couldn't revert this commit, but doing a
> >>> > compile with these messages commented out. Will update you on the
> >>> > results and then test the new git
> >>> >
> >>> > -- Shuah
> >>>
> >>> Here is what I tried:
> >>>
> >>> 1. Applied your latest disable_dma_ring_on_6xx-2.diff and still see
> >>> messages.
> >>
> >> If that is the case, I'm beginning to think the bug is elsewhere. Support
> for the DMA ring was the only major feature we added in this cycle. If you
> are still getting errors even with the ring completely disabled, it's probably
> not the DMA ring.
> >>
> >> Make sure your kernel has this patch:
> >>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=2
> 0707874fd4fd37e09513f508e642fa8bd06365a
> >> That's the only thing I can think of that may cause the DMAR errors if the
> DMA ring is disabled.
> >>
> >
> > I verified I have this commit. ok maybe the bug is elsewhere. So far
> > all my bisects are on drivers/gpu/drm/radeon - I am going go one more
> > level up and start at drivers/gpu/drm and see what I can isolate it
> > that way. I do know that I don't see this problem on 3.7.4
> >
> > -- Shuah
>
> Alex,
>
> I was out sick for a few days and finally picked this bisect backup
> again. I started at 3.7 tag instead of 3.8-rc1 that I did in the past
> and also did bisect at drivers/gpu/drm/radeon instead. Here are the
> results:
>
> 6253e4c75d96006c06b9ac8f417eba873de2497b is the first bad commit
> commit 6253e4c75d96006c06b9ac8f417eba873de2497b
> Author: Alex Deucher <alexander.deucher@amd.com>
> Date: Wed Dec 12 14:30:32 2012 -0500
>
> drm/radeon: improve mc_stop/mc_resume on r5xx-r7xx
>
> Along the same lines of what was done for evergreen+
> in the last kernel.
>
> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>
> git bisect log attached.
>
Try the attached patch. I think it should fix the issue. I just applied a similar patch for newer asics.
Alex
[-- Attachment #2: 0001-drm-radeon-fix-MC-blackout-on-r5xx-r7xx.patch --]
[-- Type: application/octet-stream, Size: 2469 bytes --]
From 9085f78d289bc75d69162b402d715d32da403080 Mon Sep 17 00:00:00 2001
From: Alex Deucher <alexander.deucher@amd.com>
Date: Tue, 29 Jan 2013 07:59:07 -0500
Subject: [PATCH] drm/radeon: fix MC blackout on r5xx-r7xx
Force the crtc mem requests on/off immediately rather
than waiting for the double buffered updates to kick in.
Seems we miss the update in certain conditions. Based on
a similar fix for evergreen.
Reported-by: Shuah Khan <shuahkhan@gmail.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org
---
drivers/gpu/drm/radeon/r500_reg.h | 1 +
drivers/gpu/drm/radeon/rv515.c | 4 ++++
2 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/radeon/r500_reg.h b/drivers/gpu/drm/radeon/r500_reg.h
index ec576aa..5159f0d 100644
--- a/drivers/gpu/drm/radeon/r500_reg.h
+++ b/drivers/gpu/drm/radeon/r500_reg.h
@@ -358,6 +358,7 @@
#define AVIVO_D1CRTC_STEREO_CONTROL 0x60c4
#define AVIVO_D1MODE_MASTER_UPDATE_MODE 0x60e4
+#define AVIVO_D1CRTC_UPDATE_LOCK 0x60e8
/* master controls */
#define AVIVO_DC_CRTC_MASTER_EN 0x60f8
diff --git a/drivers/gpu/drm/radeon/rv515.c b/drivers/gpu/drm/radeon/rv515.c
index 2bb6d0e..a5290b2 100644
--- a/drivers/gpu/drm/radeon/rv515.c
+++ b/drivers/gpu/drm/radeon/rv515.c
@@ -304,7 +304,9 @@ void rv515_mc_stop(struct radeon_device *rdev, struct rv515_mc_save *save)
if (!(tmp & AVIVO_CRTC_DISP_READ_REQUEST_DISABLE)) {
radeon_wait_for_vblank(rdev, i);
tmp |= AVIVO_CRTC_DISP_READ_REQUEST_DISABLE;
+ WREG32(AVIVO_D1CRTC_UPDATE_LOCK + crtc_offsets[i], 1);
WREG32(AVIVO_D1CRTC_CONTROL + crtc_offsets[i], tmp);
+ WREG32(AVIVO_D1CRTC_UPDATE_LOCK + crtc_offsets[i], 0);
}
/* wait for the next frame */
frame_count = radeon_get_vblank_counter(rdev, i);
@@ -384,7 +386,9 @@ void rv515_mc_resume(struct radeon_device *rdev, struct rv515_mc_save *save)
if (save->crtc_enabled[i]) {
tmp = RREG32(AVIVO_D1CRTC_CONTROL + crtc_offsets[i]);
tmp &= ~AVIVO_CRTC_DISP_READ_REQUEST_DISABLE;
+ WREG32(AVIVO_D1CRTC_UPDATE_LOCK + crtc_offsets[i], 1);
WREG32(AVIVO_D1CRTC_CONTROL + crtc_offsets[i], tmp);
+ WREG32(AVIVO_D1CRTC_UPDATE_LOCK + crtc_offsets[i], 0);
/* wait for the next frame */
frame_count = radeon_get_vblank_counter(rdev, i);
for (j = 0; j < rdev->usec_timeout; j++) {
--
1.7.7.5
^ permalink raw reply related [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-29 13:05 ` Deucher, Alexander
@ 2013-01-29 19:11 ` Shuah Khan
2013-01-29 20:13 ` Deucher, Alexander
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-29 19:11 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
On Tue, Jan 29, 2013 at 6:05 AM, Deucher, Alexander
<Alexander.Deucher@amd.com> wrote:
>> -----Original Message-----
>> I was out sick for a few days and finally picked this bisect backup
>> again. I started at 3.7 tag instead of 3.8-rc1 that I did in the past
>> and also did bisect at drivers/gpu/drm/radeon instead. Here are the
>> results:
>>
>> 6253e4c75d96006c06b9ac8f417eba873de2497b is the first bad commit
>> commit 6253e4c75d96006c06b9ac8f417eba873de2497b
>> Author: Alex Deucher <alexander.deucher@amd.com>
>> Date: Wed Dec 12 14:30:32 2012 -0500
>>
>> drm/radeon: improve mc_stop/mc_resume on r5xx-r7xx
>>
>> Along the same lines of what was done for evergreen+
>> in the last kernel.
>>
>> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>>
>> git bisect log attached.
>>
>
> Try the attached patch. I think it should fix the issue. I just applied a similar patch for newer asics.
>
> Alex
>
I reverted 6253e4c75d96006c06b9ac8f417eba873de2497b and DMAR faults
went away. Undid the revert and applied your new patch. DMAR faults
are back again.
[ 25.158653] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 25.158715] radeon 0000:01:00.0: WB enabled
[ 25.158719] radeon 0000:01:00.0: fence driver on ring 0 use gpu
addr 0x0000000008000c00 and cpu addr 0xffff88002f143c00
[ 25.158721] radeon 0000:01:00.0: fence driver on ring 3 use gpu
addr 0x0000000008000c0c and cpu addr 0xffff88002f143c0c
A few observations and questions about r600_startup() code sequence:
I notice DMAR faults right after
[drm] Loading RV620 Microcode message which is from
r600_init_microcode(). This routine does a series of
request_firmware() calls. btw. don't see release_firmware() calls in
regular code path, only from error legs in r600_init_microcode().
However, this routine doesn't do any loading yet. When this routine
returns, I am assuming request_firmware() step isn't complete yet
based on my reading request_firmware() interface. At this point
r600_startup() keeps chugging along, and does r600_mc_program() which
in turn calls rv515_mc_stop() which was changed with the
6253e4c75d96006c06b9ac8f417eba873de2497b commit.
I am thinking the changes somehow eliminated a wait or delay that used
be there for request_firmware() step to complete (?)
I can see from dmesg that the faults occur right after:
r600_init_microcode(rdev);
and stop before r600_pcie_gart_enable()
-- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: Linux 3.8-rc4
2013-01-29 19:11 ` Shuah Khan
@ 2013-01-29 20:13 ` Deucher, Alexander
2013-01-29 21:39 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Deucher, Alexander @ 2013-01-29 20:13 UTC (permalink / raw)
To: Shuah Khan; +Cc: Linus Torvalds, Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 3837 bytes --]
> -----Original Message-----
> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> Sent: Tuesday, January 29, 2013 2:11 PM
> To: Deucher, Alexander
> Cc: Linus Torvalds; Linux Kernel Mailing List
> Subject: Re: Linux 3.8-rc4
>
> On Tue, Jan 29, 2013 at 6:05 AM, Deucher, Alexander
> <Alexander.Deucher@amd.com> wrote:
> >> -----Original Message-----
> >> I was out sick for a few days and finally picked this bisect backup
> >> again. I started at 3.7 tag instead of 3.8-rc1 that I did in the past
> >> and also did bisect at drivers/gpu/drm/radeon instead. Here are the
> >> results:
> >>
> >> 6253e4c75d96006c06b9ac8f417eba873de2497b is the first bad commit
> >> commit 6253e4c75d96006c06b9ac8f417eba873de2497b
> >> Author: Alex Deucher <alexander.deucher@amd.com>
> >> Date: Wed Dec 12 14:30:32 2012 -0500
> >>
> >> drm/radeon: improve mc_stop/mc_resume on r5xx-r7xx
> >>
> >> Along the same lines of what was done for evergreen+
> >> in the last kernel.
> >>
> >> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> >>
> >> git bisect log attached.
> >>
> >
> > Try the attached patch. I think it should fix the issue. I just applied a similar
> patch for newer asics.
> >
> > Alex
> >
>
> I reverted 6253e4c75d96006c06b9ac8f417eba873de2497b and DMAR faults
> went away. Undid the revert and applied your new patch. DMAR faults
> are back again.
>
>
> [ 25.158653] [drm] PCIE GART of 512M enabled (table at
> 0x0000000000040000).
> [ 25.158715] radeon 0000:01:00.0: WB enabled
> [ 25.158719] radeon 0000:01:00.0: fence driver on ring 0 use gpu
> addr 0x0000000008000c00 and cpu addr 0xffff88002f143c00
> [ 25.158721] radeon 0000:01:00.0: fence driver on ring 3 use gpu
> addr 0x0000000008000c0c and cpu addr 0xffff88002f143c0c
>
> A few observations and questions about r600_startup() code sequence:
>
> I notice DMAR faults right after
>
> [drm] Loading RV620 Microcode message which is from
> r600_init_microcode(). This routine does a series of
> request_firmware() calls. btw. don't see release_firmware() calls in
> regular code path, only from error legs in r600_init_microcode().
>
> However, this routine doesn't do any loading yet. When this routine
> returns, I am assuming request_firmware() step isn't complete yet
> based on my reading request_firmware() interface. At this point
> r600_startup() keeps chugging along, and does r600_mc_program() which
> in turn calls rv515_mc_stop() which was changed with the
> 6253e4c75d96006c06b9ac8f417eba873de2497b commit.
>
> I am thinking the changes somehow eliminated a wait or delay that used
> be there for request_firmware() step to complete (?)
>
> I can see from dmesg that the faults occur right after:
>
> r600_init_microcode(rdev);
>
> and stop before r600_pcie_gart_enable()
r600_init_microcode() doesn't actually touch the hardware it just calls request_firmware() to fetch the microcode images from disk. The microcode doesn't get loaded onto the hardware until r600_cp_load_microcode() much later in the function. I don't think the microcode has anything to do with this.
rv515_mc_stop() stops GPU memory clients (e.g., the displays) and blacks out the GPU memory controller so that we can change the location of VRAM within the GPU's address space. If one of the display controllers memory request stop requests takes too long to go through for some reason, it's possible that the display hardware may attempt to read from a GPU memory location no-longer backed by vram (since we changed the location of vram in r600_mc_program()) momentarily until the stop request goes through. Does the attached updated version of the patch help? Alternatively, you can try adding delays to the end of rv515_mc_stop() and see if that helps.
Alex
[-- Attachment #2: 0001-drm-radeon-fix-MC-blackout-on-r5xx-r7xx-v2.patch --]
[-- Type: application/octet-stream, Size: 3347 bytes --]
From 1ed227b4a690da075e6e9068bc16131edbd03c96 Mon Sep 17 00:00:00 2001
From: Alex Deucher <alexander.deucher@amd.com>
Date: Tue, 29 Jan 2013 07:59:07 -0500
Subject: [PATCH] drm/radeon: fix MC blackout on r5xx-r7xx (v2)
Force the crtc mem requests on/off immediately rather
than waiting for the double buffered updates to kick in.
Seems we miss the update in certain conditions. Based on
a similar fix for evergreen.
v2: take the grph lock when updating the new display
base addresses.
Reported-by: Shuah Khan <shuahkhan@gmail.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org
---
drivers/gpu/drm/radeon/r500_reg.h | 1 +
drivers/gpu/drm/radeon/rv515.c | 8 ++++++++
2 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/radeon/r500_reg.h b/drivers/gpu/drm/radeon/r500_reg.h
index ec576aa..5159f0d 100644
--- a/drivers/gpu/drm/radeon/r500_reg.h
+++ b/drivers/gpu/drm/radeon/r500_reg.h
@@ -358,6 +358,7 @@
#define AVIVO_D1CRTC_STEREO_CONTROL 0x60c4
#define AVIVO_D1MODE_MASTER_UPDATE_MODE 0x60e4
+#define AVIVO_D1CRTC_UPDATE_LOCK 0x60e8
/* master controls */
#define AVIVO_DC_CRTC_MASTER_EN 0x60f8
diff --git a/drivers/gpu/drm/radeon/rv515.c b/drivers/gpu/drm/radeon/rv515.c
index 2bb6d0e..c736b4a 100644
--- a/drivers/gpu/drm/radeon/rv515.c
+++ b/drivers/gpu/drm/radeon/rv515.c
@@ -304,7 +304,9 @@ void rv515_mc_stop(struct radeon_device *rdev, struct rv515_mc_save *save)
if (!(tmp & AVIVO_CRTC_DISP_READ_REQUEST_DISABLE)) {
radeon_wait_for_vblank(rdev, i);
tmp |= AVIVO_CRTC_DISP_READ_REQUEST_DISABLE;
+ WREG32(AVIVO_D1CRTC_UPDATE_LOCK + crtc_offsets[i], 1);
WREG32(AVIVO_D1CRTC_CONTROL + crtc_offsets[i], tmp);
+ WREG32(AVIVO_D1CRTC_UPDATE_LOCK + crtc_offsets[i], 0);
}
/* wait for the next frame */
frame_count = radeon_get_vblank_counter(rdev, i);
@@ -345,6 +347,8 @@ void rv515_mc_resume(struct radeon_device *rdev, struct rv515_mc_save *save)
/* update crtc base addresses */
for (i = 0; i < rdev->num_crtc; i++) {
+ WREG32_P(AVIVO_D1GRPH_UPDATE + crtc_offsets[i],
+ AVIVO_D1GRPH_UPDATE_LOCK, ~AVIVO_D1GRPH_UPDATE_LOCK);
if (rdev->family >= CHIP_RV770) {
if (i == 1) {
WREG32(R700_D1GRPH_PRIMARY_SURFACE_ADDRESS_HIGH,
@@ -362,6 +366,8 @@ void rv515_mc_resume(struct radeon_device *rdev, struct rv515_mc_save *save)
(u32)rdev->mc.vram_start);
WREG32(R_006118_D1GRPH_SECONDARY_SURFACE_ADDRESS + crtc_offsets[i],
(u32)rdev->mc.vram_start);
+ WREG32_P(AVIVO_D1GRPH_UPDATE + crtc_offsets[i],
+ 0, ~AVIVO_D1GRPH_UPDATE_LOCK);
}
WREG32(R_000310_VGA_MEMORY_BASE_ADDRESS, (u32)rdev->mc.vram_start);
@@ -384,7 +390,9 @@ void rv515_mc_resume(struct radeon_device *rdev, struct rv515_mc_save *save)
if (save->crtc_enabled[i]) {
tmp = RREG32(AVIVO_D1CRTC_CONTROL + crtc_offsets[i]);
tmp &= ~AVIVO_CRTC_DISP_READ_REQUEST_DISABLE;
+ WREG32(AVIVO_D1CRTC_UPDATE_LOCK + crtc_offsets[i], 1);
WREG32(AVIVO_D1CRTC_CONTROL + crtc_offsets[i], tmp);
+ WREG32(AVIVO_D1CRTC_UPDATE_LOCK + crtc_offsets[i], 0);
/* wait for the next frame */
frame_count = radeon_get_vblank_counter(rdev, i);
for (j = 0; j < rdev->usec_timeout; j++) {
--
1.7.7.5
^ permalink raw reply related [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-29 20:13 ` Deucher, Alexander
@ 2013-01-29 21:39 ` Shuah Khan
2013-01-29 22:02 ` Deucher, Alexander
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-29 21:39 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
On Tue, Jan 29, 2013 at 1:13 PM, Deucher, Alexander
<Alexander.Deucher@amd.com> wrote:
>> -----Original Message-----
>> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> Sent: Tuesday, January 29, 2013 2:11 PM
>> To: Deucher, Alexander
>> Cc: Linus Torvalds; Linux Kernel Mailing List
>> Subject: Re: Linux 3.8-rc4
>>
>> On Tue, Jan 29, 2013 at 6:05 AM, Deucher, Alexander
>> <Alexander.Deucher@amd.com> wrote:
>> >> -----Original Message-----
>> >> I was out sick for a few days and finally picked this bisect backup
>> >> again. I started at 3.7 tag instead of 3.8-rc1 that I did in the past
>> >> and also did bisect at drivers/gpu/drm/radeon instead. Here are the
>> >> results:
>> >>
>> >> 6253e4c75d96006c06b9ac8f417eba873de2497b is the first bad commit
>> >> commit 6253e4c75d96006c06b9ac8f417eba873de2497b
>> >> Author: Alex Deucher <alexander.deucher@amd.com>
>> >> Date: Wed Dec 12 14:30:32 2012 -0500
>> >>
>> >> drm/radeon: improve mc_stop/mc_resume on r5xx-r7xx
>> >>
>> >> Along the same lines of what was done for evergreen+
>> >> in the last kernel.
>> >>
>> >> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>> >>
>> >> git bisect log attached.
>> >>
>> >
>> > Try the attached patch. I think it should fix the issue. I just applied a similar
>> patch for newer asics.
>> >
>> > Alex
>> >
>>
>> I reverted 6253e4c75d96006c06b9ac8f417eba873de2497b and DMAR faults
>> went away. Undid the revert and applied your new patch. DMAR faults
>> are back again.
>>
>>
>> [ 25.158653] [drm] PCIE GART of 512M enabled (table at
>> 0x0000000000040000).
>> [ 25.158715] radeon 0000:01:00.0: WB enabled
>> [ 25.158719] radeon 0000:01:00.0: fence driver on ring 0 use gpu
>> addr 0x0000000008000c00 and cpu addr 0xffff88002f143c00
>> [ 25.158721] radeon 0000:01:00.0: fence driver on ring 3 use gpu
>> addr 0x0000000008000c0c and cpu addr 0xffff88002f143c0c
>>
>> A few observations and questions about r600_startup() code sequence:
>>
>> I notice DMAR faults right after
>>
>> [drm] Loading RV620 Microcode message which is from
>> r600_init_microcode(). This routine does a series of
>> request_firmware() calls. btw. don't see release_firmware() calls in
>> regular code path, only from error legs in r600_init_microcode().
>>
>> However, this routine doesn't do any loading yet. When this routine
>> returns, I am assuming request_firmware() step isn't complete yet
>> based on my reading request_firmware() interface. At this point
>> r600_startup() keeps chugging along, and does r600_mc_program() which
>> in turn calls rv515_mc_stop() which was changed with the
>> 6253e4c75d96006c06b9ac8f417eba873de2497b commit.
>>
>> I am thinking the changes somehow eliminated a wait or delay that used
>> be there for request_firmware() step to complete (?)
>>
>> I can see from dmesg that the faults occur right after:
>>
>> r600_init_microcode(rdev);
>>
>> and stop before r600_pcie_gart_enable()
>
> r600_init_microcode() doesn't actually touch the hardware it just calls request_firmware() to fetch the microcode images from disk. The microcode doesn't get loaded onto the hardware until r600_cp_load_microcode() much later in the function. I don't think the microcode has anything to do with this.
>
> rv515_mc_stop() stops GPU memory clients (e.g., the displays) and blacks out the GPU memory controller so that we can change the location of VRAM within the GPU's address space. If one of the display controllers memory request stop requests takes too long to go through for some reason, it's possible that the display hardware may attempt to read from a GPU memory location no-longer backed by vram (since we changed the location of vram in r600_mc_program()) momentarily until the stop request goes through. Does the attached updated version of the patch help? Alternatively, you can try adding delays to the end of rv515_mc_stop() and see if that helps.
>
> Alex
>
This v2 patch didn't help. I added mdelay(15); at the end of
rv515_mc_stop() on top of this v2 patch and that fixed the problem.
mdelay(15) is a bit much I am sure. Shouldn't rv515_mc_wait_for_idle()
take care of the delay? It waits for idle usec_timeout?
-- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: Linux 3.8-rc4
2013-01-29 21:39 ` Shuah Khan
@ 2013-01-29 22:02 ` Deucher, Alexander
2013-01-29 23:45 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Deucher, Alexander @ 2013-01-29 22:02 UTC (permalink / raw)
To: Shuah Khan; +Cc: Linus Torvalds, Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 4970 bytes --]
> -----Original Message-----
> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> Sent: Tuesday, January 29, 2013 4:40 PM
> To: Deucher, Alexander
> Cc: Linus Torvalds; Linux Kernel Mailing List
> Subject: Re: Linux 3.8-rc4
>
> On Tue, Jan 29, 2013 at 1:13 PM, Deucher, Alexander
> <Alexander.Deucher@amd.com> wrote:
> >> -----Original Message-----
> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> >> Sent: Tuesday, January 29, 2013 2:11 PM
> >> To: Deucher, Alexander
> >> Cc: Linus Torvalds; Linux Kernel Mailing List
> >> Subject: Re: Linux 3.8-rc4
> >>
> >> On Tue, Jan 29, 2013 at 6:05 AM, Deucher, Alexander
> >> <Alexander.Deucher@amd.com> wrote:
> >> >> -----Original Message-----
> >> >> I was out sick for a few days and finally picked this bisect backup
> >> >> again. I started at 3.7 tag instead of 3.8-rc1 that I did in the past
> >> >> and also did bisect at drivers/gpu/drm/radeon instead. Here are the
> >> >> results:
> >> >>
> >> >> 6253e4c75d96006c06b9ac8f417eba873de2497b is the first bad commit
> >> >> commit 6253e4c75d96006c06b9ac8f417eba873de2497b
> >> >> Author: Alex Deucher <alexander.deucher@amd.com>
> >> >> Date: Wed Dec 12 14:30:32 2012 -0500
> >> >>
> >> >> drm/radeon: improve mc_stop/mc_resume on r5xx-r7xx
> >> >>
> >> >> Along the same lines of what was done for evergreen+
> >> >> in the last kernel.
> >> >>
> >> >> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> >> >>
> >> >> git bisect log attached.
> >> >>
> >> >
> >> > Try the attached patch. I think it should fix the issue. I just applied a
> similar
> >> patch for newer asics.
> >> >
> >> > Alex
> >> >
> >>
> >> I reverted 6253e4c75d96006c06b9ac8f417eba873de2497b and DMAR
> faults
> >> went away. Undid the revert and applied your new patch. DMAR faults
> >> are back again.
> >>
> >>
> >> [ 25.158653] [drm] PCIE GART of 512M enabled (table at
> >> 0x0000000000040000).
> >> [ 25.158715] radeon 0000:01:00.0: WB enabled
> >> [ 25.158719] radeon 0000:01:00.0: fence driver on ring 0 use gpu
> >> addr 0x0000000008000c00 and cpu addr 0xffff88002f143c00
> >> [ 25.158721] radeon 0000:01:00.0: fence driver on ring 3 use gpu
> >> addr 0x0000000008000c0c and cpu addr 0xffff88002f143c0c
> >>
> >> A few observations and questions about r600_startup() code sequence:
> >>
> >> I notice DMAR faults right after
> >>
> >> [drm] Loading RV620 Microcode message which is from
> >> r600_init_microcode(). This routine does a series of
> >> request_firmware() calls. btw. don't see release_firmware() calls in
> >> regular code path, only from error legs in r600_init_microcode().
> >>
> >> However, this routine doesn't do any loading yet. When this routine
> >> returns, I am assuming request_firmware() step isn't complete yet
> >> based on my reading request_firmware() interface. At this point
> >> r600_startup() keeps chugging along, and does r600_mc_program() which
> >> in turn calls rv515_mc_stop() which was changed with the
> >> 6253e4c75d96006c06b9ac8f417eba873de2497b commit.
> >>
> >> I am thinking the changes somehow eliminated a wait or delay that used
> >> be there for request_firmware() step to complete (?)
> >>
> >> I can see from dmesg that the faults occur right after:
> >>
> >> r600_init_microcode(rdev);
> >>
> >> and stop before r600_pcie_gart_enable()
> >
> > r600_init_microcode() doesn't actually touch the hardware it just calls
> request_firmware() to fetch the microcode images from disk. The microcode
> doesn't get loaded onto the hardware until r600_cp_load_microcode() much
> later in the function. I don't think the microcode has anything to do with this.
> >
> > rv515_mc_stop() stops GPU memory clients (e.g., the displays) and blacks
> out the GPU memory controller so that we can change the location of VRAM
> within the GPU's address space. If one of the display controllers memory
> request stop requests takes too long to go through for some reason, it's
> possible that the display hardware may attempt to read from a GPU memory
> location no-longer backed by vram (since we changed the location of vram in
> r600_mc_program()) momentarily until the stop request goes through. Does
> the attached updated version of the patch help? Alternatively, you can try
> adding delays to the end of rv515_mc_stop() and see if that helps.
> >
> > Alex
> >
>
> This v2 patch didn't help. I added mdelay(15); at the end of
> rv515_mc_stop() on top of this v2 patch and that fixed the problem.
> mdelay(15) is a bit much I am sure. Shouldn't rv515_mc_wait_for_idle()
> take care of the delay? It waits for idle usec_timeout?
It only waits that long if the MC never goes idle. If the MC happens to be idle at the time, it will return immediately. Does the attached patch fix the issue? It waits for the update pending bit to clear in addition to waiting for the next frame.
Alex
[-- Attachment #2: 0001-drm-radeon-fix-MC-blackout-on-r5xx-r7xx-v3.patch --]
[-- Type: application/octet-stream, Size: 2444 bytes --]
From c30471c7eb49d98f4c224a1b3060f7cb773e4900 Mon Sep 17 00:00:00 2001
From: Alex Deucher <alexander.deucher@amd.com>
Date: Tue, 29 Jan 2013 16:56:16 -0500
Subject: [PATCH] drm/radeon: fix MC blackout on r5xx-r7xx (v3)
Seems we miss the update in certain conditions. Wait
for the update pending bit to clear in addition to waiting
for the next frame.
v3: wait for pending bit to clear in addition to waiting
for the next frame.
Reported-by: Shuah Khan <shuahkhan@gmail.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Cc: stable@vger.kernel.org
---
drivers/gpu/drm/radeon/r500_reg.h | 2 ++
drivers/gpu/drm/radeon/rv515.c | 6 ++++--
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/radeon/r500_reg.h b/drivers/gpu/drm/radeon/r500_reg.h
index ec576aa..4fbabde 100644
--- a/drivers/gpu/drm/radeon/r500_reg.h
+++ b/drivers/gpu/drm/radeon/r500_reg.h
@@ -358,6 +358,8 @@
#define AVIVO_D1CRTC_STEREO_CONTROL 0x60c4
#define AVIVO_D1MODE_MASTER_UPDATE_MODE 0x60e4
+#define AVIVO_D1CRTC_UPDATE_LOCK 0x60e8
+#define AVIVO_D1CRTC_DOUBLE_BUFFER_CONTROL 0x60ec
/* master controls */
#define AVIVO_DC_CRTC_MASTER_EN 0x60f8
diff --git a/drivers/gpu/drm/radeon/rv515.c b/drivers/gpu/drm/radeon/rv515.c
index 2bb6d0e..7a0ce53 100644
--- a/drivers/gpu/drm/radeon/rv515.c
+++ b/drivers/gpu/drm/radeon/rv515.c
@@ -309,7 +309,8 @@ void rv515_mc_stop(struct radeon_device *rdev, struct rv515_mc_save *save)
/* wait for the next frame */
frame_count = radeon_get_vblank_counter(rdev, i);
for (j = 0; j < rdev->usec_timeout; j++) {
- if (radeon_get_vblank_counter(rdev, i) != frame_count)
+ if ((radeon_get_vblank_counter(rdev, i) != frame_count) &&
+ (!(RREG32(AVIVO_D1CRTC_DOUBLE_BUFFER_CONTROL + crtc_offsets[i]) & 1)))
break;
udelay(1);
}
@@ -388,7 +389,8 @@ void rv515_mc_resume(struct radeon_device *rdev, struct rv515_mc_save *save)
/* wait for the next frame */
frame_count = radeon_get_vblank_counter(rdev, i);
for (j = 0; j < rdev->usec_timeout; j++) {
- if (radeon_get_vblank_counter(rdev, i) != frame_count)
+ if ((radeon_get_vblank_counter(rdev, i) != frame_count) &&
+ (!(RREG32(AVIVO_D1CRTC_DOUBLE_BUFFER_CONTROL + crtc_offsets[i]) & 1)))
break;
udelay(1);
}
--
1.7.7.5
^ permalink raw reply related [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-29 22:02 ` Deucher, Alexander
@ 2013-01-29 23:45 ` Shuah Khan
2013-01-30 2:38 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-29 23:45 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
On Tue, Jan 29, 2013 at 3:02 PM, Deucher, Alexander
<Alexander.Deucher@amd.com> wrote:
>> -----Original Message-----
>> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> Sent: Tuesday, January 29, 2013 4:40 PM
>> To: Deucher, Alexander
>> Cc: Linus Torvalds; Linux Kernel Mailing List
>> Subject: Re: Linux 3.8-rc4
>>
>> On Tue, Jan 29, 2013 at 1:13 PM, Deucher, Alexander
>> <Alexander.Deucher@amd.com> wrote:
>> >> -----Original Message-----
>> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> >> Sent: Tuesday, January 29, 2013 2:11 PM
>> >> To: Deucher, Alexander
>> >> Cc: Linus Torvalds; Linux Kernel Mailing List
>> >> Subject: Re: Linux 3.8-rc4
>> >>
>> >> On Tue, Jan 29, 2013 at 6:05 AM, Deucher, Alexander
>> >> <Alexander.Deucher@amd.com> wrote:
>> >> >> -----Original Message-----
>> >> >> I was out sick for a few days and finally picked this bisect backup
>> >> >> again. I started at 3.7 tag instead of 3.8-rc1 that I did in the past
>> >> >> and also did bisect at drivers/gpu/drm/radeon instead. Here are the
>> >> >> results:
>> >> >>
>> >> >> 6253e4c75d96006c06b9ac8f417eba873de2497b is the first bad commit
>> >> >> commit 6253e4c75d96006c06b9ac8f417eba873de2497b
>> >> >> Author: Alex Deucher <alexander.deucher@amd.com>
>> >> >> Date: Wed Dec 12 14:30:32 2012 -0500
>> >> >>
>> >> >> drm/radeon: improve mc_stop/mc_resume on r5xx-r7xx
>> >> >>
>> >> >> Along the same lines of what was done for evergreen+
>> >> >> in the last kernel.
>> >> >>
>> >> >> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>> >> >>
>> >> >> git bisect log attached.
>> >> >>
>> >> >
>> >> > Try the attached patch. I think it should fix the issue. I just applied a
>> similar
>> >> patch for newer asics.
>> >> >
>> >> > Alex
>> >> >
>> >>
>> >> I reverted 6253e4c75d96006c06b9ac8f417eba873de2497b and DMAR
>> faults
>> >> went away. Undid the revert and applied your new patch. DMAR faults
>> >> are back again.
>> >>
>> >>
>> >> [ 25.158653] [drm] PCIE GART of 512M enabled (table at
>> >> 0x0000000000040000).
>> >> [ 25.158715] radeon 0000:01:00.0: WB enabled
>> >> [ 25.158719] radeon 0000:01:00.0: fence driver on ring 0 use gpu
>> >> addr 0x0000000008000c00 and cpu addr 0xffff88002f143c00
>> >> [ 25.158721] radeon 0000:01:00.0: fence driver on ring 3 use gpu
>> >> addr 0x0000000008000c0c and cpu addr 0xffff88002f143c0c
>> >>
>> >> A few observations and questions about r600_startup() code sequence:
>> >>
>> >> I notice DMAR faults right after
>> >>
>> >> [drm] Loading RV620 Microcode message which is from
>> >> r600_init_microcode(). This routine does a series of
>> >> request_firmware() calls. btw. don't see release_firmware() calls in
>> >> regular code path, only from error legs in r600_init_microcode().
>> >>
>> >> However, this routine doesn't do any loading yet. When this routine
>> >> returns, I am assuming request_firmware() step isn't complete yet
>> >> based on my reading request_firmware() interface. At this point
>> >> r600_startup() keeps chugging along, and does r600_mc_program() which
>> >> in turn calls rv515_mc_stop() which was changed with the
>> >> 6253e4c75d96006c06b9ac8f417eba873de2497b commit.
>> >>
>> >> I am thinking the changes somehow eliminated a wait or delay that used
>> >> be there for request_firmware() step to complete (?)
>> >>
>> >> I can see from dmesg that the faults occur right after:
>> >>
>> >> r600_init_microcode(rdev);
>> >>
>> >> and stop before r600_pcie_gart_enable()
>> >
>> > r600_init_microcode() doesn't actually touch the hardware it just calls
>> request_firmware() to fetch the microcode images from disk. The microcode
>> doesn't get loaded onto the hardware until r600_cp_load_microcode() much
>> later in the function. I don't think the microcode has anything to do with this.
>> >
>> > rv515_mc_stop() stops GPU memory clients (e.g., the displays) and blacks
>> out the GPU memory controller so that we can change the location of VRAM
>> within the GPU's address space. If one of the display controllers memory
>> request stop requests takes too long to go through for some reason, it's
>> possible that the display hardware may attempt to read from a GPU memory
>> location no-longer backed by vram (since we changed the location of vram in
>> r600_mc_program()) momentarily until the stop request goes through. Does
>> the attached updated version of the patch help? Alternatively, you can try
>> adding delays to the end of rv515_mc_stop() and see if that helps.
>> >
>> > Alex
>> >
>>
>> This v2 patch didn't help. I added mdelay(15); at the end of
>> rv515_mc_stop() on top of this v2 patch and that fixed the problem.
>> mdelay(15) is a bit much I am sure. Shouldn't rv515_mc_wait_for_idle()
>> take care of the delay? It waits for idle usec_timeout?
>
>
> It only waits that long if the MC never goes idle. If the MC happens to be idle at the time, it will return immediately. Does the attached patch fix the issue? It waits for the update pending bit to clear in addition to waiting for the next frame.
>
> Alex
>
No. This patch didn't fix the problem.
-- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-29 23:45 ` Shuah Khan
@ 2013-01-30 2:38 ` Shuah Khan
2013-01-30 13:31 ` Deucher, Alexander
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-30 2:38 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
On Tue, Jan 29, 2013 at 4:45 PM, Shuah Khan <shuahkhan@gmail.com> wrote:
> On Tue, Jan 29, 2013 at 3:02 PM, Deucher, Alexander
> <Alexander.Deucher@amd.com> wrote:
>>> -----Original Message-----
>>> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>>> Sent: Tuesday, January 29, 2013 4:40 PM
>>> To: Deucher, Alexander
>>> Cc: Linus Torvalds; Linux Kernel Mailing List
>>> Subject: Re: Linux 3.8-rc4
>>>
>>> On Tue, Jan 29, 2013 at 1:13 PM, Deucher, Alexander
>>> <Alexander.Deucher@amd.com> wrote:
>>> >> -----Original Message-----
>>> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>>> >> Sent: Tuesday, January 29, 2013 2:11 PM
>>> >> To: Deucher, Alexander
>>> >> Cc: Linus Torvalds; Linux Kernel Mailing List
>>> >> Subject: Re: Linux 3.8-rc4
>>> >>
>>> >> On Tue, Jan 29, 2013 at 6:05 AM, Deucher, Alexander
>>> >> <Alexander.Deucher@amd.com> wrote:
>>> >> >> -----Original Message-----
>>> >> >> I was out sick for a few days and finally picked this bisect backup
>>> >> >> again. I started at 3.7 tag instead of 3.8-rc1 that I did in the past
>>> >> >> and also did bisect at drivers/gpu/drm/radeon instead. Here are the
>>> >> >> results:
>>> >> >>
>>> >> >> 6253e4c75d96006c06b9ac8f417eba873de2497b is the first bad commit
>>> >> >> commit 6253e4c75d96006c06b9ac8f417eba873de2497b
>>> >> >> Author: Alex Deucher <alexander.deucher@amd.com>
>>> >> >> Date: Wed Dec 12 14:30:32 2012 -0500
>>> >> >>
>>> >> >> drm/radeon: improve mc_stop/mc_resume on r5xx-r7xx
>>> >> >>
>>> >> >> Along the same lines of what was done for evergreen+
>>> >> >> in the last kernel.
>>> >> >>
>>> >> >> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>>> >> >>
>>> >> >> git bisect log attached.
>>> >> >>
>>> >> >
>>> >> > Try the attached patch. I think it should fix the issue. I just applied a
>>> similar
>>> >> patch for newer asics.
>>> >> >
>>> >> > Alex
>>> >> >
>>> >>
>>> >> I reverted 6253e4c75d96006c06b9ac8f417eba873de2497b and DMAR
>>> faults
>>> >> went away. Undid the revert and applied your new patch. DMAR faults
>>> >> are back again.
>>> >>
>>> >>
>>> >> [ 25.158653] [drm] PCIE GART of 512M enabled (table at
>>> >> 0x0000000000040000).
>>> >> [ 25.158715] radeon 0000:01:00.0: WB enabled
>>> >> [ 25.158719] radeon 0000:01:00.0: fence driver on ring 0 use gpu
>>> >> addr 0x0000000008000c00 and cpu addr 0xffff88002f143c00
>>> >> [ 25.158721] radeon 0000:01:00.0: fence driver on ring 3 use gpu
>>> >> addr 0x0000000008000c0c and cpu addr 0xffff88002f143c0c
>>> >>
>>> >> A few observations and questions about r600_startup() code sequence:
>>> >>
>>> >> I notice DMAR faults right after
>>> >>
>>> >> [drm] Loading RV620 Microcode message which is from
>>> >> r600_init_microcode(). This routine does a series of
>>> >> request_firmware() calls. btw. don't see release_firmware() calls in
>>> >> regular code path, only from error legs in r600_init_microcode().
>>> >>
>>> >> However, this routine doesn't do any loading yet. When this routine
>>> >> returns, I am assuming request_firmware() step isn't complete yet
>>> >> based on my reading request_firmware() interface. At this point
>>> >> r600_startup() keeps chugging along, and does r600_mc_program() which
>>> >> in turn calls rv515_mc_stop() which was changed with the
>>> >> 6253e4c75d96006c06b9ac8f417eba873de2497b commit.
>>> >>
>>> >> I am thinking the changes somehow eliminated a wait or delay that used
>>> >> be there for request_firmware() step to complete (?)
>>> >>
>>> >> I can see from dmesg that the faults occur right after:
>>> >>
>>> >> r600_init_microcode(rdev);
>>> >>
>>> >> and stop before r600_pcie_gart_enable()
>>> >
>>> > r600_init_microcode() doesn't actually touch the hardware it just calls
>>> request_firmware() to fetch the microcode images from disk. The microcode
>>> doesn't get loaded onto the hardware until r600_cp_load_microcode() much
>>> later in the function. I don't think the microcode has anything to do with this.
>>> >
>>> > rv515_mc_stop() stops GPU memory clients (e.g., the displays) and blacks
>>> out the GPU memory controller so that we can change the location of VRAM
>>> within the GPU's address space. If one of the display controllers memory
>>> request stop requests takes too long to go through for some reason, it's
>>> possible that the display hardware may attempt to read from a GPU memory
>>> location no-longer backed by vram (since we changed the location of vram in
>>> r600_mc_program()) momentarily until the stop request goes through. Does
>>> the attached updated version of the patch help? Alternatively, you can try
>>> adding delays to the end of rv515_mc_stop() and see if that helps.
>>> >
>>> > Alex
>>> >
>>>
>>> This v2 patch didn't help. I added mdelay(15); at the end of
>>> rv515_mc_stop() on top of this v2 patch and that fixed the problem.
>>> mdelay(15) is a bit much I am sure. Shouldn't rv515_mc_wait_for_idle()
>>> take care of the delay? It waits for idle usec_timeout?
>>
>>
>> It only waits that long if the MC never goes idle. If the MC happens to be idle at the time, it will return immediately. Does the attached patch fix the issue? It waits for the update pending bit to clear in addition to waiting for the next frame.
>>
>> Alex
>>
>
> No. This patch didn't fix the problem.
>
> -- Shuah
ok. I did more debugging in rv515_mc_stop() and here is what's
happening. It has two display controllers and one of them is enabled
and the other is in disabled state when AVIVO_D1CRTC_CONTROL is
checked. The current code doesn't blank the disabled crtc. However, it
needs to be blanked to avoid DMAR faults it appears. I think that is
what the original code prior to
6253e4c75d96006c06b9ac8f417eba873de2497b commit was doing:
- WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 1);
- WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 1);
- WREG32(R_006080_D1CRTC_CONTROL, 0);
- WREG32(R_006880_D2CRTC_CONTROL, 0);
- WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 0);
- WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 0);
- WREG32(R_000330_D1VGA_CONTROL, 0);
- WREG32(R_000338_D2VGA_CONTROL, 0);
Anyways, here is the diff for the change (by no means a patch) I made
that fixed the problem:
diff --git a/drivers/gpu/drm/radeon/rv515.c b/drivers/gpu/drm/radeon/rv515.c
index 2bb6d0e..29ac184 100644
--- a/drivers/gpu/drm/radeon/rv515.c
+++ b/drivers/gpu/drm/radeon/rv515.c
@@ -298,6 +298,10 @@ void rv515_mc_stop(struct radeon_device *rdev, struct rv515
/* blank the display controllers */
for (i = 0; i < rdev->num_crtc; i++) {
crtc_enabled = RREG32(AVIVO_D1CRTC_CONTROL + crtc_offsets[i]) &
+ dev_info(rdev->dev, "num_crtc = %d crtc_enabled %d for %d.\n",
+ rdev->num_crtc, crtc_enabled, i);
+ crtc_enabled = 1;
+
if (crtc_enabled) {
save->crtc_enabled[i] = true;
tmp = RREG32(AVIVO_D1CRTC_CONTROL + crtc_offsets[i]);
-- Shuah
^ permalink raw reply related [flat|nested] 30+ messages in thread
* RE: Linux 3.8-rc4
2013-01-30 2:38 ` Shuah Khan
@ 2013-01-30 13:31 ` Deucher, Alexander
2013-01-30 15:35 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Deucher, Alexander @ 2013-01-30 13:31 UTC (permalink / raw)
To: Shuah Khan; +Cc: Linus Torvalds, Linux Kernel Mailing List
> -----Original Message-----
> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> Sent: Tuesday, January 29, 2013 9:38 PM
> To: Deucher, Alexander
> Cc: Linus Torvalds; Linux Kernel Mailing List
> Subject: Re: Linux 3.8-rc4
>
> On Tue, Jan 29, 2013 at 4:45 PM, Shuah Khan <shuahkhan@gmail.com>
> wrote:
> > On Tue, Jan 29, 2013 at 3:02 PM, Deucher, Alexander
> > <Alexander.Deucher@amd.com> wrote:
> >>> -----Original Message-----
> >>> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> >>> Sent: Tuesday, January 29, 2013 4:40 PM
> >>> To: Deucher, Alexander
> >>> Cc: Linus Torvalds; Linux Kernel Mailing List
> >>> Subject: Re: Linux 3.8-rc4
> >>>
> >>> On Tue, Jan 29, 2013 at 1:13 PM, Deucher, Alexander
> >>> <Alexander.Deucher@amd.com> wrote:
> >>> >> -----Original Message-----
> >>> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> >>> >> Sent: Tuesday, January 29, 2013 2:11 PM
> >>> >> To: Deucher, Alexander
> >>> >> Cc: Linus Torvalds; Linux Kernel Mailing List
> >>> >> Subject: Re: Linux 3.8-rc4
> >>> >>
> >>> >> On Tue, Jan 29, 2013 at 6:05 AM, Deucher, Alexander
> >>> >> <Alexander.Deucher@amd.com> wrote:
> >>> >> >> -----Original Message-----
> >>> >> >> I was out sick for a few days and finally picked this bisect backup
> >>> >> >> again. I started at 3.7 tag instead of 3.8-rc1 that I did in the past
> >>> >> >> and also did bisect at drivers/gpu/drm/radeon instead. Here are
> the
> >>> >> >> results:
> >>> >> >>
> >>> >> >> 6253e4c75d96006c06b9ac8f417eba873de2497b is the first bad
> commit
> >>> >> >> commit 6253e4c75d96006c06b9ac8f417eba873de2497b
> >>> >> >> Author: Alex Deucher <alexander.deucher@amd.com>
> >>> >> >> Date: Wed Dec 12 14:30:32 2012 -0500
> >>> >> >>
> >>> >> >> drm/radeon: improve mc_stop/mc_resume on r5xx-r7xx
> >>> >> >>
> >>> >> >> Along the same lines of what was done for evergreen+
> >>> >> >> in the last kernel.
> >>> >> >>
> >>> >> >> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
> >>> >> >>
> >>> >> >> git bisect log attached.
> >>> >> >>
> >>> >> >
> >>> >> > Try the attached patch. I think it should fix the issue. I just applied
> a
> >>> similar
> >>> >> patch for newer asics.
> >>> >> >
> >>> >> > Alex
> >>> >> >
> >>> >>
> >>> >> I reverted 6253e4c75d96006c06b9ac8f417eba873de2497b and DMAR
> >>> faults
> >>> >> went away. Undid the revert and applied your new patch. DMAR
> faults
> >>> >> are back again.
> >>> >>
> >>> >>
> >>> >> [ 25.158653] [drm] PCIE GART of 512M enabled (table at
> >>> >> 0x0000000000040000).
> >>> >> [ 25.158715] radeon 0000:01:00.0: WB enabled
> >>> >> [ 25.158719] radeon 0000:01:00.0: fence driver on ring 0 use gpu
> >>> >> addr 0x0000000008000c00 and cpu addr 0xffff88002f143c00
> >>> >> [ 25.158721] radeon 0000:01:00.0: fence driver on ring 3 use gpu
> >>> >> addr 0x0000000008000c0c and cpu addr 0xffff88002f143c0c
> >>> >>
> >>> >> A few observations and questions about r600_startup() code
> sequence:
> >>> >>
> >>> >> I notice DMAR faults right after
> >>> >>
> >>> >> [drm] Loading RV620 Microcode message which is from
> >>> >> r600_init_microcode(). This routine does a series of
> >>> >> request_firmware() calls. btw. don't see release_firmware() calls in
> >>> >> regular code path, only from error legs in r600_init_microcode().
> >>> >>
> >>> >> However, this routine doesn't do any loading yet. When this routine
> >>> >> returns, I am assuming request_firmware() step isn't complete yet
> >>> >> based on my reading request_firmware() interface. At this point
> >>> >> r600_startup() keeps chugging along, and does r600_mc_program()
> which
> >>> >> in turn calls rv515_mc_stop() which was changed with the
> >>> >> 6253e4c75d96006c06b9ac8f417eba873de2497b commit.
> >>> >>
> >>> >> I am thinking the changes somehow eliminated a wait or delay that
> used
> >>> >> be there for request_firmware() step to complete (?)
> >>> >>
> >>> >> I can see from dmesg that the faults occur right after:
> >>> >>
> >>> >> r600_init_microcode(rdev);
> >>> >>
> >>> >> and stop before r600_pcie_gart_enable()
> >>> >
> >>> > r600_init_microcode() doesn't actually touch the hardware it just calls
> >>> request_firmware() to fetch the microcode images from disk. The
> microcode
> >>> doesn't get loaded onto the hardware until r600_cp_load_microcode()
> much
> >>> later in the function. I don't think the microcode has anything to do with
> this.
> >>> >
> >>> > rv515_mc_stop() stops GPU memory clients (e.g., the displays) and
> blacks
> >>> out the GPU memory controller so that we can change the location of
> VRAM
> >>> within the GPU's address space. If one of the display controllers
> memory
> >>> request stop requests takes too long to go through for some reason, it's
> >>> possible that the display hardware may attempt to read from a GPU
> memory
> >>> location no-longer backed by vram (since we changed the location of
> vram in
> >>> r600_mc_program()) momentarily until the stop request goes through.
> Does
> >>> the attached updated version of the patch help? Alternatively, you can
> try
> >>> adding delays to the end of rv515_mc_stop() and see if that helps.
> >>> >
> >>> > Alex
> >>> >
> >>>
> >>> This v2 patch didn't help. I added mdelay(15); at the end of
> >>> rv515_mc_stop() on top of this v2 patch and that fixed the problem.
> >>> mdelay(15) is a bit much I am sure. Shouldn't rv515_mc_wait_for_idle()
> >>> take care of the delay? It waits for idle usec_timeout?
> >>
> >>
> >> It only waits that long if the MC never goes idle. If the MC happens to be
> idle at the time, it will return immediately. Does the attached patch fix the
> issue? It waits for the update pending bit to clear in addition to waiting for
> the next frame.
> >>
> >> Alex
> >>
> >
> > No. This patch didn't fix the problem.
> >
> > -- Shuah
>
> ok. I did more debugging in rv515_mc_stop() and here is what's
> happening. It has two display controllers and one of them is enabled
> and the other is in disabled state when AVIVO_D1CRTC_CONTROL is
> checked. The current code doesn't blank the disabled crtc. However, it
> needs to be blanked to avoid DMAR faults it appears. I think that is
> what the original code prior to
> 6253e4c75d96006c06b9ac8f417eba873de2497b commit was doing:
>
> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 1);
> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 1);
> - WREG32(R_006080_D1CRTC_CONTROL, 0);
> - WREG32(R_006880_D2CRTC_CONTROL, 0);
> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 0);
> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 0);
> - WREG32(R_000330_D1VGA_CONTROL, 0);
> - WREG32(R_000338_D2VGA_CONTROL, 0);
>
> Anyways, here is the diff for the change (by no means a patch) I made
> that fixed the problem:
Unfortunately, that just fixes the problem by causing an additional delay since the wait_for_vblank() and get_frame_count() loops will timeout since the secondary display is disabled. The previous code disabled the displays completely while the new code just disables the memory request interface so that the display timing stays on to avoid additional flicker at startup or GPU reset. For some reason on your system there seems to be a delay in getting the memory request interface to stop.
Alex
>
> diff --git a/drivers/gpu/drm/radeon/rv515.c
> b/drivers/gpu/drm/radeon/rv515.c
> index 2bb6d0e..29ac184 100644
> --- a/drivers/gpu/drm/radeon/rv515.c
> +++ b/drivers/gpu/drm/radeon/rv515.c
> @@ -298,6 +298,10 @@ void rv515_mc_stop(struct radeon_device *rdev,
> struct rv515
> /* blank the display controllers */
> for (i = 0; i < rdev->num_crtc; i++) {
> crtc_enabled = RREG32(AVIVO_D1CRTC_CONTROL + crtc_offsets[i])
> &
> + dev_info(rdev->dev, "num_crtc = %d crtc_enabled %d for %d.\n",
> + rdev->num_crtc, crtc_enabled, i);
> + crtc_enabled = 1;
> +
> if (crtc_enabled) {
> save->crtc_enabled[i] = true;
> tmp = RREG32(AVIVO_D1CRTC_CONTROL + crtc_offsets[i]);
>
> -- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-30 13:31 ` Deucher, Alexander
@ 2013-01-30 15:35 ` Shuah Khan
2013-01-30 15:53 ` Deucher, Alexander
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-30 15:35 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
On Wed, Jan 30, 2013 at 6:31 AM, Deucher, Alexander
<Alexander.Deucher@amd.com> wrote:
>>
>> ok. I did more debugging in rv515_mc_stop() and here is what's
>> happening. It has two display controllers and one of them is enabled
>> and the other is in disabled state when AVIVO_D1CRTC_CONTROL is
>> checked. The current code doesn't blank the disabled crtc. However, it
>> needs to be blanked to avoid DMAR faults it appears. I think that is
>> what the original code prior to
>> 6253e4c75d96006c06b9ac8f417eba873de2497b commit was doing:
>>
>> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 1);
>> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 1);
>> - WREG32(R_006080_D1CRTC_CONTROL, 0);
>> - WREG32(R_006880_D2CRTC_CONTROL, 0);
>> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 0);
>> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 0);
>> - WREG32(R_000330_D1VGA_CONTROL, 0);
>> - WREG32(R_000338_D2VGA_CONTROL, 0);
>>
>> Anyways, here is the diff for the change (by no means a patch) I made
>> that fixed the problem:
>
> Unfortunately, that just fixes the problem by causing an additional delay since the wait_for_vblank() and get_frame_count() loops will timeout since the secondary display is disabled. The previous code disabled the displays completely while the new code just disables the memory request interface so that the display timing stays on to avoid additional flicker at startup or GPU reset. For some reason on your system there seems to be a delay in getting the memory request interface to stop.
>
> Alex
Right. That makes sense and yes the annoying flicker went away. :) Can
you think of something that can address systems that would need more
time to get the memory request interface to stop such as mine?
-- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: Linux 3.8-rc4
2013-01-30 15:35 ` Shuah Khan
@ 2013-01-30 15:53 ` Deucher, Alexander
2013-01-30 21:12 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Deucher, Alexander @ 2013-01-30 15:53 UTC (permalink / raw)
To: Shuah Khan; +Cc: Linus Torvalds, Linux Kernel Mailing List
> -----Original Message-----
> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> Sent: Wednesday, January 30, 2013 10:35 AM
> To: Deucher, Alexander
> Cc: Linus Torvalds; Linux Kernel Mailing List
> Subject: Re: Linux 3.8-rc4
>
> On Wed, Jan 30, 2013 at 6:31 AM, Deucher, Alexander
> <Alexander.Deucher@amd.com> wrote:
>
> >>
> >> ok. I did more debugging in rv515_mc_stop() and here is what's
> >> happening. It has two display controllers and one of them is enabled
> >> and the other is in disabled state when AVIVO_D1CRTC_CONTROL is
> >> checked. The current code doesn't blank the disabled crtc. However, it
> >> needs to be blanked to avoid DMAR faults it appears. I think that is
> >> what the original code prior to
> >> 6253e4c75d96006c06b9ac8f417eba873de2497b commit was doing:
> >>
> >> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 1);
> >> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 1);
> >> - WREG32(R_006080_D1CRTC_CONTROL, 0);
> >> - WREG32(R_006880_D2CRTC_CONTROL, 0);
> >> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 0);
> >> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 0);
> >> - WREG32(R_000330_D1VGA_CONTROL, 0);
> >> - WREG32(R_000338_D2VGA_CONTROL, 0);
> >>
> >> Anyways, here is the diff for the change (by no means a patch) I made
> >> that fixed the problem:
> >
> > Unfortunately, that just fixes the problem by causing an additional delay
> since the wait_for_vblank() and get_frame_count() loops will timeout since
> the secondary display is disabled. The previous code disabled the displays
> completely while the new code just disables the memory request interface
> so that the display timing stays on to avoid additional flicker at startup or GPU
> reset. For some reason on your system there seems to be a delay in getting
> the memory request interface to stop.
> >
> > Alex
>
> Right. That makes sense and yes the annoying flicker went away. :) Can
> you think of something that can address systems that would need more
> time to get the memory request interface to stop such as mine?
Does adding an additional radeon_mc_wait_for_idle(rdev) call at the end of rv515_mc_stop() help? Can you find out what the minimum delay required for your system is?
Alex
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-30 15:53 ` Deucher, Alexander
@ 2013-01-30 21:12 ` Shuah Khan
2013-01-31 14:56 ` Deucher, Alexander
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-30 21:12 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
On Wed, Jan 30, 2013 at 8:53 AM, Deucher, Alexander
<Alexander.Deucher@amd.com> wrote:
>> -----Original Message-----
>> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> Sent: Wednesday, January 30, 2013 10:35 AM
>> To: Deucher, Alexander
>> Cc: Linus Torvalds; Linux Kernel Mailing List
>> Subject: Re: Linux 3.8-rc4
>>
>> On Wed, Jan 30, 2013 at 6:31 AM, Deucher, Alexander
>> <Alexander.Deucher@amd.com> wrote:
>>
>> >>
>> >> ok. I did more debugging in rv515_mc_stop() and here is what's
>> >> happening. It has two display controllers and one of them is enabled
>> >> and the other is in disabled state when AVIVO_D1CRTC_CONTROL is
>> >> checked. The current code doesn't blank the disabled crtc. However, it
>> >> needs to be blanked to avoid DMAR faults it appears. I think that is
>> >> what the original code prior to
>> >> 6253e4c75d96006c06b9ac8f417eba873de2497b commit was doing:
>> >>
>> >> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 1);
>> >> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 1);
>> >> - WREG32(R_006080_D1CRTC_CONTROL, 0);
>> >> - WREG32(R_006880_D2CRTC_CONTROL, 0);
>> >> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 0);
>> >> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 0);
>> >> - WREG32(R_000330_D1VGA_CONTROL, 0);
>> >> - WREG32(R_000338_D2VGA_CONTROL, 0);
>> >>
>> >> Anyways, here is the diff for the change (by no means a patch) I made
>> >> that fixed the problem:
>> >
>> > Unfortunately, that just fixes the problem by causing an additional delay
>> since the wait_for_vblank() and get_frame_count() loops will timeout since
>> the secondary display is disabled. The previous code disabled the displays
>> completely while the new code just disables the memory request interface
>> so that the display timing stays on to avoid additional flicker at startup or GPU
>> reset. For some reason on your system there seems to be a delay in getting
>> the memory request interface to stop.
>> >
>> > Alex
>>
>> Right. That makes sense and yes the annoying flicker went away. :) Can
>> you think of something that can address systems that would need more
>> time to get the memory request interface to stop such as mine?
>
> Does adding an additional radeon_mc_wait_for_idle(rdev) call at the end of rv515_mc_stop() help? Can you find out what the minimum delay required for your system is?
>
> Alex
Adding radeon_mc_wait_for_idle(rdev) call at the end of
rv515_mc_stop() - didn't help.
I tried with adding udelay() with delay values of 1,10, and 50, and
100 at the end of rv515_mc_stop(). 100 is the minimum that fixed the
DMAR faults.
-- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: Linux 3.8-rc4
2013-01-30 21:12 ` Shuah Khan
@ 2013-01-31 14:56 ` Deucher, Alexander
2013-01-31 16:01 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Deucher, Alexander @ 2013-01-31 14:56 UTC (permalink / raw)
To: Shuah Khan; +Cc: Linus Torvalds, Linux Kernel Mailing List
> -----Original Message-----
> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> Sent: Wednesday, January 30, 2013 4:12 PM
> To: Deucher, Alexander
> Cc: Linus Torvalds; Linux Kernel Mailing List
> Subject: Re: Linux 3.8-rc4
>
> On Wed, Jan 30, 2013 at 8:53 AM, Deucher, Alexander
> <Alexander.Deucher@amd.com> wrote:
> >> -----Original Message-----
> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> >> Sent: Wednesday, January 30, 2013 10:35 AM
> >> To: Deucher, Alexander
> >> Cc: Linus Torvalds; Linux Kernel Mailing List
> >> Subject: Re: Linux 3.8-rc4
> >>
> >> On Wed, Jan 30, 2013 at 6:31 AM, Deucher, Alexander
> >> <Alexander.Deucher@amd.com> wrote:
> >>
> >> >>
> >> >> ok. I did more debugging in rv515_mc_stop() and here is what's
> >> >> happening. It has two display controllers and one of them is enabled
> >> >> and the other is in disabled state when AVIVO_D1CRTC_CONTROL is
> >> >> checked. The current code doesn't blank the disabled crtc. However, it
> >> >> needs to be blanked to avoid DMAR faults it appears. I think that is
> >> >> what the original code prior to
> >> >> 6253e4c75d96006c06b9ac8f417eba873de2497b commit was doing:
> >> >>
> >> >> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 1);
> >> >> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 1);
> >> >> - WREG32(R_006080_D1CRTC_CONTROL, 0);
> >> >> - WREG32(R_006880_D2CRTC_CONTROL, 0);
> >> >> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 0);
> >> >> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 0);
> >> >> - WREG32(R_000330_D1VGA_CONTROL, 0);
> >> >> - WREG32(R_000338_D2VGA_CONTROL, 0);
> >> >>
> >> >> Anyways, here is the diff for the change (by no means a patch) I made
> >> >> that fixed the problem:
> >> >
> >> > Unfortunately, that just fixes the problem by causing an additional delay
> >> since the wait_for_vblank() and get_frame_count() loops will timeout
> since
> >> the secondary display is disabled. The previous code disabled the displays
> >> completely while the new code just disables the memory request
> interface
> >> so that the display timing stays on to avoid additional flicker at startup or
> GPU
> >> reset. For some reason on your system there seems to be a delay in
> getting
> >> the memory request interface to stop.
> >> >
> >> > Alex
> >>
> >> Right. That makes sense and yes the annoying flicker went away. :) Can
> >> you think of something that can address systems that would need more
> >> time to get the memory request interface to stop such as mine?
> >
> > Does adding an additional radeon_mc_wait_for_idle(rdev) call at the end
> of rv515_mc_stop() help? Can you find out what the minimum delay
> required for your system is?
> >
> > Alex
>
> Adding radeon_mc_wait_for_idle(rdev) call at the end of
> rv515_mc_stop() - didn't help.
>
> I tried with adding udelay() with delay values of 1,10, and 50, and
> 100 at the end of rv515_mc_stop(). 100 is the minimum that fixed the
> DMAR faults.
I guess we can just add the delay. I've tried all the ways I know of to get proper feedback from the hardware.
Alex
^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-31 14:56 ` Deucher, Alexander
@ 2013-01-31 16:01 ` Shuah Khan
2013-01-31 16:05 ` Deucher, Alexander
0 siblings, 1 reply; 30+ messages in thread
From: Shuah Khan @ 2013-01-31 16:01 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
On Thu, Jan 31, 2013 at 7:56 AM, Deucher, Alexander
<Alexander.Deucher@amd.com> wrote:
>> -----Original Message-----
>> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> Sent: Wednesday, January 30, 2013 4:12 PM
>> To: Deucher, Alexander
>> Cc: Linus Torvalds; Linux Kernel Mailing List
>> Subject: Re: Linux 3.8-rc4
>>
>> On Wed, Jan 30, 2013 at 8:53 AM, Deucher, Alexander
>> <Alexander.Deucher@amd.com> wrote:
>> >> -----Original Message-----
>> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> >> Sent: Wednesday, January 30, 2013 10:35 AM
>> >> To: Deucher, Alexander
>> >> Cc: Linus Torvalds; Linux Kernel Mailing List
>> >> Subject: Re: Linux 3.8-rc4
>> >>
>> >> On Wed, Jan 30, 2013 at 6:31 AM, Deucher, Alexander
>> >> <Alexander.Deucher@amd.com> wrote:
>> >>
>> >> >>
>> >> >> ok. I did more debugging in rv515_mc_stop() and here is what's
>> >> >> happening. It has two display controllers and one of them is enabled
>> >> >> and the other is in disabled state when AVIVO_D1CRTC_CONTROL is
>> >> >> checked. The current code doesn't blank the disabled crtc. However, it
>> >> >> needs to be blanked to avoid DMAR faults it appears. I think that is
>> >> >> what the original code prior to
>> >> >> 6253e4c75d96006c06b9ac8f417eba873de2497b commit was doing:
>> >> >>
>> >> >> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 1);
>> >> >> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 1);
>> >> >> - WREG32(R_006080_D1CRTC_CONTROL, 0);
>> >> >> - WREG32(R_006880_D2CRTC_CONTROL, 0);
>> >> >> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 0);
>> >> >> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 0);
>> >> >> - WREG32(R_000330_D1VGA_CONTROL, 0);
>> >> >> - WREG32(R_000338_D2VGA_CONTROL, 0);
>> >> >>
>> >> >> Anyways, here is the diff for the change (by no means a patch) I made
>> >> >> that fixed the problem:
>> >> >
>> >> > Unfortunately, that just fixes the problem by causing an additional delay
>> >> since the wait_for_vblank() and get_frame_count() loops will timeout
>> since
>> >> the secondary display is disabled. The previous code disabled the displays
>> >> completely while the new code just disables the memory request
>> interface
>> >> so that the display timing stays on to avoid additional flicker at startup or
>> GPU
>> >> reset. For some reason on your system there seems to be a delay in
>> getting
>> >> the memory request interface to stop.
>> >> >
>> >> > Alex
>> >>
>> >> Right. That makes sense and yes the annoying flicker went away. :) Can
>> >> you think of something that can address systems that would need more
>> >> time to get the memory request interface to stop such as mine?
>> >
>> > Does adding an additional radeon_mc_wait_for_idle(rdev) call at the end
>> of rv515_mc_stop() help? Can you find out what the minimum delay
>> required for your system is?
>> >
>> > Alex
>>
>> Adding radeon_mc_wait_for_idle(rdev) call at the end of
>> rv515_mc_stop() - didn't help.
>>
>> I tried with adding udelay() with delay values of 1,10, and 50, and
>> 100 at the end of rv515_mc_stop(). 100 is the minimum that fixed the
>> DMAR faults.
>
> I guess we can just add the delay. I've tried all the ways I know of to get proper feedback from the hardware.
>
> Alex
>
Do you want me to send a patch with delay()? Would you like to see the
delay specific to this chipset which is RV620? That said if you think
of other ideas to try instead of delay, I can continue the debug and
testing effort.
-- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
* RE: Linux 3.8-rc4
2013-01-31 16:01 ` Shuah Khan
@ 2013-01-31 16:05 ` Deucher, Alexander
2013-01-31 16:47 ` Shuah Khan
0 siblings, 1 reply; 30+ messages in thread
From: Deucher, Alexander @ 2013-01-31 16:05 UTC (permalink / raw)
To: Shuah Khan; +Cc: Linus Torvalds, Linux Kernel Mailing List
[-- Attachment #1: Type: text/plain, Size: 4077 bytes --]
> -----Original Message-----
> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> Sent: Thursday, January 31, 2013 11:01 AM
> To: Deucher, Alexander
> Cc: Linus Torvalds; Linux Kernel Mailing List
> Subject: Re: Linux 3.8-rc4
>
> On Thu, Jan 31, 2013 at 7:56 AM, Deucher, Alexander
> <Alexander.Deucher@amd.com> wrote:
> >> -----Original Message-----
> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> >> Sent: Wednesday, January 30, 2013 4:12 PM
> >> To: Deucher, Alexander
> >> Cc: Linus Torvalds; Linux Kernel Mailing List
> >> Subject: Re: Linux 3.8-rc4
> >>
> >> On Wed, Jan 30, 2013 at 8:53 AM, Deucher, Alexander
> >> <Alexander.Deucher@amd.com> wrote:
> >> >> -----Original Message-----
> >> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
> >> >> Sent: Wednesday, January 30, 2013 10:35 AM
> >> >> To: Deucher, Alexander
> >> >> Cc: Linus Torvalds; Linux Kernel Mailing List
> >> >> Subject: Re: Linux 3.8-rc4
> >> >>
> >> >> On Wed, Jan 30, 2013 at 6:31 AM, Deucher, Alexander
> >> >> <Alexander.Deucher@amd.com> wrote:
> >> >>
> >> >> >>
> >> >> >> ok. I did more debugging in rv515_mc_stop() and here is what's
> >> >> >> happening. It has two display controllers and one of them is
> enabled
> >> >> >> and the other is in disabled state when AVIVO_D1CRTC_CONTROL
> is
> >> >> >> checked. The current code doesn't blank the disabled crtc.
> However, it
> >> >> >> needs to be blanked to avoid DMAR faults it appears. I think that is
> >> >> >> what the original code prior to
> >> >> >> 6253e4c75d96006c06b9ac8f417eba873de2497b commit was doing:
> >> >> >>
> >> >> >> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 1);
> >> >> >> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 1);
> >> >> >> - WREG32(R_006080_D1CRTC_CONTROL, 0);
> >> >> >> - WREG32(R_006880_D2CRTC_CONTROL, 0);
> >> >> >> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 0);
> >> >> >> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 0);
> >> >> >> - WREG32(R_000330_D1VGA_CONTROL, 0);
> >> >> >> - WREG32(R_000338_D2VGA_CONTROL, 0);
> >> >> >>
> >> >> >> Anyways, here is the diff for the change (by no means a patch) I
> made
> >> >> >> that fixed the problem:
> >> >> >
> >> >> > Unfortunately, that just fixes the problem by causing an additional
> delay
> >> >> since the wait_for_vblank() and get_frame_count() loops will timeout
> >> since
> >> >> the secondary display is disabled. The previous code disabled the
> displays
> >> >> completely while the new code just disables the memory request
> >> interface
> >> >> so that the display timing stays on to avoid additional flicker at startup
> or
> >> GPU
> >> >> reset. For some reason on your system there seems to be a delay in
> >> getting
> >> >> the memory request interface to stop.
> >> >> >
> >> >> > Alex
> >> >>
> >> >> Right. That makes sense and yes the annoying flicker went away. :) Can
> >> >> you think of something that can address systems that would need
> more
> >> >> time to get the memory request interface to stop such as mine?
> >> >
> >> > Does adding an additional radeon_mc_wait_for_idle(rdev) call at the
> end
> >> of rv515_mc_stop() help? Can you find out what the minimum delay
> >> required for your system is?
> >> >
> >> > Alex
> >>
> >> Adding radeon_mc_wait_for_idle(rdev) call at the end of
> >> rv515_mc_stop() - didn't help.
> >>
> >> I tried with adding udelay() with delay values of 1,10, and 50, and
> >> 100 at the end of rv515_mc_stop(). 100 is the minimum that fixed the
> >> DMAR faults.
> >
> > I guess we can just add the delay. I've tried all the ways I know of to get
> proper feedback from the hardware.
> >
> > Alex
> >
>
> Do you want me to send a patch with delay()? Would you like to see the
> delay specific to this chipset which is RV620? That said if you think
> of other ideas to try instead of delay, I can continue the debug and
> testing effort.
I'm planning to merge the attached patch. I'll let you know if I found out any other things to try.
Alex
[-- Attachment #2: 0001-drm-radeon-r5xx-r7xx-wait-for-the-MC-to-settle-after.patch --]
[-- Type: application/octet-stream, Size: 1010 bytes --]
From 01d0ec41cdd30d9ce08f228f950a5e9db8cf386f Mon Sep 17 00:00:00 2001
From: Alex Deucher <alexander.deucher@amd.com>
Date: Thu, 31 Jan 2013 09:01:59 -0500
Subject: [PATCH] drm/radeon/r5xx-r7xx: wait for the MC to settle after MC
blackout
Some chips seem to need a little delay after blacking out
the MC before the requests actually stop.
Reported-by: Shuah Khan <shuahkhan@gmail.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
---
drivers/gpu/drm/radeon/rv515.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/radeon/rv515.c b/drivers/gpu/drm/radeon/rv515.c
index 2bb6d0e..435ed35 100644
--- a/drivers/gpu/drm/radeon/rv515.c
+++ b/drivers/gpu/drm/radeon/rv515.c
@@ -336,6 +336,8 @@ void rv515_mc_stop(struct radeon_device *rdev, struct rv515_mc_save *save)
WREG32(R600_CITF_CNTL, blackout);
}
}
+ /* wait for the MC to settle */
+ udelay(100);
}
void rv515_mc_resume(struct radeon_device *rdev, struct rv515_mc_save *save)
--
1.7.7.5
^ permalink raw reply related [flat|nested] 30+ messages in thread
* Re: Linux 3.8-rc4
2013-01-31 16:05 ` Deucher, Alexander
@ 2013-01-31 16:47 ` Shuah Khan
0 siblings, 0 replies; 30+ messages in thread
From: Shuah Khan @ 2013-01-31 16:47 UTC (permalink / raw)
To: Deucher, Alexander; +Cc: Linus Torvalds, Linux Kernel Mailing List
On Thu, Jan 31, 2013 at 9:05 AM, Deucher, Alexander
<Alexander.Deucher@amd.com> wrote:
>> -----Original Message-----
>> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> Sent: Thursday, January 31, 2013 11:01 AM
>> To: Deucher, Alexander
>> Cc: Linus Torvalds; Linux Kernel Mailing List
>> Subject: Re: Linux 3.8-rc4
>>
>> On Thu, Jan 31, 2013 at 7:56 AM, Deucher, Alexander
>> <Alexander.Deucher@amd.com> wrote:
>> >> -----Original Message-----
>> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> >> Sent: Wednesday, January 30, 2013 4:12 PM
>> >> To: Deucher, Alexander
>> >> Cc: Linus Torvalds; Linux Kernel Mailing List
>> >> Subject: Re: Linux 3.8-rc4
>> >>
>> >> On Wed, Jan 30, 2013 at 8:53 AM, Deucher, Alexander
>> >> <Alexander.Deucher@amd.com> wrote:
>> >> >> -----Original Message-----
>> >> >> From: Shuah Khan [mailto:shuahkhan@gmail.com]
>> >> >> Sent: Wednesday, January 30, 2013 10:35 AM
>> >> >> To: Deucher, Alexander
>> >> >> Cc: Linus Torvalds; Linux Kernel Mailing List
>> >> >> Subject: Re: Linux 3.8-rc4
>> >> >>
>> >> >> On Wed, Jan 30, 2013 at 6:31 AM, Deucher, Alexander
>> >> >> <Alexander.Deucher@amd.com> wrote:
>> >> >>
>> >> >> >>
>> >> >> >> ok. I did more debugging in rv515_mc_stop() and here is what's
>> >> >> >> happening. It has two display controllers and one of them is
>> enabled
>> >> >> >> and the other is in disabled state when AVIVO_D1CRTC_CONTROL
>> is
>> >> >> >> checked. The current code doesn't blank the disabled crtc.
>> However, it
>> >> >> >> needs to be blanked to avoid DMAR faults it appears. I think that is
>> >> >> >> what the original code prior to
>> >> >> >> 6253e4c75d96006c06b9ac8f417eba873de2497b commit was doing:
>> >> >> >>
>> >> >> >> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 1);
>> >> >> >> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 1);
>> >> >> >> - WREG32(R_006080_D1CRTC_CONTROL, 0);
>> >> >> >> - WREG32(R_006880_D2CRTC_CONTROL, 0);
>> >> >> >> - WREG32(R_0060E8_D1CRTC_UPDATE_LOCK, 0);
>> >> >> >> - WREG32(R_0068E8_D2CRTC_UPDATE_LOCK, 0);
>> >> >> >> - WREG32(R_000330_D1VGA_CONTROL, 0);
>> >> >> >> - WREG32(R_000338_D2VGA_CONTROL, 0);
>> >> >> >>
>> >> >> >> Anyways, here is the diff for the change (by no means a patch) I
>> made
>> >> >> >> that fixed the problem:
>> >> >> >
>> >> >> > Unfortunately, that just fixes the problem by causing an additional
>> delay
>> >> >> since the wait_for_vblank() and get_frame_count() loops will timeout
>> >> since
>> >> >> the secondary display is disabled. The previous code disabled the
>> displays
>> >> >> completely while the new code just disables the memory request
>> >> interface
>> >> >> so that the display timing stays on to avoid additional flicker at startup
>> or
>> >> GPU
>> >> >> reset. For some reason on your system there seems to be a delay in
>> >> getting
>> >> >> the memory request interface to stop.
>> >> >> >
>> >> >> > Alex
>> >> >>
>> >> >> Right. That makes sense and yes the annoying flicker went away. :) Can
>> >> >> you think of something that can address systems that would need
>> more
>> >> >> time to get the memory request interface to stop such as mine?
>> >> >
>> >> > Does adding an additional radeon_mc_wait_for_idle(rdev) call at the
>> end
>> >> of rv515_mc_stop() help? Can you find out what the minimum delay
>> >> required for your system is?
>> >> >
>> >> > Alex
>> >>
>> >> Adding radeon_mc_wait_for_idle(rdev) call at the end of
>> >> rv515_mc_stop() - didn't help.
>> >>
>> >> I tried with adding udelay() with delay values of 1,10, and 50, and
>> >> 100 at the end of rv515_mc_stop(). 100 is the minimum that fixed the
>> >> DMAR faults.
>> >
>> > I guess we can just add the delay. I've tried all the ways I know of to get
>> proper feedback from the hardware.
>> >
>> > Alex
>> >
>>
>> Do you want me to send a patch with delay()? Would you like to see the
>> delay specific to this chipset which is RV620? That said if you think
>> of other ideas to try instead of delay, I can continue the debug and
>> testing effort.
>
> I'm planning to merge the attached patch. I'll let you know if I found out any other things to try.
>
> Alex
>
Tested it on 3.8-rc5 - looks good.
-- Shuah
^ permalink raw reply [flat|nested] 30+ messages in thread
end of thread, other threads:[~2013-01-31 16:47 UTC | newest]
Thread overview: 30+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-01-18 3:51 Linux 3.8-rc4 Linus Torvalds
2013-01-18 17:51 ` Shuah Khan
2013-01-18 22:37 ` Shuah Khan
2013-01-19 0:40 ` Shuah Khan
2013-01-19 16:44 ` Deucher, Alexander
2013-01-22 16:14 ` Shuah Khan
2013-01-22 16:36 ` Deucher, Alexander
2013-01-22 18:05 ` Shuah Khan
2013-01-22 18:29 ` Shuah Khan
2013-01-22 18:40 ` Deucher, Alexander
2013-01-22 18:55 ` Shuah Khan
2013-01-22 23:57 ` Shuah Khan
2013-01-23 13:40 ` Deucher, Alexander
2013-01-23 18:44 ` Shuah Khan
2013-01-29 3:19 ` Shuah Khan
2013-01-29 13:05 ` Deucher, Alexander
2013-01-29 19:11 ` Shuah Khan
2013-01-29 20:13 ` Deucher, Alexander
2013-01-29 21:39 ` Shuah Khan
2013-01-29 22:02 ` Deucher, Alexander
2013-01-29 23:45 ` Shuah Khan
2013-01-30 2:38 ` Shuah Khan
2013-01-30 13:31 ` Deucher, Alexander
2013-01-30 15:35 ` Shuah Khan
2013-01-30 15:53 ` Deucher, Alexander
2013-01-30 21:12 ` Shuah Khan
2013-01-31 14:56 ` Deucher, Alexander
2013-01-31 16:01 ` Shuah Khan
2013-01-31 16:05 ` Deucher, Alexander
2013-01-31 16:47 ` Shuah Khan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).