scsi/firewire kernel oops, any point in reporting a bug ?
Hi All,
I've attached the output of dmesg at the end of the e-mail.
As usual everything was perfectly stable before I made the mistake of
doing dist-upgrade. I've really got to quit doing that unless I
_really_ need to.
So I can't see that anyone is going to be able to use the information
to do anything, but I thought I'd ask. If there's a chance then I'll
go ahead and submit a bug report and do what I can to help figure out
the problem.
I think it has something to do with firewire as I'm getting lots of
messages of all sorts of things being broken, and yet firewire seems to
be working fine.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100713193149.04a36762@windy.deldotd.com">http://lists.debian.org/20100713193149.04a36762@windy.deldotd.com
07-14-2010, 07:09 AM
Sven Joachim
scsi/firewire kernel oops, any point in reporting a bug ?
On 2010-07-14 04:31 +0200, briand@aracnet.com wrote:
> The question is , submit to Debian or to LKML ?
Report a bug in Debian, they will likely instruct how to report
upstream. But first of all, boot a newer kernel because your current
one…
> [24128.816259] Pid: 716, comm: scsi_eh_10 Tainted: P 2.6.32-3-amd64 #1
…is more than four months old. It is quite possible that the problem
has already been solved.
Sven
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87mxtuleuh.fsf@turtle.gmx.de">http://lists.debian.org/87mxtuleuh.fsf@turtle.gmx.de
07-15-2010, 01:35 AM
scsi/firewire kernel oops, any point in reporting a bug ?
On Wed, 14 Jul 2010 09:09:10 +0200
Sven Joachim <svenjoac@gmx.de> wrote:
> On 2010-07-14 04:31 +0200, briand@aracnet.com wrote:
>
> > The question is , submit to Debian or to LKML ?
>
> Report a bug in Debian, they will likely instruct how to report
> upstream. But first of all, boot a newer kernel because your current
> one…
>
> > [24128.816259] Pid: 716, comm: scsi_eh_10 Tainted: P
> > 2.6.32-3-amd64 #1
>
> …is more than four months old. It is quite possible that the problem
> has already been solved.
>
Looks like the latest kernel is -5, is that correct ?
Brian
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100714183551.52e85f07@windy.deldotd.com">http://lists.debian.org/20100714183551.52e85f07@windy.deldotd.com
07-15-2010, 03:46 AM
Sven Joachim
scsi/firewire kernel oops, any point in reporting a bug ?
On 2010-07-15 03:35 +0200, briand@aracnet.com wrote:
> Looks like the latest kernel is -5, is that correct ?
Yes.
Sven
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87d3upqudu.fsf@turtle.gmx.de">http://lists.debian.org/87d3upqudu.fsf@turtle.gmx.de