[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#322878: marked as done (kernel-image-2.6.11-1-k7: Firewire sbp2 errors reported ... looks distrurbing)

Your message dated Fri, 27 Oct 2006 19:08:29 +0200
with message-id <87zmbhofea.fsf@ouvaton.org>
and subject line Bug#322878: kernel-image-2.6.11-1-k7: Firewire sbp2 errors reported ... looks distrurbing
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: kernel-image-2.6.11-1-k7
Version: 2.6.11-7
Severity: normal

Hi.

I'm using backuppc to backup my systems on an external Hard disk (160 Gb LaCie d2 Hard Drive Extreme with Triple Interface) connected through Firewire.

I've noticed corruption in the data in the past, so I started over and was monitoring ieee1394 messages in the log this time (after having repartitioned, reformatted and tested for bad blocks).

I've found these error messages :

Aug 13 09:34:19 shuttle kernel: ieee1394: sbp2: sbp2util_node_write_no_wait failed
Aug 13 09:34:19 shuttle last message repeated 8 times
Aug 13 09:34:48 shuttle kernel: ieee1394: sbp2: aborting sbp2 command
Aug 13 09:34:48 shuttle kernel: Write (10) 2a 00 0d 6c 0c bf 00 00 08 00
Aug 13 09:34:48 shuttle kernel: ieee1394: sbp2: aborting sbp2 command
Aug 13 09:34:48 shuttle kernel: Write (10) 2a 00 0d 6c 0c ef 00 00 08 00
Aug 13 09:34:48 shuttle kernel: ieee1394: sbp2: aborting sbp2 command
Aug 13 09:34:48 shuttle kernel: Write (10) 2a 00 0d 6c 0d 37 00 00 08 00
Aug 13 09:34:48 shuttle kernel: ieee1394: sbp2: aborting sbp2 command
Aug 13 09:34:48 shuttle kernel: Write (10) 2a 00 0d 6c 0d 57 00 00 08 00
Aug 13 09:34:48 shuttle kernel: ieee1394: sbp2: aborting sbp2 command
Aug 13 09:34:48 shuttle kernel: Write (10) 2a 00 0d 6c 0d 7f 00 00 08 00
Aug 13 09:34:48 shuttle kernel: ieee1394: sbp2: aborting sbp2 command
Aug 13 09:34:48 shuttle kernel: Write (10) 2a 00 0d 6c 0e 0f 00 00 08 00
Aug 13 09:34:48 shuttle kernel: ieee1394: sbp2: aborting sbp2 command
Aug 13 09:34:48 shuttle kernel: Write (10) 2a 00 0d 6c 0e 5f 00 00 08 00
Aug 13 09:34:48 shuttle kernel: ieee1394: sbp2: aborting sbp2 command
Aug 13 09:34:48 shuttle kernel: Write (10) 2a 00 0d 6c 0f 4f 00 00 08 00

Actually don't know if this is the same issue as in bug #312320 since I haven't experienced any freeze so far... but could be.

Also, I haven't been able to check if there is any data corrupted yet (backup still on-going)... but anyway, I feel these messages aren't normal.

My controller gives the following in lspci :

0000:00:0c.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) (prog-if 10 [OHCI])
        Subsystem: VIA Technologies, Inc. IEEE 1394 Host Controller
        Flags: bus master, medium devsel, latency 32, IRQ 5
        Memory at ec101000 (32-bit, non-prefetchable) [size=2K]
        I/O ports at d400 [size=128]
        Capabilities: [50] Power Management version 2

Best regards,


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages kernel-image-2.6.11-1-k7 depends on:
ii  coreutils [fileutils]         5.2.1-2    The GNU core utilities
ii  fileutils                     5.2.1-2    The GNU file management utilities 
ii  initrd-tools                  0.1.81.1   tools to create initrd image for p
ii  module-init-tools             3.2-pre1-2 tools for managing Linux kernel mo

kernel-image-2.6.11-1-k7 recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi.

It seems to have been fixed, as I'm using it again on 2.6.17-2-686
without too much pain.

Best regards,

David Schmitt <david@schmitt.edv-bus.at> writes:

> Hi Olivier!
>
>
> In preparation of the upcoming etch release, would you please
> test if either 2.6.17-9 from testing or 2.6.18-3 from unstable
> fixes your problem with the sbp2 driver?
>
>
-- 
Olivier BERGER (OpenPGP: 1024D/B4C5F37F)
APRIL (http://www.april.org) - Vive python (http://www.python.org)
Pétition contre les brevets logiciels : http://petition.eurolinux.org

--- End Message ---
Reply to: