reboot problem

reboot problem

[Ming Li]

Hi,

My name is Sam, I found your email address at MAINTAINERS of SuSE 10.1.

I met a problem when I reboot the Radiant machine, it just halt when
rebooting after shutdown all the resources.

I did some research, the reason is the SuSE linux 10.1 Set the low to the
reset of keyboard controller, but unfortunately, there is not keyboard
controller in Radiant machine, so bios can not start the POST code.

Firstly, I added the parameter "reboot=bios" in /boot/grub/menu.lst, try to
let reboot using bios post, it does work, I do not know why ?

Secondly, I built a new kernel added some debug information in file
/usr/src/linux/arch/i386/kernel/reboot.c,  I added debug information in
functions "machine_restart()" , "machine_real_restart()", "reboot_setup()" ,
but when I running command "reboot", I did not see my debug information,
what I was try to do is to call the function: "machine_real_restart()", but
it seems to me that, functions of reboot.c do not be call during the
rebooting. 

Thirdly, I check the command "reboot" in /sbin, it just the symbol link to
the command "halt", I am little bit confused.

My question is :

1. where is the reboot source code, what files are actually do the rebooting
work ?
2. Why command "reboot" command is just a symbol link to the command "halt"
?
3. What can I do to reboot machine by bios mode ?

Thank you very much, I appreciate your time.

Regards,
Sam.

RE: Reboot Problem

[Chaitra Gorantla]

Hi,

Yes, Insipte of adding
kernel.panic = 10
in sysctl.conf,
the kernel does not reboot when kvm-i9ntel.ko is been inserted.

Do you have any idea , because, when the kvm-intel.ko is not inserted, kernel reboots.


-----Original Message-----
From: Sterling Windmill [mailto:sterling@ampx.net]
Sent: Monday, June 07, 2010 8:49 AM
To: Chaitra Gorantla
Cc: kvm@vger.kernel.org
Subject: Re: Reboot Problem

The Linux kernel does not reboot on panic by default.

Read here: http://www.cyberciti.biz/tips/reboot-linux-box-after-a-kernel-panic.html

----- Original Message -----
From: "Chaitra Gorantla" <Chaitra.Gorantla@lntinfotech.com>
To: kvm@vger.kernel.org
Sent: Sunday, June 6, 2010 10:59:11 PM
Subject: Reboot Problem

Hi all,

We know that kernel reboots after any panic or crash.

I am using 2.6.21 kernel (HOST machine) and KVM-88 package.

After inserting kvm-intel.ko , if any kernel crash occurs, the Host
halts= .
The kernel never reboots.

Please suggest regarding this.

Thanks in advance,
Chaitra


This Email may contain confidential or privileged information for the
intended recipient (s) If you are not the intended recipient, please do
not use or disseminate the information, notify the sender and delete it
from your system.

______________________________________________________________________
-- To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

______________________________________________________________________

This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

______________________________________________________________________

Re: Reboot Problem

[Sterling Windmill]

The Linux kernel does not reboot on panic by default.

Read here: http://www.cyberciti.biz/tips/reboot-linux-box-after-a-kernel-panic.html

----- Original Message -----
From: "Chaitra Gorantla" <Chaitra.Gorantla@lntinfotech.com>
To: kvm@vger.kernel.org
Sent: Sunday, June 6, 2010 10:59:11 PM
Subject: Reboot Problem

Hi all,

We know that kernel reboots after any panic or crash.

I am using 2.6.21 kernel (HOST machine) and KVM-88 package.

After inserting kvm-intel.ko , if any kernel crash occurs, the Host
halts= .
The kernel never reboots.

Please suggest regarding this.

Thanks in advance,
Chaitra


This Email may contain confidential or privileged information for the
intended recipient (s) If you are not the intended recipient, please do
not use or disseminate the information, notify the sender and delete it
from your system.

______________________________________________________________________
-- To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Reboot Problem

[Chaitra Gorantla]

Hi all,

We know that kernel reboots after any panic or crash.

I am using 2.6.21 kernel (HOST machine) and KVM-88 package.

After inserting kvm-intel.ko , if any kernel crash occurs,  the Host halts= .
The kernel never reboots.

Please suggest regarding this.

Thanks in advance,
Chaitra


This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

______________________________________________________________________

Re: reboot problem

[Jonathan E Brassow]

[-- Attachment #1.1: Type: text/plain, Size: 1251 bytes --]

Device Mapper does not remember the tables you have created across 
reboots.  For persistent volume creation, I would use LVM2.

If you must use device mapper, you could create an init script that 
creates the devices you've mentioned and mounts "v2".  Be forewarned, 
Linux can reorder block devices, so hard-coding block device names in 
your init script may result in mapping the wrong device(s).  (LVM2 gets 
around this by writing labels to the devices, so that it can identify 
the proper devices and assemble them in the correct order.)

  brassow

On Oct 29, 2006, at 8:01 PM, ~{KNUq;*~} wrote:

> Hi all:
> 	I'm a beginner to Device Mapper, now I have a problem perhaps stupid.
> 	However, I have made a mapped device named "v1" with table "t1", then 
> I made a mapped device named "v2" with table "t2" using "v1" as the 
> targed device, and mount "/dev/mapper/v2" at "/mnt/vd".
> 	Now I hope that after reboot there are still "v1","v2" and "v2" will 
> be still mounted at "/mnt/vd". How should I do for these? Thanks!
>
> ~{!!!!!!!!!!!!!!!!~}Song Zhenhua
> ~{!!!!!!!!!!!!!!!!~}songzhh81@163.com
> ~{!!!!!!!!!!!!!!!!!!!!~}2006-10-30
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

[-- Attachment #1.2: Type: text/enriched, Size: 1502 bytes --]

Device Mapper does not remember the tables you have created across
reboots.  For persistent volume creation, I would use LVM2.


If you must use device mapper, you could create an init script that
creates the devices you've mentioned and mounts "v2".  Be forewarned,
Linux can reorder block devices, so hard-coding block device names in
your init script may result in mapping the wrong device(s).  (LVM2
gets around this by writing labels to the devices, so that it can
identify the proper devices and assemble them in the correct order.)


 brassow


On Oct 29, 2006, at 8:01 PM,
<fontfamily><param>Hiragino Kaku Gothic Pro</param>~{KNUq~}</fontfamily><fontfamily><param>STHeiti</param>~{;*~}</fontfamily>
wrote:


<excerpt>Hi all:

	I'm a beginner to Device Mapper, now I have a problem perhaps stupid. 

	However, I have made a mapped device named "v1" with table "t1", then
I made a mapped device named "v2" with table "t2" using "v1" as the
targed device, and mount "/dev/mapper/v2" at "/mnt/vd". 

	Now I hope that after reboot there are still "v1","v2" and "v2" will
be still mounted at "/mnt/vd". How should I do for these? Thanks!


<fontfamily><param>STHeiti</param>~{!!!!!!!!!!!!!!!!~}</fontfamily>Song Zhenhua

<fontfamily><param>STHeiti</param>~{!!!!!!!!!!!!!!!!~}</fontfamily>songzhh81@163.com

<fontfamily><param>STHeiti</param>~{!!!!!!!!!!!!!!!!!!!!~}</fontfamily>2006-10-30


--

dm-devel mailing list

dm-devel@redhat.com

https://www.redhat.com/mailman/listinfo/dm-devel


</excerpt>

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]

reboot problem

[宋振华]

Hi all:
	I'm a beginner to Device Mapper, now I have a problem perhaps stupid. 
	However, I have made a mapped device named "v1" with table "t1", then I made a mapped device named "v2" with table "t2" using "v1" as the targed device, and mount "/dev/mapper/v2" at "/mnt/vd". 
	Now I hope that after reboot there are still "v1","v2" and "v2" will be still mounted at "/mnt/vd". How should I do for these? Thanks!

　　　　　　　　Song Zhenhua
　　　　　　　　songzhh81@163.com
　　　　　　　　　　2006-10-30

Re: Reboot problem.

[Willy Tarreau]

Hello,

On Fri, Nov 04, 2005 at 01:33:01AM +0100, JaniD++ wrote:
> Hello list,
> 
> Is there any way to force reboot after this:
> 
> Nov  3 21:31:39 192.168.2.50 kernel: ------------[ cut here ]------------
> Nov  3 21:31:39 192.168.2.50 kernel: kernel BUG at mm/highmem.c:183!
> Nov  3 21:31:39 192.168.2.50 kernel: invalid operand: 0000 [#1]
> Nov  3 21:31:39 192.168.2.50 kernel: SMP
> Nov  3 21:31:39 192.168.2.50 kernel: Modules linked in: netconsole
> Nov  3 21:31:39 192.168.2.50 kernel: CPU:    3
(...)
> Nov  3 21:31:39 192.168.2.50 kernel: Code: e8 08 06 00 00 89 c7 e9 38 ff ff
> ff 55 89 e5 53 83 ec 04 89 c3 b8 80 6c 68 c0 e8 3e
> Nov  3 21:31:39 192.168.2.50 kernel:  <0>Fatal exception: panic in 5 seconds
> 
> At this point the system is freez, and only reset can help.

It should have rebooted, but the system is too instable to be able to
do so. In this case, the only thing that can help is a hardware watchdog.
Possibly, you motherboard includes a chipset with a watchdog that you can
simply enable by loading the module and having a simple daemon to ping it
(I have one which takes 12 kB of RAM and which tries mallocs, forks and
FS accesses).

If the daemon stops pinging the hardware watchdog for too long, the chipset
will simply assert the RESET signal and the system will reboot.

> Thanks
> 
> Janos

Regards,
Willy

Reboot problem.

[JaniD++]

Hello list,

Is there any way to force reboot after this:

Nov  3 21:31:39 192.168.2.50 kernel: ------------[ cut here ]------------
Nov  3 21:31:39 192.168.2.50 kernel: kernel BUG at mm/highmem.c:183!
Nov  3 21:31:39 192.168.2.50 kernel: invalid operand: 0000 [#1]
Nov  3 21:31:39 192.168.2.50 kernel: SMP
Nov  3 21:31:39 192.168.2.50 kernel: Modules linked in: netconsole
Nov  3 21:31:39 192.168.2.50 kernel: CPU:    3
Nov  3 21:31:39 192.168.2.50 kernel: EIP:    0060:[<c015094f>]    Not
tainted VLI
Nov  3 21:31:39 192.168.2.50 kernel: EFLAGS: 00010246   (2.6.14)
Nov  3 21:31:39 192.168.2.50 kernel: EIP is at kunmap_high+0x1f/0x93
Nov  3 21:31:39 192.168.2.50 kernel: eax: 00000000   ebx: c30e1280   ecx:
c0764a78   edx: 00000286
Nov  3 21:31:39 192.168.2.50 kernel: esi: 00001000   edi: 00000000   ebp:
f6eade64   esp: f6eade5c
Nov  3 21:31:39 192.168.2.50 kernel: ds: 007b   es: 007b   ss: 0068
Nov  3 21:31:39 192.168.2.50 kernel: Process md4_raid1 (pid: 3367,
threadinfo=f6eac000 task=f7bd8030)
Nov  3 21:31:39 192.168.2.50 kernel: Stack: c30e1280 cc31b8d0 f6eade6c
c0118349 f6eadec4 c038f626 c30e1280 00000001
Nov  3 21:31:39 192.168.2.50 kernel:        ed143000 00001000 00004000
c0104e81 f6eadeec f7292d00 c07768ec f179e600
Nov  3 21:31:39 192.168.2.50 kernel:        13956025 01000000 e25b6edc
f6eadeec 22010000 00801bbc 00900100 c07768cc
Nov  3 21:31:39 192.168.2.50 kernel: Call Trace:
Nov  3 21:31:39 192.168.2.50 kernel:  [<c0103bf2>] show_stack+0x9a/0xd0
Nov  3 21:31:39 192.168.2.50 kernel:  [<c0103db2>]
show_registers+0x16a/0x1fa
Nov  3 21:31:39 192.168.2.50 kernel:  [<c0103fc3>] die+0xfa/0x17c
Nov  3 21:31:39 192.168.2.50 kernel:  [<c055510e>] do_trap+0x7e/0xb2
Nov  3 21:31:39 192.168.2.50 kernel:  [<c010432d>] do_invalid_op+0xa9/0xb3
Nov  3 21:31:39 192.168.2.50 kernel:  [<c01038ab>] error_code+0x4f/0x54
Nov  3 21:31:39 192.168.2.50 kernel:  [<c0118349>] kunmap+0x42/0x44
Nov  3 21:31:39 192.168.2.50 kernel:  [<c038f626>] nbd_send_req+0x1fc/0x297
Nov  3 21:31:39 192.168.2.50 kernel:  [<c038fb17>] do_nbd_request+0xf4/0x27d
Nov  3 21:31:39 192.168.2.50 kernel:  [<c0380e0c>]
__generic_unplug_device+0x28/0x2e
Nov  3 21:31:39 192.168.2.50 kernel:  [<c0380e2f>]
generic_unplug_device+0x1d/0x2e
Nov  3 21:31:39 192.168.2.50 kernel:  [<c046910b>] unplug_slaves+0x54/0xaf
Nov  3 21:31:39 192.168.2.50 kernel:  [<c046a81b>] raid1d+0x288/0x2cb
Nov  3 21:31:39 192.168.2.50 kernel:  [<c0478d4a>] md_thread+0x5f/0x10b
Nov  3 21:31:39 192.168.2.50 kernel:  [<c0132f07>] kthread+0xb1/0xb5
Nov  3 21:31:39 192.168.2.50 kernel:  [<c0101145>]
kernel_thread_helper+0x5/0xb
Nov  3 21:31:39 192.168.2.50 kernel: Code: e8 08 06 00 00 89 c7 e9 38 ff ff
ff 55 89 e5 53 83 ec 04 89 c3 b8 80 6c 68 c0 e8 3e
Nov  3 21:31:39 192.168.2.50 kernel:  <0>Fatal exception: panic in 5 seconds


At this point the system is freez, and only reset can help.

Thanks

Janos

Reboot problem

[Aleksey Gorelov]

[-- Attachment #1: Type: text/plain, Size: 437 bytes --]

Hello everybody,

  I noticed a weird thing while running 2.4.27 on Sony VAIO PCG-K15
laptop with ALI M5229 IDE controller. If native ALI driver
(CONFIG_BLK_DEV_ALI15X3) is enabled, machine reboots nicely. However, if
it is disabled, and only generic IDE driver is used, reboot hangs inside
machine_restart() if /dev/hda1 has ever been mounted during the session.
Any clue? Logs for both cases are attached. 

Thanks, 
Aleks.

[-- Attachment #2: ALI_LOG.TXT --]
[-- Type: text/plain, Size: 7143 bytes --]

000000000009f800 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000d0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001bf70000 (usable)
 BIOS-e820: 000000001bf70000 - 000000001bf7f000 (ACPI data)
 BIOS-e820: 000000001bf7f000 - 000000001bf80000 (ACPI NVS)
 BIOS-e820: 000000001bf80000 - 000000001c000000 (reserved)
 BIOS-e820: 000000002bf80000 - 000000002c000000 (reserved)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
447MB LOWMEM available.
On node 0 totalpages: 114544
zone(0): 4096 pages.
zone(1): 110448 pages.
zone(2): 0 pages.
Sony Vaio laptop detected.
ACPI: RSDP (v000 PTLTD                                     ) @ 0x000f6fc0
ACPI: RSDT (v001 SONY   K7       0x06040000  LTP 0x00000000) @ 0x1bf7a842
ACPI: FADT (v001 SONY   K7       0x06040000 PTL  0x000f4240) @ 0x1bf7ef64
ACPI: BOOT (v001 PTLTD  $SBFTBL$ 0x06040000  LTP 0x00000001) @ 0x1bf7efd8
ACPI: DSDT (v001  SONY  K7       0x06040000 MSFT 0x0100000e) @ 0x00000000
Kernel command line: root=/dev/ram ide1=noprobe ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe ide6=noprobe

ide_setup: ide1=noprobe
ide_setup: ide2=noprobe
ide_setup: ide3=noprobe
ide_setup: ide4=noprobe
ide_setup: ide5=noprobe
ide_setup: ide6=noprobe
Initializing CPU#0
Detected 2791.120 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 5570.56 BogoMIPS
Memory: 449088k/458176k available (1001k kernel code, 8700k reserved, 246k data, 104k init, 0k highmem)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU:     After generic, caps: bfebf9ff 00000000 00000000 00000000
CPU:             Common caps: bfebf9ff 00000000 00000000 00000000
CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
ACPI: Subsystem revision 20040326
PCI: PCI BIOS revision 2.10 entry at 0xfd890, last bus=1
PCI: Using configuration type 1
ACPI: IRQ9 SCI: Edge set to Level Trigger.
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: System [ACPI] (supports S0 S3 S4 S5)
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNK0] (IRQs 4) *0, disabled.
ACPI: PCI Interrupt Link [LNK1] (IRQs 3) *11
ACPI: PCI Interrupt Link [LNK2] (IRQs 10) *11
ACPI: PCI Interrupt Link [LNK3] (IRQs 11) *0, disabled.
ACPI: PCI Interrupt Link [LNK4] (IRQs 6) *10
ACPI: PCI Interrupt Link [LNK5] (IRQs *11)
ACPI: PCI Interrupt Link [LNK6] (IRQs 9) *0, disabled.
ACPI: PCI Interrupt Link [LNK7] (IRQs 9) *11
ACPI: PCI Interrupt Link [LNK8] (IRQs 3 4 5 7 10 *11)
ACPI: Embedded Controller [EC0] (gpe 24)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PPB_._PRT]
schedule_task(): keventd has not started
PCI: Probing PCI hardware
ACPI: PCI Interrupt Link [LNK6] enabled at IRQ 9
ACPI: PCI Interrupt Link [LNK7] enabled at IRQ 9
ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 11
ACPI: PCI Interrupt Link [LNK0] enabled at IRQ 4
ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 10
ACPI: PCI Interrupt Link [LNK4] enabled at IRQ 6
ACPI: PCI Interrupt Link [LNK5] enabled at IRQ 11
PCI: No IRQ known for interrupt pin A of device 00:0f.0
ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 3
PCI: Using ACPI for IRQ routing
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
apm: overridden by ACPI.
Starting kswapd
NTFS driver v1.1.22 [Flags: R/W]
vesafb: framebuffer at 0xf0000000, mapped to 0xdc808000, size 3072k
vesafb: mode is 1024x768x16, linelength=2048, pages=41
vesafb: protected mode interface info at c000:51e3
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
PCI: Enabling device 00:03.0 (0000 -> 0003)
Redundant entry in serial pci_table.  Please send the output of
lspci -vv, this message (10b9,5457,104d,8175)
and the manufacturer and name of serial board or modem board
to serial-pci-info@lists.sourceforge.net.
register_serial(): autoconfig failed
Real Time Clock Driver v1.10f
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ALI15X3: IDE controller at PCI slot 00:0f.0
PCI: No IRQ known for interrupt pin A of device 00:0f.0
ALI15X3: chipset revision 196
ALI15X3: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x8080-0x8087, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0x8088-0x808f, BIOS settings: hdc:DMA, hdd:pio
hda: TOSHIBA MK6021GAS, ATA DISK drive
blk: queue c02785e0, I/O limit 4095Mb (mask 0xffffffff)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 117210240 sectors (60012 MB), CHS=7296/255/63, UDMA(100)
Partition check:
 hda: hda1 hda2
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
usb.c: registered new driver hub
ehci_hcd 00:0c.2: PCI device 1033:00e0
ehci_hcd 00:0c.2: irq 11, pci mem dcb09800
usb.c: new USB bus registered, assigned bus number 1
ehci_hcd 00:0c.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
hub.c: USB hub found
hub.c: 5 ports detected
host/usb-uhci.c: $Revision: 1.275 $ time 18:15:24 Aug 11 2004
host/usb-uhci.c: High bandwidth mode enabled
host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
host/usb-ohci.c: USB OHCI at membase 0xdcb0b000, IRQ 10
host/usb-ohci.c: usb-00:0c.0, PCI device 1033:0035
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 3 ports detected
host/usb-ohci.c: USB OHCI at membase 0xdcb0d000, IRQ 6
host/usb-ohci.c: usb-00:0c.1, PCI device 1033:0035
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 2187k freed
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 104k freed

[-- Attachment #3: NOALI_LO.TXT --]
[-- Type: text/plain, Size: 6993 bytes --]

Linux version 2.4.27 (aleksey@dared.phoenix.com) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #9 Wed Aug 11 19:26:50 PDT 2004
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
 BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000d0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000001bf70000 (usable)
 BIOS-e820: 000000001bf70000 - 000000001bf7f000 (ACPI data)
 BIOS-e820: 000000001bf7f000 - 000000001bf80000 (ACPI NVS)
 BIOS-e820: 000000001bf80000 - 000000001c000000 (reserved)
 BIOS-e820: 000000002bf80000 - 000000002c000000 (reserved)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
447MB LOWMEM available.
On node 0 totalpages: 114544
zone(0): 4096 pages.
zone(1): 110448 pages.
zone(2): 0 pages.
Sony Vaio laptop detected.
ACPI: RSDP (v000 PTLTD                                     ) @ 0x000f6fc0
ACPI: RSDT (v001 SONY   K7       0x06040000  LTP 0x00000000) @ 0x1bf7a842
ACPI: FADT (v001 SONY   K7       0x06040000 PTL  0x000f4240) @ 0x1bf7ef64
ACPI: BOOT (v001 PTLTD  $SBFTBL$ 0x06040000  LTP 0x00000001) @ 0x1bf7efd8
ACPI: DSDT (v001  SONY  K7       0x06040000 MSFT 0x0100000e) @ 0x00000000
Kernel command line: root=/dev/ram ide1=noprobe ide2=noprobe ide3=noprobe ide4=noprobe ide5=noprobe ide6=noprobe

ide_setup: ide1=noprobe
ide_setup: ide2=noprobe
ide_setup: ide3=noprobe
ide_setup: ide4=noprobe
ide_setup: ide5=noprobe
ide_setup: ide6=noprobe
Initializing CPU#0
Detected 2791.127 MHz processor.
Console: colour dummy device 80x25
Calibrating delay loop... 5570.56 BogoMIPS
Memory: 449100k/458176k available (998k kernel code, 8688k reserved, 244k data, 100k init, 0k highmem)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU:     After generic, caps: bfebf9ff 00000000 00000000 00000000
CPU:             Common caps: bfebf9ff 00000000 00000000 00000000
CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
ACPI: Subsystem revision 20040326
PCI: PCI BIOS revision 2.10 entry at 0xfd890, last bus=1
PCI: Using configuration type 1
ACPI: IRQ9 SCI: Edge set to Level Trigger.
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: System [ACPI] (supports S0 S3 S4 S5)
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Link [LNK0] (IRQs 4) *0, disabled.
ACPI: PCI Interrupt Link [LNK1] (IRQs 3) *11
ACPI: PCI Interrupt Link [LNK2] (IRQs 10) *11
ACPI: PCI Interrupt Link [LNK3] (IRQs 11) *0, disabled.
ACPI: PCI Interrupt Link [LNK4] (IRQs 6) *10
ACPI: PCI Interrupt Link [LNK5] (IRQs *11)
ACPI: PCI Interrupt Link [LNK6] (IRQs 9) *0, disabled.
ACPI: PCI Interrupt Link [LNK7] (IRQs 9) *11
ACPI: PCI Interrupt Link [LNK8] (IRQs 3 4 5 7 10 *11)
ACPI: Embedded Controller [EC0] (gpe 24)
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PPB_._PRT]
schedule_task(): keventd has not started
PCI: Probing PCI hardware
ACPI: PCI Interrupt Link [LNK6] enabled at IRQ 9
ACPI: PCI Interrupt Link [LNK7] enabled at IRQ 9
ACPI: PCI Interrupt Link [LNK3] enabled at IRQ 11
ACPI: PCI Interrupt Link [LNK0] enabled at IRQ 4
ACPI: PCI Interrupt Link [LNK2] enabled at IRQ 10
ACPI: PCI Interrupt Link [LNK4] enabled at IRQ 6
ACPI: PCI Interrupt Link [LNK5] enabled at IRQ 11
PCI: No IRQ known for interrupt pin A of device 00:0f.0
ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 3
PCI: Using ACPI for IRQ routing
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16)
apm: overridden by ACPI.
Starting kswapd
NTFS driver v1.1.22 [Flags: R/W]
vesafb: framebuffer at 0xf0000000, mapped to 0xdc808000, size 3072k
vesafb: mode is 1024x768x16, linelength=2048, pages=41
vesafb: protected mode interface info at c000:51e3
vesafb: scrolling: redraw
vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
PCI: Enabling device 00:03.0 (0000 -> 0003)
Redundant entry in serial pci_table.  Please send the output of
lspci -vv, this message (10b9,5457,104d,8175)
and the manufacturer and name of serial board or modem board
to serial-pci-info@lists.sourceforge.net.
register_serial(): autoconfig failed
Real Time Clock Driver v1.10f
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hda: TOSHIBA MK6021GAS, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 117210240 sectors (60012 MB), CHS=7296/255/63
Partition check:
 hda: hda1 hda2
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
usb.c: registered new driver hub
ehci_hcd 00:0c.2: PCI device 1033:00e0
ehci_hcd 00:0c.2: irq 11, pci mem dcb09800
usb.c: new USB bus registered, assigned bus number 1
ehci_hcd 00:0c.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
hub.c: USB hub found
hub.c: 5 ports detected
host/usb-uhci.c: $Revision: 1.275 $ time 19:27:11 Aug 11 2004
host/usb-uhci.c: High bandwidth mode enabled
host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
host/usb-ohci.c: USB OHCI at membase 0xdcb0b000, IRQ 10
host/usb-ohci.c: usb-00:0c.0, PCI device 1033:0035
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 3 ports detected
host/usb-ohci.c: USB OHCI at membase 0xdcb0d000, IRQ 6
host/usb-ohci.c: usb-00:0c.1, PCI device 1033:0035
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 2187k freed
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 100k freed

reboot problem

[Edward Brookhouse]

Can anyone tell me why when given a shutdown -r or reboot or even an init 6
a machine would gracefully switch to runlevel 6 but hang before unmounting
filesystems and not reboot?? I reinstalled  initscripts-3.78-1 still no
luck ...

Edward