lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 22 Jan 2013 11:05:37 -0700
From:	Shuah Khan <shuahkhan@...il.com>
To:	"Deucher, Alexander" <Alexander.Deucher@....com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 3.8-rc4

On Tue, Jan 22, 2013 at 9:36 AM, Deucher, Alexander
<Alexander.Deucher@....com> wrote:
>> -----Original Message-----
>> From: Shuah Khan [mailto:shuahkhan@...il.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@....com> wrote:
>> >> -----Original Message-----
>> >> From: Shuah Khan [mailto:shuahkhan@...il.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@...il.com>
>> wrote:
>> >> > On Fri, Jan 18, 2013 at 10:51 AM, Shuah Khan <shuahkhan@...il.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

Download attachment "dmesg_3.8-rc4_radeaon" of type "application/octet-stream" (202682 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ