Bug#865928: linux-image-4.9.0-3-m68k: fails to boot on ARAnyM due to NMI watchdog / soft stuck

2017-06-25 Thread Finn Thain 
On Mon, 26 Jun 2017, Thorsten Glaser wrote:

> >> I think you ran into this issue:
> >>
> >> > https://patchwork.kernel.org/patch/8098441/
> 
> I use NatFeat disc only, though, not the ncr controller.

There is no working ncr controller provided by aranym, just a stub for 
one, sufficient to fool certain operating systems.

> While I agree that, in general, keeping workarounds for emulator bugs is 
> not desirable, there *are* workarounds for real hardware bugs, so 
> keeping one for a while until the emulator fixes have propagated,

Well, the kernel command line workaround should meet that need, for those 
aranym users who use a kernel with CONFIG_ATARI_SCSI enabled.

> but also something about probing a device crashing a machine (no idea 
> whether this affects other environments, though…) which is generally 
> unacceptable.
> 

Driver probe crashes aren't surprising if the emulated device is 
sufficiently broken.

> >See also the aranym patch I sent:
> >
> >https://sourceforge.net/p/aranym/bugs/40/
> >http://marc.info/?l=linux-m68k=145387217330168=2
> >
> >regression caused by a kernel improvement which exposed an aranym flaw.
> 
> Hm, true. Unfortunately, I cannot upgrade ARAnyM until I get a newer 
> kernel provided to Zigo’s domU (or switched to pvgrub-xen).
> 

The aranym fix was merged upsteam by Andreas Schwab on 2016-03-20.
https://sourceforge.net/p/aranym/code/ci/7af1cbfc5257d2c524ffe009790045d687c69fa5/

If you can't upgrade your emulator, why not ask the aranym maintainers to 
backport the fix?

> >This BTS entry should be reassigned to the aranym package. It's a
> 
> Unclear about that. Yes, there’s an emulator bug, but does that mean 
> there’s nothing to be done in the kernel?
> 

You just have to pursuade one of the driver maintainers that there is a 
real need.

Michael Schmitz and I are the maintainers for the upstream driver, and 
eighteen months ago he and I were in agreement: "Making the 5380 emulation 
a bit more complete such as in the MAME source snippet would be my 
preference". So that's what was done.

> I will just leave that to the parties responsible.
> 

Fair enough.

-- 

> bye,
> //mirabilos
>

Bug#865928: linux-image-4.9.0-3-m68k: fails to boot on ARAnyM due to NMI watchdog / soft stuck

2017-06-25 Thread Thorsten Glaser 
Finn Thain dixit:

>On Mon, 26 Jun 2017, John Paul Adrian Glaubitz wrote:
>> Which can be worked-around by adding
>> "initcall_blacklist=atari_scsi_driver_init" to the kernel command line.
>> The buildd "mama" is running 4.11 with that work around.

Looks like it:
Linux ara5.mirbsd.org 4.9.0-3-m68k #1 Debian 4.9.30-2 (2017-06-12) m68k 
GNU/Linux

ARAnyM 1.0.2
Using config file: 'buildd.nym-ssh'
>>> Missing value in Config file buildd.nym-ssh on line 8 !!!
Could not open joystick 0
ARAnyM RTC Timer: /dev/rtc: No such file or directory
Blitter tried to read byte from register ff8a00 at 006f86
[0.00] Linux version 4.9.0-3-m68k (debian-kernel@lists.debian.org) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 Debian 4.9.30-2 (2017-06-12)
[0.00] Atari hardware found:
[0.00] VIDEL
[0.00] STDMA-SCSI
[0.00] ST_MFP
[0.00] YM2149
[0.00] PCM
[0.00] CODEC
[0.00] DSP56K
[0.00] SCC
[0.00] ANALOG_JOY
[0.00] BLITTER
[0.00] IDE
[0.00] TT_CLK
[0.00] FDC_SPEED
[0.00]
[0.00] NatFeats found (ARAnyM, 1.0)
[0.00] initrd: 302a7e00 - 3100
[0.00] Built 2 zonelists in Zone order, mobility grouping on.  Total 
pages: 198237
[0.00] Kernel command line: root=/dev/nfhd8p1 console=nfcon 
devtmpfs.mount=1 initcall_blacklist=atari_scsi_driver_init BOOT_IMAGE=vmlinux
[0.00] PID hash table entries: 4096 (order: 2, 16384 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.00] Sorting __ex_table...
[0.00] Memory: 772724K/800768K available (2445K kernel code, 426K 
rwdata, 828K rodata, 144K init, 205K bss, 28044K reserved, 0K cma-reserved)
[0.00] Virtual kernel memory layout:
[0.00] vector  : 0x0036d858 - 0x0036dc58   (   1 KiB)
[0.00] kmap: 0xd000 - 0xf000   ( 512 MiB)
[0.00] vmalloc : 0x3180 - 0xd000   (2536 MiB)
[0.00] lowmem  : 0x - 0x3100   ( 784 MiB)
[0.00]   .init : 0x003a1000 - 0x003c5000   ( 144 KiB)
[0.00]   .text : 0x1000 - 0x002646d4   (2446 KiB)
[0.00]   .data : 0x002672a0 - 0x003a0d0c   (1255 KiB)
[0.00]   .bss  : 0x0036d760 - 0x003a0d0c   ( 206 KiB)
[0.00] NR_IRQS:200
[0.00] Console: colour dummy device 80x25
[0.07] Calibrating delay loop... 139.67 BogoMIPS (lpj=698368)
[0.07] pid_max: default: 32768 minimum: 301
[0.07] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.07] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.09] devtmpfs: initialized
[0.11] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 1911260446275 ns
[0.11] futex hash table entries: 256 (order: -1, 3072 bytes)
[0.11] NET: Registered protocol family 16
[0.15] SCSI subsystem initialized
[0.15] VFS: Disk quotas dquot_6.6.0
[0.15] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[0.20] NET: Registered protocol family 2
[0.21] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[0.21] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[0.21] TCP: Hash tables configured (established 8192 bind 8192)
[0.21] UDP hash table entries: 512 (order: 1, 8192 bytes)
[0.21] UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)
[0.21] NET: Registered protocol family 1
[0.21] Unpacking initramfs...
[0.75] Freeing initrd memory: 13664K (302a8000 - 3100)
[0.75] nfhd8: found device with 37748592 blocks (512 bytes)
[0.75]  nfhd8: AHDI p1 p2 p3
[0.77] console [nfcon0] enabled
[0.77] nfeth: API 5
[0.77] eth0: nfeth addr:192.168.0.1 (192.168.0.2) 
HWaddr:52:54:00:22:81:00
[0.78] workingset: timestamp_bits=11 max_order=18 bucket_order=7
[0.78] zbud: loaded
[0.81] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 
252)
[0.81] io scheduler noop registered
[0.81] io scheduler cfq registered (default)
[0.81] atafb_init: start
[0.81] atafb_init: initializing Falcon hw
[0.81] atafb: screen_base 00c42000 phys_screen_base c42000 screen_len 
311296
[0.81] Determined 640x480, depth 4
[0.81]virtual 640x972
[0.85] Console: switching to colour frame buffer device 80x30
[0.90] fb0: frame buffer device, using 304K of video memory
[0.90] pmac_zilog: 0.6 (Benjamin Herrenschmidt 
)
[0.90] Non-volatile memory driver v1.3
[0.90] mousedev: PS/2 mouse device common for all mice
[1.15] input: Atari Keyboard as /devices/virtual/input/input0
[1.40] rtc-generic rtc-generic: rtc core:

Bug#865928: linux-image-4.9.0-3-m68k: fails to boot on ARAnyM due to NMI watchdog / soft stuck

2017-06-25 Thread Finn Thain 
On Mon, 26 Jun 2017, John Paul Adrian Glaubitz wrote:

> On 06/26/2017 12:29 AM, Thorsten Glaser wrote:
> > I cannot boot Linux 4.9, but 4.1 still works. (I think 4.3 also 
> > failed, but I had autoremoved that already.)
> 
> I think you ran into this issue:
> 
> > https://patchwork.kernel.org/patch/8098441/
> 
> Which can be worked-around by adding 
> "initcall_blacklist=atari_scsi_driver_init" to the kernel command line. 
> The buildd "mama" is running 4.11 with that work around.
> 

See also the aranym patch I sent:

https://sourceforge.net/p/aranym/bugs/40/
http://marc.info/?l=linux-m68k=145387217330168=2

This BTS entry should be reassigned to the aranym package. It's a 
regression caused by a kernel improvement which exposed an aranym flaw.

-- 

> Adrian
> 
>

Bug#801759: Experiencing same problem with 4.9.0-3-686-pae

2017-06-25 Thread Nicholas Humfrey 

Hello,

I am also experiencing this problem.

During boot, the screen goes black and the display shows a "No signal 
detected" message.
Additionally, the machine stopped responding to pings, so may have 
kernel panicked - but could not find any evidence of this in any logs.


I am using the machine as a server, so do not need graphics/X11. So my 
solution was also to disable the gma500_gfx module by blacklisting it.



ii  linux-image-4.9.0-3-686-pae  4.9.30-2+deb9u1  i386  Linux 4.9 for 
modern PCs



nick.

Bug#860534: Similar bug

2017-06-25 Thread bugs . report . filter 

Hi.

I get a similar bug, but my system doesn't freeze, it directly reboot 
without any warning. I looked into all my logs files, nothing is 
reported by the system.


I've got the same GPU as the guy who reported this bug : AMD/ATI Juniper 
XT [Radeon HD 5770]


lspci :

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper XT [Radeon HD 5770] (prog-if 00 [VGA controller])

Subsystem: Gigabyte Technology Co., Ltd Juniper XT [Radeon HD 5770]
Flags: bus master, fast devsel, latency 0, IRQ 5, NUMA node 0
Memory at d000 (64-bit, prefetchable) [size=256M]
Memory at fdfc (64-bit, non-prefetchable) [size=128K]
I/O ports at ae00 [size=256]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 

Capabilities: [150] Advanced Error Reporting
Kernel modules: radeon

Regards.

Bug#865928: linux-image-4.9.0-3-m68k: fails to boot on ARAnyM due to NMI watchdog / soft stuck

2017-06-25 Thread John Paul Adrian Glaubitz 
On 06/26/2017 12:29 AM, Thorsten Glaser wrote:
> I cannot boot Linux 4.9, but 4.1 still works. (I think 4.3 also failed,
> but I had autoremoved that already.)

I think you ran into this issue:

> https://patchwork.kernel.org/patch/8098441/

Which can be worked-around by adding 
"initcall_blacklist=atari_scsi_driver_init" to the
kernel command line. The buildd "mama" is running 4.11 with that work around.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#865928: linux-image-4.9.0-3-m68k: fails to boot on ARAnyM due to NMI watchdog / soft stuck

2017-06-25 Thread Thorsten Glaser 
Package: src:linux
Version: 4.9.30-2
Severity: important

I cannot boot Linux 4.9, but 4.1 still works. (I think 4.3 also failed,
but I had autoremoved that already.)

ARAnyM console log for failed build:

-cutting here may damage your screen surface-
ARAnyM 1.0.2
Using config file: 'buildd.nym-ssh'
>>> Missing value in Config file buildd.nym-ssh on line 8 !!!
Could not open joystick 0
ARAnyM RTC Timer: /dev/rtc: No such file or directory
Blitter tried to read byte from register ff8a00 at 006f86
[0.00] Linux version 4.9.0-3-m68k (debian-kernel@lists.debian.org) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18) ) #1 Debian 4.9.30-2 (2017-06-12)
[0.00] Atari hardware found:
[0.00] VIDEL
[0.00] STDMA-SCSI
[0.00] ST_MFP
[0.00] YM2149
[0.00] PCM
[0.00] CODEC
[0.00] DSP56K
[0.00] SCC
[0.00] ANALOG_JOY
[0.00] BLITTER
[0.00] IDE
[0.00] TT_CLK
[0.00] FDC_SPEED
[0.00]
[0.00] NatFeats found (ARAnyM, 1.0)
[0.00] initrd: 302a7e00 - 3100
[0.00] Built 2 zonelists in Zone order, mobility grouping on.  Total 
pages: 198237
[0.00] Kernel command line: root=/dev/nfhd8p1 console=nfcon 
devtmpfs.mount=1 BOOT_IMAGE=vmlinux
[0.00] PID hash table entries: 4096 (order: 2, 16384 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.00] Sorting __ex_table...
[0.00] Memory: 772724K/800768K available (2445K kernel code, 426K 
rwdata, 828K rodata, 144K init, 205K bss, 28044K reserved, 0K cma-reserved)
[0.00] Virtual kernel memory layout:
[0.00] vector  : 0x0036d858 - 0x0036dc58   (   1 KiB)
[0.00] kmap: 0xd000 - 0xf000   ( 512 MiB)
[0.00] vmalloc : 0x3180 - 0xd000   (2536 MiB)
[0.00] lowmem  : 0x - 0x3100   ( 784 MiB)
[0.00]   .init : 0x003a1000 - 0x003c5000   ( 144 KiB)
[0.00]   .text : 0x1000 - 0x002646d4   (2446 KiB)
[0.00]   .data : 0x002672a0 - 0x003a0d0c   (1255 KiB)
[0.00]   .bss  : 0x0036d760 - 0x003a0d0c   ( 206 KiB)
[0.00] NR_IRQS:200
[0.01] Console: colour dummy device 80x25
[0.01] Calibrating delay loop... 138.64 BogoMIPS (lpj=693248)
[0.08] pid_max: default: 32768 minimum: 301
[0.09] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.09] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[0.11] devtmpfs: initialized
[0.12] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 1911260446275 ns
[0.12] futex hash table entries: 256 (order: -1, 3072 bytes)
[0.12] NET: Registered protocol family 16
[0.16] SCSI subsystem initialized
[0.16] VFS: Disk quotas dquot_6.6.0
[0.16] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[0.21] NET: Registered protocol family 2
[0.21] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[0.22] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[0.22] TCP: Hash tables configured (established 8192 bind 8192)
[0.22] UDP hash table entries: 512 (order: 1, 8192 bytes)
[0.22] UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)
[0.22] NET: Registered protocol family 1
[0.22] Unpacking initramfs...
[0.75] Freeing initrd memory: 13664K (302a8000 - 3100)
[0.76] nfhd8: found device with 37748592 blocks (512 bytes)
[0.77]  nfhd8: AHDI p1 p2 p3
[0.79] console [nfcon0] enabled
[0.79] nfeth: API 5
[0.79] eth0: nfeth addr:192.168.0.1 (192.168.0.2) 
HWaddr:52:54:00:22:81:00
[0.81] workingset: timestamp_bits=11 max_order=18 bucket_order=7
[0.81] zbud: loaded
[0.85] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 
252)
[0.85] io scheduler noop registered
[0.85] io scheduler cfq registered (default)
[0.85] atafb_init: start
[0.85] atafb_init: initializing Falcon hw
[0.85] atafb: screen_base 00c42000 phys_screen_base c42000 screen_len 
311296
[0.85] Determined 640x480, depth 4
[0.85]virtual 640x972
[0.86] Console: switching to colour frame buffer device 80x30
[0.88] fb0: frame buffer device, using 304K of video memory
[0.88] pmac_zilog: 0.6 (Benjamin Herrenschmidt 
)
[0.88] Non-volatile memory driver v1.3
[0.88] mousedev: PS/2 mouse device common for all mice
[1.13] input: Atari Keyboard as /devices/virtual/input/input0
[1.38] rtc-generic rtc-generic: rtc core: registered rtc-generic as rtc0
[1.38] ledtrig-cpu: registered to indicate activity on CPUs
[1.38] NET: Registered

Bug#704420: 'Fixed' in recent kernel versions

2017-06-25 Thread Nicholas Humfrey 

Hello,

There was a patch applied in 2014 that added the Atom CPU model (54 / 
0x36) to the list of CPUs that support intel_idle:


http://marc.info/?l=linux-pm=139068510624936=2


Unfortunately, I believe it has caused me quite a lot of pain today due 
to some machines not supporting Intel Idle correctly.


See #816751 for details.


nick.

Bug#816751: Boot hang also experienced in 4.9.0-3-686-pae

2017-06-25 Thread Nicholas Humfrey 

Hello,

I am also experiencing this problem, with a Jetway NF9C motherboard with 
an Intel NM10 chipset:

http://www.jetwaycomputer.com/NF9C.html

I experienced the problem while upgrading to Debian 9 (Stretch). I was 
previously running Debian 8 (Jessie) but I had not upgraded the kernel 
version from 3.2.78 because of the pain I had first experienced getting 
RTL8168 Ethernet working.



After upgrading the kernel to 4.9.30-2+deb9u1, the machine froze 
straight after starting the kernel on a normal boot. It got as far as 
detecting USB in 'recovery mode' before freezing. I tried various Debian 
installers on a USB stick and experienced the same freezing during 
kernel boot.



Due to the lack of relevant error messages, it was very difficult to 
diagnose the problem but after discovering that the 'nolacpi' kernel 
option allowed the machine to boot, it was enough to find this bug 
report.



Processor:
3rd Generation Intel® Atom Dual Core N2800 (1.86GHz@6.5W)

processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 54
model name  : Intel(R) Atom(TM) CPU N2800   @ 1.86GHz
stepping: 1
microcode   : 0x10d
cpu MHz : 798.000
cache size  : 512 KB


I worked around this problem by putting the following line in 
/etc/default/grub:


GRUB_CMDLINE_LINUX="intel_idle.max_cstate=0"

I don't know why this problem only appears to be affecting some machines 
but I can only assume that it has something to do with the BIOS, as it 
can't be affecting all machines with a Atom N2600/N2800 CPU ?


Thank you so much for reporting this Chad. I very much doubt that I 
would have identified the problem and solution without your bug report.



nick.

Bug#862723: closed by Ben Hutchings <b...@decadent.org.uk> (Bug#862723: fixed in linux 4.9.30-1)

2017-06-25 Thread Data Bot 
Hello,

Thank you for finding that cherryview kernel issue. Unfortunately, their
original patch is very limited as it's tied to an arbitrary BIOS date and
doesn't work for my machine. Would it be possible to also include better
quirk that went into 4.12? Please see v2 quirk in 194945 or
https://github.com/torvalds/linux/commit/2a8209fa68236ad65363dba03db5dbced520268a

Thank you in advance.

Bug#859639:

2017-06-25 Thread Magnus Wallin 
I can confirm this bug on a HP ProBook 6450b.

The exact same thing happens as Uwe has described with kernel:
4.9.0-3-amd64

--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com