[PATCH] drm/radeon: deal with errors from framebuffer init path.

2012-03-06 Thread Dave Airlie
From: Dave Airlie We've been seeing a very occasional oops on a 32-bit rn50 platform running EL6 kernels at boot. It seems to be due to one of these functions failing and us then accessing a NULL-300 pointer. This should prevent the oops and give some info in the logs as to what is going on. S

[PATCH] drm/radeon: deal with errors from framebuffer init path.

2012-03-06 Thread Alex Deucher
On Tue, Mar 6, 2012 at 5:48 AM, Dave Airlie wrote: > From: Dave Airlie > > We've been seeing a very occasional oops on a 32-bit rn50 platform running EL6 > kernels at boot. It seems to be due to one of these functions failing and > us then accessing a NULL-300 pointer. > > This should prevent the

Re: [PATCH] drm/radeon: deal with errors from framebuffer init path.

2012-03-06 Thread Alex Deucher
On Tue, Mar 6, 2012 at 5:48 AM, Dave Airlie wrote: > From: Dave Airlie > > We've been seeing a very occasional oops on a 32-bit rn50 platform running EL6 > kernels at boot. It seems to be due to one of these functions failing and > us then accessing a NULL-300 pointer. > > This should prevent the

[PATCH] drm/radeon: deal with errors from framebuffer init path.

2012-03-06 Thread Dave Airlie
From: Dave Airlie We've been seeing a very occasional oops on a 32-bit rn50 platform running EL6 kernels at boot. It seems to be due to one of these functions failing and us then accessing a NULL-300 pointer. This should prevent the oops and give some info in the logs as to what is going on. S