Re: linux-next: Tree for Jun 26 [ vfs | block | fuse (cpuidle)releated? ]

[Sedat Dilek]

On Wed, Jun 26, 2013 at 10:06 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
> Hi all,
>
> Changes since 20130625:
>
> New tree: cpuinit
>
> The arm-mpidr tree gained a conflict against the arm tree.
>
> The net-next tree gained a conflict against the pm tree and a build
> failure for which I reverted a commit.
>
> The drm-intel tree gained a conflict against Linus' tree.
>
> The pinctrl tree gained a conflict against the regmap tree.
>
> The akpm tree lost a patch that turned up elsewhere and gained a conflict
> against the powerpc tree.
>
> The cpuinit tree lost a patch that turned up in the arc tree and gained a
> conflict against the arm-current tree.
>
> ----------------------------------------------------------------------------
>

[ CC some vfs | block | fuse maintainers ]

Since yesterday (next-20130625) and today (next-20130626) I can NOT
boot into my -next kernels.

I have seen two traces whereas I would like to concentrate on Trace #1.

Trace #1 (noted manually, read from the screen):
...
general_protection
spin_dump
spin_bug
do_raw_spin_lock
_raw_spin_locking
rwsem_spin_locking
rwsem_downwrite_failed
_rwsem_downwrite_failed
call_rwsem_downwrite_failed
downwrite
fuse_kill_sb_blk
deactivate_locked_super
mount_bdev
fuse_iget
fuse_mountblk
mount_fs
vfs_kern_mount
do_mount
__get_free_pages
copy_mount_options
SyS_mount
tracesys

Trace #2 (noted manually, read from the screen):
...
blablabla cpuidle
...
arch_trigger_all_cpu_backtrace_handler

I have attached my kernel-config.

Any hints/feedback welcome!

Regards,
- Sedat -

Attachment: config-3.10.0-rc7-next20130626-1-iniza-small
Description: Binary data