Linus,
Could you apply his patch?
On Mon, 18 Sep 2000, Rasmus Andersen wrote:
> On Sun, Sep 17, 2000 at 10:53:55PM -0300, Marcelo Tosatti wrote:
> >
> > AFAIK most distros use CONFIG_PCI_GOANY, which causes the kernel to try to
> > detect the PCI devices directly, and in case this fails, it t
On Sun, Sep 17, 2000 at 10:53:55PM -0300, Marcelo Tosatti wrote:
>
> AFAIK most distros use CONFIG_PCI_GOANY, which causes the kernel to try to
> detect the PCI devices directly, and in case this fails, it tries to
> detect via BIOS.
I thought so too from reading the help regarding this option,
On Sun, 17 Sep 2000, Rasmus Andersen wrote:
> Also (for Mike Galbraith): Why did the KDB make a difference in
> this case? I could not this any code it touched in the vicinity
> of pcibios_init(). But I probably did not look hard enough.
I looked all over the place for an explanation. Elves and
On Sun, 17 Sep 2000, Rasmus Andersen wrote:
> [This is an aging thread where my old P75 machine oopsed early in
> boot for both 2.4.0-XX and 2.2.17. Mike Galbraith helped me a lot
> and among other things mailed me KDB, which, when enabled, made a
> 2.4.0-test8 kernel boot.]
>
> Hi.
>
> I fina
[This is an aging thread where my old P75 machine oopsed early in
boot for both 2.4.0-XX and 2.2.17. Mike Galbraith helped me a lot
and among other things mailed me KDB, which, when enabled, made a
2.4.0-test8 kernel boot.]
Hi.
I finally had some time to put printks into the kernel and that
got
On Mon, Sep 11, 2000 at 09:00:02PM +0200, Mike Galbraith wrote:
> The symptom is _different_ than without the patch being applied? That
> should be impossible. With Kernel Debugging disabled, the patch should
> have zero effect.. you should have your original oops back.
Yeah, sorry about that :
On Mon, 11 Sep 2000, Rasmus Andersen wrote:
> On Mon, Sep 11, 2000 at 12:40:25AM +0200, Mike Galbraith wrote:
> > On Sun, 10 Sep 2000, Rasmus Andersen wrote:
> >
> [...]
> > > So adding IKD to 2.4.0t8 made the initial oops go away/be hidden.
> >
> > The odd colours/chars are the print EIP featu
On Mon, Sep 11, 2000 at 12:40:25AM +0200, Mike Galbraith wrote:
> On Sun, 10 Sep 2000, Rasmus Andersen wrote:
>
[...]
> > So adding IKD to 2.4.0t8 made the initial oops go away/be hidden.
>
> The odd colours/chars are the print EIP feature in action. You should
> almost never say yes to all con
On Sun, 10 Sep 2000, Rasmus Andersen wrote:
> Hi.
>
> Interesting turn in my efforts to make linux boot on my newly acquired
> old computer: Mike Galbraith offered me IKD for 2.4.0t8, which I
> accepted and tried (I said yes to all the IKD config options). This
> made 2.4.0t8 boot and get as far
Hi.
Interesting turn in my efforts to make linux boot on my newly acquired
old computer: Mike Galbraith offered me IKD for 2.4.0t8, which I
accepted and tried (I said yes to all the IKD config options). This
made 2.4.0t8 boot and get as far as complaining about bad root fs
(which is correct for i
On Fri, 8 Sep 2000, Andrew Burgess wrote:
>
> > >Oops from 2.2.17 (some more before this, but it went offscreen):
> ...
> > You need to capture and decode the first oops. Compile a kernel with a
> > serial console and capture the oops log on a second machine.
>
> Or set your console for more
> Thats not the first oops yet, and as Keith told you, its useless.
You are right and I fscked up. Apologies. This should be the first
oops (from 2.2.17):
ksymoops 0.7c on i686 2.2.17pre13. Options used
-V (specified)
-K (specified)
-L (specified)
-O (specified)
-m ../l
On Sat, 9 Sep 2000, Rasmus Andersen wrote:
>
> Code: 0f b6 0c 03 89 4c 24 14 51 68 8e e5 17 c0 e8 de a4 00 00 83
> >>EIP; c0107f27<=
> Trace; c300
> Trace; c0107f85
Thats not the first oops yet, and as Keith told you, its useless.
-
To unsubscribe from this list: send the l
On 0, Keith Owens <[EMAIL PROTECTED]> wrote:
> On Fri, 8 Sep 2000 14:48:51 +0200,
> Rasmus Andersen <[EMAIL PROTECTED]> wrote:
> >I just got hold of an old machine (P75, 32MB RAM). On trying to install
> >RH 6.2 on it, I got an oops after loading the kernel from the boot floppy.
> >I then tried
> >Oops from 2.2.17 (some more before this, but it went offscreen):
...
> You need to capture and decode the first oops. Compile a kernel with a
> serial console and capture the oops log on a second machine.
Or set your console for more than 80x25 using SVGATextMode. I use
/usr/sbin/SVGATextMo
On Fri, 8 Sep 2000 14:48:51 +0200,
Rasmus Andersen <[EMAIL PROTECTED]> wrote:
>I just got hold of an old machine (P75, 32MB RAM). On trying to install
>RH 6.2 on it, I got an oops after loading the kernel from the boot floppy.
>I then tried to boot a 2.4.0-test8-pre6 (made with make bzdisk), but
16 matches
Mail list logo
