FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu Kernel Team

 
 
LinkBack Thread Tools
 
Old 09-30-2010, 10:15 PM
Brian Murray
 
Default Kernel Oops Reports

With the end goal of trying to consolidate some of the duplicate Oops
reports I've been poking at Oops bugs some and haven written a few
scripts for finding the tops Oops reports for example 23 Oops'es are
about:

WARNING: at
/build/buildd/linux-2.6.35/drivers/gpu/drm/radeon/radeon_fence.c:235
radeon_fence_wait

Talking with Brad about this he indicated that finding out the hardware
involved with this bug reports would be quite useful. So I've something
like this[1] now:

WARNING: at
/build/buildd/linux-2.6.35/drivers/gpu/drm/radeon/radeon_fence.c:235

This device: ATI Technologies Inc Mobility Radeon HD 3400 Series
[1002:95c4] (prog-if 00 [VGA controller])
LP: #642088 is New, has 0 dupes
LP: #620052 is New, has 0 dupes

With my limited kernel knowledge I'd guess bug 642088 and bug 620052 are
duplicates. However, not being a kernel developer I'd like input as to
what other properties of the bugs should be checked to ensure that they
are in fact duplicates. Alternatively, what type of report would you
like to have to facilitate your consolidation of likely duplicate
Oops'es.

[1] The full output of warning results for that Oops is attached

Thanks,
--
Brian Murray
Ubuntu Bug Master
WARNING: at /build/buildd/linux-2.6.35/drivers/gpu/drm/radeon/radeon_fence.c:235
This device: ATI Technologies Inc Mobility Radeon HD 3400 Series [1002:95c4] (prog-if 00 [VGA controller])
LP: #642088 is New, has 0 dupes
LP: #620052 is New, has 0 dupes
This device: ATI Technologies Inc Radeon Mobility X1400 [1002:7145] (prog-if 00 [VGA controller])
LP: #612375 is New, has 0 dupes
This device: ATI Technologies Inc RV635 PRO AGP [Radeon HD 3650] [1002:9596] (prog-if 00 [VGA controller])
LP: #621655 is New, has 0 dupes
This device: ATI Technologies Inc R300 NF [Radeon 9600 TX] [1002:4e46] (prog-if 00 [VGA controller])
LP: #641691 is New, has 0 dupes
This device: ATI Technologies Inc Mobility Radeon HD 3470 [1002:95c0]
LP: #603758 is New, has 5 dupes
This device: ATI Technologies Inc RV770 [Radeon HD 4850] [1002:9442] (prog-if 00 [VGA controller])
LP: #640970 is New, has 0 dupes
This device: ATI Technologies Inc M880G [Mobility Radeon HD 4200] [1002:9712] (prog-if 00 [VGA controller])
LP: #623710 is New, has 0 dupes
LP: #619793 is New, has 0 dupes
This device: ATI Technologies Inc RV730 PRO [Radeon HD 4650] [1002:9498] (prog-if 00 [VGA controller])
LP: #621863 is Confirmed, has 3 dupes
This device: ATI Technologies Inc M92 [Mobility Radeon HD 4500 Series] [1002:9553] (prog-if 00 [VGA controller])
LP: #634244 is New, has 0 dupes
This device: ATI Technologies Inc RV710 [Radeon HD 4350] [1002:954f] (prog-if 00 [VGA controller])
LP: #619185 is New, has 0 dupes
This device: ATI Technologies Inc RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller])
LP: #623634 is New, has 0 dupes
This device: ATI Technologies Inc RS780MC [Radeon HD 3100 Graphics] [1002:9613] (prog-if 00 [VGA controller])
LP: #621232 is New, has 0 dupes
LP: #618672 is New, has 0 dupes
This device: ATI Technologies Inc M52 [Mobility Radeon X1300] [1002:7149] (prog-if 00 [VGA controller])
LP: #620831 is New, has 6 dupes
This device: ATI Technologies Inc RS780M/RS780MN [Radeon HD 3200 Graphics] [1002:9612] (prog-if 00 [VGA controller])
LP: #623041 is New, has 0 dupes
LP: #622200 is New, has 0 dupes
This device: ATI Technologies Inc R430 [Radeon X800 (PCIE)] [1002:554f] (prog-if 00 [VGA controller])
LP: #636459 is New, has 0 dupes
This device: ATI Technologies Inc RV515 [Radeon X1300] [1002:7146] (prog-if 00 [VGA controller])
LP: #622362 is New, has 0 dupes
This device: ATI Technologies Inc RV670PRO [Radeon HD 3850] [1002:9505] (prog-if 00 [VGA controller])
LP: #618034 is New, has 0 dupes
This device: ATI Technologies Inc M92 LP [Mobility Radeon HD 4300 Series] [1002:9552] (prog-if 00 [VGA controller])
LP: #636112 is New, has 0 dupes
This device: ATI Technologies Inc M860G [Mobility Radeon 4100] [1002:9713]
LP: #594435 is New, has 0 dupes
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 10-01-2010, 07:41 AM
Andy Whitcroft
 
Default Kernel Oops Reports

On Thu, Sep 30, 2010 at 03:15:47PM -0700, Brian Murray wrote:
> With the end goal of trying to consolidate some of the duplicate Oops
> reports I've been poking at Oops bugs some and haven written a few
> scripts for finding the tops Oops reports for example 23 Oops'es are
> about:
>
> WARNING: at
> /build/buildd/linux-2.6.35/drivers/gpu/drm/radeon/radeon_fence.c:235
> radeon_fence_wait
>
> Talking with Brad about this he indicated that finding out the hardware
> involved with this bug reports would be quite useful. So I've something
> like this[1] now:
>
> WARNING: at
> /build/buildd/linux-2.6.35/drivers/gpu/drm/radeon/radeon_fence.c:235
>
> This device: ATI Technologies Inc Mobility Radeon HD 3400 Series
> [1002:95c4] (prog-if 00 [VGA controller])
> LP: #642088 is New, has 0 dupes
> LP: #620052 is New, has 0 dupes
>
> With my limited kernel knowledge I'd guess bug 642088 and bug 620052 are
> duplicates. However, not being a kernel developer I'd like input as to
> what other properties of the bugs should be checked to ensure that they
> are in fact duplicates. Alternatively, what type of report would you
> like to have to facilitate your consolidation of likely duplicate
> Oops'es.
>
> [1] The full output of warning results for that Oops is attached

Well that report is pretty handy, perhaps we could use something like
that to feed into our weekly review. As a general form it looks handy
to me as a consumer, obviously for other types of oops we need different
types of hardware information. It might make sense to generalise the
report so it brings base system information and graphics information.

JFo, perhaps we should try reviewing a couple of these monday.

-apw

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 10-01-2010, 10:12 AM
Jeremy Foshee
 
Default Kernel Oops Reports

On Fri, Oct 01, 2010 at 08:41:43AM +0100, Andy Whitcroft wrote:
> On Thu, Sep 30, 2010 at 03:15:47PM -0700, Brian Murray wrote:
> > With the end goal of trying to consolidate some of the duplicate Oops
> > reports I've been poking at Oops bugs some and haven written a few
> > scripts for finding the tops Oops reports for example 23 Oops'es are
> > about:
> >
> > WARNING: at
> > /build/buildd/linux-2.6.35/drivers/gpu/drm/radeon/radeon_fence.c:235
> > radeon_fence_wait
> >
> > Talking with Brad about this he indicated that finding out the hardware
> > involved with this bug reports would be quite useful. So I've something
> > like this[1] now:
> >
> > WARNING: at
> > /build/buildd/linux-2.6.35/drivers/gpu/drm/radeon/radeon_fence.c:235
> >
> > This device: ATI Technologies Inc Mobility Radeon HD 3400 Series
> > [1002:95c4] (prog-if 00 [VGA controller])
> > LP: #642088 is New, has 0 dupes
> > LP: #620052 is New, has 0 dupes
> >
> > With my limited kernel knowledge I'd guess bug 642088 and bug 620052 are
> > duplicates. However, not being a kernel developer I'd like input as to
> > what other properties of the bugs should be checked to ensure that they
> > are in fact duplicates. Alternatively, what type of report would you
> > like to have to facilitate your consolidation of likely duplicate
> > Oops'es.
> >
> > [1] The full output of warning results for that Oops is attached
>
> Well that report is pretty handy, perhaps we could use something like
> that to feed into our weekly review. As a general form it looks handy
> to me as a consumer, obviously for other types of oops we need different
> types of hardware information. It might make sense to generalise the
> report so it brings base system information and graphics information.
>
> JFo, perhaps we should try reviewing a couple of these monday.
>
Sounds good to me.

~JFo
> -apw
>
> --
> kernel-team mailing list
> kernel-team@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kernel-team
>

--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 10-01-2010, 02:35 PM
Brian Murray
 
Default Kernel Oops Reports

On Fri, Oct 01, 2010 at 08:41:43AM +0100, Andy Whitcroft wrote:
> On Thu, Sep 30, 2010 at 03:15:47PM -0700, Brian Murray wrote:
> > With the end goal of trying to consolidate some of the duplicate Oops
> > reports I've been poking at Oops bugs some and haven written a few
> > scripts for finding the tops Oops reports for example 23 Oops'es are
> > about:
> >
> > WARNING: at
> > /build/buildd/linux-2.6.35/drivers/gpu/drm/radeon/radeon_fence.c:235
> > radeon_fence_wait
> >
> > Talking with Brad about this he indicated that finding out the hardware
> > involved with this bug reports would be quite useful. So I've something
> > like this[1] now:
> >
> > WARNING: at
> > /build/buildd/linux-2.6.35/drivers/gpu/drm/radeon/radeon_fence.c:235
> >
> > This device: ATI Technologies Inc Mobility Radeon HD 3400 Series
> > [1002:95c4] (prog-if 00 [VGA controller])
> > LP: #642088 is New, has 0 dupes
> > LP: #620052 is New, has 0 dupes
> >
> > With my limited kernel knowledge I'd guess bug 642088 and bug 620052 are
> > duplicates. However, not being a kernel developer I'd like input as to
> > what other properties of the bugs should be checked to ensure that they
> > are in fact duplicates. Alternatively, what type of report would you
> > like to have to facilitate your consolidation of likely duplicate
> > Oops'es.
> >
> > [1] The full output of warning results for that Oops is attached
>
> Well that report is pretty handy, perhaps we could use something like
> that to feed into our weekly review. As a general form it looks handy
> to me as a consumer, obviously for other types of oops we need different
> types of hardware information. It might make sense to generalise the
> report so it brings base system information and graphics information.

I was thinking of creating some sort of relationship between the path
mentioned in the Oops and hardware. For example drivers/gpu would map
to video card(s).

Would hardware information be necessary for a warning like:

WARNING: at /build/buildd/linux-2.6.35/ubuntu/aufs/plink.c:332
au_plink_append

or

WARNING: at
/build/buildd/linux-2.6.35/arch/x86/include/asm/processor.h:1005
read_measured_perf_ctrs

> JFo, perhaps we should try reviewing a couple of these monday.

If the answer to the above question is no then perhaps reviewing a
collection of the bug reports related to either of the above Oops'es
would be more productive.

--
Brian Murray
Ubuntu Bug Master
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 
Old 10-12-2010, 03:12 PM
Brian Murray
 
Default Kernel Oops Reports

On Fri, Oct 01, 2010 at 08:41:43AM +0100, Andy Whitcroft wrote:
> On Thu, Sep 30, 2010 at 03:15:47PM -0700, Brian Murray wrote:
> > With the end goal of trying to consolidate some of the duplicate Oops
> > reports I've been poking at Oops bugs some and haven written a few
> > scripts for finding the tops Oops reports for example 23 Oops'es are
> > about:
> >
> > WARNING: at
> > /build/buildd/linux-2.6.35/drivers/gpu/drm/radeon/radeon_fence.c:235
> > radeon_fence_wait
> >
> > Talking with Brad about this he indicated that finding out the hardware
> > involved with this bug reports would be quite useful. So I've something
> > like this[1] now:
> >
> > WARNING: at
> > /build/buildd/linux-2.6.35/drivers/gpu/drm/radeon/radeon_fence.c:235
> >
> > This device: ATI Technologies Inc Mobility Radeon HD 3400 Series
> > [1002:95c4] (prog-if 00 [VGA controller])
> > LP: #642088 is New, has 0 dupes
> > LP: #620052 is New, has 0 dupes
> >
> > With my limited kernel knowledge I'd guess bug 642088 and bug 620052 are
> > duplicates. However, not being a kernel developer I'd like input as to
> > what other properties of the bugs should be checked to ensure that they
> > are in fact duplicates. Alternatively, what type of report would you
> > like to have to facilitate your consolidation of likely duplicate
> > Oops'es.
> >
> > [1] The full output of warning results for that Oops is attached
>
> Well that report is pretty handy, perhaps we could use something like
> that to feed into our weekly review. As a general form it looks handy
> to me as a consumer, obviously for other types of oops we need different
> types of hardware information. It might make sense to generalise the
> report so it brings base system information and graphics information.
>
> JFo, perhaps we should try reviewing a couple of these monday.

Did these get reviewed? How did the review go?

--
Brian Murray
Ubuntu Bug Master
--
kernel-team mailing list
kernel-team@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kernel-team
 

Thread Tools




All times are GMT. The time now is 03:38 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org