NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/57226: NetBSD 10_BETA kernel crash
The following reply was made to PR kern/57226; it has been noted by GNATS.
From: Takahiro Kambe <taca%back-street.net@localhost>
To: martin%duskware.de@localhost
Cc: gnats-bugs%netbsd.org@localhost
Subject: Re: kern/57226: NetBSD 10_BETA kernel crash
Date: Tue, 14 Feb 2023 14:18:41 +0900 (JST)
In message <20230213150322.GB4036%mail.duskware.de@localhost>
on Mon, 13 Feb 2023 16:03:22 +0100,
Martin Husemann <martin%duskware.de@localhost> wrote:
> You do not need a kernel core dump for that, just the /netbsd you were
> using at the time of the crash (or even better: the netbsd.gdb version
> if you happen to have that in your kernel build directory).
Oh. I see. Here it is.
>> > Can you use gdb (or addr2line) to identify the two functions mentioned
>> > in the panic? Something like
>> >
>> > gdb> list *(0xffffffff80dea0a3)
(gdb) list *(0xffffffff80dea0a3)
0xffffffff80dea0a3 is in itimer_callout (/data/netbsd/src/sys/kern/kern_time.c:834).
829 * N.B. A delay in processing this callout causes multiple
830 * SIGALRM calls to be compressed into one.
831 */
832 static void
833 itimer_callout(void *arg)
834 {
835 uint64_t last_val, next_val, interval, now_ns;
836 struct timespec now, next;
837 struct itimer * const it = arg;
838 int backwards;
>> > gdb> list *(0xffffffff80e34fc9)
(gdb) list *(0xffffffff80e34fc9)
0xffffffff80e34fc9 is in timerfd_fop_close (/data/netbsd/src/sys/kern/sys_timerfd.c:194).
189
190 itimer_lock();
191 itimer_poison(&tfd->tfd_itimer);
192 itimer_fini(&tfd->tfd_itimer); /* drops itimer lock */
193
194 cv_destroy(&tfd->tfd_read_wait);
195
196 seldestroy(&tfd->tfd_read_sel);
197
198 kmem_free(tfd, sizeof(*tfd));
--
Takahiro Kambe <taca%back-street.net@localhost>
Home |
Main Index |
Thread Index |
Old Index