Locks up with CURRENT
Hi, I cvsuped at about 10/10/03 11PM GMT and rebuilt world and kernel. It locks up after displaying: GEOM: create disk ad0 dp=0xc456d370 ad0: 28615MB TOSHIBA MK3021GAS [58140/16/63] at ata0-master UDMA100 ata1: resetting devices .. done System is a Toshiba Satellite 2455 notebook. -- Antony T Curtis BSc Unix Analyst Programmer http://homepage.ntlworld.com/antony.t.curtis/ signature.asc Description: This is a digitally signed message part
Re: Locks up with CURRENT
On Sat, 2003-10-11 at 10:36, Antony T Curtis wrote: Hi, I cvsuped at about 10/10/03 11PM GMT and rebuilt world and kernel. It locks up after displaying: GEOM: create disk ad0 dp=0xc456d370 ad0: 28615MB TOSHIBA MK3021GAS [58140/16/63] at ata0-master UDMA100 ata1: resetting devices .. done System is a Toshiba Satellite 2455 notebook. Removing the CDRW drive allowed it to boot -- Antony T Curtis BSc Unix Analyst Programmer http://homepage.ntlworld.com/antony.t.curtis/ signature.asc Description: This is a digitally signed message part
Re: Locks up with CURRENT
On Sat, 2003-10-11 at 17:10, Anish Mistry wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 11 October 2003 06:20 am, Antony T Curtis wrote: On Sat, 2003-10-11 at 10:36, Antony T Curtis wrote: Hi, I cvsuped at about 10/10/03 11PM GMT and rebuilt world and kernel. It locks up after displaying: GEOM: create disk ad0 dp=0xc456d370 ad0: 28615MB TOSHIBA MK3021GAS [58140/16/63] at ata0-master UDMA100 ata1: resetting devices .. done System is a Toshiba Satellite 2455 notebook. Removing the CDRW drive allowed it to boot Does your laptop have an Acer chipset? There are issues with them, I have a similar problem on my fujitsu. No - it appears to have an Intel ICH4 chipset. atapci0: Intel ICH4 UDMA100 controller port 0xbfa0-0xbfaf,0xbfe4-0xbfe7,0xbfe8-0xbfef,0xbff4-0xbff7,0xbff8-0xbfff irq 11 at device 31.1 on pci0 -- Antony T Curtis BSc Unix Analyst Programmer http://homepage.ntlworld.com/antony.t.curtis/ signature.asc Description: This is a digitally signed message part
Re: Locks up with CURRENT
On Sat, 2003-10-11 at 18:31, Sam Leffler wrote: On Saturday 11 October 2003 03:20 am, Antony T Curtis wrote: On Sat, 2003-10-11 at 10:36, Antony T Curtis wrote: Hi, I cvsuped at about 10/10/03 11PM GMT and rebuilt world and kernel. It locks up after displaying: GEOM: create disk ad0 dp=0xc456d370 ad0: 28615MB TOSHIBA MK3021GAS [58140/16/63] at ata0-master UDMA100 ata1: resetting devices .. done System is a Toshiba Satellite 2455 notebook. Removing the CDRW drive allowed it to boot I suspect this is the same problem I've encountered with a Toshiba DVD/CDRW drive on a ServerWorks CSB5 controller. The following change re-enables some code to workaround a missed interrupt and allows my system to boot:: It used to work fine on a kernel cvsupped at around 2 weeks ago. If I reinsert the CDRW drive after it boots up and use atacontrol, it probes and detects the drive correctly. I'll have a look at what has been committed between my cvsups. -- Antony T Curtis BSc Unix Analyst Programmer http://homepage.ntlworld.com/antony.t.curtis/ signature.asc Description: This is a digitally signed message part
UMASS: fatal trap while unplugging floppy drive
Hi I cvsupped this morning and rebuilt world and kernel... When I unplug the USB floppy drive, I get the following umass0: at uhub1 port 1 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry GEOM: destroy disk da0 dp=0xc40b6450 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x8:0xc05fc8b7 stack pointer = 0x10:0xd7151b68 frame pointer = 0x10:0xd7151b70 code segment= base 0x0, limit 0xf , type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 29 (usb1) kernel: type 12 trap, code=0 Stopped at cam_periph_invalidate_0xc: testb $0x8,0x2c(%bx) db trace cam_periph_invalidate(0,c06205b5,0,,) at cam_periph_invalidate+0xc targbhasync(0,40,d7151c1c,0,0) at targbhasync_0xdd xpt_async_bcast(c150de70,40,d7151c1c,0,0) at xpt_async_bcast+0x3c xpt_bus_deregister(0,d7151c4c,c44390a8,d7151c5c,c44a9d7f) at xpt_bus_deregister+0x6e umass_cam_detach_sim(c445,c44390a8,c442b200,c442b200,d7151cb0) at umass_cam_detach_sim+0x21 umass_detach(c442b200,c44390a8,c02ff818,c442b200,0) at umass_detach+0x31 device_detach(c3fde8b0,c3fdec00,11,186,c018505b) at device_detach+0x6e uhub_explore(c3fde980,c3fcdd00,d7151d18,c04046d7,c3fcdd00) at uhub_explore+0x17c usb_discover(c3fcdd00,0,5c,c0416ce8,1770) at usb_discover+0x36 usb_event_thread(c3fcdd00,d7151d48,c02c47bb,314,c3fcdd00) at usb_event_thread+0x62 fork_exit() at fork_exit+0xaf -- Antony T Curtis BSc Unix Analyst Programmer http://homepage.ntlworld.com/antony.t.curtis/ signature.asc Description: This is a digitally signed message part
Re: UMASS: fatal trap while unplugging floppy drive
On Sun, 2003-09-28 at 11:48, John-Mark Gurney wrote: Antony T Curtis wrote this message on Sun, Sep 28, 2003 at 11:34 +0100: I cvsupped this morning and rebuilt world and kernel... When I unplug the USB floppy drive, I get the following Did you have the filesystem mounted? Right now USB is not at all safe for hot plugging. If the recent move to GEOM, it may make unplugging devices even more dangerous. You might try ejecting the media through camcontrol before unplugging the drive. (or even physically ejecting it) The filesystem was not mounted - I used mtools to examine the disk. Plugging in seemed to work fine. I just cannot unplug. patches welcome! :) I'll probably take a peek... -- Antony T Curtis BSc Unix Analyst Programmer http://homepage.ntlworld.com/antony.t.curtis/ signature.asc Description: This is a digitally signed message part
Re: ACPI problems on 5.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks! I have it working nicely now - without any problems. I decompiled, fixed and compiled... problem sorted :) On Wednesday 18 June 2003 8:58 am, Sid Carter wrote: On Tue, Jun 17, 2003 at 04:21:41PM +0100, Antony T Curtis wrote: On a Compaq Armada V300 notebook, if I load the acpi module, boot fails after the kernel prints about half a dozen acpi_bus_number: can't get _ADR, fails to detect any of the hardware and panics because of failure to mount root. With the acpi module disabled, the machine is able to boot up. This same machine used to be able to run 5.0-CURRENT with ACPI enabled and I think the ACPICA merge at around May 2003 could be responsible. Hi, Was able to get ACPI working with FreeBSD on my Compaq Evo N800c. I have put up the stuff at my site here - http://khader.net/archives/p/319/c/1#comments Of course, now, acpi_thermal seems to be giving me problems, as it crashes every 5 minutes. Will see if I can get a trace and post the same here. Regards Sid - -- Antony T Curtis BSc Unix Analyst Programmer http://homepage.ntlworld.com/antony.t.curtis/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+8Sq4ql7dp2cddmIRAjtwAJ9zAEI1jC5m7hvLjeHw7N78i1Uf5ACfW9Tf 0wkliqBvDlGpuf9Dc4s/eMo= =E2VV -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI problems on 5.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On a Compaq Armada V300 notebook, if I load the acpi module, boot fails after the kernel prints about half a dozen acpi_bus_number: can't get _ADR, fails to detect any of the hardware and panics because of failure to mount root. With the acpi module disabled, the machine is able to boot up. This same machine used to be able to run 5.0-CURRENT with ACPI enabled and I think the ACPICA merge at around May 2003 could be responsible. Should I try to get a old copy of the acpica parts or does 5.1 depend on new stuff in it? I am thinking of getting src/sys/dev/acpica and src/sys/contrib/dev/acpica from around 1 April 2003 - -- Antony T Curtis BSc Unix Analyst Programmer http://homepage.ntlworld.com/antony.t.curtis/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+7zIGql7dp2cddmIRAkXzAKDJqDoXikYCVPmUxaTaM3IVi43KBACgqNie uzODS8XCBODHy8ZRwOVnIDg= =y3on -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Compaq and 5.1-RELEASE
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm trying to install 5.1-R onto a Compaq Amarda V300 series laptop. If I allow ACPI to be loaded, it hangs pretty quick right after trying to mount the memory disk. However, in safe mode, it works until during the unpacking/installing, I get a Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1c fault code = supervisor write, page not present instruction pointer = 0x8:0xc02fb3c5 stack pointer = 0x10:0xcae09898 frame pointer = 0x10:0xcae098ac code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 36 (bufdaemon) trap number = 12 panic: page fault This is 100% reproducable. - -- ANTONY T CURTIS Tel: +44 (1635) 36222 Abacus Polar Holdings Ltd Fax: +44 (1635) 38670 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+5t6aA98IbJ8osCYRAmAPAJ9hg6JZ0/kaI/edPptkWiviqxSiMQCgzVsE by5tCEa54Tyh7EhvZOzArLI= =3mUV -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
