On Mon, 15 Mar 2021 at 14:58, Kevin Oberman wrote:
> >
> > It appears that the messages are associated with reading
> > the disk(s), not directly with writing them, where the
> > reads take more than "hz * 20" time units to complete.
> > (I'm looking at main (14) code.) What might contribute
> >
yeah, that we'll have to look into..
-a
On Mon, 12 Nov 2018 at 13:33, tech-lists wrote:
> On Mon, Nov 12, 2018 at 12:32:25PM -0800, Adrian Chadd wrote:
> >If it's showing up like that then it's not an AR9170 device; it's a
> >broadcom firmware device. :(
If it's showing up like that then it's not an AR9170 device; it's a
broadcom firmware device. :(
-a
On Mon, 12 Nov 2018 at 12:08, tech-lists wrote:
> Hi,
>
> context:
> freebsd-12-beta4 on amd64 and freebsd-12 on arm64, I'm trying right now
> with amd64 r340354.
>
> I have a Netgear WNDA3100
hi,
I'm busy and there isn't a specific maintainer!
Bug me in a couple days; we need to figure out how to enable the right
command to enable debugging the firmware messages. Hopefully we can
narrow down which firmware message its erroring out on!
-a
_
It's the same pages, right? Is it just the refcounting locking that's
causing it?
I think the biggest thing here is to figure out how to have pages have
a lifecycle where the refcount can be inc/dec (obviously >1, ie not in
a state where you can dec to 0) via atomics, without grabbing a lock.
That
can you capture a usb transfer dump from usbdump ?
I'd like to see if it's because the usb bluetooth code is trying to
attach and failing, or whether it really is just some broken transfer
/ notification loop.
-a
On 6 April 2017 at 03:16, Dominic Fandrey wrote:
> I have an Interrupt load of 2
hiya,
Install the 'intel-pcm' package, then as root;
kldload cpuctl
pcm.x 1
-adrian
On 26 November 2016 at 10:25, Jakub Lach wrote:
> I've found that the original technology was called Intel Dynamic
> Acceleration,
> though it should be only utilized if not all cores working?
>
> I'm ok with
the acpi cpu frequency module just exposes the frequency lis given to
it by ACPI. If your ACPI table exposes the turbo boost frequency but
doesn't implement it on the backend, FreeBSD doesn't know. We just
obey what we're told. :)
-a
On 25 November 2016 at 20:16, Jakub Lach wrote:
> Hello,
>
>
rge
>
> On 11/03/16 18:48, Adrian Chadd wrote:
>> hi,
>>
>> can you please try freebsd-11.0 ? I fixed a whole bunch of bugs in the
>> AR9380 HAL and it may have improved that device.
>>
>> Thanks!
>>
>>
>> -a
>>
>>
>> O
hi,
can you please try freebsd-11.0 ? I fixed a whole bunch of bugs in the
AR9380 HAL and it may have improved that device.
Thanks!
-a
On 3 November 2016 at 07:09, George Mitchell wrote:
> Originally posted to freebsd-wireless; no solution yet so I thought
> I'd try here. After booting up,
On 25 August 2016 at 12:45, Stefan Wendler wrote:
> Hi,
>
> is this fixed in RC2? I haven't tried it yet but would be nice to know
Hi,
Just so everyone who may be interested/involved can see - I don't have
the spare bandwidth/cycles to try and make wifi + lagg "work", and
personally I still main
Just pop open the crashdump and "print *ifp" in the last stack frame
before trap.
-a
On 11 August 2016 at 16:42, David Wolfskill wrote:
> On Thu, Aug 11, 2016 at 04:37:26PM -0700, Adrian Chadd wrote:
>> Eep. Is this anotehr case where there's a race and ifp is NULL
.. and maybe we should revert or comment out the code until we figure
out what to do about LLADDR checks.
(I see this in the detach path too; same kind of race. Sigh.)
-adrian
On 11 August 2016 at 16:37, Adrian Chadd wrote:
> Eep. Is this anotehr case where there's a race and ifp is
Eep. Is this anotehr case where there's a race and ifp is NULL or the
ll pointer for ifp is NULL or use-after-free'd?
I remember bumping into these here and there because we don't seem to
have a well defined lifecycle for lladdr access. ;(
-adrian
On 10 August 2016 at 12:10, Bryan Drewery wro
Hi,
I think a bunch of the lock order checks with witness get disabled for ZFS ?
Maybe compile up a witness kernel so you can get 'show alllocks' in
ddb. That should help narrow down exactly what's going on.
Thanks!
-a
___
freebsd-stable@freebsd.org
hi,
please bug me in a couple weeks. still moving house, etc.
-a
On 16 February 2016 at 02:30, Slawa Olhovchenkov wrote:
> On Tue, Feb 16, 2016 at 11:23:20AM +0100, Giuseppe Lettieri wrote:
>
>> I am sorry, I did not participate to the implementation of kqueue
>> support and I am not able to
Hm, the runtime going backwards is a bit odd, maybe they fixed that in
-HEAD recently. Other than that, yeah, you'll need a crash dump or at
least some screenshot when it does reboot.
-a
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.
hiya,
how much RAM does the VM have?
Yes, you need to either run dumpon or reboot once you update /etc/rc.conf .
-a
On 5 February 2016 at 13:55, Scott Otis wrote:
> Been trying to get a FreeBSD VM server running on Azure on a "Standard DS"
> size VM (so I have access to SSD storage for Post
.. but if it does, can you enable witness and see what it reports as
lock order violations?
-a
On 4 February 2016 at 10:47, Adrian Chadd wrote:
> I've no time to help with this, I'm sorry :(
>
>
> -a
>
>
> On 4 February 2016 at 05:00, Slawa Olhovchenkov wrote
I've no time to help with this, I'm sorry :(
-a
On 4 February 2016 at 05:00, Slawa Olhovchenkov wrote:
> On Tue, Feb 02, 2016 at 11:44:47PM +0300, Slawa Olhovchenkov wrote:
>
>> On Thu, Oct 22, 2015 at 11:24:53AM -0700, Luigi Rizzo wrote:
>>
>> > On Thu, O
hiya,
+wireless, +andriy
Andriy has been working on adding lots of new things to urtwn and
tidying it up. It's possible he's introduced some regressions. Just
check in on the wireless list and join #freebsd-wireless on efnet to
ask questions.
Hopefully it was fixed a couple days ago with the TX
Hi,
The stable/10 code doesn't have all the fixes I did over the last two
years. Just disable 11n (ifconfig wlan0 -ht) and use that. :-)
Sorry!
-adrian
On 3 November 2015 at 07:19, Alban Hertroys wrote:
>
>> On 26 Oct 2015, at 22:10, Adrian Chadd wrote:
>>
>>
hiya,
you should try -head.
But there's some long standing issues hiding around in the AR9227 code
somewhere where they occasionally go deaf and I never figured out
why... :(
-a
On 26 October 2015 at 13:27, Alban Hertroys wrote:
> At random times my devices suddenly fail to connect to Wifi o
On 22 October 2015 at 11:24, Luigi Rizzo wrote:
> On Thu, Oct 22, 2015 at 11:12 AM, Adrian Chadd wrote:
>> On 22 October 2015 at 09:35, Slawa Olhovchenkov wrote:
>>> On Sun, Oct 18, 2015 at 07:45:52PM -0700, Adrian Chadd wrote:
>>>
>>>> Heh, file a bug
On 22 October 2015 at 09:35, Slawa Olhovchenkov wrote:
> On Sun, Oct 18, 2015 at 07:45:52PM -0700, Adrian Chadd wrote:
>
>> Heh, file a bug with luigi; it should be defined better inside netmap itself.
>
> I am CC: luigi.
>
> Next question: do kevent RX/TX sync?
> In m
Heh, file a bug with luigi; it should be defined better inside netmap itself.
-a
On 18 October 2015 at 14:00, Slawa Olhovchenkov wrote:
> On Sun, Oct 18, 2015 at 01:29:23PM -0700, Adrian Chadd wrote:
>
>> On 18 October 2015 at 11:56, Slawa Olhovchenkov wrote:
>> > I have
On 18 October 2015 at 11:56, Slawa Olhovchenkov wrote:
> I have 82576 in NETMAP mode.
> 802.1q packets received in decapsulated form.
> This is bug or this is normal behavior?
I don't know if it's a bug or not; I don't know if it was ever defined
behaviour.
You should just disable the hardware vl
Hi,
Some hand-waving suggestions:
* if you're running something before 10.2, please disable IXGBE_FDIR
in sys/conf/options and sys/modules/ixgbe/Makefile . It's buggy and it
caused a lot of issues.
* It sounds like some extra latency is happening, so I'd fiddle around
with interrupt settings. By
hi,
you'll have to do some debugging. it looks like it's some kind of odd
race - line 461 is _ieee80211_crypto_delkey(); line 105 is
cipher_detach() and it blows up there.
Try "wlandebug +crypto" during your next boot and let's see what it
logs for the key.
If you can 'print *key' in kgdb on the
hi!
What was that option actually doing? How'd it break things?
-adrian
On 27 July 2015 at 05:02, Andre Meiser wrote:
> Kudos to Konstantin Belousov!
>
> I'm not sure if this list was interested into all this error tracking. So we
> made the error tracking with private mails.
>
> Anyway, i
Hi,
Yes, the USB device suspend/resume thing is a more generic
suspend/resume problem. Warner has some ideas - eg, registering a "is
this a new device?" method; the device driver will check if the device
has changed upon resume and optionally go through a detach/reattach
process. So for USB it cou
accessing hardware isn't free. Locking also isn't free. That's why
there's this mechanism.
-adrian
On 24 July 2015 at 08:58, wrote:
>
> OK.
>
> I read the document and understood it I guess.
> Very interesting, and well engineered.
>
> On x86/i386/amd64, could not all this be replaced by a s
On 15 July 2015 at 14:58, Philip Murray wrote:
>
>> On 13/07/2015, at 11:58 pm, Karl Denninger wrote:
>>
>> Put this on your box and see if the problem goes away :-)
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187594
>>
>
> Is there a concise explanation of why this hasn’t been me
hi,
With that much storage and that many snapshots, I do think you need
more than 96GB of RAM in the box. I'm hoping someone doing active ZFS
work can comment..
I don't think the ZFS code is completely "memory usage" safe. The
"old" Sun suggestions when I started using ZFS was "if your server
pan
.. and in one instance, you had 57gig of RAM allocated just to ZFS
65536 size buffers.
-adrian
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubsc
Ok, so which subset of changes is the culprit?
(sorry, I'm tired.. :( )
-a
On 28 June 2015 at 22:45, Kevin Oberman wrote:
> On Sun, Jun 28, 2015 at 4:54 PM, Kevin Oberman wrote:
>>
>> On Sun, Jun 28, 2015 at 10:38 AM, Joseph Mingrone wrote:
>>>
>>>
Thanks for digging into this!
(two laptops are now running -head from today, all iswell. I'll update
the t400 tomorrow.)
-a
On 28 June 2015 at 16:54, Kevin Oberman wrote:
> On Sun, Jun 28, 2015 at 10:38 AM, Joseph Mingrone wrote:
>>
>> Adrian Chadd writes:
>> >
Hi,
ok. I've updated my x230 to the latest -head and itis okay at suspend/resume.
I can go acquire an x220 (now that they're cheap) to have as another
reference laptop.
I don't run stable/10 on anything, so it may be something odd with
what he MFCed and what's in stable/10.
I'll update the othe
Hi,
please start binary searching.
I'll update my x230 tonight when I get home and see if -head is broken.
-adrian
On 27 June 2015 at 15:48, Kevin Oberman wrote:
> On Sat, Jun 27, 2015 at 3:13 PM, Joseph Mingrone wrote:
>>
>> Adrian Chadd writes:
>> > does
does it always fail now?
-a
On 26 June 2015 at 14:06, Joseph Mingrone wrote:
> This is on a Lenovo X220. Suspend/resume was working until some time
> between late April and last week's STABLE snapshot.
>
> Suspend always seems to work, but there are two issues with resume.
>
> 1) When i915kms
s, it works!
> >
> >
> https://svnweb.freebsd.org/base/head/sys/dev/pci/vga_pci.c?r1=284012&r2=284011&pathrev=284012
> >
> >
> >
> > 2015-06-11 0:38 GMT+08:00 Adrian Chadd :
> >
> > > Hi,
> > >
> > > There was an updat
Hi,
There was an update to freebsd-head a few days ago from hans - it
disabled PCI interrupts for VGA until a driver claims it.
See if that helps?
-a
b
On 10 June 2015 at 05:33, Yanhui Shen wrote:
> Hi,
>
> I noticed the interrupt rate of my FreeBSD system is very high (~35%) after
> upgrade
Frequency control may not be relevant on that platform.
Try installing the intel-pcm package; then
# kldload cpuctl
# pcm.x 1
Then paste some of that in here. Let's see if the CPU is idling some other way.
-adrian
___
freebsd-stable@freebsd.org mail
Hm, no thermal monitoring and no speedstep. Could be dangerous/fun.
What's the output of sysctl dev.cpu.0 ?
-adrian
On 23 May 2015 at 07:40, Kimmo Paasiala wrote:
> On Sat, May 23, 2015 at 5:15 PM, Ian Smith wrote:
>> On Sat, 23 May 2015 14:01:16 +0300, Kimmo Paasiala wrote:
>> > On Sat,
Hi,
The whole point of throttling on modern hardware isn't to get really
low clock rates, it's to deal with being out of thermal envelope.
But, the modern intel cores will do that for you without OS involvement.
So, you don't have to actually use p4tcc and it may actually configure
your hardware
I honestly have no idea, and this is kind of why I didn't want to
commit it to stable/10 without it getting a whole lot more testing.
Does -HEAD also fail to suspend for you?
-a
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailm
Hi,
that GEM idle fail is problematic.
Try backing it out say, 1 month or so? I think that's before the drm
merge from head to stable/10.
-a
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubs
On 21 March 2015 at 08:52, John Baldwin wrote:
> On 3/20/15 8:46 PM, Mike Tancsa wrote:
>> On 3/20/2015 8:15 PM, Konstantin Belousov wrote:
For the purpose of devfs, does it make sense to bump timestamps like
normal filesystems for each read/write operation? Looks like Mac OS X
>>>
.. ipfw showed up?
-a
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 12 March 2015 at 18:19, Kevin Oberman wrote:
> On Thu, Mar 12, 2015 at 12:40 PM, Adrian Chadd wrote:
>>
>> I thought jhb already mfc'ed it?
>>
>>
>> -a
>>
>>
>
> Adrian,
>
> jhb asked that I ask you to MFC. I did so and, since
I thought jhb already mfc'ed it?
-a
On 12 March 2015 at 12:36, Kevin Oberman wrote:
> I have just submitted a PR to MFC the code that will fix brightness
> adjustmant on may laptops with modern Intel GPUs. It has been tested by at
> least two people and I have been using it for at least three
oh, wait a sec. I think some stuff went in that wired some important
processes into memory.
-adrian
On 4 October 2013 06:29, John Marshall wrote:
> On Mon, 30 Sep 2013, 19:55 +1000, John Marshall wrote:
> > > >> > On Fri, 27 Sep 2013, 11:12 +0300, Konstantin Belousov wrote:
> > > >> >> On Fri
There's an LACP knob that ignores doing the LACP hash if the mbuf has a
flowid. Find that knob and set it to 0. Then, retry.
-a
On 3 October 2013 15:24, Rumen Telbizov wrote:
> Jack,
>
> Thanks for the hints.
>
> I checked that the card is inserted into PCIe v3.0 x16 + I get no
> complaints f
Sure, uhm, just remind me to commit it to -HEAD in the next few days. Then
I'll get it backported to stable/9.
Thanks,
-adrian
On 29 September 2013 10:03, Alexey Dokuchaev wrote:
> On Wed, Jul 04, 2012 at 06:51:56PM +0200, Bernhard Schmidt wrote:
> > On Tuesday 19 June 2012 07:28:11 Alexey
On 17 September 2013 00:45, Marko Cupać wrote:
> On Sun, 15 Sep 2013 23:34:45 -0700
> Adrian Chadd wrote:
>
> > Hi,
> >
> > Please try -HEAD or -10. I fixed a number o AR9285 bugs there.
>
> Uh, I did this a few times before, and indeed it fixed some pr
Hi,
Please try -HEAD or -10. I fixed a number o AR9285 bugs there.
Thanks,
-adrian
On 15 September 2013 05:48, Marko Cupać wrote:
> I just had another core dump on 9.2-PRERELEASE #1 r255487 amd64, and I
> think i see a pattern. Every now and then, at least once per day, my
> Atheros AR9285
.. anything happening?
-adrian
On 2 September 2013 07:29, Adrian Chadd wrote:
>
> On 2 September 2013 07:25, Mike Harding wrote:
>
>> It's detailed in the ticket, see
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=181632 and search for
>> 'reverted&#
On 2 September 2013 07:25, Mike Harding wrote:
> It's detailed in the ticket, see
> http://www.freebsd.org/cgi/query-pr.cgi?pr=181632 and search for
> 'reverted'.
>
>
Ok. You and avg@ are digging into it deeper, so I'll leave it be for now.
I'll retest this on my test laptops when I'm back home.
So you tinkered with this - which particular line(s) did you revert back to
get the old behaviour?
-adrian
On 1 September 2013 22:46, Mike Harding wrote:
> Why not put this out to stable and take a survey with more than 2
> members? I am sure that there
> are those who will be delighted, as I
.. well, when is that pointer NULL? It looks like it's supposed to be NULL
for one pair of the two HT CPUs?
Are you taking the whole core into an ACPI idle state if one of two logical
CPUs representing a core is going idle?
-adrian
___
freebsd-stable@
On 1 September 2013 14:35, Andriy Gapon wrote:
> Do you have any evidence that there is anybody else besides Mike who has
> this
> problem?
>
Nope! but we can't assume that users are reporting all the system slowdowns.
And honestly, I've heard enough strange stories on mailing lists and IRC o
On 31 August 2013 23:41, Andriy Gapon wrote:
> >
> > I've tracked this down to a single line, details in
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=181632. Basically, the
> code is
> > now doing a 'sti, hlt' vs. a 'sti' in some code that is only
> supposed to run
> > if idle
On 31 August 2013 10:35, Mike Harding wrote:
> I've tracked this down to a single line, details in
> http://www.freebsd.org/cgi/query-pr.cgi?pr=181632. Basically, the code
> is now doing a 'sti, hlt' vs. a 'sti' in some code that is only supposed to
> run if idle is disabled. Given that 'hlt' i
On 29 August 2013 23:46, Mike Harding wrote:
> I was able to track this down by building kernels against /base/stable/9
> (it took
> -hours!-).
>
Wow, thanks!
> The issue does occur with commit 244616, but does not occur with 244614.
> The
> only difference is a small patch to /usr/src/sys/dev
.. after tinkering in the USB world, i wonder what's wrong with this:
* created a basic markup / description language to encapsulate what PCI/USB
probing requires;
* generated both config files _and_ .c / .h files for drivers to include;
* have the kernel build process do .device_description -> .c
Wow. Uhm, can you downgrade to 9.1 and see if it still happens?
Would you be able to bisect the kernel source and see if you can find where
along stable/9 it happened? That's the fastest way to determine what broke.
Thanks!
-adrian
On 29 August 2013 06:32, Mike Harding wrote:
> I opened a
Hm! Are they dynamically loaded if you insert the cards?
(Ie, has devd been taught about them as appropriate?)
-adrian
On 29 August 2013 02:15, Kimmo Paasiala wrote:
> In reference to this FreeBSD forums post:
>
> http://forums.freebsd.org/showpost.php?p=231135&postcount=4
>
> Would it be a
Hi,
There's bus limits on how much data you can push over a PCI bus. You can
look around online to see what 32/64 bit, 33/66MHz PCI throughput estimates
are.
It changes massively if you use small versus large frames as well.
The last time I tried it i couldn't hit gige on PCI; I only managed to
Hi,
Does -HEAD have this same problem?
If so, we should likely just revert the patch entirely from -HEAD and -9
until it's resolved.
-adrian
On 24 August 2013 23:51, Michael Tratz wrote:
>
> On Aug 15, 2013, at 2:39 PM, Rick Macklem wrote:
>
> > Michael Tratz wrote:
> >>
> >> On Jul 27,
> >
> > "Aug 19 10:53:47 tahoe dhclient[79063]: ioctl(SIOCGIFFLAGS) on
> > wlan0: Operation not permitted"
>
> > On Sun, Aug 18, 2013 at 09:02:41AM -0700, Adrian Chadd wrote:
> > > good to know!
> > >
> > >
> &
A lot of the ath PRs filed by me can be closed. They're reminders that
things needed fixing, which I've done.
A lot of them are for older cards on older machines with odd behaviour due
to PCI/cardbus issues, power save bugs, ACPI hilarity, etc. I've tried to
port over some fixes to address these b
Are you running the AR9285 on -HEAD? If not, upgrade. It should behave
much, much better.
-adrian
On 19 August 2013 00:59, Marko Cupać wrote:
> I am struggling with my AR9285 for more than a year now. Sometimes it
> is better, sometimes worse, but never without disconnections.
>
> I have al
... so, unless you have a million wpi NICs and you can control purchasing
of further hardware from intel, I doubt they're going to care about a very
old, EOL NIC.
Sorry!
-adrian
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailm
domain thing or something else.
Sorry, I don't have the cycles to try and fix wpi issues. ;(
-adrian
On 18 August 2013 13:58, Dominic Fandrey wrote:
> On 18/08/2013 21:29, Adrian Chadd wrote:
> > ... hm, but if you do destroy, then re-create manually, does it work?
> > (Versus
Hah!
I'm not tired of it. I like the layout; I'd like to see an better ascii
beastie logo (one that uses block characters if the terminal supports it)
to display something pretty. But I do like the centred layout of the boot
menu.
-adrian
___
freebsd-
... hm, but if you do destroy, then re-create manually, does it work?
(Versus using service)
-adrian
On 18 August 2013 10:14, Dominic Fandrey wrote:
> My system was built yesterday. I just figured I'm not using the entire
> frequency range available in Europe. This is a potential problem whe
omly.
> I have no idea what is causing this, though. (the r254246 was from
> installing from a download of 9.2 dvd).
> On Sat, Aug 17, 2013 at 09:49:49PM -0700, Adrian Chadd wrote:
> > Hi!
> >
> > I'm not sure what could've caused this! Not much has changed in the
Hi!
I'm not sure what could've caused this! Not much has changed in the
wireless stack and ath driver between 9.1 and 9.2. Would you be able to
work through different svn versions of stable/9 between 9.1 and 9.2 to
narrow down when things broke?
It may be something other than the wifi driver/stac
Did the kmem_size_scale parameter get changed too?
Did you test this on 128mb or 256mb of RAM (in a VM will do) to see if
you still panic shortly after boot? Doing any kind of file/net IO
quickly leads to death.
-adrian
On 1 August 2013 06:22, wrote:
> Synopsis: 9.1 installer panics with a k
Nope, no such joy.
What else can I try?
-adrian
On 16 July 2013 02:16, Adrian Chadd wrote:
> I'll try it out soon, thanks!
>
>
>
> -adrian
>
> On 15 July 2013 14:35, Taku YAMAMOTO wrote:
>> This reminds me of my local patch which I wrote and forgot about deep
ether it's still required because I don't have X61 handy
> anymore...
>
>
> On Mon, 8 Jul 2013 11:09:20 -0700
> Adrian Chadd wrote:
>
>> On 7 July 2013 22:00, Ian Smith wrote:
>>
>> > Checking one more point .. do the USB ports come up ok if you o
Nope. It's a -10 thing.
-adrian
On 14 July 2013 08:01, Thomas Zander wrote:
> Hi,
>
> from the mailing lists I couldn't figure out whether 11n is supposed
> to work on stable since the existing mail threads seem to focus on
> current exclusively.
>
> And since the option exists in the stable k
Please test on VMs.
I've tested -HEAD in i386 virtualbox all the way down to 128mb with no
panics. I'll test with 64mb soon. It's easy to do.
i think the i386 PAE stuff on ${LARGE} memory systems is still broken. Peter?
-adrian
On 11 July 2013 07:59, Alfred Perlstein wrote:
> Andre, Peter wha
On 8 July 2013 11:19, John Baldwin wrote:
> From sys/amd64/include/apicreg.h:
This system runs an i386 kernel.
> /* fields in ESR */
> #define APIC_ESR_SEND_CS_ERROR 0x0001
> #define APIC_ESR_RECEIVE_CS_ERROR 0x0002
> #define APIC_ESR_SEND_ACCEPT0x0004
> #
On 7 July 2013 22:00, Ian Smith wrote:
> Checking one more point .. do the USB ports come up ok if you originally
> boot with nothing plugged in? If so (or if not), does that local APIC
Yes.
> error message appear the same then too?
>
No
-adrian
Nope, no power after first resume if i have nothing plugged in.
Why?
-adrian
On 7 July 2013 13:49, Lars Engels wrote:
> On Sun, Jun 30, 2013 at 03:02:57PM -0700, Adrian Chadd wrote:
>> On 30 June 2013 07:22, Ian Smith wrote:
>>
>> > After removing [numbers] (for
The USB stack will currently run a complete controller reset upon
> resume, like during boot.
>
> --HPS
>
>
>
> -Original message-
>> From:Ian Smith
>> Sent: Sunday 7th July 2013 7:52
>> To: Adrian Chadd
>> Cc: freebsd-a...@freebsd.org; freebsd-s
On 30 June 2013 07:22, Ian Smith wrote:
> After removing [numbers] (for WITNESS?), diff started making sense.
> The below is between the first and second suspend/resume cycles in
> dmesg-3.txt, encompassing the others.
Cool!
> Nothing of note that I can see, if that usb hub-to-bus remapping is
On 27 June 2013 04:58, Ian Smith wrote:
> Well if there's a functional change in head that fixes this on Lars' and
> yours, getting it into stable shouldn't be so hard I expect. However if
> there's a fix (or some Lenovo workaround) for yours on 9 it'd be useful
> to hunt it down, no? I utterly
t VGA Mode (say, 80x50)
* go through an ACPI suspend/resume cycle
* See the VGA display be corrupt.
On 21 July 2012 17:28, Adrian Chadd wrote:
> Hi!
>
> I just tried it. It worked:
>
> * resume occured and the video mode was corrupt;
> * then shortly after it went through all the
On 26 June 2013 12:51, Lars Engels wrote:
> On Tue, Jun 25, 2013 at 11:09:20PM -0700, Adrian Chadd wrote:
>> [snip] ok, I'll do a boot -v tonight when I get home and log things.
>>
>> Thanks!
>
> Please also try a recent CURRENT. I was having the same issues with
[snip] ok, I'll do a boot -v tonight when I get home and log things.
Thanks!
Adrian
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freeb
On 21 June 2013 05:48, Ian Smith wrote:
> No acpidump output on -stable or -acpi anyway .. likely best as an URL,
> if it comes down to ACPI.
Ok, I'll put it online in a sec.
> So the fingerprint reader, camera and bluetooth shown in your usbconfig
> don't serve as 'USB devices plugged in' in t
Hi,
FreeBSD-9 works fine on this Lenovo T400 - except that suspending with
no USB devices plugged in result in no ports working after resume.
If I have a device plugged in during suspend - on any port - then all
the ports work fine after resume.
I've attached usbconfig and acpidump output.
here
'ola!
Cool, you've nailed it down to a specific revision.
Can you create a PR (www.freebsd.org/send-pr.html) with all of this information?
Hans/USB folk - here's an interesting problem. The original email is below.
===
Sorry, for waiting this long to post this problem, I thought it would
be de
Are you able to narrow down the specific commit along 9-stable that broke it?
Thanks!
Adrian
On 16 May 2013 18:00, Jože Zobec wrote:
> Sorry, for waiting this long to post this problem, I thought it would be
> dealt with this week, but since it wasn't better to report it now. I hope
> this
Hi,
Are you able to help someone figure out what's going on?
The main problem with IPX / netware testing is that we just don't have
netware servers lying around. :)
Adrian
On 13 May 2013 14:10, Marek Salwerowicz wrote:
> W dniu 2013-05-13 08:52, Jeremy Chadwick pisze:
>
>> IPX has been negl
It's supported as long as someone wants to use it and can help in at
least diagnosing issues.
So, if you have a segfault, run it inside gdb and report where its dying.
Chances are things have just bitrotted a bit but not so much that it's
worth killing.
adrian
On 12 May 2013 14:54, Marek Sa
On 29 April 2013 11:00, Fabian Wenk wrote:
> Is there anything I can do to debug?
I don't know. Unfortunately there's no active uart maintainer.
That's why I was wondering if someone already knew about whether uart
kept underflow/overflow statistics.
Adrian
___
Hm, can you double check the port configuration? is it somehow getting
the number of stop bits wrong or something? What about flow control?
Are there overflow/underflow counters with the uart driver? I wonder
if you're hitting issues there.
adrian
___
1 - 100 of 305 matches
Mail list logo
