Re: sparc32: boot fails with > 256 MB memory after switch to NO_BOOTMEM

On 2021-01-28 10:35, Mike Rapoport wrote: On Wed, Jan 27, 2021 at 04:03:00PM +0100, Andreas Larsson wrote: Commit cca079ef8ac29a7c02192d2bad2ffe4c0c5ffdd0 makes sparc32 use memblocks instead of the previous bootmem solution. Unfortunately, due to this: #define PAGE_OFFSET 0xf000 #define

Re: sparc32: boot fails with > 256 MB memory after switch to NO_BOOTMEM

On Wed, Jan 27, 2021 at 04:03:00PM +0100, Andreas Larsson wrote: > > > Commit cca079ef8ac29a7c02192d2bad2ffe4c0c5ffdd0 makes sparc32 use > memblocks instead of the previous bootmem solution. Unfortunately, due > to this: > > #define PAGE_OFFSET 0xf000 > #define __va(x)((void

sparc32: boot fails with > 256 MB memory after switch to NO_BOOTMEM

Commit cca079ef8ac29a7c02192d2bad2ffe4c0c5ffdd0 makes sparc32 use memblocks instead of the previous bootmem solution. Unfortunately, due to this: #define PAGE_OFFSET 0xf000 #define __va(x) ((void *)((unsigned long) (x) - phys_base + PAGE_OFFSET)) #define phys_to_virt __va it

Re: BUG: omap5: v5.8-rc7 boot fails

Hi Tony, > Am 29.07.2020 um 13:55 schrieb Tony Lindgren : > > * Tony Lindgren [200728 08:23]: >> * H. Nikolaus Schaller [200727 20:51]: >>> Hi Tony, >>> after trying v5.8-rc7 the Pyra boot hangs after ca. 3 seconds >>> (a little random what the last log line is). >>> >>> I could bisect it to:

Re: BUG: omap5: v5.8-rc7 boot fails

* Tony Lindgren [200728 08:23]: > * H. Nikolaus Schaller [200727 20:51]: > > Hi Tony, > > after trying v5.8-rc7 the Pyra boot hangs after ca. 3 seconds > > (a little random what the last log line is). > > > > I could bisect it to: > > > > 6cfcd5563b4fadbf49ba8fa481978e5e86d30322 is the first

Re: BUG: omap5: v5.8-rc7 boot fails

* H. Nikolaus Schaller [200727 20:51]: > Hi Tony, > after trying v5.8-rc7 the Pyra boot hangs after ca. 3 seconds > (a little random what the last log line is). > > I could bisect it to: > > 6cfcd5563b4fadbf49ba8fa481978e5e86d30322 is the first bad commit > commit

BUG: omap5: v5.8-rc7 boot fails

Hi Tony, after trying v5.8-rc7 the Pyra boot hangs after ca. 3 seconds (a little random what the last log line is). I could bisect it to: 6cfcd5563b4fadbf49ba8fa481978e5e86d30322 is the first bad commit commit 6cfcd5563b4fadbf49ba8fa481978e5e86d30322 Author: Tony Lindgren Date: Mon Jul 13

Re: [mainline][Oops][bisected 2ba3e6 ] 5.7.0 boot fails with kernel panic on powerpc

On Wed, 3 Jun 2020 at 19:03, Joerg Roedel wrote: > > On Wed, Jun 03, 2020 at 04:20:57PM +0530, Abdul Haleem wrote: > > @Joerg, Could you please have a look? > > Can you please try the attached patch? @Joerg, Linaro test farm noticed this kernel crash on nxp ls2088 Machine model: Freescale

Re: [mainline][Oops][bisected 2ba3e6 ] 5.7.0 boot fails with kernel panic on powerpc

On Wed, 2020-06-03 at 15:32 +0200, Joerg Roedel wrote: > On Wed, Jun 03, 2020 at 04:20:57PM +0530, Abdul Haleem wrote: > > @Joerg, Could you please have a look? > > Can you please try the attached patch? Thanks Joerg, The given patch fixes the boot problem. Please add Reported-by in fix commit.

Re: [mainline][Oops][bisected 2ba3e6 ] 5.7.0 boot fails with kernel panic on powerpc

On Wed, Jun 03, 2020 at 03:32:57PM +0200, Joerg Roedel wrote: > On Wed, Jun 03, 2020 at 04:20:57PM +0530, Abdul Haleem wrote: > > @Joerg, Could you please have a look? > > Can you please try the attached patch? Hi Joerg, I did hit the similar boot failue on a Power9 baremetal box(mentioned in

Re: [mainline][Oops][bisected 2ba3e6 ] 5.7.0 boot fails with kernel panic on powerpc

On Wed, Jun 03, 2020 at 04:20:57PM +0530, Abdul Haleem wrote: > @Joerg, Could you please have a look? Can you please try the attached patch? diff --git a/include/asm-generic/5level-fixup.h b/include/asm-generic/5level-fixup.h index 58046ddc08d0..afbab31fbd7e 100644 ---

Re: [mainline][Oops][bisected 2ba3e6 ] 5.7.0 boot fails with kernel panic on powerpc

hi Abdul, On Wed, Jun 03, 2020 at 04:20:57PM +0530, Abdul Haleem wrote: > Greeting's > > Today's mainline kernel panics when booting on my powerpc lpar Thanks for the report, I am looking into it with my limited powerpc knowledge. But I have an idea and will send you something to test later

RE: [EXT] [BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma: support little endian for edma driver"

;Subject: Re: [EXT] [BUG BISECT] Net boot fails on VF50 after "dmaengine: >fsl-edma: support little endian for edma driver" > >Caution: EXT Email > >On Thu, 4 Jul 2019 at 04:10, Peng Ma wrote: >> >> Hi Krzysztof, >> >> I am sorry, It is my mistake to f

RE: [EXT] [BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma: support little endian for edma driver"

org; >linux-kernel@vger.kernel.org; Fabio Estevam ; Leo >Li ; Andy Tang >Subject: Re: [EXT] [BUG BISECT] Net boot fails on VF50 after "dmaengine: >fsl-edma: support little endian for edma driver" > >Caution: EXT Email > >Hi Peng, > >On Wed, Jul 3, 2019 at 11:10

Re: [EXT] [BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma: support little endian for edma driver"

On Thu, 4 Jul 2019 at 04:10, Peng Ma wrote: > > Hi Krzysztof, > > I am sorry, It is my mistake to forget about VF50 used EDMA IP with little > endian. > The Register(CHCFG0 - CHCFG15) of our platform designed as follows: >

Re: [EXT] [BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma: support little endian for edma driver"

Hi Peng, On Wed, Jul 3, 2019 at 11:10 PM Peng Ma wrote: > So we need this patch, I make some changes,Please help me to test attatchment > on VF50 board, You need to change the Subject to something like: Subject: [PATCH] dmaengine: fsl-edma: Add support for LS1028A Also, in the commit log,

RE: [EXT] [BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma: support little endian for edma driver"

;To: Peng Ma ; Vinod Koul ; >dmaeng...@vger.kernel.org; linux-kernel@vger.kernel.org >Subject: [EXT] [BUG BISECT] Net boot fails on VF50 after "dmaengine: >fsl-edma: support little endian for edma driver" > >Caution: EXT Email > >Hi, > >Bisect pointed commit:

Re: [BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma: support little endian for edma driver"

On Tue, Jul 2, 2019 at 10:11 AM Krzysztof Kozlowski wrote: > No, unfortunately it does not help. Just looked at "dmaengine: fsl-edma: support little endian for edma driver" more closely and this one assumes that there wasn't little-endian support originally, which is incorrect. Vybryd,

Re: [BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma: support little endian for edma driver"

On Tue, 2 Jul 2019 at 15:04, Fabio Estevam wrote: > > Hi Krzysztof, > > On Tue, Jul 2, 2019 at 9:13 AM Krzysztof Kozłowski > wrote: > > > > Hi, > > > > Bisect pointed commit: > > commit 002905eca5bedab08bafd9e32541670c7712 > > Author: Peng Ma > > Date: Thu Jun 13 10:27:08 2019 + > >

Re: [BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma: support little endian for edma driver"

Hi Krzysztof, On Tue, Jul 2, 2019 at 9:13 AM Krzysztof Kozłowski wrote: > > Hi, > > Bisect pointed commit: > commit 002905eca5bedab08bafd9e32541670c7712 > Author: Peng Ma > Date: Thu Jun 13 10:27:08 2019 + > dmaengine: fsl-edma: support little endian for edma driver > > as a

Re: [BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma: support little endian for edma driver"

... one more time, but from proper email address: Hi, Bisect pointed commit: commit 002905eca5bedab08bafd9e32541670c7712 Author: Peng Ma Date: Thu Jun 13 10:27:08 2019 + dmaengine: fsl-edma: support little endian for edma driver as a reason of NFSv4 root boot failures. Toradex

[BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma: support little endian for edma driver"

Hi, Bisect pointed commit: commit 002905eca5bedab08bafd9e32541670c7712 Author: Peng Ma Date: Thu Jun 13 10:27:08 2019 + dmaengine: fsl-edma: support little endian for edma driver as a reason of NFSv4 root boot failures. Toradex Colibri VF50 (Cortex A5) on Toradex Iris board. The

Re: APIC timer checked before it is set up, boot fails on Connex L1430

On Mon, 7 Jan 2019, Daniel Drake wrote: > I asked the motherboard vendor if they have any idea why the 8254 is > not ticking and they sent me a new BIOS where it is now working. So we > can probably consider this a non issue, although there are a few other > curious points to mention: > > 1.

Re: APIC timer checked before it is set up, boot fails on Connex L1430

On Fri, Dec 28, 2018 at 2:11 PM Daniel Drake wrote: > On the Connex L1430 laptop based on Intel Apollo Lake N3350, Linux > doesn't boot. It hangs early on a blank screen. Reproduced with Linus > git, 4.18 and 4.19 (there is no previous known working kernel > version). EFI earlyprintk shows: > >

APIC timer checked before it is set up, boot fails on Connex L1430

Hi, On the Connex L1430 laptop based on Intel Apollo Lake N3350, Linux doesn't boot. It hangs early on a blank screen. Reproduced with Linus git, 4.18 and 4.19 (there is no previous known working kernel version). EFI earlyprintk shows: APIC: switch to symmetric I/O mode setup x2apic: IRQ

Re: [BUG][next-20170619][347de24] PowerPC boot fails with Oops

On Tue, 20 Jun 2017 12:49:25 +0530 Abdul Haleem wrote: > Hi, > > commit: 347de24 (powerpc/64s: implement arch-specific hardlockup > watchdog) > > linux-next fails to boot on PowerPC Bare-metal box. > > Test: boot > Machine type: Power 8 Bare-metal > Kernel:

Re: [BUG][next-20170619][347de24] PowerPC boot fails with Oops

On Tue, 20 Jun 2017 12:49:25 +0530 Abdul Haleem wrote: > Hi, > > commit: 347de24 (powerpc/64s: implement arch-specific hardlockup > watchdog) > > linux-next fails to boot on PowerPC Bare-metal box. > > Test: boot > Machine type: Power 8 Bare-metal > Kernel: 4.12.0-rc5-next-20170619 > gcc:

[BUG][next-20170619][347de24] PowerPC boot fails with Oops

Hi, commit: 347de24 (powerpc/64s: implement arch-specific hardlockup watchdog) linux-next fails to boot on PowerPC Bare-metal box. Test: boot Machine type: Power 8 Bare-metal Kernel: 4.12.0-rc5-next-20170619 gcc: version 4.8.5 In file arch/powerpc/kernel/watchdog.c void

[BUG][next-20170619][347de24] PowerPC boot fails with Oops

Hi, commit: 347de24 (powerpc/64s: implement arch-specific hardlockup watchdog) linux-next fails to boot on PowerPC Bare-metal box. Test: boot Machine type: Power 8 Bare-metal Kernel: 4.12.0-rc5-next-20170619 gcc: version 4.8.5 In file arch/powerpc/kernel/watchdog.c void

Re: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

Stephen Rothwell writes: > On Fri, 16 Jun 2017 11:13:35 +1000 Stephen Rothwell > wrote: >> On Fri, 16 Jun 2017 10:57:22 +1000 Michael Ellerman >> wrote: >> > "Rowand, Frank" writes: >> > > On Thursday,

Re: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

Stephen Rothwell writes: > On Fri, 16 Jun 2017 11:13:35 +1000 Stephen Rothwell > wrote: >> On Fri, 16 Jun 2017 10:57:22 +1000 Michael Ellerman >> wrote: >> > "Rowand, Frank" writes: >> > > On Thursday, June 15, 2017 2:25 AM, Abdul Haleem >> > > [mailto:abdha...@linux.vnet.ibm.com] wrote:

Re: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

Hi all, On Fri, 16 Jun 2017 11:13:35 +1000 Stephen Rothwell wrote: > > On Fri, 16 Jun 2017 10:57:22 +1000 Michael Ellerman > wrote: > > > > "Rowand, Frank" writes: > > > > > On Thursday, June 15, 2017 2:25 AM, Abdul Haleem

Re: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

Hi all, On Fri, 16 Jun 2017 11:13:35 +1000 Stephen Rothwell wrote: > > On Fri, 16 Jun 2017 10:57:22 +1000 Michael Ellerman > wrote: > > > > "Rowand, Frank" writes: > > > > > On Thursday, June 15, 2017 2:25 AM, Abdul Haleem > > > [mailto:abdha...@linux.vnet.ibm.com] wrote: > > >> > >

Re: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

Hi Michael, On Fri, 16 Jun 2017 10:57:22 +1000 Michael Ellerman wrote: > > "Rowand, Frank" writes: > > > On Thursday, June 15, 2017 2:25 AM, Abdul Haleem > > [mailto:abdha...@linux.vnet.ibm.com] wrote: > >> > >> On Thu, 2017-06-15 at 11:30 +0530,

Re: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

Hi Michael, On Fri, 16 Jun 2017 10:57:22 +1000 Michael Ellerman wrote: > > "Rowand, Frank" writes: > > > On Thursday, June 15, 2017 2:25 AM, Abdul Haleem > > [mailto:abdha...@linux.vnet.ibm.com] wrote: > >> > >> On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote: > >>> > >>>

RE: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

"Rowand, Frank" writes: > On Thursday, June 15, 2017 2:25 AM, Abdul Haleem > [mailto:abdha...@linux.vnet.ibm.com] wrote: >> >> On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote: >>> Hi, >>> >>> linux-next fails to boot on powerpc Bare-metal with these warnings. >>>

RE: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

"Rowand, Frank" writes: > On Thursday, June 15, 2017 2:25 AM, Abdul Haleem > [mailto:abdha...@linux.vnet.ibm.com] wrote: >> >> On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote: >>> Hi, >>> >>> linux-next fails to boot on powerpc Bare-metal with these warnings. >>> >>> machine booted fine

Re: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

On Thu, 2017-06-15 at 17:06 +, Rowand, Frank wrote: > On Thursday, June 15, 2017 2:25 AM, Abdul Haleem > [mailto:abdha...@linux.vnet.ibm.com] wrote: > > > > On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote: > > > Hi, > > > > > > linux-next fails to boot on powerpc Bare-metal with

Re: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

On Thu, 2017-06-15 at 17:06 +, Rowand, Frank wrote: > On Thursday, June 15, 2017 2:25 AM, Abdul Haleem > [mailto:abdha...@linux.vnet.ibm.com] wrote: > > > > On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote: > > > Hi, > > > > > > linux-next fails to boot on powerpc Bare-metal with

RE: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

On Thursday, June 15, 2017 2:25 AM, Abdul Haleem [mailto:abdha...@linux.vnet.ibm.com] wrote: > > On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote: >> Hi, >> >> linux-next fails to boot on powerpc Bare-metal with these warnings. >> >> machine booted fine on next-20170613 > > Thanks Michael,

RE: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

On Thursday, June 15, 2017 2:25 AM, Abdul Haleem [mailto:abdha...@linux.vnet.ibm.com] wrote: > > On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote: >> Hi, >> >> linux-next fails to boot on powerpc Bare-metal with these warnings. >> >> machine booted fine on next-20170613 > > Thanks Michael,

Re: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote: > Hi, > > linux-next fails to boot on powerpc Bare-metal with these warnings. > > machine booted fine on next-20170613 Thanks Michael, Yes it is (75fe04e59 of: remove *phandle properties from expanded device tree) Frank, would you please

Re: [Oops][next-20170614][] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

On Thu, 2017-06-15 at 11:30 +0530, Abdul Haleem wrote: > Hi, > > linux-next fails to boot on powerpc Bare-metal with these warnings. > > machine booted fine on next-20170613 Thanks Michael, Yes it is (75fe04e59 of: remove *phandle properties from expanded device tree) Frank, would you please

[Oops][next-20170614] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

Hi, linux-next fails to boot on powerpc Bare-metal with these warnings. machine booted fine on next-20170613 Test: Boot Machine type: Power8 Bare-metal Kernel : 4.12.0-rc5-next-20170614 config: attached Trace logs: --- numa: NODE_DATA [mem 0x3fff50a300-0x3fff513fff] numa:

[Oops][next-20170614] powerpc boot fails with WARNING: CPU: 12 PID: 0 at mm/memblock.c

Hi, linux-next fails to boot on powerpc Bare-metal with these warnings. machine booted fine on next-20170613 Test: Boot Machine type: Power8 Bare-metal Kernel : 4.12.0-rc5-next-20170614 config: attached Trace logs: --- numa: NODE_DATA [mem 0x3fff50a300-0x3fff513fff] numa:

3.9-rc0: Boot fails: RIP: 0010:[] [] stop_machine_cpu_stop+0x8a/0x160

Hi All, Current tip (with last commit id: c41b3810c09e60664433548c5218cc6ece6a8903 (Merge tag 'pm+acpi-fixes-3.9-rc1') fails to boot with: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.8.0-rc0-20130226

3.9-rc0: Boot fails: RIP: 0010:[ffffffff810d4e9a] [ffffffff810d4e9a] stop_machine_cpu_stop+0x8a/0x160

Hi All, Current tip (with last commit id: c41b3810c09e60664433548c5218cc6ece6a8903 (Merge tag 'pm+acpi-fixes-3.9-rc1') fails to boot with: [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.8.0-rc0-20130226

Re: [PATCH] mfd: arizona: Error out if initial boot fails

Hi Mark, On Mon, Jul 09, 2012 at 11:56:43AM +0100, Mark Brown wrote: > Signed-off-by: Mark Brown > --- > drivers/mfd/arizona-core.c |6 +- > 1 file changed, 5 insertions(+), 1 deletion(-) Applied, thanks. Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ --

[PATCH] mfd: arizona: Error out if initial boot fails

Signed-off-by: Mark Brown --- drivers/mfd/arizona-core.c |6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c index ed2de7b..011d80e 100644 --- a/drivers/mfd/arizona-core.c +++ b/drivers/mfd/arizona-core.c @@ -418,7

[PATCH] mfd: arizona: Error out if initial boot fails

Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com --- drivers/mfd/arizona-core.c |6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/drivers/mfd/arizona-core.c b/drivers/mfd/arizona-core.c index ed2de7b..011d80e 100644 --- a/drivers/mfd/arizona-core.c +++

Re: [PATCH] mfd: arizona: Error out if initial boot fails

Hi Mark, On Mon, Jul 09, 2012 at 11:56:43AM +0100, Mark Brown wrote: Signed-off-by: Mark Brown broo...@opensource.wolfsonmicro.com --- drivers/mfd/arizona-core.c |6 +- 1 file changed, 5 insertions(+), 1 deletion(-) Applied, thanks. Cheers, Samuel. -- Intel Open Source Technology

Boot fails with 2.6.20-rc3 / git-current Was: 2.6.20-rc3: Clocksource tsc unstable

On Fri, Mar 09, 2007 at 06:41:45PM +0100, Jiri Slaby wrote: > Hi. > > I got this message after suspend;resume on my notebook > Clocksource tsc unstable (delta = -154983451 ns) > I am getting the exact same line on bootup on my Fujitsu Siemens Lifebook E8110. After that line the boot halts with

Boot fails with 2.6.20-rc3 / git-current Was: 2.6.20-rc3: Clocksource tsc unstable

On Fri, Mar 09, 2007 at 06:41:45PM +0100, Jiri Slaby wrote: Hi. I got this message after suspend;resume on my notebook Clocksource tsc unstable (delta = -154983451 ns) I am getting the exact same line on bootup on my Fujitsu Siemens Lifebook E8110. After that line the boot halts with

Re: 2.4.5-ac6 and 2.4.4-ac11 boot fails with APIC timer

On Sat, 16 Jun 2001 11:27:53 +0900, <[EMAIL PROTECTED]> wrote: >> The message on the screen >> >> calibrating APIC timer . >> CPU clock speed is 1395.7390MHz >> ... host bus clock speed is 0. MHz >> cpu: 0, clocks: 0, slic: 0 >> >> Then nothing. I had to push the reset button

Re: 2.4.5-ac6 and 2.4.4-ac11 boot fails with APIC timer

On Sat, 16 Jun 2001 11:27:53 +0900, [EMAIL PROTECTED] wrote: The message on the screen calibrating APIC timer . CPU clock speed is 1395.7390MHz ... host bus clock speed is 0. MHz cpu: 0, clocks: 0, slic: 0 Then nothing. I had to push the reset button at this point.

Re: 2.4.5-ac6 and 2.4.4-ac11 boot fails with APIC timer

> The message on the screen > > calibrating APIC timer . > CPU clock speed is 1395.7390MHz > ... host bus clock speed is 0. MHz > cpu: 0, clocks: 0, slic: 0 > > Then nothing. I had to push the reset button at this point. > ACPI and APM were disabled from the kernel config. >

Re: 2.4.5-ac6 and 2.4.4-ac11 boot fails with APIC timer

The message on the screen calibrating APIC timer . CPU clock speed is 1395.7390MHz ... host bus clock speed is 0. MHz cpu: 0, clocks: 0, slic: 0 Then nothing. I had to push the reset button at this point. ACPI and APM were disabled from the kernel config. This

2.4.5-ac6 and 2.4.4-ac11 boot fails with APIC timer

The message on the screen calibrating APIC timer . CPU clock speed is 1395.7390MHz ... host bus clock speed is 0. MHz cpu: 0, clocks: 0, slic: 0 Then nothing. I had to push the reset button at this point. ACPI and APM were disabled from the kernel config. This boot failure

2.4.5-ac6 and 2.4.4-ac11 boot fails with APIC timer

The message on the screen calibrating APIC timer . CPU clock speed is 1395.7390MHz ... host bus clock speed is 0. MHz cpu: 0, clocks: 0, slic: 0 Then nothing. I had to push the reset button at this point. ACPI and APM were disabled from the kernel config. This boot failure

Boot fails in Avanti AS 400 4/233, include boot log and sysrq dump

Hello, I compiled both kernel versions 2.4.2-pre4 and 2.4.1-ac18 on my Alpha Station 400 4/233 and both stop when they are start init. I include the boot log and sysrq dumps for 2.4.1-ac18, I passed init=/bin/bash as kernel parameter. I'd appreciate any help. Thanks. -- Rafael Linux

Boot fails in Avanti AS 400 4/233, include boot log and sysrq dump

Hello, I compiled both kernel versions 2.4.2-pre4 and 2.4.1-ac18 on my Alpha Station 400 4/233 and both stop when they are start init. I include the boot log and sysrq dumps for 2.4.1-ac18, I passed init=/bin/bash as kernel parameter. I'd appreciate any help. Thanks. -- Rafael Linux

Re: boot fails with test9-pre3 and above

Looks that the scsi changes introduced in test9-pre3 broke the functioning of "scsihosts" that can be specified from lilo.conf In my kernel, I had ncr53c896 and aic7xxx compiled in and was using append = "scsihosts=ncr53c8xx" in /etc/lilo.conf as the boot disk was on ncr controller.

Re: boot fails with test9-pre3 and above

Looks that the scsi changes introduced in test9-pre3 broke the functioning of "scsihosts" that can be specified from lilo.conf In my kernel, I had ncr53c896 and aic7xxx compiled in and was using append = "scsihosts=ncr53c8xx" in /etc/lilo.conf as the boot disk was on ncr controller.

Re: boot fails with test9-pre3 and above

On Sun, 24 Sep 2000 17:43:29 -0700 (PDT), [EMAIL PROTECTED] (Prasanna Narayana) wrote: >In our Dell 8-way 1gb machine, test9-pre3 and above kernel >doesn't boot (test9-pre2 boots ok). I just get the message > Loading 2.4test8 > Uncompressing Linux... ok, booting the

boot fails with test9-pre3 and above

Hi, In our Dell 8-way 1gb machine, test9-pre3 and above kernel doesn't boot (test9-pre2 boots ok). I just get the message Loading 2.4test8 Uncompressing Linux... ok, booting the kernel. Verified that the same bzImage boots correctly on another 2-way machine. Let

boot fails with test9-pre3 and above

Hi, In our Dell 8-way 1gb machine, test9-pre3 and above kernel doesn't boot (test9-pre2 boots ok). I just get the message Loading 2.4test8 Uncompressing Linux... ok, booting the kernel. Verified that the same bzImage boots correctly on another 2-way machine. Let

Re: boot fails with test9-pre3 and above

On Sun, 24 Sep 2000 17:43:29 -0700 (PDT), [EMAIL PROTECTED] (Prasanna Narayana) wrote: In our Dell 8-way 1gb machine, test9-pre3 and above kernel doesn't boot (test9-pre2 boots ok). I just get the message Loading 2.4test8 Uncompressing Linux... ok, booting the

Boot fails

Hello, Trying kernel 2.4.0-test9-pre3 and 2.4.0-test9-pre4 results in kernel panic with AIC-7890... Regards -- Angel Luis Uruñuela <> Unix Systems Administrator "You can't change the past, but you can ruin the present by worrying over the future" - To unsubscribe from this list: send

Boot fails

Hello, Trying kernel 2.4.0-test9-pre3 and 2.4.0-test9-pre4 results in kernel panic with AIC-7890... Regards -- Angel Luis Uruñuela Unix Systems Administrator "You can't change the past, but you can ruin the present by worrying over the future" - To unsubscribe from this list: send