| From | Subject | Date |
|---|---|---|
| Doug Barton | Re: [RFC] More meaningful information about ENOEXEC for ...
+1 on anything that makes this (and related) error more clear. I know
I've stumbled over it numerous times.
Doug
--
Nothin' ever doesn't change, but nothin' changes much.
-- OK Go
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any ...
| Oct 25, 12:26 pm 2010 |
| Xin LI | [RFC] More meaningful information about ENOEXEC for kldload(8)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
Here is a simple patch that adds more meaning messages when kldload hits
ENOEXEC.
Before patch:
kldload: can't load geom_eli.ko: Exec format error
After patch:
kldload: can't load geom_eli.ko: Exec format error
kldload: Dependendent kernel module cannot be loaded from kern.module_path?
Comments?
Cheers,
- --
Xin LI <delphij@delphij.net> http://www.delphij.net/
FreeBSD - The Power to Serve! Live free or ...
| Oct 25, 12:19 pm 2010 |
| Ivan Voras | Re: [RFC] More meaningful information about ENOEXEC for ...
Yes...
> so why not just keep status quo?
And no :)
I've often encountered the kldload failure and I've always had to look
at the kernel logs to find out the actual reason. There are several
cases where kldload can fail, including recursively - when a module
fails to load as a dependancy of the module the user is trying to load,
for all the reasons a module can fail to load.
I think something should be done to make the message more descriptive
but statically changing the error ...
| Oct 25, 1:33 pm 2010 |
| Paul B Mahol | Re: [RFC] More meaningful information about ENOEXEC for ...
What about modules built for different __FreeBSD_version ?
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 25, 1:24 pm 2010 |
| Doug Barton | Re: [RFC] More meaningful information about ENOEXEC for ...
Thinking about Garrett's response as well, this may be the best way to
go. At this point I'm also not concerned about waiting for an ideal
solution. IMO an incremental change here would be most welcome.
Doug
--
Nothin' ever doesn't change, but nothin' changes much.
-- OK Go
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
_______________________________________________
freebsd-current@freebsd.org ...
| Oct 25, 2:15 pm 2010 |
| Garrett Cooper | Re: [RFC] More meaningful information about ENOEXEC for ...
Typo in the error message aside...
Technically you can dig the source of these errors from
/var/log/messages // syslog though, so why not just keep status quo?
Making errors more intuitive is nice, but providing more misleading
errors are worse than providing less misleading errors; this kind of
error message falls in the more misleading message category, as
ENOEXEC means:
[ENOEXEC] The file format of file was unrecognized.
That is open for a lot of interpretation ...
| Oct 25, 1:13 pm 2010 |
| Rene Ladan | Re: Tested wanted: BSD-licensed libgcc replacement, libc ...
[...]
I noticed that the nvidia driver (from ports/x11/nvidia-driver*) needs
to be recompiled after upgrading from HEAD to this branch. If you don't,
it will load, but cause a panic when used by X.
Rene
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 25, 7:05 am 2010 |
| Matthias Apitz | Broadcom BCM4310 USB Controller (Wifi)
Hello,
I have a new laptop Acer Aspire One D250 and pulled out HEAD from SVN
today morning. As far as I can see in sys/dev/bwi and sys/dev/bwn the
above chip is still not supported. I am wrong?
Any other idea how to get Wifi working on this mini laptop?
Thanks in advance
matthias
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <guru@unixarea.de> - w http://www.unixarea.de/
_______________________________________________
freebsd-current@freebsd.org ...
| Oct 25, 1:07 am 2010 |
| Alexander Motin | Re: kern/151608: [ata] FreeBSD doesn't detect Sandforce- ...
I would agree if it was the first case.
I am not saying that ata(4) perfect. ata(4) is a big thing and Marvell
part is definitely not the best part of it. That's why there is several
new drivers: ahci(4), siis(4), mvs(4), which together with ATA_CAM
options should substitute most of it.
--
Alexander Motin
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to ...
| Oct 25, 7:04 am 2010 |
| Thomas E. Spanjaard | Re: kern/151608: [ata] FreeBSD doesn't detect Sandforce- ...
No, I only tried to use ata(4). I tried using mvs(4) now, and that works!
mvs0: <Marvell 88SX6081 SATA controller> port 0x4000-0x40ff mem
0xb0100000-0xb01fffff irq 11 at device 2.0 on pci1
mvs0: Gen-II, 8 3Gbps ports, Port Multiplier supported
mvsch0: <Marvell SATA channel> at channel 0 on mvs0
mvsch1: <Marvell SATA channel> at channel 1 on mvs0
mvsch2: <Marvell SATA channel> at channel 2 on mvs0
mvsch3: <Marvell SATA channel> at channel 3 on mvs0
mvsch4: <Marvell SATA channel> at channel 4 ...
| Oct 25, 5:39 am 2010 |
| Alexander Motin | Re: serious issue caused by usb device, stalling almost ...
It is a bit suspicious that problem happens only when device dies during
request. Are you sure that running command was properly aborted when
device got detached? Every running command has own set of references,
denying detach.
--
Alexander Motin
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 24, 11:55 pm 2010 |
| Andriy Gapon | Re: c 213323 breaks Sony Vaio P11Z w/o acpi
Hmm, it looks like you have ACPI and APIC disabled... either in kernel config or
in BIOS?
If yes, can you try to not do it?
--
Andriy Gapon
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Oct 25, 4:03 am 2010 |
| volker | Re: c 213323 breaks Sony Vaio P11Z w/o acpi
Andriy,
the Vaio P11Z does not boot at all with ACPI enabled so it's disabled in
loader.conf. The panic messages are various if I try.
But I haven't disabled APIC anywhere. The kernel configuration is simply
a GENERIC (included) with some different options set. I've uploaded the
kernel config for you at http://people.freebsd.org/~vwe/misc/Vaio_p11z/JUNO
I may try, of course, to compile a plain vanilla GENERIC kernel but
AFAIR INVARIANTS and WITNESS caused more trouble with this device ...
| Oct 25, 4:23 am 2010 |
| volker | Re: c 213323 breaks Sony Vaio P11Z w/o acpi
Dear Andriy,
sorry for the delay.
Sure! Please find it at
hmm, a KASSERT would cause my P11Z to panic in a more controlled way but
in the end I understand your intention.
I'll try to get the cpu topo code into a working condition tomorrow and
will post the results (and a pointer to the new code base).
Thanks a lot,
Volker
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To ...
| Oct 25, 3:35 am 2010 |
| Andriy Gapon | Re: c 213323 breaks Sony Vaio P11Z w/o acpi
I would be interested to look at that problem (or those problems) too.
And now I think that see what the immediate problem is.
In your current configuration there is no away for FreeBSD to determine number of
processors and their IDs, because neither MP Table nor MADT are found.
So essentially it's a uni-processor system (for FreeBSD at least) and we shouldn't
try to probe CPU topology, because it neither make sense nor can be properly.
I will add code to handle this case.
--
Andriy ...
| Oct 25, 5:06 am 2010 |
| previous day | today | next day |
|---|---|---|
| October 24, 2010 | October 25, 2010 | October 26, 2010 |
