Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 45438 - external firewire harddrive, goes "offline" according to dmesg when no activity after a few hours
Summary: external firewire harddrive, goes "offline" according to dmesg when no activi...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Mobile Herd (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-03-22 14:19 UTC by Joseph Roback
Modified: 2004-05-04 02:25 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joseph Roback 2004-03-22 14:19:15 UTC
I have an addonics external 2.5" harddrive firewire case with a 40GB IBM/HITACHI laptop drive.  Works perfectly, detects fine, transfer rates are more then excepted, but when the drive is inactive for an hour or so, the following messages show up in dmesg and then the drive is unusable, cannot umount the share, cannot reboot without holding power button.

Mar 22 03:15:33 wrx ieee1394: sbp2: aborting sbp2 command
Mar 22 03:15:33 wrx 0x2a 00 00 00 c7 ef 00 00 50 00
Mar 22 03:15:43 wrx ieee1394: sbp2: aborting sbp2 command
Mar 22 03:15:43 wrx 0x00 00 00 00 00 00
Mar 22 03:15:43 wrx ieee1394: sbp2: reset requested
Mar 22 03:15:43 wrx ieee1394: sbp2: Generating sbp2 fetch agent reset
Mar 22 03:15:53 wrx ieee1394: sbp2: aborting sbp2 command
Mar 22 03:15:53 wrx 0x00 00 00 00 00 00
Mar 22 03:15:53 wrx ieee1394: sbp2: reset requested
Mar 22 03:15:53 wrx ieee1394: sbp2: Generating sbp2 fetch agent reset
Mar 22 03:16:13 wrx ieee1394: sbp2: aborting sbp2 command
Mar 22 03:16:13 wrx 0x00 00 00 00 00 00
Mar 22 03:16:13 wrx ieee1394: sbp2: reset requested
Mar 22 03:16:13 wrx ieee1394: sbp2: Generating sbp2 fetch agent reset
Mar 22 03:16:33 wrx ieee1394: sbp2: aborting sbp2 command
Mar 22 03:16:33 wrx 0x00 00 00 00 00 00
Mar 22 03:16:33 wrx scsi: Device offlined - not ready after error recovery: host 0 channel 0 id 0 lun 0
Mar 22 03:16:33 wrx SCSI error : <0 0 0 0> return code = 0x50000
Mar 22 03:16:33 wrx end_request: I/O error, dev sda, sector 51183
Mar 22 03:16:33 wrx Buffer I/O error on device sda1, logical block 6390
Mar 22 03:16:33 wrx lost page write due to I/O error on sda1

and tons more that look like this:

03:53:42 wrx zam-7001: io error in reiserfs_find_entry
Mar 22 03:53:42 wrx scsi0 (0:0): rejecting I/O to offline device
Mar 22 03:53:42 wrx zam-7001: io error in reiserfs_find_entry
Mar 22 03:53:42 wrx scsi0 (0:0): rejecting I/O to offline device
Mar 22 03:53:42 wrx vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [49 542 0x0 SD]
Mar 22 03:53:42 wrx scsi0 (0:0): rejecting I/O to offline device
Mar 22 03:53:42 wrx vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [49 542 0x0 SD]
Mar 22 03:53:42 wrx scsi0 (0:0): rejecting I/O to offline device
Mar 22 03:53:42 wrx vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [49 542 0x0 SD]
Mar 22 03:53:42 wrx scsi0 (0:0): rejecting I/O to offline device
Mar 22 03:53:42 wrx vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [49 543 0x0 SD]
Mar 22 03:53:42 wrx scsi0 (0:0): rejecting I/O to offline device

I couldn't find much about it on the internet, except the sbp2 author (or former author) mentioned it might be the harddrive going to sleep.  The whole ext. firewire drive thing would be worthless if it could be woken up...



Reproducible: Always
Steps to Reproduce:
1.attach drive or boot with it on, hotplug picks it up
2.leave it inactive for about an hour or so.
3.try to access anything on the drive

Actual Results:  
programs / processes trying to access files become daemon'd, "D" status and 
hang.  unmount either hangs or segfaults twice. computer will not reboot. 
hangs on unmount filesystems.  must be hard reset. 

Expected Results:  
sbp2 needs wake or reset the drive if asleep??? 

emerge info: 
Portage 2.0.50-r1 (default-x86-2004.0, gcc-3.3.2, glibc-2.3.2-r9, 
2.6.4-gentoo) 
================================================================= 
System uname: 2.6.4-gentoo i686 Intel(R) Pentium(R) 4 Mobile CPU 1.90GHz 
Gentoo Base System version 1.4.3.13 
Autoconf: sys-devel/autoconf-2.58-r1 
Automake: sys-devel/automake-1.7.7 
ACCEPT_KEYWORDS="x86" 
AUTOCLEAN="yes" 
CFLAGS="-march=pentium4 -O3 -pipe -mmmx -msse -msse2 -fforce-addr 
-fomit-frame-pointer -funroll-loops -falign-functions=4" 
CHOST="i686-pc-linux-gnu" 
COMPILER="gcc3" 
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" 
CXXFLAGS="-march=pentium4 -O3 -pipe -mmmx -msse -msse2 -fforce-addr 
-fomit-frame-pointer -funroll-loops -falign-functions=4" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="autoaddcvs ccache sandbox" 
GENTOO_MIRRORS="http://mirrors.tds.net/gentoo ftp://mirrors.tds.net/gentoo" 
MAKEOPTS="-j2" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/var/tmp" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="/usr/local/portage" 
SYNC="rsync://rsync.gentoo.org/gentoo-portage" 
USE="X Xaw3d aavm acpi acpi4linux alsa apache2 arts avi berkdb bonobo crypt 
cups dga dv dvd emacs encode esd fbcon ffmpeg foomaticdb freetype gd gdbm gif 
gtk gtk2 gtkhtml guile ieee1394 imap imlib innodb ipv6 java joystick jpeg kde 
lcms ldap leim libgda libwww mbox mmx motif mozilla moznocompose moznoirc 
moznomail mpeg mysql ncurses offensive oggvorbis opengl oss pam pcap pcmcia 
pda pdflib perl png ppds python qt quicktime readline samba sdl slang slp snmp 
spell sse ssl svga tiff transcode truetype usb videos wxwindows x86 xinerama 
xml xml2 xmms xv xvid zlib"
Comment 1 Joseph Roback 2004-05-04 02:24:37 UTC
using gentoo-dev-sources-2.6.5-r1, i left the drive idle for 48 hrs and it worked fine. you can even hear the drive come out of sleep mode and start spinning.  i have been using 2.6.5-r1 for about 6 or 7 days now and no problems.
Comment 2 Joseph Roback 2004-05-04 02:25:49 UTC
just another comment, all those messages no longer appear in the system log either. :)