Re: Attempt to access beyond end of device/Raid linear and 1

[Arnt Karlsen <arnt@c2i.net>]

On Mon, 8 Dec 2003 12:39:41 -0600, 
Larry W.Irwin Sr. <riverw@bigriver.net> wrote in message 
<[🔎] 20031208123941.1f8a9f3e.riverw@bigriver.net>:

> Kernel command line: BOOT_IMAGE=Linux ro root=306
> Initializing CPU#0
> Detected 474.979 MHz processor.
> Console: colour VGA+ 80x25
> Calibrating delay loop... 946.99 BogoMIPS

..an overclocked K6-2 450?

> Memory: 245332k/253888k available (895k kernel code, 8172k reserved,
> 233k data, 192k init, 0k highmem) 
> Dentry-cache hash table entries: 32768 (order: 6, 262144 bytes) 
> Inode-cache hash table entries: 16384 (order: 5, 131072 bytes) 
> Mount-cache hash table entries: 4096 (order: 3, 32768 bytes) 
> Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes) 
> Page-cache hash table entries: 65536 (order: 6, 262144 bytes) 
> CPU: Before vendor init, caps: 008021bf 808029bf 00000000, vendor = 2 
> CPU: L1 I Cache: 32K (32 bytes/line), D cache 32K (32 bytes/line) 
> CPU: After vendor init, caps: 008021bf 808029bf 00000000 00000002 
> CPU: After generic, caps: 008021bf 808029bf 00000000 00000002 
> CPU: Common caps: 008021bf 808029bf 00000000 00000002 
> CPU: AMD-K6(tm) 3D processor stepping 0c

-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.