Re: 2.6.20-rc4-mm1: different values for OHCI_QUIRK_ZFMICRO

2007-03-30 Thread Tony Olech
ECTED]>; "Geoff Levand" <[EMAIL PROTECTED]>; "Greg Kroah-Hartman" <[EMAIL PROTECTED]>; "Tony Olech" <[EMAIL PROTECTED]>; ; Sent: Thursday, March 29, 2007 11:06 PM Subject: Re: 2.6.20-rc4-mm1: different values for OHCI_QUIRK_ZFMICRO On Tue

Re: 2.6.20-rc4-mm1: different values for OHCI_QUIRK_ZFMICRO

2007-03-29 Thread David Brownell
On Thursday 29 March 2007 3:06 pm, Randy Dunlap wrote: > On Tue, 20 Feb 2007 01:06:54 +0100 Adrian Bunk wrote: > > > On Sun, Jan 14, 2007 at 06:36:10AM -0800, David Brownell wrote: > > > On Sunday 14 January 2007 1:10 am, Adrian Bunk wrote: > > > > <-- snip --> > > > > > > Waiting for Tony to s

Re: 2.6.20-rc4-mm1: different values for OHCI_QUIRK_ZFMICRO

2007-03-29 Thread Randy Dunlap
> > Still unfixed as of 2.6.20-mm1. > > > > ... > > > CC drivers/usb/misc/ftdi-elan.o > > > /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/usb/misc/ftdi-elan.c:2307:1: > > > warning: "OHCI_QUIRK_ZFMICRO" redefined > >

Re: 2.6.20-rc4-mm1: PCI=n: drivers/net/3c59x.c compile error

2007-03-09 Thread Tejun Heo
Hello, Randy Dunlap wrote: >> Erm, before I do that, could somebody explain what >> >> #define HAVE_PCI_REQ_REGIONS 2 >> >> accompanying their declaration is for? I have't found any references to it >> in >> the source. Should I duplicate it for CONFIG_PCI=n case (I guess not)? > > I wouldn

Re: 2.6.20-rc4-mm1: PCI=n: drivers/net/3c59x.c compile error

2007-03-06 Thread Randy Dunlap
t;>>>><-- snip --> > > >>>>>>>... > >>>>>>> CC drivers/net/3c59x.o > >>>>>>>/home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/net/3c59x.c: > >>>>>>>In function 'vortex_init

Re: 2.6.20-rc4-mm1: PCI=n: drivers/net/3c59x.c compile error

2007-03-06 Thread Sergei Shtylyov
Hello. Greg KH wrote: 3x59x-fix-pci-resource-management.patch causes the following compile error with CONFIG_PCI=n: <-- snip --> ... CC drivers/net/3c59x.o /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/net/3c59x.c: In function 'vortex_init_one':

Re: 2.6.20-rc4-mm1: PCI=n: drivers/net/3c59x.c compile error

2007-02-26 Thread Greg KH
;> error with CONFIG_PCI=n: > > > > >>>> <-- snip --> > > > > >>>> ... > > >>>> CC drivers/net/3c59x.o > > >>>> /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/net/3c59x.c: > > >

Re: 2.6.20-rc4-mm1: PCI=n: drivers/net/3c59x.c compile error

2007-02-26 Thread Randy Dunlap
t;> ... > >>>> CC drivers/net/3c59x.o > >>>> /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/net/3c59x.c: > >>>> In function 'vortex_init_one': > >>>> /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/ne

Re: 2.6.20-rc4-mm1: PCI=n: drivers/net/3c59x.c compile error

2007-02-26 Thread Sergei Shtylyov
Hello, I wrote: 3x59x-fix-pci-resource-management.patch causes the following compile error with CONFIG_PCI=n: <-- snip --> ... CC drivers/net/3c59x.o /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/net/3c59x.c: In function 'vortex_init_one': /home/bunk/

Re: 2.6.20-rc4-mm1: different values for OHCI_QUIRK_ZFMICRO

2007-02-19 Thread Adrian Bunk
b/misc/ftdi-elan.o > > /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/usb/misc/ftdi-elan.c:2307:1: > > warning: "OHCI_QUIRK_ZFMICRO" redefined > > In file included from > > /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/usb/misc/ftdi-elan.c:7

Re: 2.6.20-rc4-mm1: PCI=n: drivers/net/3c59x.c compile error

2007-02-17 Thread Sergei Shtylyov
Hello. Sergei Shtylyov wrote: 3x59x-fix-pci-resource-management.patch causes the following compile error with CONFIG_PCI=n: <-- snip --> ... CC drivers/net/3c59x.o /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/net/3c59x.c: In function 'vortex_init_one&#

Re: 2.6.20-rc4-mm1: PCI=n: drivers/net/3c59x.c compile error

2007-02-17 Thread Sergei Shtylyov
Hello, I wrote: 3x59x-fix-pci-resource-management.patch causes the following compile error with CONFIG_PCI=n: <-- snip --> ... CC drivers/net/3c59x.o /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/net/3c59x.c: In function 'vortex_init_one': /home/bunk/

Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption

2007-02-01 Thread Zan Lynx
On Thu, 2007-02-01 at 18:54 +0300, Edward Shishkin wrote: [snip] > Thanks for the dump. > > >[ 3138.456588] [] current_atom_finish_all_fq+0x12e/0x280 > >[ 3138.456661] [] autoremove_wake_function+0x0/0x30 > >[ 3138.456674] [] submit_wb_list+0x11c/0x130 > >[ 3138.456690] [] reiser4_txn_end+0x34

Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption

2007-02-01 Thread Edward Shishkin
Zan Lynx wrote: On Sat, 2007-01-20 at 03:34 +0300, Vladimir V. Saveliev wrote: Hello On Friday 19 January 2007 20:58, Zan Lynx wrote: I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1 and rc4-mm1 have been giving me these freezes. They were happening inside X and

Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption

2007-01-24 Thread Vince
Vladimir V. Saveliev wrote: Hello On Tuesday 23 January 2007 10:38, Vince wrote: [...] I don't know if it is related, but I've had the following BUG on 2.6.20-rc4-mm1 (+ hot-fixes patches applied) : --- kernel BUG at fs/reiser4/plugin/item/extent_file_ops.c:973!

Re: 2.6.20-rc4-mm1: PCI=n: drivers/net/3c59x.c compile error

2007-01-24 Thread Sergei Shtylyov
Hello. Adrian Bunk wrote: 3x59x-fix-pci-resource-management.patch causes the following compile error with CONFIG_PCI=n: <-- snip --> ... CC drivers/net/3c59x.o /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/net/3c59x.c: In function 'vortex_init_one':

2.6.20-rc4-mm1: PCI=n: drivers/net/3c59x.c compile error

2007-01-24 Thread Adrian Bunk
3x59x-fix-pci-resource-management.patch causes the following compile error with CONFIG_PCI=n: <-- snip --> ... CC drivers/net/3c59x.o /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/net/3c59x.c: In function 'vortex_init_one': /home/bunk/linux/kernel-2.6/linu

Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption

2007-01-23 Thread Vladimir V. Saveliev
sible to get anything, > > plus I was reluctant to test it since the freeze sometimes requires a > > full fsck.reiser4 --build-fs to recover the filesystem. > > [...] > > Hi, > > I don't know if it is related, but I've had the fo

Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption

2007-01-22 Thread Vince
full fsck.reiser4 --build-fs to recover the filesystem. > [...] Hi, I don't know if it is related, but I've had the following BUG on 2.6.20-rc4-mm1 (+ hot-fixes patches applied) : --- kernel BUG at fs/reiser4/plugin/item/extent_file_ops.c:973! invalid opcode:

Re: `make htmldocs` fails -- 2.6.20-rc4-mm1

2007-01-22 Thread Don Mullis
n accurate description of what kernel tree has this problem? > It's not 2.6.19. It's not 2.6.20-rc5. 2.6.20-rc4-mm1, sorry. Forgot that posting as a reply to the 2.6.20-rc4-mm1 announcement is no help for someone receiving the mail directly. - To unsubscribe from this list: send

2.6.20-rc4-mm1 aio bug

2007-01-21 Thread Michal Piotrowski
Hi, I get this while running aiostress. Jan 22 01:50:05 black-mamba kernel: === Jan 22 01:50:05 black-mamba kernel: [ INFO: possible circular locking dependency detected ] Jan 22 01:50:05 black-mamba kernel: 2.6.20-rc4-mm1 #1 Jan 22 01:50:05

Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption

2007-01-19 Thread Vladimir V. Saveliev
Hello On Friday 19 January 2007 20:58, Zan Lynx wrote: > I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1 > and rc4-mm1 have been giving me these freezes. They were happening > inside X and without external console it was impossible to get anything, > plus I was reluctant to

Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption

2007-01-19 Thread Edward Shishkin
Zan Lynx wrote: I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1 and rc4-mm1 have been giving me these freezes. I didn't investigate it in details yet, other file systems also freeze for me: http://marc.theaimsgroup.com/?l=linux-kernel&m=116809282829254&w=2 They were

linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption

2007-01-19 Thread Zan Lynx
I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1 and rc4-mm1 have been giving me these freezes. They were happening inside X and without external console it was impossible to get anything, plus I was reluctant to test it since the freeze sometimes requires a full fsck.reiser4

Re: [BUG] 2.6.20-rc4-mm1: Panic in e1000_write_vfta_82543()

2007-01-18 Thread Auke Kok
Sukadev Bhattiprolu wrote: I get following panic on 2.6.20-rc4-mm1 on a 2-cpu AMD Opteron system. Same basic config file seems to work with 2.6.20-rc2-mm1 on this same system. Have not tried -rc3-mm1 yet. Attached are config file and "lspci -vv" output. Let me know if you need more i

Re: [BUG] 2.6.20-rc4-mm1: Panic in e1000_write_vfta_82543()

2007-01-18 Thread Sukadev Bhattiprolu
Auke Kok [EMAIL PROTECTED] wrote: | Sukadev Bhattiprolu wrote: | >I get following panic on 2.6.20-rc4-mm1 on a 2-cpu AMD Opteron system. | > | >Same basic config file seems to work with 2.6.20-rc2-mm1 on this same | >system. Have not tried -rc3-mm1 yet. | > | >Attached are conf

[BUG] 2.6.20-rc4-mm1: Panic in e1000_write_vfta_82543()

2007-01-18 Thread Sukadev Bhattiprolu
I get following panic on 2.6.20-rc4-mm1 on a 2-cpu AMD Opteron system. Same basic config file seems to work with 2.6.20-rc2-mm1 on this same system. Have not tried -rc3-mm1 yet. Attached are config file and "lspci -vv" output. Let me know if you need more info. Suka --- [ 168.92584

Re: [PATCH: 2.6.20-rc4-mm1] JFS: Avoid deadlock introduced by explicit I/O plugging

2007-01-18 Thread Dave Kleikamp
On Thu, 2007-01-18 at 01:30 -0500, Josef Sipek wrote: > On Wed, Jan 17, 2007 at 04:55:49PM -0600, Dave Kleikamp wrote: > > /* > > * jfs_lock.h > > @@ -42,6 +43,7 @@ do { > > \ > > if (cond) \ > >

Re: [PATCH: 2.6.20-rc4-mm1] JFS: Avoid deadlock introduced by explicit I/O plugging

2007-01-17 Thread Josef Sipek
On Wed, Jan 17, 2007 at 04:55:49PM -0600, Dave Kleikamp wrote: ... > diff -Nurp linux-2.6.20-rc4-mm1/fs/jfs/jfs_lock.h linux/fs/jfs/jfs_lock.h > --- linux-2.6.20-rc4-mm1/fs/jfs/jfs_lock.h2006-11-29 15:57:37.0 > -0600 > +++ linux/fs/jfs/jfs_lock.h 2007-01-17 15:30:19.000

Re: [PATCH: 2.6.20-rc4-mm1] JFS: Avoid deadlock introduced by explicit I/O plugging

2007-01-17 Thread Dave Kleikamp
On Thu, 2007-01-18 at 10:46 +1100, Jens Axboe wrote: > On Wed, Jan 17 2007, Dave Kleikamp wrote: > > On Thu, 2007-01-18 at 10:18 +1100, Jens Axboe wrote: > > > > > Can you try io_schedule() and verify that things just work? > > > > I actually did do that in the first place, but wondered if it was t

Re: [PATCH: 2.6.20-rc4-mm1] JFS: Avoid deadlock introduced by explicit I/O plugging

2007-01-17 Thread Jens Axboe
On Wed, Jan 17 2007, Dave Kleikamp wrote: > On Thu, 2007-01-18 at 10:18 +1100, Jens Axboe wrote: > > > Can you try io_schedule() and verify that things just work? > > I actually did do that in the first place, but wondered if it was the > right thing to introduce the accounting changes that came

Re: [PATCH: 2.6.20-rc4-mm1] JFS: Avoid deadlock introduced by explicit I/O plugging

2007-01-17 Thread Dave Kleikamp
On Thu, 2007-01-18 at 10:18 +1100, Jens Axboe wrote: > Can you try io_schedule() and verify that things just work? I actually did do that in the first place, but wondered if it was the right thing to introduce the accounting changes that came with that. I'll change it back to io_schedule() and te

Re: [PATCH: 2.6.20-rc4-mm1] JFS: Avoid deadlock introduced by explicit I/O plugging

2007-01-17 Thread Jens Axboe
On Wed, Jan 17 2007, Dave Kleikamp wrote: > Jens, > Can you please take a look at this patch, and if you think it's sane, > add it to your explicit i/o plugging patchset? Would it make sense in > any of these paths to use io_schedule() instead of schedule()? I'm glad you bring that up, actually.

[PATCH: 2.6.20-rc4-mm1] JFS: Avoid deadlock introduced by explicit I/O plugging

2007-01-17 Thread Dave Kleikamp
d it. Signed-off-by: Dave Kleikamp <[EMAIL PROTECTED]> diff -Nurp linux-2.6.20-rc4-mm1/fs/jfs/jfs_lock.h linux/fs/jfs/jfs_lock.h --- linux-2.6.20-rc4-mm1/fs/jfs/jfs_lock.h 2006-11-29 15:57:37.0 -0600 +++ linux/fs/jfs/jfs_lock.h 2007-01-17 15:30:19.0 -0600 @@ -22,6 +22

Re: 2.6.20-rc4-mm1 - cvs merge whoops in git-ioat.patch?

2007-01-17 Thread Andrew Morton
> On Wed, 17 Jan 2007 16:09:41 -0500 [EMAIL PROTECTED] wrote: > commit d8238afa7eedc047b57da7ec98e98fb051fc4e85 > Author: Chris Leech <[EMAIL PROTECTED]> > Date: Fri Nov 17 11:37:29 2006 -0800 > > I/OAT: Add documentation for the tcp_dma_copybreak sysctl > > Signed-off-by: Chris Leech <

2.6.20-rc4-mm1 - cvs merge whoops in git-ioat.patch?

2007-01-17 Thread Valdis . Kletnieks
commit d8238afa7eedc047b57da7ec98e98fb051fc4e85 Author: Chris Leech <[EMAIL PROTECTED]> Date: Fri Nov 17 11:37:29 2006 -0800 I/OAT: Add documentation for the tcp_dma_copybreak sysctl Signed-off-by: Chris Leech <[EMAIL PROTECTED]> looks fishy, like a cvs update went bad: diff -puN Docu

Re: 2.6.20-rc4-mm1 USB (asix) problem

2007-01-17 Thread Eric Buddington
On Wed, Jan 17, 2007 at 07:00:48AM -0500, David Hollis wrote: > > 'rmmod asix' takes a really long time (45-80s) with any setting, and > > sometimes coincides with ksoftirqd pegging (99.9% CPU) for several > > seconds. > > This I haven't seen before. Does it occur even when the device is able > t

Re: 2.6.20-rc4-mm1 USB (asix) problem

2007-01-17 Thread David Hollis
On Tue, 2007-01-16 at 17:59 -0500, Eric Buddington wrote: > On Mon, Jan 15, 2007 at 08:32:17PM +, David Hollis wrote: > > Interesting. It would really be something if your devices happen to > > work better with 0. Wouldn't make much sense at all unfortunately. If > > 0 works, could you also

Re: 2.6.20-rc4-mm1 USB (asix) problem

2007-01-16 Thread Eric Buddington
On Mon, Jan 15, 2007 at 08:32:17PM +, David Hollis wrote: > Interesting. It would really be something if your devices happen to > work better with 0. Wouldn't make much sense at all unfortunately. If > 0 works, could you also try setting it to 2 or 3? The PHY select value > is a bit field w

Re: 2.6.20-rc4-mm1

2007-01-15 Thread Jens Axboe
On Mon, Jan 15 2007, Ingo Molnar wrote: > > * Jens Axboe <[EMAIL PROTECTED]> wrote: > > > > In a previous write invoked by: fsck.ext3(1896): WRITE block 8552 on > > > sdb1 end_buffer_async_write() is invoked. > > > > > > sdb1 is not a part of a raid device. > > > > When I briefly tested this b

Re: 2.6.20-rc4-mm1 USB (asix) problem

2007-01-15 Thread David Hollis
On Mon, 2007-01-15 at 14:50 -0500, Eric Buddington wrote: > The asix_write_cmd argument in question did indeed change from 0 to 1 > between 2.6.20-rc3-mm1 and -rc4-mm1. I'll change it back, rebuild, > and test. Probably tomorrow. > Interesting. It would really be something if your devices happe

Re: 2.6.20-rc4-mm1 USB (asix) problem

2007-01-15 Thread David Hollis
On Sat, 2007-01-13 at 15:31 -0500, Eric Buddington wrote: > The following problem occured on an Athlon64 X2 under 2.6.20-rc4-mm1, > but not 2.6.20-rc3-mm1. > > I'm using two D-Link DUB-E100 USB ethernet adapters, using the 'asix' > driver. When I upgraded to 2

Re: 2.6.20-rc4-mm1 USB (asix) problem

2007-01-15 Thread Eric Buddington
On Mon, Jan 15, 2007 at 07:27:56PM +, David Hollis wrote: > Do you happen to have a Rev. B1 DLink adapter? If so, the only change > that was put in (PHY Select fix) should actually make these devices > work. Can you check the top of the ax88772_bind() call in your file and > see if it has thi

Re: 2.6.20-rc4-mm1: status of sn9c102_pas202bca?

2007-01-15 Thread Mauro Carvalho Chehab
Hi Adrian, Em Sáb, 2007-01-13 às 08:27 +0100, Adrian Bunk escreveu: > On Thu, Jan 11, 2007 at 10:26:27PM -0800, Andrew Morton wrote: > >... > > Changes since 2.6.20-rc3-mm1: > >... > > git-dvb.patch > >... > > git trees > >... > > drivers/media/video/sn9c102/sn9c102_pas202bca.c is no longer us

Re: 2.6.20-rc4-mm1

2007-01-15 Thread Ingo Molnar
* Jens Axboe <[EMAIL PROTECTED]> wrote: > > In a previous write invoked by: fsck.ext3(1896): WRITE block 8552 on > > sdb1 end_buffer_async_write() is invoked. > > > > sdb1 is not a part of a raid device. > > When I briefly tested this before I left (and found it broken), doing > a cat /proc/m

Re: 2.6.20-rc4-mm1 md problem

2007-01-15 Thread Thomas Gleixner
On Mon, 2007-01-15 at 08:17 +0100, Ingo Molnar wrote: > > Debug plan: > > - revert md-* patches > > - binary search > > > > Does someone have a better idea? > > Thomas saw something similar yesterday and he the partial results that > git.block (between rc2-mm1 and rc4-mm1) breaks certain disk dr

Re: 2.6.20-rc4-mm1 md problem

2007-01-14 Thread Ingo Molnar
* Michal Piotrowski <[EMAIL PROTECTED]> wrote: > My system hangs on this > http://www.stardust.webpages.pl/files/tbf/euridica/2.6.20-rc4-mm1/bug2.jpg > http://www.stardust.webpages.pl/files/tbf/euridica/2.6.20-rc4-mm1/mm-config > > Debug plan: > - revert md-* patches >

Re: i810fb fails to load (was: 2.6.20-rc4-mm1)

2007-01-14 Thread Andrew Morton
> On Mon, 15 Jan 2007 00:52:36 +0100 Tilman Schmidt <[EMAIL PROTECTED]> wrote: > With kernel 2.6.20-rc4-mm1 and all hotfixes, i810fb fails to load on my > Dell Optiplex GX110. Here's an excerpt of the diff between the boot logs > of 2.6.20-rc5 (working) and 2.6.

Re: 2.6.20-rc4-mm1

2007-01-14 Thread Jens Axboe
On Sun, Jan 14 2007, Thomas Gleixner wrote: > On Sun, 2007-01-14 at 11:46 +0100, Thomas Gleixner wrote: > > > Boot proceeds, but gets stuck hard at: > > > "Remounting root filesystem in read-write mode:" > > > > > > No SysRq-T, nothing. > > > > > > The above BUG seems unrelated to that. Investiga

i810fb fails to load (was: 2.6.20-rc4-mm1)

2007-01-14 Thread Tilman Schmidt
With kernel 2.6.20-rc4-mm1 and all hotfixes, i810fb fails to load on my Dell Optiplex GX110. Here's an excerpt of the diff between the boot logs of 2.6.20-rc5 (working) and 2.6.20-rc4-mm1 (non-working): @@ -4,7 +4,7 @@ No module symbols loaded - kernel modules not enabled. klogd 1.4.1

Re: 2.6.20-rc4-mm1

2007-01-14 Thread Jens Axboe
On Sun, Jan 14 2007, Thomas Gleixner wrote: > On Mon, 2007-01-15 at 09:05 +1100, Jens Axboe wrote: > > raid seems to have severe problems with the plugging change. I'll try > > and find Neil and have a chat with him, hopefully we can work it out. > > Some hints: > > mount(1899): WRITE block 16424

Re: 2.6.20-rc4-mm1

2007-01-14 Thread Thomas Gleixner
On Mon, 2007-01-15 at 09:05 +1100, Jens Axboe wrote: > raid seems to have severe problems with the plugging change. I'll try > and find Neil and have a chat with him, hopefully we can work it out. Some hints: mount(1899): WRITE block 16424 on md3 call md_write_start md3_raid1(438): WRITE block 40

Re: 2.6.20-rc4-mm1 md problem

2007-01-14 Thread Jens Axboe
t; My system hangs on this > >> > > >http://www.stardust.webpages.pl/files/tbf/euridica/2.6.20-rc4-mm1/bug2.jpg > >> > > >http://www.stardust.webpages.pl/files/tbf/euridica/2.6.20-rc4-mm1/mm-config > >> > > >> > Debug plan: > >> > - revert md-*

Re: 2.6.20-rc4-mm1

2007-01-14 Thread Jens Axboe
On Sun, Jan 14 2007, Thomas Gleixner wrote: > On Sun, 2007-01-14 at 11:46 +0100, Thomas Gleixner wrote: > > > Boot proceeds, but gets stuck hard at: > > > "Remounting root filesystem in read-write mode:" > > > > > > No SysRq-T, nothing. > > > > > > The above BUG seems unrelated to that. Investiga

Re: 2.6.20-rc4-mm1: different values for OHCI_QUIRK_ZFMICRO

2007-01-14 Thread David Brownell
On Sunday 14 January 2007 1:10 am, Adrian Bunk wrote: > <-- snip --> Waiting for Tony to submit bugfixes to his driver... > ... > CC drivers/usb/misc/ftdi-elan.o > /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/usb/misc/ftdi-elan.c:2307:1: > warning

Re: 2.6.20-rc4-mm1

2007-01-14 Thread Thomas Gleixner
On Sun, 2007-01-14 at 11:46 +0100, Thomas Gleixner wrote: > > Boot proceeds, but gets stuck hard at: > > "Remounting root filesystem in read-write mode:" > > > > No SysRq-T, nothing. > > > > The above BUG seems unrelated to that. Investigating further. > > Bisect identified: git-block.patch Doe

Re: 2.6.20-rc4-mm1

2007-01-14 Thread Thomas Gleixner
On Sun, 2007-01-14 at 10:48 +0100, Thomas Gleixner wrote: > ata_scsi_rbuf_get requests KM_IRQ0 type memory and calls kmap_atomic > with interrupts enabled. > > Boot proceeds, but gets stuck hard at: > "Remounting root filesystem in read-write mode:" > > No SysRq-T, nothing. > > The above BUG see

Re: 2.6.20-rc4-mm1

2007-01-14 Thread Thomas Gleixner
On Thu, 2007-01-11 at 22:26 -0800, Andrew Morton wrote: > - Merged the "filesystem AIO patches". Hotfixes alreday applied. BUG: at /home/tglx/work/kernel/vanilla/linux-2.6.20-rc4-mm1/arch/i386/mm/highmem.c:60 kmap_atomic() [] show_trace_log_lvl+0x1a/0x2f [] show_tr

2.6.20-rc4-mm1: different values for OHCI_QUIRK_ZFMICRO

2007-01-14 Thread Adrian Bunk
<-- snip --> ... CC drivers/usb/misc/ftdi-elan.o /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/usb/misc/ftdi-elan.c:2307:1: warning: "OHCI_QUIRK_ZFMICRO" redefined In file included from /home/bunk/linux/kernel-2.6/linux-2.6.20-rc4-mm1/drivers/usb/misc/ftdi-

2.6.20-rc4-mm1 USB (asix) problem

2007-01-13 Thread Eric Buddington
The following problem occured on an Athlon64 X2 under 2.6.20-rc4-mm1, but not 2.6.20-rc3-mm1. I'm using two D-Link DUB-E100 USB ethernet adapters, using the 'asix' driver. When I upgraded to 2.6.20-rc4-mm1, they were still recognized, but various ifconfig operations on them (up/do

2.6.20-rc4-mm1: status of sn9c102_pas202bca?

2007-01-12 Thread Adrian Bunk
On Thu, Jan 11, 2007 at 10:26:27PM -0800, Andrew Morton wrote: >... > Changes since 2.6.20-rc3-mm1: >... > git-dvb.patch >... > git trees >... drivers/media/video/sn9c102/sn9c102_pas202bca.c is no longer used or built but still shipped. cu Adrian -- "Is there not promise of rain?" Li

Re: Early ACPI lockup (was Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Frederik Deweerdt
> On Thu, Jan 11, 2007 at 10:26:27PM -0800, Andrew Morton wrote: > >>>>> > >>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc4-mm1/ > >>>>> > >>>> Hi, > >>>> > >>>

Re: Early ACPI lockup (was Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Jiri Slaby
Jiri Slaby wrote: >> On Fri, Jan 12, 2007 at 05:53:08PM -0500, Len Brown wrote: >>> What do you see if on failure you also print out the params, like below? [...] > ACPI: acpi_table_parse(17, ) HPET NULL handler! After re-enabling HPET, it disappeared. regards, -- http://www.fi.muni.cz/~

Re: Early ACPI lockup (was Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Michal Piotrowski
>>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc4-mm1/ >>>>> >>>> Hi, >>>> >>>> The git-acpi.patch replaces earlier "if(!handler) return -EINVAL" by >>>> "BUG_O

Re: Early ACPI lockup (was Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Jiri Slaby
inux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc4-mm1/ >>>> >>> Hi, >>> >>> The git-acpi.patch replaces earlier "if(!handler) return -EINVAL" by >>> "BUG_ON(!handler)". This locks my machine early at boot with a message >

Re: Early ACPI lockup (was Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Frederik Deweerdt
On Fri, Jan 12, 2007 at 05:53:08PM -0500, Len Brown wrote: > On Friday 12 January 2007 05:20, Frederik Deweerdt wrote: > > On Thu, Jan 11, 2007 at 10:26:27PM -0800, Andrew Morton wrote: > > > > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/p

Re: Early ACPI lockup (was Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Len Brown
On Friday 12 January 2007 05:20, Frederik Deweerdt wrote: > On Thu, Jan 11, 2007 at 10:26:27PM -0800, Andrew Morton wrote: > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc4-mm1/ > > > Hi, > > The git-acpi

Re: 'struct task_struct' has no member named 'mems_allowed' (was: Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Andrew Morton
On Fri, 12 Jan 2007 14:00:16 -0800 (PST) Christoph Lameter <[EMAIL PROTECTED]> wrote: > On Fri, 12 Jan 2007, Paul Jackson wrote: > > > It might look clearer to someone who is focused on that particular > > change, but it adds unnecessary noise for the other 90% of the readers > > of that code who

Re: 'struct task_struct' has no member named 'mems_allowed' (was: Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Paul Jackson
Christoph wrote: > If this is hidden in a macro then it may be overlooked. Sooner or later, every line of code is important. Shouting any one of them in #ifdef brackets creates a noisier environment, increasing the chance of missing another. And besides ... the other umpteen cpuset hooks all use

Re: 'struct task_struct' has no member named 'mems_allowed' (was: Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Christoph Lameter
On Fri, 12 Jan 2007, Paul Jackson wrote: > It might look clearer to someone who is focused on that particular > change, but it adds unnecessary noise for the other 90% of the readers > of that code who are not concerned with cpusets at that point in time. This is in NUMA specific code. And they s

Re: 'struct task_struct' has no member named 'mems_allowed' (was: Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Paul Jackson
> Sorry but there will be number of those once we get the dirty writeback > for cpusets fixed. Did you review that patchset (only internally mailed > so far). I haven't reviewed it - sorry. Too much stuff; too little time. If only I had Alan's bots, which are apparently on loan now to Andrew.

Re: 'struct task_struct' has no member named 'mems_allowed' (was: Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Christoph Lameter
On Fri, 12 Jan 2007, Paul Jackson wrote: > Argh - minor detail, but this is the first (outside of fs/proc/base.c) > "#ifdef CONFIG_CPUSETS" in a kernel *.c file. I prefer to avoid that. Sorry but there will be number of those once we get the dirty writeback for cpusets fixed. Did you review tha

Re: 'struct task_struct' has no member named 'mems_allowed' (was: Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Paul Jackson
Christoph wrote: > +++ linux-2.6.20-rc4-mm1/mm/mempolicy.c 2007-01-12 13:21:30.220968608 > -0600 > ... > +#ifdef CONFIG_CPUSETS Argh - minor detail, but this is the first (outside of fs/proc/base.c) "#ifdef CONFIG_CPUSETS" in a kernel *.c file. I prefer to avoid

Re: 'struct task_struct' has no member named 'mems_allowed' (was: Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Christoph Lameter
nd add a comment. Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]> Index: linux-2.6.20-rc4-mm1/mm/mempolicy.c === --- linux-2.6.20-rc4-mm1.orig/mm/mempolicy.c2007-01-12 13:20:17.0 -0600 +++ linux-2.6.20-rc4-mm1/

Re: 2.6.20-rc4-mm1 md problem

2007-01-12 Thread Michal Piotrowski
On 12/01/07, Michal Piotrowski <[EMAIL PROTECTED]> wrote: On 12/01/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > On Friday, 12 January 2007 14:33, Michal Piotrowski wrote: > > My system hangs on this > > http://www.stardust.webpages.pl/files/tbf/euridica/2.6.2

Re: 2.6.20-rc4-mm1 md problem

2007-01-12 Thread Michal Piotrowski
On 12/01/07, Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: On Friday, 12 January 2007 14:33, Michal Piotrowski wrote: > My system hangs on this > http://www.stardust.webpages.pl/files/tbf/euridica/2.6.20-rc4-mm1/bug2.jpg > http://www.stardust.webpages.pl/files/tbf/euridica/2.

Re: 2.6.20-rc4-mm1

2007-01-12 Thread Mariusz Kozlowski
Hello, > This may help > http://lkml.org/lkml/2007/1/12/45 True. Now it boots fine. Tanks for the tip. Dzięki Michał. -- Regards, Mariusz Kozlowski - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo i

Re: 2.6.20-rc4-mm1 md problem

2007-01-12 Thread Rafael J. Wysocki
On Friday, 12 January 2007 14:33, Michal Piotrowski wrote: > My system hangs on this > http://www.stardust.webpages.pl/files/tbf/euridica/2.6.20-rc4-mm1/bug2.jpg > http://www.stardust.webpages.pl/files/tbf/euridica/2.6.20-rc4-mm1/mm-config > > Debug plan: > - revert md-* patches

Re: 2.6.20-rc4-mm1

2007-01-12 Thread Michal Piotrowski
On 12/01/07, Mariusz Kozlowski <[EMAIL PROTECTED]> wrote: Hello, > That's because mmc_lock_unlock should depend on CONFIG_KEYS, it uses struct key. > Could you try the following patch (compile tested)? Thanks. Compiles ok but now I run into another problem and the laptop doesn't boot. The las

Re: 2.6.20-rc4-mm1

2007-01-12 Thread Mariusz Kozlowski
Hello, > That's because mmc_lock_unlock should depend on CONFIG_KEYS, it uses struct > key. > Could you try the following patch (compile tested)? Thanks. Compiles ok but now I run into another problem and the laptop doesn't boot. The last thing I see is grub. So no way to test it now. Time to

2.6.20-rc4-mm1 md problem

2007-01-12 Thread Michal Piotrowski
My system hangs on this http://www.stardust.webpages.pl/files/tbf/euridica/2.6.20-rc4-mm1/bug2.jpg http://www.stardust.webpages.pl/files/tbf/euridica/2.6.20-rc4-mm1/mm-config Debug plan: - revert md-* patches - binary search Does someone have a better idea? Regards, Michal -- Michal K. K

Re: spurious sparse warnings from linux/aio.h (was: 2.6.20-rc4-mm1)

2007-01-12 Thread Suparna Bhattacharya
On Fri, Jan 12, 2007 at 12:55:18PM +0100, Tilman Schmidt wrote: > Andrew Morton schrieb: > > - Merged the "filesystem AIO patches". > > This construct: > > > --- linux-2.6.20-rc4/include/linux/aio.h2007-01-06 > > 23:34:08.0 -0800 > > +++ devel/include/linux/aio.h 2007-01-11 21:

Re: 2.6.20-rc4-mm1

2007-01-12 Thread Frederik Deweerdt
On Fri, Jan 12, 2007 at 11:25:58AM +0100, Mariusz Kozlowski wrote: > Hello, > > Doesn't build on my laptop. > > drivers/mmc/mmc.c: In function 'mmc_lock_unlock': > drivers/mmc/mmc.c:1527: error: dereferencing pointer to incomplete type > drivers/mmc/mmc.c:1527: warning: type defaults to 'in

spurious sparse warnings from linux/aio.h (was: 2.6.20-rc4-mm1)

2007-01-12 Thread Tilman Schmidt
Andrew Morton schrieb: > - Merged the "filesystem AIO patches". This construct: > --- linux-2.6.20-rc4/include/linux/aio.h2007-01-06 23:34:08.0 > -0800 > +++ devel/include/linux/aio.h 2007-01-11 21:36:16.0 -0800 > @@ -237,7 +243,8 @@ do {

Re: 'struct task_struct' has no member named 'mems_allowed' (was: Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Paul Jackson
Sander wrote: > > +mbind-restrict-nodes-to-the-currently-allowed-cpuset.patch > > I had to revert this patch because of: > > === > mm/mempolicy.c: In function 'sys_mbind': > mm/mempolicy.c:885: error: 'struct task_struct' has no member named > 'mems_allowed' You're right - this patch won't buil

'struct task_struct' has no member named 'mems_allowed' (was: Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Sander
Andrew Morton wrote (ao): > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc4-mm1/ > x86/x86_64 things > +mbind-restrict-nodes-to-the-currently-allowed-cpuset.patch I had to revert this patch because of: === mm/mempolicy.c: In function &#x

Re: 2.6.20-rc4-mm1

2007-01-12 Thread Mariusz Kozlowski
Kozlowski # # Automatically generated make config: don't edit # Linux kernel version: 2.6.20-rc4-mm1 # Fri Jan 12 11:07:58 2007 # CONFIG_X86_32=y CONFIG_GENERIC_TIME=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT

Early ACPI lockup (was Re: 2.6.20-rc4-mm1)

2007-01-12 Thread Frederik Deweerdt
On Thu, Jan 11, 2007 at 10:26:27PM -0800, Andrew Morton wrote: > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc4-mm1/ > Hi, The git-acpi.patch replaces earlier "if(!handler) return -EINVAL" by "BUG_ON(!handler)". Thi

Re: 2.6.20-rc4-mm1 -- WARNING: "profile_hits" [drivers/kvm/kvm-intel.ko] undefined!

2007-01-11 Thread Andrew Morton
On Fri, 12 Jan 2007 01:18:17 -0600 "Miles Lane" <[EMAIL PROTECTED]> wrote: > WARNING: "profile_hits" [drivers/kvm/kvm-intel.ko] undefined! This? From: Andrew Morton <[EMAIL PROTECTED]> export profile_hits() on !SMP too. Cc: Ingo Molnar <[EMAIL PROTECTED]> Cc: Avi Kivity <[EMAIL PROTECTED]> Sig

Re: 2.6.20-rc4-mm1 -- WARNING: "profile_hits" [drivers/kvm/kvm-intel.ko] undefined!

2007-01-11 Thread Miles Lane
t 0xc02da66a) and '_etext' WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from .paravirtprobe between '__start_paravirtprobe' (at offset 0xc03aef64) and '__stop_paravirtprobe' WARNING: "profile_hits" [drivers

2.6.20-rc4-mm1

2007-01-11 Thread Andrew Morton
Temporarily at http://userweb.kernel.org/~akpm/2.6.20-rc4-mm1/ Will appear later at ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc4-mm1/ - Added the e1000 driver development tree, as git-e1000.patch (Auke Kok <[EMAIL PROTECTED]>) - Added t