Re: panic on shutdown
I did a couple of reboots and the problem seems to be gone. Thank you, for the quick fix. Regards Stefan >Can you try the attached patch ? -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Re: panic on shutdown
> Can you try the attached patch ? yes, currently building a new kernel and doing some tests. Thank you, for your quick reply!
panic on shutdown
Hello, most of the time current panics on shutdown. Should i file a bug report? thanks Stefan [ 125193,164748] syncing disks... done [ 125193,224761] unmounted procfs on /proc type procfs [ 125193,244769] unmounted ptyfs on /dev/pts type ptyfs [ 125193,264777] unmounted kernfs on /kern type kernfs [ 125193,714946] cd0: detached [ 125193,714946] makphy0: detached [ 125193,714946] msk0: detached [ 125193,714946] atapibus0: detached [ 125194,285160] wd1: detached [ 125194,795352] wd0: detached [ 125194,795352] uhub7: detached [ 125194,795352] uhub5: detached [ 125194,795352] uhub4: detached [ 125194,795352] uhub3: detached [ 125194,795352] uhub2: detached [ 125194,795352] uhub1: detached [ 125194,795352] uhub0: detached [ 125194,795352] fatal page fault in supervisor mode [ 125194,795352] trap type 6 code 0 rip 0x803db031 cs 0x8 rflags 0x10292 cr2 0x8554 ilevel 0x6 rsp 0xcc00ae9e5df8 [ 125194,795352] curlwp 0xf38c495f9860 pid 0.5 lowest kstack 0xcc00ae9e22c0 [ 125194,795352] dumping to dev 0,33 (offset=3688, size=2096927): [ 125194,795352] dump 0x80222d75 in cpu_reboot () (gdb) bt #0 0x80222d75 in cpu_reboot () #1 0x8076f4f8 in db_sync_cmd () #2 0x8076fcf2 in db_command () #3 0x8077006c in db_command_loop () #4 0x807739e0 in db_trap () #5 0x8021f5c2 in kdb_trap () #6 0x802244b1 in trap () #7 0x8021d568 in alltraps () #8 0x803db031 in msk_rxeof () #9 0x803db840 in msk_intr () #10 0x8023f0f9 in intr_biglock_wrapper () #11 0x8020d216 in Xhandle_ioapic_edge18 () #12 0x8021dee0 in ?? () #13 0x8098b478 in _kernel_lock () #14 0x809b712a in callout_softclock () #15 0x809ab165 in softint_dispatch () #16 0x8021d21f in Xsoftintr ()
8.99.12 hang
Hello, i have those hang's too. For me current, 8, 7.1.1 is affected, 7.0.2 doesn't hang. I could break into the debugger and reboot. The hangs appear even when the laptop is idle mostly after a couple of minutes, sometimes it take longer up to a couple of hours. regards Stefan
Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40000001 tfd 0x2051
Am 10. November 2017 14:16:51 MEZ schrieb Martin Husemann: >On Fri, Nov 10, 2017 at 02:11:12PM +0100, Jaromír Dole?ek wrote: >> The TFD 0x2051 corresponds to Media Changed error, with DRDY/ERR >status >> bits. Is it possible this message appears every time you change media >in >> the cd0? >> >> Alternatively, I imagine this could be generated if the drive is >setup to >> hibernate/suspend. > >For me it happens w/o any medium and never touching the drive. > >Martin For me too, starts while booting w/o interaction from me. Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
Re: dmesg spam: ahcisata0 port 1: active 2 is 0x40000001 tfd 0x2051
Am Fri, 10 Nov 2017 18:43:19 +0100 schrieb Jaromír Doleček: > TFES usually means an unsupported command was sent to the device, or a > command was sent while previous was finished. > > Could you please try to figure out what is the command sent to the cd0 > device just before that error? It should be possible to turn the debug > messages on via the ahcdebug_mask variable in ddb, set it to > DEBUG_XFERS (0x02). Hope this helps ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 32768 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 16384 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 16384 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 32768 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 32768 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 16384 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 16384 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 32768 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 32768 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 16384 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 16384 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 32768 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 32768 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 16384 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 16384 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 32768 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 32768 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 16384 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 16384 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 32768 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 32768 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 16384 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 16384 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 32768 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 32768 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 16384 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0 port 0 tbl 0x80008e021200 ahcisata0 port 0 header 0x80008e01f020 ahci_bio_complete bcount 16384 now 0 ahci_ata_bio port 0 CI 0x0 ahci_bio_start CI 0x0 ahcisata0
dmesg spam: ahcisata0 port 1: active 2 is 0x40000001 tfd 0x2051
Since some time i get a lot of dmesg spam ... ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ... regards Stefan ve 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0 port 1: active 2 is 0x4001 tfd 0x2051 ahcisata0
Re: current panics with urtwn0
Spam detection software, running on the system "vbsd.hertenberger.bayern", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see postmaster for details. Content preview: Am Mon, 23 Jan 2017 20:42:32 + (UTC) schrieb chris...@astron.com (Christos Zoulas): > Looks like it should have already been fixed. > > christos > Sorry for the noise, after a cleaning the obj dir and rebuilding, the panic is gone. [...] Content analysis details: (6.1 points, 5.0 required) pts rule name description -- -- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: astron.com] 3.6 RCVD_IN_PBLRBL: Received via a relay in Spamhaus PBL [80.128.179.157 listed in zen.spamhaus.org] 0.9 SPF_FAIL SPF: sender does not match SPF record (fail) [SPF failed: Please see http://www.openspf.org/Why?s=mfrom;id=stefan%40hertenberger.bayern;ip=80.128.179.157;r=vbsd.hertenberger.bayern] 1.6 RCVD_IN_BRBL_LASTEXT RBL: No description available. [80.128.179.157 listed in bb.barracudacentral.org] --- Begin Message --- Am Mon, 23 Jan 2017 20:42:32 + (UTC) schrieb chris...@astron.com (Christos Zoulas): > Looks like it should have already been fixed. > > christos > Sorry for the noise, after a cleaning the obj dir and rebuilding, the panic is gone. thx Stefan --- End Message ---
current panics with urtwn0
Spam detection software, running on the system "vbsd.hertenberger.bayern", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see postmaster for details. Content preview: hello, latest current panics when my usb wireless device is attached. i made a screenshot of the stack trace => https://www.alarum.de/netbsd/20170123_205754.jpg urtwn0 at uhub4 port 4 urtwn0: Realtek 802.11n WLAN Adapter, rev 2.00/2.00, addr 4 urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R, address 74:da:38:88:7c:ad urtwn0: 1 rx pipe, 2 tx pipes urtwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps urtwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps [...] Content analysis details: (6.1 points, 5.0 required) pts rule name description -- -- 0.9 SPF_FAIL SPF: sender does not match SPF record (fail) [SPF failed: Please see http://www.openspf.org/Why?s=mfrom;id=stefan%40hertenberger.bayern;ip=80.128.179.157;r=vbsd.hertenberger.bayern] 3.6 RCVD_IN_PBLRBL: Received via a relay in Spamhaus PBL [80.128.179.157 listed in zen.spamhaus.org] 1.6 RCVD_IN_BRBL_LASTEXT RBL: No description available. [80.128.179.157 listed in bb.barracudacentral.org] 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: alarum.de] --- Begin Message --- hello, latest current panics when my usb wireless device is attached. i made a screenshot of the stack trace => https://www.alarum.de/netbsd/20170123_205754.jpg urtwn0 at uhub4 port 4 urtwn0: Realtek 802.11n WLAN Adapter, rev 2.00/2.00, addr 4 urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R, address 74:da:38:88:7c:ad urtwn0: 1 rx pipe, 2 tx pipes urtwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps urtwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps --- End Message ---
Re: Beagleboard C4 problems
Am Tue, 11 Oct 2016 17:49:30 +0900 (JST) schrieb KIYOHARA Takashi: > Or do you have access to the Linux source? In this case .dts file is > want. i guese you mean this https://github.com/torvalds/linux/blob/b66484cd74706fa8681d051840fe4b18a3da40ff/arch/arm/boot/dts/omap3-beagle.dts
Re: Beagleboard C4 problems
Am Tue, 11 Oct 2016 17:49:30 +0900 (JST) schrieb KIYOHARA Takashi <kiyoh...@kk.iij4u.or.jp>: > Does your beagleboard can handle the device other than the wireless > key? For example, the storage device. i get the error messages while booting and the usb port seems to be dead. ld0 at sdmmc0: <0x03:0x5344:SU08G:0x80:0xb05e36af:0x0b2> ld0: 7580 MB, 3850 cyl, 64 head, 63 sec, 512 bytes/sect x 15523840 sectors ld0: 4-bit width, 25.000 MHz ehci_sync_hc: timed out ehci_sync_hc: timed out ... ehci_sync_hc: timed out ehci_sync_hc: timed out uhub0: device problem, disabling port 2 > > Do you have a Linux of the image you want to work? > I'm want .dtb files that exist under /boot in image. > Or do you have access to the Linux source? In this case .dts file is > want. > No, i don't use Linux. I found some Demo files here http://downloads.angstrom-distribution.org/demo/beagleboard/ but there is no .dtb file in /boot Kind regards Stefan Hertenberger
Beagleboard C4 problems
Hello, i have still problems with my beagleboard, with the image from 2016/10/10 the previous error is gone, so nomore timeouts sdhc0: timeout waiting for mask 0x400 value 0x400 (state=0x1e70106) sdhc0: timeout waiting for mask 0x3 value 0 (state=0x1e70506) sdhc0: command or data phase inhibited but now my usb wireless key isn't detected anymore ehci_sync_hc: timed out ehci_sync_hc: timed out is all i get and after a couple of minutes the system crashes and reboots panic: kernel diagnostic assertion "l2b != NULL" failed: file "/usr/src/sys/arch/arm/arm32/pmap.c", line 3685 va 0xc8a58000 pa 0xb8642000 prot 1 maxkvaddr 0xcb60: l 2 0xc007c310 l2b 0xc007c38c kva 0x0 cpu0: Begin traceback... 0xbfc9dad4: netbsd:db_panic+0xc 0xbfc9daec: netbsd:vpanic+0x174 0xbfc9db04: netbsd:__udivmoddi4 0xbfc9db74: netbsd:pmap_kenter_pa+0x39c 0xbfc9dbdc: netbsd:uvm_pagermapin+0x1a4 0xbfc9dc1c: netbsd:genfs_gop_write+0x38 0xbfc9ddac: netbsd:genfs_do_putpages+0x878 0xbfc9ddd4: netbsd:genfs_putpages+0x38 0xbfc9de0c: netbsd:VOP_PUTPAGES+0x4c 0xbfc9de3c: netbsd:vflushbuf+0x4c 0xbfc9de7c: netbsd:ffs_full_fsync+0x190 0xbfc9df0c: netbsd:ffs_fsync+0x50 0xbfc9df4c: netbsd:VOP_FSYNC+0x50 0xbfc9dfac: netbsd:sched_sync+0x20c cpu0: End traceback... regards Stefan
Fwd: Re: drmkms panic
Ursprüngliche Nachricht Von: Stefan Hertenberger <stefan@hertenberger.bayern> Gesendet: 5. August 2016 22:46:31 MESZ An: co...@sdf.org Betreff: Re: drmkms panic Am , schrieb co...@sdf.org: > > > The problem is pretty obvious. netbsd kmem_alloc doesn't like > allocating > zero-sized things, whereas linux kmalloc does. > > Now for patching the code to return a sane value provided a zero > size... i did a bit of testing and add a little patch, Index: dist/drm/drm_gem.c === RCS file: /cvsroot/src/sys/external/bsd/drm2/dist/drm/drm_gem.c,v retrieving revision 1.5 diff -u -r1.5 drm_gem.c --- dist/drm/drm_gem.c 18 Aug 2014 01:21:03 - 1.5 +++ dist/drm/drm_gem.c 5 Aug 2016 20:45:48 - @@ -154,6 +154,7 @@ drm_gem_private_object_init(dev, obj, size); #ifdef __NetBSD__ + if (size == 0) return 0; obj->gemo_shm_uao = uao_create(size, 0); /* * XXX This is gross. We ought to do it the other way around: this doesn't fix the the issue but the panic is gone and now i get DRM error in radeon_gem_object_create: Failed to allocate GEM object (0, 6, 4096, -22) Illegal buffer object size Illegal buffer object size DRM error in radeon_gem_object_create: Failed to allocate GEM object (0, 6, 4096, -22) Illegal buffer object size Illegal buffer object size DRM error in radeon_gem_object_create: Failed to allocate GEM object (0, 6, 4096, -22) Illegal buffer object size Illegal buffer object size DRM error in radeon_gem_object_create: Failed to allocate GEM object (0, 6, 4096, -22) Illegal buffer object size Illegal buffer object size DRM error in radeon_gem_object_create: Failed to allocate GEM object (0, 6, 4096, -22) Illegal buffer object size Illegal buffer object size DRM error in radeon_gem_object_create: Failed to allocate GEM object (0, 6, 4096, -22) Illegal buffer object size Illegal buffer object size DRM error in radeon_gem_object_create: Failed to allocate GEM object (0, 6, 4096, -22) Illegal buffer object size Illegal buffer object size DRM error in radeon_gem_object_create: Failed to allocate GEM object (0, 6, 4096, -22) Illegal buffer object size Illegal buffer object size DRM error in radeon_gem_object_create: Failed to allocate GEM object (0, 6, 4096, -22) Illegal buffer object size Illegal buffer object size DRM error in radeon_gem_object_create: Failed to allocate GEM object (0, 6, 4096, -22) Illegal buffer object size Illegal buffer object size DRM error in radeon_gem_object_create: Failed to allocate GEM object (0, 6, 4096, -22) Illegal buffer object size Illegal buffer object size DRM error in radeon_gem_object_create: Failed to allocate GEM object (0, 6, 4096, -22) Illegal buffer object size Illegal buffer object size DRM error in radeon_gem_object_create: Failed to allocate GEM object (0, 6, 4096, -22) -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
drmkms panic
Hello, i hope this dump's are more useful, latest sources compiled with debug symbols. https://www.alarum.de/netbsd/netbsd.2.gz https://www.alarum.de/netbsd/netbsd.2.core.gz the kernel with debug symbols, not sure this is needed https://www.alarum.de/netbsd/netbsd.gdb.gz regards, Stefan Hertenberger
drmkms panic
Hello, when i try to start graphics/blender from pkgsrc my system panics. I use a radeon hd 7650 and modular xorg. the crash dumps are available here: www.alarum.de/netbsd/netbsd.0.gz www.alarum.de/netbsd/netbsd.0.core.gz i am not subscribed to the mailing list, please cc me. bsd64$ uname -a NetBSD bsd64 7.99.34 NetBSD 7.99.34 (GENERIC.201607310950Z) amd64 bsd64$ dmesg|grep radeon radeon0 at pci1 dev 0 function 0: vendor 1002 product 679a (rev. 0x00) radeon0: info: VRAM: 3072M 0x - 0xBFFF (3072M used) radeon0: info: GTT: 1024M 0xC000 - 0x drm: radeon: 3072M of VRAM memory ready drm: radeon: 1024M of GTT memory ready. drm: radeon/TAHITI_mc2.bin: 31232 bytes drm: radeon: dpm initialized radeon0: info: WB enabled radeon0: info: fence driver on ring 0 use gpu addr 0xcc00 and cpu addr 0x0x80004a216c00 radeon0: info: fence driver on ring 1 use gpu addr 0xcc04 and cpu addr 0x0x80004a216c04 radeon0: info: fence driver on ring 2 use gpu addr 0xcc08 and cpu addr 0x0x80004a216c08 radeon0: info: fence driver on ring 3 use gpu addr 0xcc0c and cpu addr 0x0x80004a216c0c radeon0: info: fence driver on ring 4 use gpu addr 0xcc10 and cpu addr 0x0x80004a216c10 radeon0: info: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x0x800049e15a18 radeon0: interrupting at ioapic0 pin 16 (radeon) drm: radeon: irq initialized. radeondrmkmsfb0 at radeon0 radeon0: info: registered panic notifier radeondrmkmsfb0: framebuffer at 0x80004a648000, size 1280x1024, depth 32, stride 5120 wsdisplay0 at radeondrmkmsfb0 kbdmux 1: console (default, vt100 emulation)