From: Neil Armstrong
Date: Wed, 20 Apr 2016 10:56:45 +0200
> When the DaVinci emac driver is removed and re-probed, the actual
> pdev->dev.platform_data is populated with an unwanted valid pointer saved by
> the previous davinci_emac_of_get_pdata() call, causing a kernel crash wh
it's blocking on?
Yes, I have sysrq. Blocked state (w):
##
[ *** ] (2 of 4) A start job is running for…v-ttySAC2.device (1min / 1min 30s)
*** break sent ***
[*** ] (2 of 4) A start job is running for…v-ttySAC2.device (1min / 1min
30s)[ 110.962917] sysrq: SysRq : Show Blocke
it's blocking on?
Yes, I have sysrq. Blocked state (w):
##
[ *** ] (2 of 4) A start job is running for…v-ttySAC2.device (1min / 1min 30s)
*** break sent ***
[*** ] (2 of 4) A start job is running for…v-ttySAC2.device (1min / 1min
30s)[ 110.962917] sysrq: SysRq : Show Blocke
Hello.
What kind of problem is this:
1.) the one that should be fixed, but also can be ignored or
2.) the one that have to be fixed and ignorance is a bad idea?
WARNING: vmlinux - Section mismatch: reference to .init.data:boot_params
from .text between '_text' (at offset 0xc0100029
to address section mismatches
with that config option. I suppose that they will be in the
next -mm release (?), so this needs to be retested with
those patches applied.
WARNING: vmlinux - Section mismatch: reference to .init.data:boot_params
from .text between '_text' (at offset 0xc0100029
hid_generic snd_usb_audio snd_usbmidi_lib snd_hwdep mct_u232
snd_rawmidi snd_seq_device snd_pcm snd_page_alloc usbhid usbserial
snd_timer snd hid soundcore mv_cesa cryptodev(O) ipv6 autofs4
[ 54.231214] [c000d020] (unwind_backtrace+0x0/0xe0) from
[c03fd1d0] (__schedule_bug+0x48/0x60)
[ 54.240171
Hello.
What kind of problem is this:
1.) the one that should be fixed, but also can be ignored or
2.) the one that have to be fixed and ignorance is a bad idea?
WARNING: vmlinux - Section mismatch: reference to .init.data:boot_params
from .text between '_text' (at offset 0xc0100029
ome patches posted to address section mismatches
with that config option. I suppose that they will be in the
next -mm release (?), so this needs to be retested with
those patches applied.
> WARNING: vmlinux - Section mismatch: reference to .init.data:boot_params
> from .text between '_tex
hid_generic snd_usb_audio snd_usbmidi_lib snd_hwdep mct_u232
snd_rawmidi snd_seq_device snd_pcm snd_page_alloc usbhid usbserial
snd_timer snd hid soundcore mv_cesa cryptodev(O) ipv6 autofs4
[ 54.231214] [] (unwind_backtrace+0x0/0xe0) from
[] (__schedule_bug+0x48/0x60)
[ 54.240171
nd_timer snd hid soundcore mv_cesa cryptodev(O) ipv6 autofs4
> [ 54.231214] [] (unwind_backtrace+0x0/0xe0) from
> [] (__schedule_bug+0x48/0x60)
> [ 54.240171] [] (__schedule_bug+0x48/0x60) from
> [] (__schedule+0x4c/0x4bc)
> [ 54.248773] [] (__schedule+0x4c/0x4bc) from []
>
gument]
clang-12: warning: argument unused during compilation: '-mno-branch-likely'
[-Wunused-command-line-argument]
In file included from kernel/bounds.c:14:
In file included from include/linux/spinlock_types.h:18:
In file included from include/linux/lockdep.h:44:
In file included from i
gument]
clang-12: warning: argument unused during compilation: '-mno-branch-likely'
[-Wunused-command-line-argument]
In file included from kernel/bounds.c:14:
In file included from include/linux/spinlock_types.h:18:
In file included from include/linux/lockdep.h:44:
In file included from i
gument]
clang-11: warning: argument unused during compilation: '-mno-branch-likely'
[-Wunused-command-line-argument]
In file included from kernel/bounds.c:14:
In file included from include/linux/spinlock_types.h:18:
In file included from include/linux/lockdep.h:44:
In file included from i
-uninline-skb_put-fix.patch
In file included from include/linux/if_ether.h:111,
from include/linux/netdevice.h:29,
from include/net/sock.h:48,
from kernel/audit.c:54:
include/linux/skbuff.h: In function 'skb_put':
include/linux/skbuff.h:885: warning
than 120 seconds.
echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message.
iozoneD c021685c 0 227222
[c02164c0] (schedule+0x0/0x41c) from [c0216314] (__down+0xa4/0xfc)
[c0216270] (__down+0x0/0xfc) from [c021620c] (__down_failed+0xc/0x20)
r8:c3815c70 r7: r6
On Thu, 2005-02-17 at 10:27 -0500, Fao, Sean wrote:
Where are those nonsense (base64) messages from [EMAIL PROTECTED] coming
from after I post?
Looks like a new spammer tactic. They have progressed from spoofing
emails from real LKML posters to sending spam replies to actual threads.
Lee
] stack backtrace:
[5.725528] [c0013c78] (unwind_backtrace+0x0/0xf0) from [c0426f94]
(rpc_wait_bit_killable+0x94/0xb4)
[5.735184] [c0426f94] (rpc_wait_bit_killable+0x94/0xb4) from [c044684c]
(__wait_on_bit+0x74/0xb8)
[5.744645] [c044684c] (__wait_on_bit+0x74/0xb8) from [c04468f4
Why has the link to version 3.5 been removed from kernel.org and also from
lkml.org? When I browse there I see that mainline is 3.6-rc1 and stable is
3.4.7 which is different from the last time. Is version 3.5 no longer
considered stable?
--
To unsubscribe from this list: send the line
It is derived from original LZO 2.02 code found at:
http://www.oberhumer.com/opensource/lzo/download/
The code has also been reformatted to match general kernel style.
--
Bill Davidsen [EMAIL PROTECTED]
We have more to fear from the bungling of the incompetent than from
the machinations
at
/home/linus/linux-stericsson/kernel/irq/irqdomain.c:676
irq_domain_xlate_twocell+0x40/0x48()
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted
3.15.0-07915-gf6d059821ce9-dirty #46
[c0014660] (unwind_backtrace)
from [c0011424] (show_stack+0x10/0x14)
[c0011424] (show_stack)
from
On Thu, 2005-02-17 at 10:27 -0500, Fao, Sean wrote:
> Where are those nonsense (base64) messages from [EMAIL PROTECTED] coming
> from after I post?
>
Looks like a new spammer tactic. They have progressed from spoofing
emails from real LKML posters to sending spam replies to actua
op net-uninline-skb_put-fix.patch
In file included from include/linux/if_ether.h:111,
from include/linux/netdevice.h:29,
from include/net/sock.h:48,
from kernel/audit.c:54:
include/linux/skbuff.h: In function 'skb_put':
include/linux/skbuff.h:885: w
It is derived from original LZO 2.02 code found at:
http://www.oberhumer.com/opensource/lzo/download/
The code has also been reformatted to match general kernel style.
--
Bill Davidsen <[EMAIL PROTECTED]>
"We have more to fear from the bungling of the incompetent than from
the m
at
/home/linus/linux-stericsson/kernel/irq/irqdomain.c:676
irq_domain_xlate_twocell+0x40/0x48()
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted
3.15.0-07915-gf6d059821ce9-dirty #46
[] (unwind_backtrace)
from [] (show_stack+0x10/0x14)
[] (show_stack)
from [] (dump_stack+0x9c/0xd4
From: Will Deacon
Rewritting from commit f71c2ffcb20d upstream. On LTS 4.9, there has no
raw_copy_from/to_user, neither __copy_user_flushcache, and it isn't good
idead to pick up them. The following is origin commit log, that's also
applicable for the new patch.
Like we've done for get_user
From: Will Deacon
Rewritting from commit f71c2ffcb20d upstream. On LTS 4.9, there has no
raw_copy_from/to_user, neither __copy_user_flushcache, and it isn't good
idead to pick up them. The following is origin commit log, that's also
applicable for the new patch.
Like we've done for get_user
};
> };
>
> debug_phy: ethernet-phy@1 {
> compatible = "marvell";
> reg = <1>;
> device_type = "ethernet-phy";
> label = "debug-phy";
> };
Hi Michael
This is pretty unreadable with all the white space removed. Please
On Mon, Jan 04, 2021 at 09:27:01AM +0100, Geert Uytterhoeven wrote:
> On Mon, Jan 4, 2021 at 6:12 AM Stephen Rothwell wrote:
> > After merging the staging tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> > In file included fr
Hi all,
After merging the staging tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/printk.h:6,
from include/linux/kernel.h:16,
from drivers/staging/board/kzm9d.c:4:
drivers/staging/board/kzm9d.c:28:17
Hi Dmitry,
On 23/11/2020 00:27, Dmitry Osipenko wrote:
> Add EMC OPP DVFS tables and update board device-trees by removing
> unsupported OPPs.
>
> Signed-off-by: Dmitry Osipenko
This change is generating the following warning on Tegra20 Ventana
and prevents the EMC
On Sat, Aug 22, 2020 at 02:36:37AM +0200, Thomas Gleixner wrote:
> From: Thomas Gleixner
>
> followed by an empty new line before the actual changelog text
> starts. That way the attribution of the patch when applying it will be
> correct.
The way he sent it attribution will b
ask iozone:227 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
iozoneD c021685c 0 227 222
[] (schedule+0x0/0x41c) from [] (__down+0xa4/0xfc)
[] (__down+0x0/0xfc) from [] (__down_failed+0xc/0x20)
r8:c3815c70 r7:
Why has the link to version 3.5 been removed from kernel.org and also from
lkml.org? When I browse there I see that mainline is 3.6-rc1 and stable is
3.4.7 which is different from the last time. Is version 3.5 no longer
considered stable?
--
To unsubscribe from this list: send the line
On Wed, Feb 24, 2021 at 11:52:38AM +0100, Pascal Roeleven wrote:
> On request I'm resending the last two patches from the Topwise A721 tablet
> series from a year ago as they weren't picked up. The other patches are
> already merged, so I didn't resend them.
>
> Changes from v4:
&g
On Tue, Jul 28, 2015 at 04:19:36PM +0530, Jignesh R Patel wrote:
From: Jignesh R Patel jigneshpatel0...@gmail.com
For your next patches please do not add this From: line here. It is not
needed. It will be taken from your email From: header.
regards
sudip
--
To unsubscribe from this list: send
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Amanieu d'Antras aman...@gmail.com
commit 26135022f85105ad725cda103fa069e29e83bd16 upstream.
This function may copy the si_addr_lsb, si_lower and si_upper fields to
user mode when they haven't
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Thursday, September 17, 2015 1:57 AM
> To: Chao Yu
> Cc: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net; sta...@vger.kernel.org
> S
pm_runtime_put_sync(csdev->dev.parent);
>> list_del(>link);
>> kfree(nd);
>> }
>
> This leads to the following splat:
>
> BUG: sleeping function called from invalid context at
> /home/rabin/dev/linux/drivers/base/power/r
leads to the following splat:
BUG: sleeping function called from invalid context at
/home/rabin/dev/linux/drivers/base/power/runtime.c:892
in_atomic(): 1, irqs_disabled(): 128, pid: 763, name: perf
2 locks held by perf/763:
#0: (>mmap_sem){++}, at: [] vm_munmap+0x2c/0x50
#1: (>
Now when new refcount_t type and API are finally merged
(see include/linux/refcount.h), the following
patches convert various refcounters in the kernel susystem from atomic_t
to refcount_t. By doing this we prevent intentional or accidental
underflows or overflows that can led to use-after-free
19 Not tainted
> [2.597717] ---
> [2.597717] ./include/trace/events/printk.h:32 suspicious
> rcu_dereference_check() usage!
so this is trace_console(text, len) from
cpuidle_enter_state()
...
vprintk_emit() <<
On Thu, Sep 15, 2016 at 2:19 AM, Stephen Rothwell <s...@canb.auug.org.au> wrote:
> 23b4ed268076 ("driver: base: pinctrl: return error from
> pinctrl_bind_pins()")
>
> from the pinctrl tree and commit:
>
> eb4ec68acf5e ("driver: base: pinctrl:
Rafał Miłecki wrote:
> From: Rafał Miłecki <ra...@milecki.pl>
>
> They seem to be there from the first day. We calculate these values but
> never use them.
>
> Signed-off-by: Rafał Miłecki <ra...@milecki.pl>
Patch applied to wireless-drivers-next.git, thanks.
2df8
From: Herbert Xu <herb...@gondor.apana.org.au>
Date: Mon, 5 Dec 2016 15:28:21 +0800
> It is wrong to schedule a work from sk_destruct using the socket
> as the memory reserve because the socket will be freed immediately
> after the return from sk_destruct.
>
> Instead we s
On 12/13, gabriel.fernan...@st.com wrote:
> From: Gabriel Fernandez <gabriel.fernan...@st.com>
>
> In the stm32f469 soc, the 48Mhz clock could be derived from pll-q or
> from pll-sai-p.
>
> The SDIO clock could be also derived from 48Mhz or from sys clock.
>
> Si
On Thu, Jun 15, 2017 at 7:51 PM, Daniel Micay <danielmi...@gmail.com> wrote:
> On Fri, 2017-06-16 at 11:30 +1000, Stephen Rothwell wrote:
>> Hi Kees,
>>
>> After merging the kspp tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
From: Will Deacon <will.dea...@arm.com>
Rewritting from commit f71c2ffcb20d upstream. On LTS 4.9, there has no
raw_copy_from/to_user, neither __copy_user_flushcache, and it isn't good
idead to pick up them. The following is origin commit log, that's also
applicable for the new patch.
at the page related logs in calculate_node_totalpages(),
> it is KERNEL_DEBUG level and without any config macro.
>
> Maybe we should leave them at the same state?
I guess we can do that for the to debug messages.
When offlining memory right now:
:/# echo 0 > /sys/devices/system/memory/m
From: Will Deacon <will.dea...@arm.com>
Rewritting from commit f71c2ffcb20d upstream. On LTS 4.9, there has no
raw_copy_from/to_user, neither __copy_user_flushcache, and it isn't good
idead to pick up them. The following is origin commit log, that's also
applicable for the new patch.
From: Doug Berger
Date: Thu, 16 Jul 2020 16:38:14 -0700
> The WAKE_FILTER logic can only wake the system from the standby
> power state. However, some systems that include the GENET IP
> support deeper power saving states and the driver should suspend
> and resume correctly from
From: "Michal Vokáč"
[ Upstream commit 67122a7910bf2135dc7f7ececfcf16a5bdb362c1 ]
Commit 7e99e3470172 ("net: dsa: remove dsa_switch_alloc helper")
replaced the dsa_switch_alloc helper by devm_kzalloc in all DSA
drivers. Unfortunately it introduced a typo in qca8k.c drive
From: "Michal Vokáč"
[ Upstream commit 67122a7910bf2135dc7f7ececfcf16a5bdb362c1 ]
Commit 7e99e3470172 ("net: dsa: remove dsa_switch_alloc helper")
replaced the dsa_switch_alloc helper by devm_kzalloc in all DSA
drivers. Unfortunately it introduced a typo in qca8k.c drive
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Maninder Singh
[ Upstream commit 299815a4fba9f3c7a81434dba0072148f1690608 ]
This patch fixes commit 5f48f0bd4e36 ("mm, page_owner: skip unnecessary
stack_trace entries").
Because
at the page related logs in calculate_node_totalpages(),
> it is KERNEL_DEBUG level and without any config macro.
>
> Maybe we should leave them at the same state?
I guess we can do that for the to debug messages.
When offlining memory right now:
:/# echo 0 > /sys/devices/system/memory/m
Matthew Garrett wrote:
> + /* Ban synthetic events from some sysrq functionality */
> + if ((from == SYSRQ_FROM_PROC || from == SYSRQ_FROM_SYNTHETIC) &&
> + op_p->enable_mask & SYSRQ_DISABLE_USERSPACE)
> + p
: 0 PID: 0 Comm: swapper Not tainted 3.17.0-rc7-00012-gb38ee8265941 #69
[] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[] (show_stack) from [] (do_raw_spin_lock+0x11c/0x13c)
[] (do_raw_spin_lock) from [] (msm_console_write+0x78/0x188)
[] (msm_console_write) from
On Tue, Jul 28, 2015 at 04:19:36PM +0530, Jignesh R Patel wrote:
> From: Jignesh R Patel
For your next patches please do not add this From: line here. It is not
needed. It will be taken from your email From: header.
regards
sudip
--
To unsubscribe from this list: send the line "uns
ssages dropped ** [ 29.963836] []
(__aeabi_uidivmod) from []
(cfb_imageblit+0xac/0x464)
** 8426 printk messages dropped ** [ 30.111083] []
(fbcon_redraw.isra.12) from []
(fbcon_scroll+0x6a0/0xcbc)
** 8380 printk messages dropped ** [ 30.258209] []
(fbcon_redraw.isra.12) from []
(fbcon_scroll+0x6a0/
4.1-stable review patch. If anyone has any objections, please let me know.
--
From: Amanieu d'Antras
commit 26135022f85105ad725cda103fa069e29e83bd16 upstream.
This function may copy the si_addr_lsb, si_lower and si_upper fields to
user mode when they haven't been initialized
_ports+0x1e0/0x2d0, .magic: dead4ead, .owner: swapper/0,
> .owner_cpu: 0
> CPU: 0 PID: 0 Comm: swapper Not tainted 3.17.0-rc7-00012-gb38ee8265941 #69
> [] (unwind_backtrace) from [] (show_stack+0x10/0x14)
> [] (show_stack) from [] (do_raw_spin_lock+0x11c/0x13c)
> [] (do_raw_spin_lock) f
From: Niklas Cassel
Date: Tue, 6 Dec 2016 14:47:15 +0100
> From: Niklas Cassel
>
> From what I can tell, spin_lock(>lock) is not needed, since the
> phy_ethtool_ksettings_set call is not given the priv struct.
>
> phy_start_aneg takes the phydev->lock. Calls t
On Wed, Sep 21, 2016 at 06:51:13PM -0600, Shuah Khan wrote:
> Move pcmcia crc32hash tool from Documentation to tools/pcmcia and
> remove it from Documentation Makefile. Update location information
> for this tool. Create a new Makefile to build pcmcia. It can be built
> from top lev
On Thu, Jun 15, 2017 at 7:51 PM, Daniel Micay wrote:
> On Fri, 2017-06-16 at 11:30 +1000, Stephen Rothwell wrote:
>> Hi Kees,
>>
>> After merging the kspp tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> In file i
19 Not tainted
> [2.597717] ---
> [2.597717] ./include/trace/events/printk.h:32 suspicious
> rcu_dereference_check() usage!
so this is trace_console(text, len) from
cpuidle_enter_state()
...
vprintk_emit() <<
Use rcuidle console tracepoint because, apparently, it may be issued
from an idle CPU:
[2.581939] hw-breakpoint: Failed to enable monitor mode on CPU 0.
[2.591613] hw-breakpoint: CPU 0 failed to disable vector catch
[2.597686]
[2.597717
Now when new refcount_t type and API are finally merged
(see include/linux/refcount.h), the following
patches convert various refcounters in the kernel susystem from atomic_t
to refcount_t. By doing this we prevent intentional or accidental
underflows or overflows that can led to use-after-free
On Thu, Sep 15, 2016 at 2:19 AM, Stephen Rothwell wrote:
> 23b4ed268076 ("driver: base: pinctrl: return error from
> pinctrl_bind_pins()")
>
> from the pinctrl tree and commit:
>
> eb4ec68acf5e ("driver: base: pinctrl: return error from
> pinctrl_bin
Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> They seem to be there from the first day. We calculate these values but
> never use them.
>
> Signed-off-by: Rafał Miłecki
Patch applied to wireless-drivers-next.git, thanks.
2df86ad959c9 brcmfmac: drop unused fields fro
On 12/13, gabriel.fernan...@st.com wrote:
> From: Gabriel Fernandez
>
> In the stm32f469 soc, the 48Mhz clock could be derived from pll-q or
> from pll-sai-p.
>
> The SDIO clock could be also derived from 48Mhz or from sys clock.
>
> Signed-off-by: Gabriel Fernande
From: Herbert Xu
Date: Mon, 5 Dec 2016 15:28:21 +0800
> It is wrong to schedule a work from sk_destruct using the socket
> as the memory reserve because the socket will be freed immediately
> after the return from sk_destruct.
>
> Instead we should do the deferral p
sdev->dev.parent);
>> list_del(>link);
>> kfree(nd);
>> }
>
> This leads to the following splat:
>
> BUG: sleeping function called from invalid context at
> /home/rabin/dev/linux/drivers/base/power/runtime.c:892
> in_atomic(): 1
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Thursday, September 17, 2015 1:57 AM
> To: Chao Yu
> Cc: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net; sta...@vger.kernel.org
> S
leads to the following splat:
BUG: sleeping function called from invalid context at
/home/rabin/dev/linux/drivers/base/power/runtime.c:892
in_atomic(): 1, irqs_disabled(): 128, pid: 763, name: perf
2 locks held by perf/763:
#0: (>mmap_sem){++}, at: [] vm_munmap+0x2c/0x50
#1: (>
x){}-{3:3}, at: __device_attach+0x34/0x180
#3: df509cd8 (>mutex){}-{3:3}, at: __device_attach+0x34/0x180
#4: df4fe8c0 (regulator_ww_class_mutex){+.+.}-{3:3}, at:
regulator_resolve_supply+0x98/0x320
stack backtrace:
CPU: 3 PID: 1 Comm: swapper/0 Not tainted
5.11.0-rc3-next-20210
t;bind() or during udc_start(). In the first case, the HW was
not yet enabled, so there is no need to disable it. In the latter one,
the error might be returned only from the dwc2_lowlevel_hw_enable(), so
again there is no need to call dwc2_lowlevel_hw_disable().
If I keep the "goto error
_init label, then there is unbalanced call to
> dwc2_lowlevel_hw_disable(). usb_add_gadget_udc() can fail in 2 places:
> on gadget->bind() or during udc_start(). In the first case, the HW was
> not yet enabled, so there is no need to disable it. In the latter one,
> the error might be ret
.
>>> So, I suggest to keep jump to error_init label.
>> If I keep the jump to error_init label, then there is unbalanced call to
>> dwc2_lowlevel_hw_disable(). usb_add_gadget_udc() can fail in 2 places:
>> on gadget->bind() or during udc_start(). In the first case, the HW was
&
owlevel_hw_disable(). usb_add_gadget_udc() can fail in 2 places:
>>> on gadget->bind() or during udc_start(). In the first case, the HW was
>>> not yet enabled, so there is no need to disable it. In the latter one,
>>> the error might be returned only from the
Hi !
I had a similar problem also for the 2.4.0-test10 kernel ... if I switch
from the standard settings in the .config file and change only the
processor type to Athlon/K7 compilation fails and I waited for a
newer kernel ...
I'm using a RedHat 7.0 distribution (with all available updates
these.
Is this your own personal bug list, or is it accessible anywhere?
It's just an email folder at present. A totally unscreened summary is
below. USB, ALSA, Input, ACPI and suspend are the usual culprits.
From: Marcelo Tosatti [EMAIL PROTECTED]
Subject: Re: [BUG] 2.4.27 - 2.4.29 tar: /dev/nst0
Hi !
I had a similar problem also for the 2.4.0-test10 kernel ... if I switch
from the standard settings in the .config file and change only the
processor type to Athlon/K7 compilation fails and I waited for a
newer kernel ...
I'm using a RedHat 7.0 distribution (with all available updates
ions.
> > We should fix these.
>
> Is this your own personal bug list, or is it accessible anywhere?
It's just an email folder at present. A totally unscreened summary is
below. USB, ALSA, Input, ACPI and suspend are the usual culprits.
From: Marcelo Tosatti <[EMAIL PROTECTE
reset",
Below is the stack dump I added in of_get_named_gpiod_flags call. Which
apparently shows mdiobus_register_device would get gpio at first and
then DSA driver does.
[2.570607] [] (show_stack) from [] (dump_stack
+0x98/0xac)
[2.59] [] (dump_stack) from []
(of_ge
2 0x
[ 243.719780] Workqueue: events_unbound async_run_entry_fn
[ 243.725118] [] (__schedule) from [] (schedule+0xb0/0xcc)
[ 243.732181] [] (schedule) from []
(schedule_timeout+0x18/0x1f4)
[ 243.739840] [] (schedule_timeout) from []
(wait_for_common+0x100/0x19c)
[ 243.748207]
reset",
Below is the stack dump I added in of_get_named_gpiod_flags call. Which
apparently shows mdiobus_register_device would get gpio at first and
then DSA driver does.
[2.570607] [] (show_stack) from [] (dump_stack
+0x98/0xac)
[2.59] [] (dump_stack) from []
(of_ge
nel flip_done timed out as:
> > >
> > > WARNING: CPU: 0 PID: 31 at drivers/gpu/drm/drm_atomic_helper.c:1429
> > > drm_atomic_helper_wait_for_vblanks.part.1+0x298/0x2a0
> > > [CRTC:46:crtc-0] vblank wait timed out
> > > Modules linked in:
>
eue: events_unbound async_run_entry_fn
[ 243.725118] [] (__schedule) from [] (schedule+0xb0/0xcc)
[ 243.732181] [] (schedule) from []
(schedule_timeout+0x18/0x1f4)
[ 243.739840] [] (schedule_timeout) from []
(wait_for_common+0x100/0x19c)
[ 243.748207] [] (wait_for_common) from
On 04/07/2013 03:55 PM, Hans-Christian Egtvedt wrote:
Around Sun 07 Apr 2013 00:43:36 +0800 or thereabout, Jiang Liu wrote:
Fix building warnings caused by redifinitions of HZ:
In file included from
/ws/linux/kernel/linux.git/include/uapi/linux/param.h:4,
from include/linux
) from
[c001eb80] (warn_slowpath_common+0x4c/0x64)
[4.18] [c001eb80] (warn_slowpath_common+0x4c/0x64) from
[c001ec2c] (warn_slowpath_fmt+0x30/0x40)
[4.18] [c001ec2c] (warn_slowpath_fmt+0x30/0x40) from
[c0076908] (rcu_idle_exit_common+0x88/0xa0)
[4.18] [c0076908
[3.453582]
[3.453582] stack backtrace:
[3.458190] CPU: 0 PID: 805 Comm: w1_bus_master1 Not tainted
3.14.0-rc7-gta04 #520
[3.466156] [c0014418] (unwind_backtrace) from [c0011788]
(show_stack+0x10/0x14)
[3.474304] [c0011788] (show_stack) from [c04ee204]
(dump_stack+0x68/0x84
On Wed, Apr 09, 2014 at 10:43:32AM -0700, Lin Ming wrote:
[12890.586996] [c007a364] (sys_sched_yield+0x0/0x90) from [c03cbf90]
(yield+0x2c/0x30)
[12890.594779] r5:c18f4000 r4:
[12890.598258] [c03cbf64] (yield+0x0/0x30) from [c02eb650]
(netlink_broadcast_filtered+0x3ec/0x400
On Wed, Apr 09, 2014 at 09:47:42PM +0200, Peter Zijlstra wrote:
On Wed, Apr 09, 2014 at 10:43:32AM -0700, Lin Ming wrote:
[12890.586996] [c007a364] (sys_sched_yield+0x0/0x90) from [c03cbf90]
(yield+0x2c/0x30)
[12890.594779] r5:c18f4000 r4:
[12890.598258] [c03cbf64] (yield+0x0
On Wed, Apr 9, 2014 at 1:08 PM, Peter Zijlstra pet...@infradead.org wrote:
On Wed, Apr 09, 2014 at 09:47:42PM +0200, Peter Zijlstra wrote:
On Wed, Apr 09, 2014 at 10:43:32AM -0700, Lin Ming wrote:
[12890.586996] [c007a364] (sys_sched_yield+0x0/0x90) from [c03cbf90]
(yield+0x2c/0x30
in: i2c_viperboard viperboard netconsole [last unloaded:
viperboard]
CPU: 0 PID: 181 Comm: bash Tainted: GW 3.17.0-rc6 #1
[c0016bf4] (unwind_backtrace) from [c0013860] (show_stack+0x20/0x24)
[c0013860] (show_stack) from [c04305f8] (dump_stack+0x24/0x28)
[c04305f8] (dump_stack) from [c0040fb4
On 04/07/2013 03:55 PM, Hans-Christian Egtvedt wrote:
> Around Sun 07 Apr 2013 00:43:36 +0800 or thereabout, Jiang Liu wrote:
>> Fix building warnings caused by redifinitions of HZ:
>> In file included from
>> /ws/linux/kernel/linux.git/include/uapi/linux/param.h:4,
>
28/0x58
[3.453582]
[3.453582] stack backtrace:
[3.458190] CPU: 0 PID: 805 Comm: w1_bus_master1 Not tainted
3.14.0-rc7-gta04 #520
[3.466156] [] (unwind_backtrace) from []
(show_stack+0x10/0x14)
[3.474304] [] (show_stack) from []
(dump_stack+0x68/0x84)
[3.481933] [] (dump_stack)
From: Weng Meiling
There is a situation event is triggered before oprofile_perf_start() finish.
Because the event is still not stored in per_cpu(perf_events, cpu)[event],
op_overflow_handler() will print the warning. During the time, if unregistered
event is triggered again, the cpu will print
~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=ia64
All errors (new ones prefixed by >>):
In file included from arch/ia64/include/asm/unaligned.h:4:0,
from arch/ia64/include/asm/i
From: Marek Szyprowski
[ Upstream commit ec653df2a0cbc306a4bfcb0e3484d318fa779002 ]
card->owner is a required property and since commit 81033c6b584b ("ALSA:
core: Warn on empty module") a warning is issued if it is empty. Fix lack
of it. This fixes following warning observed on R
From: Marek Szyprowski
[ Upstream commit ec653df2a0cbc306a4bfcb0e3484d318fa779002 ]
card->owner is a required property and since commit 81033c6b584b ("ALSA:
core: Warn on empty module") a warning is issued if it is empty. Fix lack
of it. This fixes following warning observed on R
901 - 1000 of 3269027 matches
Mail list logo
