On 06.04.2017 22:25, Jiri Kosina wrote:
> On Thu, 6 Apr 2017, Rafael J. Wysocki wrote:
>
> Your swap partition may be located on an NVDIMM or be encrypted.
An NVDIMM should be considered the same as any other persistent storage.
It may be encrypted, but where's the key
On 06.04.2017 22:25, Jiri Kosina wrote:
> On Thu, 6 Apr 2017, Rafael J. Wysocki wrote:
>
> Your swap partition may be located on an NVDIMM or be encrypted.
An NVDIMM should be considered the same as any other persistent storage.
It may be encrypted, but where's the key
0.1.fc26.x86_64/updates/mii.ko
$ lsmod | grep mcs7830
mcs783016384 0
usbnet 45056 1 mcs7830
mii16384 2 usbnet,mcs7830
$ nmcli -f GENERAL.DRIVER,GENERAL.STATE device show enp0s4f1u4
GENERAL.DRIVER: MOSCHIP usb-ethernet driver
GENERAL.STATE: 100 (connected)
Tested-by: poma <p...@gmail.com>
rep mcs7830
mcs783016384 0
usbnet 45056 1 mcs7830
mii16384 2 usbnet,mcs7830
$ nmcli -f GENERAL.DRIVER,GENERAL.STATE device show enp0s4f1u4
GENERAL.DRIVER: MOSCHIP usb-ethernet driver
GENERAL.STATE: 100 (connected)
Tested-by: poma
On 14.03.2017 17:16, Tom Horsley wrote:
> And the consistent names change every single time some
> developer decides he just has to rewrite the algorithm
> to make it better, or systemd decides to engluph yet
> another component and not be backward compatible, or
> a kernel developer gets a new
On 14.03.2017 17:16, Tom Horsley wrote:
> And the consistent names change every single time some
> developer decides he just has to rewrite the algorithm
> to make it better, or systemd decides to engluph yet
> another component and not be backward compatible, or
> a kernel developer gets a new
On 21.11.2016 21:23, Wim Osterholt wrote:
> On Mon, Nov 21, 2016 at 04:58:25PM +0100, Wim Osterholt wrote:
>>
>> I didn't find traces of kernel-4.9-rc5 being ran on any of my laptops, so I
>> can't have seen a crash on rc5. It seems rc5 and rc6 is safe now.
>
> Neither 4.8.10, nor 4.8.9 show the
On 21.11.2016 21:23, Wim Osterholt wrote:
> On Mon, Nov 21, 2016 at 04:58:25PM +0100, Wim Osterholt wrote:
>>
>> I didn't find traces of kernel-4.9-rc5 being ran on any of my laptops, so I
>> can't have seen a crash on rc5. It seems rc5 and rc6 is safe now.
>
> Neither 4.8.10, nor 4.8.9 show the
On 15.11.2016 01:16, Wim Osterholt wrote:
> On Tue, Oct 18, 2016 at 02:18:43PM +0200, Oliver Neukum wrote:
>
>> It definitely does not crash and is probed and your .config is not
>> extremely unusual.
>
> Hmmm.
>
>> ... Something odd is going on.
>
> Whell, yes.
> The only thing that appears
On 15.11.2016 01:16, Wim Osterholt wrote:
> On Tue, Oct 18, 2016 at 02:18:43PM +0200, Oliver Neukum wrote:
>
>> It definitely does not crash and is probed and your .config is not
>> extremely unusual.
>
> Hmmm.
>
>> ... Something odd is going on.
>
> Whell, yes.
> The only thing that appears
On 23.08.2016 07:57, Daniel Vetter wrote:
> On Mon, Aug 22, 2016 at 11:17:34PM +0100, Jamie Lentin wrote:
>> Lift configuration command from udlfb. This appears to be essential for
>> at least a Rextron VCUD-60, without which no URB communication occurs.
>>
>> Signed-off-by: Jamie Lentin
On 23.08.2016 07:57, Daniel Vetter wrote:
> On Mon, Aug 22, 2016 at 11:17:34PM +0100, Jamie Lentin wrote:
>> Lift configuration command from udlfb. This appears to be essential for
>> at least a Rextron VCUD-60, without which no URB communication occurs.
>>
>> Signed-off-by: Jamie Lentin
>> ---
Hi Fi
please read comment
https://bugzilla.redhat.com/show_bug.cgi?id=1282706#c2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
Hi Fi
please read comment
https://bugzilla.redhat.com/show_bug.cgi?id=1282706#c2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
WARNING: CPU: 1 PID: 1 at arch/x86/mm/dump_pagetables.c:225
note_page+0x5e1/0x780()
WARNING: CPU: 0 PID: 18 at kernel/cgroup_pids.c:97
pids_cancel.constprop.5+0x31/0x40()
Ref.
https://bugzilla.redhat.com/show_bug.cgi?id=1282706
--
To unsubscribe from this list: send the line "unsubscribe
WARNING: CPU: 1 PID: 1 at arch/x86/mm/dump_pagetables.c:225
note_page+0x5e1/0x780()
WARNING: CPU: 0 PID: 18 at kernel/cgroup_pids.c:97
pids_cancel.constprop.5+0x31/0x40()
Ref.
https://bugzilla.redhat.com/show_bug.cgi?id=1282706
--
To unsubscribe from this list: send the line "unsubscribe
On Mon, Oct 12, 2015 at 7:59 AM, Dmitry Torokhov
wrote:
> Hi,
>
> On Mon, Oct 12, 2015 at 06:39:35AM +0200, poma wrote:
>> Hi Fi
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1269667
>>
>> Guys, can you help clarify, can this be a problem of the uinput a
On Mon, Oct 12, 2015 at 7:59 AM, Dmitry Torokhov
<dmitry.torok...@gmail.com> wrote:
> Hi,
>
> On Mon, Oct 12, 2015 at 06:39:35AM +0200, poma wrote:
>> Hi Fi
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1269667
>>
>> Guys, can you help clarify,
Hi Fi
https://bugzilla.redhat.com/show_bug.cgi?id=1269667
Guys, can you help clarify, can this be a problem of the uinput after all?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Hi Fi
https://bugzilla.redhat.com/show_bug.cgi?id=1269667
Guys, can you help clarify, can this be a problem of the uinput after all?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
BUG: unable to handle kernel NULL pointer dereference at 0024
BUG: sleeping function called from invalid context at include/linux/sched.h:2756
BUG: scheduling while atomic: spice-vdagentd/906/0x0002
BUG: spinlock lockup suspected on CPU#0, spice-vdagentd/906
BUG: unable to handle kernel NULL pointer dereference at 0024
BUG: sleeping function called from invalid context at include/linux/sched.h:2756
BUG: scheduling while atomic: spice-vdagentd/906/0x0002
BUG: spinlock lockup suspected on CPU#0, spice-vdagentd/906
On 10.08.2015 23:26, poma wrote:
>
> [ cut here ]
> WARNING: CPU: 1 PID: 813 at kernel/module.c:291
> module_assert_mutex_or_preempt+0x49/0x90()
> Modules linked in: mxl5007t af9013 ... dvb_usb_af9015(+) ... dvb_usb_v2
> dvb_core rc_core ...
>
On 10.08.2015 23:26, poma wrote:
[ cut here ]
WARNING: CPU: 1 PID: 813 at kernel/module.c:291
module_assert_mutex_or_preempt+0x49/0x90()
Modules linked in: mxl5007t af9013 ... dvb_usb_af9015(+) ... dvb_usb_v2
dvb_core rc_core ...
CPU: 1 PID: 813 Comm: systemd
On 14.08.2015 14:12, Peter Hurley wrote:
> On 08/14/2015 06:33 AM, poma wrote:
>>
>> This is broken almost 2 months.
>
> First reported 19 days ago with fix-it patch on same day.
>
>> Please push this to the stable 4.1.6 and mainline 4.2-rc7.
>
> This ha
On 14.08.2015 14:12, Peter Hurley wrote:
On 08/14/2015 06:33 AM, poma wrote:
This is broken almost 2 months.
First reported 19 days ago with fix-it patch on same day.
Please push this to the stable 4.1.6 and mainline 4.2-rc7.
This has already been answered.
Hey man, thanks
This is broken almost 2 months.
Please push this to the stable 4.1.6 and mainline 4.2-rc7.
Ref.
https://bugzilla.kernel.org/show_bug.cgi?id=101971
https://bugzilla.redhat.com/show_bug.cgi?id=1253566
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
This is broken almost 2 months.
Please push this to the stable 4.1.6 and mainline 4.2-rc7.
Ref.
https://bugzilla.kernel.org/show_bug.cgi?id=101971
https://bugzilla.redhat.com/show_bug.cgi?id=1253566
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
[ cut here ]
WARNING: CPU: 3 PID: 827 at lib/dma-debug.c:1169 check_for_stack+0x94/0xe0()
ehci-pci :00:02.1: DMA-API: device driver maps memory from stack
[addr=8800bc6dfa3c]
Modules linked in: ... mt7601u(+) mac80211 ... cfg80211 rfkill ...
CPU: 3 PID: 827 Comm:
[ cut here ]
WARNING: CPU: 3 PID: 827 at lib/dma-debug.c:1169 check_for_stack+0x94/0xe0()
ehci-pci :00:02.1: DMA-API: device driver maps memory from stack
[addr=8800bc6dfa3c]
Modules linked in: ... mt7601u(+) mac80211 ... cfg80211 rfkill ...
CPU: 3 PID: 827 Comm:
[ cut here ]
WARNING: CPU: 1 PID: 813 at kernel/module.c:291
module_assert_mutex_or_preempt+0x49/0x90()
Modules linked in: mxl5007t af9013 ... dvb_usb_af9015(+) ... dvb_usb_v2
dvb_core rc_core ...
CPU: 1 PID: 813 Comm: systemd-udevd Not tainted
[ cut here ]
WARNING: CPU: 1 PID: 813 at kernel/module.c:291
module_assert_mutex_or_preempt+0x49/0x90()
Modules linked in: mxl5007t af9013 ... dvb_usb_af9015(+) ... dvb_usb_v2
dvb_core rc_core ...
CPU: 1 PID: 813 Comm: systemd-udevd Not tainted
[ 19.381055] [ cut here ]
[ 19.381225] WARNING: CPU: 3 PID: 487 at kernel/sched/core.c:7291
__might_sleep+0x87/0x90()
[ 19.381373] do not call blocking ops when !TASK_RUNNING; state=2 set at
[] wait_for_completion_io+0xe5/0x140
...
[ 19.387265] Call Trace:
[
[ 19.381055] [ cut here ]
[ 19.381225] WARNING: CPU: 3 PID: 487 at kernel/sched/core.c:7291
__might_sleep+0x87/0x90()
[ 19.381373] do not call blocking ops when !TASK_RUNNING; state=2 set at
[81897a65] wait_for_completion_io+0xe5/0x140
...
[ 19.387265]
t;
Borislav, can you help explain the man why this is happening with his
Piledriver.
http://www.cpu-world.com/CPUs/Bulldozer/AMD-FX-Series%20FX-6300.html
poma
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
M
-world.com/CPUs/Bulldozer/AMD-FX-Series%20FX-6300.html
poma
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On 21.01.2015 15:24, Don Zickus wrote:
> On Wed, Jan 21, 2015 at 10:01:32AM +0100, poma wrote:
>> On 19.01.2015 14:49, Don Zickus wrote:
>>
>> Thank you, in the meantime, I've found what causes non-maskable interrupt,
>> [23]d on CPU 0, on resuming S4,
>> on A
On 19.01.2015 14:49, Don Zickus wrote:
> On Sun, Jan 18, 2015 at 11:50:38AM +0100, poma wrote:
>>
>> Salutem
>>
>> This happened only on thaw from S4 aka hibernate.
>> What should be "strange power saving mode" these messages relate!?
>>
>> [
On 19.01.2015 14:49, Don Zickus wrote:
On Sun, Jan 18, 2015 at 11:50:38AM +0100, poma wrote:
Salutem
This happened only on thaw from S4 aka hibernate.
What should be strange power saving mode these messages relate!?
[ 208.252986] Uhhuh. NMI received for unknown reason 3d on CPU 0
On 21.01.2015 15:24, Don Zickus wrote:
On Wed, Jan 21, 2015 at 10:01:32AM +0100, poma wrote:
On 19.01.2015 14:49, Don Zickus wrote:
Thank you, in the meantime, I've found what causes non-maskable interrupt,
[23]d on CPU 0, on resuming S4,
on AMD Phenom(tm) II X4 955 Processor.
/etc
d confused, but trying to continue
3.18.3-200.fc21.x86_64
poma
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
, but trying to continue
3.18.3-200.fc21.x86_64
poma
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
02:00.0 VGA compatible controller:
NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1)
Chipset: G98 (NV98)
Family : NV50
The same for all four kernel:
- 3.18.0-0.rc0.git8.1.fc22.x86_64
- 3.18.0-0.rc0.git9.1.fc22.x86_64
- 3.18.0-0.rc0.git9.3.fc22.x86_64
- 3.18.0-0.rc0.git9.4.fc22.x86_64
02:00.0 VGA compatible controller:
NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] (rev a1)
Chipset: G98 (NV98)
Family : NV50
The same for all four kernel:
- 3.18.0-0.rc0.git8.1.fc22.x86_64
- 3.18.0-0.rc0.git9.1.fc22.x86_64
- 3.18.0-0.rc0.git9.3.fc22.x86_64
- 3.18.0-0.rc0.git9.4.fc22.x86_64
at:
[] debug_dma_alloc_coherent+0x22/0x70
[] ohci_init+0x22c/0x450
[] ohci_setup+0x59/0x60
[] ohci_pci_reset+0x4f/0x60
[] usb_add_hcd+0x29a/0x8c0
$ lsusb -s 004:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
poma
--
To unsubscribe from this list: send the line "unsubscribe linux-k
$ lsusb -s 004:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
poma
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
On 13.09.2014 06:57, poma wrote:
>
> Actually I have nothing to show cause logs are all OK.
> Haha, it seems to me that the bugs become intelligent.
>
> 3.15.10-201.fc20.x86_64
> 3.16.2-200.fc20.x86_64
> 3.17.0-0.rc4.git3.2.fc22.1.x86_64
> nouveau [ DRM] suspendi
thaw BROKEN
ALL Kernels - vesa(fb)resume & thaw BROKEN.
Have a nice weekend folks.
poma
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majord
ALL Kernels - vesa(fb)resume thaw BROKEN.
Have a nice weekend folks.
poma
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
On 13.09.2014 06:57, poma wrote:
Actually I have nothing to show cause logs are all OK.
Haha, it seems to me that the bugs become intelligent.
3.15.10-201.fc20.x86_64
3.16.2-200.fc20.x86_64
3.17.0-0.rc4.git3.2.fc22.1.x86_64
nouveau [ DRM] suspending display...
nouveau [ DRM
On 11.05.2014 12:02, poma wrote:
>
> [ cut here ]
> WARNING: CPU: 2 PID: 628 at lib/dma-debug.c:593
> debug_dma_assert_idle+0x159/0x1d0()
> snd_hda_intel :00:07.0: DMA-API: cpu touching an active dma mapped
> cacheline [cln=0x03074000]
> CPU: 2 P
On 11.05.2014 12:02, poma wrote:
[ cut here ]
WARNING: CPU: 2 PID: 628 at lib/dma-debug.c:593
debug_dma_assert_idle+0x159/0x1d0()
snd_hda_intel :00:07.0: DMA-API: cpu touching an active dma mapped
cacheline [cln=0x03074000]
CPU: 2 PID: 628 Comm: lightdm
mailinglists, but I should acknowledge Parallels as
>> supporting the work I do.
>
> Thanks, I've update the author, added a Cc to ћtable and pushed it out to
> the core-for-3.17 branch.
>
Thanks guys!
Ref.
http://git.infradead.org/users/hch/scsi-queue.git/patch/884ffee?h
acknowledge Parallels as
supporting the work I do.
Thanks, I've update the author, added a Cc to ћtable and pushed it out to
the core-for-3.17 branch.
Thanks guys!
Ref.
http://git.infradead.org/users/hch/scsi-queue.git/patch/884ffee?hp=16acf5d
poma
--
To unsubscribe from this list: send
On 21.07.2014 16:58, Christoph Hellwig wrote:
On Mon, Jul 21, 2014 at 11:39:15AM +0200, poma wrote:
Thanks for the tip.
Is there a patch somewhere?
James sent the patch earlier and you replied to it.
Yea I could be more precise. :)
What I thought, is the patch pushed in some official repo
On 19.07.2014 18:44, Christoph Hellwig wrote:
On Fri, Jul 18, 2014 at 01:07:26PM -0700, James Bottomley wrote:
Is this what you thought?
No, he means this, if you want to try it.
Yes, that's what I mean.
Thanks for the tip.
Is there a patch somewhere?
poma
--
To unsubscribe from
On 19.07.2014 18:44, Christoph Hellwig wrote:
On Fri, Jul 18, 2014 at 01:07:26PM -0700, James Bottomley wrote:
Is this what you thought?
No, he means this, if you want to try it.
Yes, that's what I mean.
Thanks for the tip.
Is there a patch somewhere?
poma
--
To unsubscribe from
On 21.07.2014 16:58, Christoph Hellwig wrote:
On Mon, Jul 21, 2014 at 11:39:15AM +0200, poma wrote:
Thanks for the tip.
Is there a patch somewhere?
James sent the patch earlier and you replied to it.
Yea I could be more precise. :)
What I thought, is the patch pushed in some official repo
On 18.07.2014 22:03, poma wrote:
On 18.07.2014 16:20, Christoph Lameter wrote:
On Fri, 18 Jul 2014, poma wrote:
I guess someone working over the summertime. :)
Cache names should not contain blanks. I guess the
WARN_ON(strchr(name, ' ')); /* It confuses parsers */
was triggered
On 18.07.2014 22:16, poma wrote:
On 18.07.2014 22:07, James Bottomley wrote:
On Fri, 2014-07-18 at 22:01 +0200, poma wrote:
On 18.07.2014 16:17, Christoph Hellwig wrote:
On Fri, Jul 18, 2014 at 05:21:04PM +0400, Vladimir Davydov wrote:
Slab warns, because the name of the cache being created
On 18.07.2014 22:07, James Bottomley wrote:
On Fri, 2014-07-18 at 22:01 +0200, poma wrote:
On 18.07.2014 16:17, Christoph Hellwig wrote:
On Fri, Jul 18, 2014 at 05:21:04PM +0400, Vladimir Davydov wrote:
Slab warns, because the name of the cache being created contains spaces.
The "bad&q
On 18.07.2014 16:20, Christoph Lameter wrote:
On Fri, 18 Jul 2014, poma wrote:
I guess someone working over the summertime. :)
Cache names should not contain blanks. I guess the
WARN_ON(strchr(name, ' ')); /* It confuses parsers */
was triggered?
I can only guess also. ;)
poma
pool->cmd_slab = kmem_cache_create(pool->proc_name, cmd_size, 0,
pool->slab_flags, NULL);
if (!pool->cmd_slab)
goto out_free_pool;
however ain't workin.
poma
--
To unsubscribe from thi
]---
https://bugzilla.redhat.com/show_bug.cgi?id=1121092
poma
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://w
ain't workin.
poma
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On 18.07.2014 16:20, Christoph Lameter wrote:
On Fri, 18 Jul 2014, poma wrote:
I guess someone working over the summertime. :)
Cache names should not contain blanks. I guess the
WARN_ON(strchr(name, ' ')); /* It confuses parsers */
was triggered?
I can only guess also. ;)
poma
On 18.07.2014 22:07, James Bottomley wrote:
On Fri, 2014-07-18 at 22:01 +0200, poma wrote:
On 18.07.2014 16:17, Christoph Hellwig wrote:
On Fri, Jul 18, 2014 at 05:21:04PM +0400, Vladimir Davydov wrote:
Slab warns, because the name of the cache being created contains spaces.
The bad cache
On 18.07.2014 22:16, poma wrote:
On 18.07.2014 22:07, James Bottomley wrote:
On Fri, 2014-07-18 at 22:01 +0200, poma wrote:
On 18.07.2014 16:17, Christoph Hellwig wrote:
On Fri, Jul 18, 2014 at 05:21:04PM +0400, Vladimir Davydov wrote:
Slab warns, because the name of the cache being created
On 18.07.2014 22:03, poma wrote:
On 18.07.2014 16:20, Christoph Lameter wrote:
On Fri, 18 Jul 2014, poma wrote:
I guess someone working over the summertime. :)
Cache names should not contain blanks. I guess the
WARN_ON(strchr(name, ' ')); /* It confuses parsers */
was triggered
+0xcd/0x120
[817223a9] system_call_fastpath+0x16/0x1b
---[ end trace 64d7cf025fd3bf4a ]---
https://bugzilla.redhat.com/show_bug.cgi?id=1121092
poma
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More
On 25.06.2014 20:49, poma wrote:
On 25.06.2014 20:10, Felix Miata wrote:
On 2014-06-25 10:05 (GMT-0700) Adam Williamson composed:
So...these are three different machines?
3 out of 14 on which Rawhide is currently installed (test machines total 20+)
here, among which are represented various
On 25.06.2014 20:49, poma wrote:
On 25.06.2014 20:10, Felix Miata wrote:
On 2014-06-25 10:05 (GMT-0700) Adam Williamson composed:
So...these are three different machines?
3 out of 14 on which Rawhide is currently installed (test machines total 20+)
here, among which are represented various
On 06.05.2014 23:42, Matthew Garrett wrote:
Thanks, if there are no objections I'll apply that.
Matthew, any info for X75VBP?
poma
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo inf
On 06.05.2014 23:42, Matthew Garrett wrote:
Thanks, if there are no objections I'll apply that.
Matthew, any info for X75VBP?
poma
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
at:
[] debug_dma_alloc_coherent+0x22/0x70
[] snd_dma_alloc_pages+0x170/0x260 [snd_pcm]
[] snd_dma_alloc_pages_fallback+0x62/0x90 [snd_pcm]
[] snd_malloc_sgbuf_pages+0xf0/0x211 [snd_pcm]
[] snd_dma_alloc_pages+0x203/0x260 [snd_pcm]
poma
--
To unsubscribe from this list: send the line "unsubs
] snd_malloc_sgbuf_pages+0xf0/0x211 [snd_pcm]
[f80c3f23] snd_dma_alloc_pages+0x203/0x260 [snd_pcm]
poma
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
/bpf_dbg.c b/tools/net/bpf_dbg.c
http://pkgs.fedoraproject.org/repo/pkgs/kernel/patch-3.15-rc4-git1.xz/4b0ef9f7c4d9492c34d8263fa875c52f/patch-3.15-rc4-git1.xz
poma
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.
/bpf_dbg.c b/tools/net/bpf_dbg.c
http://pkgs.fedoraproject.org/repo/pkgs/kernel/patch-3.15-rc4-git1.xz/4b0ef9f7c4d9492c34d8263fa875c52f/patch-3.15-rc4-git1.xz
poma
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More
>From d39d3460f1ab36365a48b6815dd9a5d26613d3ec Mon Sep 17 00:00:00 2001
From: poma
Date: Tue, 6 May 2014 22:03:38 +0200
Subject: [PATCH] WAPF 4 for ASUSTeK COMPUTER INC. X75VBP WLAN ON.
The 'asus-nb-wmi' WAPF parameter must be set to 4, so the internal Wireless LAN device is operatio
>From d39d3460f1ab36365a48b6815dd9a5d26613d3ec Mon Sep 17 00:00:00 2001
From: poma
Date: Tue, 6 May 2014 22:03:38 +0200
Subject: [PATCH] WAPF 4 for ASUSTeK COMPUTER INC. X75VBP WLAN ON.
Signed-off-by: poma
---
drivers/platform/x86/asus-nb-wmi.c | 9 +
1 file changed, 9 inserti
> Corentin, care to pick up this one?
> https://bugzilla.redhat.com/attachment.cgi?id=892751
Matthew, who actually maintains the Asus Notebooks WMI Hotkey Driver i.e.
'asus-nb-wmi'?
poma
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
Corentin, care to pick up this one?
https://bugzilla.redhat.com/attachment.cgi?id=892751
Matthew, who actually maintains the Asus Notebooks WMI Hotkey Driver i.e.
'asus-nb-wmi'?
poma
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
From d39d3460f1ab36365a48b6815dd9a5d26613d3ec Mon Sep 17 00:00:00 2001
From: poma pomidorabelis...@gmail.com
Date: Tue, 6 May 2014 22:03:38 +0200
Subject: [PATCH] WAPF 4 for ASUSTeK COMPUTER INC. X75VBP WLAN ON.
Signed-off-by: poma pomidorabelis...@gmail.com
---
drivers/platform/x86/asus-nb
From d39d3460f1ab36365a48b6815dd9a5d26613d3ec Mon Sep 17 00:00:00 2001
From: poma pomidorabelis...@gmail.com
Date: Tue, 6 May 2014 22:03:38 +0200
Subject: [PATCH] WAPF 4 for ASUSTeK COMPUTER INC. X75VBP WLAN ON.
The 'asus-nb-wmi' WAPF parameter must be set to 4, so the internal Wireless LAN
On 27.04.2014 00:12, poma wrote:
> Need to set wapf to 4 for ASUSTeK COMPUTER INC. X75VBP & X550CA, so that the
> wireless network adapter is enabled.
>
> References:
> - asus-nb-wmi: set wapf=4 for ASUSTeK COMPUTER INC. X75VBP
> http://marc.info/?l=linux-kernel=13981991
]
[] snd_dma_alloc_pages+0x203/0x260 [snd_pcm]
...
However with the 'cachelines-revert.patch',
related to
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/lib/dma-debug.c?id=3b7a641,
after rebooting 12 times sequentially, everything is OK!
i.e.
kernel-3.15.0-0.rc4.git0.3.fc21.i686 PASSED
poma
sequentially, everything is OK!
i.e.
kernel-3.15.0-0.rc4.git0.3.fc21.i686 PASSED
poma
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
On 27.04.2014 00:12, poma wrote:
Need to set wapf to 4 for ASUSTeK COMPUTER INC. X75VBP X550CA, so that the
wireless network adapter is enabled.
References:
- asus-nb-wmi: set wapf=4 for ASUSTeK COMPUTER INC. X75VBP
http://marc.info/?l=linux-kernelm=139819918125110
- Ath9k WiFi now
e -r
3.15.0-0.rc3.git3.1.fc21.i686 PASSED
Referent commit
ALSA: hda - Suppress CORBRP clear on Nvidia controller chips
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/sound/pci/hda?id=6ba736d
Eye Of The Tiger, Takashi!
poma
--
To unsubscribe from this list: send the line
.git3.1.fc21.i686 PASSED
Referent commit
ALSA: hda - Suppress CORBRP clear on Nvidia controller chips
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/sound/pci/hda?id=6ba736d
Eye Of The Tiger, Takashi!
poma
--
To unsubscribe from this list: send the line unsubscribe
ttps://bugzilla.redhat.com/show_bug.cgi?id=1089731
Reported-by: poma
Reported-by: Andreas Utterberg
Tested-by: poma
Tested-by: Andreas Utterberg
Cc: Fedora kernel development
Cc: Andreas Utterberg
Cc: Josh Boyer
Cc: Stanislaw Gruszka
---
drivers/platform/x86/asus-nb-wmi.c | 18 ++
1
://bugzilla.redhat.com/show_bug.cgi?id=1089731
Reported-by: poma pomidorabelis...@gmail.com
Reported-by: Andreas Utterberg andreas.utterb...@thundera.se
Tested-by: poma pomidorabelis...@gmail.com
Tested-by: Andreas Utterberg andreas.utterb...@thundera.se
Cc: Fedora kernel development ker
On 23.04.2014 02:53, poma wrote:
>
> This one comes and goes...
>
> [ cut here ]
> WARNING: CPU: 2 PID: 521 at lib/dma-debug.c:593
> debug_dma_assert_idle+0x159/0x1d0()
> snd_hda_intel :00:07.0: DMA-API: cpu touching an active dma mapped
> c
/kernel/git/next/linux-next.git/commit/lib/dma-debug.c?id=3b7a6418c7494b8bf0bf0537ddee1dedbca10f51
Are these two in some relation?
poma
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo inf
: Bluetooth
Soft blocked: no
Hard blocked: no
Regardless of the values of the WAPF parameter,
key combination does not give any results,
i.e. does not toggles The Internal Wireless LAN ON or OFF.
Also the WLAN LED is always ON, no matter what.
poma
diff --git a/drivers/platform/x86
: Bluetooth
Soft blocked: no
Hard blocked: no
Regardless of the values of the WAPF parameter,
FnF2 key combination does not give any results,
i.e. does not toggles The Internal Wireless LAN ON or OFF.
Also the WLAN LED is always ON, no matter what.
poma
diff --git a/drivers/platform
for cachelines and read-only mappings in overlap tracking
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/lib/dma-debug.c?id=3b7a6418c7494b8bf0bf0537ddee1dedbca10f51
Are these two in some relation?
poma
--
To unsubscribe from this list: send the line unsubscribe linux-kernel
On 23.04.2014 02:53, poma wrote:
This one comes and goes...
[ cut here ]
WARNING: CPU: 2 PID: 521 at lib/dma-debug.c:593
debug_dma_assert_idle+0x159/0x1d0()
snd_hda_intel :00:07.0: DMA-API: cpu touching an active dma mapped
cacheline [cln=0x03019000
On 17.04.2014 09:40, Clemens Ladisch wrote:
> poma wrote:
>> Sound whispers,
>
> ???
>
>> WARNING: CPU: 3 PID: 900 at lib/dma-debug.c:593
>> debug_dma_assert_idle+0x159/0x1d0()
>> snd_hda_intel :00:07.0: DMA-API: cpu touching an active dma
On 17.04.2014 09:40, Clemens Ladisch wrote:
poma wrote:
Sound whispers,
???
WARNING: CPU: 3 PID: 900 at lib/dma-debug.c:593
debug_dma_assert_idle+0x159/0x1d0()
snd_hda_intel :00:07.0: DMA-API: cpu touching an active dma mapped
cacheline [cln=0x03014000]
...
Mapped
1 - 100 of 160 matches
Mail list logo
