ov511.c

2001-05-29 Thread Stephen Crowley

The ov511 driver fails to compile in 2.4.5

gcc -D__KERNEL__ -I/home/stephenc/kernel/linux/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i686-c -o ov511.o ov511.c
ov511.c: In function ov511_read_proc':
ov511.c:340: version' undeclared (first use in this function)
ov511.c:340: (Each undeclared identifier is reported only once
ov511.c:340: for each function it appears in.)
make[4]: *** [ov511.o] Error 1
make[4]: Leaving directory /home/stephenc/kernel/linux/drivers/usb'

-- 
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



ov511.c

2001-05-29 Thread Stephen Crowley

The ov511 driver fails to compile in 2.4.5

gcc -D__KERNEL__ -I/home/stephenc/kernel/linux/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -march=i686-c -o ov511.o ov511.c
ov511.c: In function ov511_read_proc':
ov511.c:340: version' undeclared (first use in this function)
ov511.c:340: (Each undeclared identifier is reported only once
ov511.c:340: for each function it appears in.)
make[4]: *** [ov511.o] Error 1
make[4]: Leaving directory /home/stephenc/kernel/linux/drivers/usb'

-- 
Stephen
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



ipx wont compile in 2.4.3

2001-03-31 Thread Stephen Crowley

Trying to compile 2.4.3 with ipx support gives the following

net/network.o(.data+0x3e48): undefined reference to sysctl_ipx_pprop_broadcasting'


--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



ipx wont compile in 2.4.3

2001-03-31 Thread Stephen Crowley

Trying to compile 2.4.3 with ipx support gives the following

net/network.o(.data+0x3e48): undefined reference to sysctl_ipx_pprop_broadcasting'


--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



kernel BUG at page_alloc.c:84!

2000-11-29 Thread Stephen Crowley

I've been noticing some nasty problems with 2.4.0-test11-pre7, constantly
getting out of memory problems running megahal ( a conversation generator),
I think it has a memory leak.. nothing else seems to cause this.

Nov 29 21:36:41 intolerance kernel: kernel BUG at page_alloc.c:84!
Nov 29 21:36:41 intolerance kernel: invalid operand: 
Nov 29 21:36:41 intolerance kernel: CPU:0
Nov 29 21:36:41 intolerance kernel: EIP:0010:[__free_pages_ok+73/824]
Nov 29 21:36:41 intolerance kernel: EFLAGS: 00010282
Nov 29 21:36:41 intolerance kernel: eax: 001f   ebx: c100c89c   ecx: c0257828   
edx: 
Nov 29 21:36:41 intolerance kernel: esi: 03ce   edi: c8c22098   ebp:    
esp: cd80de68
Nov 29 21:36:41 intolerance kernel: ds: 0018   es: 0018   ss: 0018
Nov 29 21:36:41 intolerance kernel: Process megahal (pid: 31863, stackpage=cd80d000)
Nov 29 21:36:41 intolerance kernel: Stack: c0211c72 c0211e60 0054 c100c89c 
03ce c8c22098 ce67a0c8 c1044010 
Nov 29 21:36:41 intolerance kernel:c02588e0 0207  317e 
c012a847 c012ac7b 0040 03ce 
Nov 29 21:36:41 intolerance kernel:c011fa5a c100c89c cabbdfa0 0805 
cec55960 024a3000 c8c22098 0980 
Nov 29 21:36:41 intolerance kernel: Call Trace: [tvecs+8030/43772] [tvecs+8524/43772] 
[__free_pages+19/20] [free_page_and_swap_cache+131/136] [zap_page_range+374/504] 
[exit_mmap+201/288] [mmput+21/44] 
Nov 29 21:36:41 intolerance kernel:[do_exit+165/508] [do_signal+544/636] 
[do_page_fault+0/988] [update_process_times+29/144] [update_wall_time+11/60] 
[timer_bh+36/604] [timer_interrupt+95/264] [bh_action+27/96] 
Nov 29 21:36:41 intolerance kernel:[tasklet_hi_action+60/96] 
[do_softirq+63/100] [do_IRQ+161/176] [error_code+52/60] [signal_return+20/24] 
Nov 29 21:36:41 intolerance kernel: Code: 0f 0b 83 c4 0c 89 f6 89 d8 2b 05 38 c8 2b c0 
69 c0 f1 f0 f0 

Does that backtrace provide anything useful?

-- 
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



kernel BUG at page_alloc.c:84!

2000-11-29 Thread Stephen Crowley

I've been noticing some nasty problems with 2.4.0-test11-pre7, constantly
getting out of memory problems running megahal ( a conversation generator),
I think it has a memory leak.. nothing else seems to cause this.

Nov 29 21:36:41 intolerance kernel: kernel BUG at page_alloc.c:84!
Nov 29 21:36:41 intolerance kernel: invalid operand: 
Nov 29 21:36:41 intolerance kernel: CPU:0
Nov 29 21:36:41 intolerance kernel: EIP:0010:[__free_pages_ok+73/824]
Nov 29 21:36:41 intolerance kernel: EFLAGS: 00010282
Nov 29 21:36:41 intolerance kernel: eax: 001f   ebx: c100c89c   ecx: c0257828   
edx: 
Nov 29 21:36:41 intolerance kernel: esi: 03ce   edi: c8c22098   ebp:    
esp: cd80de68
Nov 29 21:36:41 intolerance kernel: ds: 0018   es: 0018   ss: 0018
Nov 29 21:36:41 intolerance kernel: Process megahal (pid: 31863, stackpage=cd80d000)
Nov 29 21:36:41 intolerance kernel: Stack: c0211c72 c0211e60 0054 c100c89c 
03ce c8c22098 ce67a0c8 c1044010 
Nov 29 21:36:41 intolerance kernel:c02588e0 0207  317e 
c012a847 c012ac7b 0040 03ce 
Nov 29 21:36:41 intolerance kernel:c011fa5a c100c89c cabbdfa0 0805 
cec55960 024a3000 c8c22098 0980 
Nov 29 21:36:41 intolerance kernel: Call Trace: [tvecs+8030/43772] [tvecs+8524/43772] 
[__free_pages+19/20] [free_page_and_swap_cache+131/136] [zap_page_range+374/504] 
[exit_mmap+201/288] [mmput+21/44] 
Nov 29 21:36:41 intolerance kernel:[do_exit+165/508] [do_signal+544/636] 
[do_page_fault+0/988] [update_process_times+29/144] [update_wall_time+11/60] 
[timer_bh+36/604] [timer_interrupt+95/264] [bh_action+27/96] 
Nov 29 21:36:41 intolerance kernel:[tasklet_hi_action+60/96] 
[do_softirq+63/100] [do_IRQ+161/176] [error_code+52/60] [signal_return+20/24] 
Nov 29 21:36:41 intolerance kernel: Code: 0f 0b 83 c4 0c 89 f6 89 d8 2b 05 38 c8 2b c0 
69 c0 f1 f0 f0 

Does that backtrace provide anything useful?

-- 
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: kernel BUG at fs.c:567

2000-10-29 Thread Stephen Crowley

On Sun, Oct 29, 2000 at 11:27:58AM +0100, David Weinehall wrote:
> On Sat, Oct 28, 2000 at 06:43:42PM -0500, Stephen Crowley wrote:
> > kernel 2.4.0-test10-pre6, but this has been here as long as I can
> > remember.
> > 
> > starting wine triggers the bug, C: points to /win2k which is an NTFS
> > filesystem.
>
> Yep, there's a solution for this. Get yourself the complete
> specifications for the Win2K NTFS, and implement it. The kernel NTFS
> simply doesn't support the Win2K NTFS, and rather than risking anything,
> it just OOPS:es. Not that I have any Win2K systems, but if I had, I'd
> damn sure rather see the kernel OOPS than those filesystems trashed.

I see.. but the FS is mounted read-only, so even if it didn't oops why would
there be a risk of it getting trashed? I really wouldn't mind if it did got
trashed.. thanks for the pointer though.

-- 
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



kernel BUG at fs.c:567

2000-10-28 Thread Stephen Crowley

kernel 2.4.0-test10-pre6, but this has been here as long as I can
remember.

starting wine triggers the bug, C: points to /win2k which is an NTFS
filesystem.

The offending code..

/* It's fscking broken. */

static int ntfs_get_block(struct inode *inode, long block, struct buffer_head *bh, int 
create)
{
BUG();
return -1;
}

Heh. is there something else can be done there instead of just taking a crap
on itself? I can no longer read anything from /proc after this happens.

Oct 28 18:27:54 intolerance kernel: kernel BUG at fs.c:567!
Oct 28 18:27:54 intolerance kernel: invalid operand: 
Oct 28 18:27:54 intolerance kernel: CPU:0
Oct 28 18:27:54 intolerance kernel: EIP:0010:[ntfs_get_block+20/32]
Oct 28 18:27:54 intolerance kernel: EFLAGS: 00210282
Oct 28 18:27:54 intolerance kernel: eax: 0018   ebx: cc95e2c0   ecx: c6bc2000   
edx: cf974520
Oct 28 18:27:54 intolerance kernel: esi:    edi: 000b   ebp: 0800   
esp: c6bc3dfc
Oct 28 18:27:54 intolerance kernel: ds: 0018   es: 0018   ss: 0018
Oct 28 18:27:54 intolerance kernel: Process wine (pid: 1502, stackpage=c6bc3000)
Oct 28 18:27:54 intolerance kernel: Stack: c0215e52 c0216278 0237 c012f904 
c70f7340  cc95e2c0  
Oct 28 18:27:54 intolerance kernel: c11c6170  c70f73dc 
   cc95e2c0 
Oct 28 18:27:54 intolerance kernel:02a4 c70f7340  c0122263 
c11c6170 c11c6170 c1480eb4  
Oct 28 18:27:54 intolerance kernel: Call Trace: [tvecs+44350/74220] 
[tvecs+45412/74220] [block_read_full_page+236/488] [add_to_p age_cache_unique+267/280] 
[ntfs_readpage+15/20] [ntfs_get_block+0/32] [read_cluster_nonblocking+258/324] 
Oct 28 18:27:54 intolerance kernel:[filemap_nopage+304/776] 
[filemap_nopage+0/776] [do_no_page+80/176] [handle_mm_fault+ 231/340] 
[do_page_fault+315/992] [do_page_fault+0/992] [old_mmap+192/240] [old_mmap+224/240] 
Oct 28 18:27:54 intolerance kernel:[error_code+52/60] 
Oct 28 18:27:54 intolerance kernel: Code: 0f 0b 83 c4 0c b8 ff ff ff ff c3 90 8b 44 24 
08 68 90 fb 14 


Please CC: responses, I'm not subscribed to the list.

-- 
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



kernel BUG at fs.c:567

2000-10-28 Thread Stephen Crowley

kernel 2.4.0-test10-pre6, but this has been here as long as I can
remember.

starting wine triggers the bug, C: points to /win2k which is an NTFS
filesystem.

The offending code..

/* It's fscking broken. */

static int ntfs_get_block(struct inode *inode, long block, struct buffer_head *bh, int 
create)
{
BUG();
return -1;
}

Heh. is there something else can be done there instead of just taking a crap
on itself? I can no longer read anything from /proc after this happens.

Oct 28 18:27:54 intolerance kernel: kernel BUG at fs.c:567!
Oct 28 18:27:54 intolerance kernel: invalid operand: 
Oct 28 18:27:54 intolerance kernel: CPU:0
Oct 28 18:27:54 intolerance kernel: EIP:0010:[ntfs_get_block+20/32]
Oct 28 18:27:54 intolerance kernel: EFLAGS: 00210282
Oct 28 18:27:54 intolerance kernel: eax: 0018   ebx: cc95e2c0   ecx: c6bc2000   
edx: cf974520
Oct 28 18:27:54 intolerance kernel: esi:    edi: 000b   ebp: 0800   
esp: c6bc3dfc
Oct 28 18:27:54 intolerance kernel: ds: 0018   es: 0018   ss: 0018
Oct 28 18:27:54 intolerance kernel: Process wine (pid: 1502, stackpage=c6bc3000)
Oct 28 18:27:54 intolerance kernel: Stack: c0215e52 c0216278 0237 c012f904 
c70f7340  cc95e2c0  
Oct 28 18:27:54 intolerance kernel: c11c6170  c70f73dc 
   cc95e2c0 
Oct 28 18:27:54 intolerance kernel:02a4 c70f7340  c0122263 
c11c6170 c11c6170 c1480eb4  
Oct 28 18:27:54 intolerance kernel: Call Trace: [tvecs+44350/74220] 
[tvecs+45412/74220] [block_read_full_page+236/488] [add_to_p age_cache_unique+267/280] 
[ntfs_readpage+15/20] [ntfs_get_block+0/32] [read_cluster_nonblocking+258/324] 
Oct 28 18:27:54 intolerance kernel:[filemap_nopage+304/776] 
[filemap_nopage+0/776] [do_no_page+80/176] [handle_mm_fault+ 231/340] 
[do_page_fault+315/992] [do_page_fault+0/992] [old_mmap+192/240] [old_mmap+224/240] 
Oct 28 18:27:54 intolerance kernel:[error_code+52/60] 
Oct 28 18:27:54 intolerance kernel: Code: 0f 0b 83 c4 0c b8 ff ff ff ff c3 90 8b 44 24 
08 68 90 fb 14 


Please CC: responses, I'm not subscribed to the list.

-- 
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/