linux-kernel - Re: linux-next: Tree for Jun 26 [ vfs | block

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 26 Jun 2013 11:50:48 +0200
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Al Viro <viro@...iv.linux.org.uk>,
	Jens Axboe <axboe@...nel.dk>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>,
	Miklos Szeredi <miklos@...redi.hu>,
	fuse-devel@...ts.sourceforge.net
Subject: Re: linux-next: Tree for Jun 26 [ vfs | block | fuse (cpuidle)
 releated? ]

On Wed, Jun 26, 2013 at 11:48 AM, Sedat Dilek <sedat.dilek@...il.com> wrote:
> On Wed, Jun 26, 2013 at 10:06 AM, Stephen Rothwell <sfr@...b.auug.org.au> 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!
>

Just as a sidenote:

This is not a ***native*** Ubuntu/precise AMD64 installation - I am
using a WUBI environment.

- Sedat -

https://wiki.ubuntu.com/WubiGuide

> Regards,
> - Sedat -
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/