On Sat, Feb 10, 2007 at 11:12:34PM -0800, Randy Dunlap wrote:
> On Sun, 11 Feb 2007 01:02:47 -0600 [EMAIL PROTECTED] wrote:
>
> > I don't see CONFIG_BLK_DEV_INITRD=y
> >
> > Regards,
> > Vito Caputo
> >
> > BTW, this isnt the appropriate place for asking this type of question...
>
> Please expl
Greetings,
I've been running md on my server for some time now and a few days ago one of
the (3) drives in the raid5 array starting giving read errors. The result was
usually system hangs and this was with kernel 2.6.17.13. I upgraded to the
latest production 2.6.20 kernel and experienced the same
sorry, this should of course go to the people to blame aswell :)
On Wed, Feb 07, 2007 at 09:32:54AM +0100, Christoph Hellwig wrote:
> On Wed, Feb 07, 2007 at 07:59:18AM +, Linux Kernel Mailing List wrote:
> > [IA64] swiotlb abstraction (e.g. for Xen)
> >
> > Add abstraction so tha
[EMAIL PROTECTED] wrote:
I have built a number of previous kernels, but am having problems with
2.6.20.
I initially tried just changing only the Processor type (so what I had done
would be easy to describe). Someone on this list was kind enough to tell
me that the SATA/PATA drivers were not on
On Sun, 11 Feb 2007 01:02:47 -0600 [EMAIL PROTECTED] wrote:
> I don't see CONFIG_BLK_DEV_INITRD=y
>
> Regards,
> Vito Caputo
>
> BTW, this isnt the appropriate place for asking this type of question...
Please explain why not.
And please delete large parts of email that are not needed in replie
On Sun, Feb 11, 2007 at 06:34:31AM +, Al Viro wrote:
> +config NO_IOPORT
> + bool
> + default n
please make this IOPORT. config symbols with an implicit negation
are quite horrible for the brain to understand.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Sun, 11 Feb 2007 06:34:31 + Al Viro wrote:
> My current version:
>
> >From 97f115834b5ebef4f04e0f18aaa10f78f43733a0 Mon Sep 17 00:00:00 2001
> From: Al Viro <[EMAIL PROTECTED]>
> Date: Sat, 10 Feb 2007 23:41:09 -0500
> Subject: [PATCH] sort the devres mess out
>
> Split the implementation
On Sat, Feb 10, 2007 at 08:50:27PM +0100, Rafael J. Wysocki wrote:
> On Saturday, 10 February 2007 18:52, Daniel Barkalow wrote:
> > On Sat, 10 Feb 2007, Rafael J. Wysocki wrote:
> >
> > > On Saturday, 10 February 2007 11:02, Nigel Cunningham wrote:
> > >
> > > > Well, the original desire was to s
From: Randy Dunlap <[EMAIL PROTECTED]>
Teach kernel-doc to handle functions that look like the new
pcim_iomap_table(). Fixes this fatal error in scripts/kernel-doc:
DOCPROC Documentation/DocBook/kernel-api.xml
Error(/tester/linsrc/linux-2.6.20-git6//drivers/pci/pci.c:1351): cannot
understand
From: Randy Dunlap <[EMAIL PROTECTED]>
Make devres.c ready for adding to DocBook.
Fix a few comment typos in drivers/pci/pci.c.
Add devres.c to DocBook.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
---
Documentation/DocBook/kernel-api.tmpl |4
drivers/base/devres.c |
Hi Nigel,
On Sun, Feb 11, 2007 at 09:37:06AM +1100, Nigel Cunningham wrote:
> On Sat, 2007-02-10 at 23:20 +0100, Rafael J. Wysocki wrote:
(...)
> > What about this:
> >
> > "If the device requires that, implement .suspend and .resume or at least
> > define .suspend that will always return -ENOSYS
Al Viro wrote:
My current version:
From 97f115834b5ebef4f04e0f18aaa10f78f43733a0 Mon Sep 17 00:00:00 2001
From: Al Viro <[EMAIL PROTECTED]>
Date: Sat, 10 Feb 2007 23:41:09 -0500
Subject: [PATCH] sort the devres mess out
Split the implementation-agnostic stuff in separate files.
Make sure that t
On Sun, Feb 11, 2007 at 01:26:40AM -0500, Tejun Heo wrote:
> Christoph Hellwig wrote:
> >I haven't looked at what causes it, but any leakage of pci details
> >into io.h is bogus. I'd suggest that the original submitter fixes
> >up that problem instead.
>
> pci_iomap() depends on two things - PCI
On Sun, Feb 11, 2007 at 05:50:15AM +, Al Viro wrote:
>
> I have some stuff in that direction, but it take some resurrecting...
OK, we should talk.
Here is what I have:
Linearize bytecode writer, which produce the binary linearized code.
The uncompress size is about 10 times the i386 .o file
On Sat, Feb 10, 2007 at 02:14:31AM +0100, Nicolas Kaiser wrote:
> Typos in KERN_ERR, KERN_INFO.
>
> Signed-off-by: Nicolas Kaiser <[EMAIL PROTECTED]>
> ---
>
> arch/arm/mach-imx/dma.c |2 +-
> arch/arm/mach-s3c2410/pm-simtec.c |2 +-
> arch/arm/plat-omap/dma.c |2 +
Christoph Hellwig wrote:
I haven't looked at what causes it, but any leakage of pci details
into io.h is bogus. I'd suggest that the original submitter fixes
up that problem instead.
pci_iomap() depends on two things - PCI and iomap. AFAIK, there is no
config to test whether the current arch
Andrew Morton wrote:
On Sat, 10 Feb 2007 19:32:30 +0200 "S.Çağlar Onur" <[EMAIL PROTECTED]> wrote:
Hi;
31 Oca 2007 Çar tarihinde, [EMAIL PROTECTED] şunları yazmıştı:
The patch titled
kvm: Fix asm constraint for lldt instruction
has been added to the -mmtree. Its filename is
Pierre Ossman wrote:
Alex Dubov wrote:
One more problem (you may already know about it) - I was contacted by somebody
from the hald
project and indeed I can confirm that on 2.6.20 kernel hald fails to take
action on card
insertion. I can't see anything in my code so this may be a general mmc p
On Sat, 10 Feb 2007, Eric W. Biederman wrote:
> There are not enough details in the justification to really understand
> the issue so I'm asking to see if someone has some more details.
>
> The description makes the assertion that reprograming the ioapic
> when an interrupt is pending is the onl
On Sat, Feb 10, 2007 at 06:33:25PM +0100, Andi Kleen wrote:
> Interesting. Did you find any kernel bugs with this?
In short, not very useful yet.
The current run of of sparse-0.2-cl2 on git default i386 config
will find about 6 place kernel using allocated memory without NULL
check. But Linus sai
On Sat, Feb 10, 2007 at 09:17:58PM -0800, Christopher Li wrote:
> e.g. sparse has not way to know some function only get called with interrupt
> disabled (or some lock already hold). So it assume interrupt is still
> enable and generate wrong warnings. Another example is that some helper
> function
On Sat, Feb 10, 2007 at 05:14:13PM -0500, Tejun Heo wrote:
> Heiko Carstens wrote:
> >On Sat, Feb 10, 2007 at 12:43:16PM -0500, Tejun Heo wrote:
> \>> Heiko, how about this? Does it fix s390?
> >
> >Unfortunately not. Now I get
> >
> > CC lib/iomap.o
> >lib/iomap.c: In function 'devm_ioport_
On Friday 09 February 2007 14:03, Jens Axboe wrote:
> Hi,
>
> Unfortunately I'm a little short on time as I'll be travelling tomorrow,
> but of course preparing a new kernel for the laptop is something you
> want to do right before leaving. So I discovered that the current (well
> as of yesterday,
On Sat, 10 Feb 2007, Ralf Baechle wrote:
> Unfortunately struct epoll_event contains a gap so it bets on identical
> padding rules between native and compat ABI and anyway, padding is wasted
> space so the struct members should have been swapped when this structure
> was created. Oh well, too lat
On Saturday 10 February 2007 19:33, Richard Purdie wrote:
> As mentioned previously, I've setup a backlight git tree at:
>
> http://git.o-hand.com/?p=linux-rpurdie-backlight;a=shortlog;h=for-mm
> (git://git.o-hand.com/linux-rpurdie-backlight)
>
> A patch of the combined changes to mainline is:
>
>
> This looks like the problem with races in mmc_block again. Add some printk:s
> in
> the remove function so that you can see if this oops is after the remove
> function (shouldn't be possible, but will cause crash if it is).
It just occurred to me that my synopsis of the problem was utterly l
On Wed, 7 Feb 2007, Tejun Heo wrote:
Grzegorz Kulewski wrote:
It worked very well for half a year but with one disk (IIRC it was even
plugged into second channel but I wont bet on it). Now I have second disk
(very similar) and it is always put into PIO4 mode:
[ 17.404451] libata version 2
This is the accumulated SCSI tree for 2.6.20. It is available at
master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6.git
The short changelog is:
Adrian Bunk (1):
aic79xx: make ahd_match_scb() static
Ahmed S. Darwish (1):
DAC960: kmalloc->kzalloc/Casting cleanups
Alexi
On Sat, Feb 10, 2007 at 12:45:50PM +0100, Heiko Carstens wrote:
> From: Heiko Carstens <[EMAIL PROTECTED]>
>
> 9ac7849e35f705830f7b016ff272b0ff1f7ff759 causes this:
>
> CC arch/s390/mm/ioremap.o
> In file included from arch/s390/mm/ioremap.c:18:
> include/linux/io.h:46:
> warning: "s
Andi Kleen wrote:
[Snip]
You run with report_lost_ticks and report the results to linux-kernel
Doing as I am told, here we go:
This is 100% reproducible, ie: just doing a big rsync between 2 disks
and burning a DVD at the same time. Note: the system isn't very
responsive when this happens, mo
On Sat, Feb 10 2007, Rafael J. Wysocki wrote:
> On Saturday, 10 February 2007 12:50, Jens Axboe wrote:
> > On Sat, Feb 10 2007, Jens Axboe wrote:
> > > On Sat, Feb 10 2007, Rafael J. Wysocki wrote:
> > > > Hi,
> > > >
> > > > On Friday, 9 February 2007 20:03, Jens Axboe wrote:
> > > > > Hi,
> > >
On Sat, 10 Feb 2007, Dave Jones wrote:
>
> Shrink the held_lock struct by using bitfields.
> This shrinks task_struct on lockdep enabled kernels by 480 bytes.
Are we sure that there are no users that depend on accessing the different
fields under different locks?
Having them as separate "int"
On Sat, 10 Feb 2007, David Miller wrote:
>
> Even if you have everything, every page, every log file, in the page
> cache, everything talking over the network wants to block.
>
> Will you create a thread every time tcp_sendmsg() hits the send queue
> limits?
No. You use epoll() for those.
>
On Sat, Feb 10, 2007 at 10:32:07AM +, David Woodhouse wrote:
> On Sat, 2007-02-10 at 11:22 +0100, Heiko Carstens wrote:
> > Which remembers me that I think that MIPS is using the non-compat version
> > of sys_epoll_pwait for compat syscalls. But maybe MIPS doesn't need a compat
> > syscall for
On Sat, Feb 10, 2007 at 11:22:05AM +0100, Heiko Carstens wrote:
> Which remembers me that I think that MIPS is using the non-compat version
> of sys_epoll_pwait for compat syscalls. But maybe MIPS doesn't need a compat
> syscall for some reason. Dunno.
Which reminds me that x86_64 i386 compat doe
On Sat, 10 Feb 2007 12:43:16 -0500 Tejun Heo wrote:
> devres iomap made lib/iomap.c always built and added several
> arch-indep PCI routines to include/linux/io.h and lib/iomap.c without
> wrapping them inside CONFIG_PCI. This breaks configurations where PCI
> is not configured. Wrap pci_iomap()
>> [pata_pcmcia dmesg]
>> ata1.00: CFA, max PIO0, 20480 sectors: LBA
>> ata1.00: ata1: dev 0 multi count 0
>> ata1.01: CFA, max PIO0, 20480 sectors: LBA
>> ata1.01: ata1: dev 1 multi count 0
>Do you have two cards here ?
No. one card.
I am not sure why two devices are detected.
Actually, thi
On Sat, Feb 10, 2007 at 08:45:26PM +0100, Miguel Ojeda wrote:
> When I was testing some stuff at 2.6.20-rc6-mm3 I found this at dmesg
> multiple times.
>
Could you try this hotfix
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc6/2.6.20-rc6-mm3/hot-fixes/ntfs-kmap_atomic-atomic
> The PATA_PCMCIA driver does not work.
> The kernel version is 2.6.20.
> Does anyone test this driver?
Yes it gets regularly tested and works reliably on my test harware. I am
however using standards compliant hardware.
> [pata_pcmcia dmesg]
> ata1.00: CFA, max PIO0, 20480 sectors: LBA
> ata1.0
From: Linus Torvalds <[EMAIL PROTECTED]>
Date: Fri, 9 Feb 2007 14:33:01 -0800 (PST)
> So I actually like this, because it means that while we slow down
> real IO, we don't slow down the cached cases at all.
Even if you have everything, every page, every log file, in the page
cache, everything tal
On Sat, Feb 10, 2007 at 09:56:07AM -0800, Michael Kerrisk wrote:
> Val,
>
> I'm just updating the mount(2) man page for MS_RELATIME, and this is the
> text I've come up with:
>
>MS_RELATIME(Since Linux 2.6.20)
> When a file on this file system is accessed, only
>
On Sunday, 11 February 2007 00:20, Robert Hancock wrote:
> Nigel Cunningham wrote:
> > If your device requires power management, and you know it requires power
> > management, why not just implement power management? Doing -ENOSYS
> > instead is like saying -ESPAMMEBECAUSEIMLAZY.
> >
> > Let me pu
I've added this patch to the backlight git tree since it allows the
removal of a powermac specific hack to chipsfb_blank and fixes the
backlight class to work with drivers with no hardware blanking. Can
anyone see any problems with this?
The backlight class wants notification whenever the consol
As mentioned previously, I've setup a backlight git tree at:
http://git.o-hand.com/?p=linux-rpurdie-backlight;a=shortlog;h=for-mm
(git://git.o-hand.com/linux-rpurdie-backlight)
A patch of the combined changes to mainline is:
http://www.rpsys.net/openzaurus/patches/git_backlight-r1.patch.gz
I've
On Thu, Feb 08, 2007 at 03:07:10PM -0800, Andrew Morton wrote:
>
> I'm getting fed up of holding onto hundreds of patches against subsystem
> trees, sending them over and over again seeing and nothing happen. I sent
> 242
> patches out to subsystem maintainers on Monday and look at what's s
On Sunday, 11 February 2007 00:45, Tilman Schmidt wrote:
> Am 10.02.2007 23:37 schrieb Nigel Cunningham:
> > If your device requires power management, and you know it requires power
> > management, why not just implement power management? Doing -ENOSYS
> > instead is like saying -ESPAMMEBECAUSEIMLA
On Thu, Feb 08, 2007 at 11:14:13AM -0500, William Cohen wrote:
> This past week I was playing around with that pahole tool
> (http://oops.ghostprotocols.net:81/acme/dwarves/) and looking at the
> size of various struct in the kernel. I was surprised by the size of
> the task_struct on x86_64, a
On Sat, Feb 10, 2007 at 05:14:13PM -0500, Tejun Heo wrote:
> Heiko Carstens wrote:
> >On Sat, Feb 10, 2007 at 12:43:16PM -0500, Tejun Heo wrote:
> \>> Heiko, how about this? Does it fix s390?
> >Unfortunately not. Now I get
> > CC lib/iomap.o
> >lib/iomap.c: In function 'devm_ioport_map_rele
On Thu, Feb 08, 2007 at 01:32:43PM -0800, [EMAIL PROTECTED] wrote:
>
> The patch titled
> rdmsr_on_cpu, wrmsr_on_cpu
> has been removed from the -mm tree. Its filename was
> rdmsr_on_cpu-wrmsr_on_cpu.patch
>
> This patch was dropped because I've lost the plot on this thing
Alex
On Sat, Feb 10, 2007 at 10:50:33PM +, Al Viro wrote:
> We don't even require ioremap(). What the hell could it possibly mean on
> e.g. UML? The same goes for DMA. And yes, of course it means that a lot
> of drivers are not buildable on it - hardly a surprise, that...
FWIW, the current pictu
I have recently been investigating why we reprogram ioapic irqs in the
interrupt handler, because it significantly complicates the code, and
makes things more fragile. Eventually I found the commit with the
justification, see below.
There are not enough details in the justification to really und
Am 10.02.2007 07:43 schrieb Willy Tarreau:
> On Fri, Feb 09, 2007 at 07:25:34PM -0500, Jeff Garzik wrote:
On Sat, 2007-02-10 at 08:57 +1100, Nigel Cunningham wrote:
> Can we start to NAK new drivers that don't have proper power management
> implemented?
[...]
>> Certainly we should as
Am 10.02.2007 23:37 schrieb Nigel Cunningham:
> If your device requires power management, and you know it requires power
> management, why not just implement power management? Doing -ENOSYS
> instead is like saying -ESPAMMEBECAUSEIMLAZY.
Like it or not, power management is far from trivial, and pe
Nigel Cunningham wrote:
If your device requires power management, and you know it requires power
management, why not just implement power management? Doing -ENOSYS
instead is like saying -ESPAMMEBECAUSEIMLAZY.
Let me put it another way: People keep talking about Linux being ready
for the desktop
On Sat, Feb 10, 2007 at 12:53:51PM -0500, Pavel Roskin wrote:
> Quoting "John W. Linville" <[EMAIL PROTECTED]>:
>
> > > Very cool! Is it likely that d80211 and iwlwifi will be pushed into
> > > mainline in time for 2.6.21?
> >
> > Hmmm...I think we need to spend a cycle or so in -mm. 2.6.22 seem
On Sat, Feb 10, 2007 at 02:25:53PM -0800, Linus Torvalds wrote:
>
>
> On Sat, 10 Feb 2007, Tejun Heo wrote:
> >
> > I think an arch needs to support ioport_map/unmap and noncoherent dma (just
> > alias to coherent interface on x86/amd64) interface whether PCI is
> > implemented
> > or not. No?
From: Randy Dunlap <[EMAIL PROTECTED]>
Fix kernel-doc warnings and errors in USB.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
---
Documentation/DocBook/gadget.tmpl |4 ++--
Documentation/DocBook/usb.tmpl|6 +++---
drivers/usb/core/driver.c |1 +
3 files changed, 6 ins
From: Randy Dunlap <[EMAIL PROTECTED]>
Fix kernel-doc warnings in PCI, sysfs, and kobject files.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
---
drivers/pci/pci-driver.c |1 +
drivers/pci/pci.c|2 +-
fs/sysfs/file.c |2 +-
lib/kobject.c|1 +
4 fil
From: Randy Dunlap <[EMAIL PROTECTED]>
Fix kernel-doc warnings in IRQ management.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
---
include/linux/irq.h |1 +
kernel/irq/chip.c |2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
--- linux-2.6.20-git6.orig/include/linux/irq.h
+++ l
On Sat, 2007-02-10 at 03:31 +0100, Nick Piggin wrote:
> SetNewPageUptodate does not do the S390 page_test_and_clear_dirty, so
> I'd like to make sure that's OK.
An I/O operation on s390 will set the dirty bit for a page. That is the
reason to have SetPageUptodate clear the per page dirty bit when
Hi.
On Sat, 2007-02-10 at 23:20 +0100, Rafael J. Wysocki wrote:
> Hi,
>
> On Saturday, 10 February 2007 20:38, Pavel Machek wrote:
> > Hi!
> >
> > > > I don't think this is already done (feel free to correct me if I'm
> > > > wrong)..
> > > >
> > > > Can we start to NAK new drivers that don't h
On Sat, Feb 10, 2007 at 10:58:58AM +0100, Heiko Carstens wrote:
> Alasdair, is dm already fixed or is there any chance that it will
> ever get fixed?
I still expect us to get this changed within the next few months. We've
dealt with the changes necessary to the crypt target for this. The final
p
On Sat, 10 Feb 2007, Tejun Heo wrote:
>
> I think an arch needs to support ioport_map/unmap and noncoherent dma (just
> alias to coherent interface on x86/amd64) interface whether PCI is implemented
> or not. No?
We haven't required ioport implementations in the past, afaik.
L
Hi,
On 10/02/07, Patrick Ale <[EMAIL PROTECTED]> wrote:
And again, for something completely different.
I am hammering my second machine now
You may want to use autotest
http://test.kernel.org/autotest
Patrick
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group (PL)
(h
Hi,
On Saturday, 10 February 2007 20:38, Pavel Machek wrote:
> Hi!
>
> > > I don't think this is already done (feel free to correct me if I'm
> > > wrong)..
> > >
> > > Can we start to NAK new drivers that don't have proper power management
> > > implemented? There really is no excuse for writin
Heiko Carstens wrote:
On Sat, Feb 10, 2007 at 12:43:16PM -0500, Tejun Heo wrote:
\>> Heiko, how about this? Does it fix s390?
Unfortunately not. Now I get
CC lib/iomap.o
lib/iomap.c: In function 'devm_ioport_map_release':
lib/iomap.c:270: warning: implicit declaration of function 'iop
And again, for something completely different.
I am hammering my second machine now, a cool Siemens/Fujitsu laptop
(named elisabeth) with ICH7 ATA chipset and controller.
Currently the ATA controller is in "SATA" mode (ICH7 chipsets allow
you to run in native SATA mode or compatible mode, for th
Hello,
> This looks like the problems that hopefully the patches from Tejun and
> from Mark Lord cured (the delay after reset and the task file clear)
Any chance I can find this patch(es) and try them ?
> > Also, I've seen a :
> >
> > ata1: Spurious SDB FIS during NCQ issue=0x0 SAct=0x7ff8001f
Hi!
> > I don't think this is already done (feel free to correct me if I'm
> > wrong)..
> >
> > Can we start to NAK new drivers that don't have proper power management
> > implemented? There really is no excuse for writing a new driver and not
> > putting .suspend and .resume methods in anymore,
Ken Chen writes:
> So any error value returned from invalidate_inode_pages2_range() has
> to be taken seriously in the direct IO submit path instead of dropping
> it to the floor.
If invalidate_inode_pages2_range() will return EIOCBRETRY as the patch
"aio: fix kernel bug when page is temporally b
net/ipv4/ipvs/ip_vs_core.c
module_exit
ip_vs_cleanup
ip_vs_control_cleanup
cancel_rearming_delayed_work
// done
This is unsafe. The module may be unloaded and the memory may be freed while
defense_work's handler is still running/pree
Currently typeof(delayed_work->work.data) is
"struct workqueue_struct" when the timer is pending
"struct cpu_workqueue_struct" whe the work is queued
This makes impossible to use flush_fork(delayed_work->work) in addition
to cancel_delayed_work/cancel_rearming_delayed_work, not g
Change queue_delayed_work() to use queue_delayed_work_on() to avoid the code
duplication (saves 133 bytes).
Q: queue_delayed_work() enqueues &dwork->work directly when delay == 0, why?
Signed-off-by: Oleg Nesterov <[EMAIL PROTECTED]>
--- 6.20-rc6-mm3/kernel/workqueue.c~2_factor2007-02-10 18:
Andrew, unless you stop me right now, I am going to send the following
patches in addition:
[PATCH] kill cancel_rearming_delayed_workqueue()
cancel_rearming_delayed_workqueue(wq, dwork) does not
need the first parameter, it could be figured out from
Hi,
The generic HID layer changes introduced an endianness bug for USB HID
devices.
The USB vendor and product IDs are not byteswapped appropriately, and
thus come out in the wrong endianness when fetched through the evdev
using ioctl() on big endian platforms.
This byteswapping used to be done
On Sat, 10 Feb 2007 19:32:30 +0200 "S.Çağlar Onur" <[EMAIL PROTECTED]> wrote:
> Hi;
>
> 31 Oca 2007 Çar tarihinde, [EMAIL PROTECTED] şunları yazmıştı:
> > The patch titled
> > kvm: Fix asm constraint for lldt instruction
> > has been added to the -mmtree. Its filename is
> > kvm-fix-
On Sat, 10 Feb 2007, Linus Torvalds wrote:
> On Sat, 10 Feb 2007, Davide Libenzi wrote:
> >
> > For the queue approach, I meant the async_submit() to simply add the
> > request (cookie, syscall number and params) inside queue, and not trying
> > to execute the syscall. Once you're inside schedu
James Bottomley wrote:
On Sat, 2007-02-10 at 18:46 +0100, Richard Knutsson wrote:
Convert:
FALSE -> false
TRUE -> true
Actually, downcasing true and false in this driver is pretty much a
retrograde step. The reason for their being uppercased is that they
represent constants (and uppe
Hi,
i upgraded my system from ubuntu edgy to feisty and a new kernel came with it
(2.6.15 vs. 2.6.20). Sadly my wireless card (pcmcia) has stopped working
under this system. Seeing a backttrace in the dmesg output made me believe
it's a kernel problem. I built a vanilla kernel to see if maybe
On Fri, Feb 09, 2007 at 09:22:48PM -0500, Lee Revell wrote:
> On 2/9/07, Nigel Cunningham <[EMAIL PROTECTED]> wrote:
> >On Fri, 2007-02-09 at 20:59 -0500, Lee Revell wrote:
> >> On 2/9/07, Robert Hancock <[EMAIL PROTECTED]> wrote:
> >> > I would disagree that it's a peripheral issue, it's pretty co
James Bottomley wrote:
On Sat, 2007-02-10 at 18:46 +0100, Richard Knutsson wrote:
Convert:
FALSE -> false
TRUE -> true
Actually, downcasing true and false in this driver is pretty much a
retrograde step. The reason for their being uppercased is that they
represent constants (and uppe
On 2/10/07, Alan <[EMAIL PROTECTED]> wrote:
Right umm "Your honor the gentleman is human, this is not acceptable" ?
Human and a looney who wishes Monty Python's Flying Circus still
existed so he could be a main character and having a great excuse to
act weird.
Beating the crap out of it usi
> OK, rebooting again, with a new root device as /dev/sde1...
> No problem for the old IDE devices, they are now /dev/sdX.
>
> But the Jmicron stuff is still broken though no more conflict :(
Thanks. That helps a lot as it narrows it down
>
> PCI: Enabling device :02:00.1 ( -> 0001)
> A
> > libsata == libata ?
> I don't think there is a seperate libata, it's all put under libsata
> if I understand the working correctly (Alan, don't sue me if I am
> wrong).
Right umm "Your honor the gentleman is human, this is not acceptable" ?
It is in drivers/ata the files are libata-* so it's
On 2/10/07, Randy Dunlap <[EMAIL PROTECTED]> wrote:
Hi,
What are the libsata tests and where are they, please?
No where, I just compile the drivers, see if my system boots up and
then I run some I/O intensive stuff, like bonnie++, emerge -e world at
the same time.
So you are testing libata
Hi Alan,
> You have the old driver 0n 0x1F0
>
>
> > PCI: Device :02:00.0 not available because of resource
> collisions
> > ahci: probe of :02:00.0 failed with error -22
> > ACPI: PCI Interrupt :00:1f.1[A] -> GSI 22 (level, low) -> IRQ 22
> > ata: 0x1F0 IDE port busy
>
> And the ne
On Saturday, 10 February 2007 18:52, Daniel Barkalow wrote:
> On Sat, 10 Feb 2007, Rafael J. Wysocki wrote:
>
> > On Saturday, 10 February 2007 11:02, Nigel Cunningham wrote:
> >
> > > Well, the original desire was to stop new drivers getting in without
> > > proper power management.
> >
> > I kn
Andrew, Daniel who reported the crash has tested this patch and says that it
works fine avoiding it, so you can merge.
drivers-add-lcd-support-fix-crash-when-built-in-and-no-parport-present.patch
Signed-off-by: Miguel Ojeda Sandonis <[EMAIL PROTECTED]>
---
diff --git a/drivers/auxdisplay/cfag1286
On Sat, Feb 10, 2007 at 12:43:16PM -0500, Tejun Heo wrote:
> devres iomap made lib/iomap.c always built and added several
> arch-indep PCI routines to include/linux/io.h and lib/iomap.c without
> wrapping them inside CONFIG_PCI. This breaks configurations where PCI
> is not configured. Wrap pci_i
Hi!
My schoolmate got this while using kvm-12 on 2.6.20-rc6:
http://www.fi.muni.cz/~xslaby/sklad/kvm-intel-panic/a/
Unfortunately it's only shots taken by camera. If we are able to reproduce it in
2.6.20, we'll grab netconsole output.
regards,
--
http://www.fi.muni.cz/~xslaby/Jiri
On Sat, 10 Feb 2007 17:22:28 +0100 Patrick Ale wrote:
> Hi,
>
> And now for something completely different.
>
> I started the libsata tests on one of the four machines I'll be doing
> these tests on.
Hi,
What are the libsata tests and where are they, please?
> At the moment I'm testing on 'lil
Am Samstag, 10. Februar 2007 17:59 schrieb Thibaud Hulin:
> Thanks. In effect, I already post this question in the ndiswrapper list.
> So, they told me that was a problem of USB and of kernel. Then, I'm
> looking for configuration of the kernel, because I compiled the 2.6.19,
> but I no more suc
> If invalidate_inode_pages2_range() says it can not invalidate pages,
> while dio to the same file offset range is in flight, something is
> really wrong there.
If invalidate_inode_pages2_range() says it can not invalidate pages
It means that soft_irq does completing IO now on other cpu.
Next ret
On Sat, 10 Feb 2007, Linus Torvalds wrote:
>
> But that makes it impossible to do things synchronously, which I think is
> a *major* mistake.
>
> The whole (and really _only_) point of my patch was really the whole
> "synchronous call" part. I'm personally of the opinion that if you cannot
>
[ohci1394_early]
Some remarks to the September 2006 version at
http://www.suse.de/~bk/firewire/ :
- Seems its .remove won't work properly if more than one OHCI-1394
controller is installed. And it's .probe isn't reentrant, but that
might be less of a problem.
- Its functionality will
Fixes http://bugzilla.kernel.org/show_bug.cgi?id=7810 - a silly
copy-paste bug introduced by the latest change.
Signed-off-by: Gerhard Dirschl <[EMAIL PROTECTED]>
---
Maybe it fixes http://bugzilla.kernel.org/show_bug.cgi?id=7910
as well.
diff --git a/drivers/block/pktcdvd.c b/drivers/block/pktcd
On Sat, 10 Feb 2007, Davide Libenzi wrote:
>
> For the queue approach, I meant the async_submit() to simply add the
> request (cookie, syscall number and params) inside queue, and not trying
> to execute the syscall. Once you're inside schedule, "stuff" has already
> partially happened, and y
On Sat, 10 Feb 2007 19:39:21 +0100
"Paul Rolland" <[EMAIL PROTECTED]> wrote:
> > I've been trying this, but I ended with the ICH7 not detecting anymore
> > my IDE disks...
> > Should try again, maybe I missed something.
>
> Done a new built, and I now have :
>
> Uniform Multi-Platform E-IDE dri
On Fri, 9 Feb 2007, Linus Torvalds wrote:
> > Another, even simpler way IMO, is to just have a plain per-task kthread
> > pool, and a queue.
>
> Yes, that is actually quite doable with basically the same interface. It's
> literally a "small decision" inside of "schedule_async()" on how it
> ac
On Saturday 10 February 2007 17:22, Theodore Tso wrote:
> On Fri, Feb 09, 2007 at 01:12:42PM -0800, James Ketrenos wrote:
> > Please hold all questions until I am done with this email. Thank you.
> >
> > We are pleased to announce the availability of a new driver for the
> > Intel PRO/Wireless 3
1 - 100 of 244 matches
Mail list logo
