Re: incorrect super block w recent changes
I did a newfs run on a sparse file and get a slighly different layout now: format FFSv1 endian little-endian magic 11954 timeThu Apr 30 10:53:04 2015 superblock location 8192id [ 5541ed70 4107aafa ] cylgrp dynamic inodes 4.4BSD sblock FFSv2 fslevel 4 nbfree 7082771 ndir1 nifree 14233853nffree 14 ncg 611 size57561588blocks 56662183 bsize 16384 shift 14 mask0xc000 fsize 2048shift 11 mask0xf800 frag8 shift 3 fsbtodb 2 bpg 11795 fpg 94360 ipg 23296 minfree 5% optim timemaxcontig 4 maxbpg 4096 symlinklen 60 contigsumsize 4 maxfilesize 0x000400400402 nindir 4096inopb 128 avgfilesize 16384 avgfpdir 64 sblkno 8 cblkno 16 iblkno 24 dblkno 1480 sbsize 2048cgsize 16384 csaddr 1480cssize 10240 cgrotor 0 fmod0 ronly 0 clean 0x01 Eliminating the dates, here are the changed lines: -nbfree 6806519 ndir7534nifree 14144970nffree 15854 +nbfree 7082771 ndir1 nifree 14233853nffree 14 -ncg610 size57561588blocks 56663655 +ncg611 size57561588blocks 56662183 -bpg11796 fpg 94368 ipg 23296 +bpg11795 fpg 94360 ipg 23296 Martin
Live Image build failure
Hi,
I've been trying to build liveimage for i386 and amd64 the last few dayw
without success. Today I cleaned the distdir and tried again, with the same
result:
...
--- NetBSD-7.99.13-amd64-live-wd0root.img ---
creating MBR labels...
dd if=/dev/zero of=work.mbr seek=$((4194304 - 1)) count=1
1+0 records in
1+0 records out
512 bytes transferred in 0.001 secs (512000 bytes/sec)
/home/sysbuild/Sysbuild/amd64/tools/bin/x86_64--netbsd-fdisk -f -i -u -b
261/255/63 -0 -a -s 169/2048/4192256
-F work.mbr
Making partition 0 active.
/home/sysbuild/Sysbuild/amd64/tools/bin/x86_64--netbsd-fdisk -f -i -c
work/usr/mdec/mbr -F work.mbr
dd if=work.mbr count=2048 | cat - imgroot.fs work.img
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.027 secs (38836148 bytes/sec)
dd if=/dev/zero of=work.swap seek=$((262144 - 1)) count=1
1+0 records in
1+0 records out
512 bytes transferred in 0.001 secs (512000 bytes/sec)
cat work.swap work.img
/home/sysbuild/Sysbuild/amd64/tools/bin/nbdisklabel -R -F work.img
work.diskproto
nbdisklabel: unknown label: use -M/-B and $MACHINE/$MACHINE_ARCH
*** [NetBSD-7.99.13-amd64-live-wd0root.img] Error code 1
nbmake[5]: stopped in /home/sysbuild/src/distrib/amd64/liveimage/emuimage
1 error
nbmake[5]: stopped in /home/sysbuild/src/distrib/amd64/liveimage/emuimage
*** Failed target: live_image-emuimage
*** Failed command: _makedirtarget() { dir=$1; shift; target=$1; shift;
case ${dir} in /*) this=${dir}/; real=${dir} ;; .)
this=/home/sysbuild/src/distrib/amd64/liveimage/;
real=/home/sysbuild/src/distrib/amd64/liveimage ;; *)
this=/home/sysbuild/src/distrib/amd64/liveimage/${dir}/;
real=/home/sysbuild/src/distrib/amd64/liveimage/${dir} ;; esac;
show=${this:-.}; echo ${target} === ${show%/}${1:+ (with: $@)}; cd
${real} /home/sysbuild/Sysbuild/amd64/tools/bin/nbmake
_THISDIR_=${this} $@ ${target}; }; _makedirtarget emuimage live_image
*** Error code 2
Stop.
nbmake[4]: stopped in /home/sysbuild/src/distrib/amd64/liveimage
*** [live_image] Error code 1
nbmake[3]: stopped in /home/sysbuild/src/distrib/amd64
1 error
nbmake[3]: stopped in /home/sysbuild/src/distrib/amd64
*** Failed target: live_image-amd64
*** Failed command: _makedirtarget() { dir=$1; shift; target=$1; shift;
case ${dir} in /*) this=${dir}/; real=${dir} ;; .)
this=/home/sysbuild/src/distrib/; real=/home/sysbuild/src/distrib ;; *)
this=/home/sysbuild/src/distrib/${dir}/;
real=/home/sysbuild/src/distrib/${dir} ;; esac; show=${this:-.}; echo
${target} === ${show%/}${1:+ (with: $@)}; cd ${real}
/home/sysbuild/Sysbuild/amd64/tools/bin/nbmake _THISDIR_=${this} $@
${target}; }; _makedirtarget amd64 live_image
*** Error code 2
Stop.
nbmake[2]: stopped in /home/sysbuild/src/distrib
..
The same happens with i386.
Chavdar Ivanov
Re: amd64/7.0_BETA fails to probe USB devices?
A kernel compiled with options USB_DEBUG doesn't provide any more information that I can see [...] With additionally usbdebug and uhubdebug set to 10 resulted in the attached boot messages. cd0 is still not probed. Regards, - Håvard Apr 28 23:39:11 tos-res su: he to root on /dev/pts/2 Password: Login incorrect or refused on this terminal. login: root Apr 28 23:40:12 tos-res login: ROOT LOGIN (root) on tty console Last login: Tue Apr 28 13:56:37 2015 on console Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 7.0_BETA (USB_DEBUG) #0: Tue Apr 28 13:58:53 UTC 2015 Welcome to NetBSD! This system is running a beta release of the NetBSD operating system, aimed at stabilizing the next formal release. It is close to formal release quality, but may still contain bugs, even serious ones. Please bear this in mind and use the system with care. You are encouraged to test this version as thoroughly as possible. Should you encounter any problem, please report it back to the development team using the send-pr(1) utility (requires a working MTA). If yours is not properly set up, use the web interface at: http://www.NetBSD.org/support/send-pr.html Thank you for helping us test and improve this beta NetBSD release. You have new mail. [3gHHHHHHH HHTerminal type is vt100. We recommend that you create a non-root account and use su(1) for root access. tos-res# shutdown -r now Shutdown NOW! shutdown: [pid 2676] tos-res# wall: You have write permission turned off; no reply possible *** FINAL System shutdown message from r...@tos-res.uninett.no *** System going down IMMEDIATELY Apr 28 23:40:17 tos-res shutdown: reboot by root: System shutdown time has arrived About to run shutdown hooks... Stopping cron. Waiting for PIDS: 1951. Stopping inetd. Waiting for PIDS: 1630. Saved entropy to /var/db/entropy-file. Removing block-type swap devices swapctl: removing /dev/sd0b as swap device Tue Apr 28 23:40:23 UTC 2015 Done running shutdown hooks. Apr 28 23:40:29 tos-res syslogd[560]: Exiting on signal 15 syncing disks... done uhub3: detached uhub2: detached ukphy3: detached ukphy2: detached ukphy1: detached ukphy0: detached wm3: detached wm2: detached wm1: detached wm0: detached atabus5: detached atabus4: detached atabus3: detached atabus2: detached atabus1: detached atabus0: detached pci7: detached pci6: detached pci5: detached pci4: detached pci3: detached pci1: detached sysbeep0: detached midi0: detached ppb6: detached ppb5: detached ppb4: detached ppb3: detached ppb2: detached ppb0: detached pchb0: detached audio0: detached pci10: detached sd0: detached scsibus0: detached mfi0: detached pci2: detached ppb1: detachedrebooting... NetBSD/x86 BIOS Boot, Revision 5.9 (from NetBSD 6.1.3) Memory: 635/1933196 k 1. Boot normally 2. Boot single user 3. Disable ACPI 4. Disable ACPI and SMP 5. Drop to boot prompt Choose an option; RETURN for default; SPACE to stop countdown. Option 1 will be chosen in 5 seconds. 0 seconds. Option: [1]:5 type ? or help for help. boot netbsd.usb
Re: Failure in amd64 7.99.11
Yes, I saw it and got a VM running under Hyper-V yesterday; still getting
'tlp: receive ring overflow' though, as always; I had earlier a kernel with
tlp driver modified not to use this message.
Chavdar
On Wed, 29 Apr 2015 at 22:57 Paul Goyette p...@vps1.whooppee.com wrote:
Christos has already fixed this.
On Wed, 29 Apr 2015, Chavdar Ivanov wrote:
Anyway, I am getting literally exactly the same message when trying to
install under Hyper-V (only curlwp is slightly different).
Chavdar
On Wed, 29 Apr 2015 at 09:26 Paul Goyette p...@vps1.whooppee.com
wrote:
Yes, I corrected the subject on a subsequent message.
On Wed, 29 Apr 2015, Chavdar Ivanov wrote:
Why are you having 7.99.11? It has been 7.99.13 for some days now.
Chavdar
On Wed, 29 Apr 2015 at 02:02 Paul Goyette p...@vps1.whooppee.com
wrote:
While running sysinst under qemu, I get the following, right after
sysinst has run newfs:
/targetroot: bad dir ino 2 at offset 0: mangled entry
panic: bad dir
fatal breakpoint trap in supervisor mode
trap type 1 code 0 rip 80289e5d cs 8 rflags 246 cr2
7f7ff74a0830
ilevel 0 rsp fe8001dd8980
curlwp 0xfe800f9e5580 pid 52.1 lowest kstack 0xfe8001dd52c0
Stopped in pid 52.1 (mkdir) at netbsd:breakpoint+0x5: leave
db{0}
Sources were updated via anoncvs on 2015-04-29 at 00:09:37 UTC
The only recent commit I see which might be relevant is
Module Name:src
Committed By: christos
Date: Tue Apr 28 15:15:54 UTC 2015
Modified Files:
src/sbin/newfs: mkfs.c
Log Message:
reduce bss usage
-
| Paul Goyette | PGP Key fingerprint: | E-mail addresses:
|
| (Retired)| FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com
|
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at
netbsd.org
|
-
-
| Paul Goyette | PGP Key fingerprint: | E-mail addresses:
|
| (Retired)| FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com
|
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org
|
-
-
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| (Retired)| FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com|
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org |
-
Re: Failure in amd64 7.99.11
Anyway, I am getting literally exactly the same message when trying to
install under Hyper-V (only curlwp is slightly different).
Chavdar
On Wed, 29 Apr 2015 at 09:26 Paul Goyette p...@vps1.whooppee.com wrote:
Yes, I corrected the subject on a subsequent message.
On Wed, 29 Apr 2015, Chavdar Ivanov wrote:
Why are you having 7.99.11? It has been 7.99.13 for some days now.
Chavdar
On Wed, 29 Apr 2015 at 02:02 Paul Goyette p...@vps1.whooppee.com
wrote:
While running sysinst under qemu, I get the following, right after
sysinst has run newfs:
/targetroot: bad dir ino 2 at offset 0: mangled entry
panic: bad dir
fatal breakpoint trap in supervisor mode
trap type 1 code 0 rip 80289e5d cs 8 rflags 246 cr2 7f7ff74a0830
ilevel 0 rsp fe8001dd8980
curlwp 0xfe800f9e5580 pid 52.1 lowest kstack 0xfe8001dd52c0
Stopped in pid 52.1 (mkdir) at netbsd:breakpoint+0x5: leave
db{0}
Sources were updated via anoncvs on 2015-04-29 at 00:09:37 UTC
The only recent commit I see which might be relevant is
Module Name:src
Committed By: christos
Date: Tue Apr 28 15:15:54 UTC 2015
Modified Files:
src/sbin/newfs: mkfs.c
Log Message:
reduce bss usage
-
| Paul Goyette | PGP Key fingerprint: | E-mail addresses:
|
| (Retired)| FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com
|
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org
|
-
-
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| (Retired)| FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com|
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org |
-
Re: Failure in amd64 7.99.11
On Wed, Apr 29, 2015 at 02:39:42PM +, Chavdar Ivanov wrote: Anyway, I am getting literally exactly the same message when trying to install under Hyper-V (only curlwp is slightly different). NetBSD doesn't agree with the HyperV emulation of the IOAPIC. You can try to disable it from userconf. Joerg
daily CVS update output
Updating src tree: P src/external/bsd/blacklist/bin/blacklistctl.8 P src/external/bsd/blacklist/bin/blacklistd.8 P src/external/bsd/blacklist/bin/blacklistd.conf.5 P src/sys/arch/amd64/conf/Makefile.amd64 P src/sys/arch/arm/conf/Makefile.arm P src/sys/conf/Makefile.kern.inc P src/sys/dev/bluetooth/bcsp.c P src/sys/dev/pci/if_bge.c P src/sys/dev/pci/if_bgereg.h P src/sys/dev/splash/files.splash U src/sys/dev/splash/splash.mk P src/sys/dev/wsfb/files.wsfb P src/sys/kern/init_main.c P src/sys/net/route.c P src/sys/net/route.h P src/sys/netinet6/nd6.c P src/usr.sbin/sysinst/msg.mi.en Updating xsrc tree: Killing core files: Running the SUP scanner: SUP Scan for current starting at Fri May 1 03:06:58 2015 SUP Scan for current completed at Fri May 1 03:09:23 2015 SUP Scan for mirror starting at Fri May 1 03:09:23 2015 SUP Scan for mirror completed at Fri May 1 03:12:15 2015 Updating file list: -rw-rw-r-- 1 srcmastr netbsd 46663327 May 1 03:27 ls-lRA.gz
Re: incorrect super block w recent changes
On Thu, Apr 30, 2015 at 12:34:00AM +, Michael van Elst wrote: This is ensured by mkfs.c 1.96. How old is your filesystem? The oldest files in /etc are from july 2010, so that is probably when I created it. Martin
