Re: freebsd on Intel s5000pal - kernel reboots the system

[Eugene M. Zheganin]

Hi.

On 18.04.2017 14:44, Konstantin Belousov wrote:

You did not provide any information about your issue. It is not known
even whether the loader breaks for you, or a kernel starts booting and
failing.

Ideally, you would use serial console and provide the log of everything
printed on it, before the reboot.

What kind of boot do you use, legacy BIOS or EFI ?  What version of
FreeBSD ?
Oh, yeah, I'm sorry. Nah, loader is fine, the server reboots when the 
kernel itself is initializing the devices. It starts initializing 
various PCI stuff, then reboots. I'm aware about serial console, but, 
unfortunately, this server has some proprietary RS-232 jack, in the 
form-factor of 8P8C, and the only cable I have with these jacks is Cisco 
"blue" cable, but seems like they use different pin-out scheme. Thus, so 
far, no serial console, but I'm working on it. The FreeBSD version I've 
tried to use is the 11-RELEASE amd64.


Thanks.
Eugene.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: USB problems after r316423 (LLVM-4.0)

[Philipp-Joachim Ost]

Kevin Oberman wrote:
> USB on my system (Lenovo T520-Cougar Point chipset) fails to initialize. I
> have reported this in
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218513
> 
> Can others running 11-STABLE at or after r316423 confirm the operation of
> USB ports? It seems unlikely that I am the only one seeing this as my
> system is pretty vanilla, but I have seen no other reports.
> 
> If you have such a system, can you either confirm that USB is working or
> test by plugging in any USB device and seeing if it shows up or check
> /var/run/dmesg for the errors reported in the ticket?

I'm running 11-STABLE r317090 and USB devices work just fine (keyboard,
mouse, memory sticks). I don't see the errors reported in your bug
report, either.

Not sure if it matters, but my system has an AMD/ATI chipset.
pciconf -lv reports the following:
...
ehci0@pci0:0:18:2:  class=0x0c0320 card=0x83891043 chip=0x43961002
rev=0x00
hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]'
device = 'SB7x0/SB8x0/SB9x0 USB EHCI Controller'
class  = serial bus
subclass   = USB
...

Philipp



smime.p7s
Description: S/MIME Cryptographic Signature

USB problems after r316423 (LLVM-4.0)

[Kevin Oberman]

USB on my system (Lenovo T520-Cougar Point chipset) fails to initialize. I
have reported this in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218513

Can others running 11-STABLE at or after r316423 confirm the operation of
USB ports? It seems unlikely that I am the only one seeing this as my
system is pretty vanilla, but I have seen no other reports.

If you have such a system, can you either confirm that USB is working or
test by plugging in any USB device and seeing if it shows up or check
/var/run/dmesg for the errors reported in the ticket?

I am running GENERIC except for SCHED_4BSD. (I tried SCHED_ULE with no
change.)
CPU: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz (2491.97-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206a7  Family=0x6  Model=0x2a  Stepping=7
Other details are in the ticket.

Thanks so much.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 10.3-stable random server reboots - finding the reason

[tech-lists]

On 18/04/2017 17:49, Steven Hartland wrote:
> It's not an external vulnerability in the DRAC is it as that seems to be
> more and more common these days

It was wrapped to one of my static IPs, unless that can somehow be
compromised. From what the engineer says, it's a hardware failure of the
DRAC. Maybe what's needed is for it to be powered off, unplugged, while
unplugged to press power on to drain it of 'flea voltage' as Ive heard
it put, wait a minute then power it up again
-- 
J.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 10.3-stable random server reboots - finding the reason

[Steven Hartland]

It's not an external vulnerability in the DRAC is it as that seems to be
more and more common these days
On Tue, 18 Apr 2017 at 15:10, tech-lists  wrote:

> On 18/04/2017 13:34, Kurt Jaeger wrote:
>
> > 1)
> > echo '-Dh -S115200' > /boot.config
> > 2)
> > vi /boot/loader.conf
> > 
> > console="comconsole"
> > comconsole_speed=115200
> > 
> >
> > Then: connect it to some kermit session from a different box,
> > and write a session log. This might capture some last gasp.
> >
>
> A bit more detail:
>
> Problem seems to be it's DRAC is broken. The server is a Dell R710 in a
> datacentre so I've not got physical access. I'd normally admin the
> hardware via the DRAC but it's non-functional now.
>
> The system won't boot without someone there plugging in a keyboard and
> pressing F2 to continue... arrrgh! "idrac failed press F2". It does
> boot, though. The DRAC normally shows fan speed and voltage amongst
> other things. Right now I'm looking for an in-band method of doing that
> on FreeBSD as obv the out-of-band method has failed. cpu temps look
> fine, cool.
>
> AIUI the DRAC is a chip on the motherboard and not a module that can be
> whipped out and replaced. For all I know, the DRAC might be causing the
> reboot if it's only intermittently dead. I don't know this though. It
> might be CPU or RAM, both of these can be swapped out, just need to
> capture the info...
>
> arrgh!
> --
> J.
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 10.3-stable random server reboots - finding the reason

[tech-lists]

On 18/04/2017 13:34, Kurt Jaeger wrote:

> 1)
> echo '-Dh -S115200' > /boot.config
> 2)
> vi /boot/loader.conf
> 
> console="comconsole"
> comconsole_speed=115200
> 
> 
> Then: connect it to some kermit session from a different box,
> and write a session log. This might capture some last gasp.
> 

A bit more detail:

Problem seems to be it's DRAC is broken. The server is a Dell R710 in a
datacentre so I've not got physical access. I'd normally admin the
hardware via the DRAC but it's non-functional now.

The system won't boot without someone there plugging in a keyboard and
pressing F2 to continue... arrrgh! "idrac failed press F2". It does
boot, though. The DRAC normally shows fan speed and voltage amongst
other things. Right now I'm looking for an in-band method of doing that
on FreeBSD as obv the out-of-band method has failed. cpu temps look
fine, cool.

AIUI the DRAC is a chip on the motherboard and not a module that can be
whipped out and replaced. For all I know, the DRAC might be causing the
reboot if it's only intermittently dead. I don't know this though. It
might be CPU or RAM, both of these can be swapped out, just need to
capture the info...

arrgh!
-- 
J.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 10.3-stable random server reboots - finding the reason

[Bernt Hansson]

On 2017-04-18 13:59, tech-lists wrote:

Hello stable@

I have an up-to-date 10.3 server that is randomly rebooting, after being
up for days. Previously it had been up for many months. The problem is,
nothing seems to be left in the logs to indicate why it's doing this. I
have all.log and console.log enabled.

So, what I'm asking is, how can I capture its last gasp?

many thanks,

That sounds very much like a hardware issue.
Capacitors, memory is what i would check.

Those errors won't be logged.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 10.3-stable random server reboots - finding the reason

[Kurt Jaeger]

> Hello stable@
> 
> I have an up-to-date 10.3 server that is randomly rebooting, after being
> up for days. Previously it had been up for many months. The problem is,
> nothing seems to be left in the logs to indicate why it's doing this. I
> have all.log and console.log enabled.
> 
> So, what I'm asking is, how can I capture its last gasp?

Do you have a serial port on that server ? Use it as a console port:

1)
echo '-Dh -S115200' > /boot.config
2)
vi /boot/loader.conf

console="comconsole"
comconsole_speed=115200


Then: connect it to some kermit session from a different box,
and write a session log. This might capture some last gasp.

-- 
p...@opsec.eu+49 171 3101372 3 years to go !
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Unsupported USB BT device causes high interrupt load

[Dominic Fandrey]

> I have an Interrupt load of 2000 interrupts/s from xhci0.
> 
> As the culprit I have identified the following device:
> 
> ugen0.6:  at usbus0, cfg=255 md=HOST spd=FULL 
> (12Mbps) pwr=ON (100mA)
> 
> …

The device spamms me with interrupts after every boot and resume
until I send it a power_off command.

For anyone else with a similar problem, I'm using the following devd
rule to mitigate the issue (https://pastebin.com/raw/HmDur3Le):

notify 100 {
match "system"  "USB";
match "subsystem"   "INTERFACE";
match "type""ATTACH";
match "vendor"  "0x8087";
match "product" "0x07dc";
action "usbconfig -d $cdev power_off";
};

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail? 



pgp4T6dJTSgtT.pgp
Description: PGP signature

Re: 10.3-stable random server reboots - finding the reason

[Eugene Grosbein]

On 18.04.2017 18:59, tech-lists wrote:
> Hello stable@
> 
> I have an up-to-date 10.3 server that is randomly rebooting, after being
> up for days. Previously it had been up for many months. The problem is,
> nothing seems to be left in the logs to indicate why it's doing this. I
> have all.log and console.log enabled.
> 
> So, what I'm asking is, how can I capture its last gasp?

Start with reading the Handbook on kernel debugging procedure.
You will need to enable crashdump generation and perhaps rebuild kernel
with debugging options enabled (INVARIANTS, WITNESS etc.)


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

10.3-stable random server reboots - finding the reason

[tech-lists]

Hello stable@

I have an up-to-date 10.3 server that is randomly rebooting, after being
up for days. Previously it had been up for many months. The problem is,
nothing seems to be left in the logs to indicate why it's doing this. I
have all.log and console.log enabled.

So, what I'm asking is, how can I capture its last gasp?

many thanks,
-- 
J.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: freebsd on Intel s5000pal - kernel reboots the system

[Konstantin Belousov]

On Tue, Apr 18, 2017 at 01:28:33PM +0500, Eugene M. Zheganin wrote:
> Hi,
> 
> 
> I need to install FreBSD on an Intel system with s5000pal mainboard. The 
> problem is, that on the kernel loading stage, FreeBSD reboots the 
> server. Like, always and silently, without trapping. I have plugged out 
> all of the discrete PCI controllers, leaving only onboard ones. Still 
> reboots. I was suspecting this is some kind of hardware problem, so I 
> ran the memtest (no errors for two hours) and I've even switched the 
> server (I have two identical ones). New server reboots too. So, looks 
> like it's some kind of FreeBSD issue. I've updated the BIOS on both, 
> tried to boot without ACPI - and this doesn't help (and without ACPI 
> FreeBSD refuses to even start to load kernel).
You did not provide any information about your issue. It is not known
even whether the loader breaks for you, or a kernel starts booting and
failing.

Ideally, you would use serial console and provide the log of everything
printed on it, before the reboot.

What kind of boot do you use, legacy BIOS or EFI ?  What version of
FreeBSD ?

> 
> 
> So I'll really appreciate any ideas on how to solve this. I tried to 
> boot CentOS - it boots just fine. I've alsp tried to play with various 
> BIOS settings, but this makes no difference at all. From what I see 
> FreeBSD reboots the server during the PCI initialization.
> 
> 
> Thanks.
> 
> Eugene.
> 
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

freebsd on Intel s5000pal - kernel reboots the system

[Eugene M. Zheganin]

Hi,


I need to install FreBSD on an Intel system with s5000pal mainboard. The 
problem is, that on the kernel loading stage, FreeBSD reboots the 
server. Like, always and silently, without trapping. I have plugged out 
all of the discrete PCI controllers, leaving only onboard ones. Still 
reboots. I was suspecting this is some kind of hardware problem, so I 
ran the memtest (no errors for two hours) and I've even switched the 
server (I have two identical ones). New server reboots too. So, looks 
like it's some kind of FreeBSD issue. I've updated the BIOS on both, 
tried to boot without ACPI - and this doesn't help (and without ACPI 
FreeBSD refuses to even start to load kernel).



So I'll really appreciate any ideas on how to solve this. I tried to 
boot CentOS - it boots just fine. I've alsp tried to play with various 
BIOS settings, but this makes no difference at all. From what I see 
FreeBSD reboots the server during the PCI initialization.



Thanks.

Eugene.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"