From owner-freebsd-mobile Mon Sep 29 21:12:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA00259 for mobile-outgoing; Mon, 29 Sep 1997 21:12:57 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca13-23.ix.netcom.com [204.32.168.55]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA00253 for ; Mon, 29 Sep 1997 21:12:52 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id VAA06938; Mon, 29 Sep 1997 21:12:41 -0700 (PDT) Date: Mon, 29 Sep 1997 21:12:41 -0700 (PDT) Message-Id: <199709300412.VAA06938@silvia.HIP.Berkeley.EDU> To: mobile@freebsd.org Subject: resume and TP560E From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-mobile@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I recently got an IBM ThinkPad 560E (thanks for the advice, Hosakawa-san :). Got FreeBSD installed (PAO-2.2-970616), and it's now up and running happily. However, when I suspend the machine, I see messages like this: === Sep 29 16:19:09 bubble /kernel: ep0: suspending Sep 29 16:19:09 bubble /kernel: Entire system suspend failure: errcode = 96 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Sep 29 16:19:09 bubble /kernel: calcru: negative time: -284306 usec Sep 29 16:47:45 bubble /kernel: resumed from suspended mode (slept 00:28:36) Sep 29 16:47:45 bubble /kernel: ep0: already unloaded Sep 29 16:47:45 bubble /kernel: Return IRQ=10 Sep 29 16:47:46 bubble /kernel: Card inserted, slot 0 Sep 29 16:47:50 bubble pccardd[34]: Card "3Com Corporation"("3C589D") matched "3Com Corporation" ("3C589") Sep 29 16:47:53 bubble /kernel: ep0: utp/bnc[*UTP*] address 00:60:97:93:48:aa === The lights all go off, and when I close and open the lid, the machine comes up fine. Do I have to worry about it? Also, I'm not sure how much space I have to leave at the end of the hard drive. According to IBM, this machine can have up to 80MB of memory, so the empty space should be a little more than that, right? Well, here is what fdisk says: === >> fdisk ******* Working on device /dev/rwd0 ******* parameters extracted from in-core disklabel are: cylinders=1024 heads=64 sectors/track=63 (4032 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1024 heads=64 sectors/track=63 (4032 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 11,(unknown) start 63, size 1435329 (700 Meg), flag 0 beg: cyl 0/ sector 1/ head 1; end: cyl 355/ sector 63/ head 63 The data for partition 2 is: sysid 10,(OS/2 Boot Manager or OPUS) start 4120704, size 4032 (1 Meg), flag 0 beg: cyl 1022/ sector 1/ head 0; end: cyl 1022/ sector 63/ head 63 The data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 1435392, size 2677248 (1307 Meg), flag 80 beg: cyl 356/ sector 1/ head 0; end: cyl 1019/ sector 63/ head 63 The data for partition 4 is: === I asked the vendor to divide the disk (2GB, 4128768 sectors according to dmesg) into three slices and install Lose95 in the first third. (The partition "2" is actually at the end.) I merged the second and third slices and installed FreeBSD on it. Now that I think about it, I didn't leave much space at the end, unless there are some sectors behind the partition "2" that doesn't show up in fdisk. Am I in danger of corrupting the last filesystem? I ran an fsck on the last partition after a resume, and it only showed one unreferenced file (ok, maybe that's bad enough, but it's an fsck on a running system, even though I did a sync first). Satoshi P.S. What's that "sysid 11" partition? A new Minisoft thing? Booteasy doesn't know about it either (shows up as "??").