All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srihari Vijayaraghavan <harisri@bigpond.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20pre11aa1
Date: Sat, 26 Oct 2002 00:03:06 +1000	[thread overview]
Message-ID: <200210260003.06285.harisri@bigpond.com> (raw)
In-Reply-To: <20021023143515.GE1912@dualathlon.random>

Hello Andrea,

[I tried to post the reply through groups.google.com, and it looks like it 
didn't get to lkml. :( ]

> try to apply all the scheduler related patches:
>
> 10_sched-o1-hyperthreading-3  20_apm-o1-sched-1  20_sched-o1-fixes-5
> 21_o1-A4-aa-1 20_rcu-poll-7

OK.

I have applied the patches 0* and the following patches in this order:
10_sched-o1-hyperthreading-3
20_apm-o1-sched-1
20_rcu-poll-7
20_sched-o1-fixes-5
21_o1-A4-aa-1

The resulting kernel is very stable and it does not crash.

Then I tried patches [01]* and the extra patches (20_apm-o1-sched-1,
20_rcu-poll-7, 20_sched-o1-fixes-5, 21_o1-A4-aa-1), I couldn't compile
the kernel.

Here is the current std_err:

inode.c:1468: warning: initialization from incompatible pointer type
In file included from ide.c:149:
/usr/src/01/include/linux/ide.h:333:16: warning: ISO C requires
whitespace after the macro name
ide.c: In function `init_hwif_data':
ide.c:270: `ide_disk' undeclared (first use in this function)
ide.c:270: (Each undeclared identifier is reported only once
ide.c:270: for each function it appears in.)
ide.c: In function `ide_geninit':
ide.c:639: `ide_disk' undeclared (first use in this function)
ide.c: In function `do_reset1':
ide.c:791: `ide_disk' undeclared (first use in this function)
ide.c: In function `ide_dump_status':
ide.c:973: `ide_disk' undeclared (first use in this function)
ide.c: In function `try_to_flush_leftover_data':
ide.c:1034: `ide_disk' undeclared (first use in this function)
ide.c: In function `ide_error':
ide.c:1071: `ide_disk' undeclared (first use in this function)
ide.c: In function `start_request':
ide.c:1373: `ide_disk' undeclared (first use in this function)
ide.c: In function `ide_open':
ide.c:2119: `ide_disk' undeclared (first use in this function)
ide.c: In function `ide_reinit_drive':
ide.c:2768: `ide_disk' undeclared (first use in this function)
ide.c: In function `ide_ioctl':
ide.c:2842: `ide_disk' undeclared (first use in this function)
ide.c: In function `ide_setup':
ide.c:3383: `ide_disk' undeclared (first use in this function)
make[3]: *** [ide.o] Error 1
make[2]: *** [first_rule] Error 2
make[1]: *** [_subdir_ide] Error 2
make: *** [_dir_drivers] Error 2
make: *** Waiting for unfinished jobs....
{standard input}: Assembler messages:
{standard input}:1014: Warning: indirect lcall without `*'
{standard input}:1091: Warning: indirect lcall without `*'
{standard input}:1176: Warning: indirect lcall without `*'
{standard input}:1255: Warning: indirect lcall without `*'
{standard input}:1271: Warning: indirect lcall without `*'
{standard input}:1281: Warning: indirect lcall without `*'
{standard input}:1349: Warning: indirect lcall without `*'
{standard input}:1364: Warning: indirect lcall without `*'
{standard input}:1375: Warning: indirect lcall without `*'
{standard input}:1874: Warning: indirect lcall without `*'
{standard input}:1960: Warning: indirect lcall without `*'

Thanks.
-- 
Hari
harisri@bigpond.com



  reply	other threads:[~2002-10-25 13:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-16 16:51 2.4.20pre11aa1 Andrea Arcangeli
2002-10-17 12:04 ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-17 12:10   ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-17 13:01     ` 2.4.20pre11aa1 Keith Owens
2002-10-17 15:26       ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-17 16:27         ` 2.4.20pre11aa1 Andrea Arcangeli
     [not found]           ` <200210190014.19357.harisri@bigpond.com>
2002-10-18 14:52             ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-18 15:21               ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-18 15:34               ` 2.4.20pre11aa1 Keith Owens
2002-10-18 16:00                 ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-19  1:21                   ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-19  1:25                     ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-22 10:48                       ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-22 14:55                         ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-23 12:27                           ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-23 12:46                             ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-23 14:26                               ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-23 14:35                                 ` 2.4.20pre11aa1 Andrea Arcangeli
2002-10-25 14:03                                   ` Srihari Vijayaraghavan [this message]
2002-10-31 10:47                                     ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-11-09  9:34                                       ` Solved 2.4.20pre11aa1/2.4.20rc1aa1 Agpgart/Radeon crash. [was: Re: 2.4.20pre11aa1] Srihari Vijayaraghavan
2002-11-10  2:50                                         ` Andrea Arcangeli
2002-11-10  3:24                                           ` Srihari Vijayaraghavan
2002-10-17 13:02     ` 2.4.20pre11aa1 Srihari Vijayaraghavan
2002-10-17 13:00       ` 2.4.20pre11aa1 Andrea Arcangeli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200210260003.06285.harisri@bigpond.com \
    --to=harisri@bigpond.com \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.