search for: mapcounts

I have gotten a hard system lockup several times using star on my system with a Quantum DLT-V4 SATA tape drive. I am including what got recorded in /var/log/messages from the most recent event showing stack trace. Output from uname -a: Linux lh10 2.6.9-78.0.13.ELsmp #1 SMP Wed Jan 14 15:55:36 EST 2009 x86_64 x86_64 x86_64 GNU/Linux Mar 22 22:02:59 lh10 kernel: Bad page state at

On Thu, Jun 16, 2016 at 02:22:09PM +0900, Sergey Senozhatsky wrote: > On (06/16/16 13:47), Minchan Kim wrote: > [..] > > > this is what I'm getting with the [zsmalloc: keep first object offset in struct page] > > > applied: "count:0 mapcount:-127". which may be not related to zsmalloc at this point. > > > > > > kernel: BUG: Bad page state

On Thu, Jun 16, 2016 at 02:22:09PM +0900, Sergey Senozhatsky wrote: > On (06/16/16 13:47), Minchan Kim wrote: > [..] > > > this is what I'm getting with the [zsmalloc: keep first object offset in struct page] > > > applied: "count:0 mapcount:-127". which may be not related to zsmalloc at this point. > > > > > > kernel: BUG: Bad page state

On Thu, Jun 16, 2016 at 01:23:43PM +0900, Sergey Senozhatsky wrote: > On (06/16/16 11:58), Minchan Kim wrote: > [..] > > RAX: 2065676162726166 so rax is totally garbage, I think. > > It means obj_to_head returns garbage because get_first_obj_offset is > > utter crab because (page_idx / class->pages_per_zspage) was totally > > wrong. > > > > >

On Thu, Jun 16, 2016 at 01:23:43PM +0900, Sergey Senozhatsky wrote: > On (06/16/16 11:58), Minchan Kim wrote: > [..] > > RAX: 2065676162726166 so rax is totally garbage, I think. > > It means obj_to_head returns garbage because get_first_obj_offset is > > utter crab because (page_idx / class->pages_per_zspage) was totally > > wrong. > > > > >

These mappings are in fact special and require special handling in privcmd, which already exists. Failure to mark the PTE as special on arm64 causes all sorts of bad PTE fun. x86 already gets this correct. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Cc: xen-devel@lists.xenproject.org --- arch/arm/xen/enlighten.c |

On Thu, Jun 16, 2016 at 05:42:11PM +0900, Sergey Senozhatsky wrote: > On (06/16/16 15:47), Minchan Kim wrote: > > > [..] > > > > > this is what I'm getting with the [zsmalloc: keep first object offset in struct page] > > > > > applied: "count:0 mapcount:-127". which may be not related to zsmalloc at this point. > > > > > >

On Thu, Jun 16, 2016 at 05:42:11PM +0900, Sergey Senozhatsky wrote: > On (06/16/16 15:47), Minchan Kim wrote: > > > [..] > > > > > this is what I'm getting with the [zsmalloc: keep first object offset in struct page] > > > > > applied: "count:0 mapcount:-127". which may be not related to zsmalloc at this point. > > > > > >

On Thu, Jun 16, 2016 at 11:48:27AM +0900, Sergey Senozhatsky wrote: > Hi, > > On (06/16/16 08:12), Minchan Kim wrote: > > > [ 315.146533] kasan: CONFIG_KASAN_INLINE enabled > > > [ 315.146538] kasan: GPF could be caused by NULL-ptr deref or user memory access > > > [ 315.146546] general protection fault: 0000 [#1] PREEMPT SMP KASAN > > > [

On Thu, Jun 16, 2016 at 11:48:27AM +0900, Sergey Senozhatsky wrote: > Hi, > > On (06/16/16 08:12), Minchan Kim wrote: > > > [ 315.146533] kasan: CONFIG_KASAN_INLINE enabled > > > [ 315.146538] kasan: GPF could be caused by NULL-ptr deref or user memory access > > > [ 315.146546] general protection fault: 0000 [#1] PREEMPT SMP KASAN > > > [

I recently upgraded wine from 0.9.7 to 0.9.12 and while checking out that things were working I started up Google Earth but had the following error in terminal: Message from syslogd@TheVoid at Sun May 7 02:40:26 2006 ... TheVoid kernel: Bad page state at free_hot_cold_page (in process 'GoogleEarth.exe', page c125be60) Message from syslogd@TheVoid at Sun May 7 02:40:26 2006 ... TheVoid

On (06/16/16 13:47), Minchan Kim wrote: [..] > > this is what I'm getting with the [zsmalloc: keep first object offset in struct page] > > applied: "count:0 mapcount:-127". which may be not related to zsmalloc at this point. > > > > kernel: BUG: Bad page state in process khugepaged pfn:101db8 > > kernel: page:ffffea0004076e00 count:0 mapcount:-127

I am having a xen 2.0.7 server crash, This is the first message i managed to get out of syslog, I didnt think it was related untill when i did ''xm shutdown mls'' the dom0 also goes down that i thought it might be related, I will see if not running gkrellmd in domU''s will help with this Message from syslogd@michiganlivestock.com at Fri Nov 11 17:25:02 2005 ...

On (06/16/16 11:58), Minchan Kim wrote: [..] > RAX: 2065676162726166 so rax is totally garbage, I think. > It means obj_to_head returns garbage because get_first_obj_offset is > utter crab because (page_idx / class->pages_per_zspage) was totally > wrong. > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > 6408: f0 0f ba 28 00 lock btsl $0x0,(%rax)

I have installed two CentOS 4.3 boxes with LVS (from http://mirror.centos.org/centos/4/csgfs/ ) but all boxes died withe this error frequently: kernel panic - not syncing: fs/block_dev.c:396: spin_lock (fs/block_dev.c:c0361c0) already locked by fs/block_dev.c/287. I have read from this thread http://threebit.net/mail-archive/centos/msg00243.html that this is an unsolved problem. So i have

On Tue, Nov 12, 2024 at 03:22:46PM +0100, David Hildenbrand wrote: > On 12.11.24 14:53, Jason Gunthorpe wrote: > > On Tue, Nov 12, 2024 at 10:10:06AM +0100, David Hildenbrand wrote: > > > On 12.11.24 06:26, Matthew Wilcox wrote: > > > > I don't want you to respin. I think this is a bad idea. > > > > > > I'm hoping you'll find some more

- introduce local variables (shortcuts for frequently used <dom>->grant_table) - adjust first parameter of mapcount() - drop lock acquisition from gnttab_get_version() - remove hard tabs and adjust formatting Signed-off-by: Jan Beulich <jbeulich@suse.com> Tested-by: Andrew Thomas <andrew.thomas@oracle.com> --- a/xen/common/grant_table.c +++ b/xen/common/grant_table.c @@

A migrating transparent huge page has to already be unmapped. Otherwise, the page could be modified while it is being copied to a new page and data could be lost. The function __split_huge_pmd() checks for a PMD migration entry before calling __split_huge_pmd_locked() leading one to think that __split_huge_pmd_locked() can handle splitting a migrating PMD. However, the code always increments the

On (06/16/16 15:47), Minchan Kim wrote: > > [..] > > > > this is what I'm getting with the [zsmalloc: keep first object offset in struct page] > > > > applied: "count:0 mapcount:-127". which may be not related to zsmalloc at this point. > > > > > > > > kernel: BUG: Bad page state in process khugepaged pfn:101db8 > > >

In a word, is it stable? I''m seeing some odd things; segfaults by postgres in a domU, when pae is enabled. And, this last time, I got this on the ssh I had to the domU: == database:/home/shared/doogie# Message from syslogd@database at Wed Dec 14 18:55:05 2005 ... database kernel: [27073.874149] Bad page state at prep_new_page (in process ''postmaster'', page c1326ca0)