On one of my virtual machines i got this splat(running a 3.7.0-rc7):
[167986.378985] [ cut here ]
[167986.379006] WARNING: at net/core/skbuff.c:3444
skb_try_coalesce+0x359/0x390()
[167986.379012] Modules linked in:
[167986.379021] Pid: 3231, comm: apache2 Not tainted
3.7
Hi All,
Current tip (with last commit id: c41b3810c09e60664433548c5218cc6ece6a8903
(Merge tag 'pm+acpi-fixes-3.9-rc1') fails to boot with:
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.8.0-rc0-20130226 (root@serveers
Tuesday, February 26, 2013, 1:36:36 PM, you wrote:
> On Fri, 22 Feb 2013, Konrad Rzeszutek Wilk wrote:
>>
>> I don't know if this is b/c the Xen code is missing something or
>> expects something that never happend. I hadn't looked at your
>> patch in any detail (was going to do that on Monday).
Tuesday, February 26, 2013, 6:44:33 PM, you wrote:
> On Tue, 26 Feb 2013, Sander Eikelenboom wrote:
>> Tuesday, February 26, 2013, 1:36:36 PM, you wrote:
>> > On Fri, 22 Feb 2013, Konrad Rzeszutek Wilk wrote:
>> >>
>> >> I don't know if t
Hi Jeff,
During the last merge of ahci code (d9978ec5680059d727b39d6c706777c6973587f2),
i saw this coming by:
--- a/drivers/ata/libata-acpi.c
+++ b/drivers/ata/libata-acpi.c
@@ -1024,30 +1024,20 @@ static void ata_acpi_register_power_resource(struct
ata_device *dev)
{
struct scsi_devi
Hi Konrad,
Did you push the tag ?
It doesn't seem to be in your git repo.
--
Sander
Tuesday, October 23, 2012, 6:27:07 PM, you wrote:
> Hey Linus,
> Please git pull the following tag:
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> stable/for-linus-3.7-rc2-tag
> which has
Tuesday, October 23, 2012, 7:37:53 PM, you wrote:
> Hi Konrad,
> Did you push the tag ?
> It doesn't seem to be in your git repo.
Ah nevermind, it's there now. Sorry for the noise.
> --
> Sander
> Tuesday, October 23, 2012, 6:27:07 PM, you wrote:
>> Hey Linus,
>> Please git pull the follow
Tuesday, July 9, 2013, 5:05:54 PM, you wrote:
> On Tue, Jul 09, 2013 at 10:48:40AM -0400, Konrad Rzeszutek Wilk wrote:
>> Then that should be discussed on grub2 to remove said check and modify
>> the code so that it can properly work without regression.
> Actually, the kernel patch removing that
Wednesday, July 10, 2013, 8:19:34 AM, you wrote:
> On Wed, Jul 10, 2013 at 12:34:58AM +0200, Sander Eikelenboom wrote:
>>
>> Tuesday, July 9, 2013, 5:05:54 PM, you wrote:
>>
>> > On Tue, Jul 09, 2013 at 10:48:40AM -0400, Konrad Rzeszutek Wilk wrote:
>> >&
Friday, May 17, 2013, 11:52:17 AM, you wrote:
> On Fri May 17 2013 11:04:50 Sander Eikelenboom wrote:
>>
>> Friday, May 17, 2013, 10:25:24 AM, you wrote:
>>
>> > On Thu May 16 2013 19:41:42 Sander Eikelenboom wrote:
>> >> Hi Hans / Mauro,
>>
Hi All,
Tonight one of my PV guest kernels on Xen oopsed for the looks of it on some
fuse activity (by glusterfs).
--
Sander
Oops:
[107481.132631] BUG: unable to handle kernel NULL pointer dereference at
0008
[107481.132650] IP: [] __list_add+0x17/0xd0
[107481.132660] PGD 0
[10748
Hi Jeff,
Your tree git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
seems to be quiet for a few weeks now.
Any reason for not sending a pull request for the (few) pending fixes to Linus ?
--
Sander
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Fix a copy and paste mistake introduced in:
commit bc9b6407bd6df3ab7189e5622816bbc11ae9d2d8
"ACPI / PM: Rework the handling of devices depending on power resources"
Signed-off-by: Sander Eikelenboom
---
drivers/ata/libata-acpi.c |2 +-
1 files changed, 1 insertions(+), 1 deletion
Hello Sander,
Monday, April 29, 2013, 6:05:20 PM, you wrote:
> Monday, April 29, 2013, 5:46:23 PM, you wrote:
>> On Wed, Apr 24, 2013 at 08:16:37PM +0200, Sander Eikelenboom wrote:
>>> Friday, April 19, 2013, 4:44:01 PM, you wrote:
>>>
>>> > Hey Jens,
&
Monday, April 29, 2013, 5:46:23 PM, you wrote:
> On Wed, Apr 24, 2013 at 08:16:37PM +0200, Sander Eikelenboom wrote:
>> Friday, April 19, 2013, 4:44:01 PM, you wrote:
>>
>> > Hey Jens,
>>
>> > Please in your spare time (if there is such a thing
Hi Hans / Mauro,
With 3.10.0-rc1 (including the cx25821 changes from Hans), I get the bug below
which wasn't present with 3.9.
--
Sander
[ 53.004968] =
[ 53.004968] [ BUG: bad unlock balance detected! ]
[ 53.004968] 3.10.0-rc1-20130516-jens+ #1 Not tai
Friday, May 17, 2013, 10:25:24 AM, you wrote:
> On Thu May 16 2013 19:41:42 Sander Eikelenboom wrote:
>> Hi Hans / Mauro,
>>
>> With 3.10.0-rc1 (including the cx25821 changes from Hans), I get the bug
>> below which wasn't present with 3.9.
> How do I r
Friday, May 17, 2013, 11:52:17 AM, you wrote:
> On Fri May 17 2013 11:04:50 Sander Eikelenboom wrote:
>>
>> Friday, May 17, 2013, 10:25:24 AM, you wrote:
>>
>> > On Thu May 16 2013 19:41:42 Sander Eikelenboom wrote:
>> >> Hi Hans / Mauro,
>>
On linux kernel 3.7.0-pre-rc1 (last commit =
4d7127dace8cf4b05eb7c8c8531fc204fbb195f4)
I get:
[ 2954.552722]
[ 2954.563914] =
[ 2954.573011] [ INFO: inconsistent lock state ]
[ 2954.582002] 3.6.0pre-rc1-20121013 #1 Tainted: GW
[ 2954.591174] ---
Hi,
Running a 3.8.0-rc3 kernel (latest commit
b719f43059903820c31edb30f4663a2818836e7f) kernel (debian squeeze os), i'm
running into this lockdep warning when:
- Running a perl script that uses rfcomm to communicatie via bluetooth with a
bluetooth/TTL converter.
- It can run ok for a few hours
Sunday, December 16, 2012, 6:38:24 PM, you wrote:
> On Fri, Dec 14, 2012 at 04:55:57PM +0100, Sander Eikelenboom wrote:
>> Hi Konrad,
>>
>> I just tried to boot a 3.8.0-rc0 kernel (last commit:
>> 7313264b899bbf3988841296265a6e0e8a7b6521) as dom0 on my machine wi
Sunday, December 16, 2012, 6:38:24 PM, you wrote:
> On Fri, Dec 14, 2012 at 04:55:57PM +0100, Sander Eikelenboom wrote:
>> Hi Konrad,
>>
>> I just tried to boot a 3.8.0-rc0 kernel (last commit:
>> 7313264b899bbf3988841296265a6e0e8a7b6521) as dom0 on my machine wi
Sunday, December 16, 2012, 6:38:24 PM, you wrote:
> On Fri, Dec 14, 2012 at 04:55:57PM +0100, Sander Eikelenboom wrote:
>> Hi Konrad,
>>
>> I just tried to boot a 3.8.0-rc0 kernel (last commit:
>> 7313264b899bbf3988841296265a6e0e8a7b6521) as dom0 on my machine wi
Monday, December 17, 2012, 10:12:40 PM, you wrote:
> On Mon, Dec 17, 2012 at 03:46:34PM -0500, Konrad Rzeszutek Wilk wrote:
>> On Mon, Dec 17, 2012 at 09:32:17PM +0100, Sander Eikelenboom wrote:
>> >
>> > Sunday, December 16, 2012, 6:38:24 PM, you wrote:
>> >
Saturday, January 12, 2013, 7:46:39 PM, you wrote:
> Hi,
> Running a 3.8.0-rc3 kernel (latest commit
> b719f43059903820c31edb30f4663a2818836e7f) kernel (debian squeeze os), i'm
> running into this lockdep warning when:
Ok, this seems to be fixed by commit: 852e4a8152b427c3f318bb0e1b5e938d64dc
I'm trying to use a USB bluetooth dongle to connect to a bluetooth to serial
device with RFCOMM.
It's able to work fine for some time, but tt consistently fails after some time.
This is sometimes right on the start when connecting to the /dev/rfcomm0, but
it can also require several hours of run
On 2016-09-07 16:49, Jani Nikula wrote:
On Tue, 06 Sep 2016, li...@eikelenboom.it wrote:
On 2016-09-06 11:25, Jani Nikula wrote:
On Tue, 06 Sep 2016, li...@eikelenboom.it wrote:
L.S.,
Since one of the last 4.8 RC's i'm getting the warning below when
booting on my sandybridge based thinkpad.
On 26/10/17 10:05, Sander Eikelenboom wrote:
> On 26/10/17 00:02, Craig Bergstrom wrote:
>> Thanks for the notification, my apologies for the breakage. I'll take a
>> close look and see if I can figure out what went wrong.
>>
>> Sander, any chance you can send /
On 26/10/17 00:02, Craig Bergstrom wrote:
> Thanks for the notification, my apologies for the breakage. I'll take a
> close look and see if I can figure out what went wrong.
>
> Sander, any chance you can send /proc/iomem and the inputs to the mmap call
> that fail on your affected system?
Hi Cr
On 26/10/17 10:12, Sander Eikelenboom wrote:
> On 26/10/17 10:05, Sander Eikelenboom wrote:
>> On 26/10/17 00:02, Craig Bergstrom wrote:
>>> Thanks for the notification, my apologies for the breakage. I'll take a
>>> close look and see if I can figure out what
On 26/10/17 19:49, Craig Bergstrom wrote:
> Sander, thanks for the details, they've been very useful.
>
> I suspect that your host system's mem=2048M parameter is causing the
> problem. Any chance you can confirm by removing the parameter and
> running the guest code path?
I removed it, but kept
L.S.,
While testing a linux 4.14-rc6 kernel i noticed OpenVPN didn't function
anymore.
My openvpn config uses tun devices and is pretty standard.
The openvpn version is current Debian stable: openvpn 2.4.0-6+deb9u2
>From the openvpn logging:
Sat Oct 28 16:03:34 2017 us=175829 TUN/TAP device
On 27/09/18 16:26, Jens Axboe wrote:
> On 9/27/18 1:12 AM, Juergen Gross wrote:
>> On 22/09/18 21:55, Boris Ostrovsky wrote:
>>> Commit a46b53672b2c ("xen/blkfront: cleanup stale persistent grants")
>>> added support for purging persistent grants when they are not in use. As
>>> part of the purge,
On 27/09/18 21:06, Boris Ostrovsky wrote:
> On 9/27/18 2:56 PM, Jens Axboe wrote:
>> On 9/27/18 12:52 PM, Sander Eikelenboom wrote:
>>> On 27/09/18 16:26, Jens Axboe wrote:
>>>> On 9/27/18 1:12 AM, Juergen Gross wrote:
>>>>> On 22/09/18 21:55, Bori
On 27/09/18 23:48, Boris Ostrovsky wrote:
> On 9/27/18 5:37 PM, Jens Axboe wrote:
>> On 9/27/18 2:33 PM, Sander Eikelenboom wrote:
>>> On 27/09/18 21:06, Boris Ostrovsky wrote:
>>>> On 9/27/18 2:56 PM, Jens Axboe wrote:
>>>>> On 9/27/18 12:52 PM, Sande
Thursday, December 4, 2014, 1:24:47 PM, you wrote:
> On 04/12/14 12:06, Konrad Rzeszutek Wilk wrote:
>>
>> On Dec 4, 2014 6:30 AM, David Vrabel wrote:
>>>
>>> On 03/12/14 21:40, Konrad Rzeszutek Wilk wrote:
Instead of doing all this complex dance, we depend on the toolstack
doi
Thursday, December 4, 2014, 2:43:06 PM, you wrote:
> On 04/12/14 13:10, Sander Eikelenboom wrote:
>>
>> Thursday, December 4, 2014, 1:24:47 PM, you wrote:
>>
>>> On 04/12/14 12:06, Konrad Rzeszutek Wilk wrote:
>>>>
>>>> On Dec 4, 2014 6:30
Hello Sander,
Thursday, December 4, 2014, 3:09:09 PM, you wrote:
> Thursday, December 4, 2014, 2:43:06 PM, you wrote:
>> On 04/12/14 13:10, Sander Eikelenboom wrote:
>>>
>>> Thursday, December 4, 2014, 1:24:47 PM, you wrote:
>>>
>>>>
Thursday, December 4, 2014, 3:31:11 PM, you wrote:
> On 04/12/14 14:09, Sander Eikelenboom wrote:
>>
>> Thursday, December 4, 2014, 2:43:06 PM, you wrote:
>>
>>> On 04/12/14 13:10, Sander Eikelenboom wrote:
>>>>
>>>> Thursday, December 4,
Thursday, December 4, 2014, 4:39:06 PM, you wrote:
> On Thu, 2014-12-04 at 15:50 +0100, Sander Eikelenboom wrote:
>> Thursday, December 4, 2014, 3:31:11 PM, you wrote:
>>
>> > On 04/12/14 14:09, Sander Eikelenboom wrote:
>> >>
>> >> T
Hi Rafael / Len,
When i press the power-button on my intel NUC, i get twp ACPI power-events
shortly
after one another (within a second), instead of just one.
It doesn't matter if i have the old /proc/acpi interface enabled or disabled in
the kernel config.
I have tested a few older kernels l
Tuesday, January 13, 2015, 5:35:10 PM, you wrote:
> Hi Rafael / Len,
> When i press the power-button on my intel NUC, i get twp ACPI power-events
> shortly
> after one another (within a second), instead of just one.
> It doesn't matter if i have the old /proc/acpi interface enabled or disable
Hi,
I was testing 3.19-rc4 with openvswitch and encountered the splat below.
#addr2line -e
/boot/vmlinux-3.19.0-rc4-creanuc-20150114-doflr-apicpatchv3-apicrevert+
818a1690
/mnt/kernelbuild/linux-tip/net/openvswitch/datapath.c:527
--
Sander
[ 463.033308] BUG: unable to handle kernel pa
_to_irq() fails at the very beginning.
> So move creating of IOAPIC irqdomains from setup_IO_APIC() into
> arch_early_ioapic_init().
> Signed-off-by: Jiang Liu
> Signed-off-by: David Vrabel
> Reported-and-tested-by: Sander Eikelenboom
> Cc: Konrad Rzeszutek Wilk
Thanks Ger
Hi Gerry / David / Konrad,
Some more testing uncovered another issue under Xen, this time with
PCI-passthrough.
I have bisected it to the following commit:
cffe0a2b5a34c95a4dadc9ec7132690a5b0f6687 "x86, irq: Keep balance of IOAPIC pin
reference count"
It causes these symptoms:
- On Intel
-
Thursday, January 15, 2015, 2:04:34 PM, you wrote:
> With more knowledge of Xen interrupt manangement subsytem, I realized
> previous three versions to fix https://lkml.org/lkml/2014/12/19/178 are
> just plainly wrong. Those patches try to fix the issue by creating
> irqdomain for IOAPICs for PV
Thursday, January 15, 2015, 2:04:34 PM, you wrote:
> With more knowledge of Xen interrupt manangement subsytem, I realized
> previous three versions to fix https://lkml.org/lkml/2014/12/19/178 are
> just plainly wrong. Those patches try to fix the issue by creating
> irqdomain for IOAPICs for PV
Hi all,
With a 3.19-rc3 kernel i'm running into the warning below on boot with a
pvrusb2 device.
It's hitting this warn:
/*
* Drivers MUST fill in device_caps, so check for this and
* warn if it was forgotten.
*/
WARN_ON(!(cap->capabilities & V4L2_CAP_
_to_irq() fails at the very beginning.
> Enhance xen_smp_prepare_cpus() to call setup_IO_APIC() to initialize
> irqdomain for IOAPICs.
> Signed-off-by: Jiang Liu
> Reported-and-tested-by: Sander Eikelenboom
> Cc: Konrad Rzeszutek Wilk
> ---
> Hi all,
> This
Monday, January 12, 2015, 4:01:00 PM, you wrote:
> On 12/01/15 13:39, Jiang Liu wrote:
>> Commit b81975eade8c ("x86, irq: Clean up irqdomain transition code")
>> breaks xen IRQ allocation because xen_smp_prepare_cpus() doesn't invoke
>> setup_IO_APIC(), so no irqdomains created for IOAPICs and
>>
Hello Sander,
Tuesday, January 13, 2015, 5:47:24 PM, you wrote:
> Tuesday, January 13, 2015, 5:35:10 PM, you wrote:
>> Hi Rafael / Len,
>> When i press the power-button on my intel NUC, i get twp ACPI power-events
>> shortly
>> after one another (within a second), instead of just one.
>> It
Monday, January 19, 2015, 2:09:34 PM, you wrote:
> Hello Sander,
> Tuesday, January 13, 2015, 5:47:24 PM, you wrote:
>> Tuesday, January 13, 2015, 5:35:10 PM, you wrote:
>>> Hi Rafael / Len,
>>> When i press the power-button on my intel NUC, i get twp ACPI power-events
>>> shortly
>>> after
Tuesday, March 11, 2014, 4:14:38 PM, you wrote:
> Hi John,
>>> Since:
>>> - 3.14-RC6 has been cut
>>> - this regression is known and reported since the merge window
>>> - the fix (revert of 3 patches) is known for over a month now
>>> - but it's still not in mainline
>>> - my polite ping request
Friday, March 14, 2014, 2:29:43 AM, you wrote:
> Hi Sander,
> On 03/13/2014 08:49 PM, Sander Eikelenboom wrote:
>>
>> Is it just me .. or is this going at the speed of about a bluetooth
>> connection ..
>> and probably missing the boot for 3.14 ? (for no good
Saturday, March 15, 2014, 9:45:03 PM, you wrote:
> On 03/15/2014 01:53 PM, Linus Torvalds wrote:
>> Guys, why is this being discussed?
> FWIW, the 'known breakage' for 3.14 is a (valid) lockdep report.
Hmm .. whoops you are right .. i remembered it as being an "oops",
but you are right it was m
Wednesday, February 12, 2014, 12:06:44 PM, you wrote:
> Monday, February 10, 2014, 11:09:38 PM, you wrote:
>> Hi Peter,
>>> This patch series addresses a number of previously unknown issues
>>> with the RFCOMM tty device implementation, in addition to
>>> addressing the locking regression recen
Hi Konrad,
Today decided to tryout another kernel RC and your pull request to Jens on top
of it .. and I encoutered this one:
[ 438.029756] INFO: trying to register non-static key.
[ 438.029759] the code is fine but needs lockdep annotation.
[ 438.029760] turning off the locking correctness
00.0: DMA-API: exceeded 7 overlapping mappings of
pfn 3c716 .. end of dump
--
Sander
Thursday, February 6, 2014, 3:26:09 PM, you wrote:
> On Thu, Feb 6, 2014 at 5:09 AM, Sander Eikelenboom
> wrote:
>> Hmm ok that last message was false .. sorry for that .. it did happen again
>
as
>> not been used.
>>
>> Signed-off-by: Roger Pau Monné
> Reviewed-by: David Vrabel
And a Tested-by: Sander Eikelenboom
Thanks !
> Thanks.
> David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a me
Tuesday, February 11, 2014, 10:28:52 PM, you wrote:
> On Tue, 2014-02-11 at 20:56 +0100, Sander Eikelenboom wrote:
>> Hi Dan,
>>
>> FYI just tested and put Xen out of the equation (booting baremetal) and it
>> still persists.
>>
>> I tried something els
Monday, February 10, 2014, 11:09:38 PM, you wrote:
> Hi Peter,
>> This patch series addresses a number of previously unknown issues
>> with the RFCOMM tty device implementation, in addition to
>> addressing the locking regression recently reported [1].
>>
>> As Gianluca suggested and I agree, t
a v3 with the acked and reviewed-by from Konrad for x86 in it ?
--
Sander
Monday, February 3, 2014, 3:52:05 PM, you wrote:
> On Fri, Jan 31, 2014 at 10:28:22AM +0100, Sander Eikelenboom wrote:
>> Hi Bjorn / Tony,
>>
>> I fixed up ia64 as well and brought it inline again w
Hi,
I have got a regression with a 3.14-mw kernel (last commit is
4ba9920e5e9c0e16b5ed24292d45322907bb9035):
It looks like it's related to the rtl8169 ...
--
Sander
Jan 26 11:36:26 serveerstertje kernel: [ 89.105537] [ cut here
]
Jan 26 11:36:26 serveerstertje kernel:
dma_hangs+0x0/0x40
[2.192955] pci :00:01.0: Activating ISA DMA hang workarounds
[2.206543] pci :00:03.0: calling pci_fixup_video+0x0/0xe0
[2.206623] pci :00:03.0: Boot video device
[2.206710] pci :00:05.0: calling pci_fixup_video+0x0/0xe0
[2.206842] pci 0
e the primary video device before
applying the fix and let the comment reflect this.
Signed-off-by: Sander Eikelenboom
---
arch/x86/pci/fixup.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/arch/x86/pci/fixup.c b/arch/x86/pci/fixup.c
index b046e07..525e49a 1
ports:
>>
>>[2.167076] pci :00:00.0: calling quirk_natoma+0x0/0x40
>>[2.167078] pci :00:00.0: Limiting direct PCI/PCI transfers
>>[2.179807] pci :00:00.0: calling quirk_passive_release+0x0/0x90
>>[2.179953] pci :00:01.0: PIIX3: Enabling P
t;> * The standard boot ROM sequence for an x86 machine uses the BIOS
>>>> * to select an initial video card for boot display. This boot video
>>>> * card will have it's BIOS copied to C in system RAM.
>>>> * IORESOURCE_ROM_SHADOW is used to associa
gt;>>> * From information provided by "Jon Smirl"
>>>> *
>>>> * The standard boot ROM sequence for an x86 machine uses the BIOS
>>>> * to select an initial video card for boot display. This boot video
>>>> * card will have it's
Wednesday, January 15, 2014, 10:50:09 PM, you wrote:
> On Wed, Jan 15, 2014 at 12:36 PM, Sander Eikelenboom
> wrote:
>> ...
>> And that's just what my patch does ..
>>
>> + if (!vga_default_device() || pdev == vga_default_device()) {
>>
&
Hi Raghavendra,
Since the ticketlock series have landed in this mergewindow (thanks :-) ) the
help accompanying the Kconfig entry doesn't seem to reflect the current state
well.
- Wasn't the whole purpose of the ticketlock series to mitigate this 5%
performance hit to something
far less, so d
Wednesday, December 11, 2013, 7:38:50 PM, you wrote:
> On Wed, Dec 11, 2013 at 7:11 PM, Sander Eikelenboom
> wrote:
>>
>> Wednesday, December 11, 2013, 6:53:07 PM, you wrote:
>>
>>> The best way to address all this is by automatic region awareness and
>>&
Monday, December 16, 2013, 12:37:47 PM, you wrote:
> On 12/16/2013 12:22 PM, Sander Eikelenboom wrote:
>>
>> Wednesday, December 11, 2013, 7:38:50 PM, you wrote:
>>
>>> On Wed, Dec 11, 2013 at 7:11 PM, Sander Eikelenboom
>>> wrote:
>>>>
>&
Monday, December 16, 2013, 3:35:15 PM, you wrote:
> On Mon, Dec 16, 2013 at 10:59:01AM +, David Vrabel wrote:
>> On 13/12/13 16:09, Konrad Rzeszutek Wilk wrote:
>> > Hey,
>> >
>> > While I was trying to narrow down the state of GPU passthrough
>> > (still not finished) and figuring what need
Monday, December 16, 2013, 4:36:12 PM, you wrote:
> On Mon, Dec 16, 2013 at 04:23:53PM +0100, Sander Eikelenboom wrote:
>>
>> Monday, December 16, 2013, 3:35:15 PM, you wrote:
>>
>> > On Mon, Dec 16, 2013 at 10:59:01AM +, David Vrabel wrote:
>> >>
Monday, December 16, 2013, 4:36:12 PM, you wrote:
> On Mon, Dec 16, 2013 at 04:23:53PM +0100, Sander Eikelenboom wrote:
>>
>> Monday, December 16, 2013, 3:35:15 PM, you wrote:
>>
>> > On Mon, Dec 16, 2013 at 10:59:01AM +, David Vrabel wrote:
>> >>
Tuesday, December 17, 2013, 3:17:50 AM, you wrote:
> Hi Sander,
> On Mon, Dec 16, 2013 at 11:56 PM, Sander Eikelenboom
> wrote:
>>
>> Monday, December 16, 2013, 12:37:47 PM, you wrote:
>>
>>> On 12/16/2013 12:22 PM, Sander Eikelenboom wrote:
>>>&g
Hi all,
Since:
- 3.14-RC6 has been cut
- this regression is known and reported since the merge window
- the fix (revert of 3 patches) is known for over a month now
- but it's still not in mainline
- my polite ping request from last week seems to have provoked exactly 0 (zero)
response.
IT'S TIME
+ return;
> +
> spin_lock_irqsave(&radix_lock, flags);
> /* since we are counting overlaps the final put of the
> * cacheline will occur when the overlap count is 0.
> Sander, barring a negative test result from you I'll send the atta
acks suppressed
So use dev_dbg_ratelimited() instead of this construction.
Signed-off-by: Sander Eikelenboom
---
sound/usb/pcm.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/sound/usb/pcm.c b/sound/usb/pcm.c
index 131336d..c62a165 100644
--- a/sound/usb/pcm.c
+++ b/
t;net" variant.
Sander Eikelenboom (1):
Sound USB: Prevent printk ratelimiting from spamming kernel log while
DEBUG not defined
sound/usb/pcm.c |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--
1.7.10.4
--
To unsubscribe from this list: send the line "unsubscribe l
Friday, May 2, 2014, 6:13:09 PM, you wrote:
> At Fri, 2 May 2014 15:09:27 +0200,
> Sander Eikelenboom wrote:
>>
>> This (widely used) construction:
>>
>> if(printk_ratelimit())
>> dev_dbg()
>>
>> Causes the ratelimiting to spam t
Hi,
I just ran into the oops belowafter some uptime.
--
Sander
[175753.946560] IP: [] kobject_put+0x11/0x70
[175753.964484] PGD 0
[175753.982157] Oops: [#1] SMP
[175753.999575] Modules linked in:
[175754.016705] CPU: 4 PID: 23869 Comm: kworker/u12:3 Not tainted
3.14.0-mw-20140409a+ #1
[1
t .. CC'ed some more folks .. you
never know ..
--
Sander
Tuesday, March 25, 2014, 4:29:42 PM, you wrote:
> Tuesday, March 25, 2014, 4:15:39 PM, you wrote:
>> On Sat, Mar 22, 2014 at 07:28:34PM +0100, Sander Eikelenboom wrote:
>> [...]
>>> > Yes there is
Wednesday, March 26, 2014, 3:44:42 PM, you wrote:
>> -Original Message-
>> From: Sander Eikelenboom [mailto:li...@eikelenboom.it]
>> Sent: 26 March 2014 11:11
>> To: Paul Durrant
>> Cc: Wei Liu; annie li; Zoltan Kiss; xen-de...@lists.xen.org; Ian Campb
Wednesday, March 26, 2014, 4:50:30 PM, you wrote:
>> -Original Message-
>> From: Sander Eikelenboom [mailto:li...@eikelenboom.it]
>> Sent: 26 March 2014 15:23
>> To: Paul Durrant
>> Cc: Wei Liu; annie li; Zoltan Kiss; xen-de...@lists.xen.org; Ian Campb
Wednesday, March 26, 2014, 5:25:21 PM, you wrote:
>> -Original Message-
>> From: Sander Eikelenboom [mailto:li...@eikelenboom.it]
>> Sent: 26 March 2014 16:07
>> To: Paul Durrant
>> Cc: Wei Liu; annie li; Zoltan Kiss; xen-de...@lists.xen.org; Ian Campb
Hi Paul,
Seems your last mail arrived in pretty bad shape (truncated) in my mailbox ..
--
Sander
Wednesday, March 26, 2014, 6:16:49 PM, you wrote:
>> -Original Message-
>> From: Sander Eikelenboom [mailto:li...@eikelenboom.it]
>> Sent: 26 March 2014 16:54
>>
Wednesday, March 26, 2014, 6:46:06 PM, you wrote:
> Re-send shortened version...
>> -Original Message-
>> From: Sander Eikelenboom [mailto:li...@eikelenboom.it]
>> Sent: 26 March 2014 16:54
>> To: Paul Durrant
>> Cc: Wei Liu; annie li; Zoltan Kiss; xen-
Wednesday, March 26, 2014, 6:48:15 PM, you wrote:
>> -Original Message-
>> From: Paul Durrant
>> Sent: 26 March 2014 17:47
>> To: 'Sander Eikelenboom'
>> Cc: Wei Liu; annie li; Zoltan Kiss; xen-de...@lists.xen.org; Ian Campbell;
>> linux-
&g
Wednesday, March 26, 2014, 7:15:30 PM, you wrote:
>> -Original Message-
>> From: Sander Eikelenboom [mailto:li...@eikelenboom.it]
>> Sent: 26 March 2014 18:08
>> To: Paul Durrant
>> Cc: Wei Liu; annie li; Zoltan Kiss; xen-de...@lists.xen.org; Ian Campb
Thursday, March 27, 2014, 10:47:02 AM, you wrote:
>> -Original Message-
>> From: Sander Eikelenboom [mailto:li...@eikelenboom.it]
>> Sent: 26 March 2014 19:57
>> To: Paul Durrant
>> Cc: Wei Liu; annie li; Zoltan Kiss; xen-de...@lists.xen.org; Ian Campb
shortly.
OK will test them ASAP.
Thursday, March 27, 2014, 10:54:09 AM, you wrote:
>> -Original Message-
>> From: Sander Eikelenboom [mailto:li...@eikelenboom.it]
>> Sent: 26 March 2014 20:18
>> To: Paul Durrant
>> Cc: Wei Liu; annie li; Zoltan Kiss; xen-de
Monday, April 14, 2014, 1:30:15 PM, you wrote:
> On Sat, Apr 12, 2014 at 01:34:31PM +0200, Sander Eikelenboom wrote:
>> Hi,
>>
>> I just ran into the oops belowafter some uptime.
> Classic use after free introduced by my recent changes, sorry.
> This should f
Friday, July 11, 2014, 10:08:47 PM, you wrote:
> Please see this set of patches which are fixes to Xen pciback
> for 3.17. They are also located at:
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> devel/pciback-3.17.v4
> These patches do not include the PCI bus reset/slot co
Monday, July 14, 2014, 7:22:25 PM, you wrote:
> On Mon, Jul 14, 2014 at 06:37:55PM +0200, Sander Eikelenboom wrote:
>>
>> Friday, July 11, 2014, 10:08:47 PM, you wrote:
>>
>> > Please see this set of patches which are fixes to Xen pciback
>> > for 3.17.
Monday, July 14, 2014, 7:37:53 PM, you wrote:
>> >> Ad B)
>> >>
>> >> root@dom0:~# xl pci-list router
>> >> Vdev Device
>> >> 05.0 :00:1b.0
>> >>
>> >> root@dom0:~# xl pci-assignable-list
>> >> :02:00.0
>> >>
>> >> root@dom0:~# xl pci-detach router 00:1b.0
>> >> dmesg shows:
>> >> [ 1
Monday, July 14, 2014, 7:45:25 PM, you wrote:
> On Mon, Jul 14, 2014 at 07:43:04PM +0200, Sander Eikelenboom wrote:
>>
>> Monday, July 14, 2014, 7:37:53 PM, you wrote:
>>
>> >> >> Ad B)
>> >> >>
>> >> >> root
Monday, July 14, 2014, 8:45:47 PM, you wrote:
> On Mon, Jul 14, 2014 at 08:24:33PM +0200, Sander Eikelenboom wrote:
>>
>> Monday, July 14, 2014, 7:45:25 PM, you wrote:
>>
>> > On Mon, Jul 14, 2014 at 07:43:04PM +0200, Sander Eikelenboom wrote:
>> >>
Monday, July 14, 2014, 9:01:29 PM, you wrote:
> Monday, July 14, 2014, 8:45:47 PM, you wrote:
>> On Mon, Jul 14, 2014 at 08:24:33PM +0200, Sander Eikelenboom wrote:
>>>
>>> Monday, July 14, 2014, 7:45:25 PM, you wrote:
>>>
>>> > On Mon, Jul
Monday, July 14, 2014, 9:54:05 PM, you wrote:
> On Mon, Jul 14, 2014 at 09:01:29PM +0200, Sander Eikelenboom wrote:
>>
>> Monday, July 14, 2014, 8:45:47 PM, you wrote:
>>
>> > On Mon, Jul 14, 2014 at 08:24:33PM +0200, Sander Eikelenboom wrote:
>> >>
1 - 100 of 206 matches
Mail list logo
