Bug 195145
| Summary: | net/iet kernel panic on FreeBSD 10.1 release (x64) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | patdung100 | ||||||||
| Component: | Individual Port(s) | Assignee: | Xin LI <delphij> | ||||||||
| Status: | Closed Overcome By Events | ||||||||||
| Severity: | Affects Only Me | CC: | emaste, rene, trasz | ||||||||
| Priority: | --- | ||||||||||
| Version: | Latest | ||||||||||
| Hardware: | amd64 | ||||||||||
| OS: | Any | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 149556 [details]
core.txt.0
Created attachment 149557 [details]
iet port info
Update product and summary; the panic comes from the port's kernel code. I don't know IET that well, it's a third party software ported from Linux, but is there any reason to use it instead of the native target (ctld)? Well, I was doing some testing with ietd and compare with cltd. I thought FreeBSD kernel is stable and should not have crashed easily. Anyway, if there is no big issue, please consider ticket to have lower priority or closed it later. > I thought FreeBSD kernel is stable and should not have crashed easily.
It's not really feasible for us to protect against bugs in kernel code that comes from a 3rd party. The net/iet maintainers or upstream should take a look at this, but presumably over time everyone will transition to the native built-in stack.
Totally agree. Over to maintainer. Port expired and removed |
Created attachment 149555 [details] kgdb where 1. install iet by: # pkg install iet 2. setup ietd.conf: Target iqn.2010-09.org.openindiana:02:gp2esx-clu Lun 0 Path=/dev/zvol/storage/gp2esx1,Type=blockio,ScsiId=6589cfc000000003,ScsiSN=ODJLMJNJND Lun 1 Path=/dev/zvol/storage/gp2esx2,Type=blockio,ScsiId=6589cfc000000004,ScsiSN=YWM5NJQ5OD 3. start ietd 4. client (vmware esxi 5.1 connect to iscsi target) 5. FreeBSD 10.1 iscsi target server crashed 6. attached is the related crash debug info