Re: mdconfig - need some help

* Christoph P. Kukulies <kuku <at> kukulies.org> [20041031 22:38]:
> # fsck /dev/md2
> fsck: Could not determine filesystem type

I've seen this if /dev/md2 is not in /etc/fstab

> # fsck -t ffs /dev/md2
> ** /dev/md2
> Cannot find file system superblock
> ioctl (GCINFO): Inappropriate ioctl for device
> fsck_ffs: /dev/md2: can't read disk label

Apparently, fsck needs a disklabel. 

I /again/ suggest using src/tools/tools/recoverdisk and try to get as
much as possible from your disk; let it run a couple times to diferent
files. Start from there again.

good luck
--

-- 
pica
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

Re: EHCI Kernel Panic w/ 5.2.1-RELEASE Kernel

My kernel panic seems to come from the usb port actually having a device
in the port, at boot.  When I do not have a device in the port, bootup
continues, however, my usb ports are not usable.  This is my dmesg
output.

> dmesg|grep usb
usb0: <Intel 82801DB (ICH4) USB controller USB-A> on uhci0
usb0: USB revision 1.0
usb1: <Intel 82801DB (ICH4) USB controller USB-B> on uhci1
usb1: USB revision 1.0
usb2: <Intel 82801DB (ICH4) USB controller USB-C> on uhci2
usb2: USB revision 1.0
ehci_pci_attach: companion usb0
ehci_pci_attach: companion usb1
ehci_pci_attach: companion usb2
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
usb3: unrecoverable error, controller halted
usb3: blocking intrs 0x10
usb3: port reset timeout
>

Any ideas?  I am not getting mail from the questions forum, yet, so I
just thought that I would post here, just in case someone has a solution
--

-- 
Respectfully,

M.G.W.

Re: EHCI Kernel Panic w/ 5.2.1-RELEASE Kernel

My kernel panic seems to come from the usb port actually having a device
in the port, at boot.  When I do not have a device in the port, bootup
continues, however, my usb ports are not usable.  This is my dmesg
output.

> dmesg|grep usb
usb0: <Intel 82801DB (ICH4) USB controller USB-A> on uhci0
usb0: USB revision 1.0
usb1: <Intel 82801DB (ICH4) USB controller USB-B> on uhci1
usb1: USB revision 1.0
usb2: <Intel 82801DB (ICH4) USB controller USB-C> on uhci2
usb2: USB revision 1.0
ehci_pci_attach: companion usb0
ehci_pci_attach: companion usb1
ehci_pci_attach: companion usb2
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
usb3: unrecoverable error, controller halted
usb3: blocking intrs 0x10
usb3: port reset timeout
>

Any ideas?  I am not getting mail from the questions forum, yet, so I
just thought that I would post here, just in case someone has a solution
--

-- 
Respectfully,

M.G.W.

Re: EHCI Kernel Panic w/ 5.2.1-RELEASE Kernel

Martes Wigglesworth wrote:
> My kernel panic seems to come from the usb port actually having a device
> in the port, at boot.  When I do not have a device in the port, bootup
> continues, however, my usb ports are not usable.  This is my dmesg
> output.

I have the same problem with a SeverWorks P3 machine and a 7in1 USB 
cardreader. It panics at the end of kernel init if the cardreader is 
plugged into the machine. This machine does not have EHCI controller or 
USB 2.0

I don't know if this considered a showstopper for 5.3R but it can be 
very confusing if you don't know what is causing the panic! Not a good 
first FreeBSD experience!

	/Martin
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

Re: EHCI Kernel Panic w/ 5.2.1-RELEASE Kernel

Martin Nilsson wrote:

> Martes Wigglesworth wrote:
>
>> My kernel panic seems to come from the usb port actually having a device
>> in the port, at boot.  When I do not have a device in the port, bootup
>> continues, however, my usb ports are not usable.  This is my dmesg
>> output.
>
>
> I have the same problem with a SeverWorks P3 machine and a 7in1 USB 
> cardreader. It panics at the end of kernel init if the cardreader is 
> plugged into the machine. This machine does not have EHCI controller 
> or USB 2.0
>
> I don't know if this considered a showstopper for 5.3R but it can be 
> very confusing if you don't know what is causing the panic! Not a good 
> first FreeBSD experience!

I don't think this constitutes a show stopper. A show stopper would be 
if a bug in sysinstall caused it to zero all your harddrives regardless 
of your desires.

--

-- 
Ryan Sommers
ryans <at> gamersimpact.com

_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers

Re: EHCI Kernel Panic w/ 5.2.1-RELEASE Kernel

On Monday 01 November 2004 16:09, Martes Wigglesworth wrote:
> My kernel panic seems to come from the usb port actually having a device
> in the port, at boot.  When I do not have a device in the port, bootup
> continues, however, my usb ports are not usable.  This is my dmesg
> output.
>
> > dmesg|grep usb
>
> usb0: <Intel 82801DB (ICH4) USB controller USB-A> on uhci0
> usb0: USB revision 1.0
> usb1: <Intel 82801DB (ICH4) USB controller USB-B> on uhci1
> usb1: USB revision 1.0
> usb2: <Intel 82801DB (ICH4) USB controller USB-C> on uhci2
> usb2: USB revision 1.0
Over a week ago I discovered a bug in the UHCI driver that causes problems 
when devices are plugged in during boot. I filed a PR with a patch that has 
been taken into the UHCI driver in -CURRENT :
http://www.freebsd.org/cgi/query-pr.cgi?pr=73000

Can you try the patch that's at the end of the PR on your system? (It should 
patch without a problem on 5.2.1-RELEASE).
I'm not sure if it fixes your problem since your problem seems to be 
EHCI-related, but you never know.

Good luck,
Daan

_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers

pkg_add conflicts

Can someone tell me, when was the  <at> conflicts command added to the 
package system?  I keep trying to install things on my 4.9-RELEASE box
and getting complaints from pkg_add about this command.

-Rob D.
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

serial ATA support?

Do I understand right (after looking into sources) that 4-STABLE has no 
support for serial ATA devices??

regards

_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

Re: serial ATA support?

Yury Tarasievich wrote:
> Do I understand right (after looking into sources) that 4-STABLE has no 
> support for serial ATA devices??

Almost none, it works with a few controllers that looks like stock ATA 
ones (HPT fx).
Anyhow you want 5.3 to get real SATA support..

--

-- 

-Søren

_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

Re: serial ATA support?

However if you're stuck in that "I need something now, and 5.3 isn't it" 
space, you can look at SATA drives and a hardware raid controller from 
3Ware or Adaptec...

Charles

On Tue, 2 Nov 2004, [ISO-8859-1] Søren Schmidt wrote:

> Yury Tarasievich wrote:
>> Do I understand right (after looking into sources) that 4-STABLE has no 
>> support for serial ATA devices??
>
> Almost none, it works with a few controllers that looks like stock ATA ones 
> (HPT fx).
> Anyhow you want 5.3 to get real SATA support..
>
> -- 
>
> -Søren
>
>
> _______________________________________________
> freebsd-hackers <at> freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"
>

_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers