Hi.
Unfortunately I have never seen that, but I'll try to look harder. Could
you please tell a bit about your controllers/devices? What triggered the
issue?
If you still have the full dumps, could you check values of ccb_h,
ccb_h->cbfcnp, ccb_h->path and ccb_h->path->periph for the "deadcode
After updating to r256624, the system is very unresponsive,
and really unusable - any command (ps, df, top, ls, etc.)
might take up to 1 min to return. However, I could not get
it to panic.
So I reverted back to r255488.
This time I managed to obtain a textdump:
http://www.freebsd.org/cgi/query-p
This time alllocks has lots of info.
I updated the PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007
Thanks
Anton
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
Hello,
I have an 10-CURRENT r255948 i386 which is booted from an USB stick;
no disk or SSD is involved; it boots fine and works fine mostly;
sometimes right after boot, when I plug-in another USB device
(a HUAWEI UMTS stick) the system reports:
ugen4.4 at usbus4
(da0:umass-sim0:0:0:0) WRITE(1
TB --- 2013-10-23 10:52:57 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2013-10-23 10:52:57 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
>
> ... and the verdict is in. Building src w/o iconv, then re-installing
> converters/libiconv and rebuilding the ports fixes at least
> newsbeuter, I'll now let multimedia/xbmc (and requirements) rebuild
> over night and then prepare a patch to allow -CURRENT + libiconv for
> those people that
On 10/23/2013 1:59 AM, Alexander Motin wrote:
> Hi.
>
> Unfortunately I have never seen that, but I'll try to look harder. Could
> you please tell a bit about your controllers/devices? What triggered the
> issue?
(Sorry for confusing pastes in email, bad client)
Not sure what was done, I was jus
Alexey Dokuchaev wrote, On 10/23/2013 06:26:
panic: softdep_deallocate_dependencies: unrecovered I/O error
I've seen similar panics relatively often in the last few months, but I deemed
them to be the cause of worn IDE cables and old (>10 year old) hard drives.
In fact, I have a core dump (wh
George Mitchell wrote, On 10/23/2013 03:22:
On 10/22/13 20:55, Mateusz Guzik wrote:
On Tue, Oct 22, 2013 at 07:49:21PM -0500, Saul A. Peebsen wrote:
error: 'MALLOC_PRODUCTION' macro redefined [-Werror] #define
MALLOC_PRODUCTION ^ :6:9: note: previous definition is
here #define MALLOC_PRODUCTION
TB --- 2013-10-23 11:08:32 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2013-10-23 11:08:32 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
Hi!
On 23 October 2013 02:18, Anton Shterenlikht wrote:
> After updating to r256624, the system is very unresponsive,
> and really unusable - any command (ps, df, top, ls, etc.)
> might take up to 1 min to return. However, I could not get
> it to panic.
>
> So I reverted back to r255488.
> This
On Wed, Oct 23, 2013 at 2:49 PM, wrote:
> Alexey Dokuchaev wrote, On 10/23/2013 06:26:
>
>> panic: softdep_deallocate_dependencies: unrecovered I/O error
>
>
> I've seen similar panics relatively often in the last few months, but I
> deemed them to be the cause of worn IDE cables and old (>10 yea
On 23.10.2013 14:22, Bryan Drewery wrote:
On 10/23/2013 1:59 AM, Alexander Motin wrote:
Unfortunately I have never seen that, but I'll try to look harder. Could
you please tell a bit about your controllers/devices? What triggered the
issue?
(Sorry for confusing pastes in email, bad client)
No
I just installed 10.0-BETA1 using the [very cool] new automatic ZFS
option. I noticed that /var/empty is not mounted read-only. I suspect
it could be. I made it so, and sshd still seemed to work.
Eric
___
freebsd-current@freebsd.org mailing list
http:
>From adrian.ch...@gmail.com Wed Oct 23 14:22:00 2013
>On 23 October 2013 02:18, Anton Shterenlikht wrote:
>
>> After updating to r256624, the system is very unresponsive,
>> and really unusable - any command (ps, df, top, ls, etc.)
>> might take up to 1 min to return. However, I could not get
>>
On Wed, Oct 23, 2013 at 4:25 PM, Eric van Gyzen wrote:
> I just installed 10.0-BETA1 using the [very cool] new automatic ZFS
> option. I noticed that /var/empty is not mounted read-only. I suspect
> it could be. I made it so, and sshd still seemed to work.
>
> Eric
I don't think there's a stan
On Wed, Oct 23, 2013 at 4:29 PM, Kimmo Paasiala wrote:
> On Wed, Oct 23, 2013 at 4:25 PM, Eric van Gyzen wrote:
>> I just installed 10.0-BETA1 using the [very cool] new automatic ZFS
>> option. I noticed that /var/empty is not mounted read-only. I suspect
>> it could be. I made it so, and sshd
On 10/23/2013 08:30, Kimmo Paasiala wrote:
> On Wed, Oct 23, 2013 at 4:29 PM, Kimmo Paasiala wrote:
>> On Wed, Oct 23, 2013 at 4:25 PM, Eric van Gyzen wrote:
>>> I just installed 10.0-BETA1 using the [very cool] new automatic ZFS
>>> option. I noticed that /var/empty is not mounted read-only. I
On Monday, October 21, 2013 6:29:24 pm Adrian Chadd wrote:
> The NDISulator is a crutch from a time when there wasn't _any_ real
> alternative.
>
> There are plenty of alternatives now. What's lacking is desire and
> person-power. But the datasheets are there, or the vendor code has been
> release
On Wednesday, October 23, 2013 5:27:10 am Anton Shterenlikht wrote:
> This time alllocks has lots of info.
>
> I updated the PR:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007
Hmm, unfortunately it seems like all the stack traces did not work. There are
lots of threads blocked on VM-r
On Monday, October 21, 2013 8:59:49 am Vitalij Satanivskij wrote:
> Hello.
>
> Have 10.0-BETA1 #7 r256765 whith terible load's "load averages: 23.31,
> 30.53, 31"
>
> wich degraded more and more with time.
>
> Kernel compilied with dtrace support and using script called hotkernel from
> DTr
2013/10/23 Sergio de Almeida Lenzi :
> ... and the verdict is in. Building src w/o iconv, then re-installing
> converters/libiconv and rebuilding the ports fixes at least
> newsbeuter, I'll now let multimedia/xbmc (and requirements) rebuild
> over night and then prepare a patch to allow -CURRENT +
On 2013-10-23 09:38, Eric van Gyzen wrote:
> On 10/23/2013 08:30, Kimmo Paasiala wrote:
>> On Wed, Oct 23, 2013 at 4:29 PM, Kimmo Paasiala wrote:
>>> On Wed, Oct 23, 2013 at 4:25 PM, Eric van Gyzen wrote:
I just installed 10.0-BETA1 using the [very cool] new automatic ZFS
option. I not
Hi Hiroki & current@
Hiroki Sato wrote:
> "Julian H. Stacey" wrote
> jh> Regresssion in 10.0-BETA1, mdconfig -l -v return code changed from 0
> jh> to 255. OK, its not specfied in manual, but has changed.
> jh> A test script I was using caught it:
> jh> http://www.berklix.com/~jhs/bin/sh/mdcon
On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd wrote:
> If there are drivers that people absolutely need fixed then they should
> stand up and say "hey, I really would like X to work better!" and then
> follow it up with some encouraging incentives. Right now the NDISulator
> lets people work _arou
On 2013-10-23 13:35, Eitan Adler wrote:
> On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd wrote:
>> If there are drivers that people absolutely need fixed then they should
>> stand up and say "hey, I really would like X to work better!" and then
>> follow it up with some encouraging incentives. Righ
On 23 October 2013 10:40, Allan Jude wrote:
> I think the point Adrian is trying to make, is that the NDISulator needs
> a maintainer, and rather than someone working on that hack, that person
> should spend their time on native drivers.
>
It's partially that.
It's also that a lot of the stuff
>From j...@freebsd.org Wed Oct 23 16:54:12 2013
>
>On Wednesday, October 23, 2013 5:27:10 am Anton Shterenlikht wrote:
>> This time alllocks has lots of info.
>>
>> I updated the PR:
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/183007
>
>Hmm, unfortunately it seems like all the stack traces
On 10/23/13 7:23 AM, John Baldwin wrote:
On Monday, October 21, 2013 6:29:24 pm Adrian Chadd wrote:
The NDISulator is a crutch from a time when there wasn't _any_ real
alternative.
There are plenty of alternatives now. What's lacking is desire and
person-power. But the datasheets are there, or
On 23 October 2013 11:09, Alfred Perlstein wrote:
> Eh, having taken a stab at porting the bwl blob already, I would strongly
>> oppose removing NDIS. If you do that I will just stop using my netbook
>> with a Broadcom part altogether as I wouldn't be able to use it to try to
>> test bwl change
On 10/23/13 11:11 AM, Adrian Chadd wrote:
On 23 October 2013 11:09, Alfred Perlstein wrote:
Eh, having taken a stab at porting the bwl blob already, I would strongly
oppose removing NDIS. If you do that I will just stop using my netbook
with a Broadcom part altogether as I wouldn't be able
Because the Linux stuff is mostly very GPL.
Adrian
On Oct 23, 2013 2:15 PM, "Alfred Perlstein" wrote:
> On 10/23/13 11:11 AM, Adrian Chadd wrote:
>
>> On 23 October 2013 11:09, Alfred Perlstein wrote:
>>
>>
>> Eh, having taken a stab at porting the bwl blob already, I would strongly
>>>
o
On Wednesday, October 23, 2013 2:11:29 pm Adrian Chadd wrote:
> On 23 October 2013 11:09, Alfred Perlstein wrote:
>
>
> > Eh, having taken a stab at porting the bwl blob already, I would strongly
> >> oppose removing NDIS. If you do that I will just stop using my netbook
> >> with a Broadcom pa
And the link momentum is strong now. There's driver source.
Adrian
On Oct 23, 2013 2:41 PM, "John Baldwin" wrote:
> On Wednesday, October 23, 2013 2:11:29 pm Adrian Chadd wrote:
> > On 23 October 2013 11:09, Alfred Perlstein wrote:
> >
> >
> > > Eh, having taken a stab at porting the bwl blob a
On Wednesday, October 23, 2013 1:56:01 pm Anton Shterenlikht wrote:
> >From j...@freebsd.org Wed Oct 23 16:54:12 2013
> >
> >On Wednesday, October 23, 2013 5:27:10 am Anton Shterenlikht wrote:
> >> This time alllocks has lots of info.
> >>
> >> I updated the PR:
> >> http://www.freebsd.org/cgi/que
TB --- 2013-10-23 16:30:19 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2013-10-23 16:30:19 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-10-23 16:30:19 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2013-10-23 16:30:19 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
TB --- 2013-10-23 19:40:52 - tinderbox 2.20 running on freebsd-current.sentex.ca
TB --- 2013-10-23 19:40:52 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013
Adrian Chadd wrote this message on Wed, Oct 23, 2013 at 11:11 -0700:
> On 23 October 2013 11:09, Alfred Perlstein wrote:
>
> > Eh, having taken a stab at porting the bwl blob already, I would strongly
> >> oppose removing NDIS. If you do that I will just stop using my netbook
> >> with a Broadco
> > On 23 October 2013 13:10, claudiu vasadi wrote:
> > Hi,
> > Still getting the "Cannot reset interface wlan0 - exit status 1" in
> > wifimgr but no crash yet. Will keep trying :D
> I have no idea about that. It's likely there's some net80211/iwn bug(s) but
> I don't use wifi
Hi,
The later driver model isn't supported by ndisulator. We'd have to
implement all the newer NDIS stuff for wifi and ethernet.
In the later NDIS layer the Microsoft Wireless Services implement a bunch
of stuff that used to be up to the driver. Ie, the driver just exposed an
ethernet "device" wi
On 23/10/2013 18:35, Eitan Adler wrote:
> On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd wrote:
>> If there are drivers that people absolutely need fixed then they should
>> stand up and say "hey, I really would like X to work better!" and then
>> follow it up with some encouraging incentives. Righ
On 23 October 2013 15:31, Vincent Hoffman wrote:
> On 23/10/2013 18:35, Eitan Adler wrote:
>
> On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd
> wrote:
>
> If there are drivers that people absolutely need fixed then they should
> stand up and say "hey, I really would like X to work better!" an
On Wed, Oct 23, 2013, at 19:11, Adrian Chadd wrote:
> On 23 October 2013 15:31, Vincent Hoffman wrote:
>
> > On 23/10/2013 18:35, Eitan Adler wrote:
> >
> > On Mon, Oct 21, 2013 at 6:29 PM, Adrian Chadd
> > wrote:
> >
> > If there are drivers that people absolutely need fixed then they shoul
--- trap 0, rip = 0, rsp = 0xfe2c6b70, rbp = 0 ---
uma_zalloc_arg: zone "16" with the following non-sleepable locks held:
exclusive sleep mutex balloon_lock (balloon_lock) r = 0
(0x816e9c58) locked @ /usr/src/sys/dev/xen/balloon/balloon.c:339
exclusive sleep mutex balloon_mutex (bal
> The later driver model isn't supported by ndisulator. We'd have to
> implement all the newer NDIS stuff for wifi and ethernet.
> In the later NDIS layer the Microsoft Wireless Services implement a bunch
> of stuff that used to be up to the driver. Ie, the driver just exposed an
> ether
Thomas Mueller wrote:
The later driver model isn't supported by ndisulator. We'd have to
implement all the newer NDIS stuff for wifi and ethernet.
In the later NDIS layer the Microsoft Wireless Services implement a bunch
of stuff that used to be up to the driver. Ie, the driver just
47 matches
Mail list logo
