Re: [bugreport] [5.10-rc1] Oops: 0000 [#1] SMP NOPTI bug which always starts as page allocation failure

2020-11-04 Thread Alex Deucher
/0x5b0 > [11561.928820] kthread+0x13a/0x150 > [11561.928823] ? __kthread_bind_mask+0x60/0x60 > [11561.928828] ret_from_fork+0x22/0x30 > [11561.928861] irq event stamp: 296033 > [11561.928864] hardirqs last enabled at (296041): > [] console_unlock+0x511/0x

[bugreport] [5.10-rc1] Oops: 0000 [#1] SMP NOPTI bug which always starts as page allocation failure

2020-11-03 Thread Mikhail Gavrilov
not-present page [11561.928884] PGD 0 P4D 0 [11561.928887] Oops: [#1] SMP NOPTI [11561.92] CPU: 18 PID: 39985 Comm: kworker/u64:10 Tainted: G W- --- 5.10.0-0.rc1.20201028gited8780e3f2ec.57.fc34.x86_64 #1 [11561.928889] Hardware name: System manufacturer System Product Na

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-18 Thread Matthew Wilcox
On Mon, Feb 18, 2019 at 07:11:55PM +0100, Michal Hocko wrote: > On Mon 18-02-19 09:57:26, Matthew Wilcox wrote: > > On Mon, Feb 18, 2019 at 06:05:58PM +0100, Michal Hocko wrote: > > > + end_pfn = min(start_pfn + nr_pages, > > > + zone_end_pfn(page_zone(pfn_to_page(start_pfn; > >

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-18 Thread Michal Hocko
On Mon 18-02-19 09:57:26, Matthew Wilcox wrote: > On Mon, Feb 18, 2019 at 06:05:58PM +0100, Michal Hocko wrote: > > + end_pfn = min(start_pfn + nr_pages, > > + zone_end_pfn(page_zone(pfn_to_page(start_pfn; > > > > /* Check the starting page of each pageblock within the

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-18 Thread Matthew Wilcox
On Mon, Feb 18, 2019 at 06:05:58PM +0100, Michal Hocko wrote: > + end_pfn = min(start_pfn + nr_pages, > + zone_end_pfn(page_zone(pfn_to_page(start_pfn; > > /* Check the starting page of each pageblock within the range */ > - for (; page < end_page; page = nex

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-18 Thread Mike Rapoport
On Mon, Feb 18, 2019 at 06:05:58PM +0100, Michal Hocko wrote: > On Mon 18-02-19 18:48:14, Mike Rapoport wrote: > > On Mon, Feb 18, 2019 at 04:22:13PM +0100, Michal Hocko wrote: > [...] > > > Thinking about it some more, is it possible that we are overflowing by 1 > > > here? > > > > Looks like tha

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-18 Thread Michal Hocko
On Mon 18-02-19 18:48:14, Mike Rapoport wrote: > On Mon, Feb 18, 2019 at 04:22:13PM +0100, Michal Hocko wrote: [...] > > Thinking about it some more, is it possible that we are overflowing by 1 > > here? > > Looks like that, the end_pfn is actually the first pfn in the next section. Thanks for th

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-18 Thread Mike Rapoport
.org/r/20190218052823.GH29177@shao2-debian[] > > > > > > > > > > > > On Mon 18-02-19 08:08:44, Michal Hocko wrote: > > > > > > > On Mon 18-02-19 13:28:23, kernel test robot wrote: > > > > > > [...] > > > >

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-18 Thread Michal Hocko
> > On Mon 18-02-19 08:08:44, Michal Hocko wrote: > > > > > > On Mon 18-02-19 13:28:23, kernel test robot wrote: > > > > > [...] > > > > > > > [ 40.305212] PGD 0 P4D 0 > > > > > > > [ 40.308255] Oops: [#1] PREEMPT SMP

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-18 Thread Michal Hocko
previous email] > > > > [Cc Pavel - the full report is > > > > http://lkml.kernel.org/r/20190218052823.GH29177@shao2-debian[] > > > > > > > > On Mon 18-02-19 08:08:44, Michal Hocko wrote: > > > > > On Mon 18-02-19 13:28:23, kernel

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-18 Thread Mike Rapoport
s > > > http://lkml.kernel.org/r/20190218052823.GH29177@shao2-debian[] > > > > > > On Mon 18-02-19 08:08:44, Michal Hocko wrote: > > > > On Mon 18-02-19 13:28:23, kernel test robot wrote: > > > [...] > > > > > [ 40.305212] PGD 0 P4D 0 > &

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-18 Thread Michal Hocko
Mon 18-02-19 08:08:44, Michal Hocko wrote: > > > On Mon 18-02-19 13:28:23, kernel test robot wrote: > > [...] > > > > [ 40.305212] PGD 0 P4D 0 > > > > [ 40.308255] Oops: [#1] PREEMPT SMP PTI > > > > [ 40.313055] CPU: 1 PID: 239 Comm: udev

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-18 Thread Michal Hocko
.] > > > > > [ 40.305212] PGD 0 P4D 0 > > > > > [ 40.308255] Oops: [#1] PREEMPT SMP PTI > > > > > [ 40.313055] CPU: 1 PID: 239 Comm: udevd Not tainted > > > > > 5.0.0-rc4-00149-gefad4e4 #1 > > > > > [ 40.321348] Hardware na

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-18 Thread Rong Chen
On 2/18/19 5:03 PM, Michal Hocko wrote: On Mon 18-02-19 16:47:26, Rong Chen wrote: On 2/18/19 3:08 PM, Michal Hocko wrote: On Mon 18-02-19 13:28:23, kernel test robot wrote: [...] [ 40.305212] PGD 0 P4D 0 [ 40.308255] Oops: [#1] PREEMPT SMP PTI [ 40.313055] CPU: 1 PID: 239 Comm

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-18 Thread Michal Hocko
On Mon 18-02-19 16:47:26, Rong Chen wrote: > > On 2/18/19 3:08 PM, Michal Hocko wrote: > > On Mon 18-02-19 13:28:23, kernel test robot wrote: [...] > > > [ 40.305212] PGD 0 P4D 0 > > > [ 40.308255] Oops: [#1] PREEMPT SMP PTI > > > [ 40.313055]

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-18 Thread Michal Hocko
D 0 P4D 0 > > [ 40.308255] Oops: [#1] PREEMPT SMP PTI > > [ 40.313055] CPU: 1 PID: 239 Comm: udevd Not tainted > > 5.0.0-rc4-00149-gefad4e4 #1 > > [ 40.321348] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS > > 1.10.2-1 04/01/2014 > > [

Re: [LKP] efad4e475c [ 40.308255] Oops: 0000 [#1] PREEMPT SMP PTI

2019-02-17 Thread Michal Hocko
x27;/sbin/modprobe -bv > pci:v1234dsv1AF4sd1100bc03sc00i00': No such file or > directory > udevd[312]: failed to execute '/sbin/modprobe' '/sbin/modprobe -bv > acpi:QEMU0002:': No such file or directory > udevd[314]: failed to execute '/s

Re: 98f929b1bd ("ipc/shm: Fix shmctl(..., IPC_STAT, ...) between .."): Oops: 0000 [#1]

2018-03-28 Thread Eric W. Biederman
Nagarathnam Muthusamy writes: > Hi Eric, > >     From > https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git/tree/ipc/shm.c?h=for-next > > It looks like if the following condition in Line 616 succeeds > > error = PTR_ERR(file); > if (IS_ERR(file)) >     goto no_file; > > we

Re: 98f929b1bd ("ipc/shm: Fix shmctl(..., IPC_STAT, ...) between .."): Oops: 0000 [#1]

2018-03-28 Thread Nagarathnam Muthusamy
2 bytes left Kernel tests: Boot OK! [ 18.532190] IP: put_pid+0x22/0x5c [ 18.532552] PGD 19efa067 P4D 19efa067 PUD 0 [ 18.533006] Oops: [#1] [ 18.533318] CPU: 0 PID: 727 Comm: trinity Not tainted 4.16.0-rc2-00010-g98f929b #1 [ 18.534144] RIP: 0010:put_pid+0x22/0x5c [ 18.534586] R

Re: BUG: unable to handle kernel paging request at 0000000100000003 - Oops: 0000 [#1] SMP

2014-03-03 Thread Jan Kara
On Mon 03-03-14 20:13:00, poma wrote: > On 21.02.2014 16:48, Jan Kara wrote: > > On Fri 21-02-14 14:08:03, Richard Weinberger wrote: > >> On Fri, Feb 21, 2014 at 12:40 PM, poma wrote: > >>> > >>> Affected kernels - 3.14.0-0.rc3*: > >>> > >>> - 3.14.0-0.rc3.git0.1 > >>> http://koji.fedoraproject.

Re: BUG: unable to handle kernel paging request at 0000000100000003 - Oops: 0000 [#1] SMP

2014-03-03 Thread poma
On 21.02.2014 16:48, Jan Kara wrote: > On Fri 21-02-14 14:08:03, Richard Weinberger wrote: >> On Fri, Feb 21, 2014 at 12:40 PM, poma wrote: >>> >>> Affected kernels - 3.14.0-0.rc3*: >>> >>> - 3.14.0-0.rc3.git0.1 >>> http://koji.fedoraproject.org/koji/buildinfo?buildID=498711 >>> >>> - 3.14.0-0.r

Re: BUG: unable to handle kernel paging request at 0000000100000003 - Oops: 0000 [#1] SMP

2014-02-21 Thread Jan Kara
On Fri 21-02-14 14:08:03, Richard Weinberger wrote: > On Fri, Feb 21, 2014 at 12:40 PM, poma wrote: > > > > Affected kernels - 3.14.0-0.rc3*: > > > > - 3.14.0-0.rc3.git0.1 > > http://koji.fedoraproject.org/koji/buildinfo?buildID=498711 > > > > - 3.14.0-0.rc3.git0.7 based on 3.14.0-0.rc3.git0.1 >

Re: BUG: unable to handle kernel paging request at 0000000100000003 - Oops: 0000 [#1] SMP

2014-02-21 Thread Richard Weinberger
On Fri, Feb 21, 2014 at 12:40 PM, poma wrote: > > Affected kernels - 3.14.0-0.rc3*: > > - 3.14.0-0.rc3.git0.1 > http://koji.fedoraproject.org/koji/buildinfo?buildID=498711 > > - 3.14.0-0.rc3.git0.7 based on 3.14.0-0.rc3.git0.1 > > - 3.14.0-0.rc3.git2.1 > http://koji.fedoraproject.org/koji/buil

BUG: unable to handle kernel paging request at 0000000100000003 - Oops: 0000 [#1] SMP

2014-02-21 Thread poma
Affected kernels - 3.14.0-0.rc3*: - 3.14.0-0.rc3.git0.1 http://koji.fedoraproject.org/koji/buildinfo?buildID=498711 - 3.14.0-0.rc3.git0.7 based on 3.14.0-0.rc3.git0.1 - 3.14.0-0.rc3.git2.1 http://koji.fedoraproject.org/koji/buildinfo?buildID=499061 - 3.14.0-0.rc3.git5.1 http://koji.fedor

Oops: 0000

2005-02-03 Thread Sakellarios Gerakios
Feb 2 14:37:45 geezer kernel: printing eip: Feb 2 14:37:45 geezer kernel: c0143c53 Feb 2 14:37:45 geezer kernel: *pde = Feb 2 14:37:45 geezer kernel: Oops: Feb 2 14:37:45 geezer kernel: parport_pc lp parport autofs e100 iptable_nat ip_conntrack iptable_mangle ipt_REJECT

PROBLEM: Unable to handle kernel paging request at virtual address e080f003 / Oops: 0000 [#1]

2005-01-22 Thread Julien Cigar
Hi. # [1.] Problem when rebooting # [2.] I'm running Debian/unstable and each time I reboot the system, I get a "Unable to handle kernel pading request at virt

Re: Oops 0000 and 0002 on dual PIII 750 2.4.2 SMP platform

2001-03-19 Thread Shane Y. Gibson
"Shane Y. Gibson" wrote: > > Marcelo Tosatti wrote: > > > > Did'nt you get a message similar to > > > > "kernel BUG at page_alloc.c line xxx!" Okay, I set the nmi_watchdog=0 options for LILO. Now on crashes, I get ZERO panic output in the log files. I found some old PII 450s, and don't seem to

Re: Oops 0000 and 0002 on dual PIII 750 2.4.2 SMP platform

2001-03-16 Thread Marcelo Tosatti
On Fri, 16 Mar 2001, Shane Y. Gibson wrote: > Marcelo Tosatti wrote: > > > > Can you please try to reproduce it with the following patch against 2.4.2? > > Marcelo (et al), > > I'll give it a whirl with the patch. Should I also > try setting `nmi_watchdog=0' in lilo.conf, as Andrew > Morton s

Re: Oops 0000 and 0002 on dual PIII 750 2.4.2 SMP platform

2001-03-16 Thread Shane Y. Gibson
Marcelo Tosatti wrote: > > Can you please try to reproduce it with the following patch against 2.4.2? Marcelo (et al), I'll give it a whirl with the patch. Should I also try setting `nmi_watchdog=0' in lilo.conf, as Andrew Morton suggests? Additionally, I'll upgrade my version of ksymoops. Unf

Re: Oops 0000 and 0002 on dual PIII 750 2.4.2 SMP platform

2001-03-15 Thread Marcelo Tosatti
On Thu, 15 Mar 2001, Shane Y. Gibson wrote: > Marcelo Tosatti wrote: > > > > Did'nt you get a message similar to > > > > "kernel BUG at page_alloc.c line xxx!" > > Marcelo, > > Yes there was. I'm pasting the total sum of the /var/log/messages > output. Note that I'm only able to locate det

Re: Oops 0000 and 0002 on dual PIII 750 2.4.2 SMP platform

2001-03-15 Thread Andrew Morton
"Shane Y. Gibson" wrote: > > 2.4.2 ... > dual PIII 750s ... > panicing, and freezing up. Try using the `nmi_watchdog=0' LILO option. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel

Re: Oops 0000 and 0002 on dual PIII 750 2.4.2 SMP platform

2001-03-15 Thread Shane Y. Gibson
05:12 walker kernel: Code: 0f 0b 83 c4 0c 89 d8 eb 1d 89 f6 47 83 c6 0c 83 ff 09 0f 86 Mar 14 22:05:25 walker kernel: Unable to handle kernel NULL pointer dereference at virtual address 0051 Mar 14 22:05:25 walker kernel: printing eip: Mar 14 22:05:25 walker kernel: c013f010 Mar 14 22:05:25 walk

Re: Oops 0000 and 0002 on dual PIII 750 2.4.2 SMP platform

2001-03-15 Thread Brian Gerst
nicing, and freezing > up. The first time, I got an oops , the second time an > oops 0002. Both crashes have occured only when the systems is > at 100% cpu utlization; processing several hundred MRTG > indexmaker operations. > > I ran ksymoops on both outputs, and the results

Re: Oops 0000 and 0002 on dual PIII 750 2.4.2 SMP platform

2001-03-15 Thread Marcelo Tosatti
he system is panicing, and freezing > up. The first time, I got an oops , the second time an > oops 0002. Both crashes have occured only when the systems is > at 100% cpu utlization; processing several hundred MRTG > indexmaker operations. > > I ran ksymoops on both outputs, an

Oops 0000 and 0002 on dual PIII 750 2.4.2 SMP platform

2001-03-15 Thread Shane Y. Gibson
All, I just compiled 2.4.2 and installed it on a otherwise stock Redhat 7.0 platform. The system is a SuperMicro PIIISME, running dual PIII 750s, with 256 cache. It appears that about every 10 to 18 hours, the system is panicing, and freezing up. The first time, I got an oops , the

Oops 0000

2001-01-16 Thread Stephan Henningsen
at virtual address current->tss.cr3 = 0dea4000, %%cr3 = 0dea4000 *pde = 0000 Oops: CPU:0 My gpm was killed so I tried to switch to another terminal to restart gpm and cut'n'paste the output to a file, but then it froze completely -- again. Now I am no long s