search for: 0x240

Displaying 20 results from an estimated 243 matches for "0x240".

Did you mean: 0x20
2017 Jun 05
0
BUG: KASAN: use-after-free in free_old_xmit_skbs
...310.085884] tcp_transmit_skb+0x187a/0x3e00 > > [ 310.086696] ? __tcp_select_window+0xaf0/0xaf0 > > [ 310.087524] ? sock_sendmsg+0xba/0xf0 > > [ 310.088298] ? __vfs_write+0x4e0/0x960 > > [ 310.089074] ? vfs_write+0x155/0x4b0 > > [ 310.089838] ? SyS_write+0xf7/0x240 > > [ 310.090593] ? do_syscall_64+0x235/0x5b0 > > [ 310.091372] ? entry_SYSCALL64_slow_path+0x25/0x25 > > [ 310.094690] ? sock_sendmsg+0xba/0xf0 > > [ 310.096133] ? do_syscall_64+0x235/0x5b0 > > [ 310.097593] ? entry_SYSCALL64_slow_path+0x25/0x25 > > [...
2017 Jun 05
0
BUG: KASAN: use-after-free in free_old_xmit_skbs
...310.085884] tcp_transmit_skb+0x187a/0x3e00 > > [ 310.086696] ? __tcp_select_window+0xaf0/0xaf0 > > [ 310.087524] ? sock_sendmsg+0xba/0xf0 > > [ 310.088298] ? __vfs_write+0x4e0/0x960 > > [ 310.089074] ? vfs_write+0x155/0x4b0 > > [ 310.089838] ? SyS_write+0xf7/0x240 > > [ 310.090593] ? do_syscall_64+0x235/0x5b0 > > [ 310.091372] ? entry_SYSCALL64_slow_path+0x25/0x25 > > [ 310.094690] ? sock_sendmsg+0xba/0xf0 > > [ 310.096133] ? do_syscall_64+0x235/0x5b0 > > [ 310.097593] ? entry_SYSCALL64_slow_path+0x25/0x25 > > [...
2011 May 19
1
Centos 5.6 kernel errors
...d7c c011bd9b e8ca6000 e8c6f788 e8c6f740 e8cffd90 c011be50 e8c6f740 14857 kernel: e8cffde8 00007ff0 e8cffe20 c0170a8a e8c6f740 e8c6f740 c030b547 e8cffdb8 14857 kernel: Call Trace: 14857 kernel: [<c01058bd>] show_stack_log_lvl+0xcd/0x120 14857 kernel: [<c0105abb>] show_registers+0x1ab/0x240 14857 kernel: [<c0105dc1>] die+0x111/0x240 14857 kernel: [<c01130a7>] do_page_fault+0x5f7/0x931 14857 kernel: [<c01052ab>] error_code+0x2b/0x30 14857 kernel: [<c011bd9b>] __mmdrop+0x1b/0x50 14857 kernel: [<c011be50>] mmput+0x80/0xa0 14857 kernel: [<c0170a8a&gt...
2020 Oct 23
0
kvm+nouveau induced lockdep gripe
...] setup_irq_thread+0x37/0x90 [ 70.135312] __setup_irq+0x4e0/0x7c0 [ 70.135318] request_threaded_irq+0xf8/0x160 [ 70.135371] nvkm_pci_oneinit+0x4c/0x70 [nouveau] [ 70.135399] nvkm_subdev_init+0x60/0x1e0 [nouveau] [ 70.135449] nvkm_device_init+0x10b/0x240 [nouveau] [ 70.135506] nvkm_udevice_init+0x49/0x70 [nouveau] [ 70.135531] nvkm_object_init+0x3d/0x180 [nouveau] [ 70.135555] nvkm_ioctl_new+0x1a1/0x260 [nouveau] [ 70.135578] nvkm_ioctl+0x10a/0x240 [nouveau] [ 70.135600] nvif_object_ctor+0xeb/0x150 [nouv...
2014 Jun 27
2
virt_blk BUG: sleeping function called from invalid context
...(): 1, pid: 0, name: swapper/1 2 locks held by swapper/1/0: #0: (&(&vblk->vq_lock)->rlock){-.-...}, at: [<ffffffffa0039042>] virtblk_done+0x42/0xe0 [virtio_blk] #1: (&(&bitmap->counts.lock)->rlock){-.....}, at: [<ffffffff81633718>] bitmap_endwrite+0x68/0x240 irq event stamp: 33518 hardirqs last enabled at (33515): [<ffffffff8102544f>] default_idle+0x1f/0x230 hardirqs last disabled at (33516): [<ffffffff818122ed>] common_interrupt+0x6d/0x72 softirqs last enabled at (33518): [<ffffffff810a1272>] _local_bh_enable+0x22/0x50 softirq...
2014 Jun 27
2
virt_blk BUG: sleeping function called from invalid context
...(): 1, pid: 0, name: swapper/1 2 locks held by swapper/1/0: #0: (&(&vblk->vq_lock)->rlock){-.-...}, at: [<ffffffffa0039042>] virtblk_done+0x42/0xe0 [virtio_blk] #1: (&(&bitmap->counts.lock)->rlock){-.....}, at: [<ffffffff81633718>] bitmap_endwrite+0x68/0x240 irq event stamp: 33518 hardirqs last enabled at (33515): [<ffffffff8102544f>] default_idle+0x1f/0x230 hardirqs last disabled at (33516): [<ffffffff818122ed>] common_interrupt+0x6d/0x72 softirqs last enabled at (33518): [<ffffffff810a1272>] _local_bh_enable+0x22/0x50 softirq...
2014 Jul 01
3
[PATCH driver-core-linus] kernfs: kernfs_notify() must be useable from non-sleepable contexts
...(): 1, pid: 0, name: swapper/1 2 locks held by swapper/1/0: #0: (&(&vblk->vq_lock)->rlock){-.-...}, at: [<ffffffffa0039042>] virtblk_done+0x42/0xe0 [virtio_blk] #1: (&(&bitmap->counts.lock)->rlock){-.....}, at: [<ffffffff81633718>] bitmap_endwrite+0x68/0x240 irq event stamp: 33518 hardirqs last enabled at (33515): [<ffffffff8102544f>] default_idle+0x1f/0x230 hardirqs last disabled at (33516): [<ffffffff818122ed>] common_interrupt+0x6d/0x72 softirqs last enabled at (33518): [<ffffffff810a1272>] _local_bh_enable+0x22/0x50 softirq...
2014 Jul 01
3
[PATCH driver-core-linus] kernfs: kernfs_notify() must be useable from non-sleepable contexts
...(): 1, pid: 0, name: swapper/1 2 locks held by swapper/1/0: #0: (&(&vblk->vq_lock)->rlock){-.-...}, at: [<ffffffffa0039042>] virtblk_done+0x42/0xe0 [virtio_blk] #1: (&(&bitmap->counts.lock)->rlock){-.....}, at: [<ffffffff81633718>] bitmap_endwrite+0x68/0x240 irq event stamp: 33518 hardirqs last enabled at (33515): [<ffffffff8102544f>] default_idle+0x1f/0x230 hardirqs last disabled at (33516): [<ffffffff818122ed>] common_interrupt+0x6d/0x72 softirqs last enabled at (33518): [<ffffffff810a1272>] _local_bh_enable+0x22/0x50 softirq...
2020 Oct 24
1
kvm+nouveau induced lockdep gripe
...+0x37/0x90 > [ 70.135312] __setup_irq+0x4e0/0x7c0 > [ 70.135318] request_threaded_irq+0xf8/0x160 > [ 70.135371] nvkm_pci_oneinit+0x4c/0x70 [nouveau] > [ 70.135399] nvkm_subdev_init+0x60/0x1e0 [nouveau] > [ 70.135449] nvkm_device_init+0x10b/0x240 [nouveau] > [ 70.135506] nvkm_udevice_init+0x49/0x70 [nouveau] > [ 70.135531] nvkm_object_init+0x3d/0x180 [nouveau] > [ 70.135555] nvkm_ioctl_new+0x1a1/0x260 [nouveau] > [ 70.135578] nvkm_ioctl+0x10a/0x240 [nouveau] > [ 70.135600] nvif_obj...
2014 Oct 20
0
[PATCH v4 13/25] virtio_console: enable VQs early
...> [ 1.840169] [<ffffffff810b1250>] ? process_one_work+0x530/0x530 > [ 1.840169] [<ffffffff810b67c3>] kthread+0xf3/0x110 > [ 1.840169] [<ffffffff81788f00>] ? _raw_spin_unlock_irq+0x30/0x50 > [ 1.840169] [<ffffffff810b66d0>] ? kthread_create_on_node+0x240/0x240 > [ 1.840169] [<ffffffff81789a7c>] ret_from_fork+0x7c/0xb0 > [ 1.840169] [<ffffffff810b66d0>] ? kthread_create_on_node+0x240/0x240 > [ 1.840169] Code: ff 49 89 c4 4d 85 e4 0f 8f 25 ff ff ff eb ad 48 c7 c0 f4 ff ff ff e9 17 ff ff ff e8 f5 cd eb e0 90 55 48 89 e5...
2013 Dec 04
3
Nouveau failing during probe followed by GPF on 3.13-rc2
...x150 [ 657.802272] [<ffffffff8131d8ce>] ? pcibios_set_master+0x5e/0x90 [ 657.802315] [<ffffffffa00a7eba>] nouveau_drm_probe+0x24a/0x290 [nouveau] [ 657.802321] [<ffffffff8131f36c>] pci_device_probe+0x9c/0xf0 [ 657.802328] [<ffffffff813d6046>] driver_probe_device+0x76/0x240 [ 657.802333] [<ffffffff813d62ab>] __driver_attach+0x9b/0xa0 [ 657.802339] [<ffffffff813d6210>] ? driver_probe_device+0x240/0x240 [ 657.802345] [<ffffffff813d43b5>] bus_for_each_dev+0x55/0x90 [ 657.802350] [<ffffffff813d5b79>] driver_attach+0x19/0x20 [ 657.802355]...
2014 Jun 29
0
virt_blk BUG: sleeping function called from invalid context
...per/1 > 2 locks held by swapper/1/0: > #0: (&(&vblk->vq_lock)->rlock){-.-...}, at: [<ffffffffa0039042>] > virtblk_done+0x42/0xe0 [virtio_blk] > #1: (&(&bitmap->counts.lock)->rlock){-.....}, at: > [<ffffffff81633718>] bitmap_endwrite+0x68/0x240 > irq event stamp: 33518 > hardirqs last enabled at (33515): [<ffffffff8102544f>] default_idle+0x1f/0x230 > hardirqs last disabled at (33516): [<ffffffff818122ed>] > common_interrupt+0x6d/0x72 > softirqs last enabled at (33518): [<ffffffff810a1272>] > _loca...
2013 Jan 03
2
3.8-rc2: EFI framebuffer lock inversion...
...[<ffffffff81262a16>] fb_notifier_call_chain+0x16/0x20 [<ffffffff81264c1d>] register_framebuffer+0x1bd/0x2f0 [<ffffffff81ac2bd4>] efifb_probe+0x40f/0x496 [<ffffffff81308dfe>] platform_drv_probe+0x3e/0x70 [<ffffffff81306dc6>] driver_probe_device+0x76/0x240 [<ffffffff81307033>] __driver_attach+0xa3/0xb0 [<ffffffff8130503d>] bus_for_each_dev+0x4d/0x90 [<ffffffff81306929>] driver_attach+0x19/0x20 [<ffffffff813064e0>] bus_add_driver+0x1a0/0x270 [<ffffffff813076c2>] driver_register+0x72/0x170 [<ffff...
2007 Sep 12
2
cc5 where to start debugging
Hi, I've been running close combat 5 with wine for a while now but lately I've been getting a error with the program crashing. The following output comes in the terminal: ---------------------------------------------------------------------------------------------------------------------------------------------------- wine: Unhandled page fault on write access to 0x0375fffe at
2013 Feb 05
0
[PATCH] drm/nouveau: fix lockdep splat in display
...au_engctx_create_+0x25c/0x2a0 [nouveau] [<ffffffffa0176791>] nv50_disp_data_ctor+0xc1/0xd0 [nouveau] [<ffffffffa0153722>] ? nouveau_subdev_reset+0x52/0x60 [nouveau] [<ffffffffa0152163>] nouveau_object_ctor+0x33/0xc0 [nouveau] [<ffffffffa0152a42>] nouveau_object_new+0x112/0x240 [nouveau] [<ffffffffa01f4b1d>] nv50_display_create+0x18d/0x860 [nouveau] [<ffffffff8105cb5d>] ? __cancel_work_timer+0x6d/0xc0 [<ffffffffa01db8eb>] nouveau_display_create+0x3cb/0x670 [nouveau] [<ffffffffa01cb1bf>] nouveau_drm_load+0x26f/0x590 [nouveau] [<ffffffff81304...
2013 Jan 15
0
nouveau lockdep splat on init
...nouveau] [ 40.864179] [<ffffffff816fa71d>] ? _raw_spin_unlock_irqrestore+0x3d/0x80 [ 40.864179] [<ffffffff81374566>] local_pci_probe+0x46/0x80 [ 40.864179] [<ffffffff81375db9>] pci_device_probe+0xf9/0x120 [ 40.864179] [<ffffffff81410c86>] driver_probe_device+0x76/0x240 [ 40.864179] [<ffffffff81410ef3>] __driver_attach+0xa3/0xb0 [ 40.864179] [<ffffffff81410e50>] ? driver_probe_device+0x240/0x240 [ 40.864179] [<ffffffff8140f0e6>] bus_for_each_dev+0x56/0x90 [ 40.864179] [<ffffffff814107e9>] driver_attach+0x19/0x20 [ 40.864179]...
2011 Sep 10
12
WARNING: at fs/btrfs/inode.c:2193 btrfs_orphan_commit_root+0xb0/0xc0 [btrfs]()
...x870 [btrfs] [ 5472.100155] [<ffffffffa0039b0f>] do_async_commit+0x1f/0x30 [btrfs] [ 5472.100171] [<ffffffff8108110d>] process_one_work+0x11d/0x430 [ 5472.100187] [<ffffffff81081c69>] worker_thread+0x169/0x360 [ 5472.100203] [<ffffffff81081b00>] ? manage_workers.clone.21+0x240/0x240 [ 5472.100220] [<ffffffff81086496>] kthread+0x96/0xa0 [ 5472.100236] [<ffffffff815e5bb4>] kernel_thread_helper+0x4/0x10 [ 5472.100253] [<ffffffff81086400>] ? flush_kthread_worker+0xb0/0xb0 [ 5472.100269] [<ffffffff815e5bb0>] ? gs_change+0x13/0x13 [ 5472.100279] ---...
2017 Jul 19
1
kernel-4.9.37-29.el7 (and el6)
On Mon, 17 Jul 2017, Johnny Hughes wrote: > Are the testing kernels (kernel-4.9.37-29.el7 and kernel-4.9.37-29.el6, > with the one config file change) working for everyone: > > (turn off: CONFIG_IO_STRICT_DEVMEM) Hello. Maybe it's not the most appropriate thread or time, but I have been signalling it before: 4.9.* kernels do not work well for me any more (and for other people
2014 Oct 13
2
[PATCH v4 13/25] virtio_console: enable VQs early
virtio spec requires drivers to set DRIVER_OK before using VQs. This is set automatically after probe returns, virtio console violated this rule by adding inbufs, which causes the VQ to be used directly within probe. To fix, call virtio_device_ready before using VQs. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/char/virtio_console.c | 2 ++ 1 file changed, 2
2014 Oct 13
2
[PATCH v4 13/25] virtio_console: enable VQs early
virtio spec requires drivers to set DRIVER_OK before using VQs. This is set automatically after probe returns, virtio console violated this rule by adding inbufs, which causes the VQ to be used directly within probe. To fix, call virtio_device_ready before using VQs. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/char/virtio_console.c | 2 ++ 1 file changed, 2