/init: 64: Syntax error: 0x

Bug #21922 reported by JasonCohen
30
Affects Status Importance Assigned to Milestone
initramfs-tools (Ubuntu)
Fix Released
Critical
Jeff Bailey

Bug Description

After upgrading from Hoary to Breezy with a dist-upgrade in Synpatic, I get a
kernel Panic when using either the 386 or K7 2.6.12 kernel image. The kernel
panic reads "init64: Syntax error: 0x [4294677.238000] Kernel panic- not
syncing- Attempting to kill init!" 2.6.10 continues to work without issue.

System Information:
CPU: AMD 64 3000+
Motherboard: ECS K8M800-M2 Motherboard
RAM: 512 MB Corsair PC3200 DDR

Revision history for this message
Thomas Markus (thomas-markus) wrote :

I am having the same issue having installed all the updates to this moment.

The "init64:" part of the previous post should read: "/init: 64" And above this
error additional information is printed:

"Valid format sequences for file systems:
%a free blocks available to non-superuser
%b ...
%c ...
.
.
."

Revision history for this message
Thomas Markus (thomas-markus) wrote :

The error message mentioned above the init error seems to be generated by the
"stat" command which is in coreutils.
It seems the wrong arguments are passed the this command.

Revision history for this message
Ben Collins (ben-collins) wrote :

The kernel should be able to handle bad data being passed from userspace. Maybe amd64's 32-bit->64-bit
translation for the stat() syscall is broken.

Revision history for this message
Thomas Markus (thomas-markus) wrote :

(In reply to comment #3)
> Maybe amd64's 32-bit->64-bit
> translation for the stat() syscall is broken.

Not very likely.
I am having the same problem with the 686-smp kernel.
On a dual-p3

---

0000:00:00.0 Host bridge: Intel Corp. 82840 840 (Carmel) Chipset Host Bridge
(Hub A) (rev 01)
0000:00:01.0 PCI bridge: Intel Corp. 82840 840 (Carmel) Chipset AGP Bridge (rev 01)
0000:00:1e.0 PCI bridge: Intel Corp. 82801AA PCI Bridge (rev 02)
0000:00:1f.0 ISA bridge: Intel Corp. 82801AA ISA Bridge (LPC) (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 82801AA IDE (rev 02)
0000:00:1f.2 USB Controller: Intel Corp. 82801AA USB (rev 02)
0000:00:1f.3 SMBus: Intel Corp. 82801AA SMBus (rev 02)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801AA AC'97 Audio (rev 02)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600]
0000:01:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600]
(Secondary)
0000:02:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
0000:02:07.0 SCSI storage controller: Adaptec AIC-7892P U160/m (rev 02)
0000:02:09.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 08)
0000:02:0a.0 Multimedia video controller: Brooktree Corporation Bt878 Video
Capture (rev 11)
0000:02:0a.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture
(rev 11)
0000:02:0b.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 50)
0000:02:0b.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 50)
0000:02:0b.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)

---

Revision history for this message
JasonCohen (jcohen07) wrote :
Download full text (50.6 KiB)

I wasn't sure what hardware info was pertinent so I'll paste everything:

============ start debug info ============
libhd version 8.38u (ia32)
kernel version is 2.6
----- /proc/cmdline -----
  root=/dev/hda2 ro quiet splash
----- /proc/cmdline end -----
debug = 0xff7ffff7
probe = 0x138fe4be17fffdfffe (+memory +pci +isapnp +net +floppy +misc
+misc.serial +misc.par +misc.floppy +serial +cpu +bios +monitor +mouse +scsi
+usb -usb.mods +adb +modem +modem.usb +parallel +parallel.lp +parallel.zip +isa
+isa.isdn +isdn +kbd +prom +sbus +int +braille +braille.alva +braille.fhp
+braille.ht -ignx11 +sys -bios.vbe -isapnp.old -isapnp.new -isapnp.mod
+braille.baum +manual +fb +veth +pppoe -scan +pcmcia -fork -parallel.imm +s390
-cpuemu -sysfs +s390disks +udev +block +block.cdrom +block.part +edd +edd.mod
-bios.ddc -bios.fb -bios.mode +input +block.mods +bios.vesa -max -lxrc +dsl)
shm: attached segment 5636119 at 0xb7e5b000
>> floppy.1: get nvram
>> floppy.2: klog info
>> bios.1: cmdline
>> bios.1.1: apm
>> bios.2: ram
  bios: 0 disks
>> bios.2: rom
>> bios.3: smp
----- BIOS data 0x00400 - 0x004ff -----
  400 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  410 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  420 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  430 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  440 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  450 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  460 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  470 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  480 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  490 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  4a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  4b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  4c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  4d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  4e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
  4f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 "................"
----- BIOS data end -----
>> bios.4: vbe
VBE: Could not init Int10
>> bios.5: 32
>> sys.1: cpu
vmware check: 0
>> misc.9: kernel log
----- kernel log -----
  <6>NET: Registered protocol family 1
  <6>Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
  <6>ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
  <6>VP_IDE: IDE controller at PCI slot 0000:00:0f.1
  <4>ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20
  <6>ACPI: PCI interrupt 0000:00:0f.1[A] -> GSI 20 (level, low) -> IRQ 20
  <6>VP_IDE: chipset revision 6
  <6>VP_IDE: not 100% native mode: will probe irqs later
  <6>VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
  <6> ide0: BM-DMA at 0xc800-0xc807, BIOS settings: hda:pio, hdb:pio
  <6> ide1: BM-DMA at 0xc808-0xc80f, BIOS settings: hdc:pio, hdd:pio
  <7>Probing IDE interface ide0...
  <4>hda: ST3160023A, ATA DIS...

Revision history for this message
JasonCohen (jcohen07) wrote :
Download full text (31.2 KiB)

----- udevinfo end -----
>> int.13: device names
>> int.14: soft raid
----- soft raid devices -----
----- soft raid devices end -----
----- /proc/modules -----
  udf 77060 1 - Live 0xe0c2f000
  rfcomm 36252 0 - Live 0xe0c25000
  l2cap 24324 5 rfcomm, Live 0xe0c1e000
  bluetooth 46340 4 rfcomm,l2cap, Live 0xe0c11000
  ipv6 229376 8 - Live 0xe0c45000
  speedstep_lib 4228 0 - Live 0xe0bff000
  proc_intf 4100 0 - Live 0xe0bfc000
  freq_table 4100 0 - Live 0xe0bf9000
  cpufreq_userspace 4572 0 - Live 0xe0bf6000
  cpufreq_ondemand 6172 0 - Live 0xe0bf3000
  cpufreq_powersave 1920 0 - Live 0xe0a3c000
  video 16260 0 - Live 0xe0bee000
  sony_acpi 6280 0 - Live 0xe0be4000
  pcc_acpi 11264 0 - Live 0xe0bca000
  button 6800 0 - Live 0xe0bdd000
  battery 10244 0 - Live 0xe0b97000
  container 4608 0 - Live 0xe0bbe000
  ac 4996 0 - Live 0xe0bbb000
  af_packet 20744 2 - Live 0xe0bc3000
  tsdev 7488 0 - Live 0xe0b9b000
  floppy 54864 0 - Live 0xe0bce000
  pcspkr 3816 0 - Live 0xe0948000
  rtc 12216 0 - Live 0xe0b93000
  via_rhine 19972 0 - Live 0xe0bb5000
  mii 4736 1 via_rhine, Live 0xe0b90000
  snd_seq_oss 30080 0 - Live 0xe0bac000
  snd_seq_midi 8224 0 - Live 0xe0ab9000
  snd_seq_midi_event 7424 2 snd_seq_oss,snd_seq_midi, Live 0xe0ab6000
  snd_seq 46992 5 snd_seq_oss,snd_seq_midi,snd_seq_midi_event, Live 0xe0b9f000
  snd_via82xx 25248 1 - Live 0xe0b11000
  snd_ac97_codec 64608 1 snd_via82xx, Live 0xe0adb000
  snd_pcm_oss 47652 0 - Live 0xe0b04000
  snd_mixer_oss 16768 1 snd_pcm_oss, Live 0xe0ad5000
  snd_pcm 84872 3 snd_via82xx,snd_ac97_codec,snd_pcm_oss, Live 0xe0aee000
  snd_timer 23300 2 snd_seq,snd_pcm, Live 0xe0abf000
  snd_page_alloc 9604 2 snd_via82xx,snd_pcm, Live 0xe0a75000
  gameport 4608 1 snd_via82xx, Live 0xe0a39000
  snd_mpu401_uart 7168 1 snd_via82xx, Live 0xe0a36000
  snd_rawmidi 22944 2 snd_seq_midi,snd_mpu401_uart, Live 0xe0a6e000
  snd_seq_device 8332 4 snd_seq_oss,snd_seq_midi,snd_seq,snd_rawmidi, Live
0xe094f000
  snd 50276 13
snd_seq_oss,snd_seq,snd_via82xx,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device,
Live 0xe0ac7000
  soundcore 9824 1 snd, Live 0xe094b000
  i2c_viapro 7436 0 - Live 0xe0941000
  i2c_core 21264 1 i2c_viapro, Live 0xe0a67000
  usbhid 29376 0 - Live 0xe0a5e000
  ehci_hcd 29444 0 - Live 0xe0a55000
  usblp 12032 2 - Live 0xe08f0000
  uhci_hcd 30224 0 - Live 0xe0a2d000
  usbcore 107384 7 usbhid,ehci_hcd,usblp,uhci_hcd, Live 0xe0a9a000
  sata_via 8196 0 - Live 0xe08f4000
  libata 44548 1 sata_via, Live 0xe0a21000
  scsi_mod 119936 1 libata, Live 0xe0a7b000
  shpchp 86116 0 - Live 0xe0a3e000
  pci_hotplug 30512 1 shpchp, Live 0xe09f6000
  amd64_agp 10952 1 - Live 0xe08dd000
  agpgart 31784 1 amd64_agp, Live 0xe09ed000
  vfat 12928 0 - Live 0xe08eb000
  fat 37792 1 vfat, Live 0xe0936000
  nls_cp437 5888 1 - Live 0xe08da000
  ntfs 97136 1 - Live 0xe0953000
  dm_mod 53116 1 - Live 0xe0928000
  evdev 9088 0 - Live 0xe0897000
  capability 5000 0 - Live 0xe0894000
  commoncap 7808 1 capability, Live 0xe086f000
  psmouse 19336 0 - Live 0xe08c8000
  mousedev 11160 1 - Live 0xe085e000
  parport_pc 34372 1 - Live 0xe08e1000
  lp 10792 0 - Live 0xe085a000
  parport 33480 2 par...

Revision history for this message
Matt Zimmerman (mdz) wrote :

*** Bug 21985 has been marked as a duplicate of this bug. ***

Revision history for this message
Jeff Bailey (jbailey) wrote :

This should be fixed now with initramfs-tools 0.27. Once you have that
installed, please do:

dpkg-reconfigure linux-image-2.6.12-8-686

(Replacing that with the appropriate kernel flavour as needed).

Thanks!

Revision history for this message
JasonCohen (jcohen07) wrote :

(In reply to comment #8)
> This should be fixed now with initramfs-tools 0.27. Once you have that
> installed, please do:
>
> dpkg-reconfigure linux-image-2.6.12-8-686
>
> (Replacing that with the appropriate kernel flavour as needed).
>
> Thanks!

This appears to have fixed the problem. I can now use the 2.6.12-8-686 kernel.

Revision history for this message
JasonCohen (jcohen07) wrote :

It appears I spoke to soon. While the 2.6.12-8-686 kernel works, I still get the
same kernel panic with the 2.6.12-8-386 kernel.

This is probably a side issue, but there seems to be an awfully long pause
before the initial boot screen goes to the new Ubuntu splash screen- perhaps
10-15 seconds.

Revision history for this message
Jeff Bailey (jbailey) wrote :

(In reply to comment #10)
> It appears I spoke to soon. While the 2.6.12-8-686 kernel works, I still get the
> same kernel panic with the 2.6.12-8-386 kernel.

You made sure to regenerate the initramfs for that one, too, right? They each
have their own initrd.img file.

> This is probably a side issue, but there seems to be an awfully long pause
> before the initial boot screen goes to the new Ubuntu splash screen- perhaps
> 10-15 seconds.

Probably best to keep the two issues separate for now. =)

Revision history for this message
JasonCohen (jcohen07) wrote :

Yes, I ran "dpkg-reconfigure linux-image-2.6.12-8-386" before restarting and
again after the kernel panic to make sure that the package was reconfigured
successfully. It showed some output displaying the .img files of the 386 kernel,
as if it was adding the kernel to Grub. In both cases, I received a kernel panic
when I tried to load the 386 kernel. Would it help to purge and reinstall
linux-image-2.6.12-8-386?

Revision history for this message
JasonCohen (jcohen07) wrote :

I installed linux-686 AFTER installing the new initramfs-tools package. That
might explain why the 686 kernel works, but the 386 doesn't. Is it enough to run
dpkg-reconfigure, or is there another step I'm missing?

Revision history for this message
Thomas Markus (thomas-markus) wrote :

(In reply to comment #8)
> This should be fixed now with initramfs-tools 0.27. Once you have that
> installed, please do:
>
> dpkg-reconfigure linux-image-2.6.12-8-686-smp

The problem is now gone, and the system boots fine. Although I too have a long
pause which is probably related to searching for scsi disk which I do not have
in my system.

Revision history for this message
Jeff Bailey (jbailey) wrote :

(In reply to comment #13)
> I installed linux-686 AFTER installing the new initramfs-tools package. That
> might explain why the 686 kernel works, but the 386 doesn't. Is it enough to run
> dpkg-reconfigure, or is there another step I'm missing?

Yes, but make sure you're running dpkg-reconfigure on the full name of the
kernel image, so:

linux-image-2.6.12-8-386

reconfiguring anything else won't do it. We'll shortly have a better way, but
it's not quite there yet.

It looks like this is generally working, though. Closing this bug as fixed.

Tks,
Jeff Bailey

Revision history for this message
Ben Collins (ben-collins) wrote :

*** Bug 22183 has been marked as a duplicate of this bug. ***

Revision history for this message
JasonCohen (jcohen07) wrote :

I purged the linux-image-2.6.12-8-386 package and re-installed it. It now boots
fine.

Revision history for this message
Matt Zimmerman (mdz) wrote :

(In reply to comment #14)
> (In reply to comment #8)
> > This should be fixed now with initramfs-tools 0.27. Once you have that
> > installed, please do:
> >
> > dpkg-reconfigure linux-image-2.6.12-8-686-smp
>
> The problem is now gone, and the system boots fine. Although I too have a long
> pause which is probably related to searching for scsi disk which I do not have
> in my system.
>

Yes, that pause is hardware detection happening. We plan to bring up the
progress meter earlier in the future, but not for 5.10.

You can avoid the pause by disabling your SCSI controller if you aren't using it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.