* Kernel panic on Redhat Linux AS2.1 with QLogic 2342 HBA
@ 2004-02-10 5:15 veeresh
2004-02-10 12:21 ` Matthew Wilcox
2004-02-10 18:25 ` Andrew Vasquez
0 siblings, 2 replies; 5+ messages in thread
From: veeresh @ 2004-02-10 5:15 UTC (permalink / raw)
To: linux-kernel; +Cc: linux-scsi
Hi,
I am getting kernel panic under following configuration:
Machine: DL580 multiprocessor Intel Xeon 2GHZ processors(2); 32-bit
OS: Redhat Linux Advanced Server 2.1
Kernel Version:2.4.9-e25smp
HBA: Qlogic2342 FC HBA
Device connected: Ultrium FC interface tape drive.
Info of HBA from /proc/scsi/qla2300/0
QLogic PCI to Fibre Channel Host Adapter for QLA23xx:
Firmware version: 3.02.16, Driver version 6.06.10 Entry address = f8881060
HBA: QLA2312 , Serial# A00000
Request Queue = 0x36afc000, Response Queue = 0x36ae0000
Request Queue count= 128, Response Queue count= 512
Total number of active commands = 0
Total number of interrupts = 20146612
Total number of IOCBs (used/max) = (0/600)
Total number of queued commands = 0
Device queue depth = 0x20
Number of free request entries = 52
Number of mailbox timeouts = 0
Number of ISP aborts = 0
Number of loop resyncs = 0
Number of retries for empty slots = 0
Number of reqs in pending_q= 0, retry_q= 0, done_q= 0, scsi_retry_q= 0 Host
adapter:loop state= <READY>, flags= 0x2820813 Dpc flags = 0x0 MBX flags =
0x0 SRB Free Count = 4096 Link down Timeout = 060 Port down retry = 008
Login retry count = 008 Commands retried with dropped frame(s) = 0
SCSI Device Information: scsi-qla0-adapter-node=200000e08b000000;
scsi-qla0-adapter-port=200000e08b000000;
scsi-qla0-target-0=100000e00222623c;
scsi-qla0-target-1=100000e00242623c;
SCSI LUN Information:
(Id:Lun) * - indicates lun is not registered with the OS.
( 0: 0): Total reqs 95, Pending reqs 0, flags 0x0, 0:0:81,
( 0: 1): Total reqs 1622, Pending reqs 0, flags 0x0, 0:0:81,
( 0: 2): Total reqs 189, Pending reqs 0, flags 0x0, 0:0:81,
( 0: 3): Total reqs 4694518, Pending reqs 0, flags 0x0, 0:0:81, ( 1: 0):
Total reqs 95, Pending reqs 0, flags 0x0, 0:0:82, ( 1: 1): Total reqs
12850865, Pending reqs 0, flags 0x0, 0:0:82, ( 1: 2): Total reqs 2602072,
Pending reqs 0, flags 0x0, 0:0:82,
Kernel panic information:
kernel BUG at /usr/src/linux-2.4/include/asm/pci.h:145!
invalid operand: 0000
Kernel 2.4.9-e.25smp
CPU: 2
EIP: 0010:[<f8891658>] Tainted: P
EFLAGS: 00010086
EIP is at qla2x00_64bit_start_scsi [qla2300] 0x498
eax: 0000003b ebx: 00000002 ecx: c02f6744 edx: 000ce00a
esi: c7fb4000 edi: 00000011 ebp: f6afd868 esp: df15bc18
ds: 0018 es: 0018 ss: 0018
Process hp_ltt (pid: 26018, stackpage=df15b000)
Stack: f88a2f00 00000091 00000202 c02f87cc 00000000 c02f8394 c02f8394
c02f8d40
00000000 000000f0 00004000 f6afd840 00000002 00000000 00000001 0000006f
f55cf000 f6c20084 00000046 c02f8394 c02f8d40 00000000 00000020 f6afd840
Call Trace: [<f88a2f00>] .LC2 [qla2300] 0x0
[<f889a0f6>] qla2x00_next [qla2300] 0x206
[<f888bfbd>] qla2x00_queuecommand [qla2300] 0x3dd
[<f8800690>] scsi_dispatch_cmd [scsi_mod] 0x150
[<f8800d50>] scsi_done [scsi_mod] 0x0
[<f880878e>] scsi_request_fn [scsi_mod] 0x31e
[<f8807a34>] __scsi_insert_special [scsi_mod] 0x74
[<f8807a9a>] scsi_insert_special_req [scsi_mod] 0x1a
[<f880097b>] scsi_do_req_Rsmp_bdc72156 [scsi_mod] 0x14b
[<f89ede40>] sg_cmd_done_bh [sg] 0x0
[<f89ed05b>] sg_common_write [sg] 0x23b
[<f89ede40>] sg_cmd_done_bh [sg] 0x0
[<f89ecdee>] sg_new_write [sg] 0x1ce
[<f89ef9a1>] sg_build_reserve [sg] 0x51
[<f89ed330>] sg_ioctl [sg] 0x2b0
[<c013da56>] _wrapped_alloc_pages [kernel] 0x76
[<c012c612>] do_wp_page [kernel] 0x172
[<c012d19b>] do_no_page [kernel] 0x3b
[<c012d5f0>] handle_mm_fault [kernel] 0xf0
[<c0125893>] collect_signal [kernel] 0x93
[<c0117f80>] do_page_fault [kernel] 0x0
[<c0118126>] do_page_fault [kernel] 0x1a6
[<c0107086>] do_signal [kernel] 0x66
[<c0126ed3>] sys_rt_sigaction [kernel] 0x93
[<c0155887>] sys_ioctl [kernel] 0x257
[<c01073c3>] system_call [kernel] 0x33
Code: 0f 0b 8d b6 00 00 00 00 83 c4 08 8d 04 5b 8d 14 c5 00 00 00
<0>Kernel panic: not continuing
Could you please let me know the cause for this problem as early as
possible.....
Regards,
Veeresh
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Kernel panic on Redhat Linux AS2.1 with QLogic 2342 HBA
2004-02-10 5:15 Kernel panic on Redhat Linux AS2.1 with QLogic 2342 HBA veeresh
@ 2004-02-10 12:21 ` Matthew Wilcox
2004-02-10 18:25 ` Andrew Vasquez
1 sibling, 0 replies; 5+ messages in thread
From: Matthew Wilcox @ 2004-02-10 12:21 UTC (permalink / raw)
To: veeresh; +Cc: linux-kernel, linux-scsi
On Tue, Feb 10, 2004 at 10:45:59AM +0530, veeresh wrote:
> Hi,
>
> I am getting kernel panic under following configuration:
> Machine: DL580 multiprocessor Intel Xeon 2GHZ processors(2); 32-bit
> OS: Redhat Linux Advanced Server 2.1
> Kernel Version:2.4.9-e25smp
You need to contact Red Hat for problems with RH AS.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Kernel panic on Redhat Linux AS2.1 with QLogic 2342 HBA
2004-02-10 5:15 Kernel panic on Redhat Linux AS2.1 with QLogic 2342 HBA veeresh
2004-02-10 12:21 ` Matthew Wilcox
@ 2004-02-10 18:25 ` Andrew Vasquez
2004-02-11 1:36 ` Joel Becker
2004-02-11 13:21 ` veeresh
1 sibling, 2 replies; 5+ messages in thread
From: Andrew Vasquez @ 2004-02-10 18:25 UTC (permalink / raw)
To: linux-kernel, linux-scsi; +Cc: veeresh
On Tue, 10 Feb 2004, veeresh wrote:
> Kernel panic information:
> kernel BUG at /usr/src/linux-2.4/include/asm/pci.h:145!
> invalid operand: 0000
> Kernel 2.4.9-e.25smp
> CPU: 2
> EIP: 0010:[<f8891658>] Tainted: P
> EFLAGS: 00010086
> EIP is at qla2x00_64bit_start_scsi [qla2300] 0x498
One of the scatter-gather entries of a SCSI command was NULL. Is any
of the software you are running preparing SCSI commands and sending
them down via SG perhaps? What type of I/O is occuring when the
failure occurs?
Regards,
Andrew Vasquez
QLogic Corporation
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Kernel panic on Redhat Linux AS2.1 with QLogic 2342 HBA
2004-02-10 18:25 ` Andrew Vasquez
@ 2004-02-11 1:36 ` Joel Becker
2004-02-11 13:21 ` veeresh
1 sibling, 0 replies; 5+ messages in thread
From: Joel Becker @ 2004-02-11 1:36 UTC (permalink / raw)
To: Andrew Vasquez, linux-kernel, linux-scsi, veeresh
On Tue, Feb 10, 2004 at 10:25:13AM -0800, Andrew Vasquez wrote:
> On Tue, 10 Feb 2004, veeresh wrote:
>
> > Kernel panic information:
> > kernel BUG at /usr/src/linux-2.4/include/asm/pci.h:145!
> > invalid operand: 0000
> > Kernel 2.4.9-e.25smp
> > CPU: 2
> > EIP: 0010:[<f8891658>] Tainted: P
> > EFLAGS: 00010086
> > EIP is at qla2x00_64bit_start_scsi [qla2300] 0x498
>
> One of the scatter-gather entries of a SCSI command was NULL. Is any
> of the software you are running preparing SCSI commands and sending
> them down via SG perhaps? What type of I/O is occuring when the
> failure occurs?
Andrew,
This appears to be the same bug we discussed a while back. I
thought QLogic was working on a fix? We saw it with absolutely no SG
involved. It was something to do with error retry, wasn't it?
Joel
--
Brain: I shall pollute the water supply with this DNAdefibuliser,
turning everyone into mindless slaves.
Pinky: What about the people who drink bottled water?
Brain: Pinky, people who pay 5 dollars for a bottle of water are
already mindless slaves.
Joel Becker
Senior Member of Technical Staff
Oracle Corporation
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
^ permalink raw reply [flat|nested] 5+ messages in thread* RE: Kernel panic on Redhat Linux AS2.1 with QLogic 2342 HBA
2004-02-10 18:25 ` Andrew Vasquez
2004-02-11 1:36 ` Joel Becker
@ 2004-02-11 13:21 ` veeresh
1 sibling, 0 replies; 5+ messages in thread
From: veeresh @ 2004-02-11 13:21 UTC (permalink / raw)
To: 'Andrew Vasquez', linux-kernel, linux-scsi
Cc: SAIDU BUHARI (HP-India,ex2) (E-mail)
[-- Attachment #1: Type: text/plain, Size: 1682 bytes --]
Hi Andrew,
Thanks for your quick response..
Yes, the software prepares SCSI commands and sends them down via generic
device driver SG. In our case the device file for related to device
connected(LTO-2 FC interface tape drive) is "/dev/sg0".
I have logged list of CDB the software sends to a device using SG driver and
the attached the same. The log shows that the last CDB was Receive
diagnostic command. I ran multiple times the software, but the SCSI command
that failed was the same.
Please let me know if you need any information.
Best regards,
Veeresh
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Andrew Vasquez
Sent: Tuesday, February 10, 2004 11:55 PM
To: linux-kernel@vger.kernel.org; linux-scsi@vger.kernel.org
Cc: veeresh
Subject: Re: Kernel panic on Redhat Linux AS2.1 with QLogic 2342 HBA
On Tue, 10 Feb 2004, veeresh wrote:
> Kernel panic information:
> kernel BUG at /usr/src/linux-2.4/include/asm/pci.h:145!
> invalid operand: 0000
> Kernel 2.4.9-e.25smp
> CPU: 2
> EIP: 0010:[<f8891658>] Tainted: P
> EFLAGS: 00010086
> EIP is at qla2x00_64bit_start_scsi [qla2300] 0x498
One of the scatter-gather entries of a SCSI command was NULL. Is any
of the software you are running preparing SCSI commands and sending
them down via SG perhaps? What type of I/O is occuring when the
failure occurs?
Regards,
Andrew Vasquez
QLogic Corporation
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[-- Attachment #2: CDB.log --]
[-- Type: application/octet-stream, Size: 7858 bytes --]
Data Direction:SG_DXFER_NONE
Data buffer address:0
CDB[0]-->#0
CDB[1]-->#0
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#0
CDB[5]-->#0
Before third ioctl
Third ioctl is successful
sensebuf[0]-->70
sensebuf[1]-->0
sensebuf[2]-->6
sensebuf[3]-->0
sensebuf[4]-->0
sensebuf[5]-->0
sensebuf[6]-->0
sensebuf[7]-->e
sensebuf[8]-->0
sensebuf[9]-->0
sensebuf[10]-->0
sensebuf[11]-->0
sensebuf[12]-->29
sensebuf[13]-->3
sensebuf[14]-->0
sensebuf[15]-->0
sensebuf[16]-->2c
sensebuf[17]-->e5
sensebuf[18]-->0
sensebuf[19]-->0
sensebuf[20]-->0
sensebuf[21]-->0
Before calling first ioctl
First ioctl is successful
Data Direction:SG_DXFER_NONE
Data buffer address:0
CDB[0]-->#0
CDB[1]-->#0
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#0
CDB[5]-->#0
Before third ioctl
Third ioctl is successful
sensebuf[0]-->70
sensebuf[1]-->0
sensebuf[2]-->2
sensebuf[3]-->0
sensebuf[4]-->0
sensebuf[5]-->0
sensebuf[6]-->0
sensebuf[7]-->e
sensebuf[8]-->0
sensebuf[9]-->0
sensebuf[10]-->0
sensebuf[11]-->0
sensebuf[12]-->3a
sensebuf[13]-->0
sensebuf[14]-->0
sensebuf[15]-->0
sensebuf[16]-->2c
sensebuf[17]-->6b
sensebuf[18]-->0
sensebuf[19]-->0
sensebuf[20]-->0
sensebuf[21]-->0
UnSuccessful TUR Cmd
Before calling first ioctl
First ioctl is successful
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:3221137512
CDB[0]-->#12
CDB[1]-->#0
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#40
CDB[5]-->#0
Data Direction:SG_DXFER_NONE
Data buffer address:0
CDB[0]-->#0
CDB[1]-->#0
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#0
CDB[5]-->#0
sensebuf[0]-->70
sensebuf[1]-->0
sensebuf[2]-->6
sensebuf[3]-->0
sensebuf[4]-->0
sensebuf[5]-->0
sensebuf[6]-->0
sensebuf[7]-->e
sensebuf[8]-->0
sensebuf[9]-->0
sensebuf[10]-->0
sensebuf[11]-->0
sensebuf[12]-->29
sensebuf[13]-->3
sensebuf[14]-->0
sensebuf[15]-->0
sensebuf[16]-->2c
sensebuf[17]-->e5
sensebuf[18]-->0
sensebuf[19]-->0
sensebuf[20]-->0
sensebuf[21]-->0
Data Direction:SG_DXFER_NONE
Data buffer address:0
CDB[0]-->#0
CDB[1]-->#0
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#0
CDB[5]-->#0
sensebuf[0]-->70
sensebuf[1]-->0
sensebuf[2]-->2
sensebuf[3]-->0
sensebuf[4]-->0
sensebuf[5]-->0
sensebuf[6]-->0
sensebuf[7]-->e
sensebuf[8]-->0
sensebuf[9]-->0
sensebuf[10]-->0
sensebuf[11]-->0
sensebuf[12]-->3a
sensebuf[13]-->0
sensebuf[14]-->0
sensebuf[15]-->0
sensebuf[16]-->2c
sensebuf[17]-->6b
sensebuf[18]-->0
sensebuf[19]-->0
sensebuf[20]-->0
sensebuf[21]-->0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:3221137944
CDB[0]-->#12
CDB[1]-->#0
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#40
CDB[5]-->#0
Data Direction:SG_DXFER_NONE
Data buffer address:0
CDB[0]-->#0
CDB[1]-->#0
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#0
CDB[5]-->#0
Before third ioctl
Third ioctl is successful
sensebuf[0]-->70
sensebuf[1]-->0
sensebuf[2]-->2
sensebuf[3]-->0
sensebuf[4]-->0
sensebuf[5]-->0
sensebuf[6]-->0
sensebuf[7]-->e
sensebuf[8]-->0
sensebuf[9]-->0
sensebuf[10]-->0
sensebuf[11]-->0
sensebuf[12]-->3a
sensebuf[13]-->0
sensebuf[14]-->0
sensebuf[15]-->0
sensebuf[16]-->2c
sensebuf[17]-->6b
sensebuf[18]-->0
sensebuf[19]-->0
sensebuf[20]-->0
sensebuf[21]-->0
Data Direction:SG_DXFER_NONE
Data buffer address:0
CDB[0]-->#0
CDB[1]-->#0
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#0
CDB[5]-->#0
Before third ioctl
Third ioctl is successful
sensebuf[0]-->70
sensebuf[1]-->0
sensebuf[2]-->2
sensebuf[3]-->0
sensebuf[4]-->0
sensebuf[5]-->0
sensebuf[6]-->0
sensebuf[7]-->e
sensebuf[8]-->0
sensebuf[9]-->0
sensebuf[10]-->0
sensebuf[11]-->0
sensebuf[12]-->3a
sensebuf[13]-->0
sensebuf[14]-->0
sensebuf[15]-->0
sensebuf[16]-->2c
sensebuf[17]-->6b
sensebuf[18]-->0
sensebuf[19]-->0
sensebuf[20]-->0
sensebuf[21]-->0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:3221132156
CDB[0]-->#12
CDB[1]-->#0
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#40
CDB[5]-->#0
Data Direction:SG_DXFER_NONE
Data buffer address:0
CDB[0]-->#0
CDB[1]-->#0
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#0
CDB[5]-->#0
sensebuf[0]-->70
sensebuf[1]-->0
sensebuf[2]-->2
sensebuf[3]-->0
sensebuf[4]-->0
sensebuf[5]-->0
sensebuf[6]-->0
sensebuf[7]-->e
sensebuf[8]-->0
sensebuf[9]-->0
sensebuf[10]-->0
sensebuf[11]-->0
sensebuf[12]-->3a
sensebuf[13]-->0
sensebuf[14]-->0
sensebuf[15]-->0
sensebuf[16]-->2c
sensebuf[17]-->6b
sensebuf[18]-->0
sensebuf[19]-->0
sensebuf[20]-->0
sensebuf[21]-->0
Data Direction:SG_DXFER_NONE
Data buffer address:0
CDB[0]-->#0
CDB[1]-->#0
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#0
CDB[5]-->#0
sensebuf[0]-->70
sensebuf[1]-->0
sensebuf[2]-->2
sensebuf[3]-->0
sensebuf[4]-->0
sensebuf[5]-->0
sensebuf[6]-->0
sensebuf[7]-->e
sensebuf[8]-->0
sensebuf[9]-->0
sensebuf[10]-->0
sensebuf[11]-->0
sensebuf[12]-->3a
sensebuf[13]-->0
sensebuf[14]-->0
sensebuf[15]-->0
sensebuf[16]-->2c
sensebuf[17]-->6b
sensebuf[18]-->0
sensebuf[19]-->0
sensebuf[20]-->0
sensebuf[21]-->0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:3221128232
CDB[0]-->#12
CDB[1]-->#1
CDB[2]-->#80
CDB[3]-->#0
CDB[4]-->#4
CDB[5]-->#0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:3221128508
CDB[0]-->#12
CDB[1]-->#1
CDB[2]-->#c0
CDB[3]-->#0
CDB[4]-->#4
CDB[5]-->#0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:3221128508
CDB[0]-->#12
CDB[1]-->#1
CDB[2]-->#c1
CDB[3]-->#0
CDB[4]-->#4
CDB[5]-->#0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:151844088
CDB[0]-->#12
CDB[1]-->#0
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#5c
CDB[5]-->#0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:152317528
CDB[0]-->#12
CDB[1]-->#1
CDB[2]-->#80
CDB[3]-->#0
CDB[4]-->#e
CDB[5]-->#0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:152500248
CDB[0]-->#12
CDB[1]-->#1
CDB[2]-->#c0
CDB[3]-->#0
CDB[4]-->#60
CDB[5]-->#0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:151813688
CDB[0]-->#12
CDB[1]-->#1
CDB[2]-->#c1
CDB[3]-->#0
CDB[4]-->#60
CDB[5]-->#0
Data Direction:SG_DXFER_NONE
Data buffer address:0
CDB[0]-->#0
CDB[1]-->#0
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#0
CDB[5]-->#0
sensebuf[0]-->70
sensebuf[1]-->0
sensebuf[2]-->2
sensebuf[3]-->0
sensebuf[4]-->0
sensebuf[5]-->0
sensebuf[6]-->0
sensebuf[7]-->e
sensebuf[8]-->0
sensebuf[9]-->0
sensebuf[10]-->0
sensebuf[11]-->0
sensebuf[12]-->3a
sensebuf[13]-->0
sensebuf[14]-->0
sensebuf[15]-->0
sensebuf[16]-->2c
sensebuf[17]-->6b
sensebuf[18]-->0
sensebuf[19]-->0
sensebuf[20]-->0
sensebuf[21]-->0
Data Direction:SG_DXFER_NONE
Data buffer address:0
CDB[0]-->#0
CDB[1]-->#0
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#0
CDB[5]-->#0
sensebuf[0]-->70
sensebuf[1]-->0
sensebuf[2]-->2
sensebuf[3]-->0
sensebuf[4]-->0
sensebuf[5]-->0
sensebuf[6]-->0
sensebuf[7]-->e
sensebuf[8]-->0
sensebuf[9]-->0
sensebuf[10]-->0
sensebuf[11]-->0
sensebuf[12]-->3a
sensebuf[13]-->0
sensebuf[14]-->0
sensebuf[15]-->0
sensebuf[16]-->2c
sensebuf[17]-->6b
sensebuf[18]-->0
sensebuf[19]-->0
sensebuf[20]-->0
sensebuf[21]-->0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:3221127360
CDB[0]-->#3c
CDB[1]-->#3
CDB[2]-->#11
CDB[3]-->#0
CDB[4]-->#0
CDB[5]-->#0
CDB[6]-->#0
CDB[7]-->#0
CDB[8]-->#4
CDB[9]-->#0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:3221127360
CDB[0]-->#3c
CDB[1]-->#3
CDB[2]-->#12
CDB[3]-->#0
CDB[4]-->#0
CDB[5]-->#0
CDB[6]-->#0
CDB[7]-->#0
CDB[8]-->#4
CDB[9]-->#0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:3221127360
CDB[0]-->#3c
CDB[1]-->#3
CDB[2]-->#13
CDB[3]-->#0
CDB[4]-->#0
CDB[5]-->#0
CDB[6]-->#0
CDB[7]-->#0
CDB[8]-->#4
CDB[9]-->#0
Data Direction:SG_DXFER_TO_DEV
Data buffer address:142959164
CDB[0]-->#1d
CDB[1]-->#1
CDB[2]-->#0
CDB[3]-->#0
CDB[4]-->#8
CDB[5]-->#0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:151416608
CDB[0]-->#1c
CDB[1]-->#0
CDB[2]-->#93
CDB[3]-->#0
CDB[4]-->#90
CDB[5]-->#0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:3221127980
CDB[0]-->#1c
CDB[1]-->#1
CDB[2]-->#a5
CDB[3]-->#0
CDB[4]-->#4
CDB[5]-->#0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:3221127968
CDB[0]-->#1c
CDB[1]-->#1
CDB[2]-->#a5
CDB[3]-->#0
CDB[4]-->#4
CDB[5]-->#0
Data Direction:SG_DXFER_FROM_DEV
Data buffer address:3221127980
CDB[0]-->#1c
CDB[1]-->#1
CDB[2]-->#84
CDB[3]-->#0
CDB[4]-->#4
CDB[5]-->#0
Before third ioctl
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-02-11 13:22 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-10 5:15 Kernel panic on Redhat Linux AS2.1 with QLogic 2342 HBA veeresh
2004-02-10 12:21 ` Matthew Wilcox
2004-02-10 18:25 ` Andrew Vasquez
2004-02-11 1:36 ` Joel Becker
2004-02-11 13:21 ` veeresh
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox