On Tue, Jan 15, 2008 at 12:35:15PM -0800, Andrew Morton wrote:
> On Tue, 15 Jan 2008 14:36:24 +0100 Jesper Nilsson <[EMAIL PROTECTED]> wrote:
>
> > - Move alignment to page size of init data outside ifdef for BLK_DEV_INITRD.
> > The reservation up to page size of memory after init data was previ
On Tue, 15 Jan 2008 14:36:24 +0100 Jesper Nilsson <[EMAIL PROTECTED]> wrote:
> - Move alignment to page size of init data outside ifdef for BLK_DEV_INITRD.
> The reservation up to page size of memory after init data was previously
> not done if BLK_DEV_INITRD was undefined.
> This caused a k
> > What about applying the same fixes/changes to v32?
>
> In the works.
>
> > It would btw. be nice to move the vmlinux.lds.S files to
> > arch/cris/kernel/.
> > Se how x86 handle build for two different bit sizes.
> >
> > If this is done then cris is less awkward compared
> > to the other arch
On Tue, Jan 15, 2008 at 02:54:19PM +0100, Sam Ravnborg wrote:
> On Tue, Jan 15, 2008 at 02:36:24PM +0100, Jesper Nilsson wrote:
> > - Move alignment to page size of init data outside ifdef for BLK_DEV_INITRD.
> > The reservation up to page size of memory after init data was previously
> > not d
On Tue, Jan 15, 2008 at 02:36:24PM +0100, Jesper Nilsson wrote:
> - Move alignment to page size of init data outside ifdef for BLK_DEV_INITRD.
> The reservation up to page size of memory after init data was previously
> not done if BLK_DEV_INITRD was undefined.
> This caused a kernel oops whe
- Move alignment to page size of init data outside ifdef for BLK_DEV_INITRD.
The reservation up to page size of memory after init data was previously
not done if BLK_DEV_INITRD was undefined.
This caused a kernel oops when init memory pages were freed after startup,
data placed in the same
>
> >> Trace; c0194d36
>
> >Do you have any ISAPNP cards in your system?
>
> Yes, a Soundblaster AWE64 that has never given me any problems. I tried
> booting
> test10 and test1 with that card pulled, and they both still oopsed on boot.
>
>
Jeff, I recompiled test10 with all kernel ISA PN
Jeff, thank you for responding.
>Can you play the kernel shuffle, and narrow down exactly which kernel
>version breaks for you? Read, from the linux source tree,
>Documentation/BUG-HUNTING.
OK. I've compiled test1, and it also oopsed on boot. (Which is confusing,
since I know for sure I had t
Brad Corsello wrote:
>
> [1.] One line summary of the problem:
> kernel oops on boot in 2.4.0 test 10 (i386)
>
> [2.] Full description of the problem/report:
> On every boot of test 10, I get a kernel oops very early on.
> Is reproducibl
[1.] One line summary of the problem:
kernel oops on boot in 2.4.0 test 10 (i386)
[2.] Full description of the problem/report:
On every boot of test 10, I get a kernel oops very early on.
Is reproducible (happens every boot).
I've successfully booted 2.3 ke
Mircea Damian wrote:
>
> On Thu, Oct 26, 2000 at 10:20:45AM -0400, Brian Gerst wrote:
> > Mircea Damian wrote:
> > >
> > > Hello,
> > >
> > > I'm unable to boot kernel 2.4.0-test10-pre5 on a:
> >
> > Upgrade GCC to 2.91.66 (aka egcs-1.1.2)
>
> Ok. I can do that, but there is nowhere written that
On Thu, Oct 26, 2000 at 10:20:45AM -0400, Brian Gerst wrote:
> Mircea Damian wrote:
> >
> > Hello,
> >
> > I'm unable to boot kernel 2.4.0-test10-pre5 on a:
>
> Upgrade GCC to 2.91.66 (aka egcs-1.1.2)
Ok. I can do that, but there is nowhere written that I should do
that. If I remember right gc
On Thu, 26 Oct 2000, Brian Gerst wrote:
> "Richard B. Johnson" wrote:
> > Stand-alone, it can't do anything useful. However, if it generates
> > a page-fault due to the read or write, the page-fault handler could
> > do "something". Currently, the fault it fatal, probably because
> > the passed p
Richard B. Johnson wrote:
> > And here is the broken routine:
> >
> > 03f4 :
[...]
> This is not good code. It does the following:
>
> o Gets a parameter off the stack and puts into eax (a pointer).
> o Put the value 1 into ecx.
> o Take a byte from the pointed-to location and pu
"Richard B. Johnson" wrote:
> Stand-alone, it can't do anything useful. However, if it generates
> a page-fault due to the read or write, the page-fault handler could
> do "something". Currently, the fault it fatal, probably because
> the passed pointer is invalid.
The write-protect test code is
Mircea Damian wrote:
>
> Hello,
>
> I'm unable to boot kernel 2.4.0-test10-pre5 on a:
Upgrade GCC to 2.91.66 (aka egcs-1.1.2)
--
Brian Gerst
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
On Thu, 26 Oct 2000, Mircea Damian wrote:
>
>
> Hello,
>
> I'm unable to boot kernel 2.4.0-test10-pre5 on a:
>
>
> And here is the broken routine:
>
> 03f4 :
> 3f4: 8b 44 24 04 movl 0x4(%esp,1),%eax
> 3f8: b9 01 00 00 00 movl $0x1,%ecx
> 3fd: 8a 10
Hello,
I'm unable to boot kernel 2.4.0-test10-pre5 on a:
root@cyrix:/usr/src/linux/arch/i386/mm# cat /proc/cpuinfo
processor : 0
vendor_id : CyrixInstead
cpu family : 6
model : 2
model name : 6x86MX 2.5x Core/Bus Clock
stepping: 7
cpu MHz : 166.
18 matches
Mail list logo
