LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - General (http://www.linuxquestions.org/questions/linux-general-1/)
-   -   serial console - working, then "stuck" output and can't login (http://www.linuxquestions.org/questions/linux-general-1/serial-console-working-then-stuck-output-and-cant-login-541562/)

srfeo 03-29-2007 04:45 AM

serial console - working, then "stuck" output and can't login
 
Hi there,

I recently have been trying to debug some system freezes and have implemented a serial console connected to a laptop. I am running Debian Etch on the server.

When the system boots up using Grub, I get the menu on my serial console and I can press "enter" to select which kernel to boot to.

Quote:

GNU GRUB version 0.97 (638K lower / 456576K upper memory)

+-------------------------------------------------------------------------+
| Debian GNU/Linux, kernel 2.6.18-4-686 |
| Debian GNU/Linux, kernel 2.6.18-4-686 (single-user mode) |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-------------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, or 'c' for a command-line.
Then all the bootup sequence output arrives correctly on the serial console until sometime near the end when the output begins to get "stuck". I can see it properly on the VGA console, but not everything arrives on the serial console. After this point, the system will not respond to the serial keyboard either so I cannot login via serial.

Quote:

Begin: Mokjournald starting. Commit interval 5 seconds
unting root fileEXT3-fs: mounted filesystem with ordered data mode.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Starting the hotLinux agpgart interface v0.101 (c) Dave Jones
plug events dispagpgart: Detected VIA P4M800CE chipset
atcher: udevd.
agpgart: AGP aperture is 128M @ 0xe8000000
Synthesizing theshpchp: Standard Hot Plug PCI Controller Driver version: 0.4
initial hotpluginput: PC Speaker as /class/input/input2
atkbd.c: Spurious ACK on isa0060/serio0. Some program might be trying access hardware directly.

Waiting for /deReal Time Clock Driver v1.12ac
v to be fully poparport: PnPBIOS parport detected.
pulated...parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
ACPI: PCI Interrupt Link [ALKC] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:11.5[C] -> Link [ALKC] -> GSI 22 (level, low) -> IRQ 201
Adding 144544k swap on /dev/hda5. Priority:-1 extents:1 across:144544k
done.
Setting pEXT3 FS on hda1, arameters of disinternal journal
loop: loaded (max 8 devices)
c:Activating swadevice-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
p...done.
Checkr8169: eth0: link up
ing root file syACPI: Power Button (FF) [PWRF]
Starting system ACPI: Power Button (CM) [PWRB]
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
logging: syslog-NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
ng.
Starting poNFSD: starting 90-second grace period
rtmap daemon...ANET: Registered protocol family 10
lready running..lo: Disabled Privacy Extensions

Loading ACPI mIPv6 over IPv4 tunneling driver
I then can get the login prompt text (in fragments) if I disconnect and reconnect the Ethernet port and this seems to "unstick" the output. The "eth0" log output works OK and so do things like stopping and starting an external USB drive. However if I try "logger -p kern.emerg "Testing" this output will get stuck. The system is unresponsive to the serial connected keyboard.

Quote:

r8169: eth0: link down

r8169: eth0: link up
Debian GNU/Linuxr8169: eth0: link down
4.0 247 ttyS0
r8169: eth0: link up

r8169: eth0: link down
247 login: r8169: eth0: link up
r8169: eth0: link down
r8169: eth0: link up
r8169: eth0: link down
Mar 29 09:58:47 r8169: eth0: link up
247 sgreszcz: Ter8169: eth0: link down
sting
Mar 29 09:r8169: eth0: link up
58:57 247 sgreszr8169: eth0: link down
cz: Testing
Mar r8169: eth0: link up
29 09:59:06 247 r8169: eth0: link down
sgreszcz: Testinr8169: eth0: link up
g\n

r8169: eth0: link down
Debian GNU/Linuxr8169: eth0: link up
4.0 247 ttyS0
r8169: eth0: link down

r8169: eth0: link up
247 login: r8169: eth0: link down

r8169: eth0: link down
r8169: eth0: link up
usb 5-1: USB disconnect, address 2
usb 5-1: new high speed USB device using ehci_hcd and address 3
usb 5-1: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
Vendor: SAMSUNG Model: J10Y514120 Rev: 0-33
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdb: 390721968 512-byte hdwr sectors (200050 MB)
sdb: Write Protect is off
sdb: assuming drive cache: write through
SCSI device sdb: 390721968 512-byte hdwr sectors (200050 MB)
sdb: Write Protect is off
sdb: assuming drive cache: write through
sdb: sdb1
sd 3:0:0:0: Attached scsi disk sdb
The last time my system crashed, I was unable to see any reason why on the console, and I'm afraid that this information might have become "stuck" and it got lost.


All times are GMT -5. The time now is 11:50 PM.