https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220096
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-acpi@FreeBSD.org
--
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207676
--- Comment #13 from John Baldwin ---
(In reply to Mason Loring Bliss from comment #12)
Were the warnings no longer present in your 11.1-PRERELEASE test as well? If
so, it seems that the newer ACPICA in 11.1 includes the fix for this issue
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220096
John Baldwin changed:
What|Removed |Added
Resolution|FIXED |Works As Intended
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220096
John Baldwin changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207676
--- Comment #14 from Mason Loring Bliss ---
Correct. The issue appears to have been resolved, and this bug can be closed.
(Agreed, there's little reason to backport to 11.0 as long as folks understand
that they need to run 11.1 if they expe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207676
John Baldwin changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=122887
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #9 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223435
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-acpi@FreeBSD.org
--
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223944
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-acpi@FreeBSD.org
--
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223435
Neel Chauhan changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224096
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-acpi@FreeBSD.org
--
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224096
John Baldwin changed:
What|Removed |Added
Status|New |In Progress
--- Comment #1 from Joh
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224557
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-b...@freebsd.org|freebsd-acpi@FreeBSD.org
--
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224557
--- Comment #1 from Neel Chauhan ---
A 128GB Kingston SSDNow 300 SSD also had this issue. On a Zotac BI323, this
exact SSD did not have an issue. It's not an issue with Sandisk or Kingston,
but with Dell and Insyde (who makes the UEFI in th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224557
--- Comment #2 from Neel Chauhan ---
FreeBSD 12-CURRENT r329320 does not have this issue. Thank god!
However, 11-STABLE r329338 still has this issue. Maybe it has been patched in
HEAD but hasn't been MFC'd yet.
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224557
--- Comment #3 from Neel Chauhan ---
Unfortunately, the issue came back with newer CURRENTs.
Someone else also had the same issue with recent ThinkPads: Bug 220727.
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
Mark Linimon changed:
What|Removed |Added
Keywords||regression
Assignee|freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
--- Comment #1 from Mateusz Piotrowski <0...@freebsd.org> ---
I found the following lines in my dmesg:
> ACPI Error: No handler for Region [ERAM] (0xf80003621b80)
> [EmbeddedControl] (20180313/evregion-288)
> ACPI Error: Region Embedde
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
--- Comment #2 from Mateusz Piotrowski <0...@freebsd.org> ---
It is not a hardware issue apparently. I've live booted Ubuntu and it detects
my battery just fine.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
--- Comment #3 from Conrad Meyer ---
r330957 from that period is the 20180313 ACPICA merge. Probably suspect. I
don't see any other ACPI changes in that interval that relate to x86 laptops.
Any chance you can try r330956 and r330957 and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
--- Comment #4 from Conrad Meyer ---
Your dmesg line seems related (BAT0):
ACPI Error: Method parse/execution failed \134_SB.PCI0.LPCB.EC0.BAT0._STA,
AE_NOT_EXIST
Nothing changed in any of the dmesg-mentioned files (evregion, exfldio,
pspa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
--- Comment #5 from Mateusz Piotrowski <0...@freebsd.org> ---
(In reply to Conrad Meyer from comment #3)
I'm building r330956 at the moment. I'll report back.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
--- Comment #6 from Mateusz Piotrowski <0...@freebsd.org> ---
I can confirm that `acpiconf -i 0` works as expected on r330956 while being
broken on r330957.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
--- Comment #7 from Mateusz Piotrowski <0...@freebsd.org> ---
(In reply to Mateusz Piotrowski from comment #1)
Also, I get those ACPI ERROR lines from dmesg mentioned even when the battery
is detected (before r330957) so they are probably n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
Mateusz Piotrowski <0...@freebsd.org> changed:
What|Removed |Added
Keywords||needs-patch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224096
--- Comment #2 from commit-h...@freebsd.org ---
A commit references this bug:
Author: jhb
Date: Wed Apr 18 18:36:26 UTC 2018
New revision: 332733
URL: https://svnweb.freebsd.org/changeset/base/332733
Log:
Workaround fixed I/O port resour
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224096
John Baldwin changed:
What|Removed |Added
Flags||mfc-stable10?,
|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227759
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|a...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207419
Kubilay Kocak changed:
What|Removed |Added
Status|New |Open
Keywords|patch
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227759
robert.mo...@intel.com changed:
What|Removed |Added
CC||robert.mo...@intel.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227759
Jung-uk Kim changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #6 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227759
--- Comment #7 from Jung-uk Kim ---
(In reply to Jeremy Chadwick from comment #1)
This BIOS is buggy. It does not return a buffer at all when the capability is
not supported. I think we can work around it by ignoring zero-sized buffer
ins
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227759
Jung-uk Kim changed:
What|Removed |Added
Resolution|--- |Works As Intended
Status
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227759
--- Comment #8 from Jung-uk Kim ---
(In reply to Jeremy Chadwick from comment #0)
> I am hoping someone has some idea what rXX commit may have introduced
> this.
https://svnweb.freebsd.org/changeset/base/298372
--
You are receiving
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
--- Comment #8 from Mateusz Piotrowski <0...@freebsd.org> ---
Same on 12.0-CURRENT r44.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-acpi@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224557
Neel Chauhan changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213
Eugene Grosbein changed:
What|Removed |Added
CC||a...@freebsd.org
--- Comment #35
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227213
Kubilay Kocak changed:
What|Removed |Added
Keywords||crash, needs-qa
Flags
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=152792
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #4 from Eitan Adler
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223944
Allan Jude changed:
What|Removed |Added
CC||allanj...@freebsd.org
--- Comment #1
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=122887
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #10 from Eitan Adle
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173408
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #3 from Eitan Adler
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169862
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #4 from Eitan Adler
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=112544
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #13 from Eitan Adle
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181283
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #4 from Eitan Adler
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=146436
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #10 from Eitan Adle
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=172742
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #4 from Eitan Adler
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=181283
rkober...@gmail.com changed:
What|Removed |Added
CC||rkober...@gmail.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=139088
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #6 from Eitan Adler
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=105537
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #7 from Eitan Adler
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=112544
Andriy Gapon changed:
What|Removed |Added
Resolution|--- |Overcome By Events
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=172742
Andriy Gapon changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=146436
Andriy Gapon changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227191
--- Comment #9 from Mateusz Piotrowski <0...@freebsd.org> ---
(In reply to Mateusz Piotrowski from comment #8)
Can I provide any logs/recompile the system with debugging on to help debug
this issue?
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226814
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|a...@freebsd.org
Summary
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226814
robert.mo...@intel.com changed:
What|Removed |Added
CC||robert.mo...@intel.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226814
Erik Schmauss changed:
What|Removed |Added
CC||erik.schma...@intel.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226814
Gleb Popov changed:
What|Removed |Added
CC||arr...@freebsd.org
--- Comment #3 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226814
--- Comment #4 from robert.mo...@intel.com ---
This style of acpidump won't help. It is actually a disassembly.
What I need is a dump of the form below, or the actual binary tables.
SSDT @ 0x
: 53 53 44 54 27 0A 00 0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226814
Jung-uk Kim changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #5 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228654
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|a...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226814
--- Comment #6 from Gleb Popov ---
Created attachment 193888
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193888&action=edit
acpidump binary output
Oops, sorry, attaching the binary. Hope this is right one.
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226814
Mateusz Piotrowski <0...@freebsd.org> changed:
What|Removed |Added
Keywords||needs-qa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226814
--- Comment #7 from Gleb Popov ---
Created attachment 193971
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193971&action=edit
Output of sysutils/acpica-tools acpidump
I missed the "ports" word. Here is the output of the ports v
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228654
Yuri Victorovich changed:
What|Removed |Added
Summary|[12-CURRENT] ACPI suspend |[12-CURRENT] ACPI suspend
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228654
--- Comment #2 from Yuri Victorovich ---
Hardware: Lenovo laptop IdeaPad 320.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-acpi@freebsd.org mailing list
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229074
Mark Linimon changed:
What|Removed |Added
Keywords||patch
Assignee|b...@freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229074
--- Comment #1 from Eitan Adler ---
Hey, the patch doesn't apply. Can you resend?
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--
|--- file_not_specified_in_diff
|+++ file_not_specifie
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229074
Ali Abdallah changed:
What|Removed |Added
Attachment #194314|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229074
--- Comment #3 from Ali Abdallah ---
New patch uploaded, let me know if it is okay. It applies on my system.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229074
Eitan Adler changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229074
--- Comment #4 from commit-h...@freebsd.org ---
A commit references this bug:
Author: eadler
Date: Sun Jun 17 20:44:21 UTC 2018
New revision: 335304
URL: https://svnweb.freebsd.org/changeset/base/335304
Log:
acpi: Add support for Thinkpa
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229120
Mark Linimon changed:
What|Removed |Added
Keywords||patch
Assignee|b...@freeb
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228654
Kubilay Kocak changed:
What|Removed |Added
Summary|[12-CURRENT] ACPI suspend |ACPI suspend S3 with bounce
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229074
--- Comment #5 from Ali Abdallah ---
Created attachment 195237
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=195237&action=edit
Add documentation of dev.acpi_ibm.0.mic_led
I've added documentation of the dev.acpi_ibm.0.mic_led,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229074
Ali Abdallah changed:
What|Removed |Added
Attachment #195237|0 |1
is obsolete|
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207419
--- Comment #8 from Anthony Jenkins ---
I just assumed this was dropped for lack of interest. What are my next steps?
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230290
Mark Linimon changed:
What|Removed |Added
Keywords||patch
Assignee|b...@freeb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229120
Poul-Henning Kamp changed:
What|Removed |Added
CC||p...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230290
John Baldwin changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #9 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230290
--- Comment #10 from Johannes Lundberg ---
(In reply to John Baldwin from comment #9)
Well I wanted to inform linuxkpi and the graphic drivers what state we are
suspending to but I think it's safe to assume it's always S3 (for now).
powe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230290
--- Comment #11 from John Baldwin ---
Drivers get informed of suspend and resume via DEVICE_SUSPEND and DEVICE_RESUME
callbacks on the device_t. My understanding is that linuxkpi devices are still
a device_t so are still getting that callb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230290
--- Comment #12 from Johannes Lundberg ---
(In reply to John Baldwin from comment #11)
That is correct, they get that through the normal device suspend/resume but
linuxkpi needs to keep track of target state (S0 or S3 in this case) that is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230290
--- Comment #13 from John Baldwin ---
So my question is why does Linuxkpi care about the sleep state? Does it
actually have conditional logic that it is using? If it really needs it, then
what I think we should do is change DEVICE_SUSPEND
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230290
--- Comment #14 from Johannes Lundberg ---
(In reply to John Baldwin from comment #13)
> So my question is why does Linuxkpi care about the sleep state?
Because the driver asks linuxkpi what is the state we are suspending to.
> Does it
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229120
--- Comment #2 from Ali Abdallah ---
- Thinklight is reported by the firmware to be present, but turning it on does
nothing, probably is a reminiscence of old good Thinkpads! BTW, it behaves the
same under Linux.
- lcd_brightness is assumed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230290
--- Comment #15 from John Baldwin ---
I understand the cost of carrying diffs, but I've also been thinking about
power management of devices in FreeBSD and how it should work for native
drivers not just in suspend and resume for a long time
1 - 100 of 645 matches
Mail list logo