All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dave Humphreys (Bob)" <dave@bob-the-boat.me.uk>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] UML Network Related Crashing
Date: Sat, 05 Jan 2013 15:18:17 +0000	[thread overview]
Message-ID: <1558576.MRf0N3N32R@localhost> (raw)


I have problems with UML crashing that I believe are network related, because the crash happens whenever I try to make heavier use of the network connection to rsync more significant amounts of data from the UML.

It may or may not be significant, but when I am rsyncing from one UML to another, it has so far always been the one that is supplying the data that has crashed.

I have this with a UML that is accessed via a tap link and a real network connection, and also between two UMLs on the same host communicating via an 'mcast' connection.

Most of the time the affected UML simply locks up, and I can't do anything with it. Even if I try to drive it with uml_mconsole, that will not communicate with the UML. I sometimes see the ---[cut]--- type of output, but it doesn't get beyond that line. Sometimes I see no output before the thing locks up.

I've been experimenting with two UML instances communicating via mcast on my local machine, and I have experienced this output:

-bash-4.2# /sbin/sshd                                                                                                                                                                                                                                                          
-bash-4.2#                                                                                                                                                                                                                                                                     
EIP: 0023:[<08075749>] CPU: 0 Not tainted ESP: 002b:165fffb8 EFLAGS: 00010206                                                                                                                                                                                                  
    Not tainted                                                                                                                                                                                                                                                                
EAX: 963523cf EBX: 16600638 ECX: 01400002 EDX: 01400000                                                                                                                                                                                                                        
ESI: 0a0d4828 EDI: 00000000 EBP: 165fffbc DS: 002b ES: 002b
0837a750:  [<0806cf3a>] show_regs+0xc0/0xc6
0837a77c:  [<0805cd42>] segv+0x202/0x218
0837a81c:  [<0805cdaa>] segv_handler+0x52/0x5d
0837a848:  [<08068a5f>] sig_handler_common+0x79/0x8c
0837aac8:  [<08068b4d>] sig_handler+0x34/0x43
0837aad4:  [<080687e2>] hard_handler+0x5a/0x88
0837aafc:  [<ffffe410>] 0xffffe410

Kernel panic - not syncing: Kernel mode fault at addr 0x963524a7, ip 0x8075749
0837a744:  [<08249cc3>] dump_stack+0x16/0x1a
0837a758:  [<08249d4d>] panic+0x67/0x149
0837a770:  [<0805cd4e>] segv+0x20e/0x218
0837a81c:  [<0805cdaa>] segv_handler+0x52/0x5d
0837a848:  [<08068a5f>] sig_handler_common+0x79/0x8c
0837aac8:  [<08068b4d>] sig_handler+0x34/0x43
0837aad4:  [<080687e2>] hard_handler+0x5a/0x88
0837aafc:  [<ffffe410>] 0xffffe410


EIP: 0023:[<400010c2>] CPU: 0 Not tainted ESP: 002b:ff5a8674 EFLAGS: 00000212
    Not tainted
EAX: ffffffda EBX: ff5a87f0 ECX: ff5a8790 EDX: 401edff4
ESI: 00000000 EDI: ff5a87f0 EBP: ff5a8790 DS: 002b ES: 002b
0837a6b4:  [<0806cf3a>] show_regs+0xc0/0xc6
0837a6e0:  [<0805cfd3>] panic_exit+0x20/0x36
0837a6f4:  [<08088af7>] notifier_call_chain+0x20/0x4b
0837a71c:  [<08088b39>] __atomic_notifier_call_chain+0x17/0x19
0837a72c:  [<08088b50>] atomic_notifier_call_chain+0x15/0x17
0837a748:  [<08249d65>] panic+0x7f/0x149
0837a770:  [<0805cd4e>] segv+0x20e/0x218
0837a81c:  [<0805cdaa>] segv_handler+0x52/0x5d
0837a848:  [<08068a5f>] sig_handler_common+0x79/0x8c
0837aac8:  [<08068b4d>] sig_handler+0x34/0x43
0837aad4:  [<080687e2>] hard_handler+0x5a/0x88
0837aafc:  [<ffffe410>] 0xffffe410

Terminated
bash-4.1# 

What happened here was that I started two virtually identical UML instances on the same host, communicating with each other via mcast interfaces. I started sshd on one of them and then started to rsync data from it to the other. After a short while I got the above.

I have a UML running on a remote machine that I access via the Internet. I can always crash this when I try to copy data from it, and I assume that the above represents the same fault. I'm happy to do any testing required to try to help fix this.

David Humphreys



------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122912
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel


             reply	other threads:[~2013-01-05 15:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 15:18 Dave Humphreys (Bob) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-01-06 12:16 [uml-devel] UML Network Related Crashing Dave Humphreys (Bob)
2013-01-06 12:26 ` Richard Weinberger
2013-01-19 18:59 Dave Humphreys (Bob)
2013-01-22  6:07 ` Dave (Bob)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1558576.MRf0N3N32R@localhost \
    --to=dave@bob-the-boat.me.uk \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.