hed syslog will help you.
· If you need some more special (maybe hardware-specific)
notes, let me know.
· I use RedHat 6.2.
regards, Kristian (sorry for my bad haste english)
~~ ~~ ~~ liebevolle elektronische Briefaspekte ~~ ~ ~
~
~ Korseby Online (http://www.korseby.net)
~
with eg.
tail -1 append.log
perl -lne '$x = $_ if $_ > $x; END {print $x}' inplace.log
Please let me know if there is any additional information that I can supply to
help.
(BTW, the problem is fixed/worked-around in MariaDB by using fsync() instead
of fdatasync() when
Jan Kara writes:
> On Mon 03-09-12 10:45:15, Kristian Nielsen wrote:
>> It appears that ext3 and ext4 fdatasync() does not fully sync data to
>> disk. Specifically, when new data is written at the end (so that the file
>> length is increased), not all of the new data i
ZE, there is MAX_KMALLOC_MEM
which is defined at the beginning of the file buz.c (2.4.2) as
(512*1024). The compilation went ok after I did define KMALLOC_MAXSIZE.
There should not be any problem as I don't think I need the buz driver, I
had just unknowingly put at into the config. However,
> as you can see, the above tells you exactly how many pages you have in
> each zone and the total number of usable pages. But even that is not
> relevant to your question. What is relevant is the number
> after the first
> "/" in the "Memory:" line and also the BIOS-e820 map, of course.
>
> Als
> On Wed, 21 Feb 2001, Tigran Aivazian wrote:
>
> >
> > when you compile your 2.4.x kernel make sure you set the "4G of RAM"
> > option, i.e. CONFIG_HIGHMEM4G. If you chose "up to 1G" then
> it means "up
> > to 986M" (or something like that) -- the number in Help is
> just rounded up
> ~~
-Original Message-
From: Alan Cox [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 28, 2001 12:20 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Linux 2.4.5-ac2
> But the claim was that 2.4.5-ac2 is faster than 2.4.5 plain, so which
> changes are in 2.4.5-ac2 that would make i
ns etc. you may have :-)
Enjoy,
The Umbrella Team.
--
Kristian Sørensen
- The Umbrella Project -- Security for Consumer Electronics
http://umbrella.sourceforge.net
E-mail: [EMAIL PROTECTED], Phone: +45 29723816
-
To unsubscribe from this
oo fast: disabled for 5 minutes
INIT: no more processes left in this runlevel
I've attached the .config for both 2.6.10 (working perfectly) and the one for
2.6.11-rc5. The root filesystem this:
http://prdownloads.sourceforge.net/user-mode-linux/Debian-3.0r0.ext2.bz2
Best regards
On Wednesday 02 March 2005 14:45, Christophe Lucas wrote:
> Kristian Sørensen ([EMAIL PROTECTED]) wrote:
> > Hi!
> >
> > I've just tried usermode Linux with a 2.6.11-rc5 kernel. My kernel boots,
> > but when the shell is to be spawned it freezes:
> &g
On Wednesday 02 March 2005 14:59, Kristian Sørensen wrote:
> On Wednesday 02 March 2005 14:45, Christophe Lucas wrote:
> > Kristian Sørensen ([EMAIL PROTECTED]) wrote:
> > > Hi!
> > >
> > > I've just tried usermode Linux with a 2.6.11-rc5 kernel. My kernel
6.10. Does anyone of you know why/where the change
was?
Cheers,
KS.
--
Kristian Sørensen
E-mail: [EMAIL PROTECTED], Phone: +45 29723816
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http:/
is way in the future).
Best regards,
Kristian.
--
Kristian Sørensen
- The Umbrella Project -- Security for Consumer Electronics
http://umbrella.sourceforge.net
E-mail: [EMAIL PROTECTED], Phone: +45 29723816
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel&quo
On Wednesday 09 March 2005 00:04, Peter Chubb wrote:
> >>>>> "Kristian" == Kristian Sørensen <[EMAIL PROTECTED]> writes:
>
> Kristian> Hi all! I have some trouble reading a 2346 byte /proc entry
> Kristian> from our Umbrella kernel module.
>
Hi all!
What is the maximal data I can write to a /proc file? I write two kilo bytes,
but buffer in the proc_write function only contains 1003 bytes :-((
Cheers, Kristian.
--
Kristian Sørensen
- The Umbrella Project -- Security for Consumer Electronics
http://umbrella.sourceforge.net
-
To
On Wednesday 09 March 2005 16:17, Bob Bennett wrote:
> Kristian SÃrensen cs.aau.dk> writes:
> > Hi all!
> >
> > I have some trouble reading a 2346 byte /proc entry from our Umbrella
> > kernel module.
> >
> > if (count != UMB_POLICY_SIZE) {
>
attempt to access beyond end of device
md3: rw=0, want=18446744071656162744, limit=1465175040
I have 4 250GB SATA disk combined into one raid5 volume (kernel 2.6.10), and
this error happens after copying a few gigabytes of data into the volume and
then trying to read them back.
--
Kristian
pg
or the one fixing this! :-)
Best regards,
Kristian Sørensen.
On Monday 17 January 2005 18:17, Thomas Zehetbauer wrote:
> Hi,
>
> can anyone confirm that writing to usb-storage devices is working on SMP
> systems? Especially to a SD Card in an USB 1.1 card reader attached to a
> 64-b
e is a bitch.
> but drm_zalloc shouldjust alias to drm_calloc really..
drm_calloc calls kcalloc which performs an integer overflow check on the
'n' and 'size' arguments, which isn't needed for drm_zalloc. Small
detail, of course, but I don't see the problem w
ramming. But even if the write
transactions themselves are split transactions, it is still a low
overheads solution to your problem that avoids messing with
SPLIT_TIMEOUT.
cheers,
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
fficult, but I
haven't yet figured it out and I'm sure somebody knows it off the top
of his head.
cheers,
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
so what the DRI/DRM layer does for textures etc...
That sounds a lot like what I have now (mmap method, array of pages)
so I'll just stick with that.
thanks,
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
I do like how extern inline will never generate code and
that gcc warns on missing prototype for these case is more of a gcc bug. Not
a big deal though, it's more worthwhile to track down real missing prototype
offenders.
- fw-topology.c: make struct fw_node_create static
Looks good.
Adrian Bunk wrote:
On Mon, Jan 22, 2007 at 02:41:29PM -0500, Kristian Høgsberg wrote:
Adrian Bunk wrote:
On Thu, Jan 11, 2007 at 10:26:27PM -0800, Andrew Morton wrote:
...
Changes since 2.6.20-rc3-mm1:
...
git-ieee1394.patch
...
git trees
...
This patch contains the following cleanups
d resolved the few conflicts
from that. Stefan, I'm still not sure what the work flow should be
here, do you want to just pull these changes or should I send the 13
patches to linux1394-devel?
cheers,
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
Pete Zaitcev wrote:
Hi, Kristian:
I only looked briefly at SBP-2, and at submit/callback paths it pulled,
because I do not understand most of the other issues.
Great, thanks for giving this a look-over, much appreciated.
Executive summary: please implement proper ORB cancellation. This is
Stefan Richter wrote:
Kristian Høgsberg wrote:
...
to sum up the changes:
- Got rid of bitfields.
- Tested on ppc, ppc64 x86-64 and x86.
- ioctl interface tested on 32-bit userspace / 64-bit kernels.
- ASCIIfied sources.
- Incorporated Jeff Garziks comments.
- Updated to work with
Robert Hancock wrote:
Kristian Høgsberg wrote:
...
+static struct pci_driver fw_ohci_pci_driver = {
+.name= ohci_driver_name,
+.id_table= pci_table,
+.probe= pci_probe,
+.remove= pci_remove,
+};
How about suspend/resume support? Lots of laptops
Pieter Palmers wrote:
Kristian Høgsberg wrote:
Hi,
Here's a new set of patches for the new firewire stack. The changes
since the last set of patches address the issues that were raised on
the list and can be reviewed in detail here:
.. for some reason I didn't get patch 3/4 and
x27;ll trade them for a OHCI controller :) I have a much
more useful way to put PCILynx cards to work using my firewire sniffer
(http://bitplanet.net/nosy).
cheers,
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMA
Stefan Richter wrote:
Pete Zaitcev wrote:
On Thu, 25 Jan 2007 16:18:35 -0500, Kristian Høgsberg <[EMAIL PROTECTED]> wrote:
...
will do a status write to the status address specified in the ORB, at which
point the SBP-2 transaction is complete.
You know, I wanted to use this picture
Greg KH wrote:
On Thu, Jan 25, 2007 at 03:38:24PM -0800, Pete Zaitcev wrote:
On Thu, 25 Jan 2007 16:18:35 -0500, Kristian H??gsberg <[EMAIL PROTECTED]>
wrote:
I see that ORBs are always allocated with a call (like SKB) and not
embedded into drivers (like URBs). It's great, keep
Pete Zaitcev wrote:
On Thu, 25 Jan 2007 16:18:35 -0500, Kristian Høgsberg <[EMAIL PROTECTED]> wrote:
Indeed, I've just moved to an in-tree development model now. I still think
the out-off-tree model is a good way to prototype, get started and reach
"critical mass" with
useful
with the storage devices I have available here, though, and ready for
testing for that specific use case. Once the remaining features land,
I'd like to see this in mainstream linux and I'm interested in hearing
how people feel about this.
cheers,
Kristian
-
To unsubscribe from t
Pull in the fw-sbp2 driver for firewire storage devices.
Signed-off-by: Kristian Høgsberg <[EMAIL PROTECTED]>
---
drivers/fw/fw-ohci.c |2
drivers/fw/fw-sbp2.c | 1083 ++
2 files changed, 1084 insertions(+), 1 deletions(-)
diff -
Add the OHCI driver to the stack and build system.
Signed-off-by: Kristian Høgsberg <[EMAIL PROTECTED]>
---
drivers/fw/fw-ohci.c | 1334 ++
drivers/fw/fw-ohci.h | 152 ++
2 files changed, 1486 insertions(+), 0 deletions(-)
diff -
Benjamin Herrenschmidt wrote:
On Tue, 2006-12-05 at 00:22 -0500, Kristian Høgsberg wrote:
Hi,
I'm announcing an alternative firewire stack that I've been working on
the last few weeks. I'm aiming to implement feature parity with the
current firewire stack, but not necess
Oops, looks like the fw-core patch was to big for the list. I've
split it into two parts: fw-core which is the transaction logic and
bus reset handling and fw-device which is device probing and sysfs
integration.
cheers,
Kristian
-
To unsubscribe from this list: send the line "unsubsc
-basic-offset: 8 -*-
+ *
+ * fw-device-cdev.c - Char device for device raw access
+ *
+ * Copyright © 2005 Kristian Høgsberg <[EMAIL PROTECTED]>
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as publis
Marcel Holtmann wrote:
Hi Kristian,
I'm announcing an alternative firewire stack that I've been working on
the last few weeks. I'm aiming to implement feature parity with the
...
can you please use drivers/firewire/ if you want to start clean or
aiming at replacing drivers/i
about "release early, release often"... :) Anyway, I've moved the
portability issues to the top of my list now.
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
Alexey Dobriyan wrote:
On Tue, Dec 05, 2006 at 12:22:29AM -0500, Kristian Høgsberg wrote:
I'm announcing an alternative firewire stack that I've been working on
the last few weeks.
Is mainline firewire so hopeless, that you've decided to rewrite it? Could
you show some ug
Ray Lee wrote:
On 12/4/06, Kristian Høgsberg <[EMAIL PROTECTED]> wrote:
Ok... I was planning to make big-endian versions of the structs so
that the
endian issue would be solved. But if the bit layout is not consistent, I
guess bitfields are useless for wire formats. I didn'
all set of functions anyway, and they're
all only used inside the firewire stack.
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
uire a few lines extra code in
a PCILynx driver to buffer up the self IDs. And it's arguably better to have
the PCILynx driver do this than have the OHCI controller split up and
otherwise atomic event.
But back to the subject matter: Clearly, Kristian concentrates on
PCI/OHCI-1394 hardwar
ace? The
design of the streaming interfaces have been focused on enabling all these
ad-hoc, in-kernel drivers to move to userspace, to make it feasible to
actually support the stack.
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
Ben Collins wrote:
...
I would like to see new development efforts take cleanliness WRT host
byte order and 64bit architectures into account from the ground up. (I
understand though why Kristian made the announcement in this early
phase, and I agree with him that this kind of development has to
I_ANY_ID,
I'm not sure this is a proper class_mask?
Huh, yeah... looks like ~0 should work. And I changed this to use the
PCI_DEVICE_CLASS macro.
+.vendor= PCI_ANY_ID,
+.device= PCI_ANY_ID,
+.subvendor= PCI_ANY_ID,
+ .subdevice= PCI_ANY_
On 12/8/06, Stefan Richter <[EMAIL PROTECTED]> wrote:
Pavel Machek wrote at linux-kernel:
> On Tue 05-12-06 17:05:30, Erik Mouw wrote:
>> On Tue, Dec 05, 2006 at 10:13:55AM -0500, Kristian H?gsberg wrote:
>> > Marcel Holtmann wrote:
>> > >can you please use dr
took it out and tested with the 10 or so storage
devices I have here and it makes no difference. I've never seen the
fw_notify() that I put in there trigger. I'm taking out this workaround for
now, unless someone can tell me why it should stay there.
Kristian
-
To unsubscribe from
Stefan Richter wrote:
Kristian Høgsberg wrote:
Jeff Garzik wrote:
doesn't allowing the stack to issue REPORT LUNS take care of this?
Possibly, I don't have firewire multi-LUN devices to test with here.
The LUNs are also discoverable from the firewire config rom, which is
why
Pull this define out of drivers/ieee1394/ohci1394.c and rename to match
other PCI class defines.
---
drivers/ieee1394/ohci1394.c |4 +---
include/linux/pci_ids.h |1 +
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/ieee1394/ohci1394.c b/drivers/ieee1394/ohci1394
esses.
Happy Holidays,
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Signed-off-by: Kristian Hoegsberg <[EMAIL PROTECTED]>
---
drivers/firewire/Kconfig | 12
drivers/firewire/Makefile |1
drivers/firewire/fw-sbp2.c | 1073
3 files changed, 1086 insertions(+), 0 deletions(-)
diff --git a/drivers/fi
Signed-off-by: Kristian Hoegsberg <[EMAIL PROTECTED]>
---
drivers/firewire/Makefile |3
drivers/firewire/fw-card.c| 56 +++
drivers/firewire/fw-device-cdev.c | 617 +
drivers/firewire/fw-device-cdev.h | 146 +
drivers/fi
Signed-off-by: Kristian Hoegsberg <[EMAIL PROTECTED]>
---
drivers/firewire/Kconfig | 11
drivers/firewire/Makefile |1
drivers/firewire/fw-ohci.c | 1394
drivers/firewire/fw-ohci.h | 152 +
4 files changed, 1558 insertions
ftirqs or workqueues
on a case by case basis is a better approach. That way we also avoid
the gross wrappers.
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Mon, 2007-06-25 at 15:11 -0400, Steven Rostedt wrote:
> On Mon, 2007-06-25 at 14:48 -0400, Kristian Høgsberg wrote:
> ...
> > However, I don't really understand how you can discuss a wholesale
> > replacing of tasklets with workqueues, given the very different
> >
On Mon, 2007-06-25 at 16:31 -0400, Steven Rostedt wrote:
> On Mon, 2007-06-25 at 16:07 -0400, Kristian Høgsberg wrote:
>
> > > Maybe we should be looking at something like GENERIC_SOFTIRQ to run
> > > functions that a driver could add. But they would run only on the CPU
&
, then
idr_remove_all() to remove all ids, and idr_destroy() to free
up the cached idr_layers.
Signed-off-by: Kristian Hoegsberg <[EMAIL PROTECTED]>
---
include/linux/idr.h |1 +
lib/idr.c | 47 +++
2 files changed, 48 insertions
difference for sparse idrs, but more importantly, it's a nicer
way to iterate through the elements.
The drm subsystem is moving to idr for tracking contexts and drawables, and
with this change, we can use the idr exclusively for tracking these
resources.
Signed-off-by: Kristian Hoegsberg &l
might be
useful on a more general level. It's struct fw_attribute_group in
drivers/firewire/fw-device.h and the implementation is
init_fw_attribute_group in drivers/firewire/fw-device.c. But I agree,
attribute groups require a fair bit of boiler plate code.
cheers,
Kristian
-
To unsubscribe fro
and I
don't think the length of the names is a problem. If you end up
typing the module names too much, you're doing something wrong or
working on the firewire stack, in which case you're screwed anyway :)
Kristian
-
To unsubscribe from this list: send the line "unsubscri
useful things into lib/ so that everyone doesn't invent
their own.
I'll pull in Ivo's patch and add it to the firewire branch.
thanks,
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majo
close to none of the export functions have kerneldoc
comment blocks. I think we really should have them on something that
is a driver API.
Yeah... I'll sit down and try to document it better.
thanks
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
p down the road are strictly additions anyway. I think it makes
sense to keep the version number there, though, as a way to advertise which
ioctls are present.
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTE
new patches soon.
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Christoph Hellwig wrote:
On Wed, May 02, 2007 at 05:11:45PM -0400, Kristian H??gsberg wrote:
The firewire-cdev.h file is meant to be a self-contained userspace header
file and shouldn't include other kernel header files. All duplicated
values are standardized ieee1394 values and won&#
soon.
thanks,
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
struct sbp2_device *sd = unit->device.driver_data;
+
+ if (sd->scsi_host != NULL) {
+ scsi_remove_host(sd->scsi_host);
+ scsi_host_put(sd->scsi_host);
+ }
+ sd->scsi_host = NULL;
+}
This function seems rather oddly named. And the
Stefan Richter wrote:
Kristian Høgsberg wrote:
I was trying to be clever and only allocate the host once the device had
been discovered and initialized. I have now changed the code to just
allocate the host up front and use the hostdata mechanism for the
sbp2_device struct, which also
Plus, when the drivers
are loaded as modules, the module name will be in the stack trace. I can
track down the most generic sounding functions and give them a fw_ prefix, but
doing a whole-sale prefixing of static functions will make the source more
noisy and reduce readabilty - I'm not sur
the primary reasons for me to write an alternative
stack was to be able to leave linux1394 in maintenence mode. This way
I wont screw up existing functionality in the old stack, and will be
able to make big changes without worrying about porting over every
single driver.
Kristian
-
To unsubscrib
ck is bit-rotting anyway.
- Some SBP-2 (storage) devices fail after significant amounts of IO.
Not clear what the problem is, but I can reproduce it here and am
working on fixing it.
Please pull from the juju branch in Stefans repo:
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/
Olaf Hering wrote:
On Tue, May 01, Kristian Høgsberg wrote:
drivers/firewire/Kconfig | 60 ++
NACK.
Upgrade the current drivers/ieee1394/ with the new code, and keep all
existing module names.
What's your reasoning here? Having different module names allows people to
co
Adrian Bunk wrote:
On Wed, May 02, 2007 at 02:48:11PM +0200, Stefan Richter wrote:
Olaf Hering wrote:
On Tue, May 01, Kristian Høgsberg wrote:
drivers/firewire/Kconfig | 60 ++
NACK.
Upgrade the current drivers/ieee1394/ with the new code,
Last time I believe I was the only one
ching that list.
...
(If this division seems odd, don't blame Kristian, blame me. :-)
I'm looking forward to comments.
Looks good to me, thanks Stefan. The first three patches don't compile on
their own as they are, but it's a good split of the core stack.
Kristian
-
To un
ut a #ifndef
__FW_COMMON_DEFINES protection around the duplicate values, I guess, but I'm
just wondering why I never saw a "symbol redefined" warning...
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
dn't mind moving it to lib/
though, but nobody else in the kernel is using this bit order.
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordo
ach than implementing
ad-hoc allocation data structures.
Thanks for the reviews, I'll look through your other emails.
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
he sbp2 case for the old drivers is
still in there and in the end mkinitrd works with either stack.
Kristian
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordo
PIDs/MAC addresses. In other words, it seems to be the default
behavior of ZTE CDC Ether devices (thanks Lars Melin).
Signed-off-by: Kristian Evensen
Acked-by: Oliver Neukum
---
drivers/net/usb/cdc_ether.c | 51 +
1 file changed, 51 insertions(+)
dif
On 10/1/07, Pieter Palmers <[EMAIL PROTECTED]> wrote:
> Stefan Richter wrote:
> >> This duplicates the read cycle timer feature of raw1394 (added in Linux
> >> 2.6.21) in firewire-core's userspace ABI.
> >
> > Kristian and Pieter, does this simple duplic
true, true);
> if (ret) {
> DPU_DEBUG_PLANE(pdpu, "Check plane state failed (%d)\n", ret);
Right, I can see how the drm convention of scaling factor being from
dest to src (ie 2x scaling up src to dst is as scale factor of 0.5).
Thanks for fixing this,
Tested-by: Kristian H. Kristensen
Reviewed-by: Kristian H. Kristensen
> --
> 1.9.1
>
rns up again, or should I
install -rc2 and see if it goes away?
I was not doing anything special at the time, normal desktop load (I was using
the evince pdf viewer).
Let me know if there is anything else I can do to help track this down?
- Kristian.
Full details:
I put my .confi
Gu Zheng writes:
> Hi Kristian, Dave,
>
> Could you please help to check whether the following patch can fix this issue?
> Signed-off-by: Gu Zheng
> ---
> fs/aio.c | 28 ++--
> 1 files changed, 10 insertions(+), 18 deletions(-)
>
Ok. I'
with unpatched -rc4
for some time to check if it appears again? Anything else?
- Kristian.
Dave Jones writes:
> On Mon, Dec 02, 2013 at 06:10:46PM +0800, Gu Zheng wrote:
> > Hi Kristian, Dave,
> >
> > Could you please help to check whether the following patch can f
Kristian Nielsen writes:
> Benjamin LaHaise writes:
>
>> Linus just pushed out 3.13-rc5 that has changes to aio_migratepage() that
>> should make it much more robust, as well as other fixes. Can you please
>> give it a spin as well and let me know if it works? Than
st that can be done for now.
Thanks for following up on this!
- Kristian.
--
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/
Benjamin LaHaise writes:
> Linus just pushed out 3.13-rc5 that has changes to aio_migratepage() that
> should make it much more robust, as well as other fixes. Can you please
> give it a spin as well and let me know if it works? Thanks a bunch!
Ok, will do.
- Kristian.
--
To un
>
>> * Remove the work altogether.
>>
>> Those are in descending order of (my recommended) preference.
>
> Thanks,
> Domenico
>
> [0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919356
>
It was [pointed out] by one of our license group that [hash.h] is
On 02.08.2019 12.33, Rafael J. Wysocki wrote:
Hi All,
On top of the "Simplify the suspend-to-idle control flow" patch series
posted previously:
https://lore.kernel.org/lkml/71085220.z6FKkvYQPX@kreacher/
sanitize the suspend-to-idle flow even further.
First off, decouple EC wakeup from the LP
On 19.08.2019 11.05, Rafael J. Wysocki wrote:
On Monday, August 19, 2019 9:59:02 AM CEST Rafael J. Wysocki wrote:
On Fri, Aug 16, 2019 at 10:26 PM Kristian Klausen wrote:
On 02.08.2019 12.33, Rafael J. Wysocki wrote:
Hi All,
On top of the "Simplify the suspend-to-idle control flow&q
On 19.08.2019 22.41, Rafael J. Wysocki wrote:
On Mon, Aug 19, 2019 at 5:47 PM Kristian Klausen wrote:
On 19.08.2019 11.05, Rafael J. Wysocki wrote:
On Monday, August 19, 2019 9:59:02 AM CEST Rafael J. Wysocki wrote:
On Fri, Aug 16, 2019 at 10:26 PM Kristian Klausen wrote:
On 02.08.2019
On 20.08.2019 23.38, Rafael J. Wysocki wrote:
On Tuesday, August 20, 2019 3:29:48 PM CEST Rafael J. Wysocki wrote:
On Tue, Aug 20, 2019 at 3:10 PM Kristian Klausen wrote:
On 19.08.2019 22.41, Rafael J. Wysocki wrote:
On Mon, Aug 19, 2019 at 5:47 PM Kristian Klausen wrote:
On 19.08.2019
re than once.
Reviewed-by: Kristian H. Kristensen
> Signed-off-by: Jordan Crouse
> ---
>
> drivers/gpu/drm/msm/msm_iommu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/msm/msm_iommu.c b/drivers/gpu/drm/msm/msm_iommu.c
> index 12bb54c
Hi,
On Mon, Jun 24, 2019 at 6:26 PM Bjørn Mork wrote:
> Doh! Right you are. Thanks to both you and Andrey for quick and good
> help.
>
> We obviously have some bad code patterns here, since this apparently
> worked for Kristian by pure luck.
Thanks a lot to everyone for spottin
onntrack entry.
Signed-off-by: Kristian Evensen
---
net/netfilter/nfnetlink_queue.c | 68 +
1 file changed, 68 insertions(+)
diff --git a/net/netfilter/nfnetlink_queue.c b/net/netfilter/nfnetlink_queue.c
index c97966298..150c11ff4 100644
--- a/net/netfilter/nfnetli
operational state and I can receive/sent traffic without
problems. I also tested with some other cdc_ether devices I have and did
not find any problems/regressions caused by the two general changes.
Signed-off-by: Kristian Evensen
---
drivers/net/usb/cdc_ether.c | 53
Hi,
On Mon, Jul 18, 2016 at 3:01 PM, Oliver Neukum wrote:
> On Mon, 2016-07-18 at 14:24 +0200, Kristian Evensen wrote:
>> The firmware in the ZTE MF823/831/910 modems/mifis use OS fingerprinting to
>> determine which type of device to export. In addition, these devices export
>
1 - 100 of 157 matches
Mail list logo
