Author Topic: Pluto Hangs on Reboot  (Read 2305 times)


  • Hello, I'm new here
  • Posts: 0
    • View Profile
Pluto Hangs on Reboot
« on: November 07, 2005, 08:12:24 am »
I am doing a first time install of the Pluto core on a clean box from the Kickstart CD (.32 - same problem occurs with .30 and .31).  After completing the install and restarting the system, the program hangs at the following screen:
esi: c1bee000  edi: c1befec8  ebp: c1befe94  esp: c1befe94
ds: 007b  es: 007b  ss: 0068
Process scsi_eh_2 (pid: 735, threadinfo=c1bee000 task=c1b8e540)
Stack: 00000000 f880e772 c1b58000 c1beff1c 00000014 00000000 c1b8e540 c
       00000000 00000000 c1b8e020 00000000 dfa02b80 00000000 c1b8e540 c
       c1befee8 c1befee8 00000011 00000000 00040001 c1befed4 c1befed4 f
Call Trace
[<f880e772>] adpt_12o_post_wait+0x242/0x270 [dpt_i2o]
[<c01189e0>] default_wake_function+0x0/0x20
[<c01189e0>] default_wake_function+0x0/0x20
[<f880da1d>] adpt_abort+0x9d/0x110 [dpt_i2o]
[<c02bcb67>] schedule+0x3a7/0x640
[<f88514c3>] scsi_try_to_abort_cmd+0x23/0x40 [scsi_mod]
[<f885165c>] scsi_eh_abort_cmds+0x6c/0x100 [scsi_mod]
[<c0118b17>] __wake_up_locked+0x27/0x30
[<f88525d6>] scsi_unjam_host+0xb6/0x200 [scsi_mod]
[<c01189e0>] default_wake_function+0x0/0x20
[<c0118c02>] complete+0x52/0x80
[<f88527ef>] scsi_error_handler+0xcf/0x170 [scsi_mod]
[<f8852720>] scsi_error_handler+0x0/0x170 [scsi_mod]
[<c0101395>] kernel_thread_helper+0x5/0x10
Code: 00 e0 ff ff 21 e0 3b 50 14 89 e5 7f 1e 81 fa fe 00 00 00 76 0c b8
ff 21 e0 29 50 14 5d c3 80 78 14 00 75 ee 0f 0b eb ea <of> 0b eb de 8d
00 00 8d bc 27 00 00 00 00 55 89 e5 8b

Prior to hanging here I get error messages relating to the following:
shpchp can't be loaded
missing kernel or user mode driver shpchp
iop0: DMA ? IO allocation for i2o controller failed.
modprobe: FATAL: ERROR inserting shpchp (lib/modules/ Operation not permited

Any suggestions on how to troubleshoot?  I am using an Adaptec RAID controller.  Thanks.


  • Hello, I'm new here
  • Posts: 0
    • View Profile
Pluto Hangs on Reboot
« Reply #1 on: November 07, 2005, 02:11:00 pm »
Looks like it's the Adaptec driver that makes the kernel panic. This should be reported to the kernel team ( The kernel we use is plain vanilla. No patches or any other changes to the sources.