At boot-up with newer kernels (at least v3.6.x, v3.7-rc) I always see
following on the bootup-display:
3.7-rcx: [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting
for forcewake old ack to clear.
3.6.x:[drm:__gen6_gt_force_wake_mt_get] *ERROR* Force wake wait timed out
It's an Ivy Bri
2013/1/6 Jörg Otte :
> 2013/1/5 Francois Romieu :
>> Can you check if things improve with v3.8-rc2 after removing :
>>
>> 1. 9ecb9aabaf634677c77af467f4e3028b09d7bcda
>>r8169: workaround for missing extended GigaMAC registers
>> 2. d64ec841517a25f6d468bde9f67
2013/2/3 Jörg Otte :
> 2013/1/6 Jörg Otte :
>> 2013/1/5 Francois Romieu :
>>> Can you check if things improve with v3.8-rc2 after removing :
>>>
>>> 2. d64ec841517a25f6d468bde9f67e5b4cffdc67c7
>>>r8169: enable internal ASPM and clock request se
2013/2/8 Francois Romieu :
> Linus Torvalds :
> [...]
>> However, there's still the r8169 regressions (see the emails with the
>> subject "regression: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0
>> timed out"). It's bisected, and a revert is reported to fix things.
>> It's not in this pull req
2013/9/25 Jani Nikula :
> On Wed, 25 Sep 2013, Jörg Otte wrote:
>> 2013/9/25 Jani Nikula :
>>> On Wed, 25 Sep 2013, Aaron Lu wrote:
>>>> On Wed, Sep 25, 2013 at 10:29:37AM +0200, Jörg Otte wrote:
>>>>> Backlight can't be modified with this pat
2013/9/27 Rafael J. Wysocki :
> On Thursday, September 26, 2013 09:49:03 AM Jörg Otte wrote:
>> 2013/9/25 Jani Nikula :
>> > On Wed, 25 Sep 2013, Jörg Otte wrote:
>> >> 2013/9/25 Jani Nikula :
>> >>> On Wed, 25 Sep 2013, Aaron Lu wrote:
>> >&
2013/9/25 Jani Nikula :
> On Wed, 25 Sep 2013, Aaron Lu wrote:
>> On Wed, Sep 25, 2013 at 10:29:37AM +0200, Jörg Otte wrote:
>>> Backlight can't be modified with this patch set - neither with
>>> function keys nor with the gui. It is a step backward to v3.11-rc1
Thanks, the path works.
Jörg
2012/11/27 Chris Wilson :
> On Tue, 27 Nov 2012 17:29:36 +0100, Jörg Otte wrote:
>> At boot-up with newer kernels (at least v3.6.x, v3.7-rc) I always see
>> following on the bootup-display:
>>
>> 3.7-rcx: [drm:__gen6_gt_force_wake_mt_get
I frequently see the following in the syslog:
[ 184.552914] [ cut here ]
[ 184.552927] WARNING: at
/data/kernel/linux/net/sched/sch_generic.c:254
dev_watchdog+0xf2/0x151()
[ 184.552929] Hardware name: LIFEBOOK AH532
[ 184.552932] NETDEV WATCHDOG: eth0 (r8169): transmit
2013/1/5 Francois Romieu :
> Jörg Otte :
> [...]
>> It's a regression, it never happend before 3.8-rc.
>
> Please check that 'dmesg | grep XID' exhibits a 8168evl.
jojo@ahorn:~$ dmesg | grep XID
[1.808847] r8169 :02:00.0 eth0: RTL8168evl/8111evl at
0xff
With kernel v3.8 all multimedia programs under KDE4 don't work (Kubuntu 12.04).
They alltogether ( at least Dragonplayer (Mediaplayer), Knotify4
(system-sound),
System-Settings-Multimedia,..) are looping forever producing 100% CPU-usage
and must be killed.
With kernel 3.7 there are no problems.
I
gt; just reverts the insane error code, and fixed something very similar
> for him.
>
> (I just pushed out, so it might take a few minutes to mirror out to
> the public sites).
>
> Linus
>
> On Sun, Dec 23, 2012 at 8:46 AM, Jörg Otte wrote:
>> With kernel
2012/12/23 Mauro Carvalho Chehab :
> Hi Jörg,
>
> Em Sun, 23 Dec 2012 17:46:07 +0100
> Jörg Otte escreveu:
>
>> With kernel v3.8 all multimedia programs under KDE4 don't work (Kubuntu
>> 12.04).
>> They alltogether ( at least Dragonplayer (Mediaplayer),
2013/5/25 Jörg Otte :
> If iwlwifi/iwldvm are built into the kernel (no loadable modules)
> following error is written to console and syslog since v3.10-rc:
>
> iwlwifi :08:00.0: failed to load module iwldvm (error -38), is
> dynamic loading enabled?
>
&g
2013/6/27 Sedat Dilek :
> On Wed, Jun 26, 2013 at 6:37 PM, Sedat Dilek wrote:
>> On Wed, Jun 26, 2013 at 6:16 PM, Jörg Otte wrote:
>>> 2013/5/25 Jörg Otte :
>>>> If iwlwifi/iwldvm are built into the kernel (no loadable modules)
>>>> following error is wr
The brightness of my laptop is always on maximum and can't be scaled
down.
Brightness control via function keys was always working on this
laptop, so this is a regression in v3.11-rc2.
It is a FUJITSU LIFEBOOK AH532/FJNBB1C, BIOS Version 1.09 05/22/2012
Video driver is i915.
Please Cc me in answe
2013/7/24 Aaron Lu :
> On 07/23/2013 03:52 PM, Jörg Otte wrote:
>> The brightness of my laptop is always on maximum and can't be scaled
>> down.
>> Brightness control via function keys was always working on this
>> laptop, so this is a regression in v3.11-rc2.
>
2013/7/24 Rafael J. Wysocki :
> On Tuesday, July 23, 2013 09:52:15 AM Jörg Otte wrote:
>> The brightness of my laptop is always on maximum and can't be scaled
>> down.
>> Brightness control via function keys was always working on this
>> laptop, so this is a regre
2013/7/24 Rafael J. Wysocki :
> On Tuesday, July 23, 2013 11:46:29 AM Kamal Mostafa wrote:
>> On Mon, 2013-07-22 at 21:54 +0200, Rafael J. Wysocki wrote:
>> > On Monday, July 22, 2013 11:11:54 AM Linus Torvalds wrote:
>> > > On Mon, Jul 22, 2013 at 6:02 AM, Rafael J. Wysocki wrote:
>> > > >
>> > >
2013/7/25 Rafael J. Wysocki :
> On Monday, July 22, 2013 09:54:21 PM Rafael J. Wysocki wrote:
>> On Monday, July 22, 2013 11:11:54 AM Linus Torvalds wrote:
>> > On Mon, Jul 22, 2013 at 6:02 AM, Rafael J. Wysocki wrote:
>> > >
>> > > Linus, do you want me to send a pull request reverting 8c5bd7a an
2013/7/25 Jörg Otte :
> 2013/7/25 Rafael J. Wysocki :
>> On Monday, July 22, 2013 09:54:21 PM Rafael J. Wysocki wrote:
>>> On Monday, July 22, 2013 11:11:54 AM Linus Torvalds wrote:
>>> > On Mon, Jul 22, 2013 at 6:02 AM, Rafael J. Wysocki wrote:
>>> >
If iwlwifi/iwldvm are built into the kernel (no loadable modules)
following error is written to console and syslog since v3.10-rc:
iwlwifi :08:00.0: failed to load module iwldvm (error -38), is
dynamic loading enabled?
reverting
commit 1618b2b02a3a0ee7a6863fed4b0d22e697e7e97c
Author: Johannes
Hi,
the sysfs-interface of intel_pstate is different to that of the acpi driver:
- intel_pstate shows current cpu-frequency in "cpuinfo_cur_freq" whereas
the acpi counterpart uses "scaling_cur_freq".
- moreover cpuinfo_cur_freq is readable by root only, whereas
scaling_cur_freq is world readab
2013/5/28 Johannes Berg :
> On Sat, 2013-05-25 at 11:09 +0200, Jörg Otte wrote:
>> If iwlwifi/iwldvm are built into the kernel (no loadable modules)
>> following error is written to console and syslog since v3.10-rc:
>>
>> iwlwifi :08:00.0: failed to load mo
2013/5/28 Dirk Brandewie :
> Hi Jörg,
>
>
> On 05/28/2013 08:02 AM, Jörg Otte wrote:
>>
>> Hi,
>>
>> the sysfs-interface of intel_pstate is different to that of the acpi
>> driver:
>> - intel_pstate shows current cpu-frequency in "cpui
2013/1/5 Francois Romieu :
> Can you check if things improve with v3.8-rc2 after removing :
>
> 1. 9ecb9aabaf634677c77af467f4e3028b09d7bcda
>r8169: workaround for missing extended GigaMAC registers
> 2. d64ec841517a25f6d468bde9f67e5b4cffdc67c7
>r8169: enable internal ASPM and clock request
In 4.14.0-rc7-9-g287683d cpufreq directory under
/sys/devices/system/cpu/cpufreq
is empty. Also link /sys/devices/system/cpu/cpu0/cpufreq is missing.
Is this change intentional?
Jörg
2017-11-01 21:24 GMT+01:00 Rafael J. Wysocki :
> On Wed, Nov 1, 2017 at 6:06 PM, Jörg Otte wrote:
>> In 4.14.0-rc7-9-g287683d cpufreq directory under
>> /sys/devices/system/cpu/cpufreq
>> is empty. Also link /sys/devices/system/cpu/cpu0/cpufreq is missing.
>>
&g
2017-11-02 9:37 GMT+01:00 Jörg Otte :
> 2017-11-01 21:24 GMT+01:00 Rafael J. Wysocki :
>> On Wed, Nov 1, 2017 at 6:06 PM, Jörg Otte wrote:
>>> In 4.14.0-rc7-9-g287683d cpufreq directory under
>>> /sys/devices/system/cpu/cpufreq
>>> is empty. Also link /sy
The display remains dark in V4.0-rc5 except of a small white line
at the top of the screen so I can't see anything. RC4 was good.
The latest good kernel that I know of is at least
4.0.0-rc4-00199-gb314aca.
Thanks, Jörg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
The BT mouse is "death" in v4.1.
The BT mouse has been working in 4.0 and previous kernels, so this
is a regression.
BT adapter is an intel 8087:07da. The mouse is an MS Notebook Mouse 500.
It just doesn't work without any errors displayed in dmesg.
Thanks, Jörg
--
To unsubscribe from this list:
2015-04-17 15:44 GMT+02:00 Linus Torvalds :
> On Fri, Apr 17, 2015 at 5:36 AM, Jörg Otte wrote:
>> The BT mouse is "death" in v4.1.
>> The BT mouse has been working in 4.0 and previous kernels, so this
>> is a regression.
>
> Any chance of bisecting it?
&g
2015-04-17 16:51 GMT+02:00 Jörg Otte :
> 2015-04-17 15:44 GMT+02:00 Linus Torvalds :
>> On Fri, Apr 17, 2015 at 5:36 AM, Jörg Otte wrote:
>>> The BT mouse is "death" in v4.1.
>>> The BT mouse has been working in 4.0 and previous kernels, so this
>>>
2015-04-17 18:51 GMT+02:00 Marcel Holtmann :
> Hi Joerg,
>
>>>> On Fri, Apr 17, 2015 at 5:36 AM, Jörg Otte wrote:
>>>>> The BT mouse is "death" in v4.1.
>>>>> The BT mouse has been working in 4.0 and previous kernels, so this
&
2015-04-17 18:55 GMT+02:00 Jörg Otte :
> 2015-04-17 18:51 GMT+02:00 Marcel Holtmann :
>> Hi Joerg,
>>
>>>>> On Fri, Apr 17, 2015 at 5:36 AM, Jörg Otte wrote:
>>>>>> The BT mouse is "death" in v4.1.
>>>>>> The BT mouse
What this patch tried to do is to limit it to what userspace is
currently actually using. My mistake was to look only at BlueZ 5.x
userspace and not at BlueZ 4.x userspace. The fix to not break
existing userspace is essentially this:
>
> diff --git a/net/bluetooth/hidp/core.c b/net/bluetooth/hidp/c
Hi,
In v4.16 I already had support for BPB, IBRS_FW for spectre_v2 mitigation.
But this went away in v17-rcx.
With 4.16 I have:
jojo@fichte:~$ cd /sys/devices/system/cpu/vulnerabilities; grep ".*" *
meltdown:Mitigation: PTI
spectre_v1:Mitigation: __user pointer sanitization
spectre_v2:Mitigation:
2018-04-30 21:53 GMT+02:00 Thomas Gleixner :
> Jörg,
>
> On Mon, 30 Apr 2018, Jörg Otte wrote:
>
>> In v4.16 I already had support for BPB, IBRS_FW for spectre_v2 mitigation.
>> But this went away in v17-rcx.
>>
>> With 4.16 I have:
>> jojo@fichte:~$
2018-05-01 22:14 GMT+02:00 Linus Torvalds :
> On Tue, May 1, 2018 at 5:59 AM Thomas Gleixner wrote:
>
>> Then I really have no idea how reverting the patch you pointed out would
>> fix it.
>
> So I do think that the original patch is buggy.
>
> What I think *may* be going on is:
>
> - first we d
2018-05-02 11:02 GMT+02:00 Thomas Gleixner :
> On Wed, 2 May 2018, Jörg Otte wrote:
>> With revert:
>>
>> jojo@fichte:~$ dmesg | grep -i -e spec -e micro -e "Linux version"
>>
>> [0.00] microcode: microcode updated early to revision 0x24,
&
Kernel 3.13.0-06058-g2d08cd0 displays following errors on the console:
ACPI: \_PR_.CPU4: failed to get CPU APIC ID.
ACPI: \_PR_.CPU5: failed to get CPU APIC ID.
ACPI: \_PR_.CPU6: failed to get CPU APIC ID.
ACPI: \_PR_.CPU7: failed to get CPU APIC ID.
I don't have CPUs 4..7! Error messages regardi
2014-01-25 Rafael J. Wysocki :
> On Saturday, January 25, 2014 11:03:09 AM Jörg Otte wrote:
>> Kernel 3.13.0-06058-g2d08cd0 displays following errors on the console:
>>
>> ACPI: \_PR_.CPU4: failed to get CPU APIC ID.
>> ACPI: \_PR_.CPU5: failed to get CPU APIC ID.
>
2014-01-27 Jiang Liu :
> Commit b981513f806d (ACPI / scan: bail out early if failed to parse
> APIC ID for CPU) emits an error message if ACPI processor driver fails
> to query APIC ID for the CPU.
>
> Originally it's designed to catch BIOS bugs for CPU hot-addition. But
> it accidently reveals ano
On shutdown power is not switched off. The harddisk is already down.
Reboot is working.
Last known good kernel is: 3.14.0-rc5-00265-gb01d4e6
First known bad kernel is: 3.14.0-rc5-00287-gca62eec
FUJITSU LIFEBOOK AH532/FJNBB1C, BIOS Version 1.09 05/22/2012
Jörg
--
To unsubscribe from this list: se
2014-03-09 18:15 GMT+01:00 Rafael J. Wysocki :
> On Sunday, March 09, 2014 05:58:59 PM Rafael J. Wysocki wrote:
>> On Sunday, March 09, 2014 05:55:28 PM Rafael J. Wysocki wrote:
>> > On Sunday, March 09, 2014 05:12:56 PM Jörg Otte wrote:
>> > > On shutdown power is
2014-05-16 13:53 GMT+02:00 Ville Syrjälä :
> On Tue, May 13, 2014 at 06:38:32PM +0200, Daniel Vetter wrote:
>> On Tue, May 13, 2014 at 05:21:49PM +0200, Jörg Otte wrote:
>> > 2014-05-13 15:22 GMT+02:00 Daniel Vetter :
>> > > On Tue, May 13, 2014 at 12:38:41PM +0200, D
2014-05-12 21:03 GMT+02:00 Daniel Vetter :
> On Mon, May 12, 2014 at 01:25:24PM +0200, Jörg Otte wrote:
>> 2014-05-11 18:49 GMT+02:00 Daniel Vetter :
>> > On Sat, May 10, 2014 at 10:52 AM, Jörg Otte wrote:
>> >>> On Fri, May 09, 2014 at 05:14:38PM +0100, Damien L
2014-05-13 15:22 GMT+02:00 Daniel Vetter :
> On Tue, May 13, 2014 at 12:38:41PM +0200, Daniel Vetter wrote:
>> On Tue, May 13, 2014 at 12:29 PM, Jörg Otte wrote:
>> >>> Branch drm-intel-nightly as of
>> >>> ed60c27 drm-intel-nightly: 2014y-05m-09d-21h-51
2014-05-09 19:03 GMT+02:00 Ville Syrjälä :
> On Fri, May 09, 2014 at 05:14:38PM +0100, Damien Lespiau wrote:
>> On Fri, May 09, 2014 at 06:11:37PM +0200, Jörg Otte wrote:
>> > > Jörg, can you please boot with drm.debug=0xe, reproduce the issue and
>> > > then attac
2014-05-11 18:49 GMT+02:00 Daniel Vetter :
> On Sat, May 10, 2014 at 10:52 AM, Jörg Otte wrote:
>>> On Fri, May 09, 2014 at 05:14:38PM +0100, Damien Lespiau wrote:
>>>> On Fri, May 09, 2014 at 06:11:37PM +0200, Jörg Otte wrote:
>>>> > > Jörg, can you ple
Kernel 3.14.0-12041-g75ff24f from 9.4.2014 introduces the following
on the console (driver is i915):
[drm:ivb_err_int_handler] *ERROR* Pipe B FIFO underrun
[drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun
[drm:cpt_serr_int_handler] *ERROR* PCH transcoder B FIFO underrun
In syslog
2014-04-09 12:08 GMT+02:00 Jörg Otte :
> Kernel 3.14.0-12041-g75ff24f from 9.4.2014 introduces the following
> on the console (driver is i915):
>
> [drm:ivb_err_int_handler] *ERROR* Pipe B FIFO underrun
> [drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun
> [drm:cp
I don't know how to do this.
Thanks, Jörg
2014-06-19 17:02 GMT+02:00 Alan Stern :
> On Thu, 19 Jun 2014, Jörg Otte wrote:
>
>> on resume with 3.16-rc1 I get the following error messages in dmesg
>> which are alltogether not present in 3.15:
>>
>&
2014-06-20 16:57 GMT+02:00 Alan Stern :
> On Fri, 20 Jun 2014, Jörg Otte wrote:
>
>> 2014-06-19 19:35 GMT+02:00 Alan Stern :
>> > On Thu, 19 Jun 2014, Jörg Otte wrote:
>> >
>> >> I don't know how to do this.
>> >
>> > To enable d
I still have FIFO underruns in drm:
[drm:ivb_err_int_handler] *ERROR* Pipe B FIFO underrun
[drm:cpt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun
[drm:cpt_serr_int_handler] *ERROR* PCH transcoder B FIFO underrun
which I already reported here:
https://lkml.org/lkml/2014/4/9/127
and whic
On startup I get the following error display on the console:
"*ERROR* Timed out waiting for forcewake old ack to clear"
I already reported this error a year ago at the time of v3.7
( see https://lkml.org/lkml/2012/11/27/355)
which was fixed later on.
Now this error is back again. Kernel 3.12.0-0
My network interface eth0 doesn't come up in 3.16.0-10436-g9138475
I am seeing following "security problem" in dmesg:
audit: type=1400 audit(1407684227.003:28): apparmor="DENIED"
operation="open" profile="/sbin/dhclient"
name="/proc/1540/task/1540/net/dev" pid=1540 comm="dhclient"
requested_
2014-08-11 6:30 GMT+02:00 Linus Torvalds :
> On Sun, Aug 10, 2014 at 1:05 PM, Eric W. Biederman
> wrote:
>>
>> Linus would you like me to send pull request with those two changes reverted?
>
> I just did them (delayed it a bit in the hope to get confirmation, but
> it looks very straightforward, s
2015-02-24 0:24 GMT+01:00 Rafael J. Wysocki :
> On Sunday, February 22, 2015 01:33:09 PM Jörg Otte wrote:
>> Starting with kernel 3.19.0-05184-g18320f2, I often find my notebook
>> running with 'powersave' policy even if it is on AC.
>>
>> It turned out that
2015-02-24 0:18 GMT+01:00 Rafael J. Wysocki :
> On Sunday, February 22, 2015 05:53:11 PM Jörg Otte wrote:
>> When I press backlight keys then normally OSD is shown and
>> backlight follows immediately the keystrokes step by step.
>
> That's how it works in 3.19, right?
2015-02-24 12:03 GMT+01:00 Jörg Otte :
> 2015-02-24 0:24 GMT+01:00 Rafael J. Wysocki :
>> On Sunday, February 22, 2015 01:33:09 PM Jörg Otte wrote:
>>> Starting with kernel 3.19.0-05184-g18320f2, I often find my notebook
>>> running with 'powersave' policy e
If I plug in my USB DVB-T stick I get the following in dmesg:
dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (TerraTec/qanu USB2.0 Highspeed DVB-T Receiver)
2015-03-10 14:06 GMT+01:00 Mathias Nyman :
> On 10.03.2015 11:40, Jörg Otte wrote:
>> If I plug in my USB DVB-T stick I get the following in dmesg:
>>
>> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm
>> state.
>> dvb-usb: will
2015-03-10 15:03 GMT+01:00 Jörg Otte :
> 2015-03-10 14:06 GMT+01:00 Mathias Nyman :
>> On 10.03.2015 11:40, Jörg Otte wrote:
>>> If I plug in my USB DVB-T stick I get the following in dmesg:
>>>
>>> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T
2015-03-10 18:04 GMT+01:00 Mathias Nyman :
> On 10.03.2015 17:36, Jörg Otte wrote:
>
>>>> Any chance you could take a log with xhci debugging enabled before
>>>> attaching the DVB-T
>>>> stick?
>>>>
>>>> echo -n 'module xhci_h
2015-03-11 12:01 GMT+01:00 Jörg Otte :
> 2015-03-10 18:04 GMT+01:00 Mathias Nyman :
>> On 10.03.2015 17:36, Jörg Otte wrote:
>>
>>>>> Any chance you could take a log with xhci debugging enabled before
>>>>> attaching the DVB-T
>>>>> s
2015-03-27 8:03 GMT+01:00 Kalle Valo :
> Linus Torvalds writes:
>
>> can you verify/confirm that current git works for you? And if not,
>> maybe bisect exactly where it happened?
>
> I had a similar problem as Jörg on my Lenovo x230, display black on -rc5
> except some small colored line on the t
In suspend state the power-led remains on (should be blinking).
So may be the kernel does not reach suspend state correctly.
Once suspended, pressing the suspend key to wake up does not have
any visible effect.
There is nothing special in the logs.
I tried to bisect, but I ran into an unbootable
2015-02-13 15:40 GMT+01:00 Rafael J. Wysocki :
> On Friday, February 13, 2015 09:49:20 AM Jörg Otte wrote:
>> In suspend state the power-led remains on (should be blinking).
>> So may be the kernel does not reach suspend state correctly.
>> Once suspended, pressing the suspen
Starting with kernel 3.19.0-05184-g18320f2, I often find my notebook
running with 'powersave' policy even if it is on AC.
It turned out that /sys/class/ACAD directory is missing and in the
logs I see:
ACPI Error: Cannot release Mutex [MUT0], not acquired (20150204/exmutex-376)
ACPI Error: Method
When I press backlight keys then normally OSD is shown and
backlight follows immediately the keystrokes step by step.
Now in v3.20 it behaves different:
When I press backlight keys at first nothing happens. If I watch a
video it is being stopped.
After some seconds OSD is shown, backlight changes
Bluetooth has ever been working on my Notebook. I successfully
use Bluetooth mouse and Obex file transfer for years. And with
Kernel V4.00 the Adapter is no longer recognized.
It is an Intel 8087:07da.
The first bad commit is:
commit d0ac9eb72b6dceae318c15ee82ef2aaee233666d
Author: Marcel Holtman
2016-03-29 23:34 GMT+02:00 Rafael J. Wysocki :
> On Tuesday, March 29, 2016 07:32:27 PM Jörg Otte wrote:
>> 2016-03-29 19:24 GMT+02:00 Jörg Otte :
>> > in v4.5 and earlier intel-pstate downscaled idle processors (load
>> > 0.1-0.2%) to minumum frequency, in my case 80
2016-03-30 13:05 GMT+02:00 Rafael J. Wysocki :
> On Wed, Mar 30, 2016 at 12:17 PM, Jörg Otte wrote:
>> 2016-03-29 23:34 GMT+02:00 Rafael J. Wysocki :
>>> On Tuesday, March 29, 2016 07:32:27 PM Jörg Otte wrote:
>>>> 2016-03-29 19:24 GMT+02:00 Jörg Otte :
>>&
2016-03-30 17:33 GMT+02:00 Pandruvada, Srinivas :
> On Wed, 2016-03-30 at 13:05 +0200, Rafael J. Wysocki wrote:
>> On Wed, Mar 30, 2016 at 12:17 PM, Jörg Otte
>> wrote:
>> >
>> > 2016-03-29 23:34 GMT+02:00 Rafael J. Wysocki :
>> > >
>> > &g
2016-03-30 20:39 GMT+02:00 Rafael J. Wysocki :
> On Wednesday, March 30, 2016 05:29:18 PM Jörg Otte wrote:
>> 2016-03-30 13:05 GMT+02:00 Rafael J. Wysocki :
>> > On Wed, Mar 30, 2016 at 12:17 PM, Jörg Otte wrote:
>> >> 2016-03-29 23:34 GMT+02:00 Rafael J. Wysocki
2016-03-30 22:26 GMT+02:00 Srinivas Pandruvada
:
> On Wed, 2016-03-30 at 22:12 +0200, Rafael J. Wysocki wrote:
>> On Wed, Mar 30, 2016 at 8:58 PM, Srinivas Pandruvada
>> wrote:
>> >
>> > On Wed, 2016-03-30 at 11:50 -0700, Doug Smythies wrote:
>> > &g
2016-03-31 13:42 GMT+02:00 Rafael J. Wysocki :
> On Thursday, March 31, 2016 11:05:56 AM Jörg Otte wrote:
>
> [cut]
>
>> >
>>
>> Yes, works for me.
>>
>> CPUID(7): No-SGX
>> CPU Avg_MHz Busy% Bzy_MHz TSC_MHz
>>- 1
2016-03-31 17:06 GMT+02:00 Srinivas Pandruvada
:
> On Thu, 2016-03-31 at 07:39 -0700, Doug Smythies wrote:
>> On 2016.03.31 02:24 Jörg Otte wrote:
>
> Hi Jörg,
>
> Can you send me your kernel config file?
>
> Thanks,
> Srinivas
>>
>> > jojo@fichte
2016-03-31 17:43 GMT+02:00 Rafael J. Wysocki :
> On Thursday, March 31, 2016 05:25:18 PM Jörg Otte wrote:
>> 2016-03-31 13:42 GMT+02:00 Rafael J. Wysocki :
>> > On Thursday, March 31, 2016 11:05:56 AM Jörg Otte wrote:
>> >
>> > [cut]
>> >
>> >
2016-03-31 17:43 GMT+02:00 Rafael J. Wysocki :
> On Thursday, March 31, 2016 05:25:18 PM Jörg Otte wrote:
>> 2016-03-31 13:42 GMT+02:00 Rafael J. Wysocki :
>> > On Thursday, March 31, 2016 11:05:56 AM Jörg Otte wrote:
>> >
>> > [cut]
>> >
>> >
2016-03-31 19:55 GMT+02:00 Srinivas Pandruvada
:
> On Thu, 2016-03-31 at 19:27 +0200, Jörg Otte wrote:
>> 2016-03-31 17:43 GMT+02:00 Rafael J. Wysocki :
>> > On Thursday, March 31, 2016 05:25:18 PM Jörg Otte wrote:
>> > > 2016-03-31 13:42 GMT+02:00 Rafael J. Wysocki
2016-04-01 14:40 GMT+02:00 Rafael J. Wysocki :
> On Friday, April 01, 2016 11:20:42 AM Jörg Otte wrote:
>> 2016-03-31 17:43 GMT+02:00 Rafael J. Wysocki :
>> > On Thursday, March 31, 2016 05:25:18 PM Jörg Otte wrote:
>> >> 2016-03-31 13:42 GMT+02:00 Rafael J. Wysocki :
2016-04-01 17:20 GMT+02:00 Doug Smythies :
> On 2016.04.01 05:40 Rafael J. Wysocki wrote:
>> On Friday, April 01, 2016 11:20:42 AM Jörg Otte wrote:
>>> 2016-03-31 17:43 GMT+02:00 Rafael J. Wysocki :
>>>> On Thursday, March 31, 2016 05:25:18 PM Jörg Otte wrote:
&g
2016-04-01 18:46 GMT+02:00 Jörg Otte :
> 2016-04-01 17:20 GMT+02:00 Doug Smythies :
>> On 2016.04.01 05:40 Rafael J. Wysocki wrote:
>>> On Friday, April 01, 2016 11:20:42 AM Jörg Otte wrote:
>>>> 2016-03-31 17:43 GMT+02:00 Rafael J. Wysocki :
>>>>> On T
2016-04-02 17:28 GMT+02:00 Srinivas Pandruvada
:
>
> On Sat, 2016-04-02 at 08:30 +0200, Sedat Dilek wrote:
>> > I am trying CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y from
>> > linux-pm.git#linux-next out of curiosity...
>> >
>> > $ ./scripts/diffconfig /boot/config-$(uname -r) .config
>> > CPU_FREQ_DEFAU
2015-06-29 23:13 GMT+02:00 Tedd Ho-Jeong An :
> Hi Jorg
>
> On Mon, 29 Jun 2015 16:37:32 +0200
> Jörg Otte wrote:
>
>> 2015-06-29 12:30 GMT+02:00 Alexey Dobriyan :
>> > On Mon, Jun 29, 2015 at 12:00 PM, Jörg Otte wrote:
>> >> 2015-06-28 18:09 GMT+02:
With kernels vmlinuz-4.3.0-rc2-00228-gd4a748a and earlier it is no
problem for me to stream HD-videos (700-800 Kbyte/s) from YouTube.
With the same video material and kernels
vmlinuz-4.3.0-rc2-00438-gd8cc397 and later I only reach 70-80 KByte/s.
That's a one-tenth than before.
The merges between
Am Do., 6. Juni 2019 um 08:18 Uhr schrieb Marcel Holtmann :
>
> Hi Joerg,
>
> > In 5.2.0-rcx I see a new error message on startup probably after
> > loading the Bluetooth firmware:
> > [1.609460] Bluetooth: hci0: unexpected event for opcode 0xfc2f
> >
> >> dmesg | grep Bluetooth
> > [0.1309
Am Do., 6. Juni 2019 um 13:20 Uhr schrieb Marcel Holtmann :
>
> Hi Joerg,
>
> >>> In 5.2.0-rcx I see a new error message on startup probably after
> >>> loading the Bluetooth firmware:
> >>> [1.609460] Bluetooth: hci0: unexpected event for opcode 0xfc2f
> >>>
> dmesg | grep Bluetooth
> >>>
2018-05-04 18:18 GMT+02:00 Borislav Petkov :
> On Wed, May 02, 2018 at 02:20:52PM +0200, Thomas Gleixner wrote:
>> Thanks for confirming. Still need to find a way which is less fragile, but
>> that's probably too much of churn for rc4
>>
>> At least I know exactly what's happening, so I can wri
Hi,
my notebook doesn't boot with 4.17.0-rc1. Booting stops right after
displaying "loading initial ramdisk..". No further displays.
Also nothing is wriiten to the logs.
First known bad kernel is: 4.16.0-12564-g6b0a02e
Last known good kernel is: 4.16.0-12548-g71b8ebb
Maybe the problem came in wit
2018-04-17 10:14 GMT+02:00 Borislav Petkov :
> On Tue, Apr 17, 2018 at 10:00:25AM +0200, Jörg Otte wrote:
>> Maybe the problem came in with:
>> 6b0a02e: "Merge branch 'x86-pti-for-linus' of
>> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip"
&g
2018-04-17 16:27 GMT+02:00 Borislav Petkov :
> On Tue, Apr 17, 2018 at 04:16:34PM +0200, Jörg Otte wrote:
>> Current Linus master tree (4.17.0-rc1-00021-ga27fc14) does'nt fix it.
>
> Then pls continue bisecting. Unless someone has a better idea...
&
2016-11-08 21:22 GMT+01:00 Mauro Carvalho Chehab :
> Em Tue, 8 Nov 2016 10:42:03 -0800
> Linus Torvalds escreveu:
>
>> On Sun, Nov 6, 2016 at 7:40 AM, Jörg Otte wrote:
>> > Since v4.9-rc4 I get following crash in dvb-usb-cinergyT2 module.
>>
>> Looks lik
2016-10-05 20:55 GMT+02:00 Mauro Carvalho Chehab :
> Hi Johannes,
>
> Em Wed, 5 Oct 2016 20:29:45 +0200
> Johannes Stezenbach escreveu:
>
>> On Wed, Oct 05, 2016 at 06:04:50AM -0300, Mauro Carvalho Chehab wrote:
>> > static int cinergyt2_frontend_attach(struct dvb_usb_adapter *adap)
>> > {
>> >
2016-10-06 20:29 GMT+02:00 Mauro Carvalho Chehab :
> Em Thu, 6 Oct 2016 10:27:56 -0700
> Andy Lutomirski escreveu:
>
>> On Wed, Oct 5, 2016 at 11:58 AM, Mauro Carvalho Chehab
>> wrote:
>> > Sorry, forgot to C/C people that are at the "Re: Problem with VMAP_STACK=y"
>> > thread.
>> >
>> > Forwarde
2016-11-10 9:40 GMT+01:00 Mauro Carvalho Chehab :
> Em Wed, 9 Nov 2016 11:07:35 -0800
> Linus Torvalds escreveu:
>
>> On Wed, Nov 9, 2016 at 3:09 AM, Jörg Otte wrote:
>> >
>> > Tried patch with no success. Again a NULL ptr dereferece.
>>
>> That pat
2016-11-11 14:55 GMT+01:00 Mauro Carvalho Chehab :
> Em Thu, 10 Nov 2016 12:15:39 +0100
> Jörg Otte escreveu:
>
>> 2016-11-10 9:40 GMT+01:00 Mauro Carvalho Chehab :
>> > Em Wed, 9 Nov 2016 11:07:35 -0800
>> > Linus Torvalds escreveu:
>> >
>> >
if I connect Logitech usb audio speaker (idVendor=1130, idProduct=1620) I get
a kernel panic - fatal exception in interrupt.
There is nothing written into the logs so this
is a hand written excerpt from screen:
call trace:
? snd_complete_urb
? __usb_hcd_giveback_urb
? xhci_giveback_urb_in_irq.is
1 - 100 of 127 matches
Mail list logo
