what workload do you run on the machine to trigger
> this? Can you send contents of /proc/mounts please? Thanks!
>
> Honza
>
> >
> >
> > [99390.044690] [ cut here ]
>
hello,
# CONFIG_READ_ONLY_THP_FOR_FS is not set
Le mar. 4 août 2020 à 14:39, Matthew Wilcox a écrit :
>
> On Tue, Aug 04, 2020 at 01:19:13PM +0200, Jan Kara wrote:
> > Hello!
> >
> > On Wed 27-05-20 21:05:55, nirinA raseliarison wrote:
> > > i hit again this bug with:
> > >
> > > $ cat /proc/v
On Tue, Aug 04, 2020 at 01:19:13PM +0200, Jan Kara wrote:
> Hello!
>
> On Wed 27-05-20 21:05:55, nirinA raseliarison wrote:
> > i hit again this bug with:
> >
> > $ cat /proc/version
> > Linux version 5.7.0-rc7.20200525 (nir...@supernova.org) (gcc version
> > 10.1.0 (GCC), GNU ld version 2.33.1-s
[99390.044690] [ cut here ]--------
> [99390.044695] kernel BUG at fs/inode.c:531!
> [99390.044702] invalid opcode: [#1] SMP PTI
> [99390.044705] CPU: 0 PID: 149 Comm: kswapd0 Not tainted 5.7.0-rc7.20200525 #1
> [99390.044706] Hardware name: To be filled by O.E.M. To be
hello,
i hit again this bug with:
$ cat /proc/version
Linux version 5.7.0-rc7.20200525 (nir...@supernova.org) (gcc version
10.1.0 (GCC), GNU ld version 2.33.1-slack15) #1 SMP Mon May 25
02:49:28 EAT 2020
[99390.044690] [ cut here ]
[99390.044695] kernel BUG at fs/inode.c
kernel: [16312.604139] kernel BUG at fs/inode.c:531!
> May 20 05:06:25 supernova kernel: [16312.604145] invalid opcode:
> [#1] SMP PTI
> May 20 05:06:25 supernova kernel: [16312.604148] CPU: 1 PID: 149 Comm:
> kswapd0 Not tainted 5.7.0-rc6.20200519 #1
> May 20 05:06:25 supernova
hello ,
i repeatedly hit this bug since gcc-10.1.0:
May 20 05:06:25 supernova kernel: [16312.604136] [ cut
here ]
May 20 05:06:25 supernova kernel: [16312.604139] kernel BUG at fs/inode.c:531!
May 20 05:06:25 supernova kernel: [16312.604145] invalid opcode:
[#1] SMP
> >
> > Should I be forcing fsck soon?
> > Pavel
> >
> > [12717.827444] ------------[ cut here ]
> > [12717.827465] kernel BUG at fs/inode.c:513!
>
> It seems unlikely that fsck i
forcing fsck soon?
> Pavel
>
> [12717.827444] [ cut here ]--------
> [12717.827465] kernel BUG at fs/inode.c:513!
It seems unlikely that fsck is going to help. The BUG_ON in question
appears to be:
BUG_ON(inode->i_data.nrexceptional);
Hi!
This happened on trying to sync filesystems with unison:
Any ideas?
Should I be forcing fsck soon?
Pavel
[12717.827444] [ cut here ]
[12717.827465] kernel BUG at fs/inode.c:513!
[12717.827486] invalid
On Thu 22-11-07 18:20:15, [EMAIL PROTECTED] wrote:
> Hi,
>
> > Thanks for report. It looks like a problem in UDF. Actually I think
> > I've already seen a similar report. Are there any IO errors in the logs
> > or anything else suspitious?
>
>
> At the risk of reporting further bugs :-) here
Hi,
> Thanks for report. It looks like a problem in UDF. Actually I think
> I've already seen a similar report. Are there any IO errors in the logs
> or anything else suspitious?
At the risk of reporting further bugs :-) here it goes:
==
ny IO errors in the logs
or anything else suspitious?
Honza
> Nov 20 23:30:23 *** kernel: kernel BUG at fs/inode.c:191!
> Nov 20 23:30:23 *** kernel: invalid opcode: [1] SMP
> Nov 20 23:30:23 *** kernel: CPU 1
> Nov 20 23:30:23 *** kernel: Modul
really copied, and it was syncing) and a few minutes after
this notice came up.
best regards
Paulo Nogueira
PS please cc replies to me
Nov 20 23:30:23 *** kernel: kernel BUG at fs/inode.c:191!
Nov 20 23:30:23 *** kernel: invalid opcode: [1] SMP
Nov 20 23:30:23 *** kernel: CPU 1
N
14 matches
Mail list logo
