Re: CDROM Unknown Transfer Error crashes system
Lowell Gilbert wrote: Wayne Witzke [EMAIL PROTECTED] writes: I'm a little confused... I thought I had RELENG_5_4. uname -a says: FreeBSD wlaptop 5.4-RELEASE FreeBSD 5.4-RELEASE #1: Thu Oct 6 21:18:29 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WLAPTOP i386 Isn't this RELENG_5_4? It was, but some patches have been applied since the release was made. I was suggesting RELENG_5, not RELENG_5_4; in other words, the branch that will eventually become the 5.5 release. I'll see if I can't figure out how to do this, then. I had no idea that I wasn't running the most current. Lowell Gilbert wrote: Is there anything that I can do to capture more information the next time my computer reboots spontaneously? Try to get a crash dump. There's more information on it in the Handbook. And some related information on panic analysis (if you can get it to that point) in the FAQ. I'll try that, it doens't sound too difficult. Just so I know, if I was going to see a kernel panic message, I'd be seeing one before the computer reboots, right? I thought that was what you were describing in earlier messages. I'm *NOT* getting anything of this form (from the FAQ): Fatal trap 12: page fault while in kernel mode fault virtual address = 0x40 fault code = supervisor read, page not present instruction pointer = 0x8:0xf014a7e5 stack pointer = 0x10:0xf4ed6f24 frame pointer = 0x10:0xf4ed6f28 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 = 80 (mount) interrupt mask = trap number = 12 panic: page fault All I get is the single line error message in the system log: acd0: unknown transfer phase and then the computer drops to a POST and reboots. I see nothing on my screen between the error and the POST. One of the diagnostic steps that the FAQ mentions is to trace the instruction pointer. My assumption was that if the system was going to give me a message like that, I'd see it before the POST, but I wanted to make sure that I didn't need to be looking for that message in a log somewhere, or changing a configuration option somewhere to make the system generate an error message of that form, because I definitely don't see that before the POST. Wayne ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.4 on a Dell D800
Bob Middaugh wrote: On Behalf Of Wayne Witzke Ugo Bellavance wrote: Hi, I tried installing 5.4 on my Dell D800 laptop. After the first boot, my keyboard stopped working. I don't know what to do from now or if it is even worth the effort. Should I try 6.0RC? I have 5.4 installed on a 2 year old Dell D800 laptop and so far everything works perfectly except for my CDROM (which I'm beginning to think is failing anyway). Hi Wayne, can you post your kernel config file, or tell us what devices you're using for sound and the wireless nic? My wireless nic is an Intel 2200BG, I don't know if they're the same for all D800's, mine is only about a year old. Thanks, Bob Well, my wireless nic is a DELL TrueMobile 1300 (it's a rebranded Broadcom card, I think), and the audio is a SigmaTel STAC9750/51 AC97 Codec. At least, that's what dmesg is telling me about my sound card, and since I'm listening to music right now I can only assume it's right. In order to get the audio working, I had to add the following line to /boot/loader.conf: snd_ich_load=YES My wireless nic is an 802.11b/g card, and in order to get it to work, I had to go the Project Evil route. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html That gets the device up and running, but you also have to figure out what your ssid is and set that using ifconfig for ndis0. But, heh, but doing a quick search to find out where to specify ssid in configuration options to make it pick that up automatically on boot, I ran across this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html I get the impression that you might want to try this first. It looks like it might be a bit more specific to your hardware. Hope this helps! Wayne ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CDROM Unknown Transfer Error crashes system
Lowell Gilbert wrote: Don't top-post, please. Wayne Witzke [EMAIL PROTECTED] writes: Lowell Gilbert wrote: Wayne Witzke [EMAIL PROTECTED] writes: I've googled the error, but the information was mostly related to cd burning or errors in different releases from months or years ago. Nothing recent that I could find. Does anybody have any idea what's going on and how I can fix whatever it is? You could talk to the main ATA developer ([EMAIL PROTECTED]), but he will almost certainly want to know what happens with more recent code. Can you try updating your system? Thank you for your reply! Are you talking about upgrading to the 6.0-BETA? Is it a fairly transparent process, or is it going to require a lot of reconfiguring and reinstalling? I'm not sure I have time to update if that's the case. I'm working under a deadline at the moment. RELENG_5 would be an improvement. It's not necessary, but developers find it much easier to debug recent code than older versions. I'm a little confused... I thought I had RELENG_5_4. uname -a says: FreeBSD wlaptop 5.4-RELEASE FreeBSD 5.4-RELEASE #1: Thu Oct 6 21:18:29 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WLAPTOP i386 Isn't this RELENG_5_4? Is there anything that I can do to capture more information the next time my computer reboots spontaneously? Try to get a crash dump. There's more information on it in the Handbook. And some related information on panic analysis (if you can get it to that point) in the FAQ. I'll try that, it doens't sound too difficult. Just so I know, if I was going to see a kernel panic message, I'd be seeing one before the computer reboots, right? Thank you again! Wayne ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.4 on a Dell D800
Ugo Bellavance wrote: Hi, I tried installing 5.4 on my Dell D800 laptop. After the first boot, my keyboard stopped working. I don't know what to do from now or if it is even worth the effort. Should I try 6.0RC? Regards, I have 5.4 installed on a 2 year old Dell D800 laptop and so far everything works perfectly except for my CDROM (which I'm beginning to think is failing anyway). You might want to check the boot messages and see what keyboard drivers it's loading, or connecting an external keyboard and seeing if that works. Wayne ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CDROM Unknown Transfer Error crashes system
Thank you for your reply! Are you talking about upgrading to the 6.0-BETA? Is it a fairly transparent process, or is it going to require a lot of reconfiguring and reinstalling? I'm not sure I have time to update if that's the case. I'm working under a deadline at the moment. Is there anything that I can do to capture more information the next time my computer reboots spontaneously? Wayne Lowell Gilbert wrote: Wayne Witzke [EMAIL PROTECTED] writes: I've googled the error, but the information was mostly related to cd burning or errors in different releases from months or years ago. Nothing recent that I could find. Does anybody have any idea what's going on and how I can fix whatever it is? You could talk to the main ATA developer ([EMAIL PROTECTED]), but he will almost certainly want to know what happens with more recent code. Can you try updating your system? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CDROM Unknown transfer [phase reboots] system
Dmitry Mityugov wrote: On 10/9/05, Wayne Witzke [EMAIL PROTECTED] wrote: Hello everybody, I've just installed FreeBSD on my laptop (decided I wanted a more developer-friendly computer). Aside from what appear to be the standard newbie problems, every thing's gone remarkably well, except for this: I have a CD-RW/DVD-ROM drive on my laptop. As a CDROM it had been working perfectly well since the initial install about a week and a half ago. It read CDs and DVDs without incident, and did so for hours and hours (which it was forced to do because I've been listening to music pretty much non-stop since I installed the system). The burner did not work, but after the grueling process of opening up the FreeBSD handbook and actually reading how to make it possible to burn CDs, that started working as well. That is, I recompiled the kernel with the atapicam module, changed permissions and set up links in the devfs.conf file in /etc, and set the suid on cdrecord and cdrdao. Worked like a charm. Burned my first CD, and it was beautiful. Then I think I went home. Yesterday, while not burning any CDs at all, just listening to music using kscd while I wrote perl script, my computer suddenly reboots. ... This's the last day I am reading these archives. I believe you'll have to find a better OS that suits your needs. -- Dmitry Mityugov, St. Petersburg, Russia I ignore all messages with confidentiality statements We live less by imagination than despite it - Rockwell Kent, N by E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Mr. Mityugov, I am certainly sorry if I've offended you in some way. It seemed to me that I asked a perfectly valid question. I want to know what caused the unknown transfer phase on my CDROM and how to prevent it from happening again. I certainly didn't expect that would cause such anger that it would warrant a nasty response. As for whether FreeBSD suits my needs, it most certainly does. I've been an administrator of Unix-like systems for about 7 years, starting with Linux systems back in '97 and working my way up to IRIX a few years ago. I've had FreeBSD installed and working on home systems in the past, but it's been a while. Now, my work laptop had crashed (hard disk death), and I was tired having to struggle to get Windows to do what I wanted it to do and to keep it up and running more then a month at a time. Took 6 months to make Windows work the way I wanted it to, when it only took about a week to get FreeBSD working. In my experience, Unix-like systems have *always* been easier to develop on, have always been more stable, and are always faster. The fact that FreeBSD combines these properties with the ease of the ports collection plus what I thought was a community of involved people willing to help made it the obvious choice. If by suits your needs you meant your need to listen to music, I believe that's beside the point. The fact that acd0 had an unknown transfer phase is troubling regardless of the task it was performing at the time, especially considering that it was a kernel message. I will almost certainly need to be able to read from my CDROM drive at some point in the future for data transfer purposes, and a reboot during such a read would at best cause the data transfer to fail, and at worst it could corrupt data on the hard drive in an unrecoverable way. I also apologize that my subject line wasn't 100% accurate. It should have read CDROM Unknown transfer *phase reboots* system. The word error in the subject line was incorrect, and the assertion that it caused a crash was just an assumption on my part. I was unable to find a memory dump or any information that should have led me to believe it was definitely a crash (and I still can't). Also, it's an assumption on my part that the unknown transfer phase rebooted the system, but that was the last entry in the log file and I though (and still think) that it's the best indicator for what might have gone wrong. And the word reboot may be incorrect as well. The system didn't go through the shutdown process at all, it simply dropped to a POST. If your objection was to the length of the description in my original message, I though it would be prudent to provide as much detail as I could about the steps I had gone through with my CDRW/DVDROM drive so that those who might be interested in helping would have as much detail as I could provide. I apologize if what I was hoping to be a playful tone offended you, but since I tend to enjoy working on operating systems like FreeBSD I tend to write in a manner that expresses that feeling. I also apologize that part of my message, and my actual question, was at the bottom of the message after the dmesg output. That format was, I realize, not conducive
CDROM Unknown Transfer Error crashes system
Hello everybody, I've just installed FreeBSD on my laptop (decided I wanted a more developer-friendly computer). Aside from what appear to be the standard newbie problems, every thing's gone remarkably well, except for this: I have a CD-RW/DVD-ROM drive on my laptop. As a CDROM it had been working perfectly well since the initial install about a week and a half ago. It read CDs and DVDs without incident, and did so for hours and hours (which it was forced to do because I've been listening to music pretty much non-stop since I installed the system). The burner did not work, but after the grueling process of opening up the FreeBSD handbook and actually reading how to make it possible to burn CDs, that started working as well. That is, I recompiled the kernel with the atapicam module, changed permissions and set up links in the devfs.conf file in /etc, and set the suid on cdrecord and cdrdao. Worked like a charm. Burned my first CD, and it was beautiful. Then I think I went home. Yesterday, while not burning any CDs at all, just listening to music using kscd while I wrote perl script, my computer suddenly reboots. Checking /var/log/messages, this is what I see (first log messages after the last root login): Oct 7 09:46:15 xxx kernel: acd0: unknown transfer phase Oct 7 09:50:20 xxx syslogd: kernel boot file is /boot/kernel/kernel Oct 7 09:50:20 xxx kernel: Copyright (c) 1992-2005 The FreeBSD Project. Oct 7 09:50:20 xxx kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989 etc. etc. into the boot process. Here's what dmesg tells me: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RELEASE #1: Thu Oct 6 21:18:29 EDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/XXX Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) M processor 1400MHz (1398.82-MHz 686-class CPU) Origin = GenuineIntel Id = 0x695 Stepping = 5 Features=0xa7e9f9bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE real memory = 536535040 (511 MB) avail memory = 511168512 (487 MB) npx0: math processor on motherboard npx0: INT 16 interface acpi0: DELL CPi R on motherboard Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU (4 Cx states) on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 acpi_acad0: AC Adapter on acpi0 acpi_cmbat0: Control Method Battery on acpi0 acpi_cmbat1: Control Method Battery on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Power Button on acpi0 acpi_button1: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 ACPI link \\_SB_.PCI0.LNKB has invalid initial irq 11, ignoring pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 nvidia0: GeForce4 4200 Go mem 0xf000-0xf3ff,0xfc00-0xfcff irq 11 at device 0.0 on pci1 uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0xbf80-0xbf9f irq 11 at device 29.0 on pci0 usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801DB (ICH4) USB controller USB-B port 0xbf40-0xbf5f irq 11 at device 29.1 on pci0 usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0xbf20-0xbf3f irq 11 at device 29.2 on pci0 usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: EHCI (generic) USB 2.0 controller mem 0xf4fffc00-0xf4ff irq 11 at device 29.7 on pci0 usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: EHCI (generic) USB 2.0 controller on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered uhub4: Dell Port Replicator, class 9/0, rev 2.00/10.00, addr 2 uhub4: multiple transaction translators uhub4: 4 ports with 4 removable, self powered uhub5: Lite-On Technology USB 1.1 2port downstream low power hub, class 9/0, rev 1.10/1.00, addr 3 uhub5: 3 ports with 2 removable, bus powered ukbd0: Lite-On Technology USB Productivity Option Keyboard( has the hub in # 1 ), rev 1.10/1.00, addr 4, iclass 3/1 kbd1 at ukbd0 uhid0: Lite-On Technology USB Productivity Option Keyboard( has the hub in # 1 ), rev 1.10/1.00, addr 4, iclass 3/1 ums0: Microsoft Basic Optical Mouse, rev 1.10/0.00, addr 5, iclass 3/1 ums0: 3 buttons and Z dir. pcib2: ACPI PCI-PCI
