> > But it also hangs, as it used to hang, when this driver was the newest > > one in sid: black screen, with the mouse pointer on and off > > periodically. This used to do, then I upgraded to newer intel, > > with the problems reported in this thread. > > Same with 2:2.2.0.90-2 which entered unstable today?
I don't know, see below. > > Jan 6 18:06:52 dabl kernel: Unbalanced enable for IRQ 17 > > Jan 6 18:06:52 dabl kernel: BUG: at kernel/irq/manage.c:158 > > enable_irq() > > Jan 6 18:06:52 dabl kernel: [<c014b54c>] enable_irq+0x6e/0xa2 > > Jan 6 18:06:52 dabl kernel: [<f8ba6da7>] probe_hwif+0x5c2/0x693 > > [ide_core] > > Jan 6 18:06:52 dabl kernel: [<f8ba954f>] > > do_ide_setup_pci_device+0x37e/0x3d4 [ide_core] > > Jan 6 18:06:52 dabl kernel: [<f8ba76e5>] > > probe_hwif_init_with_fixup+0xe/0x88 [ide_core] > > Jan 6 18:06:52 dabl kernel: [<c0190007>] dquot_alloc_space+0xf4/0x13c > > Jan 6 18:06:52 dabl kernel: [<f8ba967a>] > > ide_setup_pci_device+0x43/0x75 [ide_core] > > Jan 6 18:06:52 dabl kernel: [<f8838010>] jmicron_init_one+0xf/0x12 > > [jmicron] > > Jan 6 18:06:52 dabl kernel: [<c01d452f>] pci_device_probe+0x36/0x57 > > Jan 6 18:06:52 dabl kernel: [<c0227b06>] really_probe+0xbd/0x146 > > Jan 6 18:06:52 dabl kernel: [<c0227bd3>] driver_probe_device+0x44/0xa5 > > Jan 6 18:06:52 dabl kernel: [<c0227cb7>] __driver_attach+0x0/0x79 > > Jan 6 18:06:52 dabl kernel: [<c0227cfd>] __driver_attach+0x46/0x79 > > Jan 6 18:06:52 dabl kernel: [<c02271ae>] bus_for_each_dev+0x37/0x59 > > Jan 6 18:06:52 dabl kernel: [<c022798e>] driver_attach+0x16/0x18 > > Jan 6 18:06:52 dabl kernel: [<c0227cb7>] __driver_attach+0x0/0x79 > > Jan 6 18:06:52 dabl kernel: [<c0227460>] bus_add_driver+0x5e/0x15f > > Jan 6 18:06:52 dabl kernel: [<c01d468f>] __pci_register_driver > > +0x6b/0x97 > > Jan 6 18:06:52 dabl kernel: [<c013ed92>] sys_init_module+0x1698/0x17cf > > Jan 6 18:06:52 dabl kernel: [<f8843000>] uhci_hcd_init+0x0/0xa8 > > [uhci_hcd] > > Jan 6 18:06:52 dabl kernel: [<c015b75c>] do_mmap_pgoff+0x564/0x6c4 > > Jan 6 18:06:52 dabl kernel: [<f8ba50cf>] > > ide_config_drive_speed+0x0/0x31e [ide_core] > > Jan 6 18:06:52 dabl kernel: [<c0103d8c>] syscall_call+0x7/0xb > > Jan 6 18:06:52 dabl kernel: ======================= > > Jan 6 18:06:52 dabl kernel: ide0 at 0xbc00-0xbc07,0xb882 on irq 17 > > Jan 6 18:06:52 dabl kernel: Probing IDE interface ide1... > > This does not look good to me... IRQ problems can be bad... Let's hope > it is only related to the jmicron driver. Can you try without it? Unfortunately, this is a production computer (I am not even sitting at it) that I need to work very reliably, so I just installed the vesa driver and we didn't experience a single hang since then. I don't want to mess up with it, as this is just a pain for people working with it, when it freezes. We solved the problem by not using the intel driver and as to me, I am ok with this solution. I know it's not very helpful to find the real bug. But I am always testing the latest intel driver on my other computer, where I am not afraid of freezing, as I can easily fix it, and I am experiencing those font problems as I always report. Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
