Re: crash in amd64 -current
On Fri, 22 Jan 2021, Christos Zoulas wrote: In article , Paul Goyette wrote: With sources updated a few hours ago (2021-01-21 at 17:17:48 UTC) I am getting the following crash as soon as it tries to start syslogd: Also, why the heck does savecore(8) complain when I use the -N option? # savecore -fN /netbsd.bad.gdb savecore: dumpdev /dev/console is tty; override kernel Seems that the dump device it finds by reading the kernel namelist from /netbsd.bad.gdb ends up being /dev/console... Is the machine you are running gdb the same as the machine that produced the dump? because the dev_t it read from the kernel namelist matched the dev_t for the console on the local machine in /dev. Same machine. The dump was produced by a ddb ``sync'' command from a 9.99.78 kernel, and savecore(8) was running on a 9.99.77 kernel-plus- userland; that's why I specified the -N. It seems that savecore actually copied some info correctly without the -N option, and crash(8) was able to get a stack-trace. But gdb(1) was unable to provide a stack trace. This is with a custom kernel, with many device drivers loaded at run- time. ++--+---+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | p...@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoye...@netbsd.org | ++--+---+
Re: virtio scsi under VirtualBox
After the latest virtio commits I no longer get the panic; the virtio-scsi device is recognized and the bus is created; however, a disk attached to it is not seen at all. The suspicion is that the created scsibus0 has only one target and 256 LUNs (scsibus1 on the same VM, attached to an MPT SCSI adapter, has 8 and 16)L dmesg | egrep scsibus [ 1.021614] scsibus0 at vioscsi0: 1 target, 256 luns per target [ 1.021614] scsibus1 at mpt0: 16 targets, 8 luns per target [ 2.429331] scsibus1: waiting 2 seconds for devices to settle... [ 2.459338] scsibus1: holding up boot [ 4.431688] sd0 at scsibus1 target 0 lun 0: disk fixed [ 4.469382] sd1 at scsibus1 target 1 lun 0: disk fixed [ 4.479495] sd2 at scsibus1 target 2 lun 0: disk fixed Full dmesg.boot is attached. Chavdar On Thu, 21 Jan 2021 at 18:52, Chavdar Ivanov wrote: > > On Thu, 21 Jan 2021 at 16:15, Reinoud Zandijk wrote: > > > > On Thu, Jan 21, 2021 at 11:45:25AM +, Chavdar Ivanov wrote: > > > On Sat, 21 Nov 2020 at 16:37, Chavdar Ivanov wrote: > > > I see there were a few recent commits around sys/dev/pci/virtio*. Just > > > to mention that the presence of a virtio scsi device in a -current > > > (from yesterday) vm under VirtualBox 6.1.16 now results in a Guru > > > Meditation Error: > > > .. > > > 00:00:16.505215 [ 1.0443388] virtio1: SCSI device (rev. 0x01) > > > 00:00:16.505234 [ 1.0443388] vioscsi0 at virtio1: features: 0x1 > > > > It doesn't report that the feature negotiation goes wrong before printing > > its > > features, so the host is accepting v1 but nothing else and that should be > > OK. > > > > > 00:00:16.505323 virtio-scsi#0: virtio-scsci > > > numTargets=1!! > > > 00:00:16.505391 emR3Debug: rc=VERR_INVALID_PARAMETER > > > > Clumsy error reporting of VirtualBox! What parameter, what call etc. > > > > Could you please test the code with vioscsi revision 0? i.e. with `legacy' > > setting? Or/and the setting 'Virtio SCSI Single' if applicable? > > What are the knobs for these settings? The only 'legacy' VBox setting > I know of is in the System->Acceleration->Paravirtualization Interface > settings. > > > Also please boot the kernel with `netbsd -vx'? > > I can attach the dmesg.boot file without virtio-scsi; with it I still > get the error. > > > > > Is there a way to get better error message? > > I've attached the full VBox.log file, it may be useful, as there are > other places referring to virtio-scsi. > > I have been using virtio-net for a long time without problems; this VM > runs whenever I run my laptop under Windows 10 and I had added a > virtio-scsi driver with a disk just to check if at some stage this > driver would be available. The VM still uses vboxvideo (insead of the > recommended now VMware video) and I always build and install the > additions on it (although obviously in this case it doesn't get to > module load). > > > > > With regards, > > Reinoud > > > > Thanks, > > Chavdar > > > -- > -- dmesg.boot Description: Binary data
Re: virtio scsi under VirtualBox
On Fri, Jan 22, 2021 at 02:23:46PM +, Chavdar Ivanov wrote: > After the latest virtio commits I no longer get the panic; the > virtio-scsi device is recognized and the bus is created; however, a > disk attached to it is not seen at all. thats interesting, since nothing changed that ought to have had influence; the only change was for virtio PCI v1.0's i386 compat the bus_space_write_8() was split into two bus_space_write_4()'s as its allowed by the spec. Since amd64 can write on every alignment, its odd that the write_8 would fail unless its a VirtualBox emulation error that doesn't expect an 8 byter to be written in one go. Very strange, i'll see if i can manage that. But the discs are there in the dmesg! See sd0 at scsibus1 target 0 lun 0: disk fixed sd0: fabricating a geometry sd0: 16384 MB, 16384 cyl, 64 head, 32 sec, 512 bytes/sect x 33554432 sectors sd0: fabricating a geometry sd1 at scsibus1 target 1 lun 0: disk fixed sd1: fabricating a geometry sd1: 16384 MB, 16384 cyl, 64 head, 32 sec, 512 bytes/sect x 33554432 sectors sd1: fabricating a geometry sd2 at scsibus1 target 2 lun 0: disk fixed sd2: fabricating a geometry sd2: 32768 MB, 32768 cyl, 64 head, 32 sec, 512 bytes/sect x 67108864 sectors sd2: fabricating a geometry So you can just access them using `disklabel' and fsck'ing and mounting them etc. Since they don't spawn dk* i presume they are not GPT. Please let me know if anything is wrong? Reinoud
Re: Panic in usbd_create_xfer
On 2021-01-03, Yorick Hardy wrote:
> Dear matthew,
>
> On 2021-01-03, matthew green wrote:
> > Yorick Hardy writes:
> > > Dear current-users,
> > >
> > > Happy new year!
> >
> > happy new year yorick! and everyone.
> >
> > > [ 659.839003] usbd_create_xfer() at netbsd:usbd_create_xfer+0x186
> > > [ 659.849001] usbd_open_pipe_intr() at netbsd:usbd_open_pipe_intr+0x74
> > > [ 659.849001] uhidev_open() at netbsd:uhidev_open+0x21c
> >
> > can you find out what lines in the source these are?
> > espcially usbd_create_xfer+0x186, the other ones are
> > most likely obvious only the single callers - eg,
> > usbd_open_pipe_intr() calls usbd_create_xfer() once.
> >
> > thanks.
> >
> >
> > .mrg.
>
> In the disassembly (I guess due to inlining) it happens at a call to
> usb_allocmem, which I think is line sys/dev/usb/usbdi.c:606, i.e. the
> call to usbd_alloc_buffer.
>
> I am current trying to trigger the panic with all of the USB_DEBUG and
> {U,O,E}HCI_DEBUG options enabled but it has not happened yet (I was sure
> I would be able to panic the kernel by now, maybe the _DEBUG options
> worka round the panic somehow?).
Reverting to src/sys/dev/usb/ohci.c revision 1.310 seems to
solve the panic, I have not yet determined how this change
could lead to a panic.
--
Kind regards,
Yorick Hardy
daily CVS update output
Updating src tree: P src/tests/rump/rumpkern/t_vm.c P src/usr.bin/make/unit-tests/varmod-assign.mk Updating xsrc tree: Killing core files: Updating tar files: src/top-level: collecting... replacing... done src/bin: collecting... replacing... done src/common: collecting... replacing... done src/compat: collecting... replacing... done src/crypto: collecting... replacing... done src/dist: collecting... replacing... done src/distrib: collecting... replacing... done src/doc: collecting... replacing... done src/etc: collecting... replacing... done src/external: collecting... replacing... done src/extsrc: collecting... replacing... done src/games: collecting... replacing... done src/gnu: collecting...pax: Unable to access src/gnu (No such file or directory) pax: WARNING! These file names were not selected: src/gnu done src/include: collecting... replacing... done src/lib: collecting... replacing... done src/libexec: collecting... replacing... done src/regress: collecting... replacing... done src/rescue: collecting... replacing... done src/sbin: collecting... replacing... done src/share: collecting... replacing... done src/sys: collecting... replacing... done src/tests: collecting... replacing... done src/tools: collecting... replacing... done src/usr.bin: collecting... replacing... done src/usr.sbin: collecting... replacing... done src/config: collecting... replacing... done src: collecting... replacing... done xsrc/top-level: collecting... replacing... done xsrc/external: collecting... replacing... done xsrc/local: collecting... replacing... done xsrc: collecting... replacing... done Updating release-8 src tree (netbsd-8): Updating release-8 xsrc tree (netbsd-8): Updating release-8 tar files: src/top-level: collecting... replacing... done src/bin: collecting... replacing... done src/common: collecting... replacing... done src/compat: collecting... replacing... done src/crypto: collecting... replacing... done src/dist: collecting... replacing... done src/distrib: collecting... replacing... done src/doc: collecting... replacing... done src/etc: collecting... replacing... done src/external: collecting... replacing... done src/extsrc: collecting... replacing... done src/games: collecting... replacing... done src/gnu: collecting...pax: Unable to access src/gnu (No such file or directory) pax: WARNING! These file names were not selected: src/gnu done src/include: collecting... replacing... done src/lib: collecting... replacing... done src/libexec: collecting... replacing... done src/regress: collecting... replacing... done src/rescue: collecting... replacing... done src/sbin: collecting... replacing... done src/share: collecting... replacing... done src/sys: collecting... replacing... done src/tests: collecting... replacing... done src/tools: collecting... replacing... done src/usr.bin: collecting... replacing... done src/usr.sbin: collecting... replacing... done src/config: collecting... replacing... done src/x11: collecting...pax: Unable to access src/x11 (No such file or directory) pax: WARNING! These file names were not selected: src/x11 done src: collecting... replacing... done xsrc/top-level: collecting... replacing... done xsrc/external: collecting... replacing... done xsrc/local: collecting... replacing... done xsrc/xfree: collecting...pax: Unable to access xsrc/xfree (No such file or directory) pax: WARNING! These file names were not selected: xsrc/xfree done xsrc: collecting... replacing... done Updating release-9 src tree (netbsd-9): Updating release-9 xsrc tree (netbsd-9): Updating release-9 tar files: src/top-level: collecting... replacing... done src/bin: collecting... replacing... done src/common: collecting... replacing... done src/compat: collecting... replacing... done src/crypto: collecting... replacing... done src/dist: collecting... replacing... done src/distrib: collecting... replacing... done src/doc: collecting... replacing... done src/etc: collecting... replacing... done src/external: collecting... replacing... done src/extsrc: collecting... replacing... done src/games: collecting... replacing... done src/include: collecting... replacing... done src/lib: collecting... replacing... done src/libexec: collecting... replacing... done src/regress: collecting... replacing... done src/rescue: collecting... replacing... done src/sbin: collecting... replacing... done src/share: collecting... replacing... done src/sys: collecting... replacing... done src/tests: collecting... replacing... done src/tools: collecting... replacing... done src/usr.bin: collecting... replacing... done src/usr.sbin: collecting... replacing... done src/config: collecting... replacing... done src: collecting... replacing... done xsrc/top-level: collecting... replacing... done xsrc/external: collecting... replacing... done xsrc/local: collecting... replacing... done xsrc: collecting... replacing... done Updating file list: -rw-rw-r-- 1 srcmastr netbsd 37711383 Jan 23 03:34 ls-lRA.gz
