Re: iscsi crash

[6bone%6bone.informatik.uni-leipzig.de@localhost]

On Sat, 4 Jan 2014, Michael van Elst wrote:

> Lets assume with "crashes" you mean that a command entered into the
> shell on the console does not return.
>
> - Can you still type and get characters echoed?
> - Does the machine react to pings from the network?

If I enter any characters, the characters are not shown. At the console 
you get no echo either. The server still answers to pings.

If I force to enter the ddb at the console, I get the following trace:

fatal breakpoint trap in supervisor mode
trap type 1 code 0
Stopped in pid 831.2 (iscsid)
db{0}> trace
breakpoint() at netbsd:breakpoint+0x5
wskbd_translate() at netbsd:wskbd_translate+0x9ac
wskbd_input() at netbsd:wskbd_input+0xb4
wskbd_input() at netbsd:wskbd_input+0x3e
pckbcintr() at netbsd:pckbcintr+0x5d
intr_biglock_wrapper() at netbsd:intr_biglock_wrapper+0x1d
Xintr_ioapic_edge10() at netbsd:Xintr_ioapic_edge10+0xea
--- interrupt ---
iscsiioctl() at netbsd:iscsiioctl+0xbc0
cdev_ioctl() at netbsd:cdev_ioctl+0x77
VOP_IOCTL() at netbsd:VOP_IOCTL+0x3b
vn_ioctl() at netbsd:sys_ioctl+0x13c
sys_ioctl() at netbsd:sys_ioctl+0x13c
syscall() at netbsd:syscall+0xc4

> So this is a custom non-modular kernel? Any chance to use a modular
> GENERIC kernel?

You are right. It is a custom kernel. The option

options         MODULAR         # new style module(7) framework

is configured. So I think the kernel is modular. The GENERIC kernel does 
not work because the option 'pseudo-device iscsi' is needed but not set in 
GENERIC.



Regards
Uwe