Select Your Language

Infrastructure and Management

Cloud Computing

Storage

Runtimes

Integration and Automation

  • Comments
  • Rhel 6.2 x86_64 USB DAT segfault

    Posted on
    Configuration:
    
    IBM x3400 M3 with HP USB DAT 320 Rhel 6.2 fully updated.
    
    I'm getting this:
    
    Jun 12 03:56:50 smf kernel: do_IRQ: 3.143 No irq handler for vector (irq -1)
    ...
    Jun 14 07:27:06 smf kernel: do_IRQ: 1.165 No irq handler for vector (irq -1)
    
    INFO: task tar:12538 blocked for more than 120 seconds.
    "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    tar           D 0000000000000000     0 12538  12534 0x00000080
     ffff880468065c38 0000000000000082 0000000000000000 0000000000000086
     ffff880468065c08 ffffffff8105e89c ffff88046058e480 ffff880400000004
     ffff880463751af8 ffff880468065fd8 000000000000f4e8 ffff880463751af8
    Call Trace:
     [] ? try_to_wake_up+0x24c/0x3e0
     [] schedule_timeout+0x215/0x2e0
     [] ? complete+0x52/0x60
     [] wait_for_common+0x123/0x180
     [] ? default_wake_function+0x0/0x20
     [] ? __generic_unplug_device+0x32/0x40
     [] wait_for_completion+0x1d/0x20
     [] st_do_scsi.clone.0+0x213/0x380 [st]
     [] st_read+0x5ca/0xb60 [st]
     [] ? apic_timer_interrupt+0xe/0x20
     [] vfs_read+0xb5/0x1a0
     [] ? audit_syscall_entry+0x272/0x2a0
     [] sys_read+0x51/0x90
     [] system_call_fastpath+0x16/0x1b
    INFO: task tar:12538 blocked for more than 120 seconds.
    "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    tar           D 0000000000000000     0 12538  12534 0x00000080
     ffff880468065c38 0000000
    ...
    
    and this gives:
    
    /bin/tar: /dev/st0: Cannot read: Input/output error
    ...
    /bin/tar: /dev/st0: Cannot read: No such device or address
    /bin/tar: Too many errors, quitting
    /bin/tar: Error is not recoverable: exiting now
    /dev/st0: No such file or directory
    
    the system is up and running with this configuration since more than 1 year.
    
    The first fault was June 12th, rebooted the server, it worked June 13th but it faulted again June 14th.
    
    Any idea?
    
    best regards,
    LF
    

    by

    points

    Responses

    Red Hat LinkedIn YouTube Facebook X, formerly Twitter

    Quick Links

    Help

    Site Info

    Related Sites

    © 2026 Red Hat