Re: "Could not allocate I/O space" and "intsmb0 attach returned 6" in a under-Hyper-V context on Ryzen Threadripper: Is this expected?
On 09/04/2018 22:37, John Baldwin wrote: > On Sunday, April 01, 2018 02:23:36 PM Mark Millard wrote: >> For: >> >> # uname -apKU >> FreeBSD FBSDHUGE 12.0-CURRENT FreeBSD 12.0-CURRENT r331831M amd64 amd64 >> 1200060 1200060 >> >> I get: >> >> . . . >> pci0: at device 7.3 (no driver attached) >> . . . >> intsmb0: at device 7.3 on pci0 >> intsmb0: Could not allocate I/O space >> device_attach: intsmb0 attach returned 6 >> >> on a Ryzen Threadripper 1950X where FreeBSD is being run under >> Hyper-V (on a Windows 10 Pro machine). Note the above. >> Is this expected? Did I misconfigure something in Hyper-V? > > That seems like an odd device to have for an AMD machine. Except that this is not an AMD machine but a Hyper-V? (And even if that were a physical AMD machine the driver would not be odd for it as the driver supports AMD chipsets that provide SMBus controllers compatible with PIIX4). Mark provided the following information in his post: >> # pciconf -l -v 0:0:7:3 >> none0@pci0:0:7:3: class=0x068000 card=0x chip=0x71138086 >> rev=0x02 >> hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82371AB/EB/MB PIIX4 ACPI' >> class = bridge My guess is that Hyper-V's emulation of PIIX4 is not complete or correct with respect to the SMBus controller. And, as I am sure that Hyper-V does not emulate any SMBus slaves anyway, it would be completely useless. > I suspect that this has never > worked and the module started auto-loading due to devmatch. This must be true. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: Linux compat / changing compat path
On 21/03/2018 10:39, Stefan Esser wrote: > And you want to change occurances of /compat/linux in the kernel (and possibly > some libraries and user programs), e.g. in /sys/amd64/linux/linux_sysvec.c ... > > There is some magic that makes an exec of /bin/sh look up /compat/linux/bin/sh > first, if performed from within a program running under Linux emulation, and > if you need that behavior, you have to adjust at least the kernel sources. > > Maybe the hard-coded "/compat/linux" should be replaced by a macro, to allow > easy modification without loss of functionality ... I am not sure what would actually happen in the following case. Create a jail and make it "pure Linux". That is, install only Linux binaries there, no FreeBSD at all. And install them under the root of the jail, that is, no /compat/linux within the jail. Would that work? Would I be able to start such a jail (processes in it) ? Would they be able to correctly find their libraries and other executables they might want to exec? If this works or could be made to work, then I am sure that some people would it useful. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: FreeBSD on Ryzen
On 03/23/2017 06:05, Don Lewis wrote: > Package ID shift: 4 > L3 cache ID shift: 3 > L2 cache ID shift: 1 > L1 cache ID shift: 1 > Core ID shift: 0 > INTR: Adding local APIC 1 as a target > INTR: Adding local APIC 2 as a target > INTR: Adding local APIC 3 as a target > INTR: Adding local APIC 4 as a target > INTR: Adding local APIC 5 as a target > INTR: Adding local APIC 6 as a target > INTR: Adding local APIC 7 as a target > INTR: Adding local APIC 8 as a target > INTR: Adding local APIC 9 as a target > INTR: Adding local APIC 10 as a target > INTR: Adding local APIC 11 as a target > INTR: Adding local APIC 12 as a target > INTR: Adding local APIC 13 as a target > INTR: Adding local APIC 14 as a target > INTR: Adding local APIC 15 as a target > FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs > FreeBSD/SMP: 1 package(s) x 16 core(s) Don, thank you! Could you please test this patch https://paste.debian.net/923675/ and see if it allows to detect SMT threads? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: FreeBSD on Ryzen
On 03/23/2017 01:26, Don Lewis wrote: > Yes. The motherboard is a Gigabyte GA-AB350 Gaming. On the motherboard > specification page it specifically says: > Support for ECC Un-buffered DIMM 1Rx8/2Rx8 memory modules (operate in > non-ECC mode) > and there are no knobs in the BIOS to enable ECC. I was hoping to get > lucky though because the memory support list has an entry for the RAM > that I purchased with a checkmark in the ECC column. I've got some older > Gigabyte AM2 - AM3+ boards that support ECC even though it is not > mentioned anywhere in the spec. > > I have heard rumors that some other motherboards silently support ECC if > they detect it even though they don't have any mention of it in their > BIOS configuration screens. Yeah, that's the reason I asked. > To check this I installed the latest > version of Fedora rawhide and there was no indication of ECC support in > the boot messages, edac-utils didn't find it, and dmidecode said that > the memory was 64 bits wide and not 72. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: FreeBSD on Ryzen
3 on hdac0 > hdaa3: at nid 1 on hdacc3 > pcm3: at nid 5 on hdaa3 > hdacc4: at cad 0 on hdac1 > hdaa4: at nid 1 on hdacc4 > pcm4: at nid 20 and 24,26 on hdaa4 > pcm5: at nid 27 and 25 on hdaa4 > pcm6: at nid 17 on hdaa4 > ugen1.1: <0x1022 XHCI root HUB> at usbus1 > ugen0.1: <0x1022 XHCI root HUB> at usbus0 > uhub0: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1 > uhub1: <0x1022 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 > ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 > ada0: ATA8-ACS SATA 2.x device > ada0: Serial Number WD-WCASJ1778605 > ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) > ada0: Command Queueing enabled > ada0: 953869MB (1953525168 512 byte sectors) > WARNING: WITNESS option enabled, expect reduced performance. > Trying to mount root from zfs:zroot/ROOT/default []... > Root mount waiting for: usbus1 usbus0 > uhub0: 8 ports with 8 removable, self powered > uhub1: 22 ports with 22 removable, self powered > ugen1.2: at usbus1 > umass0 on uhub0 > umass0: on > usbus1 > umass0: SCSI over Bulk-Only; quirks = 0x4101 > umass0:6:0: Attached to scbus6 > da0 at umass-sim0 bus 0 scbus6 target 0 lun 0 > da0: < USB Disk 8.07> Removable Direct Access SPC-2 SCSI device > da0: Serial Number 5E2CDC72 > da0: 40.000MB/s transfers > da0: 3840MB (7864320 512 byte sectors) > da0: quirks=0x2 > GEOM: da0: the secondary GPT header is not in the last LBA. > Root mount waiting for: usbus1 > ugen1.3: at usbus1 > re0: link state changed to DOWN > ums0 on uhub0 > ums0: on > usbus1 > ums0: 3 buttons and [XYZ] coordinates ID=0 > -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: AMD Ryzen 7 support
On 07/03/2017 05:10, Yonas Yanfa wrote: > Hi, > > Does FreeBSD 11 or CURRENT support the new AMD Ryzen 7 processor? We don't know. AMD hasn't given us any documentation or patches for Ryzen. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: [CFT] gcc: support for barcelona
on 29/05/2013 11:47 David Chisnall said the following: > Seriously? Your show stopper bug is that, very occasionally, clang emits > incorrect debug info? Yes, that bug breaks some DTrace scripts that are critical to me. Otherwise I would not have noticed the issue. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: [CFT] gcc: support for barcelona
on 28/05/2013 21:10 David Chisnall said the following: > On 28 May 2013, at 18:40, Warner Losh wrote: > >> That's not going to happen soon. While it works OK for amd64, there's still >> many bugs in its ARM support and even more in its MIPS support. There's 0 >> chance it will be gone in 10... > > I disagree. There is a significant chance that gcc in base will be gone for > all Tier 1 platforms in 10.0. There are still some reasons to want gcc > installed, but there are no compelling reasons to want an ancient version of > gcc installed on x86[-64] or ARM. For people who need gcc, the ports > collection provides a selection of recent versions. I will try to veto any attempt to do so until at least this bug is fixed: http://llvm.org/bugs/show_bug.cgi?id=15662 I am sure that other developers have their favorite bugs too. In fact, I am of opinion that while such bugs exist gcc should be crowned back as a default compiler. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/177633: FreeBSD 9.1 and ZFS deadlocked at shutdown/reboot
The following reply was made to PR amd64/177633; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, sc...@kitchin.com Cc: Subject: Re: amd64/177633: FreeBSD 9.1 and ZFS deadlocked at shutdown/reboot Date: Thu, 04 Apr 2013 18:32:48 +0300 I believe that this should be fixed in stable/9. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: My panic in amd64/pmap
on 25/01/2013 03:11 Larry Rosenman said the following: > I've moved all the core.txt's to: > http://www.lerctr.org/~ler/FreeBSD-PMAP/ > > I got another one on FreeBSD9 today > > Is there ANYONE interested in this? > > These always seem to be ZFS induced. > > I've added freebsd-fs to the cc list. > > I have vmcore's from them all. Can you try to reproduce the issue using the same VM image but in a different VM implementation? E.g. qemu... -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: My panic in amd64/pmap
on 17/01/2013 21:50 Larry Rosenman said the following: > I've now seen this panic: > pmap_insert_pt_page: pindex already inserted > > on 9.1-RELEASE, 9.1-STABLE, and 10.0-CURRENT > > I've got vmcore's from the 9.1-STABLE and 10.0-CURRENT VM's available > as well as sources. > > I have the core.txt.* files available at: > http://www.lerctr.org/~ler/core.txt.0 (10.0) > http://www.lerctr.org/~ler/core.txt.2 (9.1-S) > > I'm not sure what other debug info you need. > > I can provide SSH access to both VM's as well as the host. > > These are all in VirtualBox 4.2.6 VM's > > Any help would be appreciated. Hmm, I wonder if VirtualBox is hitting the same popcnt bug that was fixed in qemu... Could you please try a patch from here http://thread.gmane.org/gmane.comp.emulators.qemu/174532/focus=174567 ? It should be applied to src/recompiler/target-i386/translate.c, make sure that it goes to a section marked as 'case 0x1b8: /* SSE4.2 popcnt */'. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764)
The following reply was made to PR amd64/174409; it has been noted by GNATS. From: Andriy Gapon To: KAHO Toshikazu Cc: bug-follo...@freebsd.org Subject: Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764) Date: Wed, 26 Dec 2012 13:47:04 +0200 on 26/12/2012 13:34 KAHO Toshikazu said the following: > With pure head + your acpi.c patch, the machine can wake up > from sleep. But "irq9: acpi0" rate showed by "vmstat -i" is > increasing every second after resume. > To close and open LCD makes 2 irq9 before resume, but irq9 rate > is too fast after resume. That's something interesting. Thank you again! Could you please now try the following patch instead of all previous patches/hacks? http://people.freebsd.org/~avg/acpi-apic-wakeup.patch -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764)
The following reply was made to PR amd64/174409; it has been noted by GNATS. From: Andriy Gapon To: KAHO Toshikazu Cc: bug-follo...@freebsd.org Subject: Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764) Date: Wed, 26 Dec 2012 09:14:33 +0200 on 26/12/2012 05:27 KAHO Toshikazu said the following: > Hello, > >> Could you please re-apply r243764 and then try the following _hack_? > > Yes, the machine can wake up with pure head src + this patch. Here is my current understanding of the situation. r243764 is actually an improvement, not a regression. What happens without r243764 during resume: ioapic pin 9 which is used for SCI/IRQ9 has some garbage in its CPU destination configuration, we unmask the pin, ioapic sends interrupt message to nowhere, the interrupt is never accepted and so the pin is stuck even after we program it with the correct destination. This is bad. What happens with r243764 during resume: we first program the correct destination (which happens to be BSP), then unmask the pin; as soon as interrupts on the BSP are re-enable SCI/IRQ9 is correctly delivered. This is the correct behavior, IMO. But apparently there is some problem in our ACPI code which leads to the hang. This is bad. While now I know where to look for the root cause, I don't know to do that in the early post-resume environment. As I understand, there is no way to output any information from kernel. This makes things hard. Some things to try (independently of each other) without the hack and with r243764: o cpuset -l 1 -x 9 -- to try to see what happens if SCI/IRQ9 is delivered to the AP instead of BSP o the following patch: --- a/sys/dev/acpica/acpi.c +++ b/sys/dev/acpica/acpi.c @@ -2776,6 +2776,9 @@ acpi_EnterSleepState(struct acpi_softc *sc, int state) sleep_result = acpi_sleep_machdep(sc, state); acpi_wakeup_machdep(sc, state, sleep_result, 0); AcpiLeaveSleepStatePrep(state); + + AcpiDisableAllGpes(); + intr_restore(intr); /* call acpi_wakeup_machdep() again with interrupt enabled */ >> Also, not sure if I asked before the following questions related to >> debugging possibilities. >> Does this system have a serial port? Are you able to setup serial >> console access? >> Or the same for firewire port/console. >> Does this system preserve memory content across reboot/reset? >> In other words, can you see messages from the previous boot in dmesg >> after a reboot? > > The machine I'm using is a cheap mobile notebook with a ULV CPU. > It does not have a serial port and a firewire. I have USB-serial > adapters, but I don't think it helps to make a serial console. > I can only take a memo by a pen, if the machine does not reboot > immediately and the keyboard on DDB is alive. > I see. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764)
The following reply was made to PR amd64/174409; it has been noted by GNATS. From: Andriy Gapon To: KAHO Toshikazu Cc: bug-follo...@freebsd.org Subject: Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764) Date: Tue, 25 Dec 2012 17:54:09 +0200 on 25/12/2012 15:38 KAHO Toshikazu said the following: > Hello, > >> Could you please take 'vmstat -i' output twice between reboot and >> resume (a few minutes apart) and then twice after resume (also a few >> minutes apart) ? > > "irq 9" does not seem to increase. > ( vmstat -i && sleep 300 && vmstat -i ) shows Thank you. Could you please re-apply r243764 and then try the following _hack_? --- a/sys/x86/x86/io_apic.c +++ b/sys/x86/x86/io_apic.c @@ -493,7 +493,7 @@ ioapic_resume(struct pic *pic) mtx_lock_spin(&icu_lock); for (i = 0; i < io->io_numintr; i++) - ioapic_program_intpin(&io->io_pins[i]); + if (i != 9) ioapic_program_intpin(&io->io_pins[i]); mtx_unlock_spin(&icu_lock); } Also, not sure if I asked before the following questions related to debugging possibilities. Does this system have a serial port? Are you able to setup serial console access? Or the same for firewire port/console. Does this system preserve memory content across reboot/reset? In other words, can you see messages from the previous boot in dmesg after a reboot? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764)
The following reply was made to PR amd64/174409; it has been noted by GNATS. From: Andriy Gapon To: KAHO Toshikazu Cc: bug-follo...@freebsd.org Subject: Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764) Date: Tue, 25 Dec 2012 12:07:58 +0200 on 25/12/2012 04:03 KAHO Toshikazu said the following: > Hello, > >> Oh, I should have realized that this won't work. Sorry about that. >> Could you please revert all patches from me and put your source tree into >> the >> working shape (head minus r243764) and the try the following purely >> diagnostic >> patch? The patch presumes that you have DDB in your kernel config. >> Please report output produced after resuming. >> Thank you. > > Thank you for making a new patch. The additional lines produced > by the patch are below here. They were copied form `dmesg -a` without > any changes, despite of some lines were mixed each other. [snip] > pin9: 00010c03:6602 [snip] > pin9: d030:0002 Hmm, quite interesting. Could you please take 'vmstat -i' output twice between reboot and resume (a few minutes apart) and then twice after resume (also a few minutes apart) ? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764)
The following reply was made to PR amd64/174409; it has been noted by GNATS.
From: Andriy Gapon
To: KAHO Toshikazu
Cc: bug-follo...@freebsd.org
Subject: Re: amd64/174409: stopping during resume caused by io_apic.c
change(r243764)
Date: Sun, 23 Dec 2012 09:32:02 +0200
on 19/12/2012 03:47 KAHO Toshikazu said the following:
> Hello,
>
>> Are you set up for crash dumps (minidumps are ok) ?
>> Could you please add a call to panic("ioapic_resume"); at the beginning of
>> ioapic_resume function in sys/x86/x86/io_apic.c and save a crash dump for
>> debugging?
>
> The machine now panics, but any keyboard operation makes nothing
> in debugger. If sysctl debug.debugger_on_panic=0 , kernel was
> trying to save a dump but failed by ahci error. All devices seem
> to be sleeping yet.
Oh, I should have realized that this won't work. Sorry about that.
Could you please revert all patches from me and put your source tree into the
working shape (head minus r243764) and the try the following purely diagnostic
patch? The patch presumes that you have DDB in your kernel config.
Please report output produced after resuming.
Thank you.
diff --git a/sys/x86/x86/io_apic.c b/sys/x86/x86/io_apic.c
index 4df27c2..1f82816 100644
--- a/sys/x86/x86/io_apic.c
+++ b/sys/x86/x86/io_apic.c
@@ -486,14 +486,30 @@ ioapic_config_intr
}
static void
+ioapic_dump(struct ioapic *io)
+{
+ int i;
+
+ printf("ioapic%u:\n", io->io_id);
+ for (i = 0; i < io->io_numintr; i++)
+ printf("pin%d: %08x:%08x\n", i,
+ ioapic_read(io->io_addr, IOAPIC_REDTBL_LO(i)),
+ ioapic_read(io->io_addr, IOAPIC_REDTBL_HI(i)));
+}
+
+static void
ioapic_resume(struct pic *pic)
{
struct ioapic *io = (struct ioapic *)pic;
int i;
mtx_lock_spin(&icu_lock);
+ printf("before re-programming ioapic\n");
+ ioapic_dump(io);
for (i = 0; i < io->io_numintr; i++)
ioapic_program_intpin(&io->io_pins[i]);
+ printf("after re-programming ioapic\n");
+ ioapic_dump(io);
mtx_unlock_spin(&icu_lock);
}
diff --git a/sys/x86/x86/local_apic.c b/sys/x86/x86/local_apic.c
index 0df973a..13e4b4f 100644
--- a/sys/x86/x86/local_apic.c
+++ b/sys/x86/x86/local_apic.c
@@ -342,6 +342,8 @@ lapic_dump(const char* str)
printf(" cmci: 0x%08x\n", lapic->lvt_cmci);
}
+static db_cmdfcn_t db_show_lapic;
+
void
lapic_setup(int boot)
{
@@ -353,6 +355,10 @@ lapic_setup(int boot)
la = &lapics[lapic_id()];
KASSERT(la->la_present, ("missing APIC structure"));
saveintr = intr_disable();
+
+ printf("before setup\n");
+ db_show_lapic(0, 0, 0, NULL);
+
maxlvt = (lapic->version & APIC_VER_MAXLVT) >> MAXLVTSHIFT;
/* Initialize the TPR to allow all interrupts. */
@@ -398,6 +404,9 @@ lapic_setup(int boot)
if (maxlvt >= LVT_CMCI)
lapic->lvt_cmci = lvt_mode(la, LVT_CMCI, lapic->lvt_cmci);
+ printf("after setup\n");
+ db_show_lapic(0, 0, 0, NULL);
+
intr_restore(saveintr);
}
--
Andriy Gapon
___
freebsd-amd64@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764)
The following reply was made to PR amd64/174409; it has been noted by GNATS.
From: Andriy Gapon
To: KAHO Toshikazu
Cc: bug-follo...@freebsd.org
Subject: Re: amd64/174409: stopping during resume caused by io_apic.c
change(r243764)
Date: Tue, 18 Dec 2012 16:18:34 +0200
on 18/12/2012 15:15 KAHO Toshikazu said the following:
> Hello,
>
>> I understand.
>> Could you please try the following patch on top of the previous one (without
>> reverting r227309, of course) ?
>
> Thank you for making patch.
>
> r244394 + patch : The machine hangs.
> r244394 + patch + io_apic.c reverting : The machine can wake up.
>
> The patch does not make any regression, but cannot solve the problem.
That's unfortunate...
Are you set up for crash dumps (minidumps are ok) ?
Could you please add a call to panic("ioapic_resume"); at the beginning of
ioapic_resume function in sys/x86/x86/io_apic.c and save a crash dump for
debugging?
--
Andriy Gapon
___
freebsd-amd64@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764)
The following reply was made to PR amd64/174409; it has been noted by GNATS.
From: Andriy Gapon
To: KAHO Toshikazu
Cc: bug-follo...@freebsd.org
Subject: Re: amd64/174409: stopping during resume caused by io_apic.c
change(r243764)
Date: Tue, 18 Dec 2012 11:55:09 +0200
on 18/12/2012 03:54 KAHO Toshikazu said the following:
> Hello, and thanks for your work.
>
>> Could you please try the following patch?
>> I suspect that it might not be sufficient, I am working on some
>> additional changes.
>
> The patched kernel dosen't solve the problem. On waking up,
> the machine hangs with LCD backlight on, but it shows nothing.
> Power off is all that I can do. Each revision (r243764 or r227309)
> of io_apic.c with the patch makes the machine hangs. The machine
> can wake up with io_apic.c reverted to r227309 and without the patch.
>
I understand.
Could you please try the following patch on top of the previous one (without
reverting r227309, of course) ?
--- a/sys/x86/acpica/acpi_wakeup.c
+++ b/sys/x86/acpica/acpi_wakeup.c
@@ -261,12 +261,17 @@ acpi_wakeup_machdep(struct acpi_softc *sc, int state, int
sleep_result,
#endif
}
+ /*
+ * Re-program IO-APIC pins to their correct states before
+ * enabling Local APICs (which is done when CPUs are restarted).
+ */
+ intr_resume();
+
#ifdef SMP
if (!CPU_EMPTY(&suspcpus))
restart_cpus(suspcpus);
#endif
mca_resume();
- intr_resume();
AcpiSetFirmwareWakingVector(0);
} else {
--- a/sys/x86/x86/intr_machdep.c
+++ b/sys/x86/x86/intr_machdep.c
@@ -287,11 +287,11 @@ intr_resume(void)
atpic_reset();
#endif
mtx_lock(&intr_table_lock);
- lapic_setup(0);
STAILQ_FOREACH(pic, &pics, pics) {
if (pic->pic_resume != NULL)
pic->pic_resume(pic);
}
+ lapic_setup(0);
mtx_unlock(&intr_table_lock);
}
I've put the combined patch here:
http://people.freebsd.org/~avg/apic-resume.diff
--
Andriy Gapon
___
freebsd-amd64@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764)
The following reply was made to PR amd64/174409; it has been noted by GNATS.
From: Andriy Gapon
To: Kaho Toshikazu
Cc: bug-follo...@freebsd.org
Subject: Re: amd64/174409: stopping during resume caused by io_apic.c
change(r243764)
Date: Tue, 18 Dec 2012 00:39:30 +0200
on 17/12/2012 13:59 Kaho Toshikazu said the following:
> Hello, and sorry for delay reply.
No problem and thank you for the data.
Could you please try the following patch?
I suspect that it might not be sufficient, I am working on some additional
changes.
--- a/sys/x86/x86/intr_machdep.c
+++ b/sys/x86/x86/intr_machdep.c
@@ -287,6 +287,7 @@ intr_resume(void)
atpic_reset();
#endif
mtx_lock(&intr_table_lock);
+ lapic_setup(0);
STAILQ_FOREACH(pic, &pics, pics) {
if (pic->pic_resume != NULL)
pic->pic_resume(pic);
diff --git a/sys/x86/x86/local_apic.c b/sys/x86/x86/local_apic.c
index 9b1e259..0df973a 100644
--- a/sys/x86/x86/local_apic.c
+++ b/sys/x86/x86/local_apic.c
@@ -160,7 +160,6 @@ static u_long lapic_timer_divisor;
static struct eventtimer lapic_et;
static void lapic_enable(void);
-static void lapic_resume(struct pic *pic);
static void lapic_timer_oneshot(struct lapic *,
u_int count, int enable_int);
static void lapic_timer_periodic(struct lapic *,
@@ -172,8 +171,6 @@ static int lapic_et_start(struct eventtimer *et,
struct bintime *first, struct bintime *period);
static intlapic_et_stop(struct eventtimer *et);
-struct pic lapic_pic = { .pic_resume = lapic_resume };
-
static uint32_t
lvt_mode(struct lapic *la, u_int pin, uint32_t value)
{
@@ -573,14 +570,6 @@ lapic_enable(void)
lapic->svr = value;
}
-/* Reset the local APIC on the BSP during resume. */
-static void
-lapic_resume(struct pic *pic)
-{
-
- lapic_setup(0);
-}
-
int
lapic_id(void)
{
@@ -1409,7 +1398,6 @@ apic_setup_io(void *dummy __unused)
* properly program the LINT pins.
*/
lapic_setup(1);
- intr_register_pic(&lapic_pic);
if (bootverbose)
lapic_dump("BSP");
--
Andriy Gapon
___
freebsd-amd64@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764)
The following reply was made to PR amd64/174409; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, k...@elam.kais.kyoto-u.ac.jp Cc: Subject: Re: amd64/174409: stopping during resume caused by io_apic.c change(r243764) Date: Fri, 14 Dec 2012 18:46:53 +0200 Could you please provide unabridged verbose dmesg from this system? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/173235: Have received two crashes within 1 day after installing new packages: Fatal trap 12: page fault in kernel mode
The following reply was made to PR amd64/173235; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, to...@anakin.ws Cc: Subject: Re: amd64/173235: Have received two crashes within 1 day after installing new packages: Fatal trap 12: page fault in kernel mode Date: Wed, 31 Oct 2012 14:31:15 +0200 This looks like an smbfs/netsmb related bug. P.S. There was no reason to chose 'amd64' category. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: regular hwpstate0: set freq failed, err 6
rq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 > orm0: at iomem 0xc-0xc7fff,0xcd800-0xce7ff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 > ppc0: cannot reserve I/O port range > ctl: CAM Target Layer loaded > acpi_throttle0: on cpu0 > hwpstate0: on cpu0 > Timecounters tick every 1.000 msec > usbus0: 12Mbps Full Speed USB v1.0 > usbus1: 12Mbps Full Speed USB v1.0 > usbus2: 480Mbps High Speed USB v2.0 > usbus3: 12Mbps Full Speed USB v1.0 > usbus4: 12Mbps Full Speed USB v1.0 > usbus5: 480Mbps High Speed USB v2.0 > usbus6: 12Mbps Full Speed USB v1.0 > ugen0.1: at usbus0 > uhub0: on usbus0 > ugen1.1: at usbus1 > uhub1: on usbus1 > ugen2.1: at usbus2 > uhub2: on usbus2 > ugen3.1: at usbus3 > uhub3: on usbus3 > ugen4.1: at usbus4 > uhub4: on usbus4 > ugen5.1: at usbus5 > uhub5: on usbus5 > ugen6.1: at usbus6 > uhub6: on usbus6 > uhub6: 2 ports with 2 removable, self powered > uhub0: 3 ports with 3 removable, self powered > uhub1: 3 ports with 3 removable, self powered > uhub3: 3 ports with 3 removable, self powered > uhub4: 3 ports with 3 removable, self powered > uhub2: 6 ports with 6 removable, self powered > uhub5: 6 ports with 6 removable, self powered > ada0 at ata1 bus 0 scbus6 target 0 lun 0 > ada0: CFA-7 device > ada0: 66.700MB/s transfers (UDMA4, PIO 512bytes) > ada0: 7647MB (15662304 512 byte sectors: 16H 63S/T 15538C) > ada0: Previously was known as ad2 > SMP: AP CPU #1 Launched! > SMP: AP CPU #3 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #4 Launched! > SMP: AP CPU #5 Launched! > Trying to mount root from ufs:/dev/ada0p2 [rw]... > > sysctl dev.cpu: > dev.cpu.0.%desc: ACPI CPU > dev.cpu.0.%driver: cpu > dev.cpu.0.%location: handle=\_PR_.P001 > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > dev.cpu.0.%parent: acpi0 > dev.cpu.0.freq: 175 > dev.cpu.0.freq_levels: 2800/8922 2500/7188 2300/6500 2000/5486 1750/4800 > 1500/4114 1400/3690 1225/3228 1050/2767 875/2306 700/1845 525/1383 350/922 > 175/461 > dev.cpu.0.cx_supported: C1/0 C2/100 > dev.cpu.0.cx_lowest: C1 > dev.cpu.0.cx_usage: 100.00% 0.00% last 14304us > dev.cpu.1.%desc: ACPI CPU > dev.cpu.1.%driver: cpu > dev.cpu.1.%location: handle=\_PR_.P002 > dev.cpu.1.%pnpinfo: _HID=none _UID=0 > dev.cpu.1.%parent: acpi0 > dev.cpu.1.cx_supported: C1/0 C2/100 > dev.cpu.1.cx_lowest: C1 > dev.cpu.1.cx_usage: 100.00% 0.00% last 28218us > dev.cpu.2.%desc: ACPI CPU > dev.cpu.2.%driver: cpu > dev.cpu.2.%location: handle=\_PR_.P003 > dev.cpu.2.%pnpinfo: _HID=none _UID=0 > dev.cpu.2.%parent: acpi0 > dev.cpu.2.cx_supported: C1/0 C2/100 > dev.cpu.2.cx_lowest: C1 > dev.cpu.2.cx_usage: 100.00% 0.00% last 125878us > dev.cpu.3.%desc: ACPI CPU > dev.cpu.3.%driver: cpu > dev.cpu.3.%location: handle=\_PR_.P004 > dev.cpu.3.%pnpinfo: _HID=none _UID=0 > dev.cpu.3.%parent: acpi0 > dev.cpu.3.cx_supported: C1/0 C2/100 > dev.cpu.3.cx_lowest: C1 > dev.cpu.3.cx_usage: 100.00% 0.00% last 94769us > dev.cpu.4.%desc: ACPI CPU > dev.cpu.4.%driver: cpu > dev.cpu.4.%location: handle=\_PR_.P005 > dev.cpu.4.%pnpinfo: _HID=none _UID=0 > dev.cpu.4.%parent: acpi0 > dev.cpu.4.cx_supported: C1/0 C2/100 > dev.cpu.4.cx_lowest: C1 > dev.cpu.4.cx_usage: 100.00% 0.00% last 46253us > dev.cpu.5.%desc: ACPI CPU > dev.cpu.5.%driver: cpu > dev.cpu.5.%location: handle=\_PR_.P006 > dev.cpu.5.%pnpinfo: _HID=none _UID=0 > dev.cpu.5.%parent: acpi0 > dev.cpu.5.cx_supported: C1/0 C2/100 > dev.cpu.5.cx_lowest: C1 > dev.cpu.5.cx_usage: 100.00% 0.00% last 19940us > > Anything I can do to help debug the message? or do I just need to > ignore it? > > Thanks. > -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: page fault after wiring page
invlva = TRUE;
> + if ((newpte & PG_W) &&
> + ((origpte & PG_RW) == 0) &&
> + (newpte & PG_RW)) {
> + invlva = TRUE;
> + }
>}
> if ((origpte & (PG_M | PG_RW)) == (PG_M | PG_RW)) {
> if ((origpte & PG_MANAGED) != 0)
>
> I wanted to see if anyone has seen issues in this area, and if this fix seems
> appropriate. I'm running 8.2, but I didn't see any obvious changes to pmap
> stuff in head which would change this behavior. Thanks for any feedback,
>
> Jeremiah Lott
> Avere Systems
--
Andriy Gapon
___
freebsd-amd64@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/164457: [install] Can't install FreeBSD 9.0 (amd64) on HP Blade (ProLiant BL465c G1 )
The following reply was made to PR amd64/164457; it has been noted by GNATS. From: Andriy Gapon To: Ewald Jenisch Cc: bug-follo...@freebsd.org Subject: Re: amd64/164457: [install] Can't install FreeBSD 9.0 (amd64) on HP Blade (ProLiant BL465c G1 ) Date: Thu, 26 Jan 2012 20:51:06 +0200 on 26/01/2012 19:45 Ewald Jenisch said the following: > On Thu, Jan 26, 2012 at 12:45:23AM +0200, Andriy Gapon wrote: >> >> I suspect that your problem might be related to the recent eventtimers >> changes. >> Could you please try playing with setting the following tunables on the >> loader >> prompt (via 'set' command)? >> >> kern.eventtimer.periodic=1 >> kern.eventtimer.timer="LAPIC" >> > > Hi Andriy, > > This neatly did the trick! :-) In setting both values I was able to boot > off the install-CD. After installation I had to make sure both of these > settings end up in /boot/loader.conf so the machine comes up. > > Unfortunately I've now got another problem: When doing a "sync" this > command obviously doesn't terminate (i.e. no commandline-prompt reappearing). > Could this be related to the same cause? Not sure. > BTW, Any documentation as to what these two settings you mentioned actually > do? > > Thanks for your help! There is eventtimers(4) manual page. You may also want to try to contact Alexander Motin (mav@) directly, he is the author and maintainer of that code. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/164457: [install] Can't install FreeBSD 9.0 (amd64) on HP Blade (ProLiant BL465c G1 )
The following reply was made to PR amd64/164457; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, a...@jenisch.at Cc: Subject: Re: amd64/164457: [install] Can't install FreeBSD 9.0 (amd64) on HP Blade (ProLiant BL465c G1 ) Date: Thu, 26 Jan 2012 00:45:23 +0200 First, there is probably no point in trying to boot without ACPI support on modern systems. Most likely "Safe mode" is just equivalent to "ACPI off" for the installation media. Second, it's surprising the Verbose option doesn't result in more verbose boot messages. Could you please re-test this? I suspect that your problem might be related to the recent eventtimers changes. Could you please try playing with setting the following tunables on the loader prompt (via 'set' command)? kern.eventtimer.periodic=1 kern.eventtimer.timer="LAPIC" -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: FreeBSD 9.0 (RC2) Causes BIOS Message on Reboot
on 14/12/2011 22:20 Thomas D. Dean said the following: > I know, this sounds strange. > > I have an ASUS P9X79 motherboard, Intel i7-3930K CPU. The motherboard > TPU switch is on. > > This overclocks the CPU to 4.162GHz. Calculated from the TSC, with code > from Intel. The details of doing this are in the CPUID datasheet. > sysctl dev.cpu.0 always shows freq as 3.201GHz no matter what the clock > actually is. > > Often, when rebooting from FreeBSD, I get a message from BIOS that > overclocking has failed - press F1 to enter setup. I press F1, exit > from setup, discarding changes, and the calculated CPU clock is > 3.201GHz. Overclocking has failed. > > I shutdown, cycle power, boot, and overclocking works, calculated CPU > clock is 4.162GHz. > > If I save changes when exiting from setup, overclocking works. A bus > reset is issued? > > I have a tripple boot, Windows 7 for possible warranty issues, Linux and > FreeBSD 9.0(RC2). > > I never see this message when rebooting from either of the other two > OS's, only FreeBSD. I booted all three 5 times and saw 3 instances of > overclocking failed when rebooting from FreeBSD. > > Here is the question: How may I find out what is causing this? > > I have an HP Envy 17 3D notebook that always has side effects of booting > FreeBSD 8.2 AMD64 where Windows 7 and Linux do not. An over temperature > message 0090D. The machine is not actually over temperature, just > something tweeked that BIOS sees. > > Two machines doing strange things on reboot - it is not hardware or > BIOS, both different. Just a hypothesis this might be caused by FreeBSD not following SMP spec recommendation on the warm reboot procedure to the last letter. Not sure how you can verify that or fix that short of implementing the recommendations. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: [head tinderbox] failure on i386/i386
on 12/12/2011 07:58 FreeBSD Tinderbox said the following: > In file included from /src/sys/kern/kern_racct.c:53: > /src/sys/sys/sx.h: In function '__sx_xlock': > /src/sys/sys/sx.h:154: warning: implicit declaration of function > 'SCHEDULER_STOPPED' > /src/sys/sys/sx.h:154: warning: nested extern declaration of > 'SCHEDULER_STOPPED' [-Wnested-externs] > *** Error code 1 This should be fixed in r228430. Apologies. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/159612: dtrace walltimestamp and timestamp functions incomplete
The following reply was made to PR amd64/159612; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, ashley@gmail.com Cc: Subject: Re: amd64/159612: dtrace walltimestamp and timestamp functions incomplete Date: Tue, 09 Aug 2011 12:45:55 +0300 You are completely correct about walltimestamp. I am not sure what problem you perceive with timestamp though. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/159222: unusual behavior writing boot0 from single user mode
on 28/07/2011 02:46 Mark Linimon said the following: > On Wed, Jul 27, 2011 at 04:31:01PM +0300, Andriy Gapon wrote: >> Why then did you pick amd64 as a category? > > IMHO it's not Tim's problem; the categories are just misnamed. > > One of these months I'm going to get out of ports-land and get back onto > the topic of "PR system". In whatever the next PR system is, there will > be a "hardware-specific" category or something similarly named. There > will not be any of the following: i386; amd64; www :-) > > (The latter will be "website".) > > It's not fair to blame our users for the drawbacks of the tool we give > them. I actually blamed not users but "us", but it was well disguised :-) I agree with you about amd64 and i386. I think I remember times when amd64 was warranted, when the architecture port was fresh and had genuine amd64-specific bugs and missing features. But now these are an extremely rare kind (comparing to total number of base OS bugs). I further agree with you that making users determine which subsystem is responsible for a bug is not a good approach. So until we have better bug reporting and management tools perhaps we could provide more clues to users in the current tools... Squeezing amd64 and i386 into kern could be done already, I guess. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/159222: unusual behavior writing boot0 from single user mode
on 27/07/2011 09:22 tim newsham said the following: >> Number: 159222 >> Category: amd64 >> Synopsis: unusual behavior writing boot0 from single user mode >> Confidential: no >> Severity: serious >> Priority: low >> Responsible:freebsd-amd64 >> State: open >> Quarter: >> Keywords: >> Date-Required: >> Class: sw-bug >> Submitter-Id: current-users >> Arrival-Date: Wed Jul 27 06:30:08 UTC 2011 >> Closed-Date: >> Last-Modified: >> Originator: tim newsham >> Release:8.2 >> Organization: >> Environment: > FreeBSD hpsux.x0d99.com 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 > 02:41:51 UTC 2011 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > amd64 > >> Description: > I boot single user, then I run "df" to see which disk is root. Then I run: > ># fdisk -B -b /boot/boot0 /dev/da0 > > when its done it says "/boot/boot0: Device not configured" (error varies) > and then afterwards most commands I type (like "ls") ellicit: > "vnode_pager_getpages: I/O read error" from the kernel. > > I get the same behavior on my real machine as well as in vmware. The vmware > has a clean 8.2 release installed off of DVD (8.2 release disk) and then > updated with "freebsd-update". > >> How-To-Repeat: > Install 8.2 release for amd64. > Update with freebsd-update (I don't know if this matters). > Boot single user. > Run "fdisk -B -b /boot/boot0 /dev/da0" (or whatever the root disk drive is). > Run "ls" after it completes. >> Fix: Picking on you at random, nothing personal. Have you verified that this problem is amd64 specific? I do not see anything in your report about trying i386. Why then did you pick amd64 as a category? If you don't know for sure that an issue is specific to some architecture, but the issue seems to be in kernel, then you can use just kern category. I wish that more users actually read this article: http://www.freebsd.org/doc/en/articles/problem-reports/article.html Section 4.4 provides quite clear guidelines on filling out the PR template. Among other things it says: If you are convinced that the problem will *only* [*] occur under the processor architecture you are using, select one of the architecture-specific categories: commonly i386 for Intel-compatible machines in 32-bit mode; amd64 for AMD machines running in 64-bit mode (this also includes Intel-compatible machines running in EMT64 mode); and less commonly arm, ia64, powerpc, and sparc64. [*] - emphasis is mine Maybe we should prominently feature a link to this article in send-pr and in the web interface. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: page fault in kernel
on 27/07/2011 09:39 Tim Newsham said the following: > I have an amd64 box that is occasionally panic'ing with a kernel > page fault while the system is under heavy load. My personal philosophy is that it is better to gather objective data before making any speculations: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html > I tried swapping > out ram and running ram tests and that hasn't seem to turn up > anything. I originally saw this with 8.1 but I recently updated to > 8.2 to be sure and I'm still seeing the problem. I'm up to date > with "freebsd-update" and I verified that the core files all match > the md5 of a clean 8.2 release (after it is also updated). I also > tried to disable various frills I had installed (like ip6 tunnel). > > The normal way I repro this issue is to start a "portupgrade -caP" > going and I usually get a crash within a few hours. Sometimes > I see some unusual behavior instead of or right before a crash > (ie. program segfaults that shouldn't normally). > > Are there any known kernel issues that sound similar to this > problem? I've been working under the assumption that this is > probably hardware related, but I haven't yet ruled out software. > > I'll probably be trying some tests with cpuburn. Any other advice > for tracking down this issue would be appreciated. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: powernow regression in 8-STABLE
on 25/07/2011 21:55 Jung-uk Kim said the following: > powernow expects a static table > (via acpi_perf) but _PSS is dynamically constructed at runtime. I > don't think we can support this case easily, sorry. Just a side note. Actually I do not see anything wrong with that _PSS except that ASL seems to have been passed through a mangler and it makes reading the code hard. _PSS is a method and it is evaluated as a method in acpi_perf, the method returns a package. I am not sure what exactly you meant when you said that powernow expects a static table. I do not see why the return value can not be dynamically constructed while _PSS is evaluated and why that would affect any of our code. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/158552: ROOT MOUNT ERROR (caused by AHCI module)
The following reply was made to PR amd64/158552; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, terrawattsh...@gmail.com Cc: Subject: Re: amd64/158552: ROOT MOUNT ERROR (caused by AHCI module) Date: Fri, 01 Jul 2011 16:03:50 +0300 That forum thread is a mess, it starts stating one problem and ends with something that looks totally different. Please clearly state your problem in the PR. BTW, there was no reason to assign this PR to category amd64, it's a 'kern' problem. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/157386: [powerd] Enabling powerd(8) with default settings on Intel Xeon-E3 results in system freeze
The following reply was made to PR amd64/157386; it has been noted by GNATS. From: Andriy Gapon To: David Graham , bug-follo...@freebsd.org Cc: Subject: Re: amd64/157386: [powerd] Enabling powerd(8) with default settings on Intel Xeon-E3 results in system freeze Date: Tue, 31 May 2011 09:08:48 +0300 on 29/05/2011 17:19 David Graham said the following: > On 05/29/11 01:59, Andriy Gapon wrote: >> >> Can you provide output of the dev.cpu sysctl and a snippet of devinfo >> command >> output that shows devices under cpu0? >> > Hi Andriy, > > ev.cpu.0.%desc: ACPI CPU > dev.cpu.0.%driver: cpu > dev.cpu.0.%location: handle=\_SB_.CP00 > dev.cpu.0.%pnpinfo: _HID=none _UID=0 > dev.cpu.0.%parent: acpi0 > dev.cpu.0.freq: 2654 > dev.cpu.0.freq_levels: 2654/-1 2322/-1 1990/-1 1658/-1 1327/-1 995/-1 663/-1 > 331/-1 > dev.cpu.0.cx_supported: C1/0 > dev.cpu.0.cx_lowest: C1 > dev.cpu.0.cx_usage: 100.00% last 2224us > [snip] > cpu0 > acpi_throttle0 > cpufreq0 > acpi_timer0 I'd say that the problem is because of acpi_throttle driver, which is kind of dangerous and useless driver because of how it regulates frequency. I usually disable it on my Intel machines via: hint.acpi_throttle.0.disabled=1 I am a bit surprised that acpi_perf and (dependent on it) est drivers haven't attached. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/157386: [powerd] Enabling powerd(8) with default settings on Intel Xeon-E3 results in system freeze
The following reply was made to PR amd64/157386; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, dgra...@unthinkable.org Cc: Subject: Re: amd64/157386: [powerd] Enabling powerd(8) with default settings on Intel Xeon-E3 results in system freeze Date: Sun, 29 May 2011 09:59:53 +0300 Can you provide output of the dev.cpu sysctl and a snippet of devinfo command output that shows devices under cpu0? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: Fwd: [releng_7 tinderbox] failure on amd64/amd64
on 20/05/2011 04:30 Jeremy Chadwick said the following: > - Forwarded message from FreeBSD Tinderbox - >> http://tinderbox.freebsd.org/tinderbox-releng_7-RELENG_7-amd64-amd64.full > > Specific to RELENG_7. Andriy, any fixes committed which haven't shown > up on cvsweb yet? If so sorry for jumping the gun. > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/sound/pcm/dsp.c > Thank you for drawing my attention to the report. I have acted sloppy again :( Should be fixed in r222113 now. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: AMD64 performance degrade under nforce310 computer
on 18/03/2011 14:37 Jacky Cao said the following: > > Any suggestion? I thought 64bit x86 should be more faster than i386. This statement is not necessarily true. No advise on your specific hardware though, sorry. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/148526: [ahci] ahci driver does not boot on AMD chip
The following reply was made to PR amd64/148526; it has been noted by GNATS. From: Andriy Gapon To: Yury Cc: bug-follo...@freebsd.org, Alexander Motin Subject: Re: amd64/148526: [ahci] ahci driver does not boot on AMD chip Date: Thu, 16 Dec 2010 19:11:38 +0200 on 09/12/2010 19:08 Yury said the following: > Here they are, message files. > > The "bad" file is messages during boot try with the ahci driver, and the > "good" > one is the backed up kernel version with ata driver. In the "bad" boot try > messages last lines could repeat infinitely. And, as I can see there are some > 'time-out' messages in "good" variant, but everything works just fine. BIOS > was > updated to 15.06. > > Only differences in kernel config files are: > > < deviceata > < deviceatadisk >--- > > #deviceata > > #deviceatadisk > > < ##deviceahci > < deviceatapicd >--- > > deviceahci > > #deviceatapicd > Yury, will you be able to test ahci with this hardware using stable/8? Alexander, can you please take a look at this PR? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/131314: [modules] [panic] large modules fail to load on amd64
The following reply was made to PR amd64/131314; it has been noted by GNATS. From: Andriy Gapon To: "Kenneth D. Merry" Cc: bug-follo...@freebsd.org Subject: Re: amd64/131314: [modules] [panic] large modules fail to load on amd64 Date: Mon, 06 Dec 2010 20:08:18 +0200 on 06/12/2010 19:58 Kenneth D. Merry said the following: > The reason is, the module in question was already very large to start with, > and the table put it over the edge. So the total amount of static data in > the module was probably a good bit larger than 800KB. OK, bumped the array size to ~7MB: l O .rodata006d6000 large3 0020 l O .data 006d6000 large2 l O .bss 006d6000 large1 Total module file size is ~14MB. Everything is OK still. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/131314: [modules] [panic] large modules fail to load on amd64
The following reply was made to PR amd64/131314; it has been noted by GNATS. From: Andriy Gapon To: "Kenneth D. Merry" Cc: bug-follo...@freebsd.org Subject: Re: amd64/131314: [modules] [panic] large modules fail to load on amd64 Date: Mon, 06 Dec 2010 19:49:26 +0200 on 06/12/2010 19:11 Andriy Gapon said the following: > BTW, do you remember if it was initialized or not, and how it was used? > I.e., did the structure end up in .data, .rodata or .bss? I couldn't reproduce the problem with an array of about 800KB in size in any of the three sections. I think that gives a ground for closing the PR. If the problem resurfaces then we could re-open it or open a new one. Do you agree? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/131314: [modules] [panic] large modules fail to load on amd64
The following reply was made to PR amd64/131314; it has been noted by GNATS. From: Andriy Gapon To: "Kenneth D. Merry" Cc: bug-follo...@freebsd.org Subject: Re: amd64/131314: [modules] [panic] large modules fail to load on amd64 Date: Mon, 06 Dec 2010 19:11:52 +0200 on 06/12/2010 18:11 Kenneth D. Merry said the following: > But, you may be able to reproduce the problem by putting a very large > global variable/table in the kernel and see what happens. As I > mentioned in the bug report, I made the problem go away by taking out that > table. I will try. BTW, do you remember if it was initialized or not, and how it was used? I.e., did the structure end up in .data, .rodata or .bss? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/115194: LCD screen remains blank after Dell XPS M1210 lid is closed and reopened.
on 06/12/2010 18:48 Jung-uk Kim said the following: > On Sunday 05 December 2010 07:56 am, Bruce Cran wrote: >> On Sun, 5 Dec 2010 10:10:15 GMT >> >> Andriy Gapon wrote: >>> is this still an issue with recent revisions of head or >>> stable/8? >> >> It's still a problem on my XPS M1530: the only workaround is to >> suspend from within X11 using a version of the closed-source >> 'nvidia' driver built using ACPI support. > > Generally speaking, we cannot fix NVIDIA resume issues without help of > closed-source driver unless we reverse-engineer their driver and > figure out their power management magic. Probably Linux KMS driver > for X.org nouveau may give us some hints but I gave up. :-( And, just in case, let me also point out, to Bruce :-), that the PR at hand is about different hardware. So it's not clear if we have a single problem here or two different problems. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/76136: [hang] system halts before reboot
on 05/12/2010 23:40 Sebastian Chmielewski said the following: > On Sun, 5 Dec 2010 09:41:33 GMT > a...@freebsd.org wrote: > >> Synopsis: [hang] system halts before reboot >> >> State-Changed-From-To: open->closed >> State-Changed-By: avg >> State-Changed-When: Sun Dec 5 09:34:16 UTC 2010 >> State-Changed-Why: >> I think that the problem reported in this PR is still >> reported from time to time, but I am closing this PR anyway: >> - it's very old and for FreeBSD 5.3 >> - no followups or feedback > > I'm experiencing this issue on my FreeBSD 8.1 with Core 2 Duo T5500 in 64 bit > mode. It happens when system was suspended at least > once before trying to shutdown. > > Steps: > - power on > - use 'zzz' command to put machine in ACPI suspend > - wake up > - shutdown -h now > - last message seen on console log is "stopping other cpus" > Hang up doesn't happen when laptop wasn't suspended befoere trying to > shutdown. Will you be able to debug this? I'd start with adding DDB support to kernel and trying to enter DDB when the hang takes place. Thanks! -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/152430: HP ProLiant Microserver n36l cannot boot into installer
The following reply was made to PR amd64/152430; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, beat.siegentha...@beatsnet.com Cc: Subject: Re: amd64/152430: HP ProLiant Microserver n36l cannot boot into installer Date: Sun, 05 Dec 2010 16:33:56 +0200 Just to clarify - the reset happens between loader and kernel? Can you try a recent CURRENT snapshot? Also, I suggest that you try to discuss this issue on current@ or stable@ mailing list depending on which FreeBSD versions you try. Thanks! -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/148152: [boot] Run levels crash on boot up for dv7-1130US HP Laptop.
The following reply was made to PR amd64/148152; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, eb30...@gmail.com Cc: Subject: Re: amd64/148152: [boot] Run levels crash on boot up for dv7-1130US HP Laptop. Date: Sun, 05 Dec 2010 16:15:28 +0200 I am going to close this PR. Sorry if I'll sound impolite, but either I don't understand what run levels mean in FreeBSD context, or you can't read the words next to the numbers in FreeBSD boot menu :-) -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/148526: [ahci] ahci driver does not boot on AMD chip
The following reply was made to PR amd64/148526; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, y...@gorodok.net, Alexander Motin Cc: Subject: Re: amd64/148526: [ahci] ahci driver does not boot on AMD chip Date: Sun, 05 Dec 2010 16:29:32 +0200 Can you provide some technical information about the problem? Screen captures, etc? Alexander, maybe you've got some ideas/suggestions? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/57250: [amd64] [patch] Broken PTRACE_GETFPREGS and PTRACE_SETFPREGS
The following reply was made to PR amd64/57250; it has been noted by GNATS. From: Andriy Gapon To: Kostik Belousov Cc: bug-follo...@freebsd.org, kette...@gnu.org Subject: Re: amd64/57250: [amd64] [patch] Broken PTRACE_GETFPREGS and PTRACE_SETFPREGS Date: Sun, 05 Dec 2010 16:26:30 +0200 on 05/12/2010 16:11 Kostik Belousov said the following: > On Sun, Dec 05, 2010 at 03:38:12PM +0200, Andriy Gapon wrote: >> >> Kostik, >> >> could you please assess the status of this issue? >> Thanks! >> -- >> Andriy Gapon > Amuzingly enough, I fixed this in r215865 on 2010-11-26, that was > merged to stable/8 in r216162 on 2010-12-03, even forgetting mentioning > this in the commit message. I suspected something like that :-) Thanks a lot! -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/134978: [panic] g_up pmap amd64 panic
The following reply was made to PR amd64/134978; it has been noted by GNATS. From: Andriy Gapon To: GD Cc: bug-follo...@freebsd.org Subject: Re: amd64/134978: [panic] g_up pmap amd64 panic Date: Sun, 05 Dec 2010 16:22:34 +0200 on 05/12/2010 14:59 GD said the following: > Sorry, but this problem in 9.0-CURRENT is not repeating. That's good news, thank you! > On 2010-12-05, at 13:28, Andriy Gapon wrote: > >> >> Are still able to reproduce the problem? >> Some additional debugging information is required to analyze the problem. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/144405: [build] [patch] include /usr/obj/lib32 in cleanworld target on amd64 arch
The following reply was made to PR amd64/144405; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, alexbes...@wwu.de, Anonymous Cc: Subject: Re: amd64/144405: [build] [patch] include /usr/obj/lib32 in cleanworld target on amd64 arch Date: Sun, 05 Dec 2010 16:11:15 +0200 Hey guys, have you tried discussing this on the mailing lists? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/122549: 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial console
The following reply was made to PR amd64/122549; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, marq...@roble.com Cc: Subject: Re: amd64/122549: 7.0-RELEASE-amd64-bootonly.iso doesn't work w/ serial console Date: Sun, 05 Dec 2010 15:52:26 +0200 Is this still an issue? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/57250: [amd64] [patch] Broken PTRACE_GETFPREGS and PTRACE_SETFPREGS
The following reply was made to PR amd64/57250; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, kette...@gnu.org, Konstantin Belousov Cc: Subject: Re: amd64/57250: [amd64] [patch] Broken PTRACE_GETFPREGS and PTRACE_SETFPREGS Date: Sun, 05 Dec 2010 15:38:12 +0200 Kostik, could you please assess the status of this issue? Thanks! -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/141413: [hang] Tyan 2881 m3289 SMDC freeze
The following reply was made to PR amd64/141413; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, bkyoung7...@yahoo.com Cc: Subject: Re: amd64/141413: [hang] Tyan 2881 m3289 SMDC freeze Date: Sun, 05 Dec 2010 16:08:44 +0200 Is this still an issue? The problem looks related to network code. It would be useful to discuss this on n...@. It would be useful if you could get a stack trace of the hang. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/127640: [amd64] gcc(1) will not build shared libraries with -fprofile-generate on amd64
The following reply was made to PR amd64/127640; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, zl...@acm.org, John Baldwin , Bruce Cran Cc: Subject: Re: amd64/127640: [amd64] gcc(1) will not build shared libraries with -fprofile-generate on amd64 Date: Sun, 05 Dec 2010 15:57:36 +0200 What's the status of this situation? Is the originator interested in pursuing it further? (The PR is 2+ years old after all). -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/115581: [Makefile] [patch] -mfancy-math-387 has no effect
The following reply was made to PR amd64/115581; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, numise...@yahoo.com, Bruce Evans Cc: Subject: Re: amd64/115581: [Makefile] [patch] -mfancy-math-387 has no effect Date: Sun, 05 Dec 2010 15:46:41 +0200 Can this PR be simply closed based on the discussion and its age? Or is there any merit for looking into this again/further? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/114270: [cpufreq] cpufreq doesnt work when compiled in to kernel on amd64 platform
The following reply was made to PR amd64/114270; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, yurte...@ispro.net Cc: Subject: Re: amd64/114270: [cpufreq] cpufreq doesnt work when compiled in to kernel on amd64 platform Date: Sun, 05 Dec 2010 15:44:12 +0200 Is this still an issue? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/110599: [geli] geli attach to gmirror device hangs and cannot be killed
The following reply was made to PR amd64/110599; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, schul...@jhu.edu Cc: Subject: Re: amd64/110599: [geli] geli attach to gmirror device hangs and cannot be killed Date: Sun, 05 Dec 2010 15:41:27 +0200 Just checking, is this still an issue? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/151385: [boot] Installation hangs on MacBook
The following reply was made to PR amd64/151385; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, rene.st...@gmail.com Cc: Subject: Re: amd64/151385: [boot] Installation hangs on MacBook Date: Sun, 05 Dec 2010 15:30:57 +0200 Can you please try the latest head or stable/8 here? jkim@ has recently committed a general fix for MacBook problems. Thanks! -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/149713: [ata] [panic] Kernel crashes on HD timeout
The following reply was made to PR amd64/149713; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, p...@swarmtv.nl Cc: Subject: Re: amd64/149713: [ata] [panic] Kernel crashes on HD timeout Date: Sun, 05 Dec 2010 15:27:44 +0200 Is still an issue for you? Have you tried the suggestion from m...@? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/141060: [install] Can't install 8.0-RELEASE on the server where 7.2 works fine [regression]
The following reply was made to PR amd64/141060; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, kos...@adfox.ru Cc: Subject: Re: amd64/141060: [install] Can't install 8.0-RELEASE on the server where 7.2 works fine [regression] Date: Sun, 05 Dec 2010 15:08:57 +0200 Is this still a problem? Have you tried to follow the suggestion? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/140145: [boot] Installation boot sequence freezes
The following reply was made to PR amd64/140145; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, rui.pfco...@gmail.com Cc: Subject: Re: amd64/140145: [boot] Installation boot sequence freezes Date: Sun, 05 Dec 2010 14:54:08 +0200 is this still a problem? Looks like possible sysinstall issue. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/140715: [boot] Dell M600 Blade fails to boot 7.2+ 64 bit
The following reply was made to PR amd64/140715; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, cliff.sprad...@gmail.com Cc: Subject: Re: amd64/140715: [boot] Dell M600 Blade fails to boot 7.2+ 64 bit Date: Sun, 05 Dec 2010 14:57:36 +0200 Is still an issue? Can you provide screen captures from a verbose boot? Will you be able to try CURRENT snapshot and break into DDB? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/139998: [panic] 7.2 amd64 panic in kern_mutex.c:339
The following reply was made to PR amd64/139998; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, all...@nbs-inc.com Cc: Subject: Re: amd64/139998: [panic] 7.2 amd64 panic in kern_mutex.c:339 Date: Sun, 05 Dec 2010 14:53:07 +0200 Is this still an issue? Looks like a problem in network code, so it is worth reporting and discussing this on n...@. P.S. Simply opening a miscategorized PR without trying to discuss a problem on the mailing list(s) is a sure way to get no help. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/139924: [boot] cd or dvd not load
The following reply was made to PR amd64/139924; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, yilma...@gmail.com Cc: Subject: Re: amd64/139924: [boot] cd or dvd not load Date: Sun, 05 Dec 2010 14:49:27 +0200 Is still an issue? Will you able to provide additional details? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/138029: [panic] periodically kernel panic and reboot
The following reply was made to PR amd64/138029; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, stepa...@gmail.com Cc: Subject: Re: amd64/138029: [panic] periodically kernel panic and reboot Date: Sun, 05 Dec 2010 14:41:48 +0200 Is this still a problem? Looks like a possible issue with bpf. Probably worth reporting to / discussing on n...@. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/137942: [pci] 8.0-BETA2 having problems with Asus M2N-SLI-deluxe motherboard [regression]
The following reply was made to PR amd64/137942; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, h...@bbnetworks.net, John Baldwin Cc: Subject: Re: amd64/137942: [pci] 8.0-BETA2 having problems with Asus M2N-SLI-deluxe motherboard [regression] Date: Sun, 05 Dec 2010 14:40:16 +0200 What's the current status of this issue? Is manual user action still required? Or do we automatically blacklist this hardware? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/135265: [install] Boot from install cd hangs on HP DL160 G5 with LSI SAS1064E
The following reply was made to PR amd64/135265; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, balda...@zsupport.ru Cc: Subject: Re: amd64/135265: [install] Boot from install cd hangs on HP DL160 G5 with LSI SAS1064E Date: Sun, 05 Dec 2010 14:34:44 +0200 Is this still a problem for you? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/135040: [ata] FreeBSD/amd64 does not (always) detect disk on SB600/AliveXFire eSata 2
The following reply was made to PR amd64/135040; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, ralf.folke...@gmx.de, Alexander Motin Cc: Subject: Re: amd64/135040: [ata] FreeBSD/amd64 does not (always) detect disk on SB600/AliveXFire eSata 2 Date: Sun, 05 Dec 2010 14:31:01 +0200 What's the current status of this PR? Is it resolved or more work is still required? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/134978: [panic] g_up pmap amd64 panic
The following reply was made to PR amd64/134978; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, g...@wp.pl Cc: Subject: Re: amd64/134978: [panic] g_up pmap amd64 panic Date: Sun, 05 Dec 2010 14:28:41 +0200 Are still able to reproduce the problem? Some additional debugging information is required to analyze the problem. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/133977: [panic] [ffs] "panic: ffs_blkfree: freeing free block" after 7.0R->7.1R amd64 src upgrade [regression]
The following reply was made to PR amd64/133977; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, freebs...@sensation.net.au Cc: Subject: Re: amd64/133977: [panic] [ffs] "panic: ffs_blkfree: freeing free block" after 7.0R->7.1R amd64 src upgrade [regression] Date: Sun, 05 Dec 2010 14:26:05 +0200 Is still an issue? A panic like that usually indicates filesystem corruption. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/132574: [boot] [hang] Freeze on bootstrap loader (CD) using ATA/133 Promise FastTrak TX2000
The following reply was made to PR amd64/132574; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, mathieu.chappuis.li...@gmail.com Cc: Subject: Re: amd64/132574: [boot] [hang] Freeze on bootstrap loader (CD) using ATA/133 Promise FastTrak TX2000 Date: Sun, 05 Dec 2010 14:23:27 +0200 Is this a problem with newer releases? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/133701: Recompiling the kernel with k8temp or smbios break GEOM autodetection
The following reply was made to PR amd64/133701; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, d-...@dctech.net Cc: Subject: Re: amd64/133701: Recompiling the kernel with k8temp or smbios break GEOM autodetection Date: Sun, 05 Dec 2010 14:24:40 +0200 Problem description sounds quite weird. Will you be able to provide more details if you can still reproduce the problem? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/131456: ACPI & ATA problems
The following reply was made to PR amd64/131456; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, d...@rodemer.net Cc: Subject: Re: amd64/131456: ACPI & ATA problems Date: Sun, 05 Dec 2010 14:21:40 +0200 What's the status of these problems for you? Considering the followup of mav@ on the ATA issue. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/131314: [modules] [panic] large modules fail to load on amd64
The following reply was made to PR amd64/131314; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, k...@freebsd.org Cc: Subject: Re: amd64/131314: [modules] [panic] large modules fail to load on amd64 Date: Sun, 05 Dec 2010 14:19:07 +0200 Ken, this is an interesting problem. Are you able to reproduce it still? I think that something like that should be easily debuggable. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/131209: [panic] [bce] 7.1-STABLE amd64 crash - m0 NULL
The following reply was made to PR amd64/131209; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, roar.petter...@it.uib.no Cc: Subject: Re: amd64/131209: [panic] [bce] 7.1-STABLE amd64 crash - m0 NULL Date: Sun, 05 Dec 2010 14:17:15 +0200 Is this still an issue? Have you tried contacting davidch@ and/or discussing the bug on the appropriate mailing lists (net@, stable@)? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/130864: [hang] Problem with copying files to a large partition
The following reply was made to PR amd64/130864; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, vsj...@gmail.com Cc: Subject: Re: amd64/130864: [hang] Problem with copying files to a large partition Date: Sun, 05 Dec 2010 14:13:46 +0200 Are you still able to reproduce this? Will you be able to help with debugging? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/130368: [hang] Switching from xorg to console locks up computer
The following reply was made to PR amd64/130368; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, xxjack1...@gmail.com Cc: Subject: Re: amd64/130368: [hang] Switching from xorg to console locks up computer Date: Sun, 05 Dec 2010 14:05:23 +0200 Is this an issue? Looks like a possible problem with X server. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/129889: [boot] [hang] The booting process stops at the line mounting root ufs /dev/md0 (Starting with the option for no acpi )
The following reply was made to PR amd64/129889; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, c_to...@otenet.gr Cc: Subject: Re: amd64/129889: [boot] [hang] The booting process stops at the line mounting root ufs /dev/md0 (Starting with the option for no acpi ) Date: Sun, 05 Dec 2010 14:04:23 +0200 Is this still an issue? Why did you have ACPI disabled? This is not advisable with modern hardware. Were you trying to fix another issue? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/129667: [ata] Elitegroup A780GM-A IDE controller not recognized in 6.4 amd64
The following reply was made to PR amd64/129667; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, tom.be...@dailyevergreen.com Cc: Subject: Re: amd64/129667: [ata] Elitegroup A780GM-A IDE controller not recognized in 6.4 amd64 Date: Sun, 05 Dec 2010 14:01:39 +0200 Is this problem still the case? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/129426: [panic] FreeBSD 7.0 crash after subdiskXX: detached
The following reply was made to PR amd64/129426; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, p...@prolixium.com Cc: Subject: Re: amd64/129426: [panic] FreeBSD 7.0 crash after subdiskXX: detached Date: Sun, 05 Dec 2010 14:00:42 +0200 Is this still reproducible? Looks like possible hardware or ata driver issue. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/129315: [boot] [reboot] amd64 motherboard: Intel DG965WH motherboard compatibility with AMD64
The following reply was made to PR amd64/129315; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, r...@robertjbrown.com Cc: Subject: Re: amd64/129315: [boot] [reboot] amd64 motherboard: Intel DG965WH motherboard compatibility with AMD64 Date: Sun, 05 Dec 2010 13:58:11 +0200 Robert, are you still able to reproduce the issue? Can you try to use a CURRENT snapshot and possibly get a backtrace or any other messages before the reboot? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/128765: [install] Install CD loads to Install choices but stops & only reboots
The following reply was made to PR amd64/128765; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, serious...@gmail.com Cc: Subject: Re: amd64/128765: [install] Install CD loads to Install choices but stops & only reboots Date: Sun, 05 Dec 2010 13:45:06 +0200 Is still an issue? The report is old and description of the actual problem with FreeBSD/PC-BSD is quite vague. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/128263: [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 and 16gb ram, crash and dump mem
The following reply was made to PR amd64/128263; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, martin.wike...@cypoint.se Cc: Subject: Re: amd64/128263: [panic] 2 amd64 dl380 g5 with dual quadcore xeons, 8 and 16gb ram, crash and dump mem Date: Sun, 05 Dec 2010 13:17:57 +0200 Is this still an issue? Can it be reproduced with head or stable/8 (8.2 prerelease)? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/127451: [scheduler] incorrect load on quad core
The following reply was made to PR amd64/127451; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, m...@skynet.lv Cc: Subject: Re: amd64/127451: [scheduler] incorrect load on quad core Date: Sun, 05 Dec 2010 13:15:51 +0200 Is this still reproducible? What kind of processes are running when that happens? top -SPH output may be of help. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/125002: [install] amd64, SATA hard disks not detected
The following reply was made to PR amd64/125002; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, goodbits...@gmail.com Cc: Subject: Re: amd64/125002: [install] amd64, SATA hard disks not detected Date: Sun, 05 Dec 2010 13:11:09 +0200 Can the issue be still reproduced with the latest FreeBSD versions? ahci(4) driver may work better than the legacy ata driver in your case. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/124432: [panic] 7.0-STABLE panic: invalbuf: dirty bufs
The following reply was made to PR amd64/124432; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, j...@zircon.seattle.wa.us Cc: Subject: Re: amd64/124432: [panic] 7.0-STABLE panic: invalbuf: dirty bufs Date: Sun, 05 Dec 2010 13:09:36 +0200 Can you still reproduce the issue? P.S. it's better to report panics to the mailing lists, much greater chance of the report getting noticed and the problem getting fixed, especially when you have debug information handy. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/120202: [amd64] [patch] [panic] kernel panic at start_all_aps, AP not starts
The following reply was made to PR amd64/120202; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, masa...@mbs.sphere.ne.jp Cc: Subject: Re: amd64/120202: [amd64] [patch] [panic] kernel panic at start_all_aps, AP not starts Date: Sun, 05 Dec 2010 12:45:21 +0200 Is this still an issue with the recent (and unpatched) versions of FreeBSD? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/116620: [hang] ifconfig spins when creating carp(4) device on amd64/SMP
The following reply was made to PR amd64/116620; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, muffal...@gmail.com Cc: Subject: Re: amd64/116620: [hang] ifconfig spins when creating carp(4) device on amd64/SMP Date: Sun, 05 Dec 2010 12:09:19 +0200 Is this still an issue with the latest versions of FreeBSD? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/117296: [ata] I don`t see second SATA IDE on VIA VT8237A
The following reply was made to PR amd64/117296; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, msnk...@mail.ru Cc: Subject: Re: amd64/117296: [ata] I don`t see second SATA IDE on VIA VT8237A Date: Sun, 05 Dec 2010 12:11:10 +0200 Is this still an issue with the latest versions of FreeBSD? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/115815: [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupported SATA
The following reply was made to PR amd64/115815; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, al...@zwingelstein.org Cc: Subject: Re: amd64/115815: [ata] [request] Gigabyte GA-M61P-S3 Motherboard unsupported SATA Date: Sun, 05 Dec 2010 12:08:24 +0200 Alain, is this still an issue with recent supported FreeBSD versions? If yes, can you provide pciconf -lv output? P.S. it might be a better idea to report issues like this on current@ or stable@ mailing lists - more chances for it to get noticed. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/115194: LCD screen remains blank after Dell XPS M1210 lid is closed and reopened.
The following reply was made to PR amd64/115194; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, an...@pcbsd.org Cc: Subject: Re: amd64/115194: LCD screen remains blank after Dell XPS M1210 lid is closed and reopened. Date: Sun, 05 Dec 2010 12:05:26 +0200 Andrei, is this still an issue with recent revisions of head or stable/8? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/108861: [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC
The following reply was made to PR amd64/108861; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, lstew...@room52.net Cc: Subject: Re: amd64/108861: [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work at 1Gbps with nForce4 NIC Date: Sun, 05 Dec 2010 12:01:48 +0200 Lawrence, how do you feel about this PR? Did David's suggestion work for you? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/91405: [asr] [panic] Kernel panic caused by asr on 6.0-amd64 box
The following reply was made to PR amd64/91405; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, freebsd-s...@freebsd.org Cc: Subject: Re: amd64/91405: [asr] [panic] Kernel panic caused by asr on 6.0-amd64 box Date: Sun, 05 Dec 2010 11:53:47 +0200 http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/91405 I wonder if this issue has been fixed or if asr(4) on amd64 is completely abandoned now. Maybe there is an alternative driver. Just want to see what can be done with this PR. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/97337: [dri] xorg reboots system if dri module is enabled
The following reply was made to PR amd64/97337; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, jtrcerr...@web.de Cc: Subject: Re: amd64/97337: [dri] xorg reboots system if dri module is enabled Date: Sat, 27 Nov 2010 10:41:07 +0200 Is this still an issue with currently supported versions of FreeBSD? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/95888: [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP DL140G2
The following reply was made to PR amd64/95888; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, te...@kgs.ru Cc: Subject: Re: amd64/95888: [ata] kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP DL140G2 Date: Sat, 27 Nov 2010 10:40:15 +0200 Is still still an issue? Have you determined the cause of those timeout? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/78406: [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and system crashes
The following reply was made to PR amd64/78406; it has been noted by GNATS. From: Andriy Gapon To: bug-follo...@freebsd.org, r...@redshift.com Cc: Subject: Re: amd64/78406: [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and system crashes Date: Sat, 27 Nov 2010 10:34:10 +0200 Is this an issue? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/152405: wrong user time is reported when CPU frequency throttled.
The following reply was made to PR amd64/152405; it has been noted by GNATS. From: Andriy Gapon To: =?UTF-8?B?IktPSUUgSGlkZXRha2EgKOmvieaxn+iLsemahu+8oOaVsOeQhuaKgOeglCki?= Cc: bug-follo...@freebsd.org Subject: Re: amd64/152405: wrong user time is reported when CPU frequency throttled. Date: Wed, 24 Nov 2010 16:19:24 +0200 on 24/11/2010 15:54 Andriy Gapon said the following: > Anyway, it seems that I missed the real cause of this problem and the > excellent > explanation by Bruce. Could you please try the following (work-in-progress) patch? http://people.freebsd.org/~avg/tsc-cpu_ticks.diff I expect that it should improve accuracy for your testcase, but may penalize system performance to certain degree. As mav@ has said, performance, accuracy, powerstate management - pick any two of the three. OTOH, I am not sure by how much the performance could be affected. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/152405: wrong user time is reported when CPU frequency throttled.
The following reply was made to PR amd64/152405; it has been noted by GNATS. From: Andriy Gapon To: =?UTF-8?B?IktPSUUgSGlkZXRha2EgKOmvieaxn+iLsemahu+8oOaVsOeQhuaKgOeglCki?= Cc: bug-follo...@freebsd.org Subject: Re: amd64/152405: wrong user time is reported when CPU frequency throttled. Date: Wed, 24 Nov 2010 15:54:19 +0200 on 24/11/2010 14:33 KOIE Hidetaka (é¯æ±è±éï¼ æ°çæç ) said the following: > | Can you try to boot with kern.eventtimer.timer="i8254" in loader.conf? > > Boot process hangs up. (I tried 2 times) Oh, hm, very strange. Not sure why that happens. Anyway, it seems that I missed the real cause of this problem and the excellent explanation by Bruce. Your CPU doesn't have invariant TSC and (x86) FreeBSD doesn't handle that correctly for some things like e.g. CPU time accounting that you are reporting about. This is not a problem for modern hardware which almost universally supports invariant TSC, but older models are affected. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/152405: wrong user time is reported when CPU frequency throttled.
The following reply was made to PR amd64/152405; it has been noted by GNATS.
From: Andriy Gapon
To: =?ISO-2022-JP?B?IktPSUUgSGlkZXRha2EgKBskQjhxOT4xUU40IXc/dE19NTs4JhsoQg==?=
=?ISO-2022-JP?B?KSI=?=
Cc: bug-follo...@freebsd.org
Subject: Re: amd64/152405: wrong user time is reported when CPU frequency
throttled.
Date: Wed, 24 Nov 2010 11:31:38 +0200
on 24/11/2010 09:17 KOIE Hidetaka ($B8q9>1QN4!w?tM}5;8&(B) said the
following:
> % sudo sysctl kern.eventtimer.timer="i8254"
> Password:
> kern.eventtimer.timer: LAPIC -> i8254
> % sudo sysctl dev.cpu.0.freq=1800
> dev.cpu.0.freq: 1800 -> 1800
> % time ./loop
>
> 0.000u 4.773s 0:00.08 5962.5% 0+0k 0+0io 0pf+0w
> % sudo sysctl dev.cpu.0.freq=1000
> dev.cpu.0.freq: 1800 -> 1000
> % time ./loop
>
> 0.000u 4.773s 0:00.21 2271.4% 0+0k 0+0io 0pf+0w
> % sleep 1
> ("sleep" had returned after sysctl kern.eventtimer.timer="LAPIC" on
> another terminal)
> %
>
> NOTE: user time is 0, system time is too long, and elapsed time is too short.
>
> And, wall-clock has been slow...
> % ssh my-server date ; env LANG=C date
> Wed Nov 24 16:03:11 JST 2010
> Wed Nov 24 16:01:15 JST 2010
Can you try to boot with kern.eventtimer.timer="i8254" in loader.conf?
--
Andriy Gapon
___
freebsd-amd64@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/152405: wrong user time is reported when CPU frequency throttled.
The following reply was made to PR amd64/152405; it has been noted by GNATS. From: Andriy Gapon To: =?ISO-2022-JP?B?IktPSUUgSGlkZXRha2EgKBskQjhxOT4xUU40IXc/dE19NTs4JhsoQg==?= =?ISO-2022-JP?B?KSI=?= Cc: bug-follo...@freebsd.org Subject: Re: amd64/152405: wrong user time is reported when CPU frequency throttled. Date: Wed, 24 Nov 2010 08:56:26 +0200 on 24/11/2010 08:54 KOIE Hidetaka ($B8q9>1QN4!w?tM}5;8&(B) said the following: > Message-Id: <4cebe965.5050...@freebsd.org> > Date: Tue, 23 Nov 2010 18:18:45 +0200 > From: Andriy Gapon > Subject:Re: amd64/152405: wrong user time is reported when CPU f.. > > | on 23/11/2010 17:15 KOIE Hidetaka ($B8q9>1QN4!w?tM}5;8&(B) said the > following: > | > I send sysctl kern.timecounter and /var/run/dmesg.boot. > | > | Could you please additionally provide output of sysctl dev.cpu and > sysctl machdep? > > output of sysctl dev.cpu machdep is attached. > > | Meanwhile, please also try your test-case after having set the following > sysctl > | kern.eventtimer.choice="i8254". > > sysctl kern.eventtimer.choice="i8254" fails. Many apologies, this should have been kern.eventtimer.timer="i8254". Could you please try that? -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
Re: amd64/152405: wrong user time is reported when CPU frequency throttled.
The following reply was made to PR amd64/152405; it has been noted by GNATS. From: Andriy Gapon To: =?UTF-8?B?IktPSUUgSGlkZXRha2EgKOmvieaxn+iLsemahu+8oOaVsOeQhuaKgOeglCki?= Cc: bug-follo...@freebsd.org Subject: Re: amd64/152405: wrong user time is reported when CPU frequency throttled. Date: Tue, 23 Nov 2010 18:18:45 +0200 on 23/11/2010 17:15 KOIE Hidetaka (é¯æ±è±éï¼ æ°çæç ) said the following: > I send sysctl kern.timecounter and /var/run/dmesg.boot. Could you please additionally provide output of sysctl dev.cpu and sysctl machdep? Meanwhile, please also try your test-case after having set the following sysctl kern.eventtimer.choice="i8254". Thank you. -- Andriy Gapon ___ freebsd-amd64@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to "freebsd-amd64-unsubscr...@freebsd.org"
