On 04/18/18 at 06:01pm, Rahul Lakkireddy wrote:
> On Wednesday, April 04/18/18, 2018 at 11:45:46 +0530, Dave Young wrote:
> > Hi Rahul,
> > On 04/17/18 at 01:14pm, Rahul Lakkireddy wrote:
> > > On production servers running variety of workloads over time, kernel
> > &
Hi Rahul,
On 04/17/18 at 01:14pm, Rahul Lakkireddy wrote:
> On production servers running variety of workloads over time, kernel
> panic can happen sporadically after days or even months. It is
> important to collect as much debug logs as possible to root cause
> and fix the problem, that may not
Hi,
On 12/11/15 at 03:26pm, Johannes Berg wrote:
> On Mon, 2015-11-23 at 09:37 +0800, Dave Young wrote:
>
> > Seems there're a lot of other wireless messages. Should we refactor
> > them as well? I still did not get chance to see where is the code.
> > (My wireless driv
Hi, Johannes
Sorry for late feedback, I was busying on other things.
On 12/11/15 at 03:38pm, Johannes Berg wrote:
> On Sun, 2015-11-15 at 15:31 +0800, Dave Young wrote:
> > cfg80211 module prints a lot of messages like below. Actually
> > printing once is acceptable but sometime
On 11/20/15 at 12:55pm, Johannes Berg wrote:
> On Sun, 2015-11-15 at 19:25 +0100, Stefan Lippers-Hollmann wrote:
> > Hi
> >
> > On 2015-11-15, Dave Young wrote:
> > > cfg80211 module prints a lot of messages like below. Actually
> > > printing once is accep
On 11/15/15 at 03:25pm, Dave Young wrote:
> On 11/13/15 at 02:54pm, Nikolay Aleksandrov wrote:
> > From: Nikolay Aleksandrov <niko...@cumulusnetworks.com>
> >
> > When __netdev_update_features() was updated to ensure some features are
> > disabled on new lower
Hi,
On 11/15/15 at 07:25pm, Stefan Lippers-Hollmann wrote:
> Hi
>
> On 2015-11-15, Dave Young wrote:
> > cfg80211 module prints a lot of messages like below. Actually printing
> > once is acceptable but sometimes it will print again and again, it looks
> > very annoy
On 11/15/15 at 09:38am, Joe Perches wrote:
> On Sun, 2015-11-15 at 15:31 +0800, Dave Young wrote:
> > cfg80211 module prints a lot of messages like below. Actually printing
> > once is acceptable but sometimes it will print again and again, it looks
> > very annoying. I
1d198dbbff 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -6426,6 +6426,8 @@ int __netdev_update_features(struct net_device *dev)
>
> if (dev->netdev_ops->ndo_set_features)
> err = dev->netdev_ops->ndo_set_features(dev, features);
> +
)
cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
The changes in this patch is to replace pr_info with pr_debug in function
print_rd_rules and print_regdomain_info
Signed-off-by: Dave Young <
Sorry, [EMAIL PROTECTED] was missed in cc
On Mon, Feb 25, 2008 at 3:34 PM, Dave Young [EMAIL PROTECTED] wrote:
On Mon, Feb 25, 2008 at 3:30 PM, Dave Young [EMAIL PROTECTED] wrote:
Quote mail from [EMAIL PROTECTED] :
2007/12/17 Louis JANG [EMAIL PROTECTED]:
Hello everybody
On Mon, Feb 25, 2008 at 5:28 PM, Louis JANG [EMAIL PROTECTED] wrote:
I ever asked marcel about the coding style. please see following thread:
http://lkml.org/lkml/2008/1/22/91
I think the style problem marcel said is
1. using kernel codeing style
2. marcel's style
On Mon, Feb 25, 2008 at 3:30 PM, Dave Young [EMAIL PROTECTED] wrote:
Quote mail from [EMAIL PROTECTED] :
2007/12/17 Louis JANG [EMAIL PROTECTED]:
Hello everybody,
I attached two patches. the first one(bluez-kernel-forcesco.patch) is to
force using HCI_OP_ADD_SCO instead
On Feb 19, 2008 12:44 PM, David Miller [EMAIL PROTECTED] wrote:
From: Dave Young [EMAIL PROTECTED]
Date: Mon, 18 Feb 2008 15:55:55 +0800
Move hci_dev_put to del_conn to avoid hci dev going away before hci conn.
This looks correct so I have applied it.
Signed-off-by: Dave Young [EMAIL
hci conn child devices other than rfcomm tty should not be moved here.
This is my lost, thanks for Barnaby's reporting and testing.
Signed-off-by: Dave Young [EMAIL PROTECTED]
---
net/bluetooth/hci_sysfs.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff -upr linux/net
Move hci_dev_put to del_conn to avoid hci dev going away before hci conn.
Signed-off-by: Dave Young [EMAIL PROTECTED]
---
net/bluetooth/hci_conn.c |1 -
net/bluetooth/hci_sysfs.c |5 -
2 files changed, 4 insertions(+), 2 deletions(-)
diff -upr linux/net/bluetooth/hci_conn.c
On Thu, Jan 31, 2008 at 02:09:30PM +0100, Jens Axboe wrote:
On Wed, Jan 30 2008, Dave Young wrote:
The bluetooth hci_conn sysfs add/del executed in the default workqueue.
If the del_conn is executed after the new add_conn with same target,
add_conn will failed with warning of same
On Feb 1, 2008 10:33 AM, David Miller [EMAIL PROTECTED] wrote:
From: Dave Young [EMAIL PROTECTED]
Date: Fri, 1 Feb 2008 09:24:41 +0800
On Thu, Jan 31, 2008 at 02:09:30PM +0100, Jens Axboe wrote:
On Wed, Jan 30 2008, Dave Young wrote:
The bluetooth hci_conn sysfs add/del executed
btaddconn btdelconn workqueues,
flush the btdelconn workqueue in the add_conn function to avoid the issue.
Signed-off-by: Dave Young [EMAIL PROTECTED]
This looks good, applied, thanks Dave.
I've queued this up for 2.6.25 merging, if you want me to
schedule it for -stable, just
to avoid the issue.
Signed-off-by: Dave Young [EMAIL PROTECTED]
---
diff -upr a/net/bluetooth/hci_sysfs.c b/net/bluetooth/hci_sysfs.c
--- a/net/bluetooth/hci_sysfs.c 2008-01-30 10:14:27.0 +0800
+++ b/net/bluetooth/hci_sysfs.c 2008-01-30 10:14:14.0 +0800
@@ -12,6 +12,8 @@
#undef
On Jan 24, 2008 11:02 AM, Dave Young [EMAIL PROTECTED] wrote:
=
[ INFO: possible recursive locking detected ]
2.6.24-rc8-mm1 #8
-
bluepush/3213 is trying to acquire lock:
(sk_lock-AF_BLUETOOTH
On Jan 24, 2008 5:54 PM, Ilpo Järvinen [EMAIL PROTECTED] wrote:
On Thu, 24 Jan 2008, Dave Young wrote:
Hi Dave ( others),
Thanks.
Thanks a lot, I was first to ignore all these because they occurred
with newreno, but looked again... :-/
New warning trigged with your debug patch
On Jan 24, 2008 5:25 PM, Dave Young [EMAIL PROTECTED] wrote:
On Jan 24, 2008 11:02 AM, Dave Young [EMAIL PROTECTED] wrote:
=
[ INFO: possible recursive locking detected ]
2.6.24-rc8-mm1 #8
from destroying rfcomm dev before tty close.
Signed-off-by: Dave Young [EMAIL PROTECTED]
---
net/bluetooth/rfcomm/tty.c |2 ++
1 file changed, 2 insertions(+)
diff -upr a/net/bluetooth/rfcomm/tty.c b/net/bluetooth/rfcomm/tty.c
--- a/net/bluetooth/rfcomm/tty.c2008-01-24 09:03
On Thu, Jan 24, 2008 at 09:19:26AM +0800, Dave Young wrote:
On Wed, Jan 23, 2008 at 02:06:29PM -0800, Andrew Morton wrote:
On Tue, 22 Jan 2008 07:18:16 +0100 Marcel Holtmann [EMAIL PROTECTED]
wrote:
Hi Dave,
Add people missed in cc-list.
Thanks Dave for your continued
On Jan 23, 2008 7:01 PM, Ilpo Järvinen [EMAIL PROTECTED] wrote:
On Wed, 23 Jan 2008, Ilpo Järvinen wrote:
On Wed, 23 Jan 2008, Dave Young wrote:
On Jan 23, 2008 3:41 PM, Ilpo Järvinen [EMAIL PROTECTED] wrote:
On Tue, 22 Jan 2008, David Miller wrote:
From: Dave Young
=
[ INFO: possible recursive locking detected ]
2.6.24-rc8-mm1 #8
-
bluepush/3213 is trying to acquire lock:
(sk_lock-AF_BLUETOOTH){--..}, at: [f8978c80]
l2cap_sock_bind+0x40/0x100 [l2cap]
but task is already
On Jan 22, 2008 2:18 PM, Marcel Holtmann [EMAIL PROTECTED] wrote:
Hi Dave,
Add people missed in cc-list.
Thanks Dave for your continued efforts on Bluetooth bugs like this.
Marcel, are you going to review/ACK/integrate/push-upstream/whatever
any of these Bluetooth patches?
It
On Jan 22, 2008 5:09 PM, Dave Young [EMAIL PROTECTED] wrote:
On Jan 22, 2008 12:37 PM, Dave Young [EMAIL PROTECTED] wrote:
On Jan 22, 2008 5:14 AM, Ilpo Järvinen [EMAIL PROTECTED] wrote:
On Mon, 21 Jan 2008, Dave Young wrote:
Please see the kernel messages following,(trigged
On Jan 22, 2008 12:37 PM, Dave Young [EMAIL PROTECTED] wrote:
On Jan 22, 2008 5:14 AM, Ilpo Järvinen [EMAIL PROTECTED] wrote:
On Mon, 21 Jan 2008, Dave Young wrote:
Please see the kernel messages following,(trigged while using some qemu
session)
BTW, seems there's some e100 error
On Jan 22, 2008 6:47 PM, Ilpo Järvinen [EMAIL PROTECTED] wrote:
On Tue, 22 Jan 2008, Dave Young wrote:
On Jan 22, 2008 12:37 PM, Dave Young [EMAIL PROTECTED] wrote:
On Jan 22, 2008 5:14 AM, Ilpo Järvinen [EMAIL PROTECTED] wrote:
On Mon, 21 Jan 2008, Dave Young wrote
On Jan 23, 2008 3:41 PM, Ilpo Järvinen [EMAIL PROTECTED] wrote:
On Tue, 22 Jan 2008, David Miller wrote:
From: Dave Young [EMAIL PROTECTED]
Date: Wed, 23 Jan 2008 09:44:30 +0800
On Jan 22, 2008 6:47 PM, Ilpo Järvinen [EMAIL PROTECTED] wrote:
[PATCH] [TCP]: debug S+L
Thanks
On Jan 22, 2008 5:14 AM, Ilpo Järvinen [EMAIL PROTECTED] wrote:
On Mon, 21 Jan 2008, Dave Young wrote:
Please see the kernel messages following,(trigged while using some qemu
session)
BTW, seems there's some e100 error message as well.
PCI: Setting latency timer of device :00:1b
On Mon, Jan 21, 2008 at 12:49:13PM +0800, Dave Young wrote:
The rfcomm tty device will possibly retain even when conn is down,
and sysfs doesn't support zombie device moving, so this patch
move the tty device before conn device is destroyed.
For the bug refered please see :
http://lkml.org
The rfcomm tty device will possibly retain even when conn is down,
and sysfs doesn't support zombie device moving, so this patch
move the tty device before conn device is destroyed.
For the bug refered please see :
http://lkml.org/lkml/2007/12/28/87
Signed-off-by: Dave Young [EMAIL PROTECTED
Please see the kernel messages following,(trigged while using some qemu session)
BTW, seems there's some e100 error message as well.
PCI: Setting latency timer of device :00:1b.0 to 64
e100: Intel(R) PRO/100 Network Driver, 3.5.23-k4-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
ACPI:
/rfcomm_dev_state_change/rfcomm_release_dev),
So add another BUG_ON when the rfcomm_dev_del is called more than one time.
Signed-off-by: Dave Young [EMAIL PROTECTED]
---
net/bluetooth/rfcomm/tty.c | 22 +-
1 file changed, 13 insertions(+), 9 deletions(-)
diff -upr linux/net/bluetooth
On Nov 22, 2007 11:56 AM, Rusty Russell [EMAIL PROTECTED] wrote:
On Thursday 22 November 2007 13:43:06 Andi Kleen wrote:
There seems to be rough consensus that the kernel currently has too many
exported symbols. A lot of these exports are generally usable utility
functions or important
On Nov 23, 2007 2:19 AM, Andi Kleen [EMAIL PROTECTED] wrote:
Andy, I like your idea. IMHO, as Rusty said a simple EXPORT_SYMBOL_TO
is better.
I don't think so. e.g. tcpcong would be very very messy this way.
And I wonder if it is possible to export to something like the struct
On 8/10/07, Dave Young [EMAIL PROTECTED] wrote:
On 8/10/07, Andrew Morton [EMAIL PROTECTED] wrote:
On Fri, 10 Aug 2007 16:18:38 +0800 Dave Young [EMAIL PROTECTED] wrote:
Hi,
2.6.23-rc2-mm2:
config with CONFIG_NF_CONNTRACK_AMANDA=y
boot oops:
hand copyed :
the EIP
40 matches
Mail list logo
