[DragonFlyBSD - Bug #2822] USB 3.0 stick throws reading primary partition table: error accessing offset 000[...] for 152 error, while the stick works on any other OS I tested

2015-06-29 Thread bugtracker-admin
Issue #2822 has been updated by profmakx. Assignee set to profmakx Bug #2822: USB 3.0 stick throws reading primary partition table: error accessing offset 000[...] for 152 error, while the stick works on any other OS I tested

[DragonFlyBSD - Bug #2686] kernel 3.8.1 freezes and panics at boot

2015-06-29 Thread bugtracker-admin
Issue #2686 has been updated by peeter. File no-prt-found-dragonfly-boot-crash.jpg added Thanks! I mean the kernel still panics later in the boot process (see attached jpg) and gives the db prompt. But since the keyboard is hung/frozen, I can't call dumpsys. There's an error message at the

[DragonFlyBSD - Bug #2686] kernel 3.8.1 freezes and panics at boot

2015-06-29 Thread bugtracker-admin
Issue #2686 has been updated by profmakx. Oh my god, I am so sorry. I did exactly what your patch does, but apparently that didn't end up in the patch I posted. I'll apply this, and test it. Unfortunately it'll be too late for 4.2, but 4.2.1 will then contain this fix (as well as -master of

[DragonFlyBSD - Bug #2686] kernel 3.8.1 freezes and panics at boot

2015-06-29 Thread bugtracker-admin
Issue #2686 has been updated by peeter. File dragonfly-boot-crash-verbose-no-prt.png added And here's the verbose boot---it's less helpful though since the No _PRT found error is out of the screen. I am working with the assumption that the latter is the culprit. Ideally one would get the

[DragonFlyBSD - Bug #2686] kernel 3.8.1 freezes and panics at boot

2015-06-29 Thread bugtracker-admin
Issue #2686 has been updated by peeter. It would be helpful if one could get a dumpsys. Since the keyboard is hung/frozen, I tried to fake a call dumpsys by brute force: I hardcoded in the sys/ddb/db_lex.c: db_read_line() that it returns call dumpsys to sys/ddb/db_input.c: db_readline()