Re: [PATCH 11/24] uswsusp: Disable when the kernel is locked down

2017-04-07 Thread poma
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 stor

Re: [PATCH 06/11] net: usb: mcs7830: use new api ethtool_{get|set}_link_ksettings

2017-03-21 Thread poma
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

Re: [...] "How does the new naming scheme look like, precisely?"

2017-03-15 Thread 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 mot

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-21 Thread poma
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 b

Re: crash by cdc_acm driver in kernels 4.8-rc1/5

2016-11-15 Thread poma
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 yo

Re: [PATCH v2] drm/udl: Ensure channel is selected before using the device.

2016-11-07 Thread poma
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 >> --- >>

Re: Kernel panic - not syncing: Fatal exception in interrupt - mainline: 4.4-rc1

2015-11-19 Thread poma
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 a

Kernel panic - not syncing: Fatal exception in interrupt - mainline: 4.4-rc1

2015-11-17 Thread poma
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 linux-

Re: mouse event for unknown monitor - uinput?

2015-10-12 Thread poma
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

mouse event for unknown monitor - uinput?

2015-10-11 Thread poma
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 http://vge

BUG: quattro stagioni

2015-09-15 Thread poma
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 https://bugzilla.kerne

Re: WARNING: CPU: 1 PID: 813 at kernel/module.c:291 module_assert_mutex_or_preempt+0x49/0x90()

2015-08-21 Thread poma
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 ... >

Re: apropos Regression with 'x86/cacheinfo: Move cacheinfo sysfs code to generic infrastructure' on AMD i686

2015-08-16 Thread poma
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

apropos Regression with 'x86/cacheinfo: Move cacheinfo sysfs code to generic infrastructure' on AMD i686

2015-08-14 Thread poma
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 mess

WARNING: CPU: 3 PID: 827 at lib/dma-debug.c:1169 check_for_stack+0x94/0xe0()

2015-08-11 Thread poma
[ 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: s

WARNING: CPU: 1 PID: 813 at kernel/module.c:291 module_assert_mutex_or_preempt+0x49/0x90()

2015-08-10 Thread poma
[ 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 4.2.0-0.rc6.git0.1.fc24.x8

do not call blocking ops when !TASK_RUNNING

2015-05-08 Thread poma
[ 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.

Re: How to increase maximum user cpu usage allowed on a multi core system?

2015-03-17 Thread poma
> Can anyone help? > 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 ma

Re: Uhhuh - Dazed and confused, but trying to continue :)

2015-01-21 Thread poma
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, >>

Re: Uhhuh - Dazed and confused, but trying to continue :)

2015-01-21 Thread poma
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!? >> >> [

Uhhuh - Dazed and confused, but trying to continue :)

2015-01-18 Thread poma
fused, 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/

INFO: task echo:622 blocked for more than 120 seconds. - 3.18.0-0.rc0.git

2014-10-19 Thread poma
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 afte

Re: debug_dma_assert_idle - ohci - cpu touching an active dma mapped cacheline

2014-09-17 Thread poma
: [] 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-kernel&qu

Re: VGA resume & thaw (wake up from S3 & S4) broken - kernel exclusively

2014-09-12 Thread poma
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

VGA resume & thaw (wake up from S3 & S4) broken - kernel exclusively

2014-09-12 Thread poma
amp; 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/m

Re: debug_dma_assert_idle - ahci - cpu touching an active dma mapped cacheline

2014-08-29 Thread poma
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

Re: WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache_create+0x1a9/0x330()

2014-07-29 Thread poma
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?

Re: WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache_create+0x1a9/0x330()

2014-07-21 Thread poma
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

Re: WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache_create+0x1a9/0x330()

2014-07-21 Thread poma
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

Re: WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache_create+0x1a9/0x330()

2014-07-18 Thread poma
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

Re: WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache_create+0x1a9/0x330()

2014-07-18 Thread poma
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

Re: WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache_create+0x1a9/0x330()

2014-07-18 Thread 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&q

Re: WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache_create+0x1a9/0x330()

2014-07-18 Thread poma
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.

Re: WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache_create+0x1a9/0x330()

2014-07-18 Thread poma
0, + 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 unsub

WARNING: CPU: 1 PID: 495 at mm/slab_common.c:69 kmem_cache_create+0x1a9/0x330()

2014-07-18 Thread poma
]--- 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

console font

2014-06-30 Thread poma
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

Re: [PATCH] asus-nb-wmi: set wapf=4 for ASUSTeK COMPUTER INC. X75VBP & X550CA

2014-06-10 Thread poma
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 majordom

Re: debug_dma_assert_idle - snd_hda_intel - cpu touching an active dma mapped cacheline

2014-05-11 Thread poma
: [] 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

Re: debug_dma_assert_idle - snd_hda_intel - cpu touching an active dma mapped cacheline

2014-05-07 Thread poma
/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.

Re: [PATCH] asus-nb-wmi: set wapf=4 for ASUSTeK COMPUTER INC. X75VBP & X550CA

2014-05-06 Thread poma
>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 i

Re: [PATCH] asus-nb-wmi: set wapf=4 for ASUSTeK COMPUTER INC. X75VBP & X550CA

2014-05-06 Thread poma
>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

Re: [PATCH] asus-nb-wmi: set wapf=4 for ASUSTeK COMPUTER INC. X75VBP & X550CA

2014-05-06 Thread poma
> 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" i

Re: [PATCH] asus-nb-wmi: set wapf=4 for ASUSTeK COMPUTER INC. X75VBP & X550CA

2014-05-05 Thread poma
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&m=1398

Re: debug_dma_assert_idle - snd_hda_intel - cpu touching an active dma mapped cacheline

2014-05-05 Thread poma
] [] 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 PAS

Re: debug_dma_assert_idle - snd_hda_intel - cpu touching an active dma mapped cacheline

2014-04-30 Thread poma
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

[PATCH] asus-nb-wmi: set wapf=4 for ASUSTeK COMPUTER INC. X75VBP & X550CA

2014-04-26 Thread poma
ch https://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 +

Re: debug_dma_assert_idle - snd_hda_intel - cpu touching an active dma mapped cacheline

2014-04-22 Thread poma
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

Re: debug_dma_assert_idle - snd_hda_intel - cpu touching an active dma mapped cacheline

2014-04-22 Thread poma
/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

asus-nb-wmi: set wapf=4 for ASUSTeK COMPUTER INC. X75VBP

2014-04-22 Thread poma
: 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

Re: debug_dma_assert_idle - snd_hda_intel - cpu touching an active dma mapped cacheline

2014-04-17 Thread poma
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

debug_dma_assert_idle - snd_hda_intel - cpu touching an active dma mapped cacheline

2014-04-16 Thread poma
] [] snd_malloc_sgbuf_pages+0xf0/0x211 [snd_pcm] [] snd_dma_alloc_pages+0x203/0x260 [snd_pcm] https://bugzilla.redhat.com/show_bug.cgi?id=1087565 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

Re: WARNING ... drivers/gpu/drm/ttm/ttm_bo_vm.c...

2014-04-10 Thread poma
On 08.04.2014 03:29, poma wrote: > ... > Command line: initrd=initrd.img > inst.stage2=hd:LABEL=Fedora\x20rawhide\x20x86_64 xdriver=modesetting > BOOT_IMAGE=vmlinuz > Kernel command line: initrd=initrd.img > inst.stage2=hd:LABEL=Fedora\x20rawhide\x20x86_64 xdriver=modese

WARNING ... drivers/gpu/drm/ttm/ttm_bo_vm.c...

2014-04-07 Thread poma
=1085145 https://bugzilla.redhat.com/attachment.cgi?id=883813 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 FA

[ INFO: possible circular locking dependency detected ]

2014-03-15 Thread poma
https://bugzilla.redhat.com/attachment.cgi?id=874823 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 FA

Re: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280()

2014-03-08 Thread poma
d=872299 https://bugzilla.redhat.com/attachment.cgi?id=872299&action=diff 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/

Re: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280()

2014-03-07 Thread poma
On 07.03.2014 17:30, poma wrote: > On 07.03.2014 00:32, poma wrote: >> ... >> After a few dozen tests with the vanilla commits, and with the same >> amount of rawhide kernels ... >> https://bugzilla.redhat.com/attachment.cgi?id=871694 >> >> Dan, Fran

Re: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280()

2014-03-07 Thread poma
On 07.03.2014 00:32, poma wrote: > ... > After a few dozen tests with the vanilla commits, and with the same > amount of rawhide kernels ... > https://bugzilla.redhat.com/attachment.cgi?id=871694 > > Dan, Francois you are both welcome with comments! > Thanks. Thomas U2. :)

Re: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280()

2014-03-06 Thread poma
... After a few dozen tests with the vanilla commits, and with the same amount of rawhide kernels ... https://bugzilla.redhat.com/attachment.cgi?id=871694 Dan, Francois you are both welcome with comments! Thanks. poma -- To unsubscribe from this list: send the line "unsubscribe linux-kerne

Re: BUG: unable to handle kernel paging request at 0000000100000003 - Oops: 0000 [#1] SMP

2014-03-03 Thread poma
On 21.02.2014 16:48, Jan Kara wrote: > On Fri 21-02-14 14:08:03, Richard Weinberger wrote: >> On Fri, Feb 21, 2014 at 12:40 PM, poma wrote: >>> >>> Affected kernels - 3.14.0-0.rc3*: >>> >>> - 3.14.0-0.rc3.git0.1 >>> http://koji.fedoraprojec

BUG: unable to handle kernel paging request at 0000000100000003 - Oops: 0000 [#1] SMP

2014-02-21 Thread poma
://koji.fedoraproject.org/koji/buildinfo?buildID=499636 Memtest86+ 4.20 - OK http://goo.gl/1nm1nV RHBZ https://bugzilla.redhat.com/show_bug.cgi?id=1067919 messages-Oops-es-3.14.0-0.rc3 https://bugzilla.redhat.com/attachment.cgi?id=865926 poma -- To unsubscribe from this list: send the line "unsubs

Re: [dma-debug.c - DMA-API] exceeded overlapping ... & sym53c8xx ... tries to free DMA ...

2014-02-18 Thread poma
On 18.02.2014 20:36, Dan Williams wrote: > On Mon, Feb 17, 2014 at 6:40 AM, poma wrote: >> On 14.02.2014 19:20, poma wrote: >>> On 14.02.2014 10:16, Stanislaw Gruszka wrote: >>>> On Fri, Feb 14, 2014 at 09:52:37AM +0100, poma wrote: >>>>> >>&

Re: WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280()

2014-02-18 Thread poma
On 18.02.2014 11:15, poma wrote: > > Ahoy! > > Debugging S3 aka suspend produces 'WARNINGS': > > Steps to Reproduce: > # echo core > /sys/power/pm_test > # cat /sys/power/pm_test > none [core] processors platform devices freezer > # echo mem > /sys

WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0x276/0x280()

2014-02-18 Thread poma
m_test-platform.diff https://bugzilla.redhat.com/attachment.cgi?id=864439 RHBZ 1010764: "[abrt] NETDEV WATCHDOG: em1 (e1000e): transmit queue 0 timed out" https://bugzilla.redhat.com/show_bug.cgi?id=1010764 Tested with Rawhide 'kernel-debug-3.14.0-0.rc3.git0.1.fc21.x86_64' http://koji.fedora

Re: [dma-debug.c - DMA-API] exceeded overlapping … & sym53c8xx … tries to free DMA …

2014-02-17 Thread poma
On 14.02.2014 19:20, poma wrote: > On 14.02.2014 10:16, Stanislaw Gruszka wrote: >> On Fri, Feb 14, 2014 at 09:52:37AM +0100, poma wrote: >>> >>> Ahoy! >>> >>> Perhaps this is already solved, but I made ​​the effort to test & record >>

Re: [dma-debug.c - DMA-API] exceeded overlapping … & sym53c8xx … tries to free DMA …

2014-02-14 Thread poma
On 14.02.2014 10:16, Stanislaw Gruszka wrote: > On Fri, Feb 14, 2014 at 09:52:37AM +0100, poma wrote: >> >> Ahoy! >> >> Perhaps this is already solved, but I made ​​the effort to test & record >> all of this, therefore here you are. :) >> >> ht

[dma-debug.c - DMA-API] exceeded overlapping … & sym53c8xx … tries to free DMA …

2014-02-14 Thread poma
337 Fragment count: 20 Press [Esc] to abort check. Checking: 100.0% The media check is complete, the result is: PASS. It is OK to use this media. sha256sum: 2b6aac6e9b55c5f49f251340a4c28e091998f9fe3a6bdba7542f0f9b2d69ba8c boot.iso poma -- To unsubscribe from this list: send the line "unsubscribe linux-kernel&q

Re: WARNING: CPU: 2 PID: 4415 at lib/idr.c:527 idr_remove.part.6+0x243/0x250()

2014-02-12 Thread poma
On 12.02.2014 09:35, Tejun Heo wrote: > On Wed, Feb 12, 2014 at 09:33:23AM +0100, poma wrote: >> >> Ahoy! >> >> My trace is the last one, therefore per LIFO I am sending this report to >> you. >> >> [ cut here ] &

WARNING: CPU: 2 PID: 4415 at lib/idr.c:527 idr_remove.part.6+0x243/0x250()

2014-02-12 Thread poma
/show_bug.cgi?id=1045755 Thanks. 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/

Re: WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:668 tick_broadcast_oneshot_control+0x17d/0x190()

2014-02-11 Thread poma
On 11.02.2014 15:25, Thomas Gleixner wrote: > On Mon, 10 Feb 2014, Thomas Gleixner wrote: >> On Mon, 10 Feb 2014, poma wrote: >> >>> [ 83.558551] [] amd_e400_idle+0x87/0x130 >> >> So this seems to happen only on AMD machines which use that e400 idle >>

Re: WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:668 tick_broadcast_oneshot_control+0x17d/0x190()

2014-02-10 Thread poma
On 10.02.2014 11:06, Thomas Gleixner wrote: > On Mon, 10 Feb 2014, poma wrote: > >> [ 83.558551] [] amd_e400_idle+0x87/0x130 > > So this seems to happen only on AMD machines which use that e400 idle > mode. I have no idea at the moment whats wrong there. I'll find o

Re: WARNING: CPU: 0 PID: 2243 at mm/slub.c:1007 deactivate_slab+0x4e0/0x590()

2014-02-10 Thread poma
On 10.02.2014 11:14, David Rientjes wrote: > On Mon, 10 Feb 2014, poma wrote: > >> [ 83.530421] WARNING: CPU: 0 PID: 2243 at mm/slub.c:1007 >> deactivate_slab+0x4e0/0x590() > > Yeah, you'll need the patch from the http://marc.info/?t=13914579132 > threa

WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:668 tick_broadcast_oneshot_control+0x17d/0x190()

2014-02-09 Thread poma
mane.org/gmane.linux.kernel/1529924 http://thread.gmane.org/gmane.linux.power-management.general/37437 poma At 600km above planet Earth the temperature fluctuates between +125 and -100 degrees Celsius There is nothing to carry sound No air pressure No oxygen Life in space is impossible LINU

WARNING: CPU: 0 PID: 2243 at mm/slub.c:1007 deactivate_slab+0x4e0/0x590()

2014-02-09 Thread poma
7] smpboot: CPU 2 is now offline [ 83.537960] kvm: disabling virtualization on CPU3 [ 83.538003] smpboot: CPU 3 is now offline [ 83.538181] [ cut here ] https://bugzilla.redhat.com/attachment.cgi?id=861203 https://bugzilla.redhat.com/show_bug.cgi?id=1063096 p

Re: [Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector 0x400

2014-01-21 Thread poma
On 15.01.2014 16:34, Robert Richter wrote: > On 10.01.14 04:21:11, poma wrote: >> >> Robert, is there a patch for this case? >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152484/comments/12 > > I just sent a patch to lkml that fixes this: > > https://

[Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector 0x400

2014-01-09 Thread poma
S3 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/

Re: WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:667

2014-01-09 Thread poma
wpath_null+0x1a/0x20 [] tick_broadcast_oneshot_control+0x17d/0x190 [] clockevents_notify+0x178/0x1a0 [] amd_e400_idle+0x7b/0x100 [] arch_cpu_idle+0x26/0x30 [] cpu_startup_entry+0xc5/0x290 [] start_secondary+0x22b/0x2e0 ---[ end trace a6717546b328eaba ]--- poma -- To unsubscribe from this li

WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:667

2013-08-21 Thread poma
e restored successfully. PM: Basic memory bitmaps freed 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/

[BUG] [skge] WARNING: at lib/dma-debug.c:937

2013-07-23 Thread poma
+0x91/0x140 [] skge_xmit_frame+0x180/0x5d0 [skge] [] dev_hard_start_xmit+0x301/0x6d0 [] sch_direct_xmit+0xee/0x290 [] dev_queue_xmit+0x27b/0x990 … poma -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More

[Re:] 3.11-rc2: WARNING: at kernel/time/tick-broadcast.c:667

2013-07-22 Thread poma
://kojipkgs.fedoraproject.org//packages/kernel/3.11.0/0.rc2.git0.1.fc20/data/logs/x86_64/build.log 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 P

3.10.2: WARNING: at kernel/time/tick-broadcast.c:585

2013-07-22 Thread poma
on CPU3 CPU3 is up ACPI: Waking up from system sleep state S3 … With an additional four patches[1] WARNING persists. CONF. http://kojipkgs.fedoraproject.org//packages/kernel/3.10.2/301.fc19/data/logs/x86_64/build.log poma [1] https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log