https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
Bjoern A. Zeeb changed:
What|Removed |Added
Assignee|u...@freebsd.org |b...@freebsd.org
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #175 from Kurt Jaeger ---
(In reply to Gerard Seibert from comment #173)
The problem is not that no-one is working on it, the problem is that
hsp, who might be able to fix it, does not have a hardware where he can
reproduce the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #174 from Graham Perrin ---
(In reply to Gerard Seibert from comment #173)
Kindly refrain. Observe and understand the comments from people who contribute
positively towards progress.
--
You are receiving this mail because:
Yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #173 from Gerard Seibert ---
Well, considering that this bug is over two years old now, and apparently with
no one actively researching the problem, that I can safely say it will never
get fixed. It is a shame since the bug did
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #172 from tech-li...@zyxst.net ---
(In reply to Gerard Seibert from comment #171)
Hi
as far as I can tell, the issue is still present in a world built 28th March
2021 from stable/13-n245213-f28241ca134
--
You are receiving thi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #171 from Gerard Seibert ---
Just checking in. Has a fix been found for this problem? It doesn't appear that
there has been any movement on it for quite a while.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
Mohammad Noureldin changed:
What|Removed |Added
CC||moham...@thelightbird.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #169 from Hans Petter Selasky ---
Is it possible to get SSH root access to a machine exhibiting this problem?
Need to be able to install a new kernel there at least.
--HPS
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #168 from Gerard Seibert ---
(In reply to tech-lists from comment #167)
I really wish that this could be corrected and included with the release of
FreeBSD version 13. I know it will never happen; however, it would be nice to
a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #167 from tech-li...@zyxst.net ---
(In reply to Gerard Seibert from comment #165)
Just for curiosity, I tried commenting out ehci (i.e. disabling usb2) and
uncommented xhci (so enabling usb3) and then rebuilding kernel, and it *
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #166 from tech-li...@zyxst.net ---
(In reply to Gerard Seibert from comment #165)
OK. Commenting out device xhci from the generic config "fixes" the problem, in
that the "device vanished" messages no longer appear at the console
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #165 from Gerard Seibert ---
(In reply to tech-lists from comment #164)
Nice catch. I want to find out if others experiencing this problem are also
using the same hardware.
The question should not be if I really require usb3,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #164 from tech-li...@zyxst.net ---
(In reply to Gerard Seibert from comment #163)
Do you absolutely require usb3?
We have in common this hardware:
device = 'ASM1142 USB 3.1 Host Controller'
I'm going to build a GENERIC ke
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #163 from Gerard Seibert ---
(In reply to tech-lists from comment #162)
I am in the same boat. Presently, I am stuck on FreeBSD 11. I cannot move past
this version due to this bug. Considering that it was not present in versions
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
tech-li...@zyxst.net changed:
What|Removed |Added
CC||tech-li...@zyxst.net
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
Eirik Oeverby changed:
What|Removed |Added
CC||ltning-free...@anduin.net
--- Comm
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #160 from Gerard Seibert ---
(In reply to Hans Petter Selasky from comment #159)
Unfortunately, I only have one system running FreeBSD at present. To do as you
ask would require me to take that system offline, and I cannot affo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #159 from Hans Petter Selasky ---
Hi Gerard,
There is no news here basically.
However, can you try installing the latest 11 release.
Then checkout sources for FreeBSD 12-stable.
Then do two experiments:
a) Apply the PCI deb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
Hans Petter Selasky changed:
What|Removed |Added
Status|Open|In Progress
--
You are rece
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #158 from Hans Petter Selasky ---
Created attachment 220423
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=220423&action=edit
PCI debug patch
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #157 from Gerard Seibert ---
(In reply to commit-hook from comment #156)
I was unable to install FreeBSD 12.x due to this bug. Does this commit correct
it, or does it simply change the way debug info for the problem is disclose
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #156 from commit-h...@freebsd.org ---
A commit references this bug:
Author: bz
Date: Mon Nov 9 23:38:39 UTC 2020
New revision: 367540
URL: https://svnweb.freebsd.org/changeset/base/367540
Log:
MFC r367435,367539:
usb_hu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #155 from commit-h...@freebsd.org ---
A commit references this bug:
Author: bz
Date: Fri Nov 6 22:40:00 UTC 2020
New revision: 367435
URL: https://svnweb.freebsd.org/changeset/base/367435
Log:
usb_hub: giving up port reset -
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #154 from Bjoern A. Zeeb ---
I found myself trying to see what is going on (given sometimes it does happen
to me on x86 when I plug in/unplug USB[-C] hubs and USB devices.
By the time it started turning logging on is possibly t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #153 from Bjoern A. Zeeb ---
Ok, got it on an arm64 on HEAD which also shows:
uhub_reattach_port: giving up port reset - device vanished
uhub_reattach_port: giving up port reset - device vanished
uhub_reattach_port: giving up p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #152 from Rpapousek ---
(In reply to Mike Karels from comment #151)
OK that was my help for users who have has problems as mine with installation.
Just by the way I solved problems with Truenas ver.12
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #151 from Mike Karels ---
(In reply to Rpapousek from comment #150)
I think we are talking about different problems, or different manifestations.
My problem had nothing to do with install. I had installed long ago on a much
ea
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #150 from Rpapousek ---
(In reply to Mike Karels from comment #149)
I don´t know how did you install your system but in my case when I try install
from DVD-Rom or USB DVD-Rom error still occurred. Same result when I chose
other
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #149 from Mike Karels ---
In my case, and in the original bug description, the problem happened with *no*
USB devices attached; nothing to unplug. The reported solution is not a
general solution.
--
You are receiving this mai
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #148 from Gerard Seibert ---
(In reply to Rpapousek from comment #147)
I don't have a machine set up to try this on presently. However, I question why
it would work though. I don't have a great knowledge of how USB works exactly
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
Rpapousek changed:
What|Removed |Added
CC||rpapou...@gmail.com
--- Comment #147 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #146 from Mark Millard ---
(In reply to Gerard Seibert from comment #145)
Comment 139 makes it seem unlikely that the fix above to my context
would be the fix to yours or most of the reports here. (No one, besides
me, commented
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #145 from Gerard Seibert ---
I admit to not being the sharpest knife in the drawer, so bear with me here.
1) Will the fix mentioned above correct the problem on a Dell XPS 8930 PC? I
have never been able to run anything newer t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #143 from commit-h...@freebsd.org ---
A commit references this bug:
Author: hselasky
Date: Sat Sep 26 08:44:16 UTC 2020
New revision: 366182
URL: https://svnweb.freebsd.org/changeset/base/366182
Log:
MFC r365918:
Fix for us
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #144 from commit-h...@freebsd.org ---
A commit references this bug:
Author: hselasky
Date: Sat Sep 26 08:45:09 UTC 2020
New revision: 366183
URL: https://svnweb.freebsd.org/changeset/base/366183
Log:
MFC r365918:
Fix for us
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #142 from Mark Millard ---
(In reply to Bjoern A. Zeeb from comment #141)
Good to know.
If you repeat the #125 experiment based on the patch,
does it still end up stuck in the repeating sequence
that involves "Resetting contro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #141 from Bjoern A. Zeeb ---
(In reply to Mark Millard from comment #140)
"ugen0.1: <0x8086 XHCI root HUB> at usbus0 (disconnected)"
is a huge clue that it wasn't arm64 ;-) It was on an Intel laptop with
external USB-C multi-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #140 from Mark Millard ---
(In reply to Mike Karels from comment #139)
Drat. Well, at least Bjoern A. Zeeb's comment #125 might also
be covered by the patch involved for changeset/base/365918 ,
given how closely the console log
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #139 from Mike Karels ---
(In reply to Mark Millard from comment #138)
The change in xhci.c does not fix the repeating "device vanished" messages on
my amd64; tested with releng/12.1 plus this fix. I suspect that Mark tripped
o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #138 from Mark Millard ---
(In reply to commit-hook from comment #137)
Folks with other platforms that show problems under this
bugzilla id (237666) may want to check if the update removes
their problems in this area. I had onl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #137 from commit-h...@freebsd.org ---
A commit references this bug:
Author: hselasky
Date: Sat Sep 19 22:37:46 UTC 2020
New revision: 365918
URL: https://svnweb.freebsd.org/changeset/base/365918
Log:
Fix for use of the XHCI d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #136 from Hans Petter Selasky ---
Mark,
Your finding indicate a problem in usb_pc_cpu_flush() and
bus_dmamap_sync(pc->tag, pc->map, BUS_DMASYNC_PREWRITE);
Try to put the dsb only after dmamap_sync.
void
usb_pc_cpu_flush(str
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #135 from Mark Millard ---
(In reply to Mark Millard from comment #134)
A cortex-a72 success! (In the form of investigatory code, not
code to check-in as is.)
Just by adding some "dsb st" commands and a "dsb ld" command in
pla
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #134 from Mark Millard ---
(In reply to Mark Millard from comment #133)
The code in xhci_do_command does a doorbell/mailbox style:
XWRITE4(sc, door, XHCI_DOORBELL(0), 0);
which seems to get to:
007c4b60
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #133 from Mark Millard ---
The message:
xhci0: Resetting controller
comes via code in xhci_do_command that has the following comment:
/*
* After some weeks of continuous operation, it has
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #132 from Mark Millard ---
(In reply to Mark Millard from comment #126, #128, #131)
Interesting finding? . . .
I've tested putting the -mcpu=cortex-a72 based kernel
on the cortext-a53 system and . . .
The result boots and ope
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #131 from Mark Millard ---
(In reply to bawdyanarch...@disroot.org from comment #130)
Just to avoid misinterpretations of what I've reported:
I run head/CURRENT, not 12.x . It was not an FreeBSD version
upgrade context at all.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #130 from bawdyanarch...@disroot.org
---
(In reply to Mark Millard from comment #128)
I see your point about the ARM devices. If I read correctly, this is a problem
you didn't have until upgrading to 12.1. Could be that we h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #129 from Gerard Seibert ---
(In reply to Mark Millard from comment #128)
As far as I can ascertain, this problem is localized to FreeBSD. I have friends
that use other operating systems like Linux on equipment similar to mine
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #128 from Mark Millard ---
(In reply to bawdyanarch...@disroot.org from comment #127)
I'm not sure how your speculation would fit with Cortex-A72 vs.
Cortex-A53 making a difference in my context. One area where
A72 vs. A53 migh
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
Kurt Jaeger changed:
What|Removed |Added
Version|12.0-RELEASE|12.1-STABLE
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
bawdyanarch...@disroot.org changed:
What|Removed |Added
CC||bawdyanarch...@disroot
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
Mark Millard changed:
What|Removed |Added
CC||marklmi26-f...@yahoo.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #125 from Bjoern A. Zeeb ---
(In reply to Hans Petter Selasky from comment #122)
Hmm, I applied the sysctl and removed the USB-C connection again and:
uhub0: detached
ugen0.1: <0x8086 XHCI root HUB> at usbus0 (disconnected)
un
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #124 from Hans Petter Selasky ---
Can you try to reach out to Scott Long about USB-C ?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #123 from Bjoern A. Zeeb ---
(In reply to Hans Petter Selasky from comment #122)
usbconfig had already returned (maybe by setting the uhub or xhci sysctl to
0x17 I think it was).
I had in the mean time just plugged the USB-C m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #122 from Hans Petter Selasky ---
Try if this unlocks usbconfig:
sysctl hw.usb.disable_enumeration=1
sleep 10
usbconfig
--HPS
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
Bjoern A. Zeeb changed:
What|Removed |Added
CC||b...@freebsd.org
--- Comment #121
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #120 from Gerard Seibert ---
(In reply to Mike Karels from comment #119)
This bug has obviously not been given the attention it deserves. With the
planned release of versions 12.2 in October of this year and 13.0 next March,
it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #119 from Mike Karels ---
I built a fresh kernel(r364289) with r343134 reverted; the problem still
occurs.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #118 from Gerard Seibert ---
(In reply to Kubilay Kocak from comment #117)
I tried installing FreeBSD 12.1-RELEASE a couple of months ago, and the bug
still existed in that version. Are you inferring that I should try the STABL
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
Kubilay Kocak changed:
What|Removed |Added
Flags|mfc-stable11? |mfc-stable11-
--- Comment #117 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #116 from Gerard Seibert ---
Hi, I am just doing my 'beginning of the month' request to see if any headway
had been made on discovering the cause and hopefully the cure for this bug.
With the release of FreeBSD 12.2 expected on
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #115 from Gerard Seibert ---
(In reply to Ihor Antonov from comment #114)
My monitor is connected in the usual manner; however, I am utilizing a keyboard
& mouse connected via USB. The next time I attempt to install 12.x, I'll
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #114 from Ihor Antonov ---
Yes, I can reproduce the bug by unplugging my external monitor.
Monitor is connected via USB-C cable. As soon as I unplug it I see this message
in dmesg appearing roughly every second.
uhub_reattach_p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
Ihor Antonov changed:
What|Removed |Added
CC||ihor@antonovs.family
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #112 from Mike Karels ---
This bug is not fixed in 12.1-STABLE as of April 26 (r360337). If there is
reason to think that it has been fixed since then, I'm happy to test.
--
You are receiving this mail because:
You are the as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #111 from Gerard Seibert ---
Can anyone confirm that this bug has been squashed? Aryeh Friedman
claims that this bug has been fixed eons ago and
that this incident should be closed. I would like some confirmation on this, if
po
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #110 from Gerard Seibert ---
(In reply to Mike Karels from comment #109)
Thanks, Mike. I was somewhat hesitant about moving up to 11.4 because of this
bug. It would seem that someone "screwed the pooch" with version 12.x, and n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #109 from Mike Karels ---
Note that FreeBSD 11.4-BETA2 does not have this problem either.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #108 from Gerard Seibert ---
Hans Petter Selasky, since I don't have a spare machine to send you, I thought
that sending the bootup log from FreeBSD 11.3-RELEASE-p8, which does work on
this machine, might be of some use.
--
Yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #107 from Gerard Seibert ---
Created attachment 213822
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=213822&action=edit
FreeBSD 11.3 boot log
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
Gerard Seibert changed:
What|Removed |Added
Attachment #209346|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #105 from Gerard Seibert ---
(In reply to Hans Petter Selasky from comment #104)
I wish I had a spare machine to ship off to you; however, I don't. I still find
it hard to believe that this bug was not caught during the initial
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #104 from Hans Petter Selasky ---
> Does anyone have any idea if this will correct the problem? I would really
> hate to trash the whole system again if this doesn't correct the problem.
> Also, why would this problem NOT exis
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #103 from Gerard Seibert ---
I just updated the BIOS on my system. That version was only one version older
than the new one. Anyway, this is the output from 'dmidecode'.
# dmidecode 3.2
# SMBIOS entry point at 0x6fe8d000
Found
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #102 from Hans Petter Selasky ---
Hi,
I have a no-name Skylake based laptop and USB XHCI works fine.
You might find the following read interesting:
http://freebsd.1045724.x6.nabble.com/Can-t-reattach-USB-devices-Lenovo-bug-td
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #101 from Gerard Seibert ---
Apparently, this problem has existed since at least April 2019. That seems, at
least to me, to be an awfully long time, at least at this level, for a bug to
go unsquashed. I am preparing to purchase
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #100 from Mike Karels ---
I am now running a stable-12 kernel at r356868, which includes this change.
The problem is unchanged (also my problem of disconnects by the UPS). I also
tried booting with no USB devices attached; the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #99 from Hans Petter Selasky ---
This fix will only be applied to 12-stable, next week, and will be part of the
next stable release.
Else you need to build a custom kernel with this patch applied, in order to
test.
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #98 from Gerard Seibert ---
(In reply to Hans Petter Selasky from comment #97)
Will this fix be applied to FreeBSD 12.1, or will I have to wait until 12.2 is
released so that I can try it and see if it works? I am not familiar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #97 from Hans Petter Selasky ---
There has been one patch for XHCI:
https://svnweb.freebsd.org/changeset/base/356545
The issue is believed to be ACPI related.
--HPS
--
You are receiving this mail because:
You are the assign
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #96 from Gerard Seibert ---
Has there been any movement on this issue? FreeBSD 12.2 is on the horizon, and
I and others, are stuck with FreeBSD 11.x because we cannot get FreeBSD 12.x to
install and run satisfactorily. This is h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
Felix Guest changed:
What|Removed |Added
CC||felix.the@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #94 from Mike Karels ---
Looks like kern.consmute is not a loader tunable, just a sysctl. It didn't
work, and I don't see that string in the kernel. I let it scroll messages
madly for about 30 minutes, but didn't get to the po
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #93 from Hans Petter Selasky ---
Can you retry enabling full ACPI debug messages, and also set:
kern.consmute=1
In /boot/loader.conf or try via the loader first.
You will need to log in via SSH.
That way the excessive debug p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #92 from Mike Karels ---
The $1 was expanded (to nothing) when I ran your script to cat it to a file,
but I fixed it at the time. The latest version runs, but produces no output in
a minute or two. I am also not getting the de
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #91 from Hans Petter Selasky ---
#!/usr/sbin/dtrace -s
fbt::$1:entry
{
@[probefunc, stack()] = count();
}
I think the $1 was expanded when you created dtrace.d!
Can you type this script verbatim and try again?
It bas
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #90 from Mike Karels ---
Similar result:
pughole# ./dtrace.d AcpiExPciConfigSpaceHandler
dtrace: failed to compile script ./dtrace.d: line 3: probe description
:fbt:AcpiExPciConfigSpaceHandler:entry does not match any probes
-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #89 from Hans Petter Selasky ---
Can you remove "filec:" from the dtrace script?
--HPS
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@free
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #88 from Mike Karels ---
Followup on previous comment: I'm not sure why, but the system is not logging
the continuous acpi messages that it did previously. It has been rebooted
several times, including other kernels, but is bac
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #87 from Mike Karels ---
Yes, I loaded dtraceall.
Derived from the command you sent, and copying/pasting the function name:
pughole# dtrace -l | grep -i acpiexpci
30153fbtkernel AcpiExPciBarSpaceHa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #86 from Hans Petter Selasky ---
Did you do:
kldload dtraceall
first?
--HPS
dtrace -l | grep -i ACPI
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #85 from Mike Karels ---
Same result with dtrace.d:
pughole# ./dtrace.d AcpiExPciConfigSpaceHandler
dtrace: failed to compile script ./dtrace.d: line 3: probe description
fbt:AcpiExPciConfigSpaceHandler:filec:entry does not mat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #84 from Hans Petter Selasky ---
@kib: It looks like ACPI is addressing a device at PCI address 128, which is
not in the list of PCI devices on the given machine. Is this allowed?
--
You are receiving this mail because:
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #83 from Hans Petter Selasky ---
Try:
AcpiExPciConfigSpaceHandler
Instead.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mai
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #82 from Mike Karels ---
pciconf-lv is attached.
When I tried the dtrace script after kldloading dtraceall, I got this:
pughole# ./dtrace.d ExPciConfigSpaceHandle
dtrace: failed to compile script ./dtrace.d: line 3: probe desc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #81 from Mike Karels ---
Created attachment 209793
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209793&action=edit
pciconf -lv from Gigabyte system
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #80 from Hans Petter Selasky ---
Are you familiar with dtrace. Could you get the backtrace of these function
calls?
kldload dtraceall
cat << EOF > dtrace.d
#!/usr/sbin/dtrace -s
fbt::$1:entry
{
@[probefunc, stack()]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666
--- Comment #79 from Hans Petter Selasky ---
Can you show the output of "pciconf -lv" ?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-usb@freebsd.org mail
1 - 100 of 181 matches
Mail list logo
