[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#454776: marked as done (linux-image-2.6.22-3-486: Does not boot on Vortex86SX)

Your message dated Thu, 8 May 2008 21:53:57 +0200
with message-id <56f6ed4a0805081253p41e1cb7en81c3278e02924a5@mail.gmail.com>
and subject line Re: Bug#454776: linux-image-2.6.22-3-486: Does not boot on Vortex86SX
has caused the Debian Bug report #454776,
regarding linux-image-2.6.22-3-486: Does not boot on Vortex86SX
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
454776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454776
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.22-3-486
Version: 2.6.22-6
Severity: important

The Linux kernel with 486 flavour should run on each Intel-based
hardware. The current Debian's Linux kernel does not run on Vortex86SX
hardware.

The Vortex86SX is a cheap System on Chip, which provides CPU
compatible with 486SX (without FPU). It does run on Debian's Linux
kernel 2.6.18 from Etch. It crashed after boot with Sid kernel.

The output from console:

Checking 'hlt' instruction... OK.
invalid opcode: 0000 [#1]
Modules linked in:
CPU:    0
EIP:    0060:[<c0108bea>]    Not tainted VLI
EFLAGS: 00000046   (2.6.22-3-486 #1)
EIP is at apply_paravirt+0x4c/0x52
eax: 00000001   ebx: c0390e04   ecx: 00000000   edx: 00000000
esi: c0390e04   edi: c1100572   ebp: c0366520   esp: c0343fc4
ds: 007b   es: 007b   fs: 0000  fs: 0000  ss: 0068
Process swapper (pid: 0, ti=c0342000 task=c031a2c0 task.ti=c0342000)
Stack: c011481d 00000293 c0366592 c034b2e8 ffffffff c0344a89 00000036 c03443dc
       00000000 c0366520 00000000 00099800 c033c000 007f3007 00000000
Call Trace:
 [<c011481d>] end_irq_disable+0x0/0x1
 [<c034b2e8>] alternative_instructions+0x3f/0x4d
 [<c0344a89>] start_kernel+0x283/0x295
 [<c03443dc>] unknown_bootoption+0x0/0x202
 =======================
Code: 0c 24 8b 0b ff 15 d0 0f 32 c0 0f b6 53 05 39 d0 76 04 0f 0b eb fe 29 c2 03
 03 83 c3 08 e8 b5 ff ff ff 39 f3 72 cd b8 01 00 00 00 <0f> a2 58 5b 5e c3 55 89
 d5 57 56 53 c3 83 ec 14 83 3d f0 6f
EIP: [<c0108bea>] apply_paravirt+0x4c/0x52 SS:ESP 0068:c0343fc4
Kernel panic - not syncing: Attempted to kill idle task!


The system crash is caused by CONFIG_PARAVIRT option. I recompiled the
486 flavour kernel without CONFIG_PARAVIRT and it works correctly.

I think this option should be removed from 486 flavour.

-- 
 .''`.    Piotr Roszatycki
: :' :    mailto:Piotr.Roszatycki@gmail.com
`. `'     mailto:dexter@debian.org
  `-

--- End Message ---
--- Begin Message --- 
The Vortex86SX boots with 2.6.24-1-486 properly if
"noreplace-paravirt" option is added to boot parameters.

2008/2/7 Piotr Roszatycki <piotr.roszatycki@gmail.com>:
> The linux-image-2.6.24-1-486 does not boot on Vortex86SX platform. It
> hangs up on apply_paravirt, so I think we have a regression.


-- 
 .''`. Piotr Roszatycki
: :' : mailto:Piotr.Roszatycki@gmail.com
`. `' mailto:dexter@debian.org
 `-

--- End Message ---
Reply to: