Re: scsi/firewire kernel oops, any point in reporting a bug ?

2010-07-14 Thread Sven Joachim
On 2010-07-14 04:31 +0200, bri...@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-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87mxtuleuh@turtle.gmx.de



Re: scsi/firewire kernel oops, any point in reporting a bug ?

2010-07-14 Thread briand
On Wed, 14 Jul 2010 09:09:10 +0200
Sven Joachim svenj...@gmx.de wrote:

 On 2010-07-14 04:31 +0200, bri...@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-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100714183551.52e85...@windy.deldotd.com



Re: scsi/firewire kernel oops, any point in reporting a bug ?

2010-07-14 Thread Sven Joachim
On 2010-07-15 03:35 +0200, bri...@aracnet.com wrote:

 Looks like the latest kernel is -5, is that correct ?

Yes.

Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87d3upqudu@turtle.gmx.de



scsi/firewire kernel oops, any point in reporting a bug ?

2010-07-13 Thread briand
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.

The question is , submit to Debian or to LKML ?


Thanks

Brian

[24128.816103] IP: [a00afde6] sbp2_scsi_abort+0x19/0x7b 
[firewire_sbp2]
[24128.816121] PGD 1160b3067 PUD 11e490067 PMD 0 
[24128.816129] Oops:  [#1] SMP 
[24128.816135] last sysfs file: /sys/devices/pci:00/:00:0e.0/class
[24128.816141] CPU 0 
[24128.816145] Modules linked in: ip6table_filter ip6_tables iptable_filter 
ip_tables x_tables powernow_k8 cpufreq_stats cpufreq_powersave 
cpufreq_conservative cpufreq_userspace ppdev lp vboxnetadp vboxnetflt vboxdrv 
kvm_amd kvm fuse nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc 
loop dm_mod cp210x usblp usbhid hid usbserial snd_hda_codec_realtek ohci_hcd sg 
firewire_sbp2 ide_cd_mod cdrom snd_hda_intel snd_hda_codec snd_hwdep snd_pcm 
snd_seq snd_timer snd_seq_device snd firewire_ohci nvidia(P) ehci_hcd soundcore 
edac_core i2c_nforce2 usbcore firewire_core ahci forcedeth snd_page_alloc 
k8temp amd74xx i2c_core edac_mce_amd evdev nls_base crc_itu_t pata_jmicron 
parport_pc processor parport pcspkr button ext3 jbd mbcache sd_mod crc_t10dif 
thermal fan thermal_sys ata_generic ide_pci_generic ide_core sata_nv libata 
scsi_mod
[24128.816259] Pid: 716, comm: scsi_eh_10 Tainted: P   2.6.32-3-amd64 
#1  
[24128.816264] RIP: 0010:[a00afde6]  [a00afde6] 
sbp2_scsi_abort+0x19/0x7b [firewire_sbp2]
[24128.816277] RSP: 0018:88011d423d30  EFLAGS: 00010286
[24128.816282] RAX:  RBX: 88011e799c00 RCX: 88011dabece8
[24128.816288] RDX: 88011d423d70 RSI: 2002 RDI: a00b0ec1
[24128.816293] RBP: 8800dfabc500 R08: 88011d422000 R09: 880005a155c0
[24128.816298] R10: 8800bb670700 R11: 0246 R12: 
[24128.816303] R13: 0286 R14: 09c4 R15: 
[24128.816310] FS:  7f7c40cb9720() GS:880005a0() 
knlGS:f4db1710
[24128.816316] CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
[24128.816321] CR2: 0010 CR3: 00011e1ef000 CR4: 06f0
[24128.816326] DR0:  DR1:  DR2: 
[24128.816332] DR3:  DR6: 0ff0 DR7: 0400
[24128.816338] Process scsi_eh_10 (pid: 716, threadinfo 88011d422000, task 
88011dabe9f0)
[24128.816342] Stack:
[24128.816346]  880119ac5000 8800dfabc500  
0286
[24128.816353] 0 880119ac5000 a0003e94  
88020002
[24128.816361] 0 88011d423d70 88011d423d70 00020002 
0006
[24128.816371] Call Trace:
[24128.816390]  [a0003e94] ? scsi_send_eh_cmnd+0x1b7/0x29e [scsi_mod]
[24128.816401]  [a00af84f] ? sbp2_cancel_orbs+0xbb/0xe7 
[firewire_sbp2]
[24128.816417]  [a0003fa3] ? scsi_eh_tur+0x28/0x78 [scsi_mod]
[24128.816433]  [a0004cd2] ? scsi_error_handler+0x328/0x5b5 [scsi_mod]
[24128.816449]  [a00049aa] ? scsi_error_handler+0x0/0x5b5 [scsi_mod]
[24128.816460]  [81064789] ? kthread+0x79/0x81
[24128.816469]  [81011baa] ? child_rip+0xa/0x20
[24128.816476]  [81064710] ? kthread+0x0/0x81
[24128.816482]  [81011ba0] ? child_rip+0x0/0x20
[24128.816486] Code: 02 74 09 c6 83 93 00 00 00 24 31 d2 59 5b 89 d0 5d c3 53 
48 83 ec 20 48 8b 07 48 c7 c7 c1 0e 0b a0 48 8b 98 88 00 00 00 48 8b 03 48 8b 
70 10 31 c0 e8 13 d6 23 e1 48 8b 03 48 8b 40 08 48 8b 30 
[24128.816543] RIP  [a00afde6] sbp2_scsi_abort+0x19/0x7b 
[firewire_sbp2]
[24128.816553]  RSP 88011d423d30
[24128.816557] CR2: 0010
[24128.816562] ---[ end trace f299684bf0dbe66c ]---


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100713193149.04a36...@windy.deldotd.com