[DragonFlyBSD - Bug #2917] da8: reading primary partition table: error accessing offset 000000000000 for 512
Issue #2917 has been updated by liweitianux. falsifian wrote: > I got the same error trying to install 6.0 on my Lenovo T430s. > > Disabling ehci (per liweitianux's instructions above) didn't help: da8 just > completely disappeared. > > Fortunately, switching to a different USB port solved the problem. (The > working one has an "SS" logo beside it.) Thank you for the follow-up. Actually, the USB port with "SS" logo should be an USB 3.x port, which uses the `xhci` module and works fine in DragonFly. I've tried to track this `ehci` issue quite some time ago, but failed to identify the cause ... Bug #2917: da8: reading primary partition table: error accessing offset for 512 http://bugs.dragonflybsd.org/issues/2917#change-14078 * Author: liweitianux * Status: New * Priority: Normal * Assignee: * Category: Driver * Target version: 6.2 Hello, Recently, I tried to install DragonFly BSD on my old ThinkPad X200 with both the 20160512-snapshot and 4.4.3-release USB image. However, DragonFly failed to mount root from the USB device. I enabled the verbose boot, and got the following error message: (da8:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR (da8:umass-sim0:0:0:0): Retrying Command ... (da8:umass-sim0:0:0:0): error 5 (da8:umass-sim0:0:0:0): Retries Exhausted da8: reading primary partition table: error accessing offset for 512 Mounting root from ufs:da8s1a no disk named 'da8s1a' setrootbyname failed ffs_mountroot: can't find rootvp kthread 0xffe02050d700 syncer3 has exited Root mount failed: 6 And there does not exist the 'da8s1a' device when listing: mountroot> ? Possibly valid devices for root FS: "vn0" "vn1" "vn2" "vn3" "md0" "md0s0" "sg8" "sg0" "da8" "da0" "da0s1" "da0s2" "da0s5" "da0s6" "da0s7" "mapper/control" I also tried to disable the "xhci" load, but the same issue remained. On the other hand, I tried to install FreeBSD (11-current) on that laptop and succeeded. And I can read the same USB device (with the DragonFly image dd'd into it) under FreeBSD (with the "geom_part_bsd64" module loaded). P.S.: I noticed there already existed a related bug report #2822 with this similar issue. But I think this bug may not related with the USB3.0, but very likely due to the CAM, and that bug stalls for a long time. Therefore I decide to open a new bug report. It's my pleasure to provide any further information if necessary. Best regards! Aly ---Files dmesg (86.8 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3273] (Closed) README: test patch
Issue #3273 has been updated by tuxillo. Status changed from New to Closed Bug #3273: README: test patch http://bugs.dragonflybsd.org/issues/3273#change-14075 * Author: tuxillo * Status: Closed * Priority: Normal * Assignee: * Category: * Target version: This message is in MIME format. --=_RmkuH762ASuwpEkQRLgwFg1 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline This is a test patch --=_RmkuH762ASuwpEkQRLgwFg1 Content-Type: text/plain; charset=utf-8 Content-Language: en_us [Attachment stripped: Original attachment type: "text/x-diff", name: "0001-README-test-commit.patch"] --=_RmkuH762ASuwpEkQRLgwFg1-- -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3273] (New) README: test patch
Issue #3273 has been reported by tuxillo. Bug #3273: README: test patch http://bugs.dragonflybsd.org/issues/3273 * Author: tuxillo * Status: New * Priority: Normal * Assignee: * Category: * Target version: This message is in MIME format. --=_RmkuH762ASuwpEkQRLgwFg1 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline This is a test patch --=_RmkuH762ASuwpEkQRLgwFg1 Content-Type: text/plain; charset=utf-8 Content-Language: en_us [Attachment stripped: Original attachment type: "text/x-diff", name: "0001-README-test-commit.patch"] --=_RmkuH762ASuwpEkQRLgwFg1-- -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3271] (Closed) README: test patch
Issue #3271 has been updated by tuxillo. Status changed from New to Closed Assignee set to tuxillo Bug #3271: README: test patch http://bugs.dragonflybsd.org/issues/3271#change-14074 * Author: tuxillo * Status: Closed * Priority: Normal * Assignee: tuxillo * Category: * Target version: This message is in MIME format. --=_RmkuH762ASuwpEkQRLgwFg1 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline This is a test patch --=_RmkuH762ASuwpEkQRLgwFg1 Content-Type: text/plain; charset=utf-8 Content-Language: en_us [Attachment stripped: Original attachment type: "text/x-diff", name: "0001-README-test-commit.patch"] --=_RmkuH762ASuwpEkQRLgwFg1-- -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2917] da8: reading primary partition table: error accessing offset 000000000000 for 512
Issue #2917 has been updated by falsifian. (To be clear, the dmesg I attached doesn't include any attempts to use a USB device.) Bug #2917: da8: reading primary partition table: error accessing offset for 512 http://bugs.dragonflybsd.org/issues/2917#change-14073 * Author: liweitianux * Status: New * Priority: Normal * Assignee: * Category: Driver * Target version: 6.2 Hello, Recently, I tried to install DragonFly BSD on my old ThinkPad X200 with both the 20160512-snapshot and 4.4.3-release USB image. However, DragonFly failed to mount root from the USB device. I enabled the verbose boot, and got the following error message: (da8:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR (da8:umass-sim0:0:0:0): Retrying Command ... (da8:umass-sim0:0:0:0): error 5 (da8:umass-sim0:0:0:0): Retries Exhausted da8: reading primary partition table: error accessing offset for 512 Mounting root from ufs:da8s1a no disk named 'da8s1a' setrootbyname failed ffs_mountroot: can't find rootvp kthread 0xffe02050d700 syncer3 has exited Root mount failed: 6 And there does not exist the 'da8s1a' device when listing: mountroot> ? Possibly valid devices for root FS: "vn0" "vn1" "vn2" "vn3" "md0" "md0s0" "sg8" "sg0" "da8" "da0" "da0s1" "da0s2" "da0s5" "da0s6" "da0s7" "mapper/control" I also tried to disable the "xhci" load, but the same issue remained. On the other hand, I tried to install FreeBSD (11-current) on that laptop and succeeded. And I can read the same USB device (with the DragonFly image dd'd into it) under FreeBSD (with the "geom_part_bsd64" module loaded). P.S.: I noticed there already existed a related bug report #2822 with this similar issue. But I think this bug may not related with the USB3.0, but very likely due to the CAM, and that bug stalls for a long time. Therefore I decide to open a new bug report. It's my pleasure to provide any further information if necessary. Best regards! Aly ---Files dmesg (86.8 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2917] da8: reading primary partition table: error accessing offset 000000000000 for 512
Issue #2917 has been updated by falsifian. File dmesg added I got the same error trying to install 6.0 on my Lenovo T430s. Disabling ehci (per liweitianux's instructions above) didn't help: da8 just completely disappeared. Fortunately, switching to a different USB port solved the problem. (The working one has an "SS" logo beside it.) Attached: dmesg, including boots into 6.0 and, later, master. Bug #2917: da8: reading primary partition table: error accessing offset for 512 http://bugs.dragonflybsd.org/issues/2917#change-14072 * Author: liweitianux * Status: New * Priority: Normal * Assignee: * Category: Driver * Target version: 6.2 Hello, Recently, I tried to install DragonFly BSD on my old ThinkPad X200 with both the 20160512-snapshot and 4.4.3-release USB image. However, DragonFly failed to mount root from the USB device. I enabled the verbose boot, and got the following error message: (da8:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR (da8:umass-sim0:0:0:0): Retrying Command ... (da8:umass-sim0:0:0:0): error 5 (da8:umass-sim0:0:0:0): Retries Exhausted da8: reading primary partition table: error accessing offset for 512 Mounting root from ufs:da8s1a no disk named 'da8s1a' setrootbyname failed ffs_mountroot: can't find rootvp kthread 0xffe02050d700 syncer3 has exited Root mount failed: 6 And there does not exist the 'da8s1a' device when listing: mountroot> ? Possibly valid devices for root FS: "vn0" "vn1" "vn2" "vn3" "md0" "md0s0" "sg8" "sg0" "da8" "da0" "da0s1" "da0s2" "da0s5" "da0s6" "da0s7" "mapper/control" I also tried to disable the "xhci" load, but the same issue remained. On the other hand, I tried to install FreeBSD (11-current) on that laptop and succeeded. And I can read the same USB device (with the DragonFly image dd'd into it) under FreeBSD (with the "geom_part_bsd64" module loaded). P.S.: I noticed there already existed a related bug report #2822 with this similar issue. But I think this bug may not related with the USB3.0, but very likely due to the CAM, and that bug stalls for a long time. Therefore I decide to open a new bug report. It's my pleasure to provide any further information if necessary. Best regards! Aly ---Files dmesg (86.8 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3271] (New) README: test patch
Issue #3271 has been reported by tuxillo. Bug #3271: README: test patch http://bugs.dragonflybsd.org/issues/3271 * Author: tuxillo * Status: New * Priority: Normal * Assignee: * Category: * Target version: This message is in MIME format. --=_RmkuH762ASuwpEkQRLgwFg1 Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline This is a test patch --=_RmkuH762ASuwpEkQRLgwFg1 Content-Type: text/plain; charset=utf-8 Content-Language: en_us [Attachment stripped: Original attachment type: "text/x-diff", name: "0001-README-test-commit.patch"] --=_RmkuH762ASuwpEkQRLgwFg1-- -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #2414] Lenovo S10 acpi freeze (not new)
Issue #2414 has been updated by tuxillo. Target version changed from 4.2 to 6.0 Parent was #2653, now removed. Need to verify if this is solved or we close it. Bug #2414: Lenovo S10 acpi freeze (not new) http://bugs.dragonflybsd.org/issues/2414#change-14067 * Author: davshao * Status: In Progress * Priority: Normal * Assignee: * Category: Other * Target version: 6.0 The Lenovo S10 is a netbook that apparently uses an Intel 945 express chipset. I can't say any recent update has broken booting when acpi is enabled: acpi has never functioned for DragonFly. Using master through 859bc3f7658630c523bbad944a2b95089f48de46 tcp: RFC3517bis is now officially RFC6675 Locks up after booting with acpi enabled at: cryptosoft0: [attached!] on motherboard acpi0.nexus0.root0 acpi0: [tentative on motherboard] ndepotmags=6 x mag_cap=22 for Acpi-Namespace ndepotmags=6 x mag_cap=22 for Acpi-State ndepotmags=6 x mag_cap=22 for Acpi-Parse ndepotmags=6 x mag_cap=22 for Acpi-ParseExt ndepotmags=6 x mag_cap=22 for Acpi-Operand IOAPIC: irq9, gsi 9 edge/high -> level/low Here are some pieces from dmesg after booting with acpi disabled: ACPI SDT: RSDP not in EBDA ACPI SDT: RSDP in BIOS mem ACPI FADT: SCI irq 9, level/low MPTABLE: warning duplicated PCI int entry for bus 0, dev 29, pin 0 MPTABLE: warning duplicated PCI int entry for bus 0, dev 31, pin 1 MPTABLE: warning duplicated PCI int entry for bus 0, dev 31, pin 1 ... CPU: Intel(R) Atom(TM) CPU N270 @ 1.60GHz (1596.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106c2 Stepping = 2 Features=0xbfe9fbff Features2=0x40c39d AMD Features=0x10 AMD Features2=0x1 ... ACPI MADT: LAPIC address 0xfee0, flags 0x1 ACPI MADT: BSP apic id 0 ACPI MADT: cpu id 0, apic id 0 ACPI MADT: cpu id 1, apic id 1 lapic: divisor index 0, frequency 66500312 Hz SMP: CPU0 apic_initialize(): lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff SMP: Waiting APs LAPIC initialization SMP: CPU1 apic_initialize(): lint0: 0x0001 lint1: 0x00010400 TPR: 0x SVR: 0x01ff ACPI MADT: warning invalid intsrc irq 9 trig, level ACPI MADT: IOAPIC addr 0xfec0, apic id 2, gsi base 0 ACPI MADT: INTSRC irq 0 -> gsi 2 edge/high ... IOAPIC: irq 9, gsi 9 -> cpu0 (sci) IOAPIC: irq 9 -> gsi 9 edge/high ... IOAPIC: legacy irq max 24 ... ELCR Found. ISA IRQs programmed as: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 E E E L E L E E E E L L E E E E MPTABLE: 0:28 INTA -> IOAPIC 0.17 MPTABLE: 0:27 INTA -> IOAPIC 0.22 MPTABLE: 0:29 INTB -> IOAPIC 0.19 MPTABLE: 0:2 INTA -> IOAPIC 0.16 MPTABLE: 0:28 INTB -> IOAPIC 0.16 MPTABLE: 0:28 INTC -> IOAPIC 0.18 MPTABLE: 0:29 INTA -> IOAPIC 0.23 MPTABLE: 0:29 INTC -> IOAPIC 0.18 MPTABLE: 0:29 INTD -> IOAPIC 0.16 MPTABLE: 0:31 INTB -> IOAPIC 0.19 MPTABLE: 2:0 INTA -> IOAPIC 0.16 ... BITS within APICID: logical_CPU_bits: 1; core_bits: 0 CPU Topology: cores_per_chip: 1; threads_per_core: 2; chips_per_package: 1; Start scheduler helpers on cpus: cpu0 - HyperThreading available. Core siblings: cpu0 cpu1 cpu1 - HyperThreading available. Core siblings: cpu0 cpu1 start dummy scheduler helpers on cpus: 0 1 ... IOAPIC: rman cpu0 0 - 1 IOAPIC: rman cpu0 3 - 95 IOAPIC: rman cpu0 97 - 191 IOAPIC: rman cpu1 24 - 95 IOAPIC: rman cpu1 97 - 191 npx0.nexus0.root0 npx0: [tentative] on motherboard npx0: INT 16 interface Using XMM optimized bcopy/copyin/copyout npx0: [attached!] on motherboard cryptosoft0.nexus0.root0 cryptosoft0: [tentative] on motherboard crypto: assign cryptosoft0 driver id 0, flags 234881024 crypto: cryptosoft0 registers alg 1 flags 0 maxoplen 0 ... crypto: cryptosoft0 registers alg 17 flags 0 maxoplen 0 cryptosoft0: [attached!] on motherboard pci_open(1):mode 1 addr port (0x0cf8) is 0x8000fa04 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=27ac8086) pcibios: BIOS version 3.00 $PIR: checksum failed! pcib0.legacy0.nexus0.root0 pcib0: [tentative] pcibus 0 on motherboard pci0.pcib0.legacy0.nexus0.root0 pci0: [tentative] on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x8086, dev=0x27ac, revid=0x03 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x2090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x27ae, revid=0x03 domain=0, bus=0, slot=2, func=0 ... agp0: [attached!] on vgapci0 ... usb0: [tentative] on uhci0 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3267] (Closed) dsynth: add zstd support
Issue #3267 has been updated by tuxillo. Status changed from New to Closed Assignee set to dillon Target version set to 6.0 % Done changed from 0 to 100 * Added in commit:ef0c0bf5ad3bdb1ebf8973ba32e94acc305df985 and commit:8d6cd05878ed6cc46db3a29cbe119a49fc6be7df Bug #3267: dsynth: add zstd support http://bugs.dragonflybsd.org/issues/3267#change-13975 * Author: piecuch * Status: Closed * Priority: Normal * Assignee: dillon * Category: Userland * Target version: 6.0 Adds zstd support for dsynth ---Files 0001-dsynth-add-zstd-support.patch (3.51 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
[DragonFlyBSD - Bug #3268] parent process does not receive POLLHUP events
Issue #3268 has been updated by mikdusan. *confirmed* : "pollhup02.patch":https://bugs.dragonflybsd.org/attachments/1677 *fixes issue* for me: * applied against DragonFly_RELEASE_6_0 * "main.c":https://bugs.dragonflybsd.org/attachments/1675 now works * zig @std.ChildProcess.exec()@ now works Thank you much Matt! Bug #3268: parent process does not receive POLLHUP events http://bugs.dragonflybsd.org/issues/3268#change-13973 * Author: mikdusan * Status: In Progress * Priority: High * Assignee: dillon * Category: Userland * Target version: Latest stable The attached `main.c` code is a reduction which takes as args, a command (absolute path) to fork/exec and poll stdout/stderr. POLLHUP events should be issued for both pipes when the child is finished. For the Zig project we have this implemented in the zig language but I've provided a similar .c implementation since it was already done during my triage. For both .zig and .c code, linux, macos, freebsd, netbsd, openbsd work as expected and dragonfly manifests this unexpected behaviour of not receiving POLLHUP. In the provided reduction, the bug manifests as an infinite loop after reading the bytes from child stdout/stderr. The parent keeps getting POLLIN events, and the read keeps returning 0 nbytes read which indicate the pipe has been closed. In the interim I will likely workaround this bug with conditional code for dragonfly to key off nbytes=0. I have reproduced the bug on dragonfly 5.8, 6.0 and 5.0.0 (the oldest .iso I could find). ---Files main.c (3.2 KB) pollhup01.patch (357 Bytes) pollhup02.patch (1.86 KB) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
