* [FYI] call trace on boot, BusLogic driver, 2.5.68
@ 2003-05-03 2:28 David Ford
0 siblings, 0 replies; only message in thread
From: David Ford @ 2003-05-03 2:28 UTC (permalink / raw)
To: Linux Kernel Mailing List
scsi: ***** BusLogic SCSI Driver Version 2.1.16 of 18 July 2002 *****
scsi: Copyright 1995-1998 by Leonard N. Zubkoff <lnz@dandelion.com>
ERROR: SCSI host `BusLogic' has no error handling
ERROR: This is not a safe way to run your SCSI host
ERROR: The error handling must be added to this driver
Call Trace:
[<c0282ea3>] scsi_register+0x623/0x630
[<c014a33b>] check_poison_obj+0x3b/0x1b0
[<c014c2f9>] kmalloc+0x169/0x1c0
[<c012664c>] __request_region+0x5c/0x90
[<c047cacd>] BusLogic_DetectHostAdapter+0x1fd/0x390
[<c0275dc7>] ide_register_driver+0x227/0x360
[<c0282ed2>] scsi_register_host+0x22/0xc0
[<c047d5a9>] init_this_scsi_driver+0x19/0x40
[<c04647bb>] do_initcalls+0x2b/0xa0
[<c0134da2>] init_workqueues+0x12/0x30
[<c0105068>] init+0x28/0x150
[<c0105040>] init+0x0/0x150
[<c01073ad>] kernel_thread_helper+0x5/0x18
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-05-03 2:16 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-05-03 2:28 [FYI] call trace on boot, BusLogic driver, 2.5.68 David Ford
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox