From owner-freebsd-current@FreeBSD.ORG Fri Jul 29 23:43:45 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1780E16A41F for ; Fri, 29 Jul 2005 23:43:45 +0000 (GMT) (envelope-from lehmann@ans-netz.de) Received: from avocado.salatschuessel.net (avocado.salatschuessel.net [83.136.81.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57EFF43D45 for ; Fri, 29 Jul 2005 23:43:44 +0000 (GMT) (envelope-from lehmann@ans-netz.de) Received: (qmail 68067 invoked by uid 89); 29 Jul 2005 23:43:30 -0000 Received: from unknown (HELO kartoffel.salatschuessel.net) (83.136.81.185) by avocado.salatschuessel.net with SMTP; 29 Jul 2005 23:43:30 -0000 Date: Sat, 30 Jul 2005 01:43:42 +0200 From: Oliver Lehmann To: current@freebsd.org Message-Id: <20050730014342.0843080d.lehmann@ans-netz.de> X-Mailer: Sylpheed version 2.0.0 (GTK+ 2.6.8; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: mlx(4) fully and ep(4) partially broken on 6.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jul 2005 23:43:45 -0000 Hi, after a <1sec power outage caused by a tempest some of my systems decided to reboot. One of the systems was my freshly updated (5.4->6.0) router. 1st problem with 6.0: --------------------- The system kept rebooting automaticly after it detected ep0. It was saying sth. like "ep0: no irq?!". The funny thing is, one line above it wrote sth. like "ep0 <3COM....> irq 9 ....". for me that looks like ep0 has of course an irq assigned. I am happy that I have physical access to this system! Damn! I changed the perfectly-on-5.4 working 3com card with an other I had on storage - panic is gone now. 2nd problem with 6.0: --------------------- The system nicely detects my mlx Controller: mlx0: port 0xec00-0xec7f mem 0xffafff80-0xffafffff irq 11 at device 17.0 on pci0 mlx0: DAC960P/PD, 2 channels, firmware 3.51-0-04, 16MB RAM but no disk (mlxd0) which means no disk over all for this system! *sigh* - I'm out of luck today So I took an old hdd with 4.11 installed, booted the system with it, mounted the well detected mlx-disk, compiled 6.0-GENERIC on an 6.0 system, transfered the GENERIC kernel via nfs to my mlxd0a:/boot/kernel, rebooted - nice still no mlxd0 on 6.0 - so I'm not able to mount root with 6.0 And once more... I'm happy that I have physical access to this system. For all that I lost 3.5hrs and I'm not really amused about this. I saw no other way then restoring the backup I made last sunday to get my router back working. DAT is great when it comes to speed. :( on my restored 5.4 system it looks like: mlxd0: on mlx0 mlxd0: 2150MB (4403200 sectors) RAID 1 (online) root@gurke olivleh1> mlxcontrol config # Controller # # Physical devices connected: # disk0000 (online) # 2150MB fast wide sync tag-enabled # disk0100 (online) # 2150MB fast wide sync tag-enabled # # System Drives defined: drive00 RAID1 writethrough span0 0x00000000-0x00433000 2150MB on disk0000 disk0100 root@gurke olivleh1> Please please someone should fix both issues until 6.0 gets released. If any further help (testing, informations) is required from my side please let me know. I've a 2nd mlx controller (but 2.73 BIOS) I can probably try with in a different system. Greetings, Oliver -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/