On Wed, 06 Dec 2006 00:00:13 +0100, Bernd Prager [EMAIL PROTECTED] said:
I'm trying to upgrade to kernel 1.6.19. The boot process immediatly
locks in a loop with the message: atkbd.c: Spurious ACK on
isa0060/serio0. Some program might be trying access hardware
directly.
The above message
On Tue, 2006-12-05 at 11:34 -0800, john stultz wrote:
On Tue, 2006-12-05 at 07:41 +, Ian Campbell wrote:
Should tsc be preferred to pit though?
Depends on your system. If C2/C3 or cpufreq state changes are detected,
we mark the tsc as unstable.
I'm not using them on purpose but I'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Sokolovsky schreef:
Hello Lennert,
Wednesday, December 6, 2006, 3:08:13 AM, you wrote:
[]
(These
days I build all kernels in EABI mode with old-ABI compat.) I have
not run into any code generation issues with this compiler yet.
I
The following messages just showed up in dmesg on one of my servers.
The server seems to be running fine but I would like to know if
there's a real problem here or if the message is just noise.
The server is running 2.4.25
vmscan.c:196: bad pmd 01e3.
vmscan.c:196: bad pmd 004001e3.
On Tue, 2006-12-05 at 20:30 -0800, Andrew Morton wrote:
I don't have a clue which review comments remain unaddressed - do you recall?
I never saw an item-by-item accounting of my own (extensive) review
comments, actually. And then an avalanche of new stuff got sent and I
didn't have time
Hi Greg,
Provide a function device_move() to move a device to a new parent
device. Add
auxilliary functions kobject_move() and sysfs_move_dir().
kobject_move() generates a new uevent of type KOBJ_MOVE,
containing the
previous path (DEVPATH_OLD) in
(Adding Cc: linux1394-devel)
Kristian Høgsberg wrote to linux-kernel:
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
* Jiri Kosina [EMAIL PROTECTED] wrote:
[PATCH] let WARN_ON() output the condition
It is possible, in some cases, that the output of WARN_ON() is
ambiguous and can't be properly used to identify the exact condition
which caused the warning to trigger. This happens whenever there is a
On Wed, 6 Dec 2006, Ingo Molnar wrote:
a WARN_ON() also triggers a stack dump, which should pinpoint the exact
location. (especially if combined with kallsyms) For example:
Actually, I was referring to something a little bit different. For example
kernel/mutex.c:__mutex_lock_common() calls
* Jiri Kosina [EMAIL PROTECTED] wrote:
On Wed, 6 Dec 2006, Ingo Molnar wrote:
a WARN_ON() also triggers a stack dump, which should pinpoint the exact
location. (especially if combined with kallsyms) For example:
Actually, I was referring to something a little bit different. For
(Adding Cc: linux1394-devel)
Ben Collins wrote at linux-kernel:
On Tue, 2006-12-05 at 18:21 -0500, Kristian Høgsberg wrote:
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
* Randy Dunlap [EMAIL PROTECTED] wrote:
sometimes the kernel prints something interesting while userspace
bootup keeps messages turned off via loglevel. Enable the printing
of /all/ kernel messages via the ignore_loglevel boot option. Off
by default.
Hi,
Is this equivalent to
On Wed, 6 Dec 2006, Ingo Molnar wrote:
DEBUG_LOCKS_WARN_ON(in_interrupt());\
local_irq_save(flags); \
__raw_spin_lock((lock)-raw_lock); \
DEBUG_LOCKS_WARN_ON(l-magic != l); \
When one of these
On 12/5/06, Marcel Holtmann [EMAIL PROTECTED] wrote:
And btw. I can't see any s390 patches that are using device_move() at
the moment.
These patches are in the git390 tree right now and will get push with
the next update.
Cornelia won't be available for a few weeks by the way (vacation).
--
* Jiri Kosina [EMAIL PROTECTED] wrote:
but i agree with you in theory that your proposed output is better, but
the side-effect issue is a killer i think. Could you try to rework it to
not evaluate the condition twice and to make it dependent on
CONFIG_DEBUG_BUGVERBOSE? You can avoid
On Wed, 6 Dec 2006, Ingo Molnar wrote:
i'll probably ack such a patch, it can be useful even when the line
number is unique: if someone reports a WARN_ON() from an old kernel i
dont have to dig up the exact source but can see it right from the
condition what happened. Useful redundancy in
On Dec 6 2006 10:07, Ingo Molnar wrote:
i'll probably ack such a patch, it can be useful even when the line
number is unique: if someone reports a WARN_ON() from an old kernel i
dont have to dig up the exact source but can see it right from the
condition what happened. Useful redundancy in
* Jiri Kosina [EMAIL PROTECTED] wrote:
On Wed, 6 Dec 2006, Ingo Molnar wrote:
i'll probably ack such a patch, it can be useful even when the line
number is unique: if someone reports a WARN_ON() from an old kernel i
dont have to dig up the exact source but can see it right from the
On Tue, 5 Dec 2006, Christoph Lameter wrote:
On Tue, 5 Dec 2006, Mel Gorman wrote:
There are times you want to reclaim just part of a zone - specifically
satisfying a high-order allocations. See sitations 1 and 2 from elsewhere
in this thread. On a similar vein, there will be times when you
On Tue, 5 Dec 2006, Jeff Dike wrote:
On Fri, Dec 01, 2006 at 05:09:17PM +0100, Geert Uytterhoeven wrote:
On Fri, 1 Dec 2006, Jeff Dike wrote:
And, do you have a cross-compilation environment which tests this?
Yes :-)
Can you test this patch? It works for UML and native x86_64 - if
Hi,
When running sparse checks on a file that ends up including srcu.h, we
get the following warnings:
include/linux/srcu.h:52:44: error: undefined identifier 'sp'
include/linux/srcu.h:52:44: error: bad constant expression
include/linux/srcu.h:53:56: error: undefined identifier 'sp'
Hello,
This patch is required to fix build errors of application programs
in userland. Please apply.
I hope this patch is to be included into the stable kernel branch.
Thank you.
--
The m32r kernel 2.6.18-rc1 or after cause build errors of unknown isa
configuration for userspace application
Don't mask the lower 12-bit of the page fault address.
In the current m32r kernel implementation, we use an access error handler
to detect page faults.
In order to check userspace address in do_page_fault, we have to pass
full 32-bit address to do_page_fault.
Signed-off-by: Hirokazu Takata
Fix a compile error of m32r_cfc.c.
In pcc_interrupt_wrapper, pcc_interrupt was called with wrong argument number.
Signed-off-by: Hirokazu Takata [EMAIL PROTECTED]
---
drivers/pcmcia/m32r_cfc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/pcmcia/m32r_cfc.c
This patch is for supporting a synthesizable M32700 core
for the Mappi-II FPGA board.
On the core, location of MFT (Multi-Function Timer) registers
is slightly different from the M32700 chip.
Signed-off-by: Hirokazu Takata [EMAIL PROTECTED]
---
include/asm-m32r/m32102.h |7 ---
1 files
On Mon, Dec 04 2006, Jens Axboe wrote:
On Mon, Dec 04 2006, Chen, Kenneth W wrote:
[...]
Another idea would be to kill SLAB_HWCACHE_ALIGN (it's pretty pointless,
I bet), and always alloc sizeof(*bio) + sizeof(*bvl) in one go when a
bio is allocated. It doesn't add a lot of
On Tue, 5 Dec 2006 20:40:45 -0700
Matthew Wilcox [EMAIL PROTECTED] wrote:
On Tue, Dec 05, 2006 at 02:56:41PM -0800, Ian Romanick wrote:
I don't know about SiS, but this is certainly *not* true for Via. There
are some PowerPC and, IIRC, Alpha motherboards that have Via chipsets.
Yes, but
From: Paul Jackson [EMAIL PROTECTED]
fallback_alloc() could end up calling cpuset_zone_allowed()
with interrupts disabled (by code in kmem_cache_alloc_node()),
but without __GFP_HARDWALL set, leading to a possible
call of a sleeping function with interrupts disabled.
This results in the BUG
On Wed, Dec 06 2006, Jens Axboe wrote:
I still can't help but think we can do better than this, and that this
is nothing more than optimizing for a benchmark. For high performance
I/O, you will be doing 1 page bio's anyway and this patch wont help
you at all. Perhaps we can just kill bio_vec
Hi, Andrew,
Sorry, I sent a patch with wrong title.
On m32r, ACE is an acronym of not access error, but access exception.
Please drop the previous patch entitled [PATCH 2.6.19] m32r: Fix access
error handler to pass full 32-bit address.
I will resend a correct patch again.
Thanks,
From:
Don't mask the lower 12-bit of the page fault address.
In the current m32r kernel implementation, we use an access exception
to detect page faults.
This patch fixes ace_handler (access exception handler) for m32r.
In order to check userspace address in do_page_fault, we have to pass
full 32-bit
Am Sonntag, 3. Dezember 2006 02:17 schrieb Kurtis D. Rader:
On Sat, 2006-12-02 01:56:06, Christoph Anton Mitterer wrote:
The issue was basically the following: I found a severe bug mainly by
fortune because it occurs very rarely. My test looks like the following:
I have about 30GB of
Al Viro [EMAIL PROTECTED] wrote:
Guys, please, look at actual users of that stuff.
I've been and looked at every single user of work_struct in the kernel (at
least, I think I have), and 99% of those just expect data to be the container
of the work_struct or a data structure linked to it. I had
This patch set include follow patches:
1. [PATCH] usb/hid: The HID Simple Driver Interface 0.4.1 (core)
2. [PATCH] usb/hid:Microsoft Natural Ergonomic Keyboard 4000 Driver
0.4.0
3. Some related kbuild changes.
The code base is 2.6.19.
Is this ready to merge? or
Changelogs (since 0.4.0):
1. Make hidinput_disconnect_core() be more robust, it can not break
anything even failed to allocate device struct.
2. Thanks new input device driver API, we need not the extra code for
support force-feed device yet, so say bye to CONFIG_HID_SIMPLE_FF.
On Wed, 6 Dec 2006, Li Yu wrote:
1. Make hidinput_disconnect_core() be more robust, it can not
break anything even failed to allocate device struct.
2. Thanks new input device driver API, we need not the extra code
for support force-feed device yet, so say bye
Randy Dunlap wrote:
On Tue, 05 Dec 2006 21:46:54 -0500 Ed Sweetman wrote:
-ETOOMANYWORDS -ENOPATCH, so here is one to consider.
Help text can also be added. supply text
This is similar to what USB storage already does.
I provided a patch a couple weeks ago when I brought this topic up
Hi,
Von: Stefan Richter [EMAIL PROTECTED]
...
bugs get fixed. Mainline's FireWire stack lost a lot of trust at
end-users and application developers because of periods of sometimes
very visible regressions.
For us it's working well, with no major problems (there was a problem with SMP
Hi,
I remember reading on LKML some time ago that using VMSPLIT_3G_OPT would
be optimal for a machine with exactly 1GB memory (like my current
desktop). Why is that option only prompted for after selecting EMBEDDED
(which I normally don't select for desktop machines)?
Best,
Norbert
-
To
The fasteoi IRQ handler is named fasteio incorrectly. This is a fix.
Signed-off-by: Maciej W. Rozycki [EMAIL PROTECTED]
---
It should be obvious.
Please apply.
Maciej
patch-mips-2.6.19-rc2-20061023-fasteoi-0
diff -up --recursive --new-file
On Wed, 2006-12-06 at 12:42 +0100, Norbert Kiesel wrote:
Hi,
I remember reading on LKML some time ago that using VMSPLIT_3G_OPT would
be optimal for a machine with exactly 1GB memory (like my current
desktop). Why is that option only prompted for after selecting EMBEDDED
(which I normally
On Wed, 2006-12-06 at 12:58 +0100, Arjan van de Ven wrote:
On Wed, 2006-12-06 at 12:42 +0100, Norbert Kiesel wrote:
Hi,
I remember reading on LKML some time ago that using VMSPLIT_3G_OPT would
be optimal for a machine with exactly 1GB memory (like my current
desktop). Why is that
On Mon, 2006-12-04 at 21:32 -0600, Larry Finger wrote:
Andrew Morton wrote:
On Fri, 24 Nov 2006 17:36:27 +0100
Benoit Boissinot [EMAIL PROTECTED] wrote:
On 11/24/06, Larry Finger [EMAIL PROTECTED] wrote:
Is there the equivalent of 'git bisect' for the -mmX kernels?
In article [EMAIL PROTECTED],
Marty Leisner [EMAIL PROTECTED] writes:
But its useful to change permissions/ownership of the initrd
files at times...
Since a cpio is just a userspace created string of bits, I suppose
you can apply a set of ownership/permissions to files IN the archive
On Tue, 5 Dec 2006, Andy Fleming wrote:
We need to make sure there are no more pending phy_change() invocations in the
work queue, this is true, however I'm not convinced that this avoids the
problem. And now that I come back to this email after Linus's response, let
me add that I agree with
Hi,
On Tue, 5 Dec 2006, Andrew Morton wrote:
IMO it least at needs one more iteration to address the comments that
were made (not just mine), in the short term the less it touches
unconditionally the less I care right now.
I don't have a clue which review comments remain unaddressed -
Alexander Neundorf wrote:
Von: Stefan Richter [EMAIL PROTECTED]
Mainline's FireWire stack lost a lot of trust
...
For us it's working well, with no major problems (there was a problem with
SMP kernels and the arm mapping, but my kernel is not recent and I didn't
find the time yet to update to
On Wed, Dec 06, 2006 at 10:38:48AM +, Alan wrote:
VIA south gets used by a lot of the systems but the VIA North bridges
I've got docs for cover only x86 variants, although one of the older ones
implies it has both K7 and Alpha support (just as the AMD chipset does)
VIA chips (even
On Wed, 2006-12-06 at 13:19 +0100, Norbert Kiesel wrote:
On Wed, 2006-12-06 at 12:58 +0100, Arjan van de Ven wrote:
On Wed, 2006-12-06 at 12:42 +0100, Norbert Kiesel wrote:
Hi,
I remember reading on LKML some time ago that using VMSPLIT_3G_OPT would
be optimal for a machine with
In populate_rootfs() the printk on line 554. It says Unpacking
initramfs.., which is confusing because if that line is reached the code
has already decided that the image is an initrd image. The printk is thus
wrong in stating that it is unpacking an initramfs. It should says
initrd instead.
Hi,
On Wed, 6 Dec 2006, Thomas Gleixner wrote:
If I understand it correctly, Roman wants clockevents to be usable for
other things aside hrtimer/dyntick, i.e. let other code request unused
timer event hardware for special purposes. I thought about that in the
originally but I stayed away
Andrew Morton [EMAIL PROTECTED] wrote:
On Wed, 6 Dec 2006 01:51:01 +0100 (CET)
Jiri Kosina [EMAIL PROTECTED] wrote:
[PATCH] let WARN_ON() output the condition
It is possible, in some cases, that the output of WARN_ON() is ambiguous
and can't be properly used to identify the exact
On Tue, 2006-12-05 at 21:31 -0500, Chuck Ebbert wrote:
In-Reply-To: [EMAIL PROTECTED]
On Tue, 05 Dec 2006 22:11:11 +, David Howells wrote:
I only have 32-bit userspace. When I run your program against
a directory on a JFS filesystem (msdos ioctls not supported)
I get this on
On Wed, Dec 06, 2006 at 01:19:08PM +0100, Norbert Kiesel wrote:
On Wed, 2006-12-06 at 12:58 +0100, Arjan van de Ven wrote:
On Wed, 2006-12-06 at 12:42 +0100, Norbert Kiesel wrote:
Hi,
I remember reading on LKML some time ago that using VMSPLIT_3G_OPT would
be optimal for a machine
Kasper Sandberg [EMAIL PROTECTED] wrote:
and i am very very sure its because of this, i can run with the kernel
(atleast with rc5 i had that long) for 10 days, and then chroot in, run
the 32bit apps, and within hours of using, hardlock.
What do you mean by hardlock? Do you mean the
Hi,
I got the following warning messages on some PCI Express ports.
pcie_portdrv_probe-Dev[1263:10cf] has invalid IRQ. Check vendor BIOS
I think this message is improper because those PCI Express ports don't
use an interrupt pin. This message should not be displayed for devices
which don't
* Roman Zippel [EMAIL PROTECTED] wrote:
On Wed, 6 Dec 2006, Thomas Gleixner wrote:
If I understand it correctly, Roman wants clockevents to be usable
for other things aside hrtimer/dyntick, i.e. let other code request
unused timer event hardware for special purposes. I thought about
Dear All,
I used to think that this:
struct foo {
int a __attribute__((packed));
char b __attribute__((packed));
... more fields, all packed ...
};
was exactly the same as this:
struct foo {
int a;
char b;
... more fields ...
} __attribute__((packed));
but it is not, in a subtle
Hi all,
As discussed with Pierre, I changed this patch and now I'm sending a new
version.
You can track the discussion here:
http://linux.omap.com/pipermail/linux-omap-open-source/2006-November/008466.html
Another patches weren't modified.
Fixed in this patch:
- Definition of
This patch supports m32r-g00ff bootloader for an OPSPUT platform.
Applying this patch, it is possible to do ATA-boot from an IDE drive or
HTTP-boot from network by m32r-g00ff.
* arch/m32r/boot/compressed/m32r_sio.c: Fix hangup on OPSPUT at boot.
* arch/m32r/kernel/io_opsput.c: IDE
On Wed, 2006-12-06 at 13:45 +0100, Arjan van de Ven wrote:
On Wed, 2006-12-06 at 13:19 +0100, Norbert Kiesel wrote:
On Wed, 2006-12-06 at 12:58 +0100, Arjan van de Ven wrote:
On Wed, 2006-12-06 at 12:42 +0100, Norbert Kiesel wrote:
Hi,
I remember reading on LKML some time ago
Since commit 368c73d4f689dae0807d0a2aa74c61fd2b9b075f the kernel will try
to update the non-writeable BAR registers 0..3 of PIIX4 IDE adapters if
pci_assign_unassigned_resources() is used to do full resource assignment
of the bus. This fails because in the PIIX4 these BAR registers have
Hi,
ENOTSUP is not used at all by linux (though it is defined for parisc),
while as susv3 specifies, ENOTSUP shall be different than EOPNOTSUPP.
Is there a reason for doing so? (except history)
Currently, code like
switch(errno) {
ENOTSUP:
foo();
break;
On Wed, 6 Dec 2006 13:41:43 +
Ralf Baechle [EMAIL PROTECTED] wrote:
Since commit 368c73d4f689dae0807d0a2aa74c61fd2b9b075f the kernel will try
to update the non-writeable BAR registers 0..3 of PIIX4 IDE adapters if
pci_assign_unassigned_resources() is used to do full resource assignment
of
* Horst H. von Brand [EMAIL PROTECTED] wrote:
Why not just:
WARN_ON(debug_locks_off())
here? Would give a more readable message too, IMHO.
debug_locks_off() has a side-effect, and in general we dont like to put
stuff with side-effects witin WARN_ON().
Ingo
-
To unsubscribe
On Wed, Dec 06, 2006 at 01:20:41PM +, Phil Endecott wrote:
Dear All,
I used to think that this:
struct foo {
int a __attribute__((packed));
char b __attribute__((packed));
... more fields, all packed ...
};
was exactly the same as this:
struct foo {
int a;
char b;
Hello,
I'm interested in kevents and related things. I think it isn't a bad
idea to incorporate more event kinds into the kevent implementation. Namely:
- processes (exitting/stopping/tracing)
- threads (ditto)
- futexes (for mutexes, semaphores and conditional variables)
- special
Peter Zijlstra wrote:
On Mon, 2006-12-04 at 11:30 -0800, Andrew Morton wrote:
I'd also like to pin down the situation with lumpy-reclaim versus
anti-fragmentation. No offence, but I would of course prefer to avoid
merging the anti-frag patches simply based on their stupendous size. It
seems
Eric Fox wrote:
Here is what i was able to capture from a terminal logged in to the machine
with the ISI board:
strace setserial -g /dev/ttyM0
execve(/bin/setserial, [setserial, -g, /dev/ttyM0], [/* 17 vars
*/]) = 0
uname({sys=Linux, node=dialin-0.vab.com, ...}) = 0
brk(0)
Is there any way to fix this? Glibc people don't seem to want to fix it
on their part, see
http://sources.redhat.com/bugzilla/show_bug.cgi?id=2363
Hi,
Ulrich asked you to go to us once your time travel machine was
finished.. is it finished yet ? ;=)
this is part of the ABI, so we can't
Frederik Deweerdt wrote:
On Wed, Dec 06, 2006 at 01:20:41PM +, Phil Endecott wrote:
I used to think that this:
struct foo {
int a __attribute__((packed));
char b __attribute__((packed));
... more fields, all packed ...
};
was exactly the same as this:
struct foo {
int a;
char
Hi,
Arjan van de Ven, le Wed 06 Dec 2006 15:25:14 +0100, a écrit :
Is there any way to fix this? Glibc people don't seem to want to fix it
on their part, see
http://sources.redhat.com/bugzilla/show_bug.cgi?id=2363
Ulrich asked you to go to us once your time travel machine was
Hi,
On Wed, 6 Dec 2006, Ingo Molnar wrote:
* Roman Zippel [EMAIL PROTECTED] wrote:
On Wed, 6 Dec 2006, Thomas Gleixner wrote:
If I understand it correctly, Roman wants clockevents to be usable
for other things aside hrtimer/dyntick, i.e. let other code request
unused timer
Hi,
I am playing with linux kernel but kernel dumps on WARN_ON , when I
commented WARN_ON in my code my kernel starts working but I get two
sideeffects :-
1. During Boot kernel Hangs sometimes in :-
Updating /etc/motd...done.
INIT: Entering runlevel: 3
hangs
2. Always Hangs in :-
cat
Peter Zijlstra wrote:
On Mon, 2006-12-04 at 21:32 -0600, Larry Finger wrote:
Andrew Morton wrote:
On Fri, 24 Nov 2006 17:36:27 +0100
Benoit Boissinot [EMAIL PROTECTED] wrote:
On 11/24/06, Larry Finger [EMAIL PROTECTED] wrote:
Is there the equivalent of 'git bisect' for the -mmX kernels?
On 12/6/06, Paul Sokolovsky [EMAIL PROTECTED] wrote:
Hello Lennert,
Wednesday, December 6, 2006, 3:08:13 AM, you wrote:
[]
(These
days I build all kernels in EABI mode with old-ABI compat.) I have
not run into any code generation issues with this compiler yet.
I wonder, if OABI-compat
This is a *proposed* restructuring of the DD menu so that one can
see and select/de-select entire submenus without having to enter each
submenu.It's also immediately obvious visually which submenus are
currently active.
Based on Randy Dunlap's earlier suggestion, it uses the kbuild
Right back from exams and with lots of spare time :)
I got your patch, so I'm going to try your patch and exchange all the
platform_device_* stuff with your display class and move ks0108,
cfag12864b and cfag12864bfb to drivers/video/display/
Thanks. I will post a new patch soon.
-
To
On Wed, 2006-12-06 at 09:56 +0100, Stefan Richter wrote:
(Adding Cc: linux1394-devel)
Ben Collins wrote at linux-kernel:
On Tue, 2006-12-05 at 18:21 -0500, Kristian Høgsberg wrote:
Alexey Dobriyan wrote:
On Tue, Dec 05, 2006 at 12:22:29AM -0500, Kristian Høgsberg wrote:
I'm announcing
On 12/5/06, James Simmons [EMAIL PROTECTED] wrote:
This is the pass at a display class to meet the needs of the output class
of Mr. Yu for acpi. Also this class could in time replace the lcd class
located in the backlight directory since a lcd is a type of display.
The final hope is that the
On Thu, 30 Nov 2006, Andrew Morton wrote:
That looks like it prevents the IO error. But why was an IO error causing
an infinite loop? What piece of code was initiating the retries?
Maybe it's related to the infinite domain validation retry loop problem
I reported on linux-scsi a few
On Sun, 03 Dec 2006 22:19:35 +0900, Tejun Heo wrote:
Jeff Garzik wrote:
Tejun Heo wrote:
Hello, Mikael.
Thanks for doing this.
Mikael Pettersson wrote:
[--snip--]
+static void pdc_freeze(struct ata_port *ap)
+{
+void __iomem *mmio = (void __iomem *) ap-ioaddr.cmd_addr;
+u32 tmp;
On Sun, 03 Dec 2006 22:05:51 +0900, Tejun Heo wrote:
Mikael Pettersson wrote:
This patch performs two simple cleanups of sata_promise.
* Remove board_20771 and map device id 0x3577 to board_2057x.
After the recent corrections for SATAII chips, board_20771 and
board_2057x were equivalent
On Sun, 03 Dec 2006 22:00:42 +0900, Tejun Heo wrote:
Mikael Pettersson wrote:
+}
+
+static void pdc_error_handler(struct ata_port *ap)
+{
+struct ata_eh_context *ehc = ap-eh_context;
+ata_reset_fn_t hardreset;
+
+/* stop DMA, mask IRQ, don't clobber anything else */
+
This patch performs two simple cleanups of sata_promise.
* Remove board_20771 and map device id 0x3577 to board_2057x.
After the recent corrections for SATAII chips, board_20771 and
board_2057x were equivalent in the driver.
* Remove hp-hotplug_offset and use hp-flags PDC_FLAG_GEN_II
to
Mikael Pettersson wrote:
On Sun, 03 Dec 2006 22:00:42 +0900, Tejun Heo wrote:
Mikael Pettersson wrote:
+}
+
+static void pdc_error_handler(struct ata_port *ap)
+{
+ struct ata_eh_context *ehc = ap-eh_context;
+ ata_reset_fn_t hardreset;
+
+ /* stop DMA, mask IRQ, don't
Mikael Pettersson wrote:
Don't freeze port unconditionally. You'll end up hardresetting on every
error. Just make sure DMA engine is stopped and the controller is in a
sane state. If that fails, then, the port should be frozen.
Sorry, s/hardresetting/resetting/
I'm looking into this now,
Arjan van de Ven wrote:
But, having those flushes won't hurt either. What was the conclusion of
mmio - spinlock sync discussion? I always feel kind of uncomfortable
about readl() flushes. I think they're too subtle.
those are orthogonal!
The posting flushes have nothing to do with
Mikael Pettersson wrote:
3. we don't have them in ahci nor sata_sil24.
But you do in sata_sil.c:sil_freeze().
Two versus one. It's democracy. :-)
But, having those flushes won't hurt either.
libata doesn't specify in its documentation that these driver
operations may have delayed
On 12/6/06, Alan J. Wylie [EMAIL PROTECTED] wrote:
On Wed, 06 Dec 2006 00:00:13 +0100, Bernd Prager [EMAIL PROTECTED] said:
I'm trying to upgrade to kernel 1.6.19. The boot process immediatly
locks in a loop with the message: atkbd.c: Spurious ACK on
isa0060/serio0. Some program might be
Hi Linus,
I've brought the work_struct reduction patches up to date once again.
David
---
The following changes since commit ec0bf39a471bf6fcd01def2bd677128cea940b73:
Linus Torvalds:
Merge master.kernel.org:/.../jejb/scsi-misc-2.6
are found in the git repository at:
On 12/6/06, Phil Endecott [EMAIL PROTECTED] wrote:
Dear All,
I used to think that this:
struct foo {
int a __attribute__((packed));
char b __attribute__((packed));
... more fields, all packed ...
};
was exactly the same as this:
struct foo {
int a;
char b;
... more fields
Needed to make last trace entry appear when trace_freerunning is 1.
Signed-off-by: Karsten Wiese [EMAIL PROTECTED]
--- rt6/kernel/latency_trace.c 2006-12-06 00:36:49.0 +0100
+++ rt6-kw/kernel/latency_trace.c 2006-12-06 14:43:52.0 +0100
@@ -181,7 +181,7 @@ static int
Am Dienstag, 5. Dezember 2006 23:10 schrieb Ingo Molnar:
freerunning should behave the same way with regard to latency
measurement. I.e. report_latency() is still needed, and the kernel will
thus do a maximum search over all traces triggered via start/stop.
the difference is in the
On Wed, 6 Dec 2006, Jaswinder Singh wrote:
I am playing with linux kernel but kernel dumps on WARN_ON , when I
commented WARN_ON in my code my kernel starts working but I get two
sideeffects :-
Hi,
please, submit a proper bugreport, including all the needed data (see
REPORTING-BUGS
* Roman Zippel [EMAIL PROTECTED] wrote:
If I understand it correctly, Roman wants clockevents to be usable
for other things aside hrtimer/dyntick, i.e. let other code request
unused timer event hardware for special purposes. I thought about
that in the originally but I stayed
It's rather large, but for those who want to look at it :
http://www.jdi-ict.nl/plain/serial-28112006.txt
The same problem, this time with 2.6.19. I've done a show tasks, a show
locks, a show regs, and after that, a sync + reboot :)
Log is at
Jan Blunck wrote:
On 12/6/06, Phil Endecott [EMAIL PROTECTED] wrote:
I used to think that this:
struct foo {
int a __attribute__((packed));
char b __attribute__((packed));
... more fields, all packed ...
};
was exactly the same as this:
struct foo {
int a;
char b;
... more
Samuel Thibault wrote:
this is part of the ABI, so we can't change this in 2006...
Ok, so Linux will never be fully posix compliant.
That's largely already the case, mostly because there is unfortunately
still a fair bit of rubber-stamping Solaris going on.
-hpa
-
To
Add atomic_t underrun to struct cpu_trace.
Increment it only when trace_freerunning is set and an older trace
entry is overwritten.
Modify copy_trace() to reorder entries, if underrun != 0.
Signed-off-by: Karsten Wiese [EMAIL PROTECTED]
--- rt6-kw/kernel/latency_trace-tk2.1.c 2006-12-06
1 - 100 of 784 matches
Mail list logo
