[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #28 from Andriy Gapon --- (In reply to Wojciech Giel from comment #27) No worries. Thank you very much! The latest information is something to chew on. -- You are receiving this mail because: You are the

[Bug 213488] bsdinstall wants MANIFEST from filesystem even when installing from ftp

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213488 Bug ID: 213488 Summary: bsdinstall wants MANIFEST from filesystem even when installing from ftp Product: Base System Version: 11.0-STABLE Hardware: Any

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #29 from Andriy Gapon --- A fellow developer suggests that the following command could provide more of interesting information: show active trace Could you please reproduce the panic and run that command? It

[Bug 213462] Retry_count in minidump code delaying ENOSPC by around 30 minutes for live cores.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213462 --- Comment #2 from rdarbha --- please review this https://reviews.freebsd.org/D8254 -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 213462] Retry_count in minidump code delaying ENOSPC by around 30 minutes for live cores.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213462 --- Comment #1 from rdarbha --- Please check this review https://reviews.freebsd.org/D8254 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 213474] sed behaviuor with a/i/c operands.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213474 Bug ID: 213474 Summary: sed behaviuor with a/i/c operands. Product: Base System Version: 11.0-STABLE Hardware: Any OS: Any Status: New Severity:

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #10 from Wojciech Giel --- Created attachment 175736 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175736=edit bt tid 4 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #9 from Wojciech Giel --- Created attachment 175735 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175735=edit bt tid 3 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #11 from Wojciech Giel --- tid 100245 returns No such command? -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 57696] [nfs] NFS client readdir terminates prematurely if renaming files

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=57696 mur...@stokely.org changed: What|Removed |Added CC||mur...@stokely.org --- Comment

[Bug 212718] cp(1)/mv(1)/install(1) cause vm_fault/panic on VIA boards w/USB cards/sticks.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212718 --- Comment #7 from nibb...@gmx.us --- There is often a huge file loss after rebooting after these panics. Rarely directories, if at all - but often dozens of the most recently created files. -- You are receiving this mail because: You

[Bug 212718] cp(1)/mv(1)/install(1) cause vm_fault/panic on VIA boards w/USB cards/sticks.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212718 nibb...@gmx.us changed: What|Removed |Added Component|bin |kern

[Bug 213497] Vidcontrol is a complete disaster!

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213497 Bug ID: 213497 Summary: Vidcontrol is a complete disaster! Product: Base System Version: 11.0-STABLE Hardware: i386 OS: Any Status: New Severity:

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #14 from Andriy Gapon --- (In reply to Wojciech Giel from comment #13) I am a little bit confused. Could you please do the following? bt thread bt So, I want to get 3 pictures of the same panic.

[Bug 213225] boot problem with 11.0-RELEASE Bootloader not found kernel

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213225 --- Comment #6 from the_t...@gmx.de --- Created attachment 175738 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175738=edit FreeBSD-11.0-RELEASE P1 vm.pmap.pcid_enabled=0 not help me... -- You are receiving this mail

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 Andriy Gapon changed: What|Removed |Added Attachment #175735|0 |1 is

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 Andriy Gapon changed: What|Removed |Added Attachment #175709|0 |1 is

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 Andriy Gapon changed: What|Removed |Added Attachment #175706|0 |1 is

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 Andriy Gapon changed: What|Removed |Added Attachment #175708|0 |1 is

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 Andriy Gapon changed: What|Removed |Added Attachment #175706|1 |0 is

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #15 from Wojciech Giel --- Created attachment 175742 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175742=edit bt -- You are receiving this mail because: You are the assignee for the bug.

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #18 from Andriy Gapon --- (In reply to Wojciech Giel from comment #17) Well, my instructions started with bt So, the first picture should be taken before any commands. Please take another 3 pictures

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #17 from Wojciech Giel --- Created attachment 175744 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175744=edit bt second time got three separate screenshots -- You are receiving this mail

[Bug 213481] SMbus ioctls don't transfer the struct smbcmd's rdata back to userland

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213481 Bug ID: 213481 Summary: SMbus ioctls don't transfer the struct smbcmd's rdata back to userland Product: Base System Version: CURRENT Hardware: Any

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #12 from Andriy Gapon --- (In reply to Wojciech Giel from comment #11) I apologise again, I confused a kgdb command with a ddb command. So, instead of 'tid' it should be 'thread'. Could you please obtain the

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 Andriy Gapon changed: What|Removed |Added Attachment #175739|0 |1 is

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 Andriy Gapon changed: What|Removed |Added Attachment #175736|0 |1 is

[Bug 213479] [patch] Fix ggatec; should support other than BIO_READ / BIO_WRITE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213479 Bug ID: 213479 Summary: [patch] Fix ggatec; should support other than BIO_READ / BIO_WRITE Product: Base System Version: CURRENT Hardware: Any OS:

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #21 from Wojciech Giel --- Created attachment 175749 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175749=edit 03.thread -- You are receiving this mail because: You are the assignee for the bug.

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #20 from Wojciech Giel --- Created attachment 175748 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175748=edit 02.bt -- You are receiving this mail because: You are the assignee for the bug.

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #19 from Wojciech Giel --- Created attachment 175747 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175747=edit 01.panic -- You are receiving this mail because: You are the assignee for the bug.

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #22 from Wojciech Giel --- Created attachment 175750 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175750=edit 04.bt -- You are receiving this mail because: You are the assignee for the bug.

[Bug 212914] CAM: SATA drives are getting deleted and then re-added after controller rescan

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212914 --- Comment #3 from Kashyap --- Here is CAMDEBUG enabled logs for SAS Drives. This is a working case - Oct 14 18:56:06 freeBSD11_RC1 kernel: cam_debug: xpt_run_allocq(0xf80060a62e00) Oct 14 18:56:06

[Bug 213491] gpt{,zfs}boot after r305353 crash in GELIBoot

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213491 Allan Jude changed: What|Removed |Added Severity|Affects Only Me |Affects Many

[Bug 213491] gpt{,zfs}boot after r305353 crash in GELIBoot

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213491 Bug ID: 213491 Summary: gpt{,zfs}boot after r305353 crash in GELIBoot Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 Andriy Gapon changed: What|Removed |Added Attachment #175743|0 |1 is

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 Andriy Gapon changed: What|Removed |Added Attachment #175748|0 |1 is

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 Andriy Gapon changed: What|Removed |Added Attachment #175747|0 |1 is

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 Andriy Gapon changed: What|Removed |Added Attachment #175749|0 |1 is

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 Andriy Gapon changed: What|Removed |Added Attachment #175750|0 |1 is

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 Andriy Gapon changed: What|Removed |Added Attachment #175744|0 |1 is

[Bug 213481] SMbus ioctls don't transfer the struct smbcmd's rdata back to userland

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213481 Andriy Gapon changed: What|Removed |Added CC||a...@freebsd.org

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 Andriy Gapon changed: What|Removed |Added Attachment #175742|0 |1 is

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #23 from Andriy Gapon --- Using your latest pictures as an example, you did 'thread 100186', but I what asked you to do was 'thread 100346'. Remember, I said the id reported in the "too long" message. That

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #25 from Wojciech Giel --- Created attachment 175753 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175753=edit 02.bt -- You are receiving this mail because: You are the assignee for the bug.

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #24 from Wojciech Giel --- Created attachment 175752 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175752=edit 01.panic -- You are receiving this mail because: You are the assignee for the bug.

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #26 from Wojciech Giel --- Created attachment 175754 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175754=edit 03.thread -- You are receiving this mail because: You are the assignee for the bug.

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #27 from Wojciech Giel --- Created attachment 175755 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175755=edit 04.thread cd sorry. it was a bit confusing. -- You are receiving this mail because:

[Bug 211705] Several "sdhci_pci0-slot0: Controller Timeout" messages during boot - no sdcard is connected [MSI Board "Cubi-N"]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211705 --- Comment #2 from miguelmcl...@gmail.com --- This is (as expected since nothing changed) still happening with 11.0-RELEASE. If I were to compile the kernel for this specific box, what could I disable get rid of the message? -- You are

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #13 from Wojciech Giel --- Created attachment 175739 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175739=edit bt thread no much there -- You are receiving this mail because: You are the assignee

[Bug 213371] panic: spin lock held too long

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213371 --- Comment #16 from Wojciech Giel --- Created attachment 175743 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175743=edit thread -- You are receiving this mail because: You are the assignee for the bug.