Setting to confirmed since it's a kernel bug (albeit in external module it
seems reasonable to treat the same way)
High->seems appropriate for oops on server.
Gavin:
Can you paste more of the syslog please; in particular is there are a line of
4 numbers just before it ; I can see an eprintk in the iscsi code that looks
like it might trigger on the path I think it might be hitting (there is an
assert at line 1053 in the code I'm looking at, although it's slightly newer).
Also, is the oops identical every time you hit it?
Dave
** Changed in: iscsitarget (Ubuntu)
Importance: Undecided => High
** Changed in: iscsitarget (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078398
Title:
iscsitarget causing kernel lockup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iscsitarget/+bug/1078398/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
