08271d9c: [<0808b029>] __atomic_notifier_call_chain+0x17/0x19
08271dac: [<0808b040>] atomic_notifier_call_chain+0x15/0x17
08271dc8: [<081f3b60>] panic+0x81/0x157
08271df0: [<0805f681>] segv+0x107/0x242
08271e9c: [<0805f811>] segv_handler+0x55/0x60
08271ec4: [<0806b1ae>] sig_
Hi,
I'm running a 3.4.47 UML kernel on a 3.4.47 system.
Recently I got the following warning, just before the UML guest system
became unresponsive:
[ cut here ]
WARNING: at kernel/softirq.c:159 local_bh_enable+0x3b/0x8b()
Modules linked in:
21274430: [<081f3adb>] dump_st
Hi,
On the following page:
http://user-mode-linux.sourceforge.net/old/projects.html
There is a link to a patch by Johan Verrept that adds some USB support
to UML:
http://user-mode-linux.sourceforge.net/old/patches/uml-hcd-2.4.3.patch
Unfortunately, this is from 2001, and is for
On Thu, Oct 14, 2010 at 03:14:28PM +0200, Tejun Heo wrote:
> Hello,
>
> Can you please try this one then? It seems to work here but I can't
> reproduce the original problem reliably so I'm not really sure.
>
> Thanks.
>
> diff --git a/arch/um/drivers/ubd_kern.c b/arch/um/drivers/ubd_kern.c
> in
On Thu, Oct 07, 2010 at 09:58:16AM +0200, Jens Axboe wrote:
> So how about this? Note that I haven't even compiled this. The request
> handling logic really should be fixed in there, it's horribly
> inefficient.
Thanks. I fixed the compile error with:
> + .rq_offset 0, \
to
>
On Mon, Oct 04, 2010 at 06:37:36PM +0200, Tejun Heo wrote:
> Hello, sorry about chiming in later. I was off last week.
No problem, I'm eager to test patches to fix this.
> I think we're on the right track. The problem with Jens' patch was
> that it didn't consider the fact that blk_end_request
On Tue, Oct 05, 2010 at 10:23:19AM +0200, Tejun Heo wrote:
> H, can you please give a shot at the following one? Thank you.
I applied this patch on top of stock 2.6.35.5 as usual (no other patches)
and tested on my maverick image as before. I ran a fsck.ext3 on the
filesystem image from the
On Sat, Oct 02, 2010 at 12:03:04AM +0200, richard -rw- weinberger wrote:
> Hi,
>
> I'm seeing often messages like this one on my UML:
> ...
> INFO: rcu_sched_state detected stall on CPU 0 (t=7348 jiffies)
> ...
>
> The system often seems to be frozen.
> When I press a button it wakes up immediate
On Wed, Sep 29, 2010 at 12:13:10AM +0200, Richard Weinberger wrote:
> Am Mittwoch 29 September 2010, 00:00:00 schrieb Andrew Morton:
> > This is a workaround, I think? Do we know what the actual bug is?
> > From the comment it appears to be a regression?
>
> Yes, it is a workaround.
> For more de
On Wed, Sep 29, 2010 at 12:13:10AM +0200, Richard Weinberger wrote:
> Am Mittwoch 29 September 2010, 00:00:00 schrieb Andrew Morton:
> > This is a workaround, I think? Do we know what the actual bug is?
> > From the comment it appears to be a regression?
>
> Yes, it is a workaround.
> For more de
On Wed, Sep 29, 2010 at 08:10:06AM +0900, Jens Axboe wrote:
> It looks like that if we need to restart the requeue, then
> we use the initial position and not the current index. Does
> this help?
>
> diff --git a/arch/um/drivers/ubd_kern.c b/arch/um/drivers/ubd_kern.c
> index 1bcd208..81ee063 1006
On Wed, Sep 29, 2010 at 02:21:07PM +0900, Jens Axboe wrote:
> This seems to imply that the original commit pin pointed is not
> the only issue we have in that code atm.
>
> I think we need to find the real fix here, just disabling merging
> is not a fix (it's just a nasty work-around for the real
Hi,
I thought it might be useful to point to the linux-kernel thread on
the same topic, which can be found here:
http://marc.info/?t=12853028071&r=1&w=2
So far, Richard Weinberger and I have reproduced the problem.
Additional tips or fixes are quite welcome.
Thanks,
- Chris
--
13 matches
Mail list logo
