Re: adding support for a possibly unsupported M.2 harddrive?
jaromir.dole...@gmail.com (=?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?=) writes: >> This is an "TREKSTOR M.2 SSD-Modul 64 GB" bought in 2018. >It seems it's configured to attach as AHCI instead of NVMe. Can you check >if there are any relevant BIOS settings, which would make it available as >NVMe? The device is advertised as SATA 6G, it's not a NVME PCI card. -- -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."
Re: adding support for a possibly unsupported M.2 harddrive?
Le dim. 24 nov. 2019 à 12:18, ng0 a écrit : > Hi folx, > > I have an M.2 SSD for which I have to assume no support exists so far > in NetBSD 9.99.17. > This is an "TREKSTOR M.2 SSD-Modul 64 GB" bought in 2018. > > Its dmesg: > > [ 3.739718] wd1 at atabus1 drive 0 > [ 3.739718] wd1: <> > [ 3.739718] wd1: drive supports 1-sector PIO transfers, LBA48 > addressing > [ 3.739718] wd1: 61057 MB, 124053 cyl, 16 head, 63 sec, 512 bytes/sect > x 125045424 sectors > [ 3.739718] wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode > 6 (Ultra/133), WRITE DMA FUA, NCQ (32 tags) > [ 3.739718] wd1(ahcisata0:1:0): using PIO mode 4, DMA mode 2, > Ultra-DMA mode 6 (Ultra/133) (using DMA), NCQ (31 tags) > > With fdisk I can see an earlier partition I created on another > system, but making any changes to partitioning etc pp operations > on disk fail (I can reproduce the information how it fails). > It seems it's configured to attach as AHCI instead of NVMe. Can you check if there are any relevant BIOS settings, which would make it available as NVMe? Nevertheless, even when attached via AHCI it shouldn't give errors. Can you please post specific errors from kernel when you try to do the partitioning? Jaromir
daily CVS update output
Updating src tree: P src/distrib/notes/Makefile.inc P src/distrib/notes/acorn32/contents P src/distrib/notes/alpha/contents P src/distrib/notes/amd64/contents P src/distrib/notes/amiga/contents P src/distrib/notes/arc/contents P src/distrib/notes/arc/prep P src/distrib/notes/atari/contents P src/distrib/notes/bebox/contents P src/distrib/notes/cats/contents P src/distrib/notes/cats/prep P src/distrib/notes/common/contents P src/distrib/notes/common/main P src/distrib/notes/common/postinstall P src/distrib/notes/common/sysinst P src/distrib/notes/common/upgrade P src/distrib/notes/emips/contents P src/distrib/notes/evbarm/contents P src/distrib/notes/evbppc/contents P src/distrib/notes/ews4800mips/contents P src/distrib/notes/hp300/contents P src/distrib/notes/hpcarm/contents P src/distrib/notes/hpcmips/contents P src/distrib/notes/hpcsh/contents P src/distrib/notes/hppa/contents P src/distrib/notes/i386/contents P src/distrib/notes/landisk/contents P src/distrib/notes/mac68k/contents P src/distrib/notes/macppc/contents P src/distrib/notes/macppc/prep.OPENFIRMWARE P src/distrib/notes/mmeye/contents P src/distrib/notes/mvme68k/contents P src/distrib/notes/news68k/contents P src/distrib/notes/newsmips/contents P src/distrib/notes/next68k/contents P src/distrib/notes/ofppc/contents P src/distrib/notes/pmax/contents P src/distrib/notes/prep/contents P src/distrib/notes/rs6000/contents P src/distrib/notes/sandpoint/contents P src/distrib/notes/sandpoint/xfer P src/distrib/notes/sgimips/contents P src/distrib/notes/shark/contents P src/distrib/notes/sparc/contents P src/distrib/notes/sparc/prep P src/distrib/notes/sparc64/contents P src/distrib/notes/sparc64/upgrade P src/distrib/notes/sun2/contents P src/distrib/notes/sun3/contents P src/distrib/notes/vax/contents P src/distrib/notes/x68k/contents P src/external/mpl/bind/dist/CHANGES P src/external/mpl/bind/dist/README P src/external/mpl/bind/dist/README.md P src/external/mpl/bind/dist/configure.ac U src/external/mpl/bind/dist/srcid P src/external/mpl/bind/dist/version P src/external/mpl/bind/dist/bin/tests/system/conf.sh.common P src/external/mpl/bind/dist/bin/tests/system/autosign/clean.sh P src/external/mpl/bind/dist/bin/tests/system/autosign/tests.sh U src/external/mpl/bind/dist/bin/tests/system/autosign/ns3/jitter.nsec3.example.db.in P src/external/mpl/bind/dist/bin/tests/system/autosign/ns3/keygen.sh P src/external/mpl/bind/dist/bin/tests/system/autosign/ns3/named.conf.in U src/external/mpl/bind/dist/bin/tests/system/checkconf/bad-ipv4-prefix-dotted1.conf U src/external/mpl/bind/dist/bin/tests/system/checkconf/bad-ipv4-prefix-dotted2.conf U src/external/mpl/bind/dist/bin/tests/system/checkconf/bad-ipv4-prefix2.conf U src/external/mpl/bind/dist/bin/tests/system/checkconf/good-dnskey-validity-3660.conf U src/external/mpl/bind/dist/bin/tests/system/checkconf/good-dnskey-validity-zero.conf P src/external/mpl/bind/dist/bin/tests/system/digdelv/tests.sh U src/external/mpl/bind/dist/bin/tests/system/dnstap/bad-missing-dnstap-output-view.conf U src/external/mpl/bind/dist/bin/tests/system/dnstap/good-dnstap-in-options.conf U src/external/mpl/bind/dist/bin/tests/system/dnstap/good-dnstap-in-view.conf P src/external/mpl/bind/dist/bin/tests/system/filter-/tests.sh P src/external/mpl/bind/dist/bin/tests/system/geoip2/tests.sh P src/external/mpl/bind/dist/bin/tests/system/legacy/tests.sh P src/external/mpl/bind/dist/bin/tests/system/staticstub/tests.sh P src/external/mpl/bind/dist/bin/tests/system/synthfromdnssec/tests.sh P src/external/mpl/bind/dist/bin/tests/system/tcp/clean.sh U src/external/mpl/bind/dist/bin/tests/system/tcp/prereq.sh P src/external/mpl/bind/dist/bin/tests/system/tcp/setup.sh P src/external/mpl/bind/dist/bin/tests/system/tcp/tests.sh U src/external/mpl/bind/dist/bin/tests/system/tcp/ans6/ans.py U src/external/mpl/bind/dist/bin/tests/system/tcp/ns5/named.conf.in U src/external/mpl/bind/dist/cocci/dns_name_copy-with-result.spatch U src/external/mpl/bind/dist/cocci/dns_name_copy.spatch U src/external/mpl/bind/dist/cocci/dns_name_copynf.spatch P src/external/mpl/bind/dist/doc/arm/Bv9ARM-book.xml P src/external/mpl/bind/dist/doc/arm/Bv9ARM.ch01.html P src/external/mpl/bind/dist/doc/arm/Bv9ARM.ch02.html P src/external/mpl/bind/dist/doc/arm/Bv9ARM.ch03.html P src/external/mpl/bind/dist/doc/arm/Bv9ARM.ch04.html P src/external/mpl/bind/dist/doc/arm/Bv9ARM.ch05.html P src/external/mpl/bind/dist/doc/arm/Bv9ARM.ch06.html P src/external/mpl/bind/dist/doc/arm/Bv9ARM.ch07.html P src/external/mpl/bind/dist/doc/arm/Bv9ARM.ch08.html P src/external/mpl/bind/dist/doc/arm/Bv9ARM.ch09.html P src/external/mpl/bind/dist/doc/arm/Bv9ARM.ch10.html P src/external/mpl/bind/dist/doc/arm/Bv9ARM.ch11.html P src/external/mpl/bind/dist/doc/arm/Bv9ARM.ch12.html P src/external/mpl/bind/dist/doc/arm/Bv9ARM.html P src/external/mpl/bind/dist/doc/arm/Makefile.in P src/external/mpl/bind/dist/doc/arm/man.arpaname.html P src/external/mpl/bind/dist/doc/arm/man.ddns-confgen.html P
Crash with HEAD on amd64 - in setrunnable()
With a very current kernel, I just got this: # crash -M /var/crash/netbsd.21.core -N /netbsd.gdb Crash version 9.99.18, image version 9.99.18. System panicked: kernel diagnostic assertion "lwp_locked(l, l->l_cpu->ci_schedstate.spc_lwplock)" failed: file "/build/netbsd-local/src_ro/sys/kern/kern_synch.c", line 910 Backtrace from time of crash is available. crash> bt _KERNEL_OPT_NVGA_RASTERCONSOLE() at 0 ?() at de890ce0af54 vpanic() at vpanic+0x181 kern_assert() at kern_assert+0x48 setrunnable() at setrunnable+0x179 lwp_start() at lwp_start+0xba do_lwp_create() at do_lwp_create+0xa1 sys__lwp_create() at sys__lwp_create+0xc1 syscall() at syscall+0x28a --- syscall (number 309) --- 45ae46: crash> (Obviously, I have a core dump, so I'll be happy to investigate further if anyone has suggestions.) ++--+---+ | 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: PATCH: use UXA on default for pre-skylake intel GPUs
On Wed, 6 Nov 2019, John D. Baker wrote: > I will be trying the patch soon-ish. I have tried the patched module on a machine with: > 82G41 and it seems to work. It selects UXA acceleration by default. As such, the TearFree option is not needed. Perhaps if the detected device causes UXA accleration to be selected, perhaps the TearFree option could default to "Off" for those as well? Then, no "xorg.conf" will be needed. As it is, it's fine for a live-USB stick to have X Just Work(tm) when booting some random machine. -- |/"\ John D. Baker, KN5UKS NetBSD Darwin/MacOS X |\ / jdbaker[snail]consolidated[flyspeck]net OpenBSDFreeBSD | X No HTML/proprietary data in email. BSD just sits there and works! |/ \ GPGkeyID: D703 4A7E 479F 63F8 D3F4 BD99 9572 8F23 E4AD 1645
Re: adding support for a possibly unsupported M.2 harddrive?
ng0 writes: > Hi folx, > > I have an M.2 SSD for which I have to assume no support exists so far > in NetBSD 9.99.17. > This is an "TREKSTOR M.2 SSD-Modul 64 GB" bought in 2018. > > Its dmesg: > > [ 3.739718] wd1 at atabus1 drive 0 > [ 3.739718] wd1: <> > [ 3.739718] wd1: drive supports 1-sector PIO transfers, LBA48 addressing > [ 3.739718] wd1: 61057 MB, 124053 cyl, 16 head, 63 sec, 512 bytes/sect x > 125045424 sectors > [ 3.739718] wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 > (Ultra/133), WRITE DMA FUA, NCQ (32 tags) > [ 3.739718] wd1(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA > mode 6 (Ultra/133) (using DMA), NCQ (31 tags) > > With fdisk I can see an earlier partition I created on another > system, but making any changes to partitioning etc pp operations > on disk fail (I can reproduce the information how it fails). > > Two question paths: > > 1. How would I go about (no prior device driver writing >experience) adding this to NetBSD? My impression is that disk drives do not need explicit support for normal operations. I have attached a number of ssd, both mSATA and regular SATA, which simply worked as any other drive. The missing device type in <> is surprising, but it's not clear that this is a real issue or related to your problem. I would check if you can read and write (destroying the label of course) to the disk with dd. Look at src/sys/dev/ata/wd.c:wdattach() which I think is what is printing the attachment messages. See the call to wd_get_params() in that function. There are debug defines you can turn on. Expect your first time in the kernel to be an extended learning experience.
adding support for a possibly unsupported M.2 harddrive?
Hi folx, I have an M.2 SSD for which I have to assume no support exists so far in NetBSD 9.99.17. This is an "TREKSTOR M.2 SSD-Modul 64 GB" bought in 2018. Its dmesg: [ 3.739718] wd1 at atabus1 drive 0 [ 3.739718] wd1: <> [ 3.739718] wd1: drive supports 1-sector PIO transfers, LBA48 addressing [ 3.739718] wd1: 61057 MB, 124053 cyl, 16 head, 63 sec, 512 bytes/sect x 125045424 sectors [ 3.739718] wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133), WRITE DMA FUA, NCQ (32 tags) [ 3.739718] wd1(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA), NCQ (31 tags) With fdisk I can see an earlier partition I created on another system, but making any changes to partitioning etc pp operations on disk fail (I can reproduce the information how it fails). Two question paths: 1. How would I go about (no prior device driver writing experience) adding this to NetBSD? or 2. Who / which list would I talk to and which details are necessary (so far I know fdisk and dmesg provide good details) to help with adding this to NetBSD? Cheers, ng0
