[parisc-linux] Some 2.5-testing

[parisc-linux] Some 2.5-testing

[Rüdiger Scholz]

Hi there,

I tried to get a running 2.5.70 kernel on my 715/100, but booting 
results in an endless loop with the following error:

    Badness in local_bh_enable at kernel/softirq.c:109
    Kernel addresses on the stack:
     [<10123d54>]  [<10105884>]  [<10127610>]  [<10285e0c>]
     [<102868c4>]  [<10285828>]  [<10287360>]  [<1012b6ac>]
     [<10287624>]  [<1012782c>]  [<101275c8>]  [<10175800>]
     [<10107000>]  [<101876ac>]  [<1010a068>]  [<10285828>]
     [<1028e468>]  [<103951b8>]  [<10123d54>]  [<1028f904>]
     [<1039541c>]  [<10100278>]  [<10109c5c>]

Only way to stop it, is to pull the plug...
Does anyone know a solution?
Another thing:  During compile I get this warning several times:   
"Warning: long unsigned int format, time_t arg (arg XX)" (But perhaps 
this warning is solved with the fixes jejb uploaded currently)

Some more informations:

    Kernel was generated  via make distclean, make oldconfig, make vmlinux.
    During compile I get this warning several times:   "Warnung: long 
unsigned int format, time_t arg (arg XX)"
    OS: Debian testing with gcc-3.3 and glibc-2.3.16
    HW: HP 715/100 with serial console and HIL-adaptor box (but no mouse 
or keyboard is connected to the adaptor)
    Debug: System.map and complete bootlog is here: 
http://rscholz.bluehash.de/parisc/

TIA,
    Ruediger

Re: [parisc-linux] Some 2.5-testing

[John David Anglin]

> I tried to get a running 2.5.70 kernel on my 715/100, but booting 
> results in an endless loop with the following error:

Until issues related to the canonicalization of function pointers
and the alignment of stack locals are resolved, it is best to stick
with debian gcc-3.0.4 for kernel building.  Loops of this kind can
happen when lock structures are misaligned on PA 1.1 machines.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)

Re: [parisc-linux] Some 2.5-testing

[Rüdiger Scholz]

John David Anglin schrieb:

>Until issues related to the canonicalization of function pointers
>and the alignment of stack locals are resolved, it is best to stick
>with debian gcc-3.0.4 for kernel building.
>
So I installed gcc-3.04 from Debian, did "make distclean", "make 
oldconfig" (selecting "PA7100LC") and booted...
And got the same loop again ;)

---------- SNIP---------------

     md: linear personality registered as nr 1
    Badness in local_bh_enable at at kernel/softirq.c:109
    Kernel addresses on the stack:

     [tirq.c:109
    <4>Kernel addresses on the stack:
    <4> [<10124edcc8>]  [<1010ea4c>]
    <4> [<1012503c>]  [<1028ac08>]  [<10124cc>]
    <4> [<1029a2a4>]  [<103ad4d4>]  [<10100284>]  [<10109c5ab8>] 
    [<101289a8>]  [<1028ac20>]
     [<1028b428>]  [<101070f28ac08>]  [<10124f10>]  [<1028adcc>]
     [<1029a2a4>]  [<103adc>]
    <4> [<1029a2a4>]  [<103ad4d4>]  [<10100284>]  [<10109c>] 
    [<103ad4d4>]  [<10100284>]  [<10109c5c>]


---------- SNAP---------------

Complete Bootlog and System.map is here: rscholz.bluehash.de/parisc .
Can I do something else to help finding the bug?

>  Loops of this kind can
>happen when lock structures are misaligned on PA 1.1 machines.
>
>Dave
>  
>

Rüdiger

Re: [parisc-linux] Some 2.5-testing

[Joel Soete]

Hi,

I do not yet tested 2.5 (or so faraway) but this message:
>     md: linear personality registered as nr 1
>    Badness in local_bh_enable at at kernel/softirq.c:109

seems to point out md support (ie raid support).
Do you already try to rebuild and re-try a kernel without this support?

Joel



---------------------------------
Tiscali ADSL: 19,50 euros/mois...abonnez-vous sur www.tiscali.be

Re: [parisc-linux] Some 2.5-testing

[Rüdiger Scholz]

Hi,

>Do you already try to rebuild and re-try a kernel without this support?
>
>Joel
>  
>
this was also my thought, so recompiled kernel without md-support. I 
just rebooted the machine with the new kernel.... Same problem at 
another place:

----------------SNIP-----------

    Keyboard initialization sequence failled
    input: PS/2 keyboard port at 0xf0108000 (irq 69) found and attached
    input: PS/2 mouse port at 0xf0108100 (irq 69) found and attached
    HP SDC: HP SDC at 0xf0201000, IRQ 126 (NMI IRQ 125)
    HP SDC: New style SDC
    HP SDC: Revision: 1820-4784
    HP SDC: TI SN76494 beeper present
    HP SDC: OKI MSM-58321 BBRTC present
    HP SDC: Spunking the self test register to force PUP on next
    firmware reset.
    HP SDC MLC: Registering the System Domain Controller's HIL MLC.
    oprofile: using timer interrupt.
    Badness in local_bh_enable at kernel/s1012503c>]  [<101615dc>] 
    [<10124f10>]
     [<1028ab94>]  [<10494>]
    <4> [<10210468>]  [<10124b3c>]  [<1018abf8>]  [<10124cc8>]
    ftirq.c:109
    Kernel addresses on the stack:
     [<10124ed8>]  b1f0>]  [<101070f8>]  [<1028c0d8>]  [<1028c20c>]
     [<10128c68>]  [<1020dd68>]  [<101e493c>]
    <4> [<10210468>]  [<10124b3ck:
    <4> [<10124ed8>]  [<10105ab8>]  [<101289a8>]  [<1028a9d03b83c8>] 
    [<10399494>]  [<10100284>]
     [<10109c5c>]
    Badnes  [<101615dc>]  [<10124f10>]
    <4> [<1028ab94>]  [<103b83c8>]> [<101e0f5c>]  [<1012503c>] 
    [<101615dc>]  [<10124f10>]
     [1020dd48>]  [<10210498>]
    <4> [<10210468>]  [<10124b3c>] c5c>]
    <4>HP SDC: Transaction add failed: transaction already queuedl
    addresses on the stack:

-----------------SNAP----------------

The interesting thing could this line:  "oprofile: using timer 
interrupt." I think in using the timer interrupt lies the problem. 
Doesn't the md-stuff  use also the timer-interrupt to measure the 
throughput with various registers?

Rüdiger

Re: [parisc-linux] Some 2.5-testing

[Joel Soete]

Hi,

> >Do you already try to rebuild and re-try a kernel without this support?
> >
> this was also my thought, so recompiled kernel without md-support. I 
> just rebooted the machine with the new kernel.... Same problem at 
> another place:

Sorry.

My best idea now is try a TOC (I presume that such a special swicth exist
on 715 model) (may be first cleanup PIMinfo with "ser clearpim" at bootprompt
before booting the kernel). Then during the 'bad loop' puch the TOC button
and at the bootprompt again collect (with minicom for instance) piminfo ("ser
pim") and try to submit it to analyse to 'dump_analyser.sh' (you can grabbe
it with a.c into cvs build-tools dir).
And report its result to this ml.

Hope this will help,
    Joel

PS: Edit dump_analyser.sh to change DUMPTYPE to TOC (default is kernel).
btw, I am impatient that hp release its p4 tools :-)


---------------------------------
Tiscali ADSL: 19,50 euros/mois...abonnez-vous sur www.tiscali.be

Re: [parisc-linux] Some 2.5-testing

[Matthew Wilcox]

On Thu, Jun 19, 2003 at 05:59:56AM +0200, Rüdiger Scholz wrote:
> John David Anglin schrieb:
> 
> >Until issues related to the canonicalization of function pointers
> >and the alignment of stack locals are resolved, it is best to stick
> >with debian gcc-3.0.4 for kernel building.
> >
> So I installed gcc-3.04 from Debian, did "make distclean", "make 
> oldconfig" (selecting "PA7100LC") and booted...
> And got the same loop again ;)
> 
> ---------- SNIP---------------
> 
>     md: linear personality registered as nr 1
>    Badness in local_bh_enable at at kernel/softirq.c:109
>    Kernel addresses on the stack:
> 
>     [tirq.c:109
>    <4>Kernel addresses on the stack:
>    <4> [<10124edcc8>]  [<1010ea4c>]
>    <4> [<1012503c>]  [<1028ac08>]  [<10124cc>]
>    <4> [<1029a2a4>]  [<103ad4d4>]  [<10100284>]  [<10109c5ab8>] 
>    [<101289a8>]  [<1028ac20>]
>     [<1028b428>]  [<101070f28ac08>]  [<10124f10>]  [<1028adcc>]
>     [<1029a2a4>]  [<103adc>]
>    <4> [<1029a2a4>]  [<103ad4d4>]  [<10100284>]  [<10109c>] 
>    [<103ad4d4>]  [<10100284>]  [<10109c5c>]

So... what's going on here is that someone's enabling softirqs with hard
interrupts disabled.  This is not a smart thing to do.  Unfortunately,
something is messing up the stack backtrace, so it's hard tosee what's
going on.  Could you turn on CONFIG_KALLSYMS so the kernel prints out
its symbols?  The messages may still be corrupt, but we should have more
information to help us figure out what's going on.

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

Re: [parisc-linux] Some 2.5-testing

[James Bottomley]

On Thu, 2003-06-19 at 06:40, Matthew Wilcox wrote:
> So... what's going on here is that someone's enabling softirqs with hard
> interrupts disabled.  This is not a smart thing to do.  Unfortunately,
> something is messing up the stack backtrace, so it's hard tosee what's
> going on.  Could you turn on CONFIG_KALLSYMS so the kernel prints out
> its symbols?  The messages may still be corrupt, but we should have more
> information to help us figure out what's going on.

This was a known problem in the HIL keyboard/mouse drivers around
2.5.70.  I think Helge already submitted a fix for this, could you try a
later version of the parisc kernel?

Thanks,

James

Re: [parisc-linux] Some 2.5-testing

[Rüdiger Scholz]

Hi,

back again with new results! Compiled Kernel with CONFIG_KALLSYMS and 
md-support. Here is a part from the boot-log:
---------SNIP

    md: linear personality registered as nr 1
    Badness in local_bh_enable at kernel/softirq.c:109
    Kernel addresses on the stack:
     [<10124ee8>] printk+0xf0/0x128
     [<10105adc>] dump_stack+0x10/0x1c
     [<101289b8>] .L886+0x0/0x50
     [<1028b3d0>] .L1082+0x8/0x18
     [<1028bdd4>] .L812+0x0/0x9c
     [<1012cdb8>] do_timer+0x68/0x118
     [<1028c9b0>] .L917+0x48/0x58
     [<1028cc0c>] hil_mlcs_process+0x28/0x4c
     [<10128c48>] .L919+0x10/0x24
     [<1012891c>] do_softirq+0x9c/0xf8
     [<1010a068>] intr_return+0x0/0x14
     [<10107268>] do_cpu_irq_mask+0x90/0xf0
     [<1020e7a0>] .L1836+0x18/0x38
     [<1010a068>] intr_return+0x0/0x14
     [<10210ef0>] serial8250_console_write+0xf0/0x158
     [<10210ec0>] serial8250_console_write+0xc0/0x158
     [<10124b4c>] __call_console_drivers+0x6c/0x98
     [<10124cd8>] call_console_drivers+0xf0/0x178
     [<1010ea4c>] .L632+0x0/0xac
     [<1012504c>] .L1637+0x0/0x2c
     [<1028b3d0>] .L1082+0x8/0x18
     [<10124f20>] .L1612+0x0/0x38
     [<1028b594>] .L1154+0x0/0x10
     [<1029aa6c>] register_md_personality+0xa0/0xa8
     [<103e14d4>] do_initcalls+0x64/0xe0
     [<10100284>] init+0x28/0x60
     [<10109c5c>] ret_from_kernel_thread+0x1c/0x24

    Badness in local_bh_enable at kernel/softirq.c:109
    Kernel addresses on the stack:
     [<10124ee8>] printk+0xf0/0x128
     [<10105adc>] dump_stack+0x10/0x1c
     [<101289b8>] .L886+0x0/0x50
     [<1028b3d0>] .L1082+0x8/0x18
     [<1028bbf0>] .L762+0x0/0x74
     [<1028ac48>] .L1018+0x0/0x3c
     [<1028cad8>] .L974+0x20/0xc4
     [<1028cc0c>] hil_mlcs_process+0x28/0x4c
     [<10128c48>] .L919+0x10/0x24
     [<1012891c>] do_softirq+0x9c/0xf8
     [<1020e7a0>] .L1836+0x18/0x38
     [<1010a260>] intr_do_softirq+0x8/0x10
     [<101e5248>] $$divU+0x100/0x120
     [<10210ec0>] serial8250_console_write+0xc0/0x158
     [<10124b4c>] __call_console_drivers+0x6c/0x98
     [<10124cd8>] call_console_drivers+0xf0/0x178
     [<1010ea4c>] .L632+0x0/0xac
     [<1012504c>] .L1637+0x0/0x2c
     [<1028b3d0>] .L1082+0x8/0x18
     [<10124f20>] .L1612+0x0/0x38
     [<1028b594>] .L1154+0x0/0x10
     [<1029aa6c>] register_md_personality+0xa0/0xa8
     [<103e14d4>] do_initcalls+0x64/0xe0
     [<10100284>] init+0x28/0x60
     [<10109c5c>] ret_from_kernel_thread+0x1c/0x24

----------SNAP

Later I will grap some piminfo on the loop, and run dump_analyser on it.
Anything else I can do?

Rüdiger

Matthew Wilcox schrieb:

>So... what's going on here is that someone's enabling softirqs with hard
>interrupts disabled.  This is not a smart thing to do.  Unfortunately,
>something is messing up the stack backtrace, so it's hard tosee what's
>going on.  Could you turn on CONFIG_KALLSYMS so the kernel prints out
>its symbols?  The messages may still be corrupt, but we should have more
>information to help us figure out what's going on.
>  
>

Re: [parisc-linux] Some 2.5-testing

[Matthew Wilcox]

On Thu, Jun 19, 2003 at 08:49:45PM +0200, Rüdiger Scholz wrote:
> Hi,
> 
> back again with new results! Compiled Kernel with CONFIG_KALLSYMS and 
> md-support. Here is a part from the boot-log:
> ---------SNIP
> 
>    md: linear personality registered as nr 1
>    Badness in local_bh_enable at kernel/softirq.c:109
>    Kernel addresses on the stack:
>     [<10124ee8>] printk+0xf0/0x128
>     [<10105adc>] dump_stack+0x10/0x1c
>     [<101289b8>] .L886+0x0/0x50
>     [<1028b3d0>] .L1082+0x8/0x18
>     [<1028bdd4>] .L812+0x0/0x9c
>     [<1012cdb8>] do_timer+0x68/0x118
>     [<1028c9b0>] .L917+0x48/0x58
>     [<1028cc0c>] hil_mlcs_process+0x28/0x4c

... we really need to get these .L symbols cleaned up; stop them entering
the System.map.  Any toolchain hackers interested in looking at this?

Anyway, the fault seems to be in the HIL drivers -- someone said Helge
was looking at this?  If you disable the HIL drivers, does it work?

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

Re: [parisc-linux] Some 2.5-testing

[Helge Deller]

On Thursday 19 June 2003 21:56, Matthew Wilcox wrote:
> Anyway, the fault seems to be in the HIL drivers -- someone said Helge
> was looking at this?  If you disable the HIL drivers, does it work?

The new HIL drivers are broken and will crash the machine at some point.
Using the old HIL drivers instead, or deactivating HIL completely should work for now, 
until I really get more time to look into the problem (which isn't easy to fix at all).

Helge

Re: [parisc-linux] Some 2.5-testing

[Rüdiger Scholz]

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

Hi there,

sorry for the delay, but it took some time to get beck to my HP and 
built an new kernel. With disabled HIL-Support I get a working kernel. 
Bootlog is attached. So I would like to say thank you for the great job 
you all do.
I just recognized two failures. One is: "Setting up general console 
font...set_kernel_font: Function not implemented" during an init-script 
and the other is this: "gsckbd_leds: timeout".
If  I can help to test patches to get HIL-Support working let me know.
Greetings,
    Rüdiger

[-- Attachment #2: gandalf-2.5.72-pa1-3.log --]
[-- Type: text/plain, Size: 11929 bytes --]



----------------------------------------------------------------------------
BootRom Version    1.6  
Memory Size:  128 MB
----------------------------------------------------------------------------




(c) Copyright 1990-1994, Hewlett-Packard Company.
All rights reserved

Press <ESCAPE> to stop boot sequence.
----------------------------------------------------------------------------
Command                                Description
-------                                -----------
Auto [boot|search] [on|off]            Set/show auto mode
Boot [pri|alt [isl]]                   Boot from primary or alternate path
Boot [scsi|eisa.<slot>[.<addr>]] [isl] Boot from SCSI or EISA
Boot lan[.<addr>] [install] [isl]      Boot from LAN
Chassis [on|off]                       Set/show chassis codes display mode
DefaultSS                              Reboot and set EEPROM to default values
Diagnostic [on|off]                    Set/show diagnostic boot mode
Fastboot [on|off]                      Set/show fast boot mode
Help                                   Show this command menu
Information                            Show system information
LanAddress                             Show LAN station addresses
Monitor [<DEV>[.<type>]]               Set/show graphics monitor type
                                       (<DEV>=graphics|graphics_<1|2>)
Path [pri|alt [<DEV>[.<addr>]]]        Set/show boot source path
                                       (<DEV>=lan|scsi|eisa.<slot>)
Path [console [<DEV>[.<parm>]]]        Set/show boot console path
                                       (<DEV>=<RS232>|<GRAPH>
                                        <RS232>=rs232|rs232_2
                                        <parm>=<baud>.<length>.<parity>
                                        <GRAPH>=graphics|graphics_<1|2>
                                        <parm>=<monitor>)
Path [keyboard [hil|ps2]]              Set/show boot keyboard path
Pim [hpmc|toc|lpmc]                    Show PIM info
Search [ipl] [scsi|eisa]               Show potential boot devices
Search [ipl] [lan [install]]           Show potential boot LAN devices
Secure [on|off]                        Set/show security mode
----------------------------------------------------------------------------
BOOT_ADMIN> bo pri ipl





Attempting to boot.

Loading Initial Program Loader


IPL successfully loaded


Booting
palo ipl 1.2 root@b2000 Tue Jan 14 13:13:07 MST 2003


Partition Start(MB) End(MB) Id Type


1               1      22   f0 Palo


2              23      64   83 ext2


3              65     194   82 swap


4             195    2046   83 ext2



PALO(F0) partition contains:

    0/vmlinux32 3223985 bytes @ 0x48000


Information: No console specified on kernel command line. This is normal.

PALO will choose the console currently used by firmware (serial).Current command line:

2/vmlinux root=/dev/sda4 HOME=/ devfs=mount console=ttyS0 TERM=vt102

 0: 2/vmlinux

 1: root=/dev/sda4

 2: HOME=/

 3: devfs=mount

 4: console=ttyS0

 5: TERM=vt102


Edit which field?

(or 'b' to boot with this command line)? 0\b \bb\b \b0

2/vmlinux-2.5.72-pa1

Current command line:

2/vmlinux-2.5.72-pa1 root=/dev/sda4 HOME=/ devfs=mount console=ttyS0 TERM=vt102

 0: 2/vmlinux-2.5.72-pa1

 1: root=/dev/sda4

 2: HOME=/

 3: devfs=mount

 4: console=ttyS0

 5: TERM=vt102


Edit which field?

(or 'b' to boot with this command line)? 0b\b \b\b \bb


Command line for kernel: 'root=/dev/sda4 HOME=/ devfs=mount console=ttyS0 TERM=vt102 palo_kernel=2/vmlinux-2.5.72-pa1'

Selected kernel: /vmlinux-2.5.72-pa1 from partition 2

ELF32 executable

Entry 00100000 first 00100000 n 3

Segment 0 load 00100000 size 2325984 mediaptr 0x1000

Segment 1 load 00338000 size 463048 mediaptr 0x239000

Segment 2 load 003ac000 size 524416 mediaptr 0x2ab000

Branching to kernel entry point 0x00100000.  If this is the last

message you see, you may need to switch your console.  This is

a common symptom -- search the FAQ and mailing list at parisc-linux.org


Linux version 2.5.72-pa1 (ruediger@gandalf) (gcc version 3.0.4) #2 Fri Jun 20 20:56:57 CEST 2003
FP[0] enabled: Rev 1 Model 13
The 32-bit Kernel has started...
Determining PDC firmware type: Snake.
model 000060b0 00000481 00000000 00000000 77b661a7 00000000 00000004 00000072 00000072
vers  0000000b
model 9000/715
Total Memory: 128 Mb
pagetable_init
On node 0 totalpages: 32768
  DMA zone: 32768 pages, LIFO batch:8
  Normal zone: 0 pages, LIFO batch:1
  HighMem zone: 0 pages, LIFO batch:1
Building zonelist for node : 0
Kernel command line: root=/dev/sda4 HOME=/ devfs=mount console=ttyS0 TERM=vt102 palo_kernel=2/vmlinux-2.5.72-pa1
PID hash table entries: 16 (order 4: 128 bytes)
Console: colour dummy device 160x64
Calibrating delay loop... 99.73 BogoMIPS
Memory: 126144k available
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
-> /dev
-> /dev/console
-> /root
POSIX conformance testing by UNIFIX
Initializing RT netlink socket
EISA bus registered
Searching for devices...
Found devices:
1. Coral SGC Graphics (10) at 0xf4000000 [0], versions 0x4, 0x0, 0x77
2. Mirage GSC Builtin Graphics (10) at 0xf8000000 [1], versions 0x13, 0x0, 0x85
3. Mirage Core BA (11) at 0xf0100000 [2], versions 0x29, 0x0, 0x81
4. Mirage Core SCSI (10) at 0xf0106000 [2/0/1], versions 0x29, 0x0, 0x82
5. Mirage Core LAN (802.3) (10) at 0xf0107000 [2/0/2], versions 0x29, 0x0, 0x8a
6. Mirage Core RS-232 (10) at 0xf0105000 [2/0/4], versions 0x29, 0x0, 0x8c
7. Mirage Core Centronics (10) at 0xf0102000 [2/0/6], versions 0x29, 0x0, 0x74
8. Mirage Audio (10) at 0xf0104000 [2/0/8], versions 0x29, 0x0, 0x7b
9. Mirage Core PC Floppy (10) at 0xf010a000 [2/0/10], versions 0x29, 0x0, 0x83
10. Mirage Core PS/2 Port (10) at 0xf0108000 [2/0/11], versions 0x29, 0x0, 0x84
11. Mirage Core PS/2 Port (10) at 0xf0108100 [2/0/12], versions 0x29, 0x0, 0x84
12. Mirage Wax BA (11) at 0xf0200000 [5], versions 0x13, 0x0, 0x8e
13. Mirage 100 Wax HIL (10) at 0xf0201000 [5/0/1], versions 0x13, 0x0, 0x73
14. Mirage Wax RS-232 (10) at 0xf0202000 [5/0/2], versions 0x13, 0x0, 0x8c
15. Mirage 100 (0) at 0xfffbe000 [8], versions 0x60b, 0x0, 0x4
16. Memory (1) at 0xfffbf000 [9], versions 0x4b, 0x0, 0x9
CPU(s): 1 x PA7100LC (PCX-L) at 100.000000 MHz
Lasi version 0 at 0xf0100000 found.
Wax at 0xf0200000 found.
BIO: pool of 256 setup, 14Kb (56 bytes/bio)
biovec pool[0]:   1 bvecs: 244 entries (12 bytes)
biovec pool[1]:   4 bvecs: 244 entries (48 bytes)
biovec pool[2]:  16 bvecs: 244 entries (192 bytes)
biovec pool[3]:  64 bvecs: 244 entries (768 bytes)
biovec pool[4]: 128 bvecs: 122 entries (1536 bytes)
biovec pool[5]: 256 bvecs:  61 entries (3072 bytes)
block request queues:
 4/128 requests per read queue
 4/128 requests per write queue
 enter congestion at 15
 exit congestion at 17
SCSI subsystem initialized
pty: 256 Unix98 ptys configured
Journalled Block Device driver loaded
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Serial: 8250/16550 driver $Revision: 1.90 $ IRQ sharing enabled
Gecko-style soft power switch enabled.
lp: driver loaded but no devices found
Generic RTC Driver v1.07
ttyS0 at MMIO 0xf0105800 (irq = 90) is a 16550A
ttyS1 at MMIO 0xf0202800 (irq = 121) is a 16550A
parport_init_chip: initialize bidirectional-mode.
parport0: PC-style at 0xf0102800, irq 88 [PCSPP,TRISTATE]
lp0: using parport0 (interrupt-driven).
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
Found i82596 at 0xf0107000, IRQ 87
eth0: 82596 at 0xf0107000, 08 00 09 7A DC 08 IRQ 87.
82596.c $Revision: 1.29 $
airo:  Probing for PCI adapters
airo:  Finished probing for PCI adapters
53c700: Version 2.8 By James.Bottomley@HansenPartnership.com
scsi0: 53c710 rev 2
scsi0 : LASI SCSI 53c700
scsi0: (2:0) Synchronous at offset 8, period 100ns
  Vendor: PLEXTOR   Model: CD-ROM PX-20TS    Rev: 1.01
  Type:   CD-ROM                             ANSI SCSI revision: 02
scsi0: (3:0) Synchronous at offset 8, period 100ns
  Vendor: SEAGATE   Model: ST32430N          Rev: HP04
  Type:   Direct-Access                      ANSI SCSI revision: 02
st: Version 20030413, fixed bufsize 32768, s/g segs 256
scsi0: (3:0) Enabling Tag Command Queuing
SCSI device sda: 4194685 512-byte hdwr sectors (2148 MB)
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3 sda4
Attached scsi disk sda at scsi0, channel 0, id 3, lun 0
sr0: scsi-1 drive
Uniform CD-ROM driver Revision: 3.12
Attached scsi generic sg0 at scsi0, channel 0, id 2, lun 0,  type 5
Attached scsi generic sg1 at scsi0, channel 0, id 3, lun 0,  type 0
STI GSC/PCI core graphics driver Version 0.9a
STI byte mode ROM at f4000000, hpa at f4000000
STI id 2bcb015a-9a02587, conforms to spec rev. 8.04
STI device: HPA4071A
STI word mode ROM at f0024000, hpa at f8000000
STI id 2b4ded6d-40a00499, conforms to spec rev. 8.04
STI device: HPA208LC1024
sticon: Initializing STI text console.
Console: switching to colour STI console 160x64
mice: PS/2 mouse device common for all mice
Found HIL bus at 0xf0201000, IRQ 126
HIL: no keyboard present.
input: HIL keyboard, ID -1 at 0xf0201000 (irq 126) found and attached
Keyboard initialization sequence failled
gsckbd_leds: timeout
input: PS/2 keyboard port at 0xf0108000 (irq 69) found and attached
input: PS/2 mouse port at 0xf0108100 (irq 69) found and attached
oprofile: using timer interrupt.
NET4: Linux TCP/IP 1.0 for NET4.0
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 16384)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 516k freed

INIT: version 2.84 booting
Mounting devfs on /dev
mount: devfs has wrong device number or fs type devfs not supported
Loading /etc/console/boottime.kmap.gz
Activating swap.
Adding 132920k swap on /dev/sda3.  Priority:-1 extents:1

Checking root file system...
fsck 1.34-WIP (21-May-2003)
/dev/sda4: clean, 105836/237120 files, 394653/474075 blocks
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on sda4, internal journal

System time was Sun Jun 22 09:37:50 UTC 2003.
Setting the System Clock using the Hardware Clock as reference...
System Clock set. System local time is now Sun Jun 22 09:37:52 UTC 2003.
Checking all file systems...
fsck 1.34-WIP (21-May-2003)
/dev/sda2: clean, 30/10944 files, 35929/43617 blocks
Setting kernel variables..
Mounting local filesystems...
/dev/sda2 on /boot type ext2 (rw)
Cleaning: /etc/network/ifstate.
Setting up IP spoofing protection: rp_filter.
Configuring network interfaces... eth0: link ok.

done.
Starting portmap daemon: portmap.
Loading the saved-state of the serial devices...
Setting up general console font...set_kernel_font: Function not implemented
cannot (un)set powersave mode
^[[14;30]
Setting the System Clock using the Hardware Clock as reference...
System Clock set. Local time: Sun Jun 22 11:37:59 CEST 2003

Cleaning: /tmp /var/lock /var/run.
Initializing random number generator... done.
Recovering nvi editor sessions... done.
Setting up X server socket directory /tmp/.X11-unix...done.

INIT: Entering runlevel: 2

Starting system log daemon: syslogd.
Starting kernel log daemon: klogd.
Starting mouse interface server: gpm.
Starting printer spooler: lpd.
Starting OpenBSD Secure Shell server: sshd.
Starting webmin: webmin.
Setting up X font server socket directory /tmp/.font-unix...done.
Starting X font server: xfs.
Starting internet superserver: xinetd.
Restoring mixer settings: failed.
Starting NFS common utilities: statd lockd.
Starting anac(h)ronistic cron: anacron.
Starting deferred execution scheduler: atd.
Starting periodic command scheduler: cron.
Setting up X server socket directory /tmp/.X11-unix...done.