RE: 2.4.2ac8 lost char devices

RE: 2.4.2ac8 lost char devices

[Ashwin D]

Hi, 

I lost graphics on my i810 - failed to get minor is the error message on 
boot. 
Ashwin

Re: 2.4.2ac8 lost char devices

[rml]

actually, its not just ps/2 mice -- it seems to be something generic to char
devices. agpgartis failing to register itself, too.

what changed with char device handling from ac7 to ac8?

robert love
rml@ufl.edu

Re: 2.4.2ac8 lost char devices

[tachino Nobuhiro]

Hello, 

At Fri, 02 Mar 2001 00:42:28 -0500,
<rml@ufl.edu> wrote:
> 
> actually, its not just ps/2 mice -- it seems to be something generic to char
> devices. agpgartis failing to register itself, too.
> 
> what changed with char device handling from ac7 to ac8?
> 
> robert love
> rml@ufl.edu
> -

  misc_register() in drivers/char/misc.c seems to have a problem.


 int misc_register(struct miscdevice * misc)
 {      
        static devfs_handle_t devfs_handle;
-               
+       struct miscdevice *c;
+               
        if (misc->next || misc->prev)
                return -EBUSY;
        down(&misc_sem);
+       c = misc_list.next;
+               
+       while ((c != &misc_list) && (c->minor != misc->minor))
+               c = c->next;
+       if (c == &misc_list) {

  This should be  (c != &misc_list)

+               up(&misc_sem);
+               return -EBUSY;
+       }


---
Nobuhiro Tachino
Development Department
Linux Division
Software Group
FUJITSU LIMITED
TEL: +81 559 24 7273
FAX: +81 559 24 6196
E-Mail: tachino@open.nm.fujitsu.co.jp

Re: 2.4.2ac8 lost char devices

[Philipp Rumpf]

On Fri, Mar 02, 2001 at 03:05:32PM +0900, tachino Nobuhiro wrote:
> 
> Hello, 
> 
> At Fri, 02 Mar 2001 00:42:28 -0500,
> <rml@ufl.edu> wrote:
> > 
> > actually, its not just ps/2 mice -- it seems to be something generic to char
> > devices. agpgartis failing to register itself, too.
> > 
> > what changed with char device handling from ac7 to ac8?
> > 
> > robert love
> > rml@ufl.edu
> > -
> 
>   misc_register() in drivers/char/misc.c seems to have a problem.

I guess it's too late now to pretend it's not my fault.  I foolishly assumed
if it would boot for me I couldn't have broken it too badly.

> +       c = misc_list.next;
> +               
> +       while ((c != &misc_list) && (c->minor != misc->minor))
> +               c = c->next;
> +       if (c == &misc_list) {
> 
>   This should be  (c != &misc_list)

Correct.  Alan,


diff -ur linux/drivers/char/misc.c linux-prumpf/drivers/char/misc.c
--- linux/drivers/char/misc.c	Fri Mar  2 02:48:04 2001
+++ linux-prumpf/drivers/char/misc.c	Fri Mar  2 02:49:43 2001
@@ -180,7 +180,7 @@
 
 	while ((c != &misc_list) && (c->minor != misc->minor))
 		c = c->next;
-	if (c == &misc_list) {
+	if (c != &misc_list) {
 		up(&misc_sem);
 		return -EBUSY;
 	}

Re: 2.4.2ac8 lost char devices

[J . A . Magallon]

On 03.02 Mark Hahn wrote:
> > > > Well, somethig has broken in ac8, because I lost my PS/2 mouse and
> > > 
> > > me too </aol>.
> > > my theory at the moment is that perhaps the new apic feature
> > > killed it (I also had ioapic enabled).  mine's a kt133 system...
> > 
> > Mmmmmm, lets try noapic...
> 

No luck.

-- 
J.A. Magallon                                                      $> cd pub
mailto:jamagallon@able.es                                          $> more beer

Linux werewolf 2.4.2-ac7 #1 SMP Fri Mar 2 02:36:23 CET 2001 i686

Re: 2.4.2ac8 lost char devices

[Mark Hahn]

> > > > > Well, somethig has broken in ac8, because I lost my PS/2 mouse and
> > > > me too </aol>.
> No luck.

it seems to be the mdelay(2) added to pc_keyb.c in -ac6.

Re: 2.4.2ac8 lost char devices

[J Sloan]

Mark Hahn wrote:

> > > > > > Well, somethig has broken in ac8, because I lost my PS/2 mouse and
> > > > > me too </aol>.
> > No luck.

same here -

> it seems to be the mdelay(2) added to pc_keyb.c in -ac6.

-ac7 is fine here, but when I boot -ac8, there's no ps/2 mouse.

jjs

Re: 2.4.2ac8 lost char devices

[Tigran Aivazian]

On Thu, 1 Mar 2001, Mark Hahn wrote:

> > > > > > Well, somethig has broken in ac8, because I lost my PS/2 mouse and
> > > > > me too </aol>.
> > No luck.
> 
> it seems to be the mdelay(2) added to pc_keyb.c in -ac6.

are you sure? My bet is that it is to do with misc device registration as
I lost not just psaux but microcode device (which happens to be misc as
well)

Regards,
Tigran

2.4.2ac8 lost char devices

[J . A . Magallon]

Hi,

Well, somethig has broken in ac8, because I lost my PS/2 mouse and
(less important, but perhaps it is useful) the microcode driver. So
I think it something common to both.

The onle diff in dmesg from ac7 to ac8 is just the errors:

1c1
< Linux version 2.4.2-ac7 (root@werewolf.able.es) (gcc version 2.96 20000731
(Linux-Mandrake 8.0)) #1 SMP Fri Mar 2 02:36:23 CET 2001
---
> Linux version 2.4.2-ac8 (root@werewolf.able.es) (gcc version 2.96 20000731
(Linux-Mandrake 8.0)) #1 SMP Fri Mar 2 01:17:50 CET 2001
82c82
< Detected 400.917 MHz processor.
---
> Detected 400.914 MHz processor.
232,237c232,237
< ..... CPU clock speed is 400.8934 MHz.
< ..... host bus clock speed is 100.2232 MHz.
< cpu: 0, clocks: 1002232, slice: 334077
< CPU0<T0:1002224,T1:668144,D:3,S:334077,C:1002232>
< cpu: 1, clocks: 1002232, slice: 334077
< CPU1<T0:1002224,T1:334064,D:6,S:334077,C:1002232>
---
> ..... CPU clock speed is 400.8944 MHz.
> ..... host bus clock speed is 100.2233 MHz.
> cpu: 0, clocks: 1002233, slice: 334077
> CPU0<T0:1002224,T1:668144,D:3,S:334077,C:1002233>
> cpu: 1, clocks: 1002233, slice: 334077
> CPU1<T0:1002224,T1:334064,D:6,S:334077,C:1002233>
245c245,246
< IA-32 Microcode Update Driver: v1.08 <tigran@veritas.com>
---
> microcode: can't misc_register on minor=184
> microcode: failed to devfs_register()

What is microcode doing with devfs ? I have not configured devfs...

--
J.A. Magallon                                                      $> cd pub
mailto:jamagallon@able.es                                          $> more beer

Linux werewolf 2.4.2-ac7 #1 SMP Fri Mar 2 02:36:23 CET 2001 i686

Re: 2.4.2ac8 lost char devices

[Alan Cox]

> Well, somethig has broken in ac8, because I lost my PS/2 mouse and
> (less important, but perhaps it is useful) the microcode driver. So
> I think it something common to both.

Someone broke all the misc devices.  Patch coming in ac9 RSN