Hi All,
I executed CRIU tests on the 4.1.0-rc8-next-20150617 kernel and met
this bug. Maybe it will be interested for someone to look at it.
[ 30.130897] BUG: unable to handle kernel NULL pointer dereference
at 001c
[ 30.130970] IP: [813bc7e1] cfq_print_leaf_weight+0x31
79378] BUG: unable to handle kernel NULL pointer dereference at
(null)
This bug was fixed by John Hubbard here:
http://permalink.gmane.org/gmane.linux.kernel.next/35308
I ack'ed it on May 6 but I think it hasn't made it from Andrew's tree to
linux-next yet.
Thanks!
--
Chris Metca
: unable to handle kernel NULL pointer dereference at
(null)
This bug was fixed by John Hubbard here:
http://permalink.gmane.org/gmane.linux.kernel.next/35308
I ack'ed it on May 6 but I think it hasn't made it from Andrew's tree to
linux-next yet.
Thanks!
--
Chris Metcalf, EZChip
detection
[1.352179] ata2.00: ATAPI: QEMU DVD-ROM, 2.1.2, max UDMA/100
[1.353501] ata2.00: configured for MWDMA2
[1.354423] BUG: unable to handle kernel NULL pointer dereference at
(null)
[1.356074] IP: [< (null)>] (null)
[1.356074] PGD 0
[1.35
[1.352179] ata2.00: ATAPI: QEMU DVD-ROM, 2.1.2, max UDMA/100
[1.353501] ata2.00: configured for MWDMA2
[1.354423] BUG: unable to handle kernel NULL pointer dereference at
(null)
[1.356074] IP: [ (null)] (null)
[1.356074] PGD 0
[1.356074] Oops: 0010 [#1
|
+--++++
[1.928994] init: Failed to create pty - disabling logging for job
[1.931296] init: Temporary process spawn error: No space left on device
Kernel tests: Boot OK!
[ 13.037537] BUG: unable to handle kernel NULL pointer dereference at 0028
[ 13.038009] IP
!
[ 13.037537] BUG: unable to handle kernel NULL pointer dereference at 0028
[ 13.038009] IP: [c12c7d96] release_pgd+0x9/0x5b
[ 13.038009] *pde =
[ 13.038009] Oops: [#1]
[ 13.038009] Modules linked in:
[ 13.038009] CPU: 0 PID: 12024 Comm: trinity-main Not tainted
Cc: Jan Kara
Cc: Vivek Goyal
[8.872697] ide_generic: please use "probe_mask=0x3f" module parameter for
probing all legacy ISA IDE ports
[8.873577] ide-gd driver 1.18
[8.873883] ide-cd driver 5.00
[8.874369] BUG: unable to handle kernel NULL pointer d
5.00
[8.874369] BUG: unable to handle kernel NULL pointer dereference at
0030
[8.875106] IP: [878166a1] blk_clear_congested+0x14/0x1f
[8.875677] PGD 0
[8.875882] Oops: [#1]
[8.876160] CPU: 0 PID: 1 Comm: swapper Not tainted 4.0.0-rc3-00183-g0f911ca
#4
0:80 12% 10:80dmesg.RIP:fib_trie_unmerge
[ 14.975179] BUG: unable to handle kernel NULL pointer dereference at
0030
[ 14.976015] IP: [] fib_trie_unmerge+0x1d/0x2f0
[ 14.976015] PGD 0
[ 14.976015] Oops: [#1] SMP
[ 14.976015] Modules linked
-not_syncing:Fatal_exception
0:80 12% 10:80dmesg.Oops
0:80 12% 10:80dmesg.RIP:fib_trie_unmerge
[ 14.975179] BUG: unable to handle kernel NULL pointer dereference at
0030
[ 14.976015] IP: [817f77bd
seconds,
margin is 60 seconds).
[0.817519] [drm] Initialized drm 1.1.0 20060810
[0.833300] brd: module loaded
[0.834038] BUG: unable to handle kernel NULL pointer dereference at
09d8
[0.834768] IP: [] percpu_ref_init+0x28/0x82
[0.835010] PGD 0
[0.835010] Oops
|
+--++++
[0.816325] Hangcheck: starting hangcheck timer 0.9.1 (tick is 180 seconds,
margin is 60 seconds).
[0.817519] [drm] Initialized drm 1.1.0 20060810
[0.833300] brd: module loaded
[0.834038] BUG: unable to handle kernel NULL pointer dereference at
09d8
[0.834768] IP
|
> +--+++-+
>
> [1.178531] udc dummy_udc.0: registering UDC driver [MIDI Gadget]
> [1.179260] MIDI Gadget gadget: adding config #1 'MIDI Gadget'/c1f006c0
> [1.184102] MIDI Gadget gadget: adding 'gmidi
[1.186606] BUG: unable to handle kernel NULL pointer dereference at 0050
[1.187008] IP: [] bus_add_device+0xd6/0x160
[1.187008] *pde =
[1.187008] Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC
[1.187008] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.0-03415-g7c37ae5
#24
(10774.22 BogoMIPS)
[0.098207] devtmpfs: unable to create devtmpfs -14
[0.102790] BUG: unable to handle kernel NULL pointer dereference at 0080
[0.103000] IP: [] __queue_work+0x1f/0x270
[0.103000] *pdpt = *pde = f000ff53f000ff53
[0.103000] Oops: 000
to config
'MIDI Gadget'/c1f006c0
[1.186606] BUG: unable to handle kernel NULL pointer dereference at 0050
[1.187008] IP: [c1590786] bus_add_device+0xd6/0x160
[1.187008] *pde =
[1.187008] Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC
[1.187008] CPU: 0 PID: 1 Comm
BogoMIPS)
[0.098207] devtmpfs: unable to create devtmpfs -14
[0.102790] BUG: unable to handle kernel NULL pointer dereference at 0080
[0.103000] IP: [c10577ff] __queue_work+0x1f/0x270
[0.103000] *pdpt = *pde = f000ff53f000ff53
[0.103000] Oops: [#1] SMP
gadget: adding config #1 'MIDI Gadget'/c1f006c0
[1.184102] MIDI Gadget gadget: adding 'gmidi function'/d1fab310 to config
'MIDI Gadget'/c1f006c0
[1.186606] BUG: unable to handle kernel NULL pointer dereference at
0050
[1.187008] IP: [c1590786] bus_add_device+0xd6/0x160
> -Original Message-
> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
> Sent: Saturday, February 28, 2015 5:57 PM
> To: linux-kernel@vger.kernel.org
> Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
> dereference
>
Removing the card did not
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Saturday, February 28, 2015 5:57 PM
To: linux-kernel@vger.kernel.org
Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
dereference
Removing the card did not fix the issue.
I've gone
nitialized drm 1.1.0 20060810
[0.702193] BUG: unable to handle kernel NULL pointer dereference at
0550
[0.702883] IP: [] blk_get_backing_dev_info+0xb/0x1a
[0.703443] PGD 0
[0.703632] Oops: [#1] PREEMPT SMP
[0.704009] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
4.0.0-r
).
[0.701079] [drm] Initialized drm 1.1.0 20060810
[0.702193] BUG: unable to handle kernel NULL pointer dereference at
0550
[0.702883] IP: [8121a84b] blk_get_backing_dev_info+0xb/0x1a
[0.703443] PGD 0
[0.703632] Oops: [#1] PREEMPT SMP
[0.704009] CPU: 0
gt; Hi Guys,
>
> [ 0.014166] BUG: unable to handle kernel NULL pointer dereference
> at (null)^M
> [0.014920] IP: [] cpumask_copy+0x17/0x1a^M
> [0.015000] PGD 0 ^M
> [0.015000] Oops: 0002 [#1] PREEMPT SMP DEBUG_PAGEALLOC ^M
> [0.015000] Dumping ftrac
Guys,
[0.014166] BUG: unable to handle kernel NULL pointer dereference
at (null)^M
[0.014920] IP: [810ab011] cpumask_copy+0x17/0x1a^M
[0.015000] PGD 0 ^M
[0.015000] Oops: 0002 [#1] PREEMPT SMP DEBUG_PAGEALLOC ^M
[0.015000] Dumping ftrace buffer:^M
Hi Guys,
[0.014166] BUG: unable to handle kernel NULL pointer dereference
at (null)^M
[0.014920] IP: [] cpumask_copy+0x17/0x1a^M
[0.015000] PGD 0 ^M
[0.015000] Oops: 0002 [#1] PREEMPT SMP DEBUG_PAGEALLOC ^M
[0.015000] Dumping ftrace buffer:^M
[0.015000
Hi Guys,
[0.014166] BUG: unable to handle kernel NULL pointer dereference
at (null)^M
[0.014920] IP: [810ab011] cpumask_copy+0x17/0x1a^M
[0.015000] PGD 0 ^M
[0.015000] Oops: 0002 [#1] PREEMPT SMP DEBUG_PAGEALLOC ^M
[0.015000] Dumping ftrace buffer:^M
gt; > think Ville mentioned he was looking/looked at the atomic-vs-load_detect
> > > > changes that is at the heart of the issue here. (Admittedly he did say
> > > > it was worthy of a drink or two.)
> > > > -Chris
> > >
> > > Thank you for t
> it was worthy of a drink or two.)
> > > -Chris
> >
> > Thank you for the help. I've tried to add to the kernel command line
> > 'video=card0-SVIDEO-1:d video=card0-VGA-1:d'. But despite of that
> > kernel crashes with 'BUG: unable to handle kernel NULL poin
TV). I
> > think Ville mentioned he was looking/looked at the atomic-vs-load_detect
> > changes that is at the heart of the issue here. (Admittedly he did say
> > it was worthy of a drink or two.)
> > -Chris
>
> Thank you for the help. I've tried to add to the kerne
-VGA-1:d'. But despite of that
kernel crashes with 'BUG: unable to handle kernel NULL pointer
dereference at' occasionally.
Remove the card0- and combine both into a single video= stanza:
video=SVIDEO-1:d,VGA-1:d
I've just tried that, but the crash with NULL pointer dereference still
that is at the heart of the issue here. (Admittedly he did say
it was worthy of a drink or two.)
-Chris
Thank you for the help. I've tried to add to the kernel command line
'video=card0-SVIDEO-1:d video=card0-VGA-1:d'. But despite of that
kernel crashes with 'BUG: unable to handle kernel NULL pointer
it was worthy of a drink or two.)
-Chris
Thank you for the help. I've tried to add to the kernel command line
'video=card0-SVIDEO-1:d video=card0-VGA-1:d'. But despite of that
kernel crashes with 'BUG: unable to handle kernel NULL pointer
dereference at' occasionally.
Remove the card0
> -Original Message-
> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
> Sent: Saturday, February 28, 2015 5:19 PM
> To: linux-kernel@vger.kernel.org
> Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
> dereference
>
>
>
> > --
> -Original Message-
> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
> Sent: Friday, February 27, 2015 10:54 AM
> To: linux-kernel@vger.kernel.org
> Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
> dereference
>
>
>
> > --
(Admittedly he did say
> it was worthy of a drink or two.)
> -Chris
Thank you for the help. I've tried to add to the kernel command line
'video=card0-SVIDEO-1:d video=card0-VGA-1:d'. But despite of that
kernel crashes with 'BUG: unable to handle kernel NULL pointer
dereference at' occasionally.
--
Best regards,
Andrey Skvortsov
signature.asc
Description: Digital signature
to the kernel command line
'video=card0-SVIDEO-1:d video=card0-VGA-1:d'. But despite of that
kernel crashes with 'BUG: unable to handle kernel NULL pointer
dereference at' occasionally.
--
Best regards,
Andrey Skvortsov
signature.asc
Description: Digital signature
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Friday, February 27, 2015 10:54 AM
To: linux-kernel@vger.kernel.org
Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
dereference
-Original Message-
From: Justin Piszcz
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Saturday, February 28, 2015 5:19 PM
To: linux-kernel@vger.kernel.org
Subject: RE: 3.19 kernel: BUG: unable to handle kernel NULL pointer
dereference
-Original Message-
From: Justin
> -Original Message-
> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
> Sent: Friday, February 27, 2015 9:54 AM
> To: linux-kernel@vger.kernel.org
> Subject: 3.19 kernel: BUG: unable to handle kernel NULL pointer
dereference
>
> Hello,
>
> With kernel 3
Hello,
With kernel 3.15, I do not recall having any issues, with 3.19, I am getting
a kernel crash when I copy files over NFS from machine A to B.
Is this a known issue?
I suspect it has to do something with this:
Feb 27 09:31:20 remote-host [ 15.745342] dmar: DRHD: handling fault status
reg 2
Hello,
With kernel 3.15, I do not recall having any issues, with 3.19, I am getting
a kernel crash when I copy files over NFS from machine A to B.
Is this a known issue?
I suspect it has to do something with this:
Feb 27 09:31:20 remote-host [ 15.745342] dmar: DRHD: handling fault status
reg 2
-Original Message-
From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
Sent: Friday, February 27, 2015 9:54 AM
To: linux-kernel@vger.kernel.org
Subject: 3.19 kernel: BUG: unable to handle kernel NULL pointer
dereference
Hello,
With kernel 3.15, I do not recall having any
wdata, 2656K rodata, 1108K init, 5048K bss, 33772K reserved, 0K cma-reserved)
> [ 0.00] BUG: unable to handle kernel NULL pointer dereference at
> 0068
> [0.00] IP: [] do_set_cpus_allowed+0x18/0x51
> [0.00] PGD 0
> [0.00] Oops: [#1] SM
rodata, 1108K init, 5048K bss, 33772K reserved, 0K cma-reserved)
[0.00] BUG: unable to handle kernel NULL pointer dereference at
0068
[0.00] IP: [880bebe6] do_set_cpus_allowed+0x18/0x51
[0.00] PGD 0
[0.00] Oops: [#1] SMP
[0.00
A area
[0.00] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[0.00] Memory: 293508K/327280K available (9326K kernel code, 3522K
rwdata, 2656K rodata, 1108K init, 5048K bss, 33772K reserved, 0K cma-reserved)
[0.000000] BUG: unable to handle kernel NULL pointer deref
bss, 33772K reserved, 0K cma-reserved)
[0.00] BUG: unable to handle kernel NULL pointer dereference at
0068
[0.00] IP: [880bebe6] do_set_cpus_allowed+0x18/0x51
[0.00] PGD 0
[0.00] Oops: [#1] SMP
[0.00] Modules linked
20060810
[1.185690] [TTM] Zone kernel: Available graphics memory: 149938 kiB
[1.186177] [TTM] Initializing pool allocator
[1.186912] BUG: unable to handle kernel NULL pointer dereference at 0008
[1.187477] IP: [<81379138>] drm_universal_plane_init+0x143/0x214
[1.187956]
|
+---++++
[1.182990] [drm] Initialized drm 1.1.0 20060810
[1.185690] [TTM] Zone kernel: Available graphics memory: 149938 kiB
[1.186177] [TTM] Initializing pool allocator
[1.186912] BUG: unable to handle kernel NULL pointer dereference at 0008
[1.187477] IP: [81379138
. You can see some tracesys_phase2() in
some of the traces. It's a very reproducible error.
dmesg-vm-vp-quantal-x86_64-14:20141214024709:x86_64-rhel:3.18.0-rc6-00015-gbbea5f5:1
[5.970508] init: Failed to create pty - disabling logging for job
[ 5.973062] init: Failed to create pty
On Mon, 2014-12-15 at 11:31 -0600, Eric W. Biederman wrote:
> Huang Ying writes:
>
> > FYI, we noticed the below changes on
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
> > for-testing
> > commit bbea5f5532501fdd67f46442ba7b1122d7ff3123
> > ("userns: Add a
Huang Ying writes:
> FYI, we noticed the below changes on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
> for-testing
> commit bbea5f5532501fdd67f46442ba7b1122d7ff3123
> ("userns: Add a knob to disable setgroups on a per user namespace basis")
Thank you.
I am
Huang Ying ying.hu...@intel.com writes:
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
for-testing
commit bbea5f5532501fdd67f46442ba7b1122d7ff3123
(userns: Add a knob to disable setgroups on a per user namespace basis)
Thank
On Mon, 2014-12-15 at 11:31 -0600, Eric W. Biederman wrote:
Huang Ying ying.hu...@intel.com writes:
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
for-testing
commit bbea5f5532501fdd67f46442ba7b1122d7ff3123
(userns:
to create pty - disabling logging for job
[5.973062] init: Failed to create pty - disabling logging for job
[5.989614] init: Failed to create pty - disabling logging for job
[ 16.365667] BUG: unable to handle kernel NULL pointer dereference at
(null)
[ 16.366010] IP
-only data: 28672k
[ 42.382977] Freeing unused kernel memory: 700K (880005951000 -
880005a0)
[ 42.563098] Freeing unused kernel memory: 988K (880006109000 -
88000620)
[ 42.773320] BUG: unable to handle kernel NULL pointer dereference at
0880
[ 42.774231
|
+--++++
[ 42.296661] Write protecting the kernel read-only data: 28672k
[ 42.382977] Freeing unused kernel memory: 700K (880005951000 -
880005a0)
[ 42.563098] Freeing unused kernel memory: 988K (880006109000 -
88000620)
[ 42.773320] BUG: unable to handle kernel
rograms to be attached to sockets
>
> > [init] Kernel was tainted on startup. Will ignore flags that are already
> > set.
> > [init] Started watchdog process, PID is 9354
> > [main] Main thread is alive.
> > [ 21.233581] BUG: unable to handle kernel NULL po
ready set.
> [init] Started watchdog process, PID is 9354
> [main] Main thread is alive.
> [ 21.233581] BUG: unable to handle kernel NULL pointer dereference at
> 0007
> [ 21.234709] IP: [] sk_attach_bpf+0x39/0xc2
thanks for the report! syscall fuzzer is great.
that are already set.
[init] Started watchdog process, PID is 9354
[main] Main thread is alive.
[ 21.233581] BUG: unable to handle kernel NULL pointer dereference at
0007
[ 21.234709] IP: [8156ebda] sk_attach_bpf+0x39/0xc2
thanks for the report! syscall fuzzer is great.
I missed
to sockets
[init] Kernel was tainted on startup. Will ignore flags that are already
set.
[init] Started watchdog process, PID is 9354
[main] Main thread is alive.
[ 21.233581] BUG: unable to handle kernel NULL pointer dereference at
0007
[ 21.234709] IP
At Sun, 30 Nov 2014 10:50:19 -0800,
Fengguang Wu wrote:
At Sun, 30 Nov 2014 10:50:19 -0800,
Fengguang Wu wrote:
>
> Hi Kyle,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next
>
> commit
[1.689386] dgap: dgap-1.3-16, Digi International Part Number 40002347_C
[1.690258] dgap: For the tools package please visit http://www.digi.com
[1.694793] BUG: unable to handle kernel NULL pointer dereference at 02a0
[1.695739] IP: [<7940555f>] snd_card_free+0x36/0x7f
[1.
[1.689386] dgap: dgap-1.3-16, Digi International Part Number 40002347_C
[1.690258] dgap: For the tools package please visit http://www.digi.com
[1.694793] BUG: unable to handle kernel NULL pointer dereference at 02a0
[1.695739] IP: [7940555f] snd_card_free+0x36/0x7f
[1.696409
At Sun, 30 Nov 2014 10:50:19 -0800,
Fengguang Wu wrote:
At Sun, 30 Nov 2014 10:50:19 -0800,
Fengguang Wu wrote:
Hi Kyle,
0day kernel testing robot got the below dmesg and the first bad commit is
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git for-next
commit
| 4 |
| backtrace:kernel_init_freeable | 0 | 4 |
+--+++
[ 20.962013] BUG: unable to handle kernel NULL pointer dereference at
0002
[ 20.964023] IP: [] init_irq_alloc_info
|
| backtrace:kernel_init_freeable | 0 | 4 |
+--+++
[ 20.962013] BUG: unable to handle kernel NULL pointer dereference at
0002
[ 20.964023] IP: [81074795] init_irq_alloc_info+0x13
--++++
>
> [0.00] Checking if this processor honours the WP bit even in
> supervisor mode...Ok.
> [0.000000] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
> [0.00] NR_IRQS:16 nr_irq
.
[0.00] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] NR_IRQS:16 nr_irqs:16 0
[0.00] BUG: unable to handle kernel NULL pointer dereference at 003a
[0.00] IP: [] setup_irq+0x2d/0xbd
[0.00] *pdpt = *pde = f000ff53f000ff53
anges on commit
> >
> > 445d95d7c384741d133251a9adac935866591c92 ("sched: Remove
> > update_rq_runnable_avg")
> >
> > [ 67.303839] BUG: unable to handle kernel NULL pointer dereference at
> > 0040
> > [ 67.304014] IP: [] print_cfs_rq+0x4a3/0xa96
>
> Well that one'
On Sat, 11 Oct 2014 13:15:30 +0800
Fengguang Wu wrote:
> FYI, we noticed the below changes on commit
>
> 445d95d7c384741d133251a9adac935866591c92 ("sched: Remove
> update_rq_runnable_avg")
>
> [ 67.303839] BUG: unable to handle kernel NULL pointer derefe
On Sat, 11 Oct 2014 13:15:30 +0800
Fengguang Wu fengguang...@intel.com wrote:
FYI, we noticed the below changes on commit
445d95d7c384741d133251a9adac935866591c92 (sched: Remove
update_rq_runnable_avg)
[ 67.303839] BUG: unable to handle kernel NULL pointer dereference
445d95d7c384741d133251a9adac935866591c92 (sched: Remove
update_rq_runnable_avg)
[ 67.303839] BUG: unable to handle kernel NULL pointer dereference at
0040
[ 67.304014] IP: [810b1d52] print_cfs_rq+0x4a3/0xa96
Well that one's pretty obvious:
--- a/kernel/sched/debug.c
+++ b/kernel
if this processor honours the WP bit even in supervisor
mode...Ok.
[0.00] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] NR_IRQS:16 nr_irqs:16 0
[0.00] BUG: unable to handle kernel NULL pointer dereference at 003a
[0.00] IP: [c10f6fe7
|
+--++++
[0.00] Checking if this processor honours the WP bit even in
supervisor mode...Ok.
[0.00] SLUB: HWalign=128, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] NR_IRQS:16 nr_irqs:16 0
[0.00] BUG: unable to handle kernel NULL pointer dereference at
003a
| 0 | 5 |
+--+++
repeat count: 267
2014-10-10 18:20:23 ./case-anon-wx-rand-mt
2014-10-10 18:20:23 ./usemem --runtime 300 -t 4 --prealloc --random 514360832
[ 67.303839] BUG: unable to handle kernel NU
| 5 |
+--+++
repeat count: 267
2014-10-10 18:20:23 ./case-anon-wx-rand-mt
2014-10-10 18:20:23 ./usemem --runtime 300 -t 4 --prealloc --random 514360832
[ 67.303839] BUG: unable to handle kernel NULL pointer
On Tue, Oct 07, 2014 at 10:17:32AM +0200, Peter Zijlstra wrote:
> On Tue, Oct 07, 2014 at 01:03:48PM +0800, Fengguang Wu wrote:
> > > What is lacking is the actual .config.
> >
> > Sorry, attached the .config. I expected the script to auto attach it,
> > but obviously it's not yet perfect and
On Tue, Oct 07, 2014 at 01:03:48PM +0800, Fengguang Wu wrote:
> > What is lacking is the actual .config.
>
> Sorry, attached the .config. I expected the script to auto attach it,
> but obviously it's not yet perfect and failed to attach .config in
> this case.
Sure no problem, just figured I'd
On Tue, Oct 07, 2014 at 01:03:48PM +0800, Fengguang Wu wrote:
What is lacking is the actual .config.
Sorry, attached the .config. I expected the script to auto attach it,
but obviously it's not yet perfect and failed to attach .config in
this case.
Sure no problem, just figured I'd tell
On Tue, Oct 07, 2014 at 10:17:32AM +0200, Peter Zijlstra wrote:
On Tue, Oct 07, 2014 at 01:03:48PM +0800, Fengguang Wu wrote:
What is lacking is the actual .config.
Sorry, attached the .config. I expected the script to auto attach it,
but obviously it's not yet perfect and failed to
> > [ 267.547006] debug: unmapping init [mem 0xc28f9000-0xc2b03fff]
> > [ 267.694378] random: init urandom read with 4 bits of entropy available
> > [ 279.465522] sock: process `trinity-main' is using obsolete setsockopt
> > SO_BSDCOMPAT
> > [ 285.269144] BUG
f]
> > [ 267.694378] random: init urandom read with 4 bits of entropy available
> > [ 279.465522] sock: process `trinity-main' is using obsolete setsockopt
> > SO_BSDCOMPAT
> > [ 285.269144] BUG: unable to handle kernel NULL pointer dereference at
> > 0085
> &g
kernel NULL pointer dereference at
0085
[ 285.273002] IP: [c11259a1] perf_prepare_sample+0x33e/0x496
[ 285.276062] *pde =
[ 285.279106] Oops: [#1] PREEMPT SMP DEBUG_PAGEALLOC
[ 285.279106] Modules linked in:
[ 285.279106] CPU: 1 PID: 1583 Comm: trinity-main
[ 267.547006] debug: unmapping init [mem 0xc28f9000-0xc2b03fff]
[ 267.694378] random: init urandom read with 4 bits of entropy available
[ 279.465522] sock: process `trinity-main' is using obsolete setsockopt
SO_BSDCOMPAT
[ 285.269144] BUG: unable to handle kernel NULL pointer
06] debug: unmapping init [mem 0xc28f9000-0xc2b03fff]
> [ 267.694378] random: init urandom read with 4 bits of entropy available
> [ 279.465522] sock: process `trinity-main' is using obsolete setsockopt
> SO_BSDCOMPAT
> [ 285.269144] BUG: unable to handle kernel NULL pointer derefer
-0xc2b03fff]
[ 267.694378] random: init urandom read with 4 bits of entropy available
[ 279.465522] sock: process `trinity-main' is using obsolete setsockopt
SO_BSDCOMPAT
[ 285.269144] BUG: unable to handle kernel NULL pointer dereference at 0085
[ 285.273002] IP: [] perf_prepare_sample
|
+---+++--+
[ 267.547006] debug: unmapping init [mem 0xc28f9000-0xc2b03fff]
[ 267.694378] random: init urandom read with 4 bits of entropy available
[ 279.465522] sock: process `trinity-main' is using obsolete setsockopt
SO_BSDCOMPAT
[ 285.269144] BUG: unable to handle kernel NULL pointer
] random: init urandom read with 4 bits of entropy available
[ 279.465522] sock: process `trinity-main' is using obsolete setsockopt
SO_BSDCOMPAT
[ 285.269144] BUG: unable to handle kernel NULL pointer dereference at
0085
[ 285.273002] IP: [c11259a1] perf_prepare_sample+0x33e/0x496
On Tue, Sep 30, 2014 at 07:41:38PM +0800, Fengguang Wu wrote:
> Hi Paul,
>
> > One thing would be something like this:
> >
> > ( sleep 300; rmmod rcutorture ) &
> >
> > Running both locktorture and rcutorture concurrently is not supported
> > at the moment because both make the assumption
Hi Paul,
> One thing would be something like this:
>
> ( sleep 300; rmmod rcutorture ) &
>
> Running both locktorture and rcutorture concurrently is not supported
> at the moment because both make the assumption that they have the entire
> system at their disposal.
It's good to know
ke this commit without losing much (sendkey
> > > > alt-sysrq-z is after all my friend), but it is not clear to me that we
> > > > have gotten to the root of this problem.
> > >
> > > Sorry about that! If you see any debug tricks that I can try, or
> > > inform
] -
[ 121.930865] BUG: unable to handle kernel NULL pointer dereference
at (null)
[ 121.931644] IP: [8959b074] print_trace_line+0x2b0/0x38a
Fair point.
One approach would be to set
rcutorture.stat_interval=200 or whatever the duration of boot is.
Another would
Hi Paul,
One thing would be something like this:
( sleep 300; rmmod rcutorture )
Running both locktorture and rcutorture concurrently is not supported
at the moment because both make the assumption that they have the entire
system at their disposal.
It's good to know that!
On Tue, Sep 30, 2014 at 07:41:38PM +0800, Fengguang Wu wrote:
Hi Paul,
One thing would be something like this:
( sleep 300; rmmod rcutorture )
Running both locktorture and rcutorture concurrently is not supported
at the moment because both make the assumption that they have
tricks that I can try, or
> > information I can collect, please let me know.
>
> Hmmm...
>
> Looks like rcutorture might be starting too soon. With all the selftests,
> it is taking 3-4 minutes to boot.
Sorry my scripts reboot the machine quickly, there is no logic to wa
the TERM signal...
mount: mounting proc on /proc failed: No such device
[ 121.930088] Dumping ftrace buffer:
[ 121.930453] -
[ 121.930865] BUG: unable to handle kernel NULL pointer dereference at
(null)
[ 121.931644
[ 2.364611] BUG: unable to handle kernel NULL pointer dereference
> at 0039
> [2.364615] IP: []
> thermal_get_trip_type+0x17/0x84 [thermal]
> [2.364616] PGD 374d6067 PUD 374d7067 PMD 0
> [2.364618] Oops: [#1] PREEMPT SMP
> [2.364621] Modules linked in:
This occurs during the boot process. It is not triggered by userspace
as far as I can tell. There are other OOPS messages. I can send the
full list if it will help.
[2.364611] BUG: unable to handle kernel NULL pointer dereference
at 0039
[2.364615] IP
This occurs during the boot process. It is not triggered by userspace
as far as I can tell. There are other OOPS messages. I can send the
full list if it will help.
[2.364611] BUG: unable to handle kernel NULL pointer dereference
at 0039
[2.364615] IP: [c015503e
801 - 900 of 1433 matches
Mail list logo
