On Fri, Jan 18, 2013 at 10:51 AM, Shuah Khan <[email protected]> wrote: > On Thu, Jan 17, 2013 at 8:51 PM, Linus Torvalds > <[email protected]> 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 <[email protected]> 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 <[email protected]> Cc: Markus Trippelsdorf <[email protected]> Reviewed-by: Jerome Glisse <[email protected]> Tested-by: Jerome Glisse <[email protected]> Signed-off-by: Alex Deucher <[email protected]> :040000 040000 f641a4e6cb7ac7426a8a80f3a4cf51a6320f95d4 e974cd1737fafb82c6dc8f85dbcdf6cacfea893a M drivers -- Shuah -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
