答复: Disk spin down issue on s hut down/suspend to disk
Tejun Heo wrote: > Michael Sedkowski wrote: > > Dnia 07-08-2007, Wt o godzinie 15:56 +0900, Tejun Heo napisał(a): > >> 192 Power-Off_Retract_Count 0x0032 100 100 000Old_age > >> Always - 388 [snip] > On power off, the r/w heads in a disk should be unloaded (parked). This > is usually achieved by either putting the disk into standby/sleep mode > during shutdown. However, all modern disks can automatically unload > their heads when the power is removed abruptly. This is called > emergency unload. Emergency unload does shorten the lifespan of the > disk but you don't have to worry too much about it. Disks are designed > to withstand certain number of emergency unloads. Out of interest, does Power-Off_Retract_Count attribute only record emergency unloads rather than normal power off by Linux shutdown command? Thanks in advance, Sam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
答复: Disk spin down issue on s hut down/suspend to disk
Tejun Heo wrote: Michael Sedkowski wrote: Dnia 07-08-2007, Wt o godzinie 15:56 +0900, Tejun Heo napisał(a): 192 Power-Off_Retract_Count 0x0032 100 100 000Old_age Always - 388 [snip] On power off, the r/w heads in a disk should be unloaded (parked). This is usually achieved by either putting the disk into standby/sleep mode during shutdown. However, all modern disks can automatically unload their heads when the power is removed abruptly. This is called emergency unload. Emergency unload does shorten the lifespan of the disk but you don't have to worry too much about it. Disks are designed to withstand certain number of emergency unloads. Out of interest, does Power-Off_Retract_Count attribute only record emergency unloads rather than normal power off by Linux shutdown command? Thanks in advance, Sam - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 2.6.13-git] 8250 tweaks
Russell King <[EMAIL PROTECTED]> wrote: > The interrupts are only claimed when the port is > actually opened, so if > only one port was open, you'll only see one > appearing in /proc/interrupts. Get it. Thanks so much, Sam Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 2.6.13-git] 8250 tweaks
Russell King <[EMAIL PROTECTED]> wrote: > but it's not. We need PPC folk to fix their > SERIAL_PORT_DFNS and remove obsolete stuff like > RS_TABLE_SIZE. Hope Mark could take care this change. I have no sandpoint board at hand:-) I removed RS_TABLE_SIZE on my target successfully and happened to found that there was other file like ../syslib/gen550_dbg.c required SERIAL_PORT_DFNS as well which could use for KGDB or sth. > Ideally, SERIAL_PORT_DFNS should end up being > completely empty. It has implemented on my target:-) Still one puzzle related serial port. That's interrupt itself. I enabled two serial ports attached two different interrupt levels like 9/10 with disable interrupt shared. How come only one appeared in /proc/interrupts? What could be on your platform or they should be? Thanks a lot, Sam __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 2.6.13-git] 8250 tweaks
Russell King [EMAIL PROTECTED] wrote: but it's not. We need PPC folk to fix their SERIAL_PORT_DFNS and remove obsolete stuff like RS_TABLE_SIZE. Hope Mark could take care this change. I have no sandpoint board at hand:-) I removed RS_TABLE_SIZE on my target successfully and happened to found that there was other file like ../syslib/gen550_dbg.c required SERIAL_PORT_DFNS as well which could use for KGDB or sth. Ideally, SERIAL_PORT_DFNS should end up being completely empty. It has implemented on my target:-) Still one puzzle related serial port. That's interrupt itself. I enabled two serial ports attached two different interrupt levels like 9/10 with disable interrupt shared. How come only one appeared in /proc/interrupts? What could be on your platform or they should be? Thanks a lot, Sam __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 2.6.13-git] 8250 tweaks
Russell King [EMAIL PROTECTED] wrote: The interrupts are only claimed when the port is actually opened, so if only one port was open, you'll only see one appearing in /proc/interrupts. Get it. Thanks so much, Sam Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 2.6.13-git] 8250 tweaks
Russell King <[EMAIL PROTECTED]> wrote: > Well, in this case, the "whinging" resulted in > finding a _real_ bug and locating why your ports > weren't being found. So I guess it's > good for something. Indeed! The old kernel didn't have such an advantage. > Can you mail me a diff of the changes you made to > arch/ppc/platforms/sandpoint.h please? Certainly. > If that file is being used it seems that you > actually have 4 ports defined in total. However, > I'm a little confused because the sandpoint.h > defines don't seem to match your original dmesg > output. Well, I use a sandpoint-based board. Not the same as the reference one. There are two serial ports on the board and I enabled them both with IRQ9/10. In addition, No 8259 on this board. Pls don't apply this patch:-) Thanks, Sam Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs sandpoint-8250.diff Description: 2389572820-sandpoint-8250.diff
Re: [patch 2.6.13-git] 8250 tweaks
Russell King <[EMAIL PROTECTED]> wrote: > v. whining > > 1. To utter a plaintive, high-pitched, > protracted sound, as in pain, >fear, supplication, or complaint. > 2. To complain or protest in a childish fashion. > 3. To produce a sustained noise of relatively > high pitch: jet engines >whining. > > The kernel isn't doing any of those. Oops, I misused this word. Thanks for your correction. > Anyway, you're going to have to help me out a lot - I'd love to:-) > Also, having the contents of /sys/devices/platform > or /sys/bus/platform/* would be useful. > > For some reason, it appears that the serial driver > is being asked to register two serial ports at MMIO > address 0, from one platform device, > which it apparantly detects as being present. I > suspect these are coming from some table included > via asm-ppc/serial.h, but where that > is I've no idea. > > It's then asked to add two more ports from the > serial8250.0 device, which doesn't exist. These > come from a platform device in arch/ppc. > Again, where these come from I don't know. It doesn't matter. Your notes is good enough to put me the right direction to find out the bug in my platform. > So. The serial driver is being asked to create > _four_ ports. It's created two, but can't create > the other two, failing with error -22. > 22 is EINVAL, which means there was something wrong > with what was requested. That generally points to > uartclk being zero, which would > be a bug in the PPC architecture code. You can > confirm this by applying this patch: Sure. The uartclk printed zero. Your simple patch did a good help. Then I tracked down to the _four_ port registering and finally picked out the "bug". It turned out the conflict of uart init definition like MPC10X_UART0_IRQ in ../syslib/mpc10x_common.c and SERIAL_PORT_DFNS in ../platform/sandpoint.h. By now, only MPC10X_UART0_IRQ stuff is needed. SERIAL_PORT_DFNS should be omitted. Seems it's time for me to stand with Russell:-) I must confess that I am a stupid guy on kernel programming. The result on PPC side, I mean sandpoint board, still needs Mark's confirmation. Following is the bug-fixed boot log on a custom 8241 board. Loading kernel .. Linux version 2.6.13-rc3 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030217 (Yellow Dog Linux 3.0 3.2.2- .. Based on the Freescale Sandpoint Development System Built 1 zonelists Kernel command line: console=ttyS1,115200 root=/dev/nfs rw nfsroot=192.168.57.200:/opt/eldk3/ppc_82xx ip=192.168.57.243:192.1OpenPIC Version 1.2 (1 CPUs and 11 IRQ sources) at fdf4 OpenPIC timer frequency is 100.00 MHz PID hash table entries: 512 (order: 9, 8192 bytes) time_init: decrementer frequency = 25.00 MHz Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 62848k available (1572k kernel code, 388k data, 104k init, 0k highmem) Mount-cache hash table entries: 512 NET: Registered protocol family 16 PCI: Probing PCI hardware PCI: Cannot allocate resource region 1 of device :00:00.0 inotify syscall VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]). Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled ttyS0 at MMIO 0xfdf04500 (irq = 9) is a 16550A ttyS1 at MMIO 0xfdf04600 (irq = 10) is a 16550A io scheduler noop registered RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize PPP generic driver version 2.4.2 PPP Deflate Compression module registered PPP BSD Compression module registered .. IP-Config: Guessing netmask 255.255.255.0 IP-Config: Complete: device=eth0, addr=192.168.57.243, mask=255.255.255.0, gw=255.255.255.255, host=8241, domain=, nis-domain=(none), bootserver=192.168.57.200, rootserver=192.168.57.200, rootpath= Looking up port of RPC 13/2 on 192.168.57.200 Looking up port of RPC 15/1 on 192.168.57.200 VFS: Mounted root (nfs filesystem). Freeing unused kernel memory: 104k init INIT: version 2.84 booting Welcome to DENX Embedded Linux Environment Press 'I' to enter interactive startup. Building the cache [ OK ] Mounting proc filesystem: [ OK ] Configuring kernel parameters: [ OK ] .. Mounting NFS filesystems: [ OK ] Mounting other filesystems: [ OK ] Starting xinetd: [ OK ] 8241 login: root Last login: Wed Dec 31 19:00:33 on console bash-2.05b# ls bash-2.05b# cd / bash-2.05b# ls bin dev images libmnt root tmp var boot etc proc sbin usr bash-2.05b# cat /proc/interrupts CPU0 0: 18707 OpenPIC Level eth0 10:258 OpenPIC Level serial BAD: 14 Thanks for your time, Sam __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe from this
Re: [patch 2.6.13-git] 8250 tweaks
Russell King [EMAIL PROTECTED] wrote: v. whining 1. To utter a plaintive, high-pitched, protracted sound, as in pain, fear, supplication, or complaint. 2. To complain or protest in a childish fashion. 3. To produce a sustained noise of relatively high pitch: jet engines whining. The kernel isn't doing any of those. Oops, I misused this word. Thanks for your correction. Anyway, you're going to have to help me out a lot - I'd love to:-) Also, having the contents of /sys/devices/platform or /sys/bus/platform/* would be useful. For some reason, it appears that the serial driver is being asked to register two serial ports at MMIO address 0, from one platform device, which it apparantly detects as being present. I suspect these are coming from some table included via asm-ppc/serial.h, but where that is I've no idea. It's then asked to add two more ports from the serial8250.0 device, which doesn't exist. These come from a platform device in arch/ppc. Again, where these come from I don't know. It doesn't matter. Your notes is good enough to put me the right direction to find out the bug in my platform. So. The serial driver is being asked to create _four_ ports. It's created two, but can't create the other two, failing with error -22. 22 is EINVAL, which means there was something wrong with what was requested. That generally points to uartclk being zero, which would be a bug in the PPC architecture code. You can confirm this by applying this patch: Sure. The uartclk printed zero. Your simple patch did a good help. Then I tracked down to the _four_ port registering and finally picked out the bug. It turned out the conflict of uart init definition like MPC10X_UART0_IRQ in ../syslib/mpc10x_common.c and SERIAL_PORT_DFNS in ../platform/sandpoint.h. By now, only MPC10X_UART0_IRQ stuff is needed. SERIAL_PORT_DFNS should be omitted. Seems it's time for me to stand with Russell:-) I must confess that I am a stupid guy on kernel programming. The result on PPC side, I mean sandpoint board, still needs Mark's confirmation. Following is the bug-fixed boot log on a custom 8241 board. Loading kernel .. Linux version 2.6.13-rc3 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030217 (Yellow Dog Linux 3.0 3.2.2- .. Based on the Freescale Sandpoint Development System Built 1 zonelists Kernel command line: console=ttyS1,115200 root=/dev/nfs rw nfsroot=192.168.57.200:/opt/eldk3/ppc_82xx ip=192.168.57.243:192.1OpenPIC Version 1.2 (1 CPUs and 11 IRQ sources) at fdf4 OpenPIC timer frequency is 100.00 MHz PID hash table entries: 512 (order: 9, 8192 bytes) time_init: decrementer frequency = 25.00 MHz Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 62848k available (1572k kernel code, 388k data, 104k init, 0k highmem) Mount-cache hash table entries: 512 NET: Registered protocol family 16 PCI: Probing PCI hardware PCI: Cannot allocate resource region 1 of device :00:00.0 inotify syscall VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]). Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled ttyS0 at MMIO 0xfdf04500 (irq = 9) is a 16550A ttyS1 at MMIO 0xfdf04600 (irq = 10) is a 16550A io scheduler noop registered RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize PPP generic driver version 2.4.2 PPP Deflate Compression module registered PPP BSD Compression module registered .. IP-Config: Guessing netmask 255.255.255.0 IP-Config: Complete: device=eth0, addr=192.168.57.243, mask=255.255.255.0, gw=255.255.255.255, host=8241, domain=, nis-domain=(none), bootserver=192.168.57.200, rootserver=192.168.57.200, rootpath= Looking up port of RPC 13/2 on 192.168.57.200 Looking up port of RPC 15/1 on 192.168.57.200 VFS: Mounted root (nfs filesystem). Freeing unused kernel memory: 104k init INIT: version 2.84 booting Welcome to DENX Embedded Linux Environment Press 'I' to enter interactive startup. Building the cache [ OK ] Mounting proc filesystem: [ OK ] Configuring kernel parameters: [ OK ] .. Mounting NFS filesystems: [ OK ] Mounting other filesystems: [ OK ] Starting xinetd: [ OK ] 8241 login: root Last login: Wed Dec 31 19:00:33 on console bash-2.05b# ls bash-2.05b# cd / bash-2.05b# ls bin dev images libmnt root tmp var boot etc proc sbin usr bash-2.05b# cat /proc/interrupts CPU0 0: 18707 OpenPIC Level eth0 10:258 OpenPIC Level serial BAD: 14 Thanks for your time, Sam __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe from this list: send the line unsubscribe
Re: [patch 2.6.13-git] 8250 tweaks
Russell King [EMAIL PROTECTED] wrote: Well, in this case, the whinging resulted in finding a _real_ bug and locating why your ports weren't being found. So I guess it's good for something. Indeed! The old kernel didn't have such an advantage. Can you mail me a diff of the changes you made to arch/ppc/platforms/sandpoint.h please? Certainly. If that file is being used it seems that you actually have 4 ports defined in total. However, I'm a little confused because the sandpoint.h defines don't seem to match your original dmesg output. Well, I use a sandpoint-based board. Not the same as the reference one. There are two serial ports on the board and I enabled them both with IRQ9/10. In addition, No 8259 on this board. Pls don't apply this patch:-) Thanks, Sam Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs sandpoint-8250.diff Description: 2389572820-sandpoint-8250.diff
Re: [patch 2.6.13-git] 8250 tweaks
Russell King <[EMAIL PROTECTED]> wrote: > However, if you merely lifted the later 8250.c and > put it into a previous kernel (which looks like the > case), there's other changes in addition which are > required. Good catch. I tried 2.6.13-rc1 and the newest version 2.6.13-rc3 on the same target[MPC8241]. The whining remained the same. Thanks, Sam __ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 2.6.13-git] 8250 tweaks
Russell King [EMAIL PROTECTED] wrote: However, if you merely lifted the later 8250.c and put it into a previous kernel (which looks like the case), there's other changes in addition which are required. Good catch. I tried 2.6.13-rc1 and the newest version 2.6.13-rc3 on the same target[MPC8241]. The whining remained the same. Thanks, Sam __ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 2.6.13-git] 8250 tweaks
Russell King <[EMAIL PROTECTED]> wrote: [snip] > It works for me on my platforms here, and everyone > else on x86. I even had a situation where I had > NR_UARTS set to 64 but only one registered... which > also worked fine with no extraneous kernel messages. But seems not functional on PowerPC platform. I used a MPC8241 which has a DURT inside to try the git tree 8250.c and got the following result: u-boot=> run kt Please enter 'kernel-test':uImage-26-13 TFTP from server 192.168.57.200; our IP address is 192.168.57.243 Filename 'uImage-26-13'. Load address: 0x120 Loading: ### done Bytes transferred = 858760 (d1a88 hex) ## Booting image at 0120 ... Image Name: Linux-2.6.13-rc1 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:858696 Bytes = 838.6 kB Load Address: Entry Point: Uncompressing Kernel Image ... OK ## Loading RAMDisk Image at ff95 ... Image Name: Ramdisk ttyS1 Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size:1478758 Bytes = 1.4 MB Load Address: Entry Point: Loading Ramdisk to 03dde000, end 03f47066 ... OK Linux version 2.6.13-rc1 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030217 (Yellow Dog Linux 3.0 3.2.2-5 .. Built 1 zonelists Kernel command line: console=ttyS1,115200 root=/dev/ram0 rw ramdisk_size=20 ip=192.168.57.243:192.168.57.200:::8241:eth1 OpenPIC Version 1.2 (1 CPUs and 7 IRQ sources) at fdf4 OpenPIC timer frequency is 100.00 MHz PID hash table entries: 512 (order: 9, 8192 bytes) time_init: decrementer frequency = 25.00 MHz Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 61268k available (1548k kernel code, 388k data, 104k init, 0k highmem) Mount-cache hash table entries: 512 checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Freeing initrd memory: 1444k freed NET: Registered protocol family 16 PCI: Probing PCI hardware PCI: Cannot allocate resource region 1 of device :00:00.0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]). Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled ttyS0 at MMIO 0x0 (irq = 5) is a 16550A ttyS1 at MMIO 0x0 (irq = 6) is a 16550A serial8250 serial8250.0: unable to register port at index 0 (IO0 MEMfdf04500 IRQ25): -22 serial8250 serial8250.0: unable to register port at index 1 (IO0 MEMfdf04600 IRQ26): -22 io scheduler noop registered RAMDISK driver initialized: 16 RAM disks of 20K size 1024 blocksize PPP generic driver version 2.4.2 PPP Deflate Compression module registered PPP BSD Compression module registered .. TCP reno registered TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 IP-Config: Device `eth0' not found. RAMDISK: Compressed image found at block 0 VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 104k init serial console detected. Disabling virtual terminals. ### Application running ... BusyBox v0.60.1 (2002.10.24-04:52+) Built-in shell (msh) Enter 'help' for a list of built-in commands. # cat /proc/interrupts CPU0 6: 39 OpenPIC Level serial BAD: 3 The whining is a little bit different from david's. ttyS1 conosle was a workable one but ttyS1 didn't register right??? After applied David's patch, it became normal as before like 2.6.12-rc2 did. So my puzzle comes to know why ttyS1 cannot register right even it works well. TTA, Sam __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch 2.6.13-git] 8250 tweaks
Russell King [EMAIL PROTECTED] wrote: [snip] It works for me on my platforms here, and everyone else on x86. I even had a situation where I had NR_UARTS set to 64 but only one registered... which also worked fine with no extraneous kernel messages. But seems not functional on PowerPC platform. I used a MPC8241 which has a DURT inside to try the git tree 8250.c and got the following result: u-boot= run kt Please enter 'kernel-test':uImage-26-13 TFTP from server 192.168.57.200; our IP address is 192.168.57.243 Filename 'uImage-26-13'. Load address: 0x120 Loading: ### done Bytes transferred = 858760 (d1a88 hex) ## Booting image at 0120 ... Image Name: Linux-2.6.13-rc1 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:858696 Bytes = 838.6 kB Load Address: Entry Point: Uncompressing Kernel Image ... OK ## Loading RAMDisk Image at ff95 ... Image Name: Ramdisk ttyS1 Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size:1478758 Bytes = 1.4 MB Load Address: Entry Point: Loading Ramdisk to 03dde000, end 03f47066 ... OK Linux version 2.6.13-rc1 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030217 (Yellow Dog Linux 3.0 3.2.2-5 .. Built 1 zonelists Kernel command line: console=ttyS1,115200 root=/dev/ram0 rw ramdisk_size=20 ip=192.168.57.243:192.168.57.200:::8241:eth1 OpenPIC Version 1.2 (1 CPUs and 7 IRQ sources) at fdf4 OpenPIC timer frequency is 100.00 MHz PID hash table entries: 512 (order: 9, 8192 bytes) time_init: decrementer frequency = 25.00 MHz Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 61268k available (1548k kernel code, 388k data, 104k init, 0k highmem) Mount-cache hash table entries: 512 checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Freeing initrd memory: 1444k freed NET: Registered protocol family 16 PCI: Probing PCI hardware PCI: Cannot allocate resource region 1 of device :00:00.0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]). Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled ttyS0 at MMIO 0x0 (irq = 5) is a 16550A ttyS1 at MMIO 0x0 (irq = 6) is a 16550A serial8250 serial8250.0: unable to register port at index 0 (IO0 MEMfdf04500 IRQ25): -22 serial8250 serial8250.0: unable to register port at index 1 (IO0 MEMfdf04600 IRQ26): -22 io scheduler noop registered RAMDISK driver initialized: 16 RAM disks of 20K size 1024 blocksize PPP generic driver version 2.4.2 PPP Deflate Compression module registered PPP BSD Compression module registered .. TCP reno registered TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 IP-Config: Device `eth0' not found. RAMDISK: Compressed image found at block 0 VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 104k init serial console detected. Disabling virtual terminals. ### Application running ... BusyBox v0.60.1 (2002.10.24-04:52+) Built-in shell (msh) Enter 'help' for a list of built-in commands. # cat /proc/interrupts CPU0 6: 39 OpenPIC Level serial BAD: 3 The whining is a little bit different from david's. ttyS1 conosle was a workable one but ttyS1 didn't register right??? After applied David's patch, it became normal as before like 2.6.12-rc2 did. So my puzzle comes to know why ttyS1 cannot register right even it works well. TTA, Sam __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
