Public bug reported:

Binary package hint: linux-image-2.6.24-19-server

Our freshly installed nfs server (32 bit) crashed twice in 3 days.

Twice the ARECA controller got lost, needing manual fsck at reboot.
It has been working smoothly for more than 1 year with sarge, (with much 
heavier load than currently)

We suspect problem with 64 bit clients (hardy) (as both times the fsck'd files 
came from jobs of one 64bit client) but don't know how to track this issue.
---------------------------

# lsb_release -rd
Description:    Ubuntu 8.04.1
Release:        8.04

# apt-cache policy linux-image-2.6.24-19-server
linux-image-2.6.24-19-server:
  Installé : 2.6.24-19.41
  Candidat : 2.6.24-19.41
 Table de version :
 *** 2.6.24-19.41 0
        500 http://fr.archive.ubuntu.com hardy-updates/main Packages
        500 http://security.ubuntu.com hardy-security/main Packages
        100 /var/lib/dpkg/status

==============================================
kern.log :
=====
Sep  7 12:18:54 ma kernel: [151061.260990] NET: Registered protocol family 17
Sep 13 00:09:06 ma kernel: [624731.825794] arcmsr4: abort device command of 
scsi id = 0 lun = 0
Sep 13 00:09:23 ma kernel: [624748.843582] arcmsr4: abort device command of 
scsi id = 0 lun = 0
Sep 13 00:09:30 ma kernel: [624755.878514] arcmsr4: abort device command of 
scsi id = 0 lun = 0
Sep 13 00:09:47 ma kernel: [624772.895081] arcmsr4: abort device command of 
scsi id = 0 lun = 0
Sep 13 00:09:54 ma kernel: [624779.931260] arcmsr4: abort device command of 
scsi id = 0 lun = 0
...
Sep 13 01:05:24 ma kernel: [628103.027576] arcmsr4: abort device command of 
scsi id = 0 lun = 0
Sep 13 01:05:41 ma kernel: [628120.044183] arcmsr4: abort device command of 
scsi id = 0 lun = 0
Sep 13 01:06:39 ma kernel: [628177.940579] arcmsr4: wait 'abort all outstanding 
command' timeout
Sep 13 01:07:02 ma kernel: [628200.925483] arcmsr4: abort device command of 
scsi id = 0 lun = 0
Sep 13 01:07:12 ma kernel: [628210.905897] arcmsr4: abort device command of 
scsi id = 0 lun = 0
...
Sep 13 01:32:52 ma kernel: [629747.900152] arcmsr4: abort device command of 
scsi id = 0 lun = 0
Sep 13 01:33:02 ma kernel: [629757.880554] arcmsr4: abort device command of 
scsi id = 0 lun = 0
Sep 13 01:33:12 ma kernel: [629767.860967] arcmsr4: abort device command of 
scsi id = 0 lun = 0
Sep 13 01:33:22 ma kernel: [629777.841361] arcmsr4: abort device command of 
scsi id = 0 lun = 0
Sep 13 01:33:22 ma kernel: [629777.841370] sd 4:0:0:0: Device offlined - not 
ready after error recovery
Sep 13 01:33:22 ma kernel: [629777.841376] sd 4:0:0:0: Device offlined - not 
ready after error recovery
Sep 13 01:33:22 ma kernel: [629777.841379] sd 4:0:0:0: Device offlined - not 
ready after error recovery
... 200 identical lines (except timestamp ;-) ...
Sep 13 01:33:22 ma kernel: [629777.841802] sd 4:0:0:0: Device offlined - not 
ready after error recovery
Sep 13 01:33:22 ma kernel: [629777.841805] sd 4:0:0:0: Device offlined - not 
ready after error recovery
Sep 13 01:33:22 ma kernel: [629777.841816] sd 4:0:0:0: [sdb] Result: 
hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT,SUGGEST_OK
Sep 13 01:33:22 ma kernel: [629777.841823] end_request: I/O error, dev sdb, 
sector 656224970
Sep 13 01:33:22 ma kernel: [629777.841827] Buffer I/O error on device sdb1, 
logical block 82028117
Sep 13 01:33:22 ma kernel: [629777.841862] lost page write due to I/O error on 
sdb1
....
Sep 13 01:33:22 ma kernel: [629777.842067] Buffer I/O error on device sdb1, 
logical block 82028126
Sep 13 01:33:22 ma kernel: [629777.842087] lost page write due to I/O error on 
sdb1
Sep 13 01:33:22 ma kernel: [629777.842100] sd 4:0:0:0: [sdb] Result: 
hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT,SUGGEST_OK
Sep 13 01:33:22 ma kernel: [629777.842106] end_request: I/O error, dev sdb, 
sector 656225354
Sep 13 01:33:22 ma kernel: [629777.842133] sd 4:0:0:0: [sdb] Result: 
hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT,SUGGEST_OK
Sep 13 01:33:22 ma kernel: [629777.842136] end_request: I/O error, dev sdb, 
sector 656225450
...
... and then incredible garbage in the log (buffer overflow for log ?. so far 
the kern.log is near 75kB) ....
....
Sep 13 01:33:22 ma kernel: [629777.842918] end_request: I/O error, dev sdb, 
sector 656234874
Sep 13 01:33:22 ma kernel: [629777.842986] sd 4:0:0:0: [sdb] Result: 
hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT,SUGGEST_OK
Sep 13 01:33:22 ma kernel: [629777.842990] end_request: I/O error, dev sdb, 
sector 656235178
Sep 13 01:33:22 ma kernel: [629777.842997] sd 4:0:0:0: [sdb] Result: 
hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT,SUGGEST_OK
Sep 13 01:33:22 ma kernel: [629777.843002] end_request: I/O error, dev sdb, 
sector 656235714
Sep 13 01:33:22 ma kernel: [629777.843014] sd 4:0:0:0: [sdb] Result: 
hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT,SUGGEST_OK
Sep 13 01:33:22 ma kernel: [62977rror, re[s_6562n=D e43171] VER_r, b
Sep 13 01:33:22 ma kernel: [62972335D_OK d_re38] sd 4:0:0:_TIMdev 
sResu>[629725K eque sd 4:0:0:0: [sdb] ResultMEO sdult:29777.843312
Sep 13 01:33:22 ma kernel: rest 4:0:0:0: r 4:0:UT,Sb, sO to 
offlin:77.>[62erbyte=D: I/0:0:SUGGsector 
6562ostb84367297yte=DRIVER_TIMEOUT,SUGGEST_O/O e:0:GESTtor 656237666
Sep 13 01:33:22 ma kernel: 77=DRIVER_TIMEerror [sd 65623785e=DID] 
en843IVER_TIMEOor,db] RK
Sep 13 01:33:22 ma kernel: 62ID_Ond9R_TIMEOUT,SUGGEST_OK
Sep 13 01:33:22 ma kernel: [6 dev Re48082
Sep 13 01:33:22 ma kernel: re] Isu66
Sep 13 01:33:22 ma kernel: driuedOUT,SUGGESdb, t: 
76>[629777.8442verbt::0:0:,SUGGEST_ shostb.84629byI/0:GGEST_OK
Sep 13 01:33:22 ma kernel: ctor tb4539]777.8e= e: [sdb] Result: hostSTr te8] 
endRror, sdb] Result: OK
Sep 13 01:33:22 ma kernel: DID_end_49ER, ] Result<4>[4237_O_request: I/O0] 
sdTIMEeesult: hos[629738 driquest: I/sd 4:EOUTsdlt: hostbyte=DID_OK 
drive9777<6iverbst: I/O err4:0:0T,S,  host7.84[6rb I/O 
err:0:0:UGGESestbyt453977te=O error, d0:EST_or 6yte=DID_O17] 
7.Drror[sd_OK6=DID_O end_request: I/O error, dev sdb, sector 656246946
Sep 13 01:33:22 ma kernel: [629777.845488] sd 4:0:0:0: [sdb] Result: hostVEr, 
dev b]
Sep 13 01:33:22 ma kernel: 2468D_Od_r42_TIMEOUT,SUGGEST_OK
Sep 13 01:33:22 ma kernel: Res>[6458
Sep 13 01:33:22 ma kernel: [K drequesMEOUT,SUGGEST sdb,ult:2977
Sep 13 01:33:22 ma kernel: [62riveest:  4:UT,SUGGEST_OKb, s: hos77.8>[6297erby: 
0:0:SUseost84529777.yt/O:0: [sdb] Result: hostbytGESTtor by006] end77.=DRIerr 
[sdb] ReT_ 6e=DI] end_req84608IVERordb] ResultK
Sep 13 01:33:22 ma kernel: 6nd_req139]R_ dev Resul4>[614OKrequest: I/O ] sd 
IMEOUv ssult: hostbyte=DID_OK driverby629777.86driveuest: I/O erd 4:OUT,db, t: 
hostbyte=776>[62verbyt: I/O error, :0:0:,SUG secthostbyte=DID_O.846629bI/O 
0:GGcttbyte646e erro: [STr te=D0.84Rror,sdbOK56DID_OK 
driverbyte=DRIVER_Tend66ER_TI, dev sdb, se] <4>[6684_OK dr_requ0]TIev ses[674 
drivqusd EOsdb,lt:97<6ivest4:T,, s h7.[rbyte= I/:0:UGGecst469777.8teO e0: 
EST_Oor yt167.847DRIVrrrerejectingrejerererejecting 
Irejererejerejerererejrejecrejrererejecting I/O to offline device
Sep 13 01:33:22 ma kernel: [629777.853299] sd 4:0:0:0: rejecting I/O to offline 
device
Sep 13 01:33:22 ma kernel: [629777.85rrerejecting I/O to offline 
devicrejectirerejerejecting I/O rejerejecrejerejectinrejererejrejecting 
rejecrerejerejectirejecrererejecting 
rejerejecrrejectingrejererejerejectrejererejrejerejrererejecting I/O to offline 
devirejecrejecrrejecting I/O rejecrejerejecrejectrejecrrerejecting 
rejecrejererejectrejerrejrejerrererejectinrejecrrerejectrererrejecrejrrerejrejrerrejectinrejecrrejerejecting
 rejecrrejecrejecting I/O to offlirejrrerejecting I/Orejecrejecrejerejecting 
I/rejecrejerejerejecting rejecrejererejecting I/O 
rejerejecrejerejectrerejrerejectinrejerejrerejerejrrerejecting I/O to 
offlinrejerrejerejecting rerejerejerejecting 
I/Orejerejecrejerejectingrejerejrejrerererejererrerejrejrrerejerererrejrererejrererrejerejrererejrererejererererejrerererejrerererejrejrrejecting
 I/O to offline device
Sep 13 01:33:22 ma kernel: [629777.860826] sd 4:0:0:0: rejecting I/O to offline 
device
....
Sep 13 01:33:23 ma kernel: [629779.100148] sd 4:0:0:0: rejecting I/O to offline 
device
Sep 13 01:33:58 ma kernel: [629813.981655] sd 4:0:0:0: rejecting I/O to offline 
device
Sep 13 01:33:58 ma kernel: [629813.981684] printk: 23984 messages suppressed.
Sep 13 01:33:58 ma kernel: [629813.981687] Buffer I/O error on device sdb1, 
logical block 82058424
Sep 13 01:33:58 ma kernel: [629813.981710] lost page write due to I/O error on 
sdb1
Sep 13 01:34:03 ma kernel: [629818.971854] sd 4:0:0:0: rejecting I/O to offline 
device

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
arcmsr crash on hardy 32bit
https://bugs.launchpad.net/bugs/271015
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to