On Wed, 6 Dec 2000, Giacomo Catenazzi wrote:
> On my box, with heavy load I saw:
> spurious 8259A interrupt: IRQ7.
> Newer seen this message before.
>
> Linux (2.4.0.11.4) or my old slow box ?
>
>
> giacomo
>
This is really "normal" occasionally, and probably should not be logged.
This
Alexander Viro wrote:
>
> On Sun, 3 Dec 2000, Linus Torvalds wrote:
>
> >
> > Synching up with Alan and various other stuff. The most important one
> > being the fix to the inode dirty block list.
>
> It doesn't solve the problem. If you unlink a file with dirty metadata
> you have a nice chanc
Alan has it and Linus hasn't applied Alan's patch yet...
Linus said.
"[ Alan - I ahve your patches in my incoming queue still, I wanted to
get
an interim version out to check with Al on the block list and the VM
stuff with Rik and people. ]"
"Garst R. Reese" wrote:
>
> Did you send it
Did you send it Linus?
It is not in pre5
Garst
"Mohammad A. Haque" wrote:
> Ok, so here's the proper patch for those who dont want to wait for t5 =)
> Ignore previous.
>
> On Mon, 4 Dec 2000, Jeff Garzik wrote:
>
> > the fix is in module.h which needs extra parens in the def of
> > set_
On Mon, 4 Dec 2000, Stephen C. Tweedie wrote:
> Agreed. However, is there any reason to have this as a separate
> function? bforget() should _always_ remove the buffer from any inode
> queue. You can make that operation conditional on (bh->b_inode !=
> NULL) if you want to avoid taking the l
On Mon, Dec 04, 2000 at 01:01:36AM -0500, Alexander Viro wrote:
>
> It doesn't solve the problem. If you unlink a file with dirty metadata
> you have a nice chance to hit the BUG() in inode.c:83. I hope that patch
> below closes all remaining holes. See analysis in previous posting
> (basically,
Ok, so here's the proper patch for those who dont want to wait for t5 =)
Ignore previous.
On Mon, 4 Dec 2000, Jeff Garzik wrote:
> the fix is in module.h which needs extra parens in the def of
> set_module_owner...
>
> Jeff
--
Alexander Viro wrote:
>
> On Sun, 3 Dec 2000, Linus Torvalds wrote:
>
> >
> > Synching up with Alan and various other stuff. The most important one
> > being the fix to the inode dirty block list.
>
> It doesn't solve the problem. If you unlink a file with dirty metadata
> you have a nice chanc
I had the same error, The .config file is attached.
Alan Cox wrote:
>> Was borking on dummy.c. This seemed to fix it. Verification please?
>>
>> gcc -D__KERNEL__ -I/usr/src/linux-2.4.0-test11/include -Wall
>> -Wstrict-prototypes -O6 -fomit-frame-pointer -fno-strict-aliasing -pipe
>> -mpreferred
> > dummy.c: In function `dummy_init_module':
> > dummy.c:103: invalid type argument of `->'
> > make[2]: *** [dummy.o] Error 1
>
> No, module.h needs fixing. I guess I didn't send that one to Alan...
You did send it, you just didnt tell me the dummy patch depended on it
and that I needed to se
> Was borking on dummy.c. This seemed to fix it. Verification please?
>
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.0-test11/include -Wall
> -Wstrict-prototypes -O6 -fomit-frame-pointer -fno-strict-aliasing -pipe
> -mpreferred-stack-boundary=2 -march=i686 -DMODULE -DMODVERSIONS -include
> /usr/src/li
Mike Galbraith wrote:
>
> Hi,
>
> When stressing swap (virgin test12-pre4), I encounter the repeatable
> oops below once load builds to heavy. The vmscan.c:UnlockPage(page)
> addition sets it off. Appears 100% repeatable.
>
Same here.
-
To unsubscribe from this list: send the line "unsubscri
the fix is in module.h which needs extra parens in the def of
set_module_owner...
Jeff
On Mon, 4 Dec 2000, Mohammad A. Haque wrote:
> Patch posted here...
> http://marc.theaimsgroup.com/?l=linux-kernel&m=97590235825341&w=2
>
> "Garst R. Reese" wrote:
> >
> > Fails to compile module
On Sun, 3 Dec 2000, Mohammad A. Haque wrote:
> Was borking on dummy.c. This seemed to fix it. Verification please?
>
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.0-test11/include -Wall
> -Wstrict-prototypes -O6 -fomit-frame-pointer -fno-strict-aliasing -pipe
> -mpreferred-stack-boundary=2 -march=i6
Patch posted here...
http://marc.theaimsgroup.com/?l=linux-kernel&m=97590235825341&w=2
"Garst R. Reese" wrote:
>
> Fails to compile module at line 103,
> invalid type argument of ->
> Sorry if this well known.
> Garst
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Sun, 3 Dec 2000, Linus Torvalds wrote:
>
> Synching up with Alan and various other stuff. The most important one
> being the fix to the inode dirty block list.
It doesn't solve the problem. If you unlink a file with dirty metadata
you have a nice chance to hit the BUG() in inode.c:83. I ho
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -mno-fp-regs -ffixed-8 -mcpu=ev6
-Wa,-mev6-DEXPORT_SYMTAB -c pci.c
pci.c: In function `pci_read_bases':
pci.c:576: `tmp' undeclared (first use in this function)
pci.c:576:
Was borking on dummy.c. This seemed to fix it. Verification please?
gcc -D__KERNEL__ -I/usr/src/linux-2.4.0-test11/include -Wall
-Wstrict-prototypes -O6 -fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i686 -DMODULE -DMODVERSIONS -include
/usr/src/linux-2.4.0-te
18 matches
Mail list logo
