Date: Mon, 04 Feb 2019 12:51:49 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 235489] llan driver causes fatal kernel trap: 0x300 (data storage interrupt) when system is low on memory Message-ID: <bug-235489-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D235489 Bug ID: 235489 Summary: llan driver causes fatal kernel trap: 0x300 (data storage interrupt) when system is low on memory Product: Base System Version: CURRENT Hardware: powerpc OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: luporl@FreeBSD.org When running several builders in parallel, on QEMU, with 8GB of memory, a f= atal kernel trap caused by llan driver is sometimes observed, when the system st= arts to run out of swap space. fatal kernel trap: exception =3D 0x300 (data storage interrupt) virtual address =3D 0x18 dsisr =3D 0x42000000 srr0 =3D 0xc000000000ac9104 (0xac9104) srr1 =3D 0x8000000000009032 current msr =3D 0x8000000000009032 lr =3D 0xc000000000ac90ec (0xac90ec) curthread =3D 0xc000000006deb000 pid =3D 12, comm =3D irq16781321: llan0 panic: data storage interrupt trap cpuid =3D 2 time =3D 1549288422 KDB: stack backtrace: 0xe0000000005a5ed0: at .kdb_backtrace+0x5c 0xe0000000005a6000: at .vpanic+0x1b4 0xe0000000005a60c0: at .panic+0x38 0xe0000000005a6150: at .trap_fatal+0x25c 0xe0000000005a61e0: at .trap+0xeec 0xe0000000005a6380: at .powerpc_interrupt+0x290 0xe0000000005a6420: kernel DSI write trap @ 0x18 by .llan_intr+0xf4: srr1=3D0x8000000000009032 r1=3D0xe0000000005a66d0 cr=3D0x22000042 xer=3D0 ctr=3D0 r2=3D0xc000000001569528 sr=3D0x42000000 0xe0000000005a66d0: at .llan_intr+0xd8 0xe0000000005a6770: at .ithread_loop+0x25c 0xe0000000005a6850: at .fork_exit+0xd0 0xe0000000005a68f0: at .fork_trampoline+0x10 0xe0000000005a6920: at -0x4 KDB: enter: panic [ thread pid 12 tid 100153 ] Stopped at .kdb_enter+0x60: ld r2, r1, 0x28 db> It seems like there is some point in the driver that does not check properl= y if UMA allocation failed. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-235489-227>