Re: 9.1-RCs issues
What 9-stable did you imply? 9.0-Release has the same problem at offset 274GB. I could not find current snapshots, ftp.freebsd.org://pub/FreeBSD/snapshots is empty, and I cannot ftp to snapshots.jp.freebsd.org. From: Hans Petter Selasky hsela...@c2i.net To: freebsd-...@freebsd.org; hack...@freebsd.org Cc: Jin Guojun jguo...@sbcglobal.net; b...@freebsd.org; curr...@freebsd.org Sent: Sun, October 7, 2012 3:40:50 AM Subject: Re: 9.1-RCs issues On Sunday 07 October 2012 01:42:33 Jin Guojun wrote: 1) moused stops functioning on 9.1-RC2. Neither PS2 nor USB mouse can work. 9.1-RC1 has no such problem. 2) All i386 / amd64 of 9.1-RC1/RC2 have USB read failure -- see dmesg output at end of this email. ada0 is internal SATA drive for system disk -- s# partitions: /, /tmp, /var, /usr s1 -- 6.4-Release s2 -- 8.3-Release s3 -- 9.1-RC2 amd64 s4 -- 9.1-RC2 i386 -- This slice also contains /home da0 is external USB2 drive (300GB) plugged in USB2 port -- mounted on /mnt Regarding USB, it might be some patches did not reach it for the RC's. Have you tried 9-stable, or any 10-current snapshots? --HPS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Panic possibly related to glabel/geom and siis(4)
This is similar to what I have fight on last two weeks (was 8.0-RC USB/FS). My back trace from the panic is some different from yours, but the behave is the same. When access USB drives from 8.0-RC and 8.0-R will cause drives dead, vanish or reset, thus causing panic. From both cases, it looks like a hotplug/automount related problem. --- On Tue, 11/24/09, Steve Polyack kor...@comcast.net wrote: From: Steve Polyack kor...@comcast.net Subject: Panic possibly related to glabel/geom and siis(4) To: freebsd-hardw...@freebsd.org, freebsd-stable freebsd-stable@FreeBSD.org, freebsd-g...@freebsd.org Date: Tuesday, November 24, 2009, 5:40 PM I have a system running 8.0-PRERELEASE with multiple drives and SATA port multipliers (siis controllers and PMPs). All of the attached drives are labeled via glabel(8) and then included into a ZFS pool. During some testing to determine how the system would react to a dead drive (simulated by physically removing a drive during operation), I was able to produce a panic. Now, I know that the SATA PMP and siis(4) code to handle and recover from device errors is incomplete, but I believe the crash may be particular to using glabel'd drives. Basically, after removing a drive while the zpool is in use and issues 'camcontrol reset' and 'rescan' on the appropriate bus, the physical device associated with the drive disappears. In this case: (pass5:siisch7:0:15:0): lost device (pass5:siisch7:0:15:0): removing device entry (ada2:siisch7:0:0:0): lost device and /dev/ada2 disappears. However, the associated glabel /dev/label/bigdisk07 remains. Since my ZFS pool is created based on the drive glabels, I believe this is why ZFS never notices the drives disappear either. Do glabels typically go away after a physical device is lost? Should this not be the case? After some runtime with the physical device missing, a kernel panic is produced: ada2:siisch7:0:0:0): Synchronize cache failed (ada2:siisch7:0:0:0): removing device entry Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 14 fault virtual address = 0x48 fault code = supervisor write data, page not present instruction pointer = 0x20:0x8035f375 stack pointer = 0x28:0xff86db60 frame pointer = 0x28:0xff86db70 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 2 (g_event) [thread pid 2 tid 100014 ] Stopped at _mtx_lock_flags+0x15: lock cmpxchgq %rsi,0x18(%rdi) db bt Tracing pid 2 tid 100014 td 0xff00014d4ab0 _mtx_lock_flags() at _mtx_lock_flags+0x15 vdev_geom_release() at vdev_geom_release+0x33 vdev_geom_orphan() at vdev_geom_orphan+0x15c g_run_events() at g_run_events+0x104 g_event_procbody() at g_event_procbody+0x55 fork_exit() at fork_exit+0x118 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xff86dd30, rbp = 0 --- I'm open to try patches and other suggestions. Thanks. ___ freebsd-hardw...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to freebsd-hardware-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b
dd 1m zero on the drive and rerun the 8.0Beta4 DVD. Created two slices S1 and S2, and did auto labling (unix partiton) on S1, hit W, the problem persists. Boot system with freeBSD 6.4, and 6.4 sees two slices (MBR partitions) S1 and S2, but no any Unix partition (ad0s1a, ad0s1b etc) on S1. Boot back to 8.0-Beta4, it still sees not Slice created. At this point, it is obviously that 8.0 looks in a wrong MBR location -- 8.0 created slices can be seen by 6.4 but not 8.0 itself. --- On Mon, 9/14/09, Thierry Thomas thie...@freebsd.org wrote: From: Thierry Thomas thie...@freebsd.org Subject: Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b To: Jin Guojun jguo...@sbcglobal.net Cc: b...@freebsd.org, freebsd-stable@freebsd.org, curr...@freebsd.org Date: Monday, September 14, 2009, 10:06 PM Le Lun 14 sep 09 à 23:08:53 +0200, Jin Guojun jguo...@sbcglobal.net écrivait : I do not enve know how to make dangerously dedicated disk, and the 8.0 may do this sliently. No, I don't think so! But such a problem may arise if your disk had been installed as dangerously dedicated in a former version. Unfortunately, previous versions of sysinstall have created uncorrect labels, and the new gpart in 8.0 does not see them. In that case, you have to boot kernel.old and wipe out the bad label. If you reboot with a 7.2 kernel, can you see your missing partitions? -- Th. Thomas. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b
It seems that disklabel is the problem spot. Use 8.0 Partition menu to allocate 2 slices (partitions) 20GB for S1 and rest for S2, then install 8.0-Beta4 on S1. W command in slice (Partition) menu succeed with bootloader manager installing option (Choose FreeBSD), but W command in Label menu had the same error -- Unable to find device node ... After quite installationm and restart the system, the bootloader is still show old partitions (S1 DOS, S2/S3 7.2). Boot 8.0-Beta4 DVD again, and Partition menu shows no partition at all (no slice allocated). This indicates that disklabel did not correctly write disk partition information on to the dirve. --- On Mon, 9/14/09, Robert Huff roberth...@rcn.com wrote: From: Robert Huff roberth...@rcn.com Subject: Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b To: Jin Guojun jguo...@sbcglobal.net Cc: Robert Huff roberth...@rcn.com, curr...@freebsd.org, b...@freebsd.org, freebsd-stable@freebsd.org Date: Monday, September 14, 2009, 3:49 AM Jin Guojun writes: Did not find anything from current, but found the same problem has been reported in earlier releases in those archives, and the latest was May 2009: Try this (for the fix) : http://lists.freebsd.org/pipermail/freebsd-current/2009-September/011254.html Robert Huff ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b
I do not enve know how to make dangerously dedicated disk, and the 8.0 may do
this sliently.
ad0 had three DOS partitions (slices),
S1 for DOS
S2 for FreeBSD 7.2
S3 for another FreeBSD
When boot to 8.0-Beta{3, 4}, 8.0 sees not partition, which means 8.0 looked at
a wrong location for partition table.
After did partition (slices S1 for FreebSD and S2 for nothing) and
Label (Unix partitions, failed to find device node /dev/ad0s1b in /dev),
content of 7.2 is gone.
But, the original partitions are still in the MBR (S1 for DOS, and S2 and S3
for FreeBSD).
--- On Mon, 9/14/09, Thierry Thomas thie...@freebsd.org wrote:
From: Thierry Thomas thie...@freebsd.org
Subject: Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b
To: Jin Guojun jguo...@sbcglobal.net
Cc: b...@freebsd.org, freebsd-stable@freebsd.org, curr...@freebsd.org
Date: Monday, September 14, 2009, 6:45 PM
Le Lun 14 sep 09 à 18:56:38 +0200,
Jin Guojun jguo...@sbcglobal.net
écrivait :
It seems that disklabel is the problem spot.
Hello,
I encountered such a problem too; was your disk ad0
installed as
dangerously dedicated?
Regards,
--
Th. Thomas.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8.0-Beta installation problem -- Unable to find /dev/ad0s1b
Tried to install from both 8.0-BETA{3, 4}-i386-dvd1.iso on a Phenom 9600
system and having
some disk problems.
The system is running 6.x and/or 7.2 FreeBSD (on different drives).
Disconnected rest drives and only left 7.2 drive in.
ad0: 76319MB Seagate ST3802110A 3.AAJ at ata0-master UDMA100
Boot 8.0-BETA3-i386-dvd1.iso and sees no partition at all on the 7.2 disk.
Boot back to 7.2 and everything works fine, so system has no hardware
problem.
Boot 8.0-BETA3-i386-dvd1.iso again, still sees no partition, so
reconfigured partition with
autoconfigure - A
512M for / on /dev/ad0s1a
about 4G for swap on /dev/ad0s1b
about 2.2G on /var
512M for /tmp
rest spaces are for /usr
After commit, installation says --
Unable to find device node for /dev/ad0s1b in /dev
The Creation of file system will abort.
OK
[Press enter or space]
Hit CR and see some other errors, then back to installation menu.
Reboot the system, 7.2 is gone.
Download 8.0-BETA4-i386-dvd1.iso and burned another DVD, also did verify
between DVD and ISO for OK.
Run installation from Beta4 DVD, the same problem presents again.
If my memory is correct, either 8.0-Beta1 or one version earlier than it
was working on this machine.
Is anything changed that requires different installation procedure? or
is this a bug introduced recently?
-Jin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b
Did not find anything from current, but found the same problem has been
reported in earlier releases in those archives, and the latest was May 2009:
* Rambler: FreeBSD mail archives search
* MarkMail: FreeBSD mail archives search
Two directly related to 8.0 was on Mar 25, 2009. One failure was due to the
FreeBSD is on the second slice, which sound liek a bug; but the other is not
clear.
In my case, FreeBSD is on the first slice, so it is not the same problem.
From 8.0-Beta{3, 4} cannot recognize FreeBSD 7.2 partition tables, it looks
like that there is a disklable and/or partition related problem in 8.0-Beta.
--- On Mon, 9/14/09, Robert Huff roberth...@rcn.com wrote:
From: Robert Huff roberth...@rcn.com
Subject: 8.0-Beta installation problem -- Unable to find /dev/ad0s1b
To: Jin Guojun jguo...@sbcglobal.net
Cc: questi...@freebsd.org, freebsd-stable@freebsd.org
Date: Monday, September 14, 2009, 2:13 AM
Jin Guojun writes:
Tried to install from both 8.0-BETA{3, 4}-i386-dvd1.iso on a
Phenom 9600 system and having some disk problems.
The system is running 6.x and/or 7.2 FreeBSD (on different drives).
Disconnected rest drives and only left 7.2 drive in.
ad0: 76319MB Seagate ST3802110A 3.AAJ at ata0-master UDMA100
Boot 8.0-BETA3-i386-dvd1.iso and sees no partition at all on the 7.2 disk.
Boot back to 7.2 and everything works fine, so system has no hardware
problem.
Boot 8.0-BETA3-i386-dvd1.iso again, still sees no partition, so
reconfigured partition with
autoconfigure - A
512M for / on /dev/ad0s1a
about 4G for swap on /dev/ad0s1b
about 2.2G on /var
512M for /tmp
rest spaces are for /usr
After commit, installation says --
Unable to find device node for /dev/ad0s1b in /dev
The Creation of file system will abort.
OK
[Press enter or space]
Look at the archives of current@ within
the last three weeks.
I (and I believe at least one other person) had what seems
like the
same problem and found a work-around.
Robert Huff
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
