Messages in this thread | | | Subject | Re: "kernel ade access" oops on LoongArch | From | Xi Ruoyao <> | Date | Wed, 15 Feb 2023 16:07:15 +0800 |
| |
On Wed, 2023-02-15 at 15:51 +0800, Jinyang He wrote:
> > There was a build error in make check, so only tst-mallocfork3- > > malloc-check was tested separately. > > > > # make test t=malloc/tst-mallocfork3-malloc-check > > make[2]: 离开目录“/home/loongson/glibc/malloc” > > PASS: malloc/tst-mallocfork3-malloc-check > > original exit status 0 > > info: signals received during fork: 301 > > info: signals received during free: 1693 > > info: signals received during malloc: 119 > > make[1]: 离开目录“/home/loongson/glibc” > > > > A total of five tests are PASS, and the serial port does not display > > CallTrace. > > > > Youling. > > > I had test it by using the cmd "while true..." Ruoyao gave on > > Loongson-3A5000, CLFS 7.1, 6.2-rc8 kernel with those patches and > > 6.2-rc7 kernel form loongson-next. No calltrace displayed, either.
Hmm... I've read the code for a while and I couldn't see how it could end up accessing a bad address too. Maybe my hardware or compiler is really faulty?
-- Xi Ruoyao <xry111@xry111.site> School of Aerospace Science and Technology, Xidian University
| |