linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] ZONE_DMA and dm_create->init_emergency_isa_pool
Date: Thu, 7 Dec 2006 20:27:45 +0100	[thread overview]
Message-ID: <200612072027.46049.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20061203210608.GA2704@cube.dyndns.org>

On Sunday 03 December 2006 22:06, rsnel@cube.dyndns.org wrote:
> Hello,
>
> When I want to create a device mapper table in user-mode-linux, I get
>
> BUG: failure at mm/bounce.c:85/init_emergency_isa_pool()!
> (full stack trace below)
>
> I think this behaviour was introduced by:
> [PATCH] uml: get rid of ZONE_DMA use
>
> I got it to work by reversing the patch.
Can you detail the used UML version? Thanks.
> Greetings,
>
> Rik.
>
> Trace:
> BUG: failure at mm/bounce.c:85/init_emergency_isa_pool()!
> Kernel panic - not syncing: BUG!
>
>  EIP: 0073:[<401300c4>] CPU: 0 Not tainted ESP: 007b:bf433948 EFLAGS:
>  00000246
>      Not tainted
>      EAX: ffffffda EBX: 00000003 ECX: c134fd03 EDX: 08050408
>      ESI: 400287c0 EDI: 40026180 EBP: bf433a98 DS: 007b ES: 007b
>      0901bd78:  [<080686b0>] show_regs+0xb4/0xb9
>      0901bda4:  [<0805a4c3>] panic_exit+0x25/0x3f
>      0901bdb8:  [<0807b018>] notifier_call_chain+0x1d/0x3c
>      0901bdd8:  [<0807b0a7>] atomic_notifier_call_chain+0x11/0x13
>      0901bdec:  [<0806f96e>] panic+0x52/0xdd
>      0901be0c:  [<0809b91b>] init_emergency_isa_pool+0x4b/0x5d
>      0901be28:  [<080f3cbd>] blk_queue_bounce_limit+0x33/0x48
>      0901be3c:  [<081106a5>] alloc_dev+0xf4/0x285
>      0901be64:  [<081109c1>] dm_create+0xb/0x20
>      0901be70:  [<08113205>] dev_create+0x3f/0x9b
>      0901be90:  [<08114047>] ctl_ioctl+0xd7/0x10e
>      0901beb8:  [<080ae385>] do_ioctl+0x45/0x5a
>      0901bed8:  [<080ae717>] vfs_ioctl+0x1ec/0x209
>      0901bf00:  [<080ae762>] sys_ioctl+0x2e/0x4c
>      0901bf28:  [<0805ac46>] handle_syscall+0x86/0xa0
>      0901bf74:  [<08065805>] handle_trap+0xbe/0xc7
>      0901bf90:  [<08065bf3>] userspace+0x123/0x166
>      0901bfdc:  [<0805a985>] fork_handler+0x74/0x7c
>      0901bffc:  [<a55a5a5a>] 0xa55a5a5a

-- 
Inform me of my mistakes, so I can add them to my list!
Paolo Giarrusso, aka Blaisorblade
http://www.user-mode-linux.org/~blaisorblade
Chiacchiera con i tuoi amici in tempo reale! 
 http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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:[~2006-12-07 19:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-03 21:06 [uml-devel] ZONE_DMA and dm_create->init_emergency_isa_pool rsnel
2006-12-07 19:27 ` Blaisorblade [this message]
2006-12-07 20:18   ` rsnel

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=200612072027.46049.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox