Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 154532 Details for
Bug 239788
kdump (scp, NFS) fail if you don't set Default Gateway
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
serial console ouput of kdump without default gateway setting
kdump-default-gw.txt (text/plain), 3.20 KB, created by
masanari iida
on 2007-05-11 12:06:34 UTC
(
hide
)
Description:
serial console ouput of kdump without default gateway setting
Filename:
MIME Type:
Creator:
masanari iida
Created:
2007-05-11 12:06:34 UTC
Size:
3.20 KB
patch
obsolete
>[root@localhost ~]# sync >[root@localhost ~]# sync >[root@localhost ~]# sync >[root@localhost ~]# echo 1 > /proc/sys/kernel/sysrq >[root@localhost ~]# echo c > /proc/sysrq-trigger >SysRq : Trigger a crashdump >PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved >PCI: Not using MMCONFIG. >ACPI: Getting cpuindex for acpiid 0x2 >ACPI: Getting cpuindex for acpiid 0x3 >ACPI: Getting cpuindex for acpiid 0x4 >ACPI: Getting cpuindex for acpiid 0x5 >ÿMounting proc filesystem >Mounting sysfs filesystem >Creating /dev >Creating initial device nodes >Loading scsi_mod.ko module >Loading sd_mod.ko module >Loading cciss.ko module >Loading jbd.ko module >Loading ext3.ko module >Loading bnx2.ko module >Loading sunrpc.ko module >Loading lockd.ko module >Loading fscache.ko module >Loading nfs_acl.ko module >Loading nfs.ko module >Creating Block Devices >Creating block device cciss!c0d0 >Creating block device cciss!c1d0 >Creating block device ram0 >Creating block device ram1 >Creating block device ram10 >Creating block device ram11 >Creating block device ram12 >Creating block device ram13 >Creating block device ram14 >Creating block device ram15 >Creating block device ram2 >Creating block device ram3 >Creating block device ram4 >Creating block device ram5 >Creating block device ram6 >Creating block device ram7 >Creating block device ram8 >Creating block device ram9 >mapping eth0 to eth0 >ifup: option with empty value " gateway" >eth0 failed to come up >Saving to remote location 192.168.1.145:/var/crash >mount: RPC: Unable to send; errno = Network is unreachable >mount: nfsmount failed: Bad file descriptor >mount: Mounting 192.168.1.145:/var/crash on /mnt failed: Bad file descriptor >Out of memory: Killed process 1025 (exe). >Killed >umount: Couldn't umount /mnt: Invalid argument >Creating root device. >Out of memory: Killed process 1033 (msh). >Killed >Out of memory: Killed process 1036 (msh). >Killed >Out of memory: Killed process 1038 (msh). >Killed >Out of memory: Killed process 1040 (msh). >Killed >Out of memory: Killed process 1042 (exe). >Out of memory: Killed process 1041 (exe). >Killed >1042: Killed >Checking root filesystem. >fsck 1.38 (30-Jun-2005) >fsck: WARNING: couldn't open /etc/fstab: No such file or directory >e2fsck 1.38 (30-Jun-2005) >fsck.ext2: while determining whether /dev/rootdev is mounted. >fsck.ext2: while trying to open /dev/rootdev > >The superblock could not be read or does not describe a correct ext2 >filesystem. If the device is valid and it really contains an ext2 >filesystem (and not swap or ufs or something else), then the superblock >is corrupt, and you might try running e2fsck with an alternate superblock: > e2fsck -b 8193 <device> > >fsck.ext2: >Mounting root filesystem. >Out of memory: Killed process 1049 (msh). >Out of memory: Killed process 1051 (msh). >Killed >1051: Killed >fsck 1.38 (30-Jun-2005) >fsck: WARNING: couldn't open /etc/fstab: No such file or directory >mount -t /dev/rootdev /sysroot >mount: Cannot read /etc/fstab: No such file or directory >unable to mount rootfs. Dropping to shell >root:/> exit >mount: Mounting Kernel panic - not syncing: Attempted to kill init! >proc on /sysroot /proc failed: No > >-=-=-=-=-=-=-=-=-=-= SYSTEM STOP HERE -=-=-=-=-=-=-=-=-=-=-=-=-=-=
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 239788
: 154532