X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7D9FC.4EC7FE08@onstor-exch02.onstor.net>; Wed, 8 Aug 2007 12:40:08 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: No problems build ing the kernel
Date: Wed, 8 Aug 2007 12:40:08 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02215962@onstor-exch02.onstor.net>
In-Reply-To: <20070808132222.44d94b33@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: No problems build ing the kernel
Thread-Index: AcfZ+dWBqC1MNuIfQqeVQcBKP8sXNAAAjoNw
From: "Larry Scheer" <larry.scheer@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Ah, I thought there was discussion (non-email) prior to this email.

-----Original Message-----
From: Andy Sharp=20
Sent: Wednesday, August 08, 2007 1:22 PM
To: Larry Scheer
Subject: Re: No problems build ing the kernel

On Tue, 7 Aug 2007 16:31:28 -0700 "Larry Scheer"
<larry.scheer@onstor.com> wrote:

Here's the email I was talking about.

> It didn't boot...
>=20
> Some interesting messages from the ssc console follow:
>=20
> Linux version 2.6.21-rc4-bc9k (larrys@linux-compile.onstor.net) (gcc
> version 4.1.2 20061115 (prerele
> ase) (Debian 4.1.1-21)) #1 Tue Aug 7 15:22:05 PDT 2007
> ...
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> ...

This is what I call an oops.  As in Oopsie-daisy.

> CPU 0 Unable to handle kernel paging request at virtual address
> d000001e, epc =3D=3D 83154018, ra =3D=3D 831
> 53ffc
> ...
> Modules linked in:
> [<83154018>] ide_probe+0x428/0x570
> [<8315a924>] pcmcia_device_probe+0xd0/0x1bc
> [<83139548>] really_probe+0x80/0x1a8
> [<83138478>] bus_for_each_drv+0x64/0xcc
> [<8313986c>] device_attach+0xac/0xd4
> [<83138354>] bus_attach_device+0x30/0x8c
> [<83136ae4>] device_add+0x610/0x794
> [<8315b3e8>] pcmcia_device_add+0x1f8/0x3a0
> [<8315b6bc>] pcmcia_card_add+0xc0/0x184
> [<8315b868>] ds_event+0xe8/0x118
> [<83154724>] send_event+0xcc/0x110
> [<83154e14>] socket_insert+0xe0/0x1c0
> [<83155924>] pccardd+0x314/0x31c
> [<83039154>] kthread+0xe8/0x130
> [<83004930>] kernel_thread_helper+0x10/0x18
> eth0: DSPCFG accepted after 0 usec.
> eth0: link up.
> eth0: Setting full-duplex based on negotiated link capability.
> pd6729_get_status: socket 1 IO card STATUS 0xff, INTCTL 0x60
> pd6729_get_status: socket 1 extended defs: 0x37
> pd6729_get_status: socket 1 data=3D0x37, value=3D0x1c0
> pd6729_get_status: socket 1 IO card STATUS 0xef, INTCTL 0x60
> pd6729_get_status: socket 1 extended defs: 0x37
> pd6729_get_status: socket 1 data=3D0x37, value=3D0x1c0
> pccard: PCMCIA card inserted into slot 1
> cs: memory probe 0x18800000-0x19ffffff: excluding
> 0x18800000-0x1897ffff 0x18f80000-0x19ffffff
> nonstatic_find_mem_region: alloc_res returned 0
> IP-Config: Complete:
>       device=3Deth0, addr=3D10.2.11.4, mask=3D255.255.0.0, =
gw=3D10.2.0.1,
>      host=3Deng216, domain=3D, nis-domain=3D(none),
>      bootserver=3D10.2.0.4, rootserver=3D10.2.0.4, rootpath=3D
>=20
> Stalls here...
> _____________________________________________
> From: Maxim Kozlovsky=20
> Sent: Tuesday, August 07, 2007 3:45 PM
> To: Larry Scheer; dl-Cougar
> Subject: RE: No problems build ing the kernel
>=20
> Does it run?
